Bug 448015
Summary: | Rhythmbox D-Bus activation hangs | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kamil Pawlowski <kamilpe> |
Component: | rhythmbox | Assignee: | Bastien Nocera <bnocera> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 9 | CC: | peter |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-03-26 06:06:09 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Kamil Pawlowski
2008-05-22 21:48:38 UTC
Is this with the plugin method set to "Command" or "D-Bus activation"? (Right click the applet, select the "Rhythmbox" plugin, and click the "Configure..." button.) Ah, I think I've narrowed it down some. I created a new user to test this with, and (from what I could tell) with an empty library, Rhythmbox seems to never show its main window until you click the "Play" icon. After adding some music to it and re-logging in, it takes a few seconds but does properly display itself. With the setting set to "Command" activation, the RB window shows nearly instantly after clicking applet. I check this and result is: dbus activation is buggy, but command work [Re-assigning to the Rhythmbox component, and re-wording summary a bit.] Okay, using rhythmbox-client to start RB also causes this problem (hangs while loading, then properly shows the window after a few minutes). At first glance this seems to be a D-Bus issue, since just running rhythmbox on its own (e.g., "rhythmbox &" in a terminal) loads it properly. With trying to use the client program to open Rhythmbox, the following warning is printed to the terminal: (rhythmbox-client:3565): Rhythmbox-WARNING **: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. If rhythmbox is already running, this error is not shown. This is with rhythmbox-(none):0.11.5-9.fc9. I'm sorry, but how exactly am I supposed to reproduce this? Staring rhythmbox from gnome-applet-music when dbus activation is on, but problem was solved on newest fedora release. Bastien: No reproduction possible, here. This is no longer an issue on updated Fedora 9 or 10 versions; and from my brief testing in Rawhide, it is also not affected there. :) [Therefor, closing as CURRENTRELEASE.] |