Created attachment 107358 [details] kscreenlocker strace I'm using Plasma 5.10.4 on a Gentoo based distribution Sabayon Linux. strace attached. Linux CtrlZ 4.11.0-sabayon #1 SMP Wed Jul 26 12:57:06 UTC 2017 x86_64 AMD A10-7850K Radeon R7, 12 Compute Cores 4C+8G AuthenticAMD GNU/Linux jcfrosty@CtrlZ ~ $ lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) I/O Memory Management Unit 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] 00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri HDMI/DP Audio Controller 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1424 00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1425 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1424 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Port 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1424 00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 09) 00:10.1 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 09) 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 40) 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11) 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11) 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11) 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11) 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 16) 00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD] FCH IDE Controller 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller (rev 01) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 11) 00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] FCH PCI Bridge (rev 40) 00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11) 00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Hudson PCI to PCI bridge (PCIE port 0) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 5 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Fiji [Radeon R9 FURY / NANO Series] (rev ca) 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Fiji HDMI/DP Audio [Radeon R9 Nano / FURY/FURY X] 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) 04:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
Could you please run kscreenlocker_greet through Feb and attach the backtrace?
Yeah, I'm fighting to use gdb right now. Wish I understood what I was doing more... I'll get it to you as soon as I can. I can definitely say this issue didn't exist in plasma 5.9.5 .
jcfrosty@CtrlZ ~ $ sudo coredumpctl gdb /usr/lib64/libexec/kscreenlocker_greet PID: 4124 (kscreenlocker_g) UID: 1002 (jcfrosty) GID: 1003 (jcfrosty) Signal: 11 (SEGV) Timestamp: Fri 2017-08-18 22:53:22 CDT (13h ago) Command Line: /usr/lib64/libexec/kscreenlocker_greet --testing Executable: /usr/lib64/libexec/kscreenlocker_greet Control Group: /user.slice/user-1002.slice/session-1.scope Unit: session-1.scope Slice: user-1002.slice Session: 1 Owner UID: 1002 (jcfrosty) Boot ID: 09af5c1a0b714138a3c9edf3caff684f Machine ID: f812d2ab6856476f95d56e868635927b Hostname: CtrlZ Storage: /var/lib/systemd/coredump/core.kscreenlocker_g.1002.09af5c1a0b714138a3c9edf3caff684f.4124.1503114802000000.lz4 Message: Process 4124 (kscreenlocker_g) of user 1002 dumped core. GNU gdb (Gentoo 7.12.1 vanilla) 7.12.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://bugs.gentoo.org/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/lib64/libexec/kscreenlocker_greet...Reading symbols from /usr/lib64/debug//usr/lib64/libexec/kscreenlocker_greet.debug...(no debugging symbols found)...done. (no debugging symbols found)...done. warning: core file may not match specified executable file. [New LWP 4124] [New LWP 4127] [New LWP 4128] [New LWP 4131] [New LWP 4132] [New LWP 4135] [New LWP 4125] [New LWP 4129] [New LWP 4130] [New LWP 4134] [New LWP 4133] Core was generated by `/usr/lib64/libexec/kscreenlocker_greet --testing'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f6fee2f732b in ?? () [Current thread is 1 (LWP 4124)] warning: File "/home/jcfrosty/.gdbinit" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load". To enable execution of this file add add-auto-load-safe-path /home/jcfrosty/.gdbinit line to your configuration file "/root/.gdbinit". To completely disable this security protection add set auto-load safe-path / line to your configuration file "/root/.gdbinit". For more information about this security protection see the "Auto-loading safe path" section in the GDB manual. E.g., run from the shell: info "(gdb)Auto-loading safe path" (gdb) run --testing Starting program: /usr/lib64/libexec/kscreenlocker_greet --testing [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7fffe5b12700 (LWP 25109)] QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' [New Thread 0x7fffd5343700 (LWP 25111)] [New Thread 0x7fffd4a01700 (LWP 25112)] [New Thread 0x7fffd3ffb700 (LWP 25113)] [New Thread 0x7fffd37fa700 (LWP 25114)] [New Thread 0x7fffd2ff9700 (LWP 25115)] [New Thread 0x7fffd27f8700 (LWP 25116)] [New Thread 0x7fffd1ff7700 (LWP 25117)] [New Thread 0x7fffd17f6700 (LWP 25118)] [Thread 0x7fffd17f6700 (LWP 25118) exited] [New Thread 0x7fffd17f6700 (LWP 25119)] [New Thread 0x7fffd0ff5700 (LWP 25125)] QObject: Cannot create children for a parent that is in a different thread. (Parent is ScreenLocker::UnlockApp(0x7fffffffe170), parent's thread is QThread(0x622450), current thread is QThread(0x699cf0) QObject::installEventFilter(): Cannot filter events for objects in a different thread. QObject: Cannot create children for a parent that is in a different thread. (Parent is ScreenLocker::UnlockApp(0x7fffffffe170), parent's thread is QThread(0x622450), current thread is QThread(0x699cf0) org.kde.kcoreaddons: Failed to establish shared memory mapping, will fallback to private memory -- memory usage will increase QObject: Cannot create children for a parent that is in a different thread. (Parent is ScreenLocker::UnlockApp(0x7fffffffe170), parent's thread is QThread(0x622450), current thread is QThread(0x699cf0) QObject::installEventFilter(): Cannot filter events for objects in a different thread. No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" [New Thread 0x7fffc235e700 (LWP 25126)] No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" Locked at 1503162656 No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" No metadata file in the package, expected it at: "/usr/share/backgrounds/" [New Thread 0x7fffc0fd6700 (LWP 25127)] Thread 1 "kscreenlocker_g" received signal SIGSEGV, Segmentation fault. 0x00007fffdf3c6697 in st_update_framebuffer_state () from /usr/lib64/dri/radeonsi_dri.so (gdb) backtrace #0 0x00007fffdf3c6697 in st_update_framebuffer_state () from /usr/lib64/dri/radeonsi_dri.so #1 0x00007fffdf3c544c in st_validate_state () from /usr/lib64/dri/radeonsi_dri.so #2 0x00007fffdf3ccbec in st_Clear () from /usr/lib64/dri/radeonsi_dri.so #3 0x00007ffff5f24da6 in QSGBatchRenderer::Renderer::renderBatches() () from /usr/lib64/libQt5Quick.so.5 #4 0x00007ffff5f2a889 in QSGBatchRenderer::Renderer::render() () from /usr/lib64/libQt5Quick.so.5 #5 0x00007ffff5f35e8c in QSGRenderer::renderScene(QSGBindable const&) () from /usr/lib64/libQt5Quick.so.5 #6 0x00007ffff5f3650b in QSGRenderer::renderScene(unsigned int) () from /usr/lib64/libQt5Quick.so.5 #7 0x00007ffff5f4577e in QSGRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () from /usr/lib64/libQt5Quick.so.5 #8 0x00007ffff5f8d8bd in QQuickWindowPrivate::renderSceneGraph(QSize const&) () from /usr/lib64/libQt5Quick.so.5 #9 0x00007ffff5f5be26 in ?? () from /usr/lib64/libQt5Quick.so.5 #10 0x00007ffff5f5ce10 in ?? () from /usr/lib64/libQt5Quick.so.5 #11 0x00007ffff54f1bca in QWindow::event(QEvent*) () from /usr/lib64/libQt5Gui.so.5 #12 0x00007ffff5f98a75 in QQuickWindow::event(QEvent*) () from /usr/lib64/libQt5Quick.so.5 #13 0x00007ffff51bb975 in ?? () from /usr/lib64/libQt5Core.so.5 #14 0x00007ffff51bbad8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #15 0x00007ffff54e7f39 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () from /usr/lib64/libQt5Gui.so.5 #16 0x00007ffff54e8a5d in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib64/libQt5Gui.so.5 #17 0x00007ffff54caad3 in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Gui.so.5 #18 0x00007fffe7e9de80 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #19 0x00007ffff0d9185d in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #20 0x00007ffff0d91b08 in ?? () from /usr/lib64/libglib-2.0.so.0 #21 0x00007ffff0d91bac in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #22 0x00007ffff5203b07 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #23 0x00007ffff51ba89a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #24 0x00007ffff51c1f6d in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #25 0x000000000040982d in main ()
From the backtrace it looks like a crash in radeon driver called from Qt. Could it be that you also updated either Qt or driver or kernel?
All we did is upgraded plasma 5.9.5 to 5.10.4 Intel is also affected. I'm part of the Sabayon Linux software testing team. We've located the issue. It's 100% with DRI3. Once we downgrade to DRI2. Everything works in both Intel and AMD graphics cards. DRI3 isn't compatible. This is bad as it disables vulkan for open source drivers. KDE+gaming is a no go at this point.
OK, so we need to figure out what is different in your distribution to all other distributions. Obvious things first: this works on other distributions. KScreenlocker saw some changes in Plasma 5.10, but no other distro reported issues with it. I sent detailed instructions to the kde distributions mailing list about the changes involved. Please verify that all (optional) build dependencies are installed. Please attach an output of the cmake run. Most importantly to verify: is the seccomp dependency found and does this work on your distribution? Are you using the default lock screen theme or a custom one? If a custom one: does the problem also happen with the default theme? If not please attach the custom theme.
Created attachment 107407 [details] machine overview View of GCC, mesa, kernel, kscreenlocker USE flags and compile output.
There are 2 ways to work around this problem: 1. use -seccomp USE flag at compile time 2. disable DRI3 1. removes seccomp flag, but keeps DRI3 and Vulkan and fixes both Intel and AMD 2. removes vulkan and DRI3 but keeps seccomp flag and fixes both Intel and AMD Issue affects both Mesa 17.1.5 and Mesa 17.2.0-rc4
Better disable seccomp than dri3. Nevertheless I would like to figure out what is different in the case of Sabayon. We shipped 5.10 in June and this is the first report of it not working. Other distributions also use seccomp and DRI3. So again: do you use the default theme?
Created attachment 107412 [details] attachment-8587-0.html Yes, both default and custom have the issue. I've even wiped out all KDE settings and started over only to see the same issue. On Sun, Aug 20, 2017, 12:07 PM Martin Flöser <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=383681 > > --- Comment #9 from Martin Flöser <mgraesslin@kde.org> --- > Better disable seccomp than dri3. > > Nevertheless I would like to figure out what is different in the case of > Sabayon. We shipped 5.10 in June and this is the first report of it not > working. Other distributions also use seccomp and DRI3. > > So again: do you use the default theme? > > -- > You are receiving this mail because: > You reported the bug.
This seems to work on openSUSE Tumbleweed - we did not get any complaints so far. Could you please compare whether there are differences in how packages like e.g. Mesa are compiled? There must be an important difference. We need to figure out what it is.
appears related to this? https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org/thread/P3GKSSLCV2YZT4UTFDHCP6S4CQ453J35/
I can't seem to find a way to see what flags were used to compile Suse Tumbleweed's packages..
(In reply to Jerrod Frost from comment #12) > appears related to this? > > https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org/ > thread/P3GKSSLCV2YZT4UTFDHCP6S4CQ453J35/ No, that's about the xorg Intel driver. Nobody uses this nowadays, everyone is on modesettings.
I can confirm that this does not appear to affect TW, at least I haven't heard of any cases nor experienced it myself. We're currently on Qt 5.9.1, Plasma 5.10.4, X.org 1.19.3 and Mesa 17.1.6. (In reply to Jerrod Frost from comment #13) > I can't seem to find a way to see what flags were used to compile Suse > Tumbleweed's packages.. For some reason the full package build logs on OBS are only available to logged-in users, so I'll dump some flags here. Qt Core: ./configure -prefix /usr -L /usr/lib64 -libdir /usr/lib64 -archdatadir /usr/lib64/qt5 -bindir /usr/lib64/qt5/bin -datadir /usr/share/qt5 -docdir /usr/share/doc/packages/qt5 -examplesdir /usr/lib64/qt5/examples -headerdir /usr/include/qt5 -importdir /usr/lib64/qt5/imports -libexecdir /usr/lib64/qt5/libexec -plugindir /usr/lib64/qt5/plugins -sysconfdir /etc/xdg -translationdir /usr/share/qt5/translations -verbose -reduce-relocations -optimized-qmake -accessibility -no-strip -opensource -no-separate-debug-info -shared -xkb -system-xkbcommon -dbus-linked -sm -no-rpath -system-libjpeg -openssl-linked -system-libpng -system-harfbuzz -fontconfig -system-freetype -cups -system-zlib -no-pch -glib -system-sqlite -no-sql-mysql -no-strip -libproxy -xcb -egl -eglfs -opengl desktop -release -plugin-sql-sqlite -nomake tests -plugin-sql-psql -I/usr/include/pgsql/ -I/usr/include/pgsql/server -plugin-sql-odbc -plugin-sql-mysql -I/usr/include/mysql/ -v Mesa: ./configure --host=x86_64-suse-linux-gnu --build=x86_64-suse-linux-gnu --program-prefix= --disable-dependency-tracking --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/lib --localstatedir=/var --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info --disable-dependency-tracking --enable-libglvnd --enable-gles1 --enable-gles2 --enable-dri --with-platforms=x11,drm,wayland --enable-shared-glapi --enable-texture-float --enable-osmesa --enable-dri3 --enable-nine --enable-gbm --enable-glx-tls --enable-opencl --enable-opencl-icd --with-dri-searchpath=/usr/lib64/dri --enable-llvm --enable-llvm-shared-libs --enable-vdpau --enable-va --enable-xvmc --with-vulkan-drivers=intel,radeon --enable-xa --with-dri-drivers=i915,i965,nouveau,r200,radeon --with-gallium-drivers=r300,r600,radeonsi,nouveau,swrast,svga,virgl 'CFLAGS=-fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -g -DNDEBUG' kscreenlocker: cmake -DCMAKE_BUILD_TYPE=None -DKDE_INSTALL_USE_QT_SYS_PATHS=OFF '-DCMAKE_C_FLAGS=-fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -DNDEBUG' '-DCMAKE_CXX_FLAGS=-fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -DNDEBUG' '-DCMAKE_EXE_LINKER_FLAGS=-Wl,--as-needed -Wl,--no-undefined -Wl,-Bsymbolic-functions' '-DCMAKE_MODULE_LINKER_FLAGS=-Wl,--as-needed -Wl,--no-undefined -Wl,-Bsymbolic-functions' '-DCMAKE_SHARED_LINKER_FLAGS=-Wl,--as-needed -Wl,--no-undefined -Wl,-Bsymbolic-functions' -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_PREFIX_PATH=/usr -DKDE_INSTALL_LIBDIR=lib64 -DKDE_INSTALL_SYSCONFDIR=/etc -DKDE_INSTALL_QTPLUGINDIR=lib64/qt5/plugins -DKDE_INSTALL_PLUGINDIR=lib64/qt5/plugins -DKDE_INSTALL_QMLDIR=lib64/qt5/qml -DKDE_INSTALL_QTQUICKIMPORTSDIR=lib64/qt5/imports -DECM_MKSPECS_INSTALL_DIR=/usr/lib64/qt5/mkspecs/modules -DKDE_INSTALL_METAINFODIR=/usr/share/metainfo -DBUILD_TESTING=OFF .. -DKDE4_COMMON_PAM_SERVICE=xdm -DCMAKE_INSTALL_LOCALEDIR=/usr/share/locale/kf5 LLVM is built with LTO, but that shouldn't matter. The common CFLAGS are "-fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -DNDEBUG" The biggest difference is proabably the version of GCC. In TW we're currently using 7.1.1, while you're still on GCC 4.9.3. There are quite a few users of Plasma 5.10.4 on Leap 42.3 however, which has older GCC (4.8), Mesa and X and doesn't seem to be affected either, or at least not that badly. Can you provide a backtrace of the crash on intel (with modesetting)?
I'm not the one with the intel card, thats another member. I only have AMD cards and one old nvidia (nouveau) card.
I am running KDE neon and got the same issue after upgrading to nvidia-384. When I downgrade to nvidia-375 everything works fine. Unfortunately, I need nvidia-384, because cuda depends on it. Here is the backtrace from the core dump: Thread 5 (Thread 0x7fffd4af4700 (LWP 5059)): #0 0x00007fffdee12892 in ?? () from /usr/lib/nvidia-384/libnvidia-glcore.so.384.66 #1 0x00007fffdf0d483a in ?? () from /usr/lib/nvidia-384/libnvidia-glcore.so.384.66 #2 0x00007fffdefa0fda in ?? () from /usr/lib/nvidia-384/libnvidia-glcore.so.384.66 #3 0x00007fffdefb6ed4 in ?? () from /usr/lib/nvidia-384/libnvidia-glcore.so.384.66 #4 0x00007fffdefa57ce in ?? () from /usr/lib/nvidia-384/libnvidia-glcore.so.384.66 #5 0x00007ffff5f0b681 in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x00007ffff5f0bf8d in QSGBatchRenderer::Renderer::renderBatches() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x00007ffff5f11909 in QSGBatchRenderer::Renderer::render() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x00007ffff5f0209f in QSGRenderer::renderScene(QSGBindable const&) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x00007ffff5f0257b in QSGRenderer::renderScene(unsigned int) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x00007ffff5f3dd2e in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x00007ffff5f97b04 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x00007ffff5f4715e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x00007ffff5f4b8dc in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x00007ffff4e28989 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x00007ffff39966ba in start_thread (arg=0x7fffd4af4700) at pthread_create.c:333 #16 0x00007ffff47353dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fffe4f2b700 (LWP 5058)): ---Type <return> to continue, or q <return> to quit--- #0 0x00007ffff472970d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007ffff122b38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007ffff122b49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007ffff505192f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x00007ffff4ffa7ca in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00007ffff4e23cd4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x00007ffff5c7d0c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x00007ffff4e28989 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x00007ffff39966ba in start_thread (arg=0x7fffe4f2b700) at pthread_create.c:333 #9 0x00007ffff47353dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fffe572c700 (LWP 5052)): #0 0x00007ffff472970d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007ffff122b38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007ffff122b49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007ffff505192f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x00007ffff4ffa7ca in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00007ffff4e23cd4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x00007ffff7f42b75 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x00007ffff4e28989 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x00007ffff39966ba in start_thread (arg=0x7fffe572c700) at pthread_create.c:333 ---Type <return> to continue, or q <return> to quit--- #9 0x00007ffff47353dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fffe7901700 (LWP 5050)): #0 0x00007ffff472970d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007ffff41c9c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x00007ffff41cb8d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x00007fffeaccb329 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x00007ffff4e28989 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00007ffff39966ba in start_thread (arg=0x7fffe7901700) at pthread_create.c:333 #6 0x00007ffff47353dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fffeb2268c0 (LWP 5045)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007ffff4e298eb in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x00007ffff5f48355 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x00007ffff5f4a51e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x00007ffff5f4ab73 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x00007ffff53f9fc5 in QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #6 0x00007ffff5fa1f45 in QQuickWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x00007ffff4ffc63a in QCoreApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x00007ffff4ffc798 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 ---Type <return> to continue, or q <return> to quit--- #9 0x00007ffff53eeced in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #10 0x00007ffff53ef91d in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #11 0x00007ffff53c9ceb in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #12 0x00007fffead29e00 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #13 0x00007ffff122b197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x00007ffff122b3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x00007ffff122b49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x00007ffff505192f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x00007ffff4ffa7ca in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x00007ffff5003704 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x00000000004097ca in ?? () #20 0x00007ffff464e830 in __libc_start_main (main=0x409000, argc=2, argv=0x7fffffffe5d8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffe5c8) at ../csu/libc-start.c:291 #21 0x0000000000409a29 in _start ()
@Markus: your issue is different. Many applications started to crash with that driver update with similar backtrace as yours. But it's clearly a different issue! We can see this that your system crashed in Thread 5 and not in Thread 1.
Ok, I only noticed crashes of kscreenlocker. Everything else is working fine so far, so I assumed that this is related to this bug. Do you know if there is already an open issue or should I create a new one? Is this a kde or a nvidia issue?
(In reply to Markus Heß from comment #19) > Ok, I only noticed crashes of kscreenlocker. Everything else is working fine > so far, so I assumed that this is related to this bug. Do you know if there > is already an open issue or should I create a new one? Is this a kde or a > nvidia issue? The crash is in the nvidia driver and you updated nvidia -> nvidia.
Thank you for the crash report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
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!
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!