Sie sind hier

KDE - Login Problems with kdm on Unstable

Some days ago I upgraded my Sid system and when I restarted my X session the other day, I wasn't able to successfully login to KDE via kdm anymore. I'm getting some errors in ~/.xsession-errors: 

kdeinit4: preparing to launch /usr/bin/knotify4
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)knotify(16474) KNotify::event: 1  ref= 0
QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance()kdeinit4: preparing to launch /usr/bin/plasma-desktop
kded4: Fatal IO error: client killedkdeinit4: Fatal IO error: client killed
kdeinit4: sending SIGHUP to children.
klauncher: Exiting on signal 1

At the user/password prompt of kdm I can login, the KDE splash screen appears and then, suddenly, the connection fails and I'm back at the kdm login again.

I tried to look for already existing bug reports, but KDE is quite large and with many programs. Are there any pointers for a bug report or even a solution/fix for the problem, dear LazyWeb?

UPDATE 21:51:
Sune suggests in the comments that it might be a Xorg problem. I've attached a xorg.txt logfile to this post. As you can see, there's a backtrace because of a sig11 error. Funny enough, when I connect via remote X from my OSX I can login into KDE, although there are visual errors. Xorg is working fine on the local server with Gnome, though. So, for me it seems related to either KDE or maybe Compiz.

UPDATE 2011-03-30:
Problem solved! LL hinted in the comments to reinstall the Nvidia driver and now it works again! Thanks! :-)

Symbol für unformatierten Text xorg.txt18.14 KB


I noticed a similar symptom when my /home FS was full.
And kde might try to generate some big files on login.

Hmmm, there are 23 GB free on /home. So I think that's not the problem in my case... ;-)

looks a bit like X is crashing. what does the xorg log file say ?


Yes, there seems a problem with local X server when using KDE, while it works with Gnome. See the attached xorg.txt.

I think you use a plasmoid that uses plasma-scriptengine-python, unfortunatelly this package is broken for a while. Try to move ~/.kde/share/config/plasma* files away.

reportbug is how you report bugs in Debian.

(BTW, captchas are a PITA WRT accessibility.)

Well, I prefer reportbug-ng usually. But first I would have to know which package is broken, before I report a bug. Using meta package kde to file a bug against seems not very clever to me. Especially when compiz is failing. So, I would like to identify the problem first and report a bug then.

And yes, I would like to turn off Captchas in my blog as well, but having lots and lots of spam is the bigger PITA.

Hi there,

I had a similar problem. For me plasma was crashing all the time.
Downgrading all packages named python-qt4 and python-qt4-*to version 4.8.3-1 solved it for me.
Bug report:

Not sure if that's your problem, too...

Hope that helps.


You are using the nvidia proprietary driver (as I can see in the log).
Please uninstall and reinstall it for the libGL links to be correct otherwise KDE 4 will crash because its trying to load desktop effects with a wrong libGL version.
So if you have manually installed the nvidia driver(assuming you have the install run file still) run:
./ --uninstall
and then after stopping kdm (sudo /etc/init.d/kdm stop)
./ .

Thanks for the hint! I tried nouveau lately but it didn't work as expected so I went back to proprietary nvidia package. It seems that something went not as planned when switching back to Nvidia. Uninstalling and reinstalling solved the problem. Thanks!

Had a similar issue in Arch Linux, where KDM would segfault when trying to enable acceleration. Turned out it was an issue with the xf86-video-ati driver.

I was able to work around it by launching KDE in safe mode until the driver was fixed.


Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer