After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 484535 - Sound-juicer don't unlock drive on exit : brasero fails to burn
Sound-juicer don't unlock drive on exit : brasero fails to burn
Status: RESOLVED FIXED
Product: sound-juicer
Classification: Applications
Component: general
2.20.x
Other Linux
: Normal normal
: ---
Assigned To: Sound Juicer Maintainers
Sound Juicer Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-07 22:54 UTC by Florent Mertens
Modified: 2007-10-08 18:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Florent Mertens 2007-10-07 22:54:20 UTC 
sound-juicer lock drive at startup via hal , but it only unlock it when ejecting the drive,
and so when you exit normally, the drive is still locked.
A consequence is that applications that respect this lock, like brasero, refuse to go ahead.

Step to reproduce :

- Start sound-juicer (even if you don't have a CD on your drive)
- Exit it normaly.
- Insert a blank CD in your drive
- Normaly you should have a dialog that ask you if you want to burn an audio
  CD or a data CD, but here you have nothing : the drive is locked (you can also check that with hal-device-manager).
- Start brasero or burn:/// and try to burn something : it will fail.
  Serpentine will work, but it's only because it don't respect the lock state.

Original report : https://bugs.edge.launchpad.net/ubuntu/+source/sound-juicer/+bug/131475
Comment 1 Ross Burton 2007-10-08 18:04:46 UTC 
This is strictly speaking a HAL bug, it should unlock the device if the application quits.  For example if SJ crashed, the drive would remain locked.

That said, I've fixed this in svn.