[kwin] [Bug 468159] After waking from sleep with complex triple-monitor setup, middle screen's desktop has the wrong size and windows leave ghost trails
https://bugs.kde.org/show_bug.cgi?id=468159 Zamundaaa changed: What|Removed |Added CC||k...@hexchain.org --- Comment #18 from Zamundaaa --- *** Bug 464674 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468159] After waking from sleep with complex triple-monitor setup, middle screen's desktop has the wrong size and windows leave ghost trails
https://bugs.kde.org/show_bug.cgi?id=468159 David Edmundson changed: What|Removed |Added Component|screencasting |multi-screen CC||k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468159] After waking from sleep with complex triple-monitor setup, middle screen's desktop has the wrong size and windows leave ghost trails
https://bugs.kde.org/show_bug.cgi?id=468159 David Edmundson changed: What|Removed |Added Component|multi-screen|screencasting -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468159] After waking from sleep with complex triple-monitor setup, middle screen's desktop has the wrong size and windows leave ghost trails
https://bugs.kde.org/show_bug.cgi?id=468159 --- Comment #17 from 13k --- Created attachment 163703 --> https://bugs.kde.org/attachment.cgi?id=163703=edit kscreen-doctor, wayland-info, journalctl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468159] After waking from sleep with complex triple-monitor setup, middle screen's desktop has the wrong size and windows leave ghost trails
https://bugs.kde.org/show_bug.cgi?id=468159 13k changed: What|Removed |Added CC||kde.wc...@slmail.me --- Comment #16 from 13k --- I can confirm this is happening with my setup too. In my case, I have a 2 monitor setup (output1 DP-3 2560x1440@144, output2 DP-1 3440x1440@16; output2 is set to primary) and it happens on screenlock, no need to enter sleep mode (I don't have sleep enabled). The thing is, this primary monitor (output2 on DP-1), when entering its own energy saving mode, behaves like it was completely turned off - as opposed to other monitors I owned where they simply turned off the screen but the DP/HDMI connection was still online - so all the unplug/re-plug events happen when the monitor goes to sleep (windows/panels are moved from primary monitor to secondary, then moved back when the monitor wakes up). I've attached the logs for `kscreen-doctor -o`, `wayland-info` and `journalctl` right after the bug happens (you can see kernel USB events indicating the monitor was detected as plugged in, but it was simply sleeping). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468159] After waking from sleep with complex triple-monitor setup, middle screen's desktop has the wrong size and windows leave ghost trails
https://bugs.kde.org/show_bug.cgi?id=468159 --- Comment #15 from Beyley Thomas --- I have recently started encountering another (perhaps related) issue in the past month or so Whenever my computer goes to sleep, my main monitor (a Samsung LC34G55T) seems to "hard crash", in that it refuses to ever turn back online after plasma puts it to sleep, i can turn my computer off and on, restart it, and press every button on the monitor, nothing happens, the only solution to get it working again is to unplug and replug the monitor's power cable This does not happen under hyprland or sway, so i'm assuming its a kwin bug -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468159] After waking from sleep with complex triple-monitor setup, middle screen's desktop has the wrong size and windows leave ghost trails
https://bugs.kde.org/show_bug.cgi?id=468159 Beyley Thomas changed: What|Removed |Added Version|5.27.8 |5.27.9 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468159] After waking from sleep with complex triple-monitor setup, middle screen's desktop has the wrong size and windows leave ghost trails
https://bugs.kde.org/show_bug.cgi?id=468159 Beyley Thomas changed: What|Removed |Added Version|5.27.7 |5.27.8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468159] After waking from sleep with complex triple-monitor setup, middle screen's desktop has the wrong size and windows leave ghost trails
https://bugs.kde.org/show_bug.cgi?id=468159 Marco Schmidlin changed: What|Removed |Added CC||ner...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468159] After waking from sleep with complex triple-monitor setup, middle screen's desktop has the wrong size and windows leave ghost trails
https://bugs.kde.org/show_bug.cgi?id=468159 Beyley Thomas changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #14 from Beyley Thomas --- after playing with it for awhile, i figured out that i needed to specify the debuginfod URLs, as sudo wasnt preserving the right ENV vars for debuginfod to work (i needed sudo for coredumpctl) [Current thread is 1 (Thread 0x7f6d83ee9640 (LWP 1183))] (gdb) bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7f6de8a3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #2 0x7f6d8883e668 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x7f6d888264b8 in __GI_abort () at abort.c:79 #4 0x7f6d8ab04fee in egl_provider_resolver (name=name@entry=0x7f6d8ab2bc44 "eglDestroySyncKHR", providers=providers@entry=0x7f6d8ab2b784 , entrypoints=entrypoints@entry=0x7f6d8ab2b778 ) at src/egl_generated_dispatch.c:3911 #5 0x7f6d8ab08ab2 in epoxy_eglDestroySyncKHR_resolver () at src/egl_generated_dispatch.c:4312 #6 epoxy_eglDestroySyncKHR_global_rewrite_ptr (dpy=0x5644b2350380, sync=0x5644b5cf7d20) at src/egl_generated_dispatch.c:5063 #7 0x5644b0fb0d52 in KWin::EGLNativeFence::~EGLNativeFence() (this=0x5644b4de5320, this=) at /usr/src/debug/kwin/kwin-5.27.7/src/plugins/screencast/eglnativefence.cpp:36 #8 std::default_delete::operator()(KWin::EGLNativeFence*) const (this=, __ptr=0x5644b4de5320) at /usr/include/c++/13.1.1/bits/unique_ptr.h:99 #9 std::default_delete::operator()(KWin::EGLNativeFence*) const (__ptr=0x5644b4de5320, this=) at /usr/include/c++/13.1.1/bits/unique_ptr.h:93 #10 std::__uniq_ptr_impl >::reset(KWin::EGLNativeFence*) (__p=0x0, this=0x5644b4e27108) at /usr/include/c++/13.1.1/bits/unique_ptr.h:211 #11 std::unique_ptr >::reset(KWin::EGLNativeFence*) (__p=0x0, this=0x5644b4e27108) at /usr/include/c++/13.1.1/bits/unique_ptr.h:509 #12 KWin::ScreenCastStream::enqueue() (this=0x5644b4e26f40) at /usr/src/debug/kwin/kwin-5.27.7/src/plugins/screencast/screencaststream.cpp:680 #13 0x7f6d89ad1637 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffd137295b0, r=, this=0x7f6d6c00a4c0, this=, r=, a=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #14 doActivate(QObject*, int, void**) (sender=0x5644b52ed5f0, signal_index=3, argv=0x7ffd137295b0) at kernel/qobject.cpp:3925 #15 0x7f6d89ad2e34 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) (this=this@entry=0x5644b52ed5f0, _t1=..., _t2=, _t3=...) at .moc/moc_qsocketnotifier.cpp:178 #16 0x7f6d89ad2f78 in QSocketNotifier::event(QEvent*) (this=0x5644b52ed5f0, e=) at kernel/qsocketnotifier.cpp:302 #17 0x7f6d8917893f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #18 0x7f6d89a9c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x5644b52ed5f0, event=0x7ffd137296d0) at kernel/qcoreapplication.cpp:1064 #19 0x7f6d89aea0dc in QEventDispatcherUNIXPrivate::activateSocketNotifiers() (this=this@entry=0x5644b1f44b20) at kernel/qeventdispatcher_unix.cpp:304 #20 0x7f6d89aeb2a9 in QEventDispatcherUNIX::processEvents(QFlags) (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:511 #21 0x5644b106bba2 in QUnixEventDispatcherQPA::processEvents(QFlags) () #22 0x7f6d89a9b404 in QEventLoop::exec(QFlags) (this=this@entry=0x7ffd13729860, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #23 0x7f6d89a9c8a3 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #24 0x5644b0f872fb in main(int, char**) (argc=, argv=) at /usr/src/debug/kwin/kwin-5.27.7/src/main_wayland.cpp:628 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468159] After waking from sleep with complex triple-monitor setup, middle screen's desktop has the wrong size and windows leave ghost trails
https://bugs.kde.org/show_bug.cgi?id=468159 --- Comment #13 from Bug Janitor Service --- 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! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468159] After waking from sleep with complex triple-monitor setup, middle screen's desktop has the wrong size and windows leave ghost trails
https://bugs.kde.org/show_bug.cgi?id=468159 --- Comment #12 from Zamundaaa --- No, as long as your distro has everything set up correctly it should work without you needing to do anything -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468159] After waking from sleep with complex triple-monitor setup, middle screen's desktop has the wrong size and windows leave ghost trails
https://bugs.kde.org/show_bug.cgi?id=468159 Beyley Thomas changed: What|Removed |Added Version|5.27.3 |5.27.7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468159] After waking from sleep with complex triple-monitor setup, middle screen's desktop has the wrong size and windows leave ghost trails
https://bugs.kde.org/show_bug.cgi?id=468159 --- Comment #11 from Beyley Thomas --- (In reply to Zamundaaa from comment #10) > The backtrace is incomplete. Please install debuginfod and get a backtrace > with debug symbols I do already have debuginfod, is there something else i need to pass to coredumpctl to get it to use it? (sorry for the late response ive been trying to replicate the crash, and it hasnt happened in a couple weeks), but i can confirm the bugged plasmashell desktop and compositor issues still happen on 5.27.7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468159] After waking from sleep with complex triple-monitor setup, middle screen's desktop has the wrong size and windows leave ghost trails
https://bugs.kde.org/show_bug.cgi?id=468159 --- Comment #10 from Zamundaaa --- The backtrace is incomplete. Please install debuginfod and get a backtrace with debug symbols -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468159] After waking from sleep with complex triple-monitor setup, middle screen's desktop has the wrong size and windows leave ghost trails
https://bugs.kde.org/show_bug.cgi?id=468159 --- Comment #9 from Beyley Thomas --- (In reply to Zamundaaa from comment #8) > Okay. When it crashes again, please afterwards start gdb with > coredumpctl debug kwin_wayland > and then get a backtrace with "bt" and attach that here [Current thread is 1 (Thread 0x7f19157c4640 (LWP 1176))] (gdb) bt #0 0x7f191a29f26c in () at /usr/lib/libc.so.6 #1 0x7f191a24fa08 in raise () at /usr/lib/libc.so.6 #2 0x7f191a238538 in abort () at /usr/lib/libc.so.6 #3 0x7f191c38afee in () at /usr/lib/libepoxy.so.0 #4 0x7f191c38eab2 in () at /usr/lib/libepoxy.so.0 #5 0x55abe5bbed52 in () #6 0x7f191b2d15a7 in () at /usr/lib/libQt5Core.so.5 #7 0x7f191b2d2da4 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #8 0x7f191b2d2ee8 in QSocketNotifier::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #9 0x7f191a97893f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #10 0x7f191b29c668 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #11 0x7f191b2ea09c in QEventDispatcherUNIXPrivate::activateSocketNotifiers() () at /usr/lib/libQt5Core.so.5 #12 0x7f191b2eb0e5 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #13 0x55abe5c79ba2 in () #14 0x7f191b29b374 in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #15 0x7f191b29c813 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #16 0x55abe5b952fb in () #17 0x7f191a239850 in () at /usr/lib/libc.so.6 #18 0x7f191a23990a in __libc_start_main () at /usr/lib/libc.so.6 #19 0x55abe5b96ed5 in () -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468159] After waking from sleep with complex triple-monitor setup, middle screen's desktop has the wrong size and windows leave ghost trails
https://bugs.kde.org/show_bug.cgi?id=468159 --- Comment #8 from Zamundaaa --- Okay. When it crashes again, please afterwards start gdb with coredumpctl debug kwin_wayland and then get a backtrace with "bt" and attach that here -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468159] After waking from sleep with complex triple-monitor setup, middle screen's desktop has the wrong size and windows leave ghost trails
https://bugs.kde.org/show_bug.cgi?id=468159 --- Comment #7 from Beyley Thomas --- (In reply to Zamundaaa from comment #6) > Please attach the output of wayland-info after reproducing the bug. > > (In reply to Beyley Thomas from comment #5) > > Another result of this bug seems to be that any app that tries to use the > > screen capture portal after the bug happens causes plasma to hard crash and > > restart > > Do you mean only plasmashell crashes, or the whole session? Also, if > plasmashell restarts (or if you restart it with `plasmashell --replace`), > does the problem go away? the whole session crashes, and when it does, the bug goes away, i shall report back next time i trigger the bug to see if restarting plasmashell alone fixes it too -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468159] After waking from sleep with complex triple-monitor setup, middle screen's desktop has the wrong size and windows leave ghost trails
https://bugs.kde.org/show_bug.cgi?id=468159 Zamundaaa changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||xaver.h...@gmail.com --- Comment #6 from Zamundaaa --- Please attach the output of wayland-info after reproducing the bug. (In reply to Beyley Thomas from comment #5) > Another result of this bug seems to be that any app that tries to use the > screen capture portal after the bug happens causes plasma to hard crash and > restart Do you mean only plasmashell crashes, or the whole session? Also, if plasmashell restarts (or if you restart it with `plasmashell --replace`), does the problem go away? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468159] After waking from sleep with complex triple-monitor setup, middle screen's desktop has the wrong size and windows leave ghost trails
https://bugs.kde.org/show_bug.cgi?id=468159 Nate Graham changed: What|Removed |Added Summary|Wayland desktop wrong size |After waking from sleep |after waking from sleep |with complex triple-monitor ||setup, middle screen's ||desktop has the wrong size ||and windows leave ghost ||trails Keywords||multiscreen -- You are receiving this mail because: You are watching all bug changes.
