Arch Linux

ArthurTaborda

Member

Registered: 2014-11-13

Posts: 2

KDE fails to start after logout

Hi

This sometimes happen after I turn the computer on, but everytime after I do a logout, I can't login again in KDE. With LXQT I can login normally.

This is the .xsession-errors output:

startkde: Starting up...
kdeinit4: Shutting down running client.
klauncher(1210) kdemain: Waiting for already running klauncher to exit. 
klauncher(1210) kdemain: Waiting for already running klauncher to exit. 
klauncher(1210) kdemain: Another instance of klauncher is already running! 
kdeinit4: Communication error with launcher. Exiting!
kdeinit4_wrapper: Warning: connect(/home/arthur/.kde4/socket-arthur-inspiron/kdeinit4__0) failed: : Connection refused
ksmserver(1212): Couldn't start kglobalaccel from kglobalaccel.desktop:  "KDEInit could not launch '/usr/bin/kglobalaccel'" 

QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kwin(1216): Couldn't start kglobalaccel from kglobalaccel.desktop:  "KDEInit could not launch '/usr/bin/kglobalaccel'" 

QCoreApplication::sendPostedEvents: Cannot send posted events for objects in another thread
QCoreApplication::sendPostedEvents: Cannot send posted events for objects in another thread
QCoreApplication::sendPostedEvents: Cannot send posted events for objects in another thread
QCoreApplication::sendPostedEvents: Cannot send posted events for objects in another thread
ksmserver(1212) KSMServer::autoStart0Done: kcminit not running? If we are running with mobile profile or in another platform other than X11 this is normal. 
ksmserver(1212): Couldn't start knotify from knotify4.desktop:  "KDEInit could not launch '/usr/bin/knotify4'" 

Thanks for the help.

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 15,558

Re: KDE fails to start after logout

Are you using a display manager, and if so which one ?

please post the content of your ~/.xinitrc & ~/.xsession files.

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky