With Mandriva 2010.2, this problem was not happening. This is new to Mageia 1. When inserting an audio CD in the tray, nothing is detected and no notification is displayed about a new media being available. But if I ask VLC to read the audio CD from /dev/cdrom, it plays the music correctly. In /etc/fstab, I can read: /dev/cdrom /media/cdrom auto umask=0,user,iocharset=utf8,noauto,ro 0 0 In /etc/fstab.old, I can read: /dev/cdrom /media/cdrom auto umask=0,users,iocharset=utf8,noauto,ro,exec 0 0 I guess fstab.old is the configuration file from Mandriva 2010, based on its timestamp (Dec 22, 2009).
Can you try to comment out that line and reboot? This line should not be needed at all.
CC: (none) => sander.lepik
(In reply to comment #1) > Can you try to comment out that line and reboot? This line should not be needed > at all. Didn't help. :(
Editing /etc/fstab and adding /dev/sr1 /media/cdrom auto umask=0,users,iocharset=utf8,noauto,ro,exec 0 0 to match what I had in Mandriva 2010.2 didn't help either.
Comment out the line, run "tail -f /var/log/syslog", insert an audio cd and copy/paste the lines added to syslog as a result of the cd being inserted (if any).
CC: (none) => davidwhodgins
(In reply to comment #4) > Comment out the line, run "tail -f /var/log/syslog", insert an audio cd and > copy/paste the lines added to syslog as a result of the cd being inserted (if > any). No lines added to syslog when inserting the CD.
Is haldaemon running? Use "service haldaemon status" to check.
# service haldaemon status hald (pid 888) est en cours d'exécution... So yes. :)
If that matters: note that I have two DVD drives.
Can you post the output of "ps -C hald-addon-storage -o command" and the contents of /etc/fstab?
$ ps -C hald-addon-storage -o command COMMAND hald-addon-storage: no polling on /dev/fd0 because it is explicitly disabled hald-addon-storage: polling /dev/sr1 (every 2 sec) hald-addon-storage: polling /dev/sr0 (every 2 sec) And their corresponding entries in /etc/fstab: /dev/sr1 /media/cdrom auto umask=0,users,iocharset=utf8,noauto,ro,exec 0 0 /dev/sr0 /media/cdrom2 auto umask=0,users,iocharset=utf8,noauto,ro,exec 0 0 /dev/fd0 /media/floppy auto umask=0,users,iocharset=utf8,noauto,exec,flush 0 0
Remove the entries for /dev/sr0 an /dev/sr1 from fstab. If they are there, that guarantees that the device notifier will not be called. Also remove the directories /media/cdrom and /media/cdrom2. The mountpoints are created/deleted by hal when the filesystems are mounted/unmounted. After removing the entries/directories, in a terminal (konsole, etc), run (as root) "udevadm monitor info", then insert the audio cd. This will confirm whether or not udev is getting the insertion event.
KERNEL[1307396009.673932] change /devices/pci0000:00/0000:00:0e.0/host1/target1:0:0/1:0:0:0/block/sr0 (block) UDEV [1307396009.861625] change /devices/pci0000:00/0000:00:0e.0/host1/target1:0:0/1:0:0:0/block/sr0 (block)
So udev is seeing the cdrom insertion event. Is your loginid in the group cdrom? If not, add it using userdrake, then logout/in for the group change to take affect, then try again with the cdrom.
(In reply to comment #13) > Is your loginid in the group cdrom? Yes, it is. :-/
Is the device notifier in the system tray? Which desktop manager are you using? What's the output of "getfacl /dev/sr0"?
(In reply to comment #15) > Is the device notifier in the system tray? Yes, but it says there is no new device. > Which desktop manager are you using? KDE 4.6.3 > What's the output of "getfacl /dev/sr0"? # getfacl /dev/sr0 getfacl : suppression du premier « / » des noms de chemins absolus # file: dev/sr0 # owner: root # group: cdrom user::rw- user:buclin:rw- group::rw- mask::rw- other::---
Do you have any applications that device notifier can use to play audio cds installed? When I put in an audio cd, it shows 2 actions, play with amarok, or play with kaffeine.
I have neither amarok nor kaffeine installed, so I have no idea what the device notifier tries to use next. But I have VLC installed, so the notifier could use it, assuming it's able to detect something. :) Or at least tell me that an audio CD is inserted.
Please install either one of them, and see if that fixes the problem. If it does, then the bug report should be changed to vlc not creating whatever file is used by the device notifier, to indicate that it is capable of playing audio cds.
Installing Kaffeine fixes the problem. A notification appears when inserting an audio CD and offers to open it with Kaffeine. Thanks for helping me track this down. :) Morphing the bug summary as suggested by Dave in comment 19.
Summary: Inserting an audio CD in the tray is not detected => The device notifier is not aware that VLC can play audio CDsSource RPM: (none) => vlc-1.1.9-4.mga1.tainted
In the meantime, you can copy the kaffeine files in /usr/share/apps/solid/actions/ to start with vlc, and change all occurrences of kaffeine to vlc in those files.
Created attachment 556 [details] patch for vlc-opencda.desktop Actually, there is already a file named /usr/share/apps/solid/actions/vlc-opencda.desktop, but it triggers no action. If I replace X-KDE-Solid-Predicate=[ StorageVolume.ignored == false AND OpticalDisc.availableContent & 'Audio' ] by X-KDE-Solid-Predicate=OpticalDisc.availableContent & 'Audio' then it works fine. See also https://bugs.launchpad.net/kubuntu-ppa/+bug/709868
This looks like a general problem in solid, it affects kde4-audiocd and kscd too. Same issue, same fix, so upstream should fix whatever it broke...
CC: (none) => balcaen.john
Upstream bug: https://bugs.kde.org/show_bug.cgi?id=265870, but it gets no traction.
See Also: (none) => https://bugs.kde.org/show_bug.cgi?id=265870, https://launchpad.net/bugs/709868
Until upstream fix this properly, could we have a fix in VLC, please?
CC: (none) => doktor5000
CC: (none) => stephengermany
Assigning to maintainer now that our maintainers database has an entry for this package. Please assign back to bugsquad@mageia.org in case of a mistake from me.
CC: (none) => stormiAssignee: bugsquad => shlomif
*** Bug 2928 has been marked as a duplicate of this bug. ***
CC: (none) => derekjenn
As stated by Ahmad in comment 23, the real bug is in solid udisks backend (kdelibs). FYI, I've just submit a patch for this bug on kde review board. https://git.reviewboard.kde.org/r/102892 regards, Luc
Keywords: (none) => UPSTREAMURL: (none) => https://git.reviewboard.kde.org/r/102892CC: (none) => lmenutHardware: i586 => AllWhiteboard: (none) => affects Mageia 1 and Cauldron, patch in review upstream
Patch now accepted upstream. This bug should be fixed with: - lib(64)solid4-4.6.5-1.3.mga1 for mga1 in update_testing (update candidate bug #3090 for validation by QA team), - lib(64)solid4-4.7.2-5.mga2 for cauldron.
Assignee: shlomif => lmenutSource RPM: vlc-1.1.9-4.mga1.tainted => kdelibs4-4.6.5Whiteboard: affects Mageia 1 and Cauldron, patch in review upstream => affects Mageia 1 and Cauldron
Testing complete on i586 for the srpm kdelibs4-4.6.5-1.3.mga1.src.rpm Before the installation, amarok was the only option shown by the device notifier, for an audio cd. After installation, and restarting kde, the device notifier is showing 7 options for an audio cd, including vlc.
Confirmed bug fixed on x86_64 No regressions found elsewhere so far.
Works for me too on i586. Congratulations and thanks for the fix, Luc. :)
Could someone from the sysadmin team push the srpm kdelibs4-4.6.5-1.3.mga1.src.rpm From core updates testing to core updates. Advisory: This bug update to kdelibs4 fixes a problem in solid, that prevented the device notifier from recognizing all applications that could handle an audio cd. https://bugs.mageia.org/show_bug.cgi?id=1594
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
(if qa-bugs is not in cc or assigned to this bug, users who user the updates-push saved search don't see this one)
CC: (none) => qa-bugs
As stated in comment 29, there is already an update candidate bug - bug #3090 - assigned to qa-bugs with advisory and how to test. Please use it, instead of this one (this one is only a special case).
as there is another bug open for the update, and it's already reported as resolved here I think we can close this one.
Keywords: validated_update => (none)Status: NEW => RESOLVEDCC: qa-bugs, sysadmin-bugs => (none)Resolution: (none) => FIXED