Summary: | media-sound/rhythmbox-0.12.5-r2 fails to start for ordinary users | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Juergen Rose <rose> |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | VERIFIED NEEDINFO | ||
Severity: | normal | CC: | gstreamer |
Priority: | High | ||
Version: | 2008.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Juergen Rose
2009-11-09 21:31:53 UTC
emerge -pv rhythmbox gvfs udev dbus please After the last 'emerge --sync; emerge -uvDN world', I could again start rhythmbox as ordinary user rose, but I got a lot of warnings: root@condor:/home/rose/(20)# rhythmbox (rhythmbox:12554): Rhythmbox-WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported (rhythmbox:12554): Rhythmbox-WARNING **: couldn't connect to session bus: 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. (rhythmbox:12554): Rhythmbox-WARNING **: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: 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.) ... (rhythmbox:13549): Rhythmbox-WARNING **: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: 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.) (rhythmbox:13549): GConf-WARNING **: Directory `/apps/rhythmbox' was not being monitored by GConfClient 0x19e0580 (rhythmbox:13549): Rhythmbox-WARNING **: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: 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.) The result of 'emerge -pv rhythmbox gvfs udev dbus' is: root@condor:/home/rose/Tarantel_hw_configuration(25)# emerge -pv rhythmbox gvfs udev dbus These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] sys-apps/dbus-1.3.0-r1 USE="X doc -debug (-selinux) -test" 0 kB [ebuild R ] media-sound/rhythmbox-0.12.5-r2 USE="brasero cdr doc gnome-keyring hal ipod libnotify lirc mtp musicbrainz nsplugin python -daap -debug -test -udev" 0 kB [ebuild R ] sys-fs/udev-146-r1 USE="devfs-compat extras (-selinux)" 0 kB [ebuild R ] gnome-base/gvfs-1.4.1 USE="bash-completion bluetooth cdda doc fuse gnome gnome-keyring gphoto2 hal samba udev -archive -avahi -gdu" 0 kB Total: 4 packages (4 reinstalls), Size of downloads: 0 kB There must be something wrong in either how you start your X session or how is your system setup. Those messages basically say you have no session dbus, no gconf and no gnome-session running. Please tell us how your start your X session. Do you have a session dbus started (ps aux |egrep "dbus.*session") ? I start X via gdm. But at the affected computer, I login very seldom, maybe I am logged in for more than to weeks. I.e., maybe I had no fresh login after the gnome upgrade. if you upgraded to a new major version of gnome, it will most likely cause problems if you do not restart your session. Did you restart your system since then and if so how are things going now ? I had this same error occur in gxine. A gentoo forum post claims that it is related to gvfs protocol changes, and suggests killing gvfs processes (on my workstation, it was "gvfsd" and "gvfs-hal-volume-monitor"). This worked for me. It also further justifies Gilles suggestion to restart the session; doing so would certainly restart any gvfs-related daemons. The forum post: http://forums.gentoo.org/viewtopic-t-801148-start-0.html Due to lack of updated information in the last 2 weeks, there is no way we can further help you solve this problem. Thanks for reporting anyway. |