Its fresh Gentoo installation, i have installed it yesterday and KDE is even not starting up due to no Dbus session-bus found. DBus is of ocurse up and running, but don't forget its system bus, NOT session bus, and should have nothing to do. I was trying to discuss this issue on #kde-devel, from what i managed to learn it should be working, but it's NOT. What i can do? * I can start KDM and login * I can start failsafe session with xterm * I can start kde software, like kwrite, konqueror from xterm What i cant do? * I cannot launch whole KDE SC from KDM * I cannot launch whole KDE SC using startx command * I cannot launch whole KDE SC using startkde command from xterm Everytime i try to launch KDE it shows splash, then icons bagin to show up and when all icons showed it stops doing anything. Reproducible: Always Steps to Reproduce: 1. Launch KDE Actual Results: When i try to launch it from KDM i got this in /var/log/kdm.log: klauncher(2434) kdemain: no Dbus session-bus found. Check if you have started the DBUS server. kdeinit4: Communication error with launcher. Exiting! kdmgreet(2393) (K*TimeZone*): kSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server" When i try to launch it using startx i got this: startkde: Starting up... Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kbuildsycoca4 running... Agent registered Object::connect: No such signal QDBusAbstractInterface::DeviceAdded(QString) Object::connect: No such signal QDBusAbstractInterface::DeviceRemoved(QString) kded(5627): Communication problem with "kded" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "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." " NVIDIA: could not open the device file /dev/nvidiactl (Permission denied). NVIDIA: could not open the device file /dev/nvidiactl (Permission denied). OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTS 360M/PCI/SSE2 OpenGL version string: 2.1.2 NVIDIA 260.19.44 OpenGL shading language version string: Driver: NVIDIA Driver version: 260.19.44 GPU class: G80/G90 OpenGL version: 2.1.2 GLSL version: 0.0 X server version: 1.9.5 Linux kernel version: 2.6.38 Direct rendering: no Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes NVIDIA: could not open the device file /dev/nvidiactl (Permission denied). kwin(5659): Invalid framebuffer status: "GL_FRAMEBUFFER_UNSUPPORTED" kwin(5659): Failed to compile shader: " kwin(5659): Failed to compile shader: " QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.13' QDBusObjectPath: invalid path "" plasma-desktop(5676)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0) plasma-desktop(5676)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0) plasma-desktop(5676)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0) plasma-desktop(5676)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0) plasma-desktop(5676)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0) plasma-desktop(5676)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0) plasma-desktop(5676)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0) plasma-desktop(5676)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0) Object::connect: No such signal KWindowSystem::windowChanged(WId,unsigned long*) plasma-desktop(5676)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(-5, -3) plasma-desktop(5676)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(-5, -3) plasma-desktop(5676)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(-5, -3) plasma-desktop(5676)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0) link XMLID_34_ hasn't been detected! link XMLID_34_ hasn't been detected! link XMLID_36_ hasn't been detected! plasma-desktop(5676)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0) Object::connect: No such signal QDBusAbstractInterface::DeviceAdded(QString) Object::connect: No such signal QDBusAbstractInterface::DeviceRemoved(QString) Object::connect: No such signal QDBusAbstractInterface::DeviceAdded(QDBusObjectPath) Object::connect: No such signal QDBusAbstractInterface::DeviceRemoved(QDBusObjectPath) Object::connect: No such signal QDBusAbstractInterface::DeviceChanged(QDBusObjectPath) Object::connect: No such signal QDBusAbstractInterface::DeviceAdded(QString) Object::connect: No such signal QDBusAbstractInterface::DeviceRemoved(QString) X Error: BadValue (integer parameter out of range for operation) 2 Major opcode: 102 (X_ChangeKeyboardControl) Resource id: 0xffffffa0 kwin(5659)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "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." Object::connect: No such signal QDBusAbstractInterface::DeviceAdded(QDBusObjectPath) Object::connect: No such signal QDBusAbstractInterface::DeviceRemoved(QDBusObjectPath) Object::connect: No such signal QDBusAbstractInterface::DeviceChanged(QDBusObjectPath) QStringList Solid::Backends::UDisks::UDisksManager::allDevicesInternal() error: "org.freedesktop.DBus.Error.NoReply" Object::connect: No such signal QDBusAbstractInterface::DeviceAdded(QDBusObjectPath) Object::connect: No such signal QDBusAbstractInterface::DeviceRemoved(QDBusObjectPath) Object::connect: No such signal QDBusAbstractInterface::DeviceChanged(QDBusObjectPath) unnamed app(5669): Communication problem with "knotify" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "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." " plasma-desktop(5675): Communication problem with "plasma-desktop" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "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." " QStringList Solid::Backends::UDisks::UDisksManager::allDevicesInternal() error: "org.freedesktop.DBus.Error.NoReply" QStringList Solid::Backends::UDisks::UDisksManager::allDevicesInternal() error: "org.freedesktop.DBus.Error.NoReply" kcminit(5651): "Error launching kaccess. Either KLauncher is not running anymore, or it failed to start the application." Couldn't find synaptics properties. No synaptics driver loaded? kdeinit4: Shutting down running client. Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) KDE Daemon (kded) already running. Expected Results: KDE should start up.
Created attachment 271809 [details] IRC logs When i was on #kde-devel, i was following instructions which may help you understand and address the problem. It shows output of some commands:
@x11: Guys i suspect nvidia of this, specialy that access error, any suggestions?
Created attachment 271813 [details] lsmod
Created attachment 271815 [details] emerge -pv nvidia
Created attachment 271819 [details] glxinfo If anyone wonders the guy cant attach from cli so I just repost his pastebins for further usage. I am really clueless now so any suggestions?
Adding also freedesktop so maybe other DE guys know this issue on dbus too.
I have managed to launch KDE. Steps i have done: 1) /etc/init.d/dbus stop 2) logged in in KDM 3) KDM showed beautiful error regarding it cannot start consolekit due to lack of dbus and i confirmed that by clicking OK 4) KDE launched pretty fast w/o throwing any other error or warning
Wow, this is rather strange... I'm getting exactly the same errors with an OLD installation of 4.6.2 (installed when it got out). It worked fine until last Saturday (30.4); I closed the computer down for the night (It had been up for 3 days straight before that), and when I booted it up the next morning (1.5), I started getting the errors. I'm not using KDE desktop, but Fluxbox with lots of KDE applications. About the symptoms: Dolphin takes several minutes to fire up, and when started from the command line throws up several dbus-related errors: Object::connect: No such signal QDBusAbstractInterface::DeviceAdded(QDBusObjectPath) Object::connect: No such signal QDBusAbstractInterface::DeviceRemoved(QDBusObjectPath) QStringList Solid::Backends::UDisks::UDisksManager::allDevicesInternal() error: "org.freedesktop.DBus.Error.NoReply" It seems that the dbus>solid connection is broken; when dolphin finally starts, the hard drive entries in 'Places' are missing, also tooltips does not work, I get only the 'busy' cursor when hovering on top of icons. K3b does not see the cd-drive, either. I have tried recompiling everything dbus-related, downgraded dbus, libdbusmenu-qt, udev, removed the 'usual suspects' i.e. /var/tmp/kdecache* and $HOME/.kde4/cache-* socket-*tmp-*... No luck, KDE dbus stays broken... :(
My problem is a little bit different. I can start KDM, w/o any problems and then failsafe with xterm. When i already have it working i can launch any kde application w/o any problem (tried already kwrite & konqueror). But when i type 'startkde' in xterm i got animated splash & tons of dbus related errors - nothing more. What is more "funny" - while starting 'startkde' kwin was complaining about dbus. But when i tried to run kwin only - it started w/o any errors, and kde window decoration presented, so i could move xterm window. What is more, i even got compositing - xterm became semi-transparent while moving.
I had an old installation of KDE 4.6.2 and it stopped working after updates yesterday night. I was getting the same errors as Rafal Kupiec. I tried to downgrade dbus, udev, udisks and libdbusmenu-qt but no go. I even re-emerged kdelibs and consolekit related packages. Finally I decided to downgraded all packages of yesterday's update and it started working again. The downgraded packages are: =sys-libs/timezone-data-2011g =dev-libs/libevent-2.0.11 =app-shells/bash-4.2_p8-r1 =media-libs/libpng-1.4.7 =dev-lang/swig-2.0.4_pre12643 =app-portage/layman-1.4.2-r2 =dev-python/setuptools-0.6.16 =sys-apps/openrc-0.8.2-r1 =dev-vcs/git-1.7.5_rc3 =sys-apps/acl-2.2.51 =sys-apps/coreutils-8.12 =sys-fs/udev-168-r1 =dev-libs/libdbusmenu-qt-0.8.2 =app-text/poppler-0.16.5 =gnome-base/gconf-2.32.3 =sys-fs/udisks-1.0.2-r2 =net-libs/libproxy-0.4.6-r2 =net-libs/glib-networking-2.28.6.1 =net-libs/libsoup-2.34.1 Not sure what package/s did the trick. But its working now and can't experiment more.
I do not confirm that: 1) i downgraded them and no success so far 2) friend updated them and doesnt get kde corrupted
have you re-emerged kdelibs after downgrade? (In reply to comment #11) > I do not confirm that: > 1) i downgraded them and no success so far > 2) friend updated them and doesnt get kde corrupted
(In reply to comment #12) > have you re-emerged kdelibs after downgrade? > (In reply to comment #11) > > I do not confirm that: > > 1) i downgraded them and no success so far > > 2) friend updated them and doesnt get kde corrupted Yeah... nothing helps
Similar reports: [1] https://bbs.archlinux.org/viewtopic.php?pid=884872 [2] https://bbs.archlinux.de/viewtopic.php?id=18695 [3] http://forums.gentoo.org/viewtopic-t-854653-start-0.html [4] http://forum.kde.org/viewtopic.php?f=66&t=93180 [5] http://old.nabble.com/Re%3A-KDE4-doesn%27t-load.--No-DBUS-session-bus-found.-td30979882.html [5] http://www.opensubscriber.com/message/fink-beginners@lists.sourceforge.net/13489555.html [3] solved the problem by downgrading the NVidia drivers (!) "to the 260 version" [4] is marked as "solved": "It appears to be a crash in the Microblog applet, which I believe has already been fixed. See https://bugs.kde.org/show_bug.cgi?id=270327#c8 for a workaround. Note that the appropriate directory may be ~/.kde4/ instead."
Ook, everyone. We need to figure out the exact problem, with your help (my system works). After talking to dfaure on #kde-devel, we suspect that the dbus session bus is active at the start, but then crashes at some point. 1) Please make a backup of your /usr/bin/startkde, and then open the file as root in an editor. Add every few lines the following command: qdbus || echo "failed at $LINENO" Then try to log in. The output of the commands should be logged in .xsession-errors - this way we can narrow down where / when the session bus fails. 2) As a second step, once we have narrowed down the problem - if you can, please enable core dumps, see http://www.gentoo.org/proj/en/qa/backtraces.xml and check if anything dbus-like is dumped. If yes, please please please try to get a backtrace of the dumped process!
Well, I modified startkde as instructed and tried to log on to KDE desktop, but the resulting .xsession-errors did not contain any "failed at <somewhere>"-messages; are you sure it should be working? Lots of dbus-related errors, though... Should I still post it? (It's a very large file)
I have also modified startkde script - nothing, i repeat nothing ;) qdbus does not fail. Even when error from KDE shows, qdbus still shows dbus running: org.kde.plasma-desktop :1.77 org.freedesktop.DBus kdeinit4: Shutting down running client. Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) KDE Daemon (kded) already running. kded(3582): Communication problem with "kded" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "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." " :1.130 org.kde.klauncher :1.133 org.kde.kcminit-3611 :1.134 :1.53 org.kde.kded :1.59 org.kde.JobViewServer org.kde.kuiserver :1.62 org.kde.BlueDevil.Service org.kde.bluedevilfilereceiverhelper-3406 :1.63 :1.64 org.openobex :1.65 org.kde.kcminit org.kde.kcminit-3430 :1.72 org.kde.kglobalaccel :1.74 org.kde.knotify :1.76 org.kde.StatusNotifierHost-3449 org.kde.plasma-desktop org.freedesktop.DBus :1.130 org.kde.klauncher :1.133 org.kde.kcminit-3611 :1.135 :1.53 org.kde.kded :1.59 org.kde.JobViewServer org.kde.kuiserver :1.62 org.kde.BlueDevil.Service org.kde.bluedevilfilereceiverhelper-3406 :1.63 :1.64 org.openobex :1.65 org.kde.kcminit org.kde.kcminit-3430 :1.72 org.kde.kglobalaccel :1.74 org.kde.knotify :1.76 org.kde.StatusNotifierHost-3449 org.kde.plasma-desktop org.freedesktop.DBus I attach full log
Created attachment 271965 [details] modified startkde log modified startkde log
Looks like same problem. Somehow related to this: after loading, NetworkManager process eats 100% CPU. After loading splash, it shows a black screen. But if I want for ~5 min, it actually loads the KDE session with polkit-kde-agent KDE crash handler (with some strange and not informative backtrace), and many broken DBus-related things (battery applet can't access UPower dbus iface, NetworkManager can't access NM iface, Devices applet can't access udisks iface..). If I start, for example, /usr/libexec/upowerd manually, it shows an error: --- (upowerd:10506): UPower-DEBUG: Starting upowerd version 0.9.9 UPower-ERROR **: failed to get pokit authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/libexec/dbus-daemon-launch-helper received signal 9 aborting... --- Udisks shows same error. So as for me it actually looks like DBus/PolKit related error. Starting "polkitd" manually shows message "Connected to the system bus", but "qdbus --system" can't see its interface.
What i noticed.... I have romoved all settings from ~ and from /tmp and /var/tmp Even so i got this: /home/belliash/Settings/.kde4/share/config/startupconfig: line 3: qdbus_: command not found Something creates that file (i mean startupconfig) while kde is starting up and it wants to call non-existen file.
(In reply to comment #19) > Looks like same problem. > Somehow related to this: after loading, NetworkManager process eats 100% CPU. > > After loading splash, it shows a black screen. But if I want for ~5 min, it > actually loads the KDE session with polkit-kde-agent KDE crash handler (with > some strange and not informative backtrace), and many broken DBus-related > things (battery applet can't access UPower dbus iface, NetworkManager can't > access NM iface, Devices applet can't access udisks iface..). > > If I start, for example, /usr/libexec/upowerd manually, it shows an error: > --- > (upowerd:10506): UPower-DEBUG: Starting upowerd version 0.9.9 > > UPower-ERROR **: failed to get pokit authority: Error initializing authority: > Error calling StartServiceByName for org.freedesktop.PolicyKit1: > GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process > /usr/libexec/dbus-daemon-launch-helper received signal 9 > aborting... > --- > Udisks shows same error. So as for me it actually looks like DBus/PolKit > related error. > > Starting "polkitd" manually shows message "Connected to the system bus", but > "qdbus --system" can't see its interface. exactly... splash shows, icons animate, then it stucks on splash or black screen shows and KDE will load after about 5-10 minutes with something policykit crashed.
Something else, please check in /var/log/emerge.log when you last time updated * sys-auth/polkit and * sys-apps/dbus, and try to remember if this correlates somehow with the problem...
It certainly is some package from the list for me. As again to test I updated the listed packages and now cannot login to kde4. (In reply to comment #13) > (In reply to comment #12) > > have you re-emerged kdelibs after downgrade? > > (In reply to comment #11) > > > I do not confirm that: > > > 1) i downgraded them and no success so far > > > 2) friend updated them and doesnt get kde corrupted > > Yeah... nothing helps
Already done. polkit was updated to version 0.101-r1 from 0.101 on 30 April. It may be related. Since 0.101 ebuild was removed from tree, I can't see what changed. I tried building polkit without patches (there are some patches in ebuild) - but it didn't help. udisks also was updated. No more related things were updated, as I can see.
Ditto. -NetworkManager at 100% CPU -Polkit error on KDE login, black screen -Wait long enough the kde desktop does come up -Dolphin takes forever to load, does not show blockdevices -I have net based services set to load from a separate run-level started by NetworkManger dispatch, and those don't get loaded -Suspect it has to do with polkit update, but can't seem to find a way around it
Hmmm... maybe some package is causing this, but downgrading didnt help (at least here). I even tried rebuilding kdelibs, but still with no success so far.
Got the same problems here. I tried to get rid of polkit friday. I also cleaned my world file. So after a reboot it was really hard finding where the problem cold come from. I reinstalled everything, recompiled all the packages with policykit and consolekit USE flags. I then recomplied every kde packages then evey package using polkit or consolekit. For the sake of trying everything, I re-emerged my world with "-e" and finally did a full installation on another partition. For nothing. I now use xfce cause kde's taking too long to start. Here is what I see in my logs May 2 18:17:47 matmat console-kit-daemon[3398]: WARNING: polkit_authority_get: Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freedesktop.PolicyKit1 timed out May 3 07:25:51 matmat console-kit-daemon[3224]: WARNING: polkit_authority_get: Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached Kde take ages to launch. Then a little longer to launch the taskbar. I can't see messages in kmail. Every once in a while I get a drkonqi message complaining about polkit: polkit-kde-authentication-agent-1 PID xxxx signal: segmentation fault (11) It's get better in xfce, but the logout button takes a while to show the logout dialog, when it does. I get "access denied" from dbus for almost every system call. # dbus --system :1.11 Error: org.freedesktop.DBus.Error.AccessDenied Rejected send message, 1 matched rules; type="method_call", sender=":1.44" (uid=501 pid=4266 comm="qdbus --system :1.11 ") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply=0 destination=":1.11" (uid=501 pid=5501 comm="/usr/bin/pulseaudio --start ")) Finally here is what shows in dbus-minitor when I click the logout button in xfce: signal sender=org.freedesktop.DBus -> dest=(null destination) serial=115 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string ":1.153" string "" string ":1.153" method call sender=:1.153 -> dest=org.freedesktop.DBus serial=1 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=Hello method call sender=:1.153 -> dest=org.xfce.SessionManager serial=2 path=/org/xfce/SessionManager; interface=org.xfce.Session.Manager; member=Shutdown uint32 0 boolean true method return sender=:1.5 -> dest=:1.153 reply_serial=2 method call sender=:1.5 -> dest=org.xfce.Xfconf serial=258 path=/org/xfce/Xfconf; interface=org.xfce.Xfconf; member=GetProperty string "xfce4-session" string "/general/SaveOnExit" error sender=:1.1 -> dest=:1.5 error_name=org.xfce.Xfconf.Error.PropertyNotFound reply_serial=258 string "Property "/general/SaveOnExit" does not exist on channel "xfce4-session"" method call sender=:1.5 -> dest=org.xfce.Xfconf serial=259 path=/org/xfce/Xfconf; interface=org.xfce.Xfconf; member=GetProperty string "xfce4-session" string "/general/AutoSave" error sender=:1.1 -> dest=:1.5 error_name=org.xfce.Xfconf.Error.PropertyNotFound reply_serial=259 string "Property "/general/AutoSave" does not exist on channel "xfce4-session"" method call sender=:1.5 -> dest=org.xfce.Xfconf serial=260 path=/org/xfce/Xfconf; interface=org.xfce.Xfconf; member=GetProperty string "xfce4-session" string "/general/PromptOnLogout" error sender=:1.1 -> dest=:1.5 error_name=org.xfce.Xfconf.Error.PropertyNotFound reply_serial=260 string "Property "/general/PromptOnLogout" does not exist on channel "xfce4-session"" method call sender=:1.5 -> dest=org.xfce.Xfconf serial=261 path=/org/xfce/Xfconf; interface=org.xfce.Xfconf; member=GetProperty string "xfce4-session" string "/shutdown/ShowSuspend" error sender=:1.1 -> dest=:1.5 error_name=org.xfce.Xfconf.Error.PropertyNotFound reply_serial=261 string "Property "/shutdown/ShowSuspend" does not exist on channel "xfce4-session"" method call sender=:1.5 -> dest=org.xfce.Xfconf serial=262 path=/org/xfce/Xfconf; interface=org.xfce.Xfconf; member=GetProperty string "xfce4-session" string "/shutdown/ShowHibernate" error sender=:1.1 -> dest=:1.5 error_name=org.xfce.Xfconf.Error.PropertyNotFound reply_serial=262 string "Property "/shutdown/ShowHibernate" does not exist on channel "xfce4-session"" signal sender=org.freedesktop.DBus -> dest=(null destination) serial=116 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string ":1.153" string ":1.153" string " Also my "real name" doesn't show on ck-list-sessions Session2: unix-user = '501' realname = '(null)' seat = 'Seat1' session-type = '' active = TRUE x11-display = ':0' x11-display-device = '/dev/tty7' display-device = '' remote-host-name = '' is-local = TRUE on-since = '2011-05-03T06:58:21.805226Z' login-session-id = '193' Anything I could try to help locate the problem source?
Now I tried to downgrade as I did yesterday. But surprise I can't login to KDE again. It seems either the old ebuild is patched without changing version, or all versions of an ebuild are patched. Still could not figure out what package is causing this. Temp workaround for me. I removed dbus from default runtime. Now I can login. (In reply to comment #26) > Hmmm... maybe some package is causing this, but downgrading didnt help (at > least here). I even tried rebuilding kdelibs, but still with no success so far.
Developers: Try reverting these changes from dbus-1.4.8: http://cgit.freedesktop.org/dbus/dbus/commit/?id=4012b009557fe8796a8e5d343548821c70322dd3 Users: Try reverting to dbus-1.4.6: Note that plain downgrade won't show correct testing, and not even quitting KDE and trying startx again from console as you'd still have first old daemon running, then secondly possibly open dbus sessions (initialized by ConsoleKit from pam_ck_connector.so for example). So when reverting the commit, or downgrading to 1.4.6 you'll propably be better off doing full system reboot to ensure everything gets properly restarted Then if this works, it's propably same as: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623492 A KDE bug rather than dbus bug, might want to take a look at eg initialize_variables_crashfix.diff from the Debian package of kdebase-workspace for example (The various different output in this bug just looks like symptoms of a dbus session disappearing to me, thus all the output might be different...)
I tried dbus-1.4.6 earlier, it worked for a short time - almost (Dolphin tooltips were still missing), but something caused things to fall apart again, on next reboot I was back where I started, with broken dbus (i.e. with dbus-1.4.6)
Downgrading to dbus-1.4.6 didn't help at all. Of course, did full system reboot. Still same symptoms (all exact the same as in comment 25, btw). And something is broken in systray (some icons are duplicated; but it is dbus-related, because tray in KDE is hardly dbus-based). The main idea is that dbus doesn't work only for some part of applications. It is definitely strange.
Downgrading dbus from 1.4.8 to 1.4.6 haven't helped here. Done nothing after downgrading - just rebooted.
Next suggestion: please rebuild dev-libs/dbus-glib and then reboot and try again!
nothing...
Hi Maneesh, could you maybe try to "bisect" to figure out the exact problem? Means, update half the packages, check if it is still working. If yes, update again half of the remaining ones... if no, undo the update and update the other half... and so on until it is narrowed down to one package... Sorry for the complicated procedure, but right now we're still in the dark here... > =sys-libs/timezone-data-2011g > =dev-libs/libevent-2.0.11 > =app-shells/bash-4.2_p8-r1 > =media-libs/libpng-1.4.7 > =dev-lang/swig-2.0.4_pre12643 > =app-portage/layman-1.4.2-r2 > =dev-python/setuptools-0.6.16 > =sys-apps/openrc-0.8.2-r1 > =dev-vcs/git-1.7.5_rc3 > =sys-apps/acl-2.2.51 > =sys-apps/coreutils-8.12 > =sys-fs/udev-168-r1 > =dev-libs/libdbusmenu-qt-0.8.2 > =app-text/poppler-0.16.5 > =gnome-base/gconf-2.32.3 > =sys-fs/udisks-1.0.2-r2 > =net-libs/libproxy-0.4.6-r2 > =net-libs/glib-networking-2.28.6.1 > =net-libs/libsoup-2.34.1
> 1) Please make a backup of your /usr/bin/startkde, and then open the file as > root in an editor. Add every few lines the following command: > > qdbus || echo "failed at $LINENO" > > Then try to log in. The output of the commands should be logged in > .xsession-errors - this way we can narrow down where / when the session bus > fails. In the meantime nirbheek suggested that qdbus might be broken too. So what you could also try is do the same trick as above, but with the command (one line) gdbus introspect -e -d org.freedesktop.DBus -o /org/freedesktop/DBus || echo "failed at $LINENO" instead...
hi Andreas, I already have a downgraded system that stopped working now. If you see all my comments it will be clear(Comment 28). So now there is no way for me to figure out the exact problem. (In reply to comment #35) > Hi Maneesh, > > could you maybe try to "bisect" to figure out the exact problem? Means, update > half the packages, check if it is still working. If yes, update again half of > the remaining ones... if no, undo the update and update the other half... and > so on until it is narrowed down to one package... > > Sorry for the complicated procedure, but right now we're still in the dark > here... > > > =sys-libs/timezone-data-2011g > > =dev-libs/libevent-2.0.11 > > =app-shells/bash-4.2_p8-r1 > > =media-libs/libpng-1.4.7 > > =dev-lang/swig-2.0.4_pre12643 > > =app-portage/layman-1.4.2-r2 > > =dev-python/setuptools-0.6.16 > > =sys-apps/openrc-0.8.2-r1 > > =dev-vcs/git-1.7.5_rc3 > > =sys-apps/acl-2.2.51 > > =sys-apps/coreutils-8.12 > > =sys-fs/udev-168-r1 > > =dev-libs/libdbusmenu-qt-0.8.2 > > =app-text/poppler-0.16.5 > > =gnome-base/gconf-2.32.3 > > =sys-fs/udisks-1.0.2-r2 > > =net-libs/libproxy-0.4.6-r2 > > =net-libs/glib-networking-2.28.6.1 > > =net-libs/libsoup-2.34.1
I checked all mentioned packages in gentoo packages and no ebuild is changed. Before downgrade I did a lot of recompile of kdelibs, udev, dbus, consolekit related packages. But now No success so far.
With a freshly modified startkde as per comment 36 still no "failed at"-messages
I had the same issue(s) on three different machines (x86 and amd64). They were restored to normal as soon as I unmerged net-libs/glib-networking: emerge -C glib-networking This leaves my system(s) in an uncomplete state, as obviously glib-networking is required for net-libs/libsoup and related stuff, but at least KDE is working like before. I followed this track due to Gentoo Bug 365479 btw. Maybe it's related... Cheers, Ralph
(In reply to comment #40) > I had the same issue(s) on three different machines (x86 and amd64). > They were restored to normal as soon as I unmerged net-libs/glib-networking: > > emerge -C glib-networking > > This leaves my system(s) in an uncomplete state, as obviously glib-networking > is required for net-libs/libsoup and related stuff, but at least KDE is working > like before. > > I followed this track due to Gentoo Bug 365479 btw. > Maybe it's related... > > Cheers, > Ralph ? I dont have this package installed...
Hmmm... yes now I can see they changed the Old ebuild also for glib-networking. glib-networking-2.28.5.ebuild is changed on Tue May 3 15:47:37 2011 UTC. This might me be the reason that downgrading first time worked. (Comment 10) And didn't work the second time. (Comment 23 & Comment 28) I will try to emerge the old ebuild without change and see. (In reply to comment #40) > I had the same issue(s) on three different machines (x86 and amd64). > They were restored to normal as soon as I unmerged net-libs/glib-networking: > > emerge -C glib-networking > > This leaves my system(s) in an uncomplete state, as obviously glib-networking > is required for net-libs/libsoup and related stuff, but at least KDE is working > like before. > > I followed this track due to Gentoo Bug 365479 btw. > Maybe it's related... > > Cheers, > Ralph
But it is just impossible - the changes in ebuild were really minor (see http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-libs/glib-networking/glib-networking-2.28.6.1.ebuild?view=log&pathrev=MAIN and somewhere near it). Anyway, I'll try doing downgrade/remove and see what will happen.
Bingo! That's it. I removed glib-networking and all works just fine now! Except the fact that libsoup wants glib-networking; but living without libsoup (actually, only webkit-gtk wants it) is much simpler that without DBus+PolKit+KDE+etc. Thanks very much BTW, since the problem is solved only partially (we only figured out where is the problem exactly), I still can try anyhow help (backtraces, configs, etc). Just ask :)
Confirmed: removal of glib-networking fixes the problems on my system
I also confirm removing glib-networking solves the problem for me. Downgrading glib-networking doesn't.
Confirmed: removal of glib-networking fixes everything. I also downgraded libsoup and libsoup-gnome to 2.32.2, which version does not depend on glib-networking
Firstly i though its dbus-networking and i written that i dont have this installed - my bad. After removal os glib-networking KDE has begun to work, so... yeah this really helps.
Thanks guys, we finally have some clue that we can work with! :) @gnome: any idea why glib-networking could cause this???
Thanks Jouni for your tip. Now I understand why downgrade worked for me first time and not second and third time today. I kept these two ebuilds in my mask file: =net-libs/glib-networking-2.28.6.1 =net-libs/libsoup-2.34.1 First downgrade I did complete emerge world, depclean and revdep-rebuild. So depclean removed now not used glib-networking-2.28.6.1 for net-libs/libsoup-2.32.2. But I never did the same for second and third downgrade. I think Rafal also forgot to depclean after the downgrade.
Exactly.I have just downgraded the packages you have listed in one of your previous comments. You listed libsoup there. But unfortunately this have not removed glib-networking, because i have not done depclean. Everything becomes clear now...
Damn, I take it back... not everything is working as it should: Dolphin tooltips are still missing, only the 'busy' cursor is showing... and it worked just fine before this 'breakage' happened! Maybe I need to recompile something... or everything... :(
(In reply to comment #52) > Damn, I take it back... not everything is working as it should: Dolphin > tooltips are still missing, only the 'busy' cursor is showing... and it worked > just fine before this 'breakage' happened! Maybe I need to recompile > something... or everything... :( Hmmm... dolphin is working fine here on all three machines (x86 and amd64). I'd guess you're right about recompiling...
I havent noticed any dolphin-related issues so far.
Decreasing severity, since a problem with unrelated ~arch cannot block stabilization. In the worst case we'll have to introduce a blocker in the kdelibs ebuild.
Blocker introduced. You may have to downgrade libsoup to net-libs/libsoup-2.32.2 get rid of the dependency on net-libs/glib-networking.
*** Bug 361041 has been marked as a duplicate of this bug. ***
Okay, I recompiled all packages depending on dbus and most of the KDE... Dolphin seems to be working all right now :) Thanks for all Gentoo devs and fellow Gentoo users who worked hard to solve this very puzzling problem!
Well, the blocker might not be a good idea. For people using KDE it's a temporary workaround no doubt. But it effectively prevents my (rather minimalistic) gnome based netbook setup from beeing able to emerge. As I said it's gnome based and has no complete kde installed, but kdelibs are pulled by some installed apps and used to work flawlessly before (with 4.6.1 kdelibs installed). I vote for >=net-libs/libsoup-2.34.1, net-libs/libsoup-gnome-2.34.1 and >=net-libs/glib-networking-2.28.6.1 beeing masked until the root cause has been worked out and the real fix implemented. Gnome setups should work anyhow (still emerging, the netbook is slow), and KDE setups wont be affected.
# qlist glib-networking /usr/lib/gio/modules/libgiolibproxy.so /usr/lib/gio/modules/libgiognutls.so /usr/lib/gio/modules/libgiognomeproxy.so /usr/lib/debug/usr/lib/gio/modules/libgiolibproxy.so.debug /usr/lib/debug/usr/lib/gio/modules/libgiognutls.so.debug /usr/lib/debug/usr/lib/gio/modules/libgiognomeproxy.so.debug /usr/lib/debug/usr/libexec/glib-pacrunner.debug /usr/share/doc/glib-networking-2.28.6.1/NEWS.bz2 /usr/share/doc/glib-networking-2.28.6.1/README.bz2 /usr/share/dbus-1/services/org.gtk.GLib.PACRunner.service /usr/share/locale/fr/LC_MESSAGES/glib-networking.mo /usr/share/locale/ja/LC_MESSAGES/glib-networking.mo /usr/share/locale/zh_CN/LC_MESSAGES/glib-networking.mo /usr/libexec/glib-pacrunner I don't see how any of this stuff would impact KDE stuff. This package only provide proxy/ssl handling modules for gio.
Perhaps it's elf symbol clashes or a service conflict on dbus ?
I got the same bug before the block and fixed it by specifying -libproxy USE flag.
(In reply to comment #62) > I got the same bug before the block and fixed it by specifying -libproxy USE > flag. Interesting... Philippe, does that mean that you don't have libproxy in your system now? I've build all packages with optional libproxy support (neon and vlc) turned off, but libsoup-gnome has an unconditional depedency of libproxy.
(In reply to comment #62) > I got the same bug before the block and fixed it by specifying -libproxy USE > flag. Well, I also started browsing the sources, and was also suspecting libproxy. Right now it's just a wild guess, but libproxy registers a PAC/WPAD auto proxy detection service with dbus which seems suspicious (and cannot be canceled cleanly according to some source comments). What kind of proxy detection does KDE do on startup? Is there a conflict with two services draining the pool? Probably worth adding the gnome herd to the bug?
Well, it seems we are getting closer. I think Bug #365479 gives a clue here.
Indeed, we seem to have here a duplicate- I'll resolve this one since bug 365479 is by now probably the more concise description... Thanks to everyone who helped figuring this out. *** This bug has been marked as a duplicate of bug 365479 ***
