Branding packages should not affect this.

Please make sure the commands "kwrapper4" and "ksmserver" are in your path. They are both required for a successful KDE startup.

Also, it may pay to see if KSMServer is starting - but later crashing due to unknown reasons. Can you try reproducing under a new account to rule out older, possibly damaged sessions?

Could you explain, what you mean with

Please make sure the commands "kwrapper4" and "ksmserver" are in your path.

? Both files are available in /usr/bin, if that answers your question.

Starting with a different user, which was freshly installed, was not successful as well.

Yes, that answers the question. The path I was referring to was $PATH, which holds a list of directories to search for executables.

Can you try running various Qt/KDE commands such as "qdbus", "kde4-config --prefix" and "kreadconfig --file kdeglobals --group General --key widgetStyle" on the console to verify there is no problem with your base Qt/KDE installation?

I don't get any error when executing the kde commands. The last one (kreadconfig), respondes with no output, but seems to be executed anyway.

I think, the installation is not corrupt in general. In kdm I have the option to login in "secure mode" when choosing the desktop environment. Selecting this, I get a console window and nothing else. When executing ksmserver in the console window, I got the plasma desktop with the first login attempt. The second time, the background and the plasmoids were not shown, but the taskbar. I will try to find out a bit more about the information shown in the console window later on.

To sum up, ksmserver crashes when executed automatically during kde login, but runs (more or less) when executed from the command line.

Once Plasma has started, could you please verify that KSMServer is indeed still running?
Does it work if you try to run it using kwrapper4?

Code: Select all

kwrapper4 ksmserver

When starting ksmserver manually, the process is still active after plasma-desktop is started. The same, when executing "kwrapper4 ksmserver".

I have no idea, what the difference is between starting ksmserver manually (or via kwrapper4) or starting kde using the default workspace login in kdm.

Well, let's see the positive side of the problem: I am going to learn a lot about kde these days.

If you run "startkde" in the terminal window you get does it startup successfully or crash?

I think we are getting much closer. Executing startkde results in the wellknown error. The output on the command line when piping it to a log file

Code: Select all

startkde > log.txt 2>&1

is

Code: Select all

startkde: Starting up...
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kbuildsycoca4 running...
QObject::connect: Cannot connect (null)::deviceFound(Device*) to BlueDevilDaemon::deviceFound(Device*)
QObject::connect: Cannot connect QTimer::timeout() to (null)::stopDiscovery()
KCrash: Attempting to start /usr/bin/kded4 from kdeinit
kded(9761): Communication problem with  "kded" , it probably crashed.
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "

QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
KCrash: Application 'kded4' crashing...
KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit
kbuildsycoca4 running...
kdeinit4: (ksmserver /usr/bin/ksmserver) Pipe closed unexpectedlykdeinit4: Pipe closed unexpectedly: Die Ressource ist zur Zeit nicht verfügbar
KInit could not launch 'ksmserver'.
startkde: Could not start ksmserver. Check your installation.
kded(9765): Communication problem with  "kded" , it probably crashed.
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "


dbus-daemon itself is running. I will try to test some more things now...

bcooksley wrote:Please make sure the commands "kwrapper4" and "ksmserver" are in your path. They are both required for a successful KDE startup.

I am having the same exact problem with the KDE Daemon segfaulting upon login after upgrading to Mesa 8.0 with the intel driver on openSUSE 12.1 x86-64. I'm running KDE 4.8.0 with Qt 4.8.0.
The only way I can get KDE to start is by issuing the command you mentioned above (kwrapper4 ksmserver). It crashes in the same manner if I try to run startkde.
I can also get plasma-desktop to run from IceWM.

Can I get some help to find out what is wrong and solve this please?

BTW, I might not be able to respond right away as I work today. Thanks in advance for any help.

Welcome to the problem, echoes.
I don't think it is about the mesa package. I also have mesa installed (Core i7 on my machine), but release 7.10.2 and this was not updated the last weeks.

There are a lot of similar error message found by Google and also some hints, which helped in other scenarios.

Without success, I have tried to:
- uninstalled Network Manager (using ifup anyway)
- deleted /var/tmp/kdecache-<username>
- checked that kcm-tablet ist not installed (makes no sense to check, but desperation lets you do stupid things)

Ok, looks like something is causing kded4 to crash - and kdeinit4 is not able to get on it's feet.
Try running this:

Code: Select all

kbuildsycoca4 --noincremental
LD_BIND_NOW=true /opt/trunk-kde/kde/lib64/kde4/libexec/start_kdeinit_wrapper +kcminit_startup

See what happens after the second command. (The LD_BIND_NOW to +kcminit_startup is one line)

The result of the second command is

Code: Select all

kdeinit4: Shutting down running client.                                                                                                                                                                 
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)                                                                                                     
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
KDE Daemon (kded) already running.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kbuildsycoca4 running...
kbuildsycoca4(10152)/kdecore (services) KServicePrivate::init: The desktop entry file  "/usr/share/applications/YaST2/groups/apparmor.desktop"  has Type= "Application"  but no Exec line

kbuildsycoca4(10152) KBuildServiceFactory::createEntry: Invalid Service :  "/usr/share/applications/YaST2/groups/apparmor.desktop"
kbuildsycoca4(10152) KConfigGroup::readXdgListEntry: List entry x-scheme-handler/webcal in "/home/<user>/.local/share/applications/mimeapps.list" is not compliant with XDG standard (missing trailing semicolon).


btw: start_kdeinit_wrapper is located in /usr/lib64/kde4/libexec in my installation

The first command ends up with a lot of other messages, also with

"...not compliant with XDG standard..." and "xxx.desktop has Type= "Application" but no Exec line"

So you can verify that command started successfully?

If so, try running this, then the start_kdeinit_wrapper command - after ensuring all KDE processes are stopped.

Code: Select all

export KDE_FULL_SESSION=true
export KDE_SESSION_VERSION=4
export KDE_SESSION_UID=`id -ru`

bcooksley wrote:Ok, looks like something is causing kded4 to crash - and kdeinit4 is not able to get on it's feet.
Try running this:

Code: Select all

kbuildsycoca4 --noincremental
LD_BIND_NOW=true /opt/trunk-kde/kde/lib64/kde4/libexec/start_kdeinit_wrapper +kcminit_startup

See what happens after the second command. (The LD_BIND_NOW to +kcminit_startup is one line)

For me, this is the output of that command:

LD_BIND_NOW=true /usr/lib64/kde4/libexec/start_kdeinit_wrapper + kcminit_startup
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kbuildsycoca4 running...
Could not find '' executable

You appear to have an extra - unneeded - space between + and kcminit_startup.