Hide Forgot
Description of problem: After starting Rhythmbox after booting or rebooting or logout and login then there is warning window "Media player device error Unable to open the (null) (null) device" Version-Release number of selected component (if applicable): rhythmbox-2.90.1-4.git20110207.fc15.x86_64 How reproducible: Always Steps to Reproduce: 1. Logout/login 2. Start rhythmbox 3. Actual results: Rhythmbox starts and works, but there is warning window "Media player device error Unable to open the (null) (null) device" Expected results: No warning Additional info: Rythminbox is working ok. This warning is not in F13 or F14. F15 runs from sdb10 content in music folder is on sda1 mounted with fstab. staring from terminal similar [floki@f15al ~]$ rhythmbox Gtk-Message: Failed to load module "pk-gtk-module" (rhythmbox:5435): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (rhythmbox:5435): Gtk-WARNING **: Unknown property: GtkDialog.has-separator (rhythmbox:5435): Rhythmbox-WARNING **: Unable to start mDNS browsing: MDNS service is not running (rhythmbox:5435): libdmapsharing-WARNING **: Unable to initialize mDNS: Daemon not running (rhythmbox:5435): libdmapsharing-WARNING **: Unable to start music sharing server (IPv4) (rhythmbox:5435): libdmapsharing-WARNING **: Unable to notify network of media sharing: The avahi MDNS service is not running (rhythmbox:5435): libdmapsharing-WARNING **: Unable to start Remote lookup: MDNS service is not running ** (rhythmbox:5435): WARNING **: Failed to load shared library 'libcairo.so' referenced by the typelib: libcairo.so: cannot open shared object file: No such file or directory Device 0 (VID=04b3 and PID=310c) is UNKNOWN. Please report this VID/PID and the device model to the libmtp development team Device 0 (VID=04b3 and PID=310c) is UNKNOWN. Please report this VID/PID and the device model to the libmtp development team LIBMTP PANIC: Unable to find interface & endpoints of device Device 0 (VID=04b3 and PID=310c) is UNKNOWN. Please report this VID/PID and the device model to the libmtp development team Device 0 (VID=04b3 and PID=310c) is UNKNOWN. Please report this VID/PID and the device model to the libmtp development team Device 0 (VID=04b3 and PID=310c) is UNKNOWN. Please report this VID/PID and the device model to the libmtp development team Device 0 (VID=04b3 and PID=310c) is UNKNOWN. Please report this VID/PID and the device model to the libmtp development team LIBMTP PANIC: Unable to find interface & endpoints of device LIBMTP PANIC: Unable to find interface & endpoints of device LIBMTP PANIC: Unable to find interface & endpoints of device LIBMTP PANIC: Unable to find interface & endpoints of device
ok now rhythmbox-2.90.1-5.git20110316.fc15.x86_64 When started from terminal [floki@f15al ~]$ rhythmbox Gtk-Message: Failed to load module "pk-gtk-module" (rhythmbox:6537): Rhythmbox-WARNING **: Unable to start mDNS browsing: MDNS service is not running (rhythmbox:6537): libdmapsharing-WARNING **: Unable to initialize mDNS: Daemon not running (rhythmbox:6537): libdmapsharing-WARNING **: Unable to start music sharing server (IPv4) (rhythmbox:6537): libdmapsharing-WARNING **: Unable to notify network of media sharing: The avahi MDNS service is not running (rhythmbox:6537): libdmapsharing-WARNING **: Unable to start Remote lookup: MDNS service is not running ** (rhythmbox:6537): WARNING **: Failed to load shared library 'libcairo.so' referenced by the typelib: libcairo.so: cannot open shared object file: No such file or directory
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. 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 '15' 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 15 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