Bug 9801 - LXDE Inserting an audio CD gives a popup error 'Cannot find drive /dev/sr0'
Summary: LXDE Inserting an audio CD gives a popup error 'Cannot find drive /dev/sr0'
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard: 3RC
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-19 19:52 CEST by claire robinson
Modified: 2013-05-15 18:19 CEST (History)
4 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
journalctl -a --no-pager > journal (114.18 KB, application/octet-stream)
2013-04-19 20:16 CEST, claire robinson
Details

Description claire robinson 2013-04-19 19:52:19 CEST
3RC lxde installation from i586 classic dvd (3rd build 19th april)

Grip was giving a message saying it wasn't able to initialise the drive so tried with an audio cd inserted.

Closed grip.

Inserting a CD generates a popup error on the desktop 'Cannot find drive /dev/sr0'

Tested with a 2nd drive and get the same error for /dev/sr1


Reproducible: 

Steps to Reproduce:
claire robinson 2013-04-19 19:52:54 CEST

CC: (none) => ennael1, oliver.bgr

claire robinson 2013-04-19 19:53:07 CEST

CC: (none) => mageia

claire robinson 2013-04-19 19:53:22 CEST

Whiteboard: (none) => 3RC

Comment 1 claire robinson 2013-04-19 20:10:00 CEST
I think this is linked to power saving after a period of inactivity and linked to bug 8073

After logging out and back in it reads the cd fine and the error is gone.
Comment 2 claire robinson 2013-04-19 20:16:20 CEST
Created attachment 3768 [details]
journalctl -a --no-pager > journal
Comment 3 claire robinson 2013-04-19 21:06:10 CEST
xsession-errors in attachment 3769 [details]
claire robinson 2013-04-26 09:42:37 CEST

CC: (none) => yochenhsieh

Comment 4 claire robinson 2013-05-13 22:35:20 CEST
see also 9522 which may be related
Comment 5 claire robinson 2013-05-15 18:19:42 CEST
Closing as fixed as I can't reproduce this now.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.