Bug 462802

Summary: kscreen system settings crash when attempting to revert display layout change
Product: [Applications] systemsettings Reporter: f.kargl
Component: kcm_kscreenAssignee: kscreen-bugs-null <kscreen-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash CC: f.kargl, nate, plasma-bugs
Priority: NOR Keywords: drkonqi
Version: 5.26.4   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: New crash information added by DrKonqi

Description f.kargl 2022-12-09 00:17:28 UTC
Application: systemsettings (5.26.4)

Qt Version: 5.15.6
Frameworks Version: 5.100.0
Operating System: Linux 6.0.0-5-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux bookworm/sid
DrKonqi: 5.26.4 [KCrashBackend]

-- Information about the crash:
Attempted to fix display layout which was reset after reboot due to https://bugs.kde.org/show_bug.cgi?id=451591
The alignment between two adjacent displays was a bit off so I tried to slightly readjust it by moving one display in the layout. The new alignment was not like intended so I attempted to revert it by clicking the revert button on the popup that is shown after making a display layout change. The display layout was reverted to the original after the screen froze for a bit. After this, the display layout system settings window did not show the usual layout settings but was mostly blank with only a light blue stripe shown at the top of the window. (The blue stripe looked similar to an information popup, but did not display any text). When attempting to interact with the window and click on it, it crashed and popped the bug report screen.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr<char []> = {get() = 0x0}
[KCrash Handler]
#6  QSharedPointer<KScreen::Screen>::data (this=<optimized out>) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qsharedpointer_impl.h:301
#7  QSharedPointer<KScreen::Screen>::operator-> (this=<optimized out>) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qsharedpointer_impl.h:307
#8  KScreen::Config::clone (this=0x0) at ./src/config.cpp:204
#9  0x00007efd4caead1e in ConfigHandler::updateInitialData (this=0x560d539d3110) at ./kcm/config_handler.cpp:77
#10 0x00007efd4caecc5f in operator() (__closure=0x560d54331510) at ./kcm/kcm.cpp:192
#11 QtPrivate::FunctorCall<QtPrivate::IndexesList<>, QtPrivate::List<>, void, KCMKScreen::doSave(bool)::<lambda()> >::call (arg=<optimized out>, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:146
#12 QtPrivate::Functor<KCMKScreen::doSave(bool)::<lambda()>, 0>::call<QtPrivate::List<>, void> (arg=<optimized out>, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:256
#13 QtPrivate::QFunctorSlotObject<KCMKScreen::doSave(bool)::<lambda()>, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=<optimized out>, this_=0x560d54331500, r=<optimized out>, a=<optimized out>, ret=<optimized out>) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:443
#14 0x00007efd666ecb62 in QtPrivate::QSlotObjectBase::call (a=0x7ffedfcf3ef0, r=<optimized out>, this=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#15 QSingleShotTimer::timerEvent (this=0x7efd58007150) at kernel/qtimer.cpp:320
#16 0x00007efd666dd26d in QObject::event (this=0x7efd58007150, e=0x7ffedfcf4030) at kernel/qobject.cpp:1369
#17 0x00007efd67362f5e in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x7efd58007150, e=0x7ffedfcf4030) at kernel/qapplication.cpp:3637
#18 0x00007efd666b1718 in QCoreApplication::notifyInternal2 (receiver=0x7efd58007150, event=0x7ffedfcf4030) at kernel/qcoreapplication.cpp:1064
#19 0x00007efd667088b1 in QTimerInfoList::activateTimers (this=0x560d51fed900) at kernel/qtimerinfo_unix.cpp:643
#20 0x00007efd66709144 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:183
#21 0x00007efd64c667a9 in g_main_dispatch (context=0x7efd58005010) at ../../../glib/gmain.c:3444
#22 g_main_context_dispatch (context=context@entry=0x7efd58005010) at ../../../glib/gmain.c:4162
#23 0x00007efd64c66a38 in g_main_context_iterate (context=context@entry=0x7efd58005010, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../glib/gmain.c:4238
#24 0x00007efd64c66acc in g_main_context_iteration (context=0x7efd58005010, may_block=1) at ../../../glib/gmain.c:4303
#25 0x00007efd667094b6 in QEventDispatcherGlib::processEvents (this=0x560d51fefb90, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#26 0x00007efd666b019b in QEventLoop::exec (this=this@entry=0x7ffedfcf4270, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#27 0x00007efd666b8306 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#28 0x00007efd66b30ffc in QGuiApplication::exec () at kernel/qguiapplication.cpp:1863
#29 0x00007efd67362ed5 in QApplication::exec () at kernel/qapplication.cpp:2829
#30 0x0000560d51041d0e in main (argc=<optimized out>, argv=<optimized out>) at ./app/main.cpp:188
[Inferior 1 (process 347990) detached]

Reported using DrKonqi
Comment 1 f.kargl 2023-01-03 12:11:06 UTC
Created attachment 154986 [details]
New crash information added by DrKonqi

systemsettings (5.26.4) using Qt 5.15.7

Was able to reproduce this again when trying to set a new display layout

-- Backtrace (Reduced):
#6  QSharedPointer<KScreen::Screen>::data (this=<optimized out>) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qsharedpointer_impl.h:301
#7  QSharedPointer<KScreen::Screen>::operator-> (this=<optimized out>) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qsharedpointer_impl.h:307
#8  KScreen::Config::clone (this=0x0) at ./src/config.cpp:204
#9  0x00007f8323563d1e in ConfigHandler::updateInitialData (this=0x55ecd69964d0) at ./kcm/config_handler.cpp:77
#10 0x00007f8323565c5f in operator() (__closure=0x55ecd69c18d0) at ./kcm/kcm.cpp:192
Comment 2 Nate Graham 2023-01-09 18:33:07 UTC

*** This bug has been marked as a duplicate of bug 461581 ***