GCDMaster doesn't work in Hardy

[Dingbats]

I have just installed Hardy Heron, and now gcdmaster doesn't work. When I run sudo gcdmaster project.toc, I get this over and over (you have to run it as root):

Error trying to open /dev/scd0 exclusively (Device or resource busy)... retrying in 1 second.

When I run it with gksudo, it opens fine. It only recognizes the burner the first time I try it after logging in. Then when I try to burn the CD, the burning process dialog opens and after a few seconds it says that it aborted with error.

After a failed attempt at burning, Ubuntu won't recognize the disk drive at all. If I insert a CD (empty/burned/music) nothing happens.

gcdmaster also takes abnormally long to open. It used to work just fine in Gutsy.

Please please tell me there is a way around this!

[Dingbats]

No one..? :(

[billd42]

No help here, but I get the same error. I'm just getting started on the project of ripping a substantial vinyl collection to digital, so I've no idea whether this worked under Gutsy.

[Stochastic]

Actually I get the same error for about 10 consecutive times, then it changes to /dev/hda for about 30 times (each error takes a full second, obviously) but then the app loads. It seems to be able to play files and add songs. I didn't attempt to open any .toc files, save a project, or burn a CD, so if anyone wants to give that a shot and report back...

I ran an strace and it looks like there's lots of bad requests going on, though I'm only beginning to be able to read those files.

Here's a launchpad bug that describes the issue: https://bugs.launchpad.net/ubuntu/+source/cdrdao/+bug/2765 that seems to have been around for the past two and a half years. There's a supposed fix linked to in the comments, but nothing has been acted on (from what I see) to get the fix into the repos (despite the fix being posted back in 2006 and the bug being on the top of the "Ubuntu Burning Team" list of four bugs). Though I've yet to try the fix myself for confirmation.
---Calling all devs, someone please take action---

The long and short of this is that the app looks promising, but I would never use an app with this many VISIBLE errors in any mastering process.

[andrew.46]

Hi,

I seem to have perhaps a variation of this problem. The cdrdao command works fine:

andrew@skamandros:~$ sudo cdrdao scanbus
Cdrdao version 1.2.2 - (C) Andreas Mueller <andreas@daneb.de>
SCSI interface library - (C) Joerg Schilling
Paranoia DAE library - (C) Monty

Check http://cdrdao.sourceforge.net/drives.html#dt for current driver tables.

Using libscg version 'ubuntu-0.8ubuntu1'

1,0,0 : Optiarc , DVD+-RW AD-5560A, DD11


But the program gcdmaster does not work at all. Not a big problem for me as I prefer the command line version :-).

Andrew

[andrew.46]

Hi,

There may be a way:

Please please tell me there is a way around this!

gcdmaster is simply a front for cdrdao. Have a look at:

http://ubuntuforums.org/showthread.php?t=795181

which I wrote a couple of days ago and see if this works where gcdmaster fails.

Andrew

[Stochastic]

Have a look at:

http://ubuntuforums.org/showthread.php?t=795181

which I wrote a couple of days ago and see if this works where gcdmaster fails.

Um, that's only for copying CDs, gcdmaster is not intended for simply copying CDs.

[andrew.46]

Hi,

Um, that's only for copying CDs, gcdmaster is not intended for simply copying CDs.

cdrdao will do everything that gcdmaster does (gcdmaster being only a front-end) and unlike gcdmaster it works under Hardy Heron. The guide does not deal explicitly with more complex material as it is intended only as a beginning.

Andrew

[tmndz]

Well, today the problem reached me: GCDMaster starts extremely slow and finds no devices, cdrdao can't scan devices.
What happens is that GCDMaster on startup as well as "cdrdao scanbus" attempts to open all available character devices /dev/sg0, /dev/sg1, and so on.
On my system, /dev/sg0 is related to my harddrive /dev/sda and belongs to the group "disk", whereas /dev/sg1 is for the CDROM drive and belongs to the "cdrom" group.
So, as quick'n'dirty workaround, I added myself to the group "disk" and everything now is working as it should.