Application: systemsettings (5.27.0) Qt Version: 5.15.8 Frameworks Version: 5.102.0 Operating System: Linux 5.15.0-60-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.0 [KCrashBackend] -- Information about the crash: I'm on a Samsung G9 monitor and the display became staggerd every couple hundred pixels. It looked like it would paint a small rectangle, then move down and over 1 unit and then paint the next rectangle of the same size and repeat. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x00007f50b83c4dcb in KScreen::Config::outputs() const () from /lib/x86_64-linux-gnu/libKF5Screen.so.8 #5 0x00007f50b841886a in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_kscreen.so #6 0x00007f50b84189c6 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_kscreen.so #7 0x00007f5119650ade in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x00007f511a242793 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x00007f511962307a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x00007f5119626167 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x00007f511967d487 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x00007f5117cc7d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x00007f5117d1c6c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x00007f5117cc53e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x00007f511967cad8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x00007f511962199b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x00007f5119629f34 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x000056489b4f65f6 in ?? () #19 0x00007f5118f3ed90 in __libc_start_call_main (main=main@entry=0x56489b4f5aa0, argc=argc@entry=1, argv=argv@entry=0x7ffe84526b38) at ../sysdeps/nptl/libc_start_call_main.h:58 #20 0x00007f5118f3ee40 in __libc_start_main_impl (main=0x56489b4f5aa0, argc=1, argv=0x7ffe84526b38, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffe84526b28) at ../csu/libc-start.c:392 #21 0x000056489b4f6f85 in ?? () [Inferior 1 (process 9978) detached] Reported using DrKonqi
Created attachment 156474 [details] Picture of what the display renders
So to be clear, the system is working fine, then you do something to make System Settings crash, and when it crashes, this also happens? Do I have that right? What specifically is the thing you do to make this happen?
(In reply to Nate Graham from comment #2) > So to be clear, the system is working fine, then you do something to make > System Settings crash, and when it crashes, this also happens? Do I have > that right? > > What specifically is the thing you do to make this happen? Apologies for the missing info. This happened when trying to change the resolution of the monitor from 3840x1080 to 5120x1440 on my monitor (Samsung G9). This happened consistently when switching to that resolution (picture attached above). I'm new to KDE and Linux as a whole, so I'm not entirely sure how to begin debugging on my end for this stuff.
Thanks! *** This bug has been marked as a duplicate of bug 464707 ***
(In reply to Nate Graham from comment #4) > Thanks! > > *** This bug has been marked as a duplicate of bug 464707 *** This seemingly may be related to 464707, but after upgrading to 5.27.1, my issue is still persisting. There's a picture attached here that shows what's happening to my screen when I change the resolution to 5120x1440. It doesn't seem to happen with changing the resolution to any other option.
Bug 464707 is fixed in 5.27.2, not 5.27.1. Can you try again once it's released tomorrow? If the issue is still not fixed, feel free to re-open this bug report and un-mark it as a duplicate of Bug 464707. Thanks!
*** This bug has been marked as a duplicate of bug 464707 ***
This is still an issue after upgrading to 5.27.2. It may be a matter of the backtrace coinciding with the issue I'm getting, but the image shows the screen tearing that I'm seeing when I switch to 5120x1440resolution.
Well darn. Thanks for following up!
(In reply to Nate Graham from comment #9) > Well darn. Thanks for following up! What's something I can do to help with debugging this? I'm super new to Linux, so I'm not entirely sure where to really begin.
This looks like a driver bug; I've had similar glitches happen before on Xorg with my Samsung CRG9. Can you try the Wayland session?
(In reply to Zamundaaa from comment #11) > This looks like a driver bug; I've had similar glitches happen before on > Xorg with my Samsung CRG9. Can you try the Wayland session? Not sure if this is how you meant, but I found [this site](https://blog.martin-graesslin.com/blog/2016/05/running-plasma-wayland-on-kde-neon/) and ran `sudo apt install plasma-workspace-wayland` in order to allow me to select which compositor to use on bootup. When I logged in with Wayland, the entire experience was borderline unusable. It took about five to seven seconds for the UI/mouse position to update and mouse events to register. If there's another way to switch to Wayland, please let me know.
(In reply to Zamundaaa from comment #11) > This looks like a driver bug; I've had similar glitches happen before on > Xorg with my Samsung CRG9. Can you try the Wayland session? Seems like this is the problem. I installed the new drivers and it's all working fine now. Thanks for the help!