Bug 171533 - KDE4 logon failure: 'startkde: Could not start D-Bus. Check your installation.'
Summary: KDE4 logon failure: 'startkde: Could not start D-Bus. Check your installation.'
Status: RESOLVED WORKSFORME
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-23 16:37 UTC by mcas
Modified: 2008-12-07 22:05 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mcas 2008-09-23 16:37:18 UTC
Version:            (using KDE 4.1.1)
OS:                Linux
Installed from:    Ubuntu Packages

This bug was reported on the ubuntu bug tracker. For further information please look here: https://bugs.edge.launchpad.net/ubuntu/+source/kdebase/+bug/187918

I installed the package, kde4-core from the repo. Everything seemed to have installed fine, however, when I choose 'KDE4' from the sessions menu in GDM, it begins to logon (shows splash /w hard drive icon) then an error message presents itself with the title-mentioned error.

Here is the output of qdbus (if it helps):

:1.0
:1.1
 org.gnome.GkbdConfigRegistry
 org.gnome.SettingsDaemon
:1.10
 org.freedesktop.Tracker
:1.11
:1.12
 org.freedesktop.Notifications
:1.14
 org.xchat.service
:1.2
:1.21
:1.3
 org.gnome.GnomeVFS.Daemon
:1.4
:1.5
:1.6
 org.gnome.ScreenSaver
:1.7
 org.freedesktop.PowerManagement
:1.8
:1.9
org.freedesktop.DBus
Comment 1 FiNeX 2008-12-07 21:45:39 UTC
I've just tried intrepid ibex (ubuntu) with kde 4.2 beta from neon repositories. It starts correctly. Could the bug has been fixed?
Comment 2 Jonathan Thomas 2008-12-07 22:05:33 UTC
Neon isn't really a good testing bed, because of the way it detaches itself from the normal software stack. (Which causes a good number of bugs itself)
But generally speaking this isn't really reproducible on any KDE installation anymore, and it was probably some malconfiguration or permissions problem or distro-specific issue in the first place. For now I would just set this as worksforme