Bug 478194 - Plasma crashes on connecting second monitor with specific display settings
Summary: Plasma crashes on connecting second monitor with specific display settings
Status: RESOLVED BACKTRACE
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (show other bugs)
Version: 5.27.9
Platform: Kubuntu Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi, multiscreen
Depends on:
Blocks:
 
Reported: 2023-12-07 07:05 UTC by kde-bugs
Modified: 2023-12-11 14:27 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kde-bugs 2023-12-07 07:05:05 UTC
Application: plasmashell (5.27.9)

Qt Version: 5.15.3
Frameworks Version: 5.104.0
Operating System: Linux 6.2.0-37-generic x86_64
Windowing System: Wayland
Distribution: Ubuntu 22.04.3 LTS
DrKonqi: 5.27.9 [KCrashBackend]

-- Information about the crash:
I've configured display setings so that when connecting to external monitor, main laptop monitor disables. So when plasma is switching working display, it crashes.
Issue not occures when main monitor is not set to be disabled on external monitor connection.

NOTE:
configuration is "built-in display enabled false + save this configuration for only this display arrangement"

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault

[KCrash Handler]
#4  0x00007fd756ce8754 in QObjectPrivate::connectImpl(QObject const*, int, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007fd756ce8b15 in QObject::connectImpl(QObject const*, void**, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x0000558b86807f48 in  ()
#7  0x0000558b868081f3 in  ()
#8  0x0000558b8681a8a1 in  ()
#9  0x00007fd756cf1793 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007fd756cf57fe in QTimer::timeout(QTimer::QPrivateSignal) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007fd756ce733f in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007fd75796c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007fd756cb9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007fd756d123eb in QTimerInfoList::activateTimers() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007fd756d12d34 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007fd7557acd3b in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007fd755802258 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007fd7557aa3e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007fd756d130b8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007fd756cb875b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007fd756cc0cf4 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x0000558b867eca6b in  ()
#23 0x00007fd756229d90 in __libc_start_call_main (main=main@entry=0x558b867ebb50, argc=argc@entry=1, argv=argv@entry=0x7fffac010e28) at ../sysdeps/nptl/libc_start_call_main.h:58
#24 0x00007fd756229e40 in __libc_start_main_impl (main=0x558b867ebb50, argc=1, argv=0x7fffac010e28, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffac010e18) at ../csu/libc-start.c:392
#25 0x0000558b867ecb95 in  ()
[Inferior 1 (process 57978) detached]

The reporter indicates this bug may be a duplicate of or related to bug 473202.

Reported using DrKonqi
Comment 1 David Edmundson 2023-12-11 14:27:52 UTC
>#6  0x0000558b86807f48 in  ()
#7  0x0000558b868081f3 in  ()
#8  0x0000558b8681a8a1 in  ()

Unfortunately we're missing symbols on the most relevant bit of code, and as such we can't do anything with this bug report. If you could ensure you have all relevant debug symbols and reopen if this crash still occurs.