Registered Member
|
This happens sometimes. But right now I inserted a cd into my drive, and then I started k3b. k3b would not load, and then kde was acting weird. So I reboot, and kdm would not finish loading to the desktop. I tried again but with failsafe plasma desktop, and it logged in. But plasma-desktop freezes after a few seconds.
Some test results: old account with plasma-desktop normal: plasma-desktop freezes a few seconds after logging in old account with plasma-desktop failsafe: same as above brand new account with normal plasma-desktop: plasma-desktop freezes a few seconds after logging in brand new account with failsafe plasma-desktop: plasma-desktop does not freeze upon login, but if i start dolphin its just an empty gray window not loading up (but I could browse locally with konqueror). Then after a few minutes, plasma-desktop freezes. xsessions-error from new account: http://pastebin.com/Qb02MaL9 using KDE 4.8.4 edit: I had fixed it just by reinstalling dolphin. So now today, a new day, I wonder if its k3b thats causing a lockup with dolphin/dbus/etc... So I start k3b, and it gets stuck "creating gui" I think. And then starting dolphin leaves me with a gray screen. This time reinstalling dolphin didn't work, but both dolphin and kdelibs fixed it. |
Administrator
|
Are you using plasmoids that connect to the network? Also, do you have stuff like Nepomuk active?
"Violence is the last refuge of the incompetent."
Plasma FAQ maintainer - Plasma programming with Python |
Registered Member
|
The new account and my main account both had no widgets. Nepomuk is active by default I believe, so the new account would have it on. Its disabled on my main account. |
Administrator
|
I don't see anything suspicious in the xsession errors file. Can you try monitoring the CPU / disk I/O when freezes occur?
"Violence is the last refuge of the incompetent."
Plasma FAQ maintainer - Plasma programming with Python |
Registered Member
|
It randomly froze up right now, and restarting x and logging in doesn't work.
I logged in with razor-qt (with kwin) instead. And trying to start plasma-desktop inside it doesn't work. terminal launching plasma-desktop: http://pastebin.com/grkXeA5j When logging in gets stuck, nothing is really showing up in cpu or disk usage. Like 1% for polkit and sometimes disk writes for consolekit |
Administrator
|
Does moving the Plasma Desktop configuration files temporarily out of the way solve the issue? If so, we can investigate configuration file corruption...
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
I had created a new account with an empty home directory just to make sure this wasn't the case. But I haven't had any problems so far with KDE 4.9, so I hope it stays this way |
Registered Member
|
plasma-desktop just froze. So I killed it, tried to restart it but it doesn't show up I moved all the plasma files in /share/apps and share/config, but nothing. rebooted and its just frozen at the bottom this is both plasma-desktop and plasma-panel freezing edit: after reading https://bugs.kde.org/show_bug.cgi?id=287002 I believe nfs is the issue. removing it from fstab now everything works fine |
Administrator
|
Good to see you found the problem.
The cause is that network mounts (whether NFS, Samba, or otherwise) which go down will cause the LInux kernel to block any application which tries to access the mounted paths. Unfortunately Plasma Desktop monitors and watches (through Solid) all mounted file systems - which causes this issue I believe.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]