Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#72420 - Plasma 5.23 crash

Attached to Project: Arch Linux
Opened by Mike Cloaked (mcloaked) - Thursday, 14 October 2021, 14:55 GMT
Last edited by Antonio Rojas (arojas) - Sunday, 17 October 2021, 16:34 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Antonio Rojas (arojas)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Plasma 5.23 crashes on startup

Additional info:
* package version(s) plasma-desktop-5.23.0-1
* config and/or log files etc.
* link to upstream bug report, if any

https://bugs.kde.org/show_bug.cgi?id=443708

Steps to reproduce: Update plasma desktop package set to 5.23 - plasma crashes on startup and is not usable. This report is to track the upstream report until a fix is in place before releasing the package set from testing to extra
This task depends upon

Closed by  Antonio Rojas (arojas)
Sunday, 17 October 2021, 16:34 GMT
Reason for closing:  Fixed
Additional comments about closing:  plasma-desktop 5.23.0-2
Comment by Mike Cloaked (mcloaked) - Thursday, 14 October 2021, 15:01 GMT
The severity should be increased as it is a more serious problem than a low severity bug.
Comment by Antonio Rojas (arojas) - Friday, 15 October 2021, 06:41 GMT
Can you post your plasma-org.kde.plasma.desktop-appletsrc? Make sure to scan it for private data first.
Comment by Mike Cloaked (mcloaked) - Friday, 15 October 2021, 09:35 GMT
plasma-org.kde.plasma.desktop-appletsrc
Comment by Gene (GeneC) - Friday, 15 October 2021, 11:40 GMT
plasma appletrc file
Comment by Antonio Rojas (arojas) - Friday, 15 October 2021, 14:41 GMT
Thank you both. I have extracted a minimal reproducer config and posted it upstream.
Comment by Gene (GeneC) - Friday, 15 October 2021, 14:44 GMT
Thank you! That's a really minimal config.
Comment by Mike Cloaked (mcloaked) - Friday, 15 October 2021, 17:46 GMT
Thank you and that is a very valuable additional input on the upstream bug.
Comment by Antonio Rojas (arojas) - Sunday, 17 October 2021, 10:07 GMT
Should be fixed with plasma-desktop 5.23.0-2, please confirm.
Comment by Gene (GeneC) - Sunday, 17 October 2021, 10:46 GMT
Partly:

Good: plasmashell no longer core dumps.

Bad: After logging in via sddm the screen flashes the background image which user uses on both monitors, then it goes black and stays black - no desktop at all.
Full update and reboot - journalctl no longer shows any crash (obviously).

The only message of interest is not new - was there with earlier versions of plasma - added for completeness only.
QObject: Cannot create children for a parent that is in a different thread.
(Parent is QGuiApplication(0x7fff0d857720), parent's thread is QThread(0x5593255c2d40), current thread is QThread(0x559325734b80)

Also same old bunch of errors from theme breeze-noir-dark - as above these are not new.
Comment by Gene (GeneC) - Sunday, 17 October 2021, 10:51 GMT
forgot to mention that the QObject message is from sddm-greeter - it repeats 3 times then followed by QObject::installEventFilter(): Cannot filter events for objects in a different thread.

As I said this is not new.

Any suggestions what I can do to help track this down?
Comment by Gene (GeneC) - Sunday, 17 October 2021, 11:00 GMT
More good news:
I created a new user with no plasma customizations at all and logged in no problem.

So something about the existing settings is causing the desktop to be black instead of showing background image. She also has 2 panels - 1 horizontal on bottom and one vertical on right side.
And uses a breeze-noir-dark theme.

I will investigate and see what else I can learn. So there really were 2 issues with 5.23.0 - the plasmashell crash (now fixed) and this missing desktop issue which remains.
Comment by Antonio Rojas (arojas) - Sunday, 17 October 2021, 11:03 GMT
It is still not clear to me what your issue is. Is it *just* the background image missing, or is plasmashell not loading at all?
Comment by Gene (GeneC) - Sunday, 17 October 2021, 11:10 GMT
Sorry for not being clear. The existing user after logging in has completely black screen - nothing at all is visible - no panes, no background nothing - screen is black.
Comment by Antonio Rojas (arojas) - Sunday, 17 October 2021, 11:13 GMT
Is plasmashell running at all? Please post the terminal output of the 'plasmashell --replace' command.
Comment by Gene (GeneC) - Sunday, 17 October 2021, 11:15 GMT
plasmashell was running yes - i checked using 'ps'.

I will go back to that computer and login as her and then report back on plasmashell --replace'
Comment by Antonio Rojas (arojas) - Sunday, 17 October 2021, 11:24 GMT
ok, then it seems to be an unrelated problem, probably related to multi-monitor setup.
Comment by Gene (GeneC) - Sunday, 17 October 2021, 11:27 GMT
Since there is nothing visible on screen, I switched to virtual terminal

1) ps -eaf | grep plasmashell
shows its running aloging with a bunch of /usr/lib/kf5/kioslave5 .... local:/run/user/xxx/plasmashellXXXX.N.slave-socket

2) In VT i ran plasmashell --replace as same user that logged in via sddm:
Typing what I saw in VT:

This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, waylandxcomposite-glx, xcb

Aborted (core dumped)

Comment by Gene (GeneC) - Sunday, 17 October 2021, 11:29 GMT
Could be, but it does work fine 2 monitors for a new user with default kde/plasma set up.
Comment by Antonio Rojas (arojas) - Sunday, 17 October 2021, 11:55 GMT
> In VT i ran plasmashell --replace as same user that logged in via sddm:

You need to run it on the VT where the X server is. Set DISPLAY=:0 (changing 0 as needed).
Comment by Gene (GeneC) - Sunday, 17 October 2021, 12:47 GMT
AH thanks that makes sense. I did that - it returns silently. WHen I switch back to desktop its the same - just black nothing visible.
She has been using the same config for many years - so at this point a fresh start looks to be required. I will delete all her .kde4 .local and .config and start fresh, unless there is something else you'd like me to try.

thanks for fixing the crash and for all your help.

Loading...