Plasma crashed

After transferring some /home/user files (no config files) from a USB HD to my desktop box I was surprised that on the next bootup I was greeted by a plasma notice telling me “We are sorry, Plasma closed unexpectedly.” I checked my home directory and ,xsession-errors confirmed it.

Where to I start a solution or do I have to remove Plasma and re-install?

Thanks in advance.

I backed up and deleted my .kde4 directory then restarted . No change.

Disk full, maybe?
What does “df -h” say?

You should still be able to run applications via the Alt+F2 krunner dialog. Or try to select a different desktop session on the login screen, IceWM should be installed by default.

Also it would maybe be helpful to see the stack backtrace, the crash dialog should provide it.

And can you be more specific what files you copied, please?

I checked my home directory and ,xsession-errors confirmed it.

In which way does it confirm it?
Or more precisely what messages does it contain that confirmed it?

Where to I start a solution or do I have to remove Plasma and re-install?

A reinstall likely won’t help, especially if you only copied user files.

If this is a Leap 42.1 system, you are using Plasma5.
And this stores its configuration in the standard XDG directories, ~/.config in particular.
Deleting .kde4 won’t have any effect on Plasma5, except that it would free up space (so I suppose we can rule out that the disk is full…).

PS: you could also try to run plasmashell in a konsole or xterm (maybe inside IceWM) and see what output you get.
Might provide a clue…

Answers in the same order.

Filesystem      Size  Used Avail Use% Mounted on
devtmpfs        930M     0  930M   0% /dev
tmpfs           937M  140K  937M   1% /dev/shm
tmpfs           937M  2.0M  935M   1% /run
tmpfs           937M     0  937M   0% /sys/fs/cgroup
/dev/sda2        45G   11G   32G  25% /
/dev/sda5       345G  103G  225G  32% /home/ion/DATA

So that’s not a problem.

Could not find IceWM.

Backtrace…

Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe90c4997c0 (LWP 1397))]

Thread 7 (Thread 0x7fe853501700 (LWP 1411)):
#0  0x00007ffdc6387b26 in clock_gettime ()
#1  0x00007fe9059a7c7d in clock_gettime () from /lib64/libc.so.6
#2  0x00007fe90613e7d6 in ?? () from /usr/lib64/libQt5Core.so.5
#3  0x00007fe9062be3b9 in QTimerInfoList::updateCurrentTime() () from /usr/lib64/libQt5Core.so.5
#4  0x00007fe9062be945 in QTimerInfoList::timerWait(timespec&) () from /usr/lib64/libQt5Core.so.5
#5  0x00007fe9062bfb5e in ?? () from /usr/lib64/libQt5Core.so.5
#6  0x00007fe90206f4ad in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0
#7  0x00007fe90206fd80 in ?? () from /usr/lib64/libglib-2.0.so.0
#8  0x00007fe90206ff7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#9  0x00007fe9062bfd8b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#10 0x00007fe906266d53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#11 0x00007fe90608861a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#12 0x00007fe909f38282 in ?? () from /usr/lib64/libQt5Quick.so.5
#13 0x00007fe90608d32f in ?? () from /usr/lib64/libQt5Core.so.5
#14 0x00007fe9014b6754 in ?? () from /usr/X11R6/lib64/libGL.so.1
#15 0x00007fe90519c0a4 in start_thread () from /lib64/libpthread.so.0
#16 0x00007fe90599b02d in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7fe8da3fa700 (LWP 1410)):
#0  0x00007fe9051a003f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007fe90bb6b86b in ?? () from /usr/lib64/libQt5Script.so.5
#2  0x00007fe90bb6b899 in ?? () from /usr/lib64/libQt5Script.so.5
#3  0x00007fe9014b6754 in ?? () from /usr/X11R6/lib64/libGL.so.1
#4  0x00007fe90519c0a4 in start_thread () from /lib64/libpthread.so.0
#5  0x00007fe90599b02d in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7fe8dbc89700 (LWP 1409)):
#0  0x00007ffdc6387b26 in clock_gettime ()
#1  0x00007fe9059a7c7d in clock_gettime () from /lib64/libc.so.6
#2  0x00007fe90613e7d6 in ?? () from /usr/lib64/libQt5Core.so.5
#3  0x00007fe9062be3b9 in QTimerInfoList::updateCurrentTime() () from /usr/lib64/libQt5Core.so.5
#4  0x00007fe9062be945 in QTimerInfoList::timerWait(timespec&) () from /usr/lib64/libQt5Core.so.5
#5  0x00007fe9062bfb5e in ?? () from /usr/lib64/libQt5Core.so.5
#6  0x00007fe90206f4ad in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0
#7  0x00007fe90206fd80 in ?? () from /usr/lib64/libglib-2.0.so.0
#8  0x00007fe90206ff7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#9  0x00007fe9062bfd8b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#10 0x00007fe906266d53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#11 0x00007fe90608861a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#12 0x00007fe90939ce18 in ?? () from /usr/lib64/libQt5Qml.so.5
#13 0x00007fe90608d32f in ?? () from /usr/lib64/libQt5Core.so.5
#14 0x00007fe9014b6754 in ?? () from /usr/X11R6/lib64/libGL.so.1
#15 0x00007fe90519c0a4 in start_thread () from /lib64/libpthread.so.0
#16 0x00007fe90599b02d in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7fe8e15c1700 (LWP 1408)):
#0  0x00007fe90206f7ec in g_main_context_check () from /usr/lib64/libglib-2.0.so.0
#1  0x00007fe90206fdf8 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007fe90206ff7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007fe9062bfd8b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#4  0x00007fe906266d53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#5  0x00007fe90608861a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x00007fe90939ce18 in ?? () from /usr/lib64/libQt5Qml.so.5
#7  0x00007fe90608d32f in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x00007fe9014b6754 in ?? () from /usr/X11R6/lib64/libGL.so.1
#9  0x00007fe90519c0a4 in start_thread () from /lib64/libpthread.so.0
#10 0x00007fe90599b02d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fe8f1c5a700 (LWP 1407)):
#0  0x00007fe906085c49 in QMutex::lock() () from /usr/lib64/libQt5Core.so.5
#1  0x00007fe9062bfcb5 in ?? () from /usr/lib64/libQt5Core.so.5
#2  0x00007fe90206f4ad in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0
#3  0x00007fe90206fd80 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x00007fe90206ff7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#5  0x00007fe9062bfd8b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#6  0x00007fe906266d53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#7  0x00007fe90608861a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#8  0x00007fe90939ce18 in ?? () from /usr/lib64/libQt5Qml.so.5
#9  0x00007fe90608d32f in ?? () from /usr/lib64/libQt5Core.so.5
#10 0x00007fe9014b6754 in ?? () from /usr/X11R6/lib64/libGL.so.1
#11 0x00007fe90519c0a4 in start_thread () from /lib64/libpthread.so.0
#12 0x00007fe90599b02d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fe8f4caa700 (LWP 1400)):
#0  0x00007fe905992bfd in poll () from /lib64/libc.so.6
#1  0x00007fe90a8e6422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x00007fe90a8e800f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x00007fe8f742d3c9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x00007fe90608d32f in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x00007fe9014b6754 in ?? () from /usr/X11R6/lib64/libGL.so.1
#6  0x00007fe90519c0a4 in start_thread () from /lib64/libpthread.so.0
#7  0x00007fe90599b02d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fe90c4997c0 (LWP 1397)):
[KCrash Handler]
#6  0x00007fe9058eb0c7 in raise () from /lib64/libc.so.6
#7  0x00007fe9058ec478 in abort () from /lib64/libc.so.6
#8  0x00007fe90607b7ce in QMessageLogger::fatal(char const*, ...) const () from /usr/lib64/libQt5Core.so.5
#9  0x00007fe909fa5e71 in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /usr/lib64/libQt5Quick.so.5
#10 0x00007fe909faece9 in ?? () from /usr/lib64/libQt5Quick.so.5
#11 0x00007fe909faf0db in ?? () from /usr/lib64/libQt5Quick.so.5
#12 0x00007fe9067c2b69 in QWindow::event(QEvent*) () from /usr/lib64/libQt5Gui.so.5
#13 0x00007fe909fe00d1 in QQuickWindow::event(QEvent*) () from /usr/lib64/libQt5Quick.so.5
#14 0x0000000000442cb6 in DesktopView::event(QEvent*) ()
#15 0x00007fe9075e3e7c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#16 0x00007fe9075e8cc8 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#17 0x00007fe906268e95 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5
#18 0x00007fe9067bb5d4 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () from /usr/lib64/libQt5Gui.so.5
#19 0x00007fe9067bc1ed in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib64/libQt5Gui.so.5
#20 0x00007fe9067a1268 in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Gui.so.5
#21 0x00007fe8f7458200 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#22 0x00007fe90206fc84 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#23 0x00007fe90206fed8 in ?? () from /usr/lib64/libglib-2.0.so.0
#24 0x00007fe90206ff7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#25 0x00007fe9062bfd6c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#26 0x00007fe906266d53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#27 0x00007fe90626e8f6 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5
#28 0x0000000000436b3d in main ()

I copied files from $HOME/bin to $HOME/bin. Only my scripts and compiled personal programs.

From .xsession-errors, repeated several times different PID’s…

KCrash: Application 'plasmashell' crashing...
KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit
kdeinit5: Got EXEC_NEW '/usr/lib64/libexec/drkonqi' from wrapper.
kdeinit5: preparing to launch '/usr/lib64/libexec/drkonqi'
kdeinit5: PID 1386 terminated.

From .xsession-errors, repeated many, many times…

org.kde.plasma: unversioned plugin detected, may result in instability

I hope I got it all. And thanks for the help.

Definitely not, I’d say.
It was just my first thought when I read that you copied over files…

Could not find IceWM.

It should be there I think?
Just to be clear, I mean the login screen where you have to choose/enter your user name and then enter the password.
If you have Auto-login enabled (which is the default) and are inside the “broken” KDE session, you can press Ctrl+Alt+Backspace twice to get back to the login screen.

Backtrace…

Ok, seems to crash somewhere inside QML.

As it’s Plasma that’s crashing, please try to delete or (better) rename ~/.config/plasma-org.kde.plasma.desktop-appletsrc.
Can you login then?

When I press Ctrl+Alt+Backspace twice all I get is a black screen.

Ok, seems to crash somewhere inside QML.

As it’s Plasma that’s crashing, please try to delete or (better) rename ~/.config/plasma-org.kde.plasma.desktop-appletsrc.
Can you login then?

I did that. It made no difference.

I have my doubts whether you didn’t copy any config files. Can you tell us what exactly you copied? F.e. ~/.local/share does contain files that could break things. And how you copied them?

Perhaps this provides a hint. When I invoke “icewm” from a console either as user or root it replies…

IceWM: Can't open display : <none>. X must be running and $DISPLAY set.

Yet when I invoke “top” it shows X as a running process.

The exact command was…

# fdisk -l
# mount  /dev/sdb1 /mnt/SERVER
# ls /mnt/SERVER/home/ion/bin (making sure I have the right directory)
# mount  /dev/sdc1 /mnt/USB_DRIVE
# rsync -av --delete   /mnt/USB_HDRIVE/IONHOME-MALMO/bin/ /mnt/SERVER/home/ion/bin

As far as I can see it was only from one directory to one directory.

Not exact, I hope.

I’m not sure what you mean by that. Do you see an obvious error? I was merely going back in time with commands invoked from the console as root.

Some further output from invoking “startplasma”

QXcbConnection: Could not connect to display xset:  unable to open display ""
xsetroot:  unable to open display ''
startplasma: Starting up...
xprop:  unable to open display ''
xprop:  unable to open display ''
kdeinit5: Aborting. $DISPLAY is not set. 
kdeinit5_wrapper: Warning: connect(/run/user/0/kdeinit5__0) failed: : No such file or directory
Cannot connect to the X server
QXcbConnection: Could not connect to display 
/usr/lib64/libexec/startplasma: line 144:  1494 Aborted                 kwrapper5 /usr/bin/ksmserver $KDEWM $KSMSERVEROPTIONS
startplasma: Shutting down...
kdeinit5_wrapper: Warning: connect(/run/user/0/kdeinit5__0) failed: : No such file or directory
Error: Can not contact kdeinit5!
xprop:  unable to open display ''
xprop:  unable to open display ''
startplasma: Done.

And yes when I “echo $DISPLAY” it’s blank.

The mountpoints used in the commands to mount the USB_DRIVE don’t match. See the bold parts

Aging eyesight problem. Thanks for pointing that out, but I still don’t see how that could affect the setting of $DISPLAY and subsequent plasma crash. I was only dealing with my home bin directory which shouldn’t come into play during bootup.

I set $DISPLAY to :0.0 but that had no effect.

First, the command to start a KDE/Plasma session is “startkde”, not “startplasma”.
Second, you cannot run that in text mode, it needs a running X11 session.

Use “startx” instead (only works as root by default though).

Apparently you only copied files to ~/bin/ then, so even if that would have caused the problem, it would only affect your user account (and not the login screen e.g.).

I would suggest trying to set DISPLAYMANAGER=“xdm” in /etc/sysconfig/displaymanager, that should give you a working login screen at least.
Plasma still won’t start I suppose, so set DEFAULT_WM=“icewm” in /etc/sysconfig/windowmanager to get a working graphical session.

Then run “startkde” or “plasmashell” in an xterm (or konsole) and post the output.

Also, I’d try a fresh user account (to at least see if Plasma starts then), but as SDDM is affected too it’s more likely a general installation problem anyway (incompatible mixture of Qt5 packages maybe?)

Also, please post /var/log/Xorg.0.log, so we can see if it’s maybe a problem with the graphics driver (QML, and therefore SDDM and Plasma, absolutely needs working OpenGL support).

Finally, a positive result. I got icewm running.

Then run “startkde” or “plasmashell” in an xterm (or konsole) and post the output.

Also, please post /var/log/Xorg.0.log, so we can see if it’s maybe a problem with the graphics driver (QML, and therefore SDDM and Plasma, absolutely needs working OpenGL support).

The output from startkde is a big file (100K). How do you want me to send it to you.

If it’s OK I posted the two requested files at…

http://pastebin.com/PP5D9FZK

http://pastebin.com/T8fVb2Zh

otherwise let me know.

Yes, that’s fine, thanks.

http://pastebin.com/PP5D9FZK

This shows that you are using nvidia 304.132.
Seems to be ok, but apparently there are problems with this driver version currently:
https://forums.opensuse.org/showthread.php/520666-Nvidia-not-working-for-non-root-user-after-upgrade-to-Leap-42-1

Can you confirm that it works fine as root?
And/or post the output of “glxinfo” (you may need to install Mesa-demo-x first).

Yes, I can boot into icewm as root, open a console and invoke startkde which runs fine. I am using it to respond now. Would you mind pointing out how you came to that conclusion from the log files. Then perhaps next time I can diagnose it on my own. Thanks for all the help.