Hide Forgot
Created attachment 486829 [details] Output of "Scan Removable Media" in debug mode. Description of problem: Rhythmbox is not detecting CDs inserted into an internal drive (/dev/sr0) and thus I can not play them. Version-Release number of selected component (if applicable): 0.13.3-1.fc14 How reproducible: I've tried it in both KDE and XFCE with the same result. Steps to Reproduce: 1. Open Rhythmbox 2. Insert CD into internal drive 3. Wait and/or click Scan Removable Media Actual results: No visible changes to rhythmbox window Expected results: Some "Play CD" option should become apparent. Additional info: Attached is the result of the "scan media" command. With reference to bug https://bugzilla.redhat.com/show_bug.cgi?id=527100 this is the output of "gvfs-mount -li" Drive(0): CD/DVD Drive Type: GProxyDrive (GProxyVolumeMonitorGdu) ids: unix-device: '/dev/sr0' themed icons: [drive-optical] [drive] is_media_removable=1 has_media=1 is_media_check_automatic=1 can_poll_for_media=1 can_eject=1 can_start=0 can_stop=0 start_stop_type=unknown Volume(0): Audio Disc Type: GProxyVolume (GProxyVolumeMonitorGdu) ids: unix-device: '/dev/sr0' activation_root=cdda://sr0/ themed icons: [media-optical-audio] [media-optical] [media] can_mount=1 can_eject=1 should_automount=1 Drive(1): 320 GB Hard Disk Type: GProxyDrive (GProxyVolumeMonitorGdu) ids: unix-device: '/dev/sda' themed icons: [drive-harddisk-ata] [drive-harddisk] [drive] is_media_removable=0 has_media=1 is_media_check_automatic=0 can_poll_for_media=0 can_eject=0 can_start=0 can_stop=0 start_stop_type=unknown Volume(0): WIN Type: GProxyVolume (GProxyVolumeMonitorGdu) ids: uuid: '26D244D46572ECD0' unix-device: '/dev/sda1' label: 'WIN' themed icons: [drive-harddisk-ata] [drive-harddisk] [drive] can_mount=1 can_eject=0 should_automount=0 Volume(1): GRUB Type: GProxyVolume (GProxyVolumeMonitorGdu) ids: uuid: 'd4e581a8-d5f2-4d5c-8447-2847bc5dd9be' unix-device: '/dev/sda3' label: 'GRUB' themed icons: [drive-harddisk-ata] [drive-harddisk] [drive] can_mount=1 can_eject=0 should_automount=0 Volume(2): DEB Type: GProxyVolume (GProxyVolumeMonitorGdu) ids: uuid: 'ee37c109-2626-4dbf-8527-4948d58f6fdf' unix-device: '/dev/sda7' label: 'DEB' themed icons: [drive-harddisk-ata] [drive-harddisk] [drive] can_mount=1 can_eject=0 should_automount=0 Volume(3): 27 GB Filesystem Type: GProxyVolume (GProxyVolumeMonitorGdu) ids: uuid: '05278ca7-8334-4022-ac7c-a9fcd8052b68' unix-device: '/dev/sda8' themed icons: [drive-harddisk-ata] [drive-harddisk] [drive] can_mount=1 can_eject=0 should_automount=0
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping