Can't log into KDE, kdeinit4 uses huge amounts of CPU and memory

Eschatokyrios · 2012-08-12 22:11:59

I start KDE (4.9) as a daemon using /etc/rc.d/kdm start, and the login manager starts up just fine in vt7. When I log in, the normal default KDE progress splash screen comes up, and eventually goes to a black screen with only the mouse cursor. Meanwhile, the kdeinit4: plasma-desktop [kdeinit] process starts using 90%+ CPU and slowly uses more and more memory. If I let it run the process would eventually use all of physical RAM and start using all of swap as well, so I kill it before then. After that, my memory and cpu usage immediately shoots down and a few seconds later I hear the kde default startup chime and a bunch of other kde-related processes start, but in vt7 KDE itself is still stuck at a black screen with just the mouse cursor.

My .xsession-errors is at http://codepad.org/WxrCOFIf

Last edited by Eschatokyrios (2012-08-12 22:14:33)

ewaller · 2012-08-12 23:02:12

I suggest that you isolate it to either your KDE session or KDM. Try not starting KDM, and then stating a KDE session straight from a console with startkde when logged in as a user.

Eschatokyrios · 2012-08-12 23:11:10

Ah, hm, starting KDE from .xinitrc works fine, kdeinit4 runs and uses a bit of cpu for a while and then the rest of the startup process continues.

Neros · 2012-09-12 00:19:23

Hello,

I have exactly the same problem and his solution (with .xinitrc) don't solve it. It's a fresh install.

What can I do?

Thank you

dn_nb · 2012-09-12 00:49:11

I just did a fresh install with kde today, and it is working fine, I am using systemd to launch it though. Is dbus set in your rc.conf?

Neros · 2012-09-12 00:51:12

Yes, dbus is set.

dn_nb · 2012-09-12 01:11:22

I ask because the .xsession-errors the OP posted is going crazy with dbus errors. I would start my troubleshooting by makeing sure that it is running with either rc.d list or systemctl list-units. Maybe try starting kdm with systemctl start kdm to see what happens.

Neros · 2012-09-12 01:23:20

You are right, it seems to be a dbus issue.

When I try to start kdm with systemctl, I have : Failed to get D-Bus connection: No connection to service manager.
But dbus is set as a deamon in /etc/rc.conf and it is started .... So I don't understand. And I have the same dbus errors as OP.

dn_nb · 2012-09-12 01:40:53

https://bugs.kde.org/show_bug.cgi?id=297020

This seems to be a bug with kdm and nepomuk.

Neros · 2012-09-12 01:57:34

Ok, but I don't see a solution... So I will try to fully reinstall Arch tomorrow...

Arch Linux

#1 2012-08-12 22:11:59

Can't log into KDE, kdeinit4 uses huge amounts of CPU and memory

#2 2012-08-12 23:02:12

Re: Can't log into KDE, kdeinit4 uses huge amounts of CPU and memory

#3 2012-08-12 23:11:10

Re: Can't log into KDE, kdeinit4 uses huge amounts of CPU and memory

#4 2012-09-12 00:19:23

Re: Can't log into KDE, kdeinit4 uses huge amounts of CPU and memory

#5 2012-09-12 00:49:11

Re: Can't log into KDE, kdeinit4 uses huge amounts of CPU and memory

#6 2012-09-12 00:51:12

Re: Can't log into KDE, kdeinit4 uses huge amounts of CPU and memory

#7 2012-09-12 01:11:22

Re: Can't log into KDE, kdeinit4 uses huge amounts of CPU and memory

#8 2012-09-12 01:23:20

Re: Can't log into KDE, kdeinit4 uses huge amounts of CPU and memory

#9 2012-09-12 01:40:53

Re: Can't log into KDE, kdeinit4 uses huge amounts of CPU and memory

#10 2012-09-12 01:57:34

Re: Can't log into KDE, kdeinit4 uses huge amounts of CPU and memory

Board footer