Fri 11 Feb 2005 01:21:35 AM UTC, comment #11:
Ok, Thanks a lot!
|
Wed 02 Feb 2005 08:00:48 PM UTC, comment #10:
I've updated 0.3.4 to 0.3.5 on my Fedora Core 3 system and just burned a data CD without any issues. In my grave.conf file the dev= line is dev=OLD|/dev/hdc. I think that line changed when I upgraded to 0.3.4, as I had manually entered dev=/dev/hdc on prior releases. If it helps, I've attached my graveman.conf file.
As reported before, the only thing I had to do manually was chnage the ICON line in the .desktop file from ICON=graveman.png to ICON=/usr/local/share/pixmaps/graveman.png. That change then allowed the icon to appear next to the graveman launcher in the Applications>Accessories menu. Not sure why FC3 isn't picking up the PNG without an absolute path...perhaps due to compiling from source(?).
Bob
|
Wed 02 Feb 2005 07:03:42 PM UTC, comment #9:
Hi,
This manual change on dev= line in graveman.conf doesn't work anymore with graveman 0.3.5.
Please can you compile graveman with debug mode support,
remove your current ~/.graveman/graveman.conf file and then
send me graveman output while detecting drives and while
burning CD ?
Thanks,
Sylvain
|
Wed 02 Feb 2005 06:29:14 PM UTC, comment #8:
Hi everyone. I compiled 0.3.5 fine on an Ubuntu Warty system and run into exactly the same error message, whenever I try to burn a cd.
I did the manual changes to the graveman.conf as suggested by Oliver Gravert on the Ubuntu mailing-list (changed device to /dev/hdc as my burning device is mounted as /dev/hdc in /etc/fstab).
As read here, I disabled automounting devices in the gnome-menu and unmounted /dev/hdc, still getting the same errors :(
Additionally, I attach my graveman.conf.
Greets,
Bernhard
|
Wed 26 Jan 2005 02:49:53 AM UTC, comment #7:
First of all, thank you very much for all your comments and research !
I will look in detail all that you have say to me before answering you. graveman send to you many messages on terminal, this is the only difference. But because this a beta release, maybe you can keep it some days again ! ;-)
I advise you to download the version 0.3.4 which corrects another problem.
Sylvain
|
Tue 25 Jan 2005 11:15:28 PM UTC, comment #6:
Just fixed the missing icon issue as well. The graveman.desktop file had the "Icon" line as "Icon=graveman.png". I changed it to "Icon=/usr/local/share/pixmaps/graveman.png" (where it actually is located) and now I have the icon in my Accessories launcher menu.
I'm beginning to think that the launcher would have worked all along had the dev= line in the graveman.conf file been correct. When it didn't work and I had to have root access to launch at the command line, that's why I thought I had root only access. I just tried to launch graveman from the command line with my non-root user ID and now that is working as well. So it appears that ID'ing the CD burner as ATAPI:1,0,0 (or whatever it was) rather than /dev/hdc (in my case) was the problem.
I now have graveman compiled and installed with the debug mode enabled. Should I reinstall without it active or just leave it alone?
Bob
|
Tue 25 Jan 2005 10:39:30 PM UTC, comment #5:
Working now!
While I still get the behavior with device detection as listed below when run from the command line, after following Oliver's instructions to change the device ID to /dev/hd*, graveman now launches from the Applications>Accessories menu. I should add that I had to edit the graveman.conf file with both Oliver's suggestion AND I had to enter my max burn speed as that line did not have any number (i.e. it was "vitesse=" and I changed it to "vitesse=52". I've attached my current graveman.conf. Device detection now works perfectly and it is remembered after quitting and launching again. I have been able to burn an ISO image to a CD with graveman.
One section of graveman.conf that is interesting is below:
[lecteur]
dev=OLD|/dev/hdc
actu=0
name=LITE-ON LTR-52327S Removable CD-ROM
type=15
vitesse=52
manual=0
I did not enter the dev=OLD|/dev/hdc, actu=0, or manual=0 lines. As I've said, the device line I entered was dev=/dev/hdc. Somehow those lines were changed by graveman or the system.
As of right now, I have graveman 0.3.3 working on my Fedora Core 3 system when launched from the Applications>Accessories menu. The only problem as of now is there is no icon in the Accessories menu associated with graveman. I've got to dig further to figure out this issue...I suspect it is a problem with the .desktop file not pointing to the correct location for the icon.
Bob
|
Tue 25 Jan 2005 08:06:35 PM UTC, comment #4:
Also found this thread (http://www.ubuntuforums.org/showthread.php?t=12057&page=1&pp=10) on the Ubuntu forums. Looks like there are others experiencing the same issues with this bug, as well as my problem of root-only access. I tried Oliver's suggestion of changing my device listing to dev=/dev/hdc (my burner is hdc per fstab), but it didn't work. ID'ing the CD burner specifically (i.e. /dev/hdc) still doesn't fix the device detection. I just relaunched graveman and it has lost detection of my CD burner (darn, I really thought this might work.) I don't know anything about programming (as I'm about to prove) but could this issue be something with SCSI emulation for the CD burner which neither Fedora or Ubuntu use?
Bob
|
Tue 25 Jan 2005 04:17:05 PM UTC, comment #3:
OK, let's see if I did this correctly. Attached is the debug output, along with some screenshots.
I'm seeing some odd behavior with graveman and I'm not sure if it's me or the app. In screenshot "graveman-bar", after adding and removing several files notice the bar indicating the size of the files to be burned.
In screenshot "graveman-settings" I find I cannot set any device in the "Duplicate to:" dropdown other than "ISO." And the "Speed" setting doesn't seem to do anything. I expected it just to say something like "Max" (as in Nautilus). But since I can't choose anything other than ISO to duplicate to I guess that makes speed irrelevent(?).
Lastly, a screenshot (gravenman-error) of the actual error being reported.
I've also had problems with the burner detection. I expected graveman to find my device(s) during installation and retain knowledge of them. That has not proven to be true. I have had to detect devices again when relaunching graveman. What happens is when I first scan for devices graveman finds three. Two are "NON CCS" disks and the third is my CD burner.
However, each time I open and close graveman one of these devices dissappears until, by the fourth time I launch graveman, I have no devices showing as detected again. I have the debug data from the device detection and have attached it. Hopefully it is useful.
Lastly, as I noted in my email to you, I can only run graveman from root. There is a launcher in Applications>Accessories but it is not funtional. I've attached a screenshot graveman-launcher that shows the launcher in mu user menu but it doesn't work and hasn't found the graveman image file for the icon.
Hopefully all this is of some help Sylvain. Anything else you need please let me know.
Bob
|
Tue 25 Jan 2005 07:39:36 AM UTC, comment #2:
Can you compile graveman with debug mode and send me
graveman output ?
To compile graveman with debug type:
./configure --enable-debug
|
Tue 25 Jan 2005 06:24:16 AM UTC, comment #1:
cdrecord version 2.01.1-5 for Fedora Core 3.
|
Tue 25 Jan 2005 06:17:52 AM UTC, original submission:
Trying to burn a data CD (ISO file) generates this error. Was able to burn ISO to CD using Nautilus without problems. Using Fedora Core 3. Not sure what other info you need. please let me know...I'm willing to help.
Bob
|