GNOME Bugzilla – Bug 681195
Rhythmbox long delay to start
Last modified: 2018-05-24 17:38:11 UTC
Originally reported at https://bugs.launchpad.net/hundredpapercuts/+bug/1029267 On some systems, Rhythmbox can take a very long time (I measured 26 seconds every time) to start. When run through console, I can also see warnings about mDNS not being available. It turns out that when the "DAAP Music Sharing" plugin is disabled in Rhythmbox settings, both the warnings and the long delay go away. This Ubuntu forums thread talks about the same problem: http://ubuntuforums.org/showthread.php?t=1947738 An ordinary user might be puzzled as to why nothing apparently happens when he tries to play some random MP3. Some possible solutions: - Fix the long delay with the plugin - Disable the DAAP plugin by default - Give the user some feedback that Rhythmbox is starting and what is causing the delay
Is this still a problem with recent versions of libdmapsharing, avahi, and libdmapsharing? I just performed a test after disabling mDNS with: sudo systemctl disable avahi-daemon.service and: sudo service avahi-daemon stop Rhythmbox still started as quickly as usual, even though it printed: [...] (rhythmbox:7878): Rhythmbox-WARNING **: Unable to start mDNS browsing: MDNS service is not running (rhythmbox:7878): libdmapsharing-WARNING **: Unable to initialize mDNS: Daemon not running [...]
*** Bug 683194 has been marked as a duplicate of this bug. ***
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/rhythmbox/issues/1206.