[kwin] [Bug 402827] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=402827 --- Comment #28 from JordanL --- I can't reproduce it (since returning to Plasma Wayland with 5.22.5), however I did replace my monitors with new ones which have far fewer issues with this sort of thing than my previous ones. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374908] Dual monitors: when screen resumes, windows are rearranged on second monitor
https://bugs.kde.org/show_bug.cgi?id=374908 JordanL changed: What|Removed |Added CC|jordanlepp...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443545] System monitor Sensor can't show more than 18 bars.
https://bugs.kde.org/show_bug.cgi?id=443545 JordanL changed: What|Removed |Added Assignee|plasma-b...@kde.org |k...@davidedmundson.co.uk Component|Panel |general CC||plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443545] System monitor Sensor can't show more than 18 bars.
https://bugs.kde.org/show_bug.cgi?id=443545 --- Comment #1 from JordanL --- Created attachment 142296 --> https://bugs.kde.org/attachment.cgi?id=142296=edit When there are only 18 bars -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443545] New: System monitor Sensor can't show more than 18 bars.
https://bugs.kde.org/show_bug.cgi?id=443545 Bug ID: 443545 Summary: System monitor Sensor can't show more than 18 bars. Product: plasmashell Version: 5.22.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: jordanlepp...@gmail.com Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. Add the "Individual Core Usage" widget to the panel, when you have 32 logical cores (16 physical with hyperthreading - 5950X) OBSERVED RESULT Nothing is visible at all for the widget. If I manually remove cores from the sensors, I can see bars when I get down to 18 cores total. The bars are very thin and unnecessarily spread out, looks like 8 pixels space in between each bar. EXPECTED RESULT Bars should be visible, and closer together. Ideally it would be configurable how many pixels thick the bars and spaces were. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Using Wayland on Opensuse Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370180] Widgets moved to secondary monitor or disappear upon reconnect
https://bugs.kde.org/show_bug.cgi?id=370180 JordanL changed: What|Removed |Added CC|jordanlepp...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422426] Implement Wayland Primary Selection Protocol bridge with XWayland
https://bugs.kde.org/show_bug.cgi?id=422426 JordanL changed: What|Removed |Added CC|jordanlepp...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422426] Implement Wayland Primary Selection Protocol bridge with XWayland
https://bugs.kde.org/show_bug.cgi?id=422426 JordanL changed: What|Removed |Added CC||jordanlepp...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370180] Widgets moved to secondary monitor upon reboot
https://bugs.kde.org/show_bug.cgi?id=370180 --- Comment #13 from JordanL --- I'm not experiencing it on reboot. Only when the screens turn off and back on. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377561] Panels switched after screen switched off
https://bugs.kde.org/show_bug.cgi?id=377561 --- Comment #12 from JordanL --- More relevant info: I have two 4k monitors connected with DisplayPort 1.2. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377561] Panels switched after screen switched off
https://bugs.kde.org/show_bug.cgi?id=377561 --- Comment #11 from JordanL --- For me though, the panels aren't so much switched, but both screens show the window list for the right hand desktop (I have the window list setup to show windows on the current screen). Both my panels are identical so I can't tell if the whole panel has been duplicated. I'm getting around this by having a constant python script running in the background that detects when the screens have been switched off and back on, and automatically restarts Plasma. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377561] Panels switched after screen switched off
https://bugs.kde.org/show_bug.cgi?id=377561 --- Comment #10 from JordanL --- Yes, this is happening with: Plasma 5.16.5 KDE Frameworks 5.62.0 Qt 5.13.1 I'm using an AMD Vega 64 GPU and running Arch. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 373907] Implement Wayland Primary Selection Protocol (middle-click paste)
https://bugs.kde.org/show_bug.cgi?id=373907 JordanL changed: What|Removed |Added CC||jordanlepp...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404152] Support for pointer_axis_discrete needed
https://bugs.kde.org/show_bug.cgi?id=404152 --- Comment #10 from JordanL --- Certainly not enough to provide a competent review of Kwin code unfortunately. I've checked out the Kwin repo anyway to see if I might familiarise myself with it enough to offer patches for some issues I can reproduce. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404152] Support for pointer_axis_discrete needed
https://bugs.kde.org/show_bug.cgi?id=404152 --- Comment #7 from JordanL --- I understand it's important for problems to be fixed properly rather than hastily, and I don't want to sound impatient, but is it normal for a fix like this to be under review for nearly two months? Having buggy scrolling in a lot of apps is at least a moderate usability hindrance. I'd just feel a tad better if I knew the fix was on its way :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404152] Support for pointer_axis_discrete needed
https://bugs.kde.org/show_bug.cgi?id=404152 JordanL changed: What|Removed |Added CC||jordanlepp...@gmail.com --- Comment #5 from JordanL --- This is still happening in Plasma/Wayland 5.15.3 (KF 5.56.0) in Chrome and Minecraft (not tested Firefox). It's not happening in Konsole, so appears to be happening to Xwayland apps. I'm on Xorg 1.20.4. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402827] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=402827 JordanL changed: What|Removed |Added Version|5.14.4 |5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402827] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=402827 --- Comment #20 from JordanL --- Just retested on Arch with Plasma 5.15.0, KDE frameworks 5.55.0, Qt 5.12.1, same hardware as before. Bug is still present, when monitors turn off due to power saving. kwin_wayland dumps core. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402827] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=402827 --- Comment #18 from JordanL --- Well that's progress at least, I might be able to use the Wayland session full time if so. Could you get the backtrace from the segfault when you turn the monitor off? In case it's different? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402827] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=402827 --- Comment #14 from JordanL --- "svn patch" would't play ball, so I manually applied the patch to 5.14.4 and rebuilt. The issue still occurs. The backtrace is different though, so I think this is progress. The backtrace differs from #8 onwards as far as I can see. Thread 1 (Thread 0x7fe8a331e440 (LWP 1160)): #0 0x7fe8ab0dfc70 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:28 #1 0x7fe8ab0ca672 in __GI_abort () at abort.c:79 #2 0x7fe8ab4ab7fc in () at /usr/lib/libQt5Core.so.5 #3 0x7fe8ab4aac83 in () at /usr/lib/libQt5Core.so.5 #4 0x7fe8a13b170e in QVector::at(int) const () at /usr/lib/qt/plugins/org.kde.kwin.waylandbackends/KWinWaylandDrmBackend.so #5 0x7fe8a13b170e in KWin::EglGbmBackend::prepareRenderingForScreen(int) (this=, screenId=) at /usr/src/debug/kwin-5.14.4/plugins/platforms/drm/egl_gbm_backend.cpp:342 #6 0x7fe8a034970e in KWin::SceneOpenGL::paint(QRegion, QList) (this=this@entry=0x55db40fa39a0, damage=..., toplevels=...) at /usr/src/debug/kwin-5.14.4/plugins/scenes/opengl/scene_opengl.cpp:663 #7 0x7fe8ac4897de in KWin::Compositor::performCompositing() (this=0x55db40989f30) at /usr/src/debug/kwin-5.14.4/composite.cpp:745 #8 0x7fe8ab6ccb1b in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #9 0x7fe8abaade34 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #10 0x7fe8abab5671 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #11 0x7fe8ab6a18f9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #12 0x7fe8ab6f6955 in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #13 0x7fe8ab6f4a9e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #14 0x7fe8a30198be in QUnixEventDispatcherQPA::processEvents(QFlags) () at /usr/lib/qt/plugins/platforms/KWinQpaPlugin.so #15 0x7fe8ab6a058c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #16 0x7fe8ab6a8896 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #17 0x55db3f62d852 in main(int, char**) (argc=, argv=) at /usr/src/debug/kwin-5.14.4/main_wayland.cpp:807 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402827] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=402827 --- Comment #13 from JordanL --- I'll attempt to test this patch, any info you can point me to to help me rebuild kwin with it? Worst case I could manually apply the changes in the src and rebuild but I'm sure there's a quicker way! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402827] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=402827 --- Comment #9 from JordanL --- Attached a new log, "Log of all threads before raise is called". This is a backtrace of all kwin threads at the point it called raise(). I believe thread 1 is the thread that is relevant here: Thread 1 (Thread 0x7f6809ac7440 (LWP 3559)): #0 0x7f6811888c70 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:28 #1 0x7f6811873672 in __GI_abort () at abort.c:79 #2 0x7f6811c547fc in () at /usr/lib/libQt5Core.so.5 #3 0x7f6811c53c83 in () at /usr/lib/libQt5Core.so.5 #4 0x7f6807b5a70e in QVector::at(int) const () at /usr/lib/qt/plugins/org.kde.kwin.waylandbackends/KWinWaylandDrmBackend.so #5 0x7f6807b5a70e in KWin::EglGbmBackend::prepareRenderingForScreen(int) (this=, screenId=) at /usr/src/debug/kwin-5.14.4/plugins/platforms/drm/egl_gbm_backend.cpp:342 #6 0x7f68072f370e in KWin::SceneOpenGL::paint(QRegion, QList) (this=this@entry=0x55f28420b560, damage=..., toplevels=...) at /usr/src/debug/kwin-5.14.4/plugins/scenes/opengl/scene_opengl.cpp:663 #7 0x7f6812c327de in KWin::Compositor::performCompositing() (this=0x7f67f800ae50) at /usr/src/debug/kwin-5.14.4/composite.cpp:745 #8 0x7f68087db705 in drmHandleEvent () at /usr/lib/libdrm.so.2 #9 0x7f6807b5b09a in KWin::DrmBackendoperator() (__closure=) at /usr/src/debug/kwin-5.14.4/plugins/platforms/drm/drm_backend.cpp:270 #10 0x7f6807b5b09a in QtPrivate::FunctorCall, QtPrivate::List<>, void, KWin::DrmBackend::openDrm():: >::call (arg=, f=...) at /usr/include/qt/QtCore/qobjectdefs_impl.h:146 #11 0x7f6807b5b09a in QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/qt/QtCore/qobjectdefs_impl.h:256 #12 0x7f6807b5b09a in QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=, ret=) at /usr/include/qt/QtCore/qobjectdefs_impl.h:439 #13 0x7f6811e753e0 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #14 0x7f6811e80eea in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #15 0x7f6811e81242 in QSocketNotifier::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #16 0x7f6812256e34 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #17 0x7f681225e671 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #18 0x7f6811e4a8f9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #19 0x7f6811e9d710 in QEventDispatcherUNIXPrivate::activateSocketNotifiers() () at /usr/lib/libQt5Core.so.5 #20 0x7f6811e9da19 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #21 0x7f68097c28be in QUnixEventDispatcherQPA::processEvents(QFlags) () at /usr/lib/qt/plugins/platforms/KWinQpaPlugin.so #22 0x7f6811e4958c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #23 0x7f6811e51896 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #24 0x55f282fb8822 in main(int, char**) (argc=, argv=) at /usr/src/debug/kwin-5.14.4/main_wayland.cpp:807 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402827] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=402827 --- Comment #8 from JordanL --- Created attachment 117283 --> https://bugs.kde.org/attachment.cgi?id=117283=edit Log of all threads before raise is called -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402827] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=402827 --- Comment #7 from JordanL --- Debugger log after rebuilding glibc with debug: Continuing. [Detaching after fork from child process 1548] Thread 1 "kwin_wayland" received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 50 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. Detaching from program: /usr/bin/kwin_wayland, process 1158 [Inferior 1 (process 1158) detached] -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402827] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=402827 --- Comment #6 from JordanL --- I worked out how to attach the debugger while kwin_wayland is still running. It throws SIGABRT when calling raise() in /usr/lib/libc.so.6 - so I will now rebuild glibc with debug symbols and see if that gets me anywhere. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402827] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=402827 --- Comment #5 from JordanL --- Created attachment 117281 --> https://bugs.kde.org/attachment.cgi?id=117281=edit New log after rebuilding kwin and mesa with debug symbols -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402827] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=402827 --- Comment #4 from JordanL --- Sorry, even after installing kwin and mesa built with debug symbols, I get no backtrace and have no idea where to go next. I've attached the latest log I get (log4.txt). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402827] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=402827 --- Comment #3 from JordanL --- Seems I also need to rebuild kwin with debug symbols (makes sense!). Think I'm close to having the backtrace now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402827] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=402827 --- Comment #2 from JordanL --- Any idea which (if any) packages I need to rebuild with debug symbols? It looks like I need to rebuild mesa but I'm not 100% sure. $ pacman -Qo /usr/lib/libgbm.so.1.0.0 /usr/lib/libgbm.so.1.0.0 is owned by mesa 18.3.1-1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402827] New: kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=402827 Bug ID: 402827 Summary: kwin_wayland segfault on monitor wakeup Product: kwin Version: 5.14.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: jordanlepp...@gmail.com Target Milestone: --- Created attachment 117266 --> https://bugs.kde.org/attachment.cgi?id=117266=edit System log from crash SUMMARY In Wayland session, when monitors go to sleep due to inactivity, when I wake it up again, kwin_wayland segfaults. STEPS TO REPRODUCE 1. Log into Wayland session 2. Wait for inactivity to cause screens to go to sleep 3. Move mouse / press key OBSERVED RESULT Black screen(s), does not respond to ctrl+alt+f1, have to hard reboot. EXPECTED RESULT Monitors wake up, can carry on using session. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.53.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION Distro: Manjaro Linux Kernel: 4.19.13-1-MANJARO x86_64 CPU: Intel Core i7-5820K GPU: AMD RX Vega 64, using AMDGPU driver Mesa: 18.3.1 Monitors: 2 * 3840x2160@60Hz, connected with DP 1.2 I attached a log from the crash. The log starts when the monitors go to sleep, I pressed a key about 15 seconds later. The relevant part seems to be: Jan 03 14:43:49 rupert kernel: kwin_wayland[15576]: segfault at 1c0 ip 7fd1e312f853 sp 7ffc3f2c1038 error 4 in libgbm.so.1.0.0[7fd1e312f000+6000] Jan 03 14:43:49 rupert kernel: Code: 00 00 00 31 c0 48 83 c4 08 c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 8b 07 ff a0 48 01 00 00 0f 1f 80 00 00 00 00 48 8b 07 a0 30 01 00 00 0f 1f 80 00 00 00 00 48 8b 07 ff a0 38 01 00 00 Jan 03 14:43:49 rupert kernel: audit: type=1701 audit(1546526629.764:79): auid=1000 uid=1000 gid=1001 ses=4 pid=15576 comm="kwin_wayland" exe="/usr/bin/kwin_wayland" sig=11 res=1 Jan 03 14:43:49 rupert systemd[1]: Started Process Core Dump (PID 16033/UID 0). Jan 03 14:43:49 rupert audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@1-16033-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 03 14:43:49 rupert kernel: audit: type=1130 audit(1546526629.781:80): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@1-16033-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' (...) Jan 03 14:43:52 rupert systemd-coredump[16034]: Core file was truncated to 2147483648 bytes. Jan 03 14:43:53 rupert systemd-coredump[16034]: Process 15576 (kwin_wayland) of user 1000 dumped core. Stack trace of thread 15576: #0 0x7fd1e312f853 n/a (n/a) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 400058] kscreenlocker_greet crashes every time
https://bugs.kde.org/show_bug.cgi?id=400058 --- Comment #7 from JordanL --- I too can confirm the issue is fixed since the second batch of Qt updates. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 400058] kscreenlocker_greet crashes every time
https://bugs.kde.org/show_bug.cgi?id=400058 --- Comment #2 from JordanL --- My issue also started today, after the update of Qt to 5.11.2. It happens whether the Plasma or the Plasma Wayland session is selected. I was going to file a bug for SDDM, but couldn't find it (is it not a KDE project?). -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 400058] kscreenlocker_greet crashes every time
https://bugs.kde.org/show_bug.cgi?id=400058 JordanL changed: What|Removed |Added CC||jordanlepp...@gmail.com --- Comment #1 from JordanL --- I have a similar issue. In my case it happens when I click the password field of the greeter screen. I have SDDM configured to auto-login to my user account, so I log out to get back to the login screen first, in case that makes a difference. System:Host: rupert Kernel: 4.15.0-36-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: KDE Plasma 5.14.1 (Qt 5.11.2) Distro: KDE neon User Edition 5.14 Machine: Device: desktop Mobo: MSI model: X99S SLI PLUS (MS-7885) v: 1.0 serial: N/A UEFI: American Megatrends v: 1.E0 date: 06/15/2018 CPU: 6 core Intel Core i7-5820K (-MT-MCP-) arch: Haswell rev.2 cache: 15360 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 39603 clock speeds: max: 3600 MHz 1: 1200 MHz 2: 1200 MHz 3: 1200 MHz 4: 1211 MHz 5: 1204 MHz 6: 1200 MHz 7: 1200 MHz 8: 1200 MHz 9: 1200 MHz 10: 1567 MHz 11: 1207 MHz 12: 1200 MHz Graphics: Card: Advanced Micro Devices [AMD/ATI] Vega [Radeon RX Vega] bus-ID: 05:00.0 Display Server: x11 (X.Org 1.19.6 ) drivers: ati,amdgpu (unloaded: modesetting,fbdev,vesa,radeon) Resolution: 3840x2160@60.00hz, 3840x2160@60.00hz OpenGL: renderer: Radeon RX Vega (VEGA10 / DRM 3.23.0 / 4.15.0-36-generic, LLVM 6.0.0) version: 4.5 Mesa 18.0.5 Direct Render: Yes Audio: Card-1 Advanced Micro Devices [AMD/ATI] Device aaf8 driver: snd_hda_intel bus-ID: 05:00.1 Card-2 Intel C610/X99 series HD Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 Sound: Advanced Linux Sound Architecture v: k4.15.0-36-generic Network: Card: Intel Ethernet Connection (2) I218-V driver: e1000e v: 3.2.6-k port: f020 bus-ID: 00:19.0 IF: eno1 state: up speed: 1000 Mbps duplex: full mac: Drives:HDD Total Size: 500.1GB (29.4% used) ID-1: /dev/sda model: Samsung_SSD_840 size: 500.1GB Partition: ID-1: / size: 457G used: 137G (32%) fs: ext4 dev: /dev/sda2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 35.0C mobo: N/A gpu: 40.0 Fan Speeds (in rpm): cpu: N/A Info: Processes: 279 Uptime: 9 min Memory: 2103.9/11905.9MB Init: systemd runlevel: 5 Gcc sys: 7.3.0 Client: Shell (bash 4.4.191) inxi: 2.3.56 Logs from journalctl: Oct 20 18:07:26 rupert systemd[1]: Started User Manager for UID 117. Oct 20 18:07:26 rupert sddm[903]: Greeter session started successfully Oct 20 18:07:26 rupert sddm-greeter[2148]: High-DPI autoscaling not Enabled Oct 20 18:07:26 rupert sddm-greeter[2148]: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf" Oct 20 18:07:26 rupert sddm-greeter[2148]: Reading from "/usr/share/xsessions/plasma.desktop" Oct 20 18:07:26 rupert sddm-greeter[2148]: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop" Oct 20 18:07:26 rupert sddm-greeter[2148]: Connected to the daemon. Oct 20 18:07:26 rupert sddm[903]: Message received from greeter: Connect Oct 20 18:07:26 rupert sddm-greeter[2148]: Loading file:///usr/share/sddm/themes/breeze/Main.qml... Oct 20 18:07:26 rupert sddm-greeter[2148]: QObject: Cannot create children for a parent that is in a different thread. (Parent is SDDM::GreeterApp(0x7fffa09028f0), parent's thread is QThread(0x560a44709020), current thread is QThread(0x560a449563c0) Oct 20 18:07:26 rupert sddm-greeter[2148]: QObject: Cannot create children for a parent that is in a different thread. (Parent is SDDM::GreeterApp(0x7fffa09028f0), parent's thread is QThread(0x560a44709020), current thread is QThread(0x560a449563c0) Oct 20 18:07:26 rupert sddm-greeter[2148]: QObject: Cannot create children for a parent that is in a different thread. (Parent is SDDM::GreeterApp(0x7fffa09028f0), parent's thread is QThread(0x560a44709020), current thread is QThread(0x560a449563c0) Oct 20 18:07:26 rupert sddm-greeter[2148]: QObject: Cannot create children for a parent that is in a different thread. (Parent is SDDM::GreeterApp(0x7fffa09028f0), parent's thread is QThread(0x560a44709020), current thread is QThread(0x560a449563c0) Oct 20 18:07:26 rupert sddm-greeter[2148]: QObject::installEventFilter(): Cannot filter events for objects in a different thread. Oct 20 18:07:26 rupert sddm-greeter[2148]: QObject: Cannot create children for a parent that is in a different thread. (Parent is SDDM::GreeterApp(0x7fffa09028f0), parent's thread is QThread(0x560a44709020), current thread is QTh
[kwin] [Bug 399564] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=399564 --- Comment #8 from JordanL --- 5.13.* was the first release I tried Wayland in, so this bug might have been around long before that. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399564] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=399564 --- Comment #7 from JordanL --- Should have mentioned, this bug was also present in 5.13.*. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399564] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=399564 --- Comment #3 from JordanL --- (gdb) continue Continuing. [Thread 0x7fc9a17fa700 (LWP 5989) exited] [Thread 0x7fc9a1ffb700 (LWP 5665) exited] [Thread 0x7fc9a27fc700 (LWP 5664) exited] [Thread 0x7fc9a2ffd700 (LWP 5663) exited] [Thread 0x7fc9a37fe700 (LWP 5662) exited] [Thread 0x7fc9a3fff700 (LWP 5661) exited] [Thread 0x7fc9a8b71700 (LWP 5660) exited] [Thread 0x7fc9a9372700 (LWP 5659) exited] [Thread 0x7fc9aa3b5700 (LWP 5658) exited] [Thread 0x7fc9bf7cc700 (LWP 5655) exited] Thread 1 "kwin_wayland" received signal SIGSEGV, Segmentation fault. 0x7fc9d07841c3 in QGuiApplication::primaryScreen() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 (gdb) backtrace #0 0x7fc9d07841c3 in QGuiApplication::primaryScreen() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #1 0x7fc9d083fc1d in qt_defaultDpiX() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #2 0x7fc9d07d2fbf in QImageData::QImageData() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #3 0x7fc9d07d3b6a in QImageData::create(unsigned char*, int, int, int, QImage::Format, bool, void (*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #4 0x7fc9d07d3e22 in QImage::QImage(unsigned char*, int, int, int, QImage::Format, void (*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #5 0x7fc9bedb5eb3 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.waylandbackends/KWinWaylandDrmBackend.so #6 0x7fc9bedac494 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.waylandbackends/KWinWaylandDrmBackend.so #7 0x7fc9bedadddc in KWin::DrmOutput::teardown() () from /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.waylandbackends/KWinWaylandDrmBackend.so #8 0x7fc9bedadeb0 in KWin::DrmOutput::~DrmOutput() () from /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.waylandbackends/KWinWaylandDrmBackend.so #9 0x7fc9bedae039 in KWin::DrmOutput::~DrmOutput() () from /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.waylandbackends/KWinWaylandDrmBackend.so #10 0x7fc9beda443f in KWin::DrmBackend::~DrmBackend() () from /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.waylandbackends/KWinWaylandDrmBackend.so #11 0x7fc9beda4779 in KWin::DrmBackend::~DrmBackend() () from /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.waylandbackends/KWinWaylandDrmBackend.so #12 0x7fc9d769f747 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fc9d76a1a7e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fc9d6ad0615 in __cxa_finalize (d=0x7fc9d7b31960) at cxa_finalize.c:83 #15 0x7fc9d74b0633 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7ffcfb09a380 in ?? () #17 0x7fc9d9dc0b73 in _dl_fini () at dl-fini.c:138 Backtrace stopped: frame did not save the PC (gdb) exit -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399564] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=399564 --- Comment #1 from JordanL --- CORRECTION The system info I posted above was back in the Xorg session, this is the output of inxi -Fxz while using Wayland: System:Host: rupert Kernel: 4.15.0-36-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: KDE Plasma 5.14.0 (Qt 5.11.1) Distro: KDE neon User Edition 5.14 Machine: Device: desktop Mobo: MSI model: X99S SLI PLUS (MS-7885) v: 1.0 serial: N/A UEFI: American Megatrends v: 1.E0 date: 06/15/2018 CPU: 6 core Intel Core i7-5820K (-MT-MCP-) arch: Haswell rev.2 cache: 15360 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 39599 clock speeds: max: 3600 MHz 1: 1732 MHz 2: 1389 MHz 3: 1905 MHz 4: 1248 MHz 5: 2240 MHz 6: 1205 MHz 7: 3057 MHz 8: 1668 MHz 9: 1520 MHz 10: 1320 MHz 11: 2831 MHz 12: 1651 MHz Graphics: Card: Advanced Micro Devices [AMD/ATI] Vega [Radeon RX Vega] bus-ID: 05:00.0 Display Server: wayland (X.Org 1.19.6 ) drivers: ati,amdgpu (unloaded: modesetting,fbdev,vesa,radeon) Resolution: 3840x2160@59.98hz, 3840x2160@59.98hz OpenGL: renderer: Radeon RX Vega (VEGA10 / DRM 3.23.0 / 4.15.0-36-generic, LLVM 6.0.0) version: 4.5 Mesa 18.0.5 Direct Render: Yes Audio: Card-1 Advanced Micro Devices [AMD/ATI] Device aaf8 driver: snd_hda_intel bus-ID: 05:00.1 Card-2 Intel C610/X99 series HD Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 Sound: Advanced Linux Sound Architecture v: k4.15.0-36-generic Network: Card: Intel Ethernet Connection (2) I218-V driver: e1000e v: 3.2.6-k port: f020 bus-ID: 00:19.0 IF: eno1 state: up speed: 1000 Mbps duplex: full mac: Drives:HDD Total Size: 500.1GB (25.6% used) ID-1: /dev/sda model: Samsung_SSD_840 size: 500.1GB Partition: ID-1: / size: 457G used: 120G (28%) fs: ext4 dev: /dev/sda2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 37.0C mobo: N/A gpu: 43.0 Fan Speeds (in rpm): cpu: N/A Info: Processes: 290 Uptime: 56 min Memory: 750.9/11905.9MB Init: systemd runlevel: 5 Gcc sys: 7.3.0 Client: Shell (bash 4.4.191) inxi: 2.3.56 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399564] New: kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=399564
Bug ID: 399564
Summary: kwin_wayland segfault on monitor wakeup
Product: kwin
Version: 5.14.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: jordanlepp...@gmail.com
Target Milestone: ---
SUMMARY
When using the Wayland session on KDE Neon 5.14.0, when the powersaving sends
the monitors to sleep due to inactivity, and I then wake them up again with
mouse/keyboard, kwin crashes.
STEPS TO REPRODUCE
1. Log into Plasma Wayland session
2. Wait for powersaving to send the monitors to sleep
3. Wake up with mouse movement/key press
OBSERVED RESULT
Plasma and KWin are dead. SDDM is still alive. This is in the log (journalctl
-b) at the point it crashes:
Oct 9 15:17:11 rupert kernel: [ 1046.307177] kwin_wayland[4108]: segfault at
561cfae8a5e0 ip 7f68a3ffa1c3 sp 7ffe84cfa4a8 error 4 in
libQt5Gui.so.5.11.1[7f68a3eff000+58d000]
EXPECTED RESULT
Desktop comes back as normal
SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.14.0
KDE Frameworks Version: 5.50.0
Qt Version: 5.11.1
ADDITIONAL INFORMATION
I'm using two 4k monitors connected via DisplayPort 1.2, to an AMD Vega 64
card, using the standard AMDGPU drivers in the 4.15 kernel.
Full system info:
System:Kernel: 4.15.0-36-generic x86_64 bits: 64 gcc: 7.3.0
Desktop: KDE Plasma 5.14.0 (Qt 5.11.1) Distro: KDE neon User Edition
5.14
Machine: Device: desktop Mobo: MSI model: X99S SLI PLUS (MS-7885) v: 1.0
serial: N/A
UEFI: American Megatrends v: 1.E0 date: 06/15/2018
CPU: 6 core Intel Core i7-5820K (-MT-MCP-) arch: Haswell rev.2 cache:
15360 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 39599
clock speeds: max: 3600 MHz 1: 1788 MHz 2: 1837 MHz 3: 1548 MHz 4:
1833 MHz 5: 1779 MHz 6: 1630 MHz
7: 1636 MHz 8: 2441 MHz 9: 1446 MHz 10: 1695 MHz 11: 1757 MHz 12:
1548 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] Vega [Radeon RX Vega] bus-ID:
05:00.0
Display Server: x11 (X.Org 1.19.6 ) drivers: ati,amdgpu (unloaded:
modesetting,fbdev,vesa,radeon)
Resolution: 3840x2160@60.00hz, 3840x2160@60.00hz
OpenGL: renderer: Radeon RX Vega (VEGA10 / DRM 3.23.0 /
4.15.0-36-generic, LLVM 6.0.0)
version: 4.5 Mesa 18.0.5 Direct Render: Yes
Audio: Card-1 Advanced Micro Devices [AMD/ATI] Device aaf8 driver:
snd_hda_intel bus-ID: 05:00.1
Card-2 Intel C610/X99 series HD Audio Controller driver:
snd_hda_intel bus-ID: 00:1b.0
Sound: Advanced Linux Sound Architecture v: k4.15.0-36-generic
Network: Card: Intel Ethernet Connection (2) I218-V driver: e1000e v: 3.2.6-k
port: f020 bus-ID: 00:19.0
IF: eno1 state: up speed: 1000 Mbps duplex: full mac:
Drives:HDD Total Size: 500.1GB (25.6% used)
ID-1: /dev/sda model: Samsung_SSD_840 size: 500.1GB
Partition: ID-1: / size: 457G used: 120G (28%) fs: ext4 dev: /dev/sda2
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 40.0C mobo: N/A gpu: 46.0
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 293 Uptime: 37 min Memory: 2982.1/11905.9MB Init: systemd
runlevel: 5 Gcc sys: 7.3.0
Client: Shell (bash 4.4.191) inxi: 2.3.56
Log:
At the point the powersaving sent monitors to sleep:
Oct 9 15:15:41 rupert kernel: [ 598.515338] [drm] HBR2x4 pass VS=2, PE=0
At the point of wakeup:
Oct 9 15:17:01 rupert CRON[4408]: (root) CMD ( cd / && run-parts --report
/etc/cron.hourly)
Oct 9 15:17:10 rupert kernel: [ 956.797760] [drm] {3840x2160,
4000x@533250Khz}
Oct 9 15:17:10 rupert kernel: [ 1045.725396] [drm] {3840x2160,
4000x@533250Khz}
Oct 9 15:17:10 rupert kernel: [ 1045.732945] [drm] HBR2x4 pass VS=1, PE=1
Oct 9 15:17:10 rupert kernel: [ 1045.745082] [drm] {3840x2160,
4000x@533250Khz}
Oct 9 15:17:10 rupert kernel: [ 1045.759031] [drm] {3840x2160,
4000x@533250Khz}
Oct 9 15:17:11 rupert kernel: [ 1045.766113] [drm] HBR2x4 pass VS=1, PE=1
Oct 9 15:17:11 rupert kernel: [ 1046.307177] kwin_wayland[4108]: segfault at
561cfae8a5e0 ip 7f68a3ffa1c3 sp 7ffe84cfa4a8 error 4 in
libQt5Gui.so.5.11.1[7f68a3eff000+58d000]
Oct 9 15:17:11 rupert sddm-helper[4073]: [PAM] Closing session
Oct 9 15:17:11 rupert sddm-helper[4073]: [PAM] Ended.
Oct 9 15:17:11 rupert sddm[3626]: Auth: sddm-helper exited successfully
Oct 9 15:17:11 rupert sddm[3626]: Greeter stopping...
Oct 9 15:17:11 rupert sddm[3626]: Socket server stopping...
Oct 9 15:17:11 rupert sddm[3626]: Socket server stopped.
Oct 9 15:17:11 rupert sddm[3626]: Display server stopping...
Oct 9 15:17:11 rupert sddm-greeter[4046]: The X11 connection broke: I/O error
(code 1)
Oct 9 15:17:11 rupert systemd[1]: session-22.scope:
[plasmashell] [Bug 394532] Multimonitor - Task Manager lists tasks for wrong screen after screens switched off
https://bugs.kde.org/show_bug.cgi?id=394532 --- Comment #3 from JordanL --- In Plasma 5.13.5 the central bug of this ticket still occurs: The window list of one screen will sometimes list the windows for the other screen after the screens come back on after powersaving. Right now, it's the left screen task manager listing the windows for the right screen. Restarting plasma shell is the only way to fix this. I'm using an AMD Vega 64 card with the default built-in mesa drivers, on KDE Neon 5.13 - based on Bionic. The rest of my system is the same as it was. The other bugs I've reported here are not present, either they were fixed in Plasma recently or they don't occur on AMD cards. $ inxi -Fxz System:Host: ** Kernel: 4.15.0-34-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: KDE Plasma 5.13.5 (Qt 5.11.1) Distro: KDE neon User Edition 5.13 Machine: Device: desktop Mobo: MSI model: X99S SLI PLUS (MS-7885) v: 1.0 serial: N/A UEFI: American Megatrends v: 1.E0 date: 06/15/2018 CPU: 6 core Intel Core i7-5820K (-MT-MCP-) arch: Haswell rev.2 cache: 15360 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 39598 clock speeds: max: 3600 MHz 1: 1200 MHz 2: 1259 MHz 3: 1779 MHz 4: 1199 MHz 5: 1279 MHz 6: 1200 MHz 7: 1200 MHz 8: 1232 MHz 9: 2328 MHz 10: 1200 MHz 11: 1204 MHz 12: 1200 MHz Graphics: Card: Advanced Micro Devices [AMD/ATI] Vega [Radeon RX Vega] bus-ID: 05:00.0 Display Server: x11 (X.Org 1.19.6 ) drivers: ati,amdgpu (unloaded: modesetting,fbdev,vesa,radeon) Resolution: 3840x2160@60.00hz, 3840x2160@60.00hz OpenGL: renderer: Radeon RX Vega (VEGA10 / DRM 3.23.0 / 4.15.0-34-generic, LLVM 6.0.0) version: 4.5 Mesa 18.0.5 Direct Render: Yes Audio: Card-1 Advanced Micro Devices [AMD/ATI] Device aaf8 driver: snd_hda_intel bus-ID: 05:00.1 Card-2 Intel C610/X99 series HD Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 Sound: Advanced Linux Sound Architecture v: k4.15.0-34-generic Network: Card: Intel Ethernet Connection (2) I218-V driver: e1000e v: 3.2.6-k port: f020 bus-ID: 00:19.0 IF: eno1 state: up speed: 1000 Mbps duplex: full mac: Drives:HDD Total Size: 500.1GB (19.1% used) ID-1: /dev/sda model: Samsung_SSD_840 size: 500.1GB Partition: ID-1: / size: 457G used: 90G (21%) fs: ext4 dev: /dev/sda2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Info: Processes: 272 Uptime: 2 days Memory: 3254.6/11905.9MB Init: systemd runlevel: 5 Gcc sys: N/A Client: Shell (bash 4.4.191) inxi: 2.3.56 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394532] Multimonitor - Task Manager lists tasks for wrong screen after screens switched off
https://bugs.kde.org/show_bug.cgi?id=394532 --- Comment #2 from JordanL <jordanlepp...@gmail.com> --- I've discovered it's only maximised windows that get moved to the left screen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377561] Panels switched after screen switched off
https://bugs.kde.org/show_bug.cgi?id=377561 --- Comment #7 from JordanL <jordanlepp...@gmail.com> --- Thanks, NVidia GPUs seem to be a common element (I mean, they're pretty popular obviously but even so). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374908] Dual monitors: when screen resumes, windows are rearranged on second monitor
https://bugs.kde.org/show_bug.cgi?id=374908 --- Comment #6 from JordanL <jordanlepp...@gmail.com> --- Do you remember if it was an NVidia GPU? That seems to be a very common element. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394532] Multimonitor - Task Manager lists tasks for wrong screen after screens switched off
https://bugs.kde.org/show_bug.cgi?id=394532 --- Comment #1 from JordanL <jordanlepp...@gmail.com> --- This seems to be "fixed" if I make the left-hand monitor the primary screen. The right-hand task manager now lists the correct tasks after screens are switched back on, and continues working without needing to restart plasma-shell. However, the windows are all still moved to the left-hand monitor. -- You are receiving this mail because: You are watching all bug changes.
