#1028197 plasmashell: Program terminated with signal SIGSEGV

Package:
plasma-workspace
Source:
plasma-workspace
Description:
Plasma Workspace for KF5
Submitter:
piorunz
Date:
2023-01-24 00:33:03 UTC
Severity:
normal
#1028197#5
Date:
2023-01-08 11:19:09 UTC
From:
To:
Dear Maintainer,

plasmashell is crashing very often on Debian Testing.
Latest crash happened just now, segmentation fault. Plasmashell, along with all
icons and panels disappeared completely and launched again.

I am using Debian Testing, fully updated, on AMD64 machine with ECC RAM and
RAID1 storage.

Full gdb backtrace attached.
#1028197#10
Date:
2023-01-23 16:05:42 UTC
From:
To:
(gdb) bt
...
#4  <signal handler called>
#5  0x00007f54b82563fb in QQuickItem::~QQuickItem() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x00007f54b83d0045 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x00007f54b66dd53f in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f54b7362f5e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x00007f54b66b17c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f54b66b4761 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007f54b670a1d3 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007f54b46657a9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007f54b4665a38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007f54b4665acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007f54b67098b6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007f54b66b024b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007f54b66b83b6 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x000055937ecd0c6c in ?? ()
#19 0x00007f54b624618a in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#20 0x00007f54b6246245 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6


Hello Piotr,
I fear that backtrace is not that distinctive.
Upstream I found [1] a few bugs, but they also do
not give helpful pointers.

So here it might also be helpful to see what might be contained
in journalctl or in .xsession-errors:

   journalctl --user --since="2023-01-08 12:10" --until="2023-01-08 12:12"

Can you please give a rough estimate how often it does crash?

Kind regards,
Bernhard

[1]
https://bugs.kde.org/show_bug.cgi?id=461464
https://bugs.kde.org/show_bug.cgi?id=460477
#1028197#15
Date:
2023-01-23 21:48:23 UTC
From:
To:
Thanks for your reply. I am not sure what bug you want me to reply to so
I reply to both.

Plasma, or kwin, or entire desktop crashes all the time. There most
likely are multiple bugs. This is one of them. Sometimes desktop crashes
and there is no SIGSEV. Usually I launch Konsole from shortcut, restart
kwin and plasmashell with --replace option, but this not always helps.
I have modern Radeon GPU, it probably adds fuel to the fire.
Can't wait for more updates regarding kwin/plasmashell/multi monitor
handling/sleeping and waking up the monitor. There is a lot of bugs in
these areas, when Radeon GPU is involved at least. I will be happy to
debug as much as I can, you can tell me what else to do.

$ journalctl --user --since="2023-01-08 14:34" --until="2023-01-08 14:38"
-- No entries --

  journalctl --user --since="2023-01-08 12:10" --until="2023-01-08 12:12"
-- No entries --

.xsession-errors:

Xsession: X session started for pioruns at Sat  7 Jan 08:04:38 GMT 2023
dbus-update-activation-environment: setting
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting
XAUTHORITY=/home/pioruns/.Xauthority
localuser:pioruns being added to access control list
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
file:///home/pioruns/.local/share/plasma/look-and-feel/com.github.vinceliuice.Qogir-light/contents/splash/Splash.qml:89:
ReferenceError: bottomRect is not defined
file:///home/pioruns/.local/share/plasma/look-and-feel/com.github.vinceliuice.Qogir-light/contents/splash/Splash.qml:88:
ReferenceError: bottomRect is not defined
file:///home/pioruns/.local/share/plasma/look-and-feel/com.github.vinceliuice.Qogir-light/contents/splash/Splash.qml:89:
ReferenceError: bottomRect is not defined
file:///home/pioruns/.local/share/plasma/look-and-feel/com.github.vinceliuice.Qogir-light/contents/splash/Splash.qml:89:
ReferenceError: bottomRect is not defined
file:///home/pioruns/.local/share/plasma/look-and-feel/com.github.vinceliuice.Qogir-light/contents/splash/Splash.qml:88:
ReferenceError: bottomRect is not defined
file:///home/pioruns/.local/share/plasma/look-and-feel/com.github.vinceliuice.Qogir-light/contents/splash/Splash.qml:89:
ReferenceError: bottomRect is not defined
Xsession: X session started for pioruns at Mon  9 Jan 10:52:01 GMT 2023

This seems to be a session between 7th and 9th January.
#1028197#20
Date:
2023-01-23 22:46:17 UTC
From:
To:
https://bugs.debian.org/1028197

Then please try something like this:

   journalctl --user --since="2023-01-08 11:08" --until="2023-01-08 11:12"
#1028197#25
Date:
2023-01-23 23:30:55 UTC
From:
To:
That worked! Attached.
#1028197#30
Date:
2023-01-24 00:05:12 UTC
From:
To:
Am 24.01.23 um 00:30 schrieb piorunz:
Jan 08 11:11:06 ryzen systemd-coredump[1987371]: Process 1341349 (kded5) of user 1000 dumped core.
...
                                                  #3  0x00007faafb991f90 n/a (libc.so.6 + 0x3bf90)
                                                  #4  0x00007faa7b2e8ba4 _ZNK10PackageKit11Transaction4roleEv (libpackagekitqt5.so.1 + 0x1aba4)
                                                  #5  0x00007faa7b3a4aae n/a (kded_apperd.so + 0xeaae)
                                                  #6  0x00007faa7b3a4b99 n/a (kded_apperd.so + 0xeb99)
                                                  #7  0x00007faafb6e8fcf n/a (libQt5Core.so.5 + 0x2e8fcf)
                                                  #8  0x00007faa7b2dc095 _ZN10PackageKit6Daemon22transactionListChangedERK11QStringList (libpackagekitqt5.so.1 + 0xe095)
Jan 08 11:11:07 ryzen kscreen_backend_launcher[5795]: kscreen.xrandr: XRandR::setConfig
Jan 08 11:11:07 ryzen kscreen_backend_launcher[5795]: kscreen.xrandr: Requested screen size is QSize(7680, 2160)
Jan 08 11:11:07 ryzen kscreen_backend_launcher[5795]: kscreen.xrandr: Needed CRTCs:  2
Jan 08 11:11:07 ryzen kscreen_backend_launcher[5795]: kscreen.xrandr: Actions to perform:
Jan 08 11:11:07 ryzen kscreen_backend_launcher[5795]:          Primary Output: false
Jan 08 11:11:07 ryzen kscreen_backend_launcher[5795]: kscreen.xrandr:         Change Screen Size: false
Jan 08 11:11:07 ryzen kscreen_backend_launcher[5795]: kscreen.xrandr:         Disable outputs: false
Jan 08 11:11:07 ryzen kscreen_backend_launcher[5795]: kscreen.xrandr:         Change outputs: false
Jan 08 11:11:07 ryzen kscreen_backend_launcher[5795]: kscreen.xrandr:         Enable outputs: false
Jan 08 11:11:07 ryzen kscreen_backend_launcher[5795]: kscreen.xrandr: XRandR::setConfig done!
Jan 08 11:11:07 ryzen plasmashell[5575]: QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
Jan 08 11:11:07 ryzen plasmashell[5575]: 25 -- exe=/usr/bin/plasmashell
Jan 08 11:11:07 ryzen plasmashell[5575]: KCrash: crashing... crashRecursionCounter = 2


Here was also just before such a kded5 crash right before.
Either this or the startup of the new kded5 might trigger this,
as it looks like setting up some screen parameters (xrandr).
And while doing this plasmashell wrote
this "QFont::setPointSizeF" message.

Those two upstream bugs appear, but both got closed,
because upstream could not reproduce them:
https://bugs.kde.org/show_bug.cgi?id=453712
https://bugs.kde.org/show_bug.cgi?id=462098

I don't know which package management you use,
but until there is a fix for Debian #1026062,
you could experiment with another package manager
like synaptic and uninstall apper for now, as a workaround.

Kind regards,
Bernhard
#1028197#35
Date:
2023-01-24 00:28:24 UTC
From:
To:
Very rarely I ever launch KDE's Discover program. Discover has came with
Debian's KDE, I did not asked for it to be installed.
apper, about which I didn't know anything until this issue, also came
with KDE uninvited. Just found this in apt logs:

Start-Date: 2023-01-08  15:03:28
Commandline: apt purge apper
Requested-By: pioruns (1000)
Purge: apper:amd64 (1.0.0-3)
End-Date: 2023-01-08  15:03:30

I uninstalled apper after I reported this bug it seems, thanks to advice
from Debian KDE mailing list. This particular bug has not returned since
then. Today I had another desktop crash, but that's probably unrelated.
I can install apper again if you want me to try and reproduce some more
of it.