On Monday 18 of May 2015 20:02:34 Cristian Rodríguez wrote:
On Mon, May 18, 2015 at 2:50 PM, Tom Wekell <Tom@northstarglove.com> wrote:
Hi all- Am I the only one? I have this problem on two machines.
After the Saturday zypper dup, I get a login box but the desktop fails to start. The first notification is krunner closed unexpectedly executable: krunner PID Signal: Aborted (6)
This is followed in short order by 3 repeats of: We are sorry Plasma closed unexpectedly. Executable: plasmashell PID Signal: Aborted.
I am left with the wallpaper and no menus, no keystrokes save <Ctrl><Esc> to see processes.
I set aside my /kde4 directory.--no change I created a new user. -- no change
How do I troubleshoot this problem?
Sounds familiar.. I faced pretty much the same issues (i.e everything crashing, does not matter what KDE component) after a great deal of pain I found that the buggy component is kscreen5.. in current tumbleweed it can be uninstalled, in the frameworks repository it was made mandatory, therefore I can no longer update :-|
Having: [Module-kscreen] autoload=false in either $XDG_CONFIG_DIRS/kded5rc or $XDG_CONFIG_HOME/kded5rc should prevent kscreen from doing anything (i.e. it's kded module won't load) Cheers, Hrvoje
I did not debug it further, as I do not have even an idea where to start.. the crashes start in the QT library itself..but when that does not happen.. something else bites the dust, even the X server ends being terminated for some reason.