Salix Forums

Just tried this for the first time, and all I get is a message that disappears before I can read it. I worked out that you need to put a symlink to the data in /tmp/burn, so it wasn't that.

Also, there is an option to check all the apps that are called are present, and one was missing, normalize. But that wasn't the cause of this problem.

I just installed Brasero and used that instead, so this is just to report the problem

Confirmed. I just tried burning a DVD iso with bashburn and nothing happened. No error message I could see. Maybe it flashed too fast for me to even notice.

A package for current is here (with capital letters in slightly different places this time):

http://people.salixos.org/mimosa/packag ... burn/3.1.0

and all I can get this latest version to do is eject a CD.

The initial configuration now asks you to tell it where to look for the CD / DVD; maybe none of the various things I tried was right. Basically /dev/sr0, /mnt/cdrom - using some of the suggested options.

If no-one else can make it work I'd suggest this isn't worth bothering with, and furthermore, it would be good to choose a different app for the Ratpoison edition this time round.

laprjns has suggested it may be worth looking at the Arch PKGBUILD. However, even if there is a problem with the build, I'm not sure if I'm doing the initial configuration right (on first run).

This part of the app seems identical to the previous version, and I can't get that to work either. Specifically, the user is asked to input where to look for the "CD-Writer" (suggested 0,0,0 for SCSI or /dev/hdX for IDE); "CD-Reader Device file" (suggested /dev/cdrom, but I think it should be /dev/sr0); and "CD-Reader Mount point" (suggested /mnt/cdrom, I also tried /media/cdrom). I've tried a lot of combinations, but nothing will mount, though "Eject /dev/sr0" does what you might expect.

Looks to me like bashburn is looking in fstab for the mount points. After I uncommented the following line in my fstab; I was able to mount, unmount and eject using /mnt/cdrom

Everything mounted with gvfs in current/14.0, is mounted under /run/media/username/. So, if you're mounting devices with gmountman, that's where they go.

I'm not running it on current, for the time being. I'm not even running the new version. I'm just trying to get the basic configuration to work - as far as the software is concerned, it's the same.

@ gapan both you and I had trouble with this app (see above). The question is was that because of an error with this initial configuration (even if that needs to be done differently for current) or for some other reason? If the latter, it may now have been fixed.

So my first step is to get the configuration to work.

If that is going to be different depending whether you happen to use gmountman during a particular session (not sure whether I have understood this correctly) then I'd say that also tells against bashburn as a usable partner for the Ratpoison edition.

Ok here a summary of my testing:

bashburn 3.0.1 on salix 13.37
Application runs (no flashing) both as a normal user and root
Can mount, dismount and eject as root with fstab line uncommented (see my 1st post), normal user can't do this (I suspect that user has to be in the sudo group
bashburn 3.1.0 on salix 12.27
Application runs (must delete the ~./bashburnrc and ~/.bashburn_history from 3.0.1 files prior to first run)
Both root and normal users can mount, dismount and eject if fstab line is uncommented

bashburn 3.1.0 on Salix current
Application runs
Both root and normal users can mount, dismount and eject if fstab line is uncommented
Does not seem to work by defining /run/media/rich/ in the configuration files.

From this I concluded that the application doesn't work with the auto detection features in both 13.37 and current, but rather just looks in fstab for valid mount points.

Odd though that it lets you put whatever you like during configuration - the fstab entries just look like suggestions.

So the question before anyone spends more time on this is whether it is desirable to have an app that requires that line in fstab to be uncommented as the default CD/DVD burner etc in the Ratpoison edition?

A further consideration is whether it will actually burn anything, even with the fstab line uncommented. That was the original error last time.

I uncommented the line in fstab, and Gmountman doesn't see a cd in the drive. Recomment and call Gmountman again, it does.