Description of problem: The Samsung YP-S2 player is classed as removable hard drive rather than a digital audio player. This means it isn't recognised by Rhythmbox et al as an audio device. Version-Release number of selected component (if applicable): hal-0.5.12-14.20081027git.fc10.x86_64 How reproducible: Consistent Steps to Reproduce: 1. Plug player into USB 2. Player is automounted 3. Properties show it as a removable hard drive - doesn't show as a device on Rythmbox Actual results: Expected results: Additional info: content from /var/log/messages on mounting device: Jan 26 21:09:05 localhost kernel: usb 1-5: new high speed USB device using ehci_hcd and address 5 Jan 26 21:09:05 localhost kernel: usb 1-5: configuration #1 chosen from 1 choice Jan 26 21:09:05 localhost kernel: scsi6 : SCSI emulation for USB Mass Storage devices Jan 26 21:09:05 localhost kernel: usb 1-5: New USB device found, idVendor=04e8, idProduct=5095 Jan 26 21:09:05 localhost kernel: usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jan 26 21:09:05 localhost kernel: usb 1-5: Product: YP-S2 Jan 26 21:09:05 localhost kernel: usb 1-5: Manufacturer: Samsung Electronics Jan 26 21:09:05 localhost kernel: usb 1-5: SerialNumber: 2A05FDB96EF00000 Jan 26 21:09:11 localhost kernel: scsi 6:0:0:0: Direct-Access Samsung YP-S2 1.00 PQ: 0 ANSI: 2 Jan 26 21:09:11 localhost kernel: sd 6:0:0:0: [sdc] 1929216 512-byte hardware sectors (988 MB) Jan 26 21:09:11 localhost kernel: sd 6:0:0:0: [sdc] Write Protect is off Jan 26 21:09:11 localhost kernel: sd 6:0:0:0: [sdc] Assuming drive cache: write through Jan 26 21:09:11 localhost kernel: sd 6:0:0:0: [sdc] 1929216 512-byte hardware sectors (988 MB) Jan 26 21:09:11 localhost kernel: sd 6:0:0:0: [sdc] Write Protect is off Jan 26 21:09:11 localhost kernel: sd 6:0:0:0: [sdc] Assuming drive cache: write through Jan 26 21:09:11 localhost kernel: sdc: Jan 26 21:09:11 localhost kernel: sd 6:0:0:0: [sdc] Attached SCSI removable disk Jan 26 21:09:11 localhost kernel: sd 6:0:0:0: Attached scsi generic sg3 type 0 Jan 26 21:09:11 localhost gnome-keyring-daemon[2874]: adding removable location: volume_uuid_E475_59CB at /media/S2 Jan 26 21:09:11 localhost hald: mounted /dev/sdc on behalf of uid 500
Have you tried with the latest hal package in Fedora 10, Fedora 11 or tried Rawhide? In either case, can you let us know whether the issue is still happening, and give the current version of the HAL packages you're using? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
No further action needed