Bug 488482 - Plasma always crashes when attaching laptop to docking station with lid closed
Summary: Plasma always crashes when attaching laptop to docking station with lid closed
Status: RESOLVED FIXED
Alias: None
Product: xdg-desktop-portal-kde
Classification: Plasma
Component: general (show other bugs)
Version: 6.1.2
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-14 06:46 UTC by Iyán M. V.
Modified: 2024-07-22 20:35 UTC (History)
6 users (show)

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


Attachments
coredumpctl debug 5984 (18.84 KB, text/x-log)
2024-06-14 06:46 UTC, Iyán M. V.
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Iyán M. V. 2024-06-14 06:46:39 UTC
Created attachment 170492 [details]
coredumpctl debug 5984

SUMMARY

This is a regression in Plasma 6.1. Plasma 6.0 was working perfectly. I can reproduce all the times. Many components crash when attaching the laptop to a docking station with the lid closed. When I open the lid, the lock screen is shown for a few seconds, before the whole session crashes and SDDM is shown.

The reason I add this bug to xdg-desktop-portal-kde is because in the list of crashes coredumpctl list (see at the end), this is the first process to crash, but feel free to move it to the right place.

STEPS TO REPRODUCE
1. Boot laptop and start Plasma 6.1 Wayland session
2. Close lid (laptop goes to sleep)
3. Attach laptop to docking station (I'm using a Dell WD19TBS)

OBSERVED RESULT
Laptop does not automatically wake up. Pressing external keyboard does not wake up the laptop either. When opening the lid (with laptop still attached to docking station), laptop wakes up but opened session crashes.

EXPECTED RESULT
Laptop automatically wakes up and lock screen is shown in external monitor (as in Plasma 6.0)

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.0.90
KDE Frameworks Version: 6.3.0
Qt Version: 6.8.0
Kernel Version: 6.9.4-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 22 × Intel® Core™ Ultra 7 155H
Memory: 30.9 GiB of RAM
Graphics Processor: Mesa Intel® Arc
Manufacturer: LENOVO
Product Name: 21KDS00600
System Version: ThinkPad X1 Carbon Gen 12

This is the output of coredumpctl list:

Fri 2024-06-14 08:18:27 CEST   5984 1000 1000 SIGABRT present  /usr/lib/xdg-desktop-portal-kde               1M
Fri 2024-06-14 08:18:27 CEST   4335 1000 1000 SIGSEGV present  /usr/bin/konsole                            3.2M
Fri 2024-06-14 08:18:27 CEST   3435 1000 1000 SIGSEGV present  /usr/bin/dolphin                            4.9M
Fri 2024-06-14 08:18:27 CEST   7037 1000 1000 SIGABRT present  /usr/lib/xdg-desktop-portal-kde          1019.9K
Fri 2024-06-14 08:18:27 CEST   7082 1000 1000 SIGABRT present  /usr/lib/xdg-desktop-portal-kde          1017.9K
Fri 2024-06-14 08:18:27 CEST   7115 1000 1000 SIGABRT present  /usr/lib/drkonqi                          863.4K
Fri 2024-06-14 08:18:27 CEST   7097 1000 1000 SIGABRT present  /usr/lib/xdg-desktop-portal-kde          1016.9K
Fri 2024-06-14 08:18:27 CEST   7117 1000 1000 SIGABRT present  /usr/lib/drkonqi                            864K
Fri 2024-06-14 08:18:28 CEST   7155 1000 1000 SIGABRT present  /usr/lib/xdg-desktop-portal-kde          1016.4K

I attach the trace of the first crash. If other would be useful I can attach later as well.
Comment 1 Nate Graham 2024-06-14 16:26:52 UTC
#8  0x00007d344c4dde49 in init_platform (pluginNamesWithArguments=..., platformPluginPath=..., platformThemeName=..., argc=@0x7fff395193cc: 1, argv=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/gui/kernel/qguiapplication.cpp:1326
        fatalMessage = {d = {d = 0x6301c5df08f0, ptr = 0x6301c5df0900 u"This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.\n\nAvailable platform plugins are: linuxfb, wayland, eglfs, minima"..., size = 263}, static _empty = 0 u'\000'}


I thought we'd fixed this.
Comment 2 Marco Martin 2024-06-25 12:35:27 UTC
does kwin crash as well?
Comment 3 Nate Graham 2024-06-26 19:12:37 UTC
.
Comment 4 Iyán M. V. 2024-07-01 14:11:59 UTC
Sometimes KWin crashes, sometimes it doesn't. When it crashes the laptop freezes for a while (sometimes just the cursor is shown) and then the SDDM screen appears. Other times, lately more often (I don't know if it's related to having updated to the release of 6.1), the laptop is unresponsive for a while and then it just works.

I got used to to open the laptop lid before attaching the laptop to the docking station, and this seems to always avoid the issue.
Comment 5 Iyán M. V. 2024-07-08 07:48:43 UTC
6.1.2 seems to have improve the situation a little bit, but still feels less reliable than 6.0. For example, last two times I attach the laptop to the docking station there was no complete crash (going to SDDM) but there was a period of time (~5-10 seconds) where the laptop was unresponsive in the locking screen.

The only crashes I observed now were related to ddcutil:

Mon 2024-07-08 09:17:48 CEST   9422    0    0 SIGSEGV present  /usr/bin/ddcutil                                                    119.3K
Mon 2024-07-08 09:17:48 CEST   9421    0    0 SIGSEGV present  /usr/bin/ddcutil                                                    118.3K
Mon 2024-07-08 09:17:49 CEST   9802    0    0 SIGSEGV present  /usr/bin/ddcutil                                                    117.8K
Mon 2024-07-08 09:17:49 CEST   9804    0    0 SIGSEGV present  /usr/bin/ddcutil                                                    117.7K

I have left a comment with the bt in this other bug report (I thought it was related when searching recent ddcutil related issues, but perhaps I'm wrong): https://bugs.kde.org/show_bug.cgi?id=489169#c19
Comment 6 Nate Graham 2024-07-22 20:35:53 UTC
These ddcutil crashes are different from that one, and also different from what this is reporting. Sounds like this issue is fixed now, and has been replaced with a new different ddcutil crash. Can you open a new bug report for that? Thanks!