Bug 470090 - [Wayland][Nvidia?] Ksplashqml, plasma and systemsettings crash on login
Summary: [Wayland][Nvidia?] Ksplashqml, plasma and systemsettings crash on login
Status: RESOLVED WORKSFORME
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Kubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: wayland
Depends on:
Blocks:
 
Reported: 2023-05-21 15:42 UTC by Syfer Polski
Modified: 2023-06-27 03:45 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
kcrash created by Dr. Konqi (1.81 KB, text/plain)
2023-05-21 15:42 UTC, Syfer Polski
Details
system settings crash file (4.27 KB, text/plain)
2023-05-21 15:57 UTC, Syfer Polski
Details
PlasmaShell crash file (1.90 KB, text/plain)
2023-05-21 16:26 UTC, Syfer Polski
Details
ksmserver crash file (1.93 KB, text/plain)
2023-05-21 16:27 UTC, Syfer Polski
Details
PlasmaShell crash file (2.00 KB, text/plain)
2023-05-21 17:12 UTC, Syfer Polski
Details
ksmservber crash file (1.58 KB, text/plain)
2023-05-21 17:16 UTC, Syfer Polski
Details
PlasmaShell crash file (1.65 KB, text/plain)
2023-05-21 17:35 UTC, Syfer Polski
Details
ksmserver crash file (1.58 KB, text/plain)
2023-05-21 17:37 UTC, Syfer Polski
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Syfer Polski 2023-05-21 15:42:52 UTC
Created attachment 159165 [details]
kcrash created by Dr. Konqi

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Select Wayland session on login screen
2. Enter password
3.  Press log in

OBSERVED RESULT
Plasma crashes on startup

EXPECTED RESULT
Plasma starts up

SOFTWARE/OS VERSIONS
Qt Version: 5.15.3
Frameworks Version: 5.92.0
Operating System: Linux 5.19.0-41-generic x86_64
Windowing System: Wayland
Distribution: Ubuntu 22.04.2 LTS
DrKonqi: 5.24.5 [KCrashBackend]

ADDITIONAL INFORMATION
This is an Optimus laptop - integrated AMD GPU and dedicated GPU. The Nvidia GPU is operating in On-demand mode - the desktop should be running from the AMD gpu. When the system works (on X11 graphics server) the drivers manifest thus:

```bash
user@laptop:~$ inxi -G
Graphics:
  Device-1: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q] driver: nvidia
    v: 525.105.17
  Device-2: AMD Renoir driver: amdgpu v: kernel
  Display: x11 server: X.Org v: 1.21.1.4 driver: X:
    loaded: amdgpu,ati,nvidia unloaded: fbdev,modesetting,nouveau,vesa
    gpu: amdgpu resolution: 1920x1080~144Hz
  OpenGL: renderer: RENOIR (renoir LLVM 15.0.6 DRM 3.47 5.19.0-41-generic)
    v: 4.6 Mesa 22.2.5
user@laptop:~$ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia inxi -G
Graphics:
  Device-1: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q] driver: nvidia
    v: 525.105.17
  Device-2: AMD Renoir driver: amdgpu v: kernel
  Display: x11 server: X.Org v: 1.21.1.4 driver: X:
    loaded: amdgpu,ati,nvidia unloaded: fbdev,modesetting,nouveau,vesa
    gpu: amdgpu resolution: 1920x1080~144Hz
  OpenGL: renderer: NVIDIA GeForce GTX 1650/PCIe/SSE2
    v: 4.6.0 NVIDIA 525.105.17
```

I've since installed more ddebug files and will reproduce the crash with fewer missing line mappings. However, I've not been able to install the following debug symbol packages used by ksplashqml:
The following packages have unmet dependencies.
 libcom-err2-dbgsym : Depends: libcom-err2 (= 1.46.5-2ubuntu1) but 1.46.5-2ubuntu1.1 is to be installed
 libdbus-1-3-dbgsym : Depends: libdbus-1-3 (= 1.12.20-2ubuntu4) but 1.12.20-2ubuntu4.1 is to be installed
 libexpat1-dbgsym : Depends: libexpat1 (= 2.4.7-1) but 2.4.7-1ubuntu0.2 is to be installed
 libgcc-s1-dbgsym : Depends: libgcc-s1 (= 12-20220319-1ubuntu1) but 12.1.0-2ubuntu1~22.04 is to be installed
 plasma-workspace-dbgsym : Depends: plasma-workspace (= 4:5.24.4-0ubuntu1) but 4:5.24.7-0ubuntu0.1 is to be installed
E: Unable to correct problems, you have held broken packages.
Comment 1 Syfer Polski 2023-05-21 15:56:55 UTC
There are 3 crashes that happen in quick succession: plasma, ksplashqml and systemsettings. I'm attachign the .kcrash files for all 3
Comment 2 Syfer Polski 2023-05-21 15:57:45 UTC
Created attachment 159167 [details]
system settings crash file
Comment 3 Syfer Polski 2023-05-21 16:26:55 UTC
Created attachment 159168 [details]
PlasmaShell crash file
Comment 4 Syfer Polski 2023-05-21 16:27:58 UTC
Created attachment 159169 [details]
ksmserver crash file

logging out subsequently also causes a crash, this time in ksmserver
Comment 5 Syfer Polski 2023-05-21 17:12:36 UTC
Created attachment 159170 [details]
PlasmaShell crash file
Comment 6 Syfer Polski 2023-05-21 17:16:21 UTC
Created attachment 159171 [details]
ksmservber crash file
Comment 7 Syfer Polski 2023-05-21 17:35:01 UTC
Created attachment 159172 [details]
PlasmaShell crash file
Comment 8 Syfer Polski 2023-05-21 17:36:51 UTC
systemsettings only crashes on startup if it was opened before the user logged out and thus tries to restore itself. Does not crash otherwise. 
plasma and ksplashqml crash 100% of the time, ksmserver crashes when attempting to log out.
Comment 9 Syfer Polski 2023-05-21 17:37:51 UTC
Created attachment 159173 [details]
ksmserver crash file
Comment 10 Syfer Polski 2023-05-21 17:40:03 UTC
I've manually installed all the debug files that find-dbgsym-packages suggested that I couldn't find in the repository. I don't know why there is no linemapping for 
#16 0x00007f49aa4b875b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
Comment 11 Syfer Polski 2023-05-21 17:48:10 UTC
Sorry the mysterious function common to all crashes is 
In ksplashqml:
#14 0x00007f49aa4f17c8 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
In plasmashell:
#15 0x00007f8ef9cf17c8 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
In ksmserver:
#14 0x00007f29816f17c8 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5

The systemsettings crash seems to happen in different functions (except for 
#12 0x00007f298132b3e4 in QtWaylandClient::QWaylandDisplay::checkError (this=<optimized out>) at ./src/client/qwaylanddisplay.cpp:211
but that's probably an error recovery function)
Comment 12 Nate Graham 2023-05-22 21:52:27 UTC
Can you use `coredumpctl --reverse` to see if kwin_wayland is crashing? If so, let's get a backtrace of that.
Comment 13 Syfer Polski 2023-05-23 20:45:37 UTC
apt info plasma-workspace
Package: plasma-workspace
Version: 4:5.24.7-0ubuntu0.1
Priority: optional
Section: universe/kde
Origin: Ubuntu
Maintainer: Kubuntu Developers <kubuntu-devel@lists.ubuntu.com>
Original-Maintainer: Debian Qt/KDE Maintainers <debian-qt-kde@lists.debian.org>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug

I'll try to get the backtrace tomorrow
Comment 14 Syfer Polski 2023-05-25 07:04:33 UTC
Kwin is not crashing. This is the output from coredumpctl:

TIME                         PID  UID  GID SIG     COREFILE     EXE                                                                       SIZE
Thu 2023-05-25 08:00:17 BST 3555 1000 1000 SIGABRT present      /usr/bin/plasmashell                                                      6.9M
Thu 2023-05-25 08:00:05 BST 3467 1000 1000 SIGABRT present      /usr/bin/ksplashqml                                                       2.2M
Thu 2023-05-25 08:00:03 BST 3915 1000 1000 SIGABRT present      /usr/bin/plasmashell                                                      9.1M
Thu 2023-05-25 08:00:00 BST 3817 1000 1000 SIGSYS  present      /usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner 332.3K
Thu 2023-05-25 07:59:56 BST 3363 1000 1000 SIGABRT present      /usr/lib/x86_64-linux-gnu/libexec/xdg-desktop-portal-kde                858.3K
Thu 2023-05-25 07:59:48 BST 3305  119  128 SIGSYS  inaccessible /usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner    n/a
Thu 2023-05-25 07:58:53 BST 1520 1000 1000 SIGSYS  present      /usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner 332.4K
Thu 2023-05-25 07:58:46 BST 1243  119  128 SIGSYS  inaccessible /usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner    n/a
Wed 2023-05-24 07:44:28 BST 1494 1000 1000 SIGSYS  present      /usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner 332.0K
Wed 2023-05-24 07:44:10 BST 1207  119  128 SIGSYS  inaccessible /usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner    n/a
Tue 2023-05-23 17:36:39 BST 1505 1000 1000 SIGSYS  present      /usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner 332.8K
Tue 2023-05-23 17:36:28 BST 1211  119  128 SIGSYS  inaccessible /usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner    n/a
Comment 15 Nate Graham 2023-05-26 14:31:48 UTC
Thanks. Unfortunately I failed to notice earlier that you're still using Plasma 5.24. I'm afraid that version is no longer supported. Can you upgrade to Kubuntu 23.04 to get Plasma 5.27, and see if it's still happening?
Comment 16 Syfer Polski 2023-05-28 07:42:15 UTC
Sorry, probably not. I guess the bug report gets closed as "unmaintained" then.
Comment 17 Bug Janitor Service 2023-06-12 03:45:26 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 18 Bug Janitor Service 2023-06-27 03:45:17 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!