I recently experienced some prolems with KDE that started from my attempts to improve the visual quality of the fonts and their rendering. Although I succeeded in improving the overall visual experience this came at the cost of having difficulties in starting KDE. I finally was able to login by fooling startkde by omitting the part that deals with problem checking. So I was able to login but I was not able to logout, either by right-clickin on the desktop and selecting logout, or by using
qdbus org.kde.ksmserver /KSMServer logout 0 0 0
Furthermore, nothing is appended to ~/.xsession-errors.
I’m puzzled, as I re-installed the whole KDE Base and Desktop Environments and X Windows Systems and renamed ~./kde4.
Can anyone shed any light please?
In case it helps, here’s the part of /var/log/messages that is relevant to the KDE session
Jun 15 11:00:25 pascaLinux systemd-logind[902]: New session 9 of user pascal.
Jun 15 11:00:25 pascaLinux systemd-logind[902]: Linked /tmp/.X11-unix/X0 to /run/user/pascal/X11-display.
Jun 15 11:00:26 pascaLinux checkproc: checkproc: can not get session id for process 1962!
Jun 15 11:00:27 pascaLinux kernel: 2915.395751] ksmserver[3089]: segfault at 20370 ip 00020370 sp bfb08cac error 14 in kdeinit4[8048000+b000]
Jun 15 11:00:27 pascaLinux kernel: 2915.424565] kded4[3083]: segfault at 20370 ip 00020370 sp bfb07bfc error 14 in kdeinit4[8048000+b000]
Jun 15 11:00:33 pascaLinux systemd-logind[902]: Removed session 9.
First we have to find out whether your attempts caused damage to the system or to your homedir. Create a new user, login as that user and see if the problem exists for that new user. If it does, it’s a system problem, if it doesn’t, we have to find out what makes KDE segfault.
Another thing you could try, is finding out if the issue is systemd related. To check this, hit F5 in the GRUB boot menu, and choose the “System V” option, then boot, login and report what happens.
Another thing you could try, is finding out if the issue is systemd related. To check this, hit F5 in the GRUB boot menu, and choose the “System V” option, then boot, login and report what happens.
I have a dual boot system, Fedora being the other one, and I used Fedora’s GRUB2. F5 does not have any effect and I do no see any option for booting System V.
Since I had nothing better to do I went to repositories/KDE:/Distro:/Factory/openSUSE_12.1 and performed an upgrade to KDE 4.8.4. I guess I was lucky but not much because the behavior the system improved (I can sort of logout and the screen artifacts are almost gone). What’s interesting is that I still get the exact same lines in /var/log/messages as before, indicating that this not a KDE problem per se.
Bug or not, I got rid of it by removing all updates since openSUSE 12.1, then adding them carefully back and finally I got a clean system. BTW, I downgraded to KDE 4.7.2 since KDE 4.8.4 is not bug-free yet.
I’m just sorry I wasn’t able to pinpoint what triggered the problem. Maybe it is indeed some rare bug.
On 2012-06-15 14:06, pligdas wrote:
>
> Knurpht;2469447 Wrote:
>> Another thing you could try, is finding out if the issue is systemd
>> related. To check this, hit F5 in the GRUB boot menu, and choose the
>> “System V” option, then boot, login and report what happens.
> I have a dual boot system, Fedora being the other one, and I used
> Fedora’s GRUB2. F5 does not have any effect and I do no see any option
> for booting System V.