[kwin] [Bug 463379] Double Monitor: Lock-screen, after some indefinite amount of time, will fail to actually display when the machine is taken out of sleep due to kwin_x11 abort

https://bugs.kde.org/show_bug.cgi?id=463379 Maluchi Ugokwe Jr. changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution

[kwin] [Bug 463379] Double Monitor: Lock-screen, after some indefinite amount of time, will fail to actually display when the machine is taken out of sleep due to kwin_x11 abort

https://bugs.kde.org/show_bug.cgi?id=463379 --- Comment #22 from Maluchi Ugokwe Jr. --- (In reply to Louis Moureaux from comment #21) > Created attachment 156960 [details] > Stack trace of crashing kwin_x11 > > So it happened again and I was able to gdb in and grab a stack trace o

[kwin] [Bug 463379] Double Monitor: Lock-screen, after some indefinite amount of time, will fail to actually display when the machine is taken out of sleep due to kwin_x11 abort

https://bugs.kde.org/show_bug.cgi?id=463379 Maluchi Ugokwe Jr. changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED

[kwin] [Bug 463379] Double Monitor: Lock-screen, after some indefinite amount of time, will fail to actually display when the machine is taken out of sleep due to kwin_x11 abort

https://bugs.kde.org/show_bug.cgi?id=463379 Maluchi Ugokwe Jr. changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED

[kwin] [Bug 463379] Double Monitor: Lock-screen, after some indefinite amount of time, will fail to actually display when the machine is taken out of sleep due to kwin_x11 abort

https://bugs.kde.org/show_bug.cgi?id=463379 --- Comment #18 from Maluchi Ugokwe Jr. --- Has not occurred on 5.27.0. Closing for now. -- You are receiving this mail because: You are watching all bug changes.

[kscreenlocker] [Bug 463379] Double Monitor: Lock-screen, after some indefinite amount of time, will fail to actually display when the machine is taken out of sleep.

https://bugs.kde.org/show_bug.cgi?id=463379 --- Comment #17 from Maluchi Ugokwe Jr. --- (In reply to Nate Graham from comment #15) > Darn. `coredumpctl --reverse` will tell you if there are any > kscreenlocker_greet crashes. Do you see any? No. Only a signal abort on /usr/bin/kwin_x11 an

[kscreenlocker] [Bug 463379] Double Monitor: Lock-screen, after some indefinite amount of time, will fail to actually display when the machine is taken out of sleep.

https://bugs.kde.org/show_bug.cgi?id=463379 --- Comment #14 from Maluchi Ugokwe Jr. --- (In reply to Maluchi Ugokwe Jr. from comment #13) > The issue occurred again at 9:27 PM. > > Same description. Put the computer to sleep. Reopen it. Pitch black and only > a cursor is shown.

[kscreenlocker] [Bug 463379] Double Monitor: Lock-screen, after some indefinite amount of time, will fail to actually display when the machine is taken out of sleep.

https://bugs.kde.org/show_bug.cgi?id=463379 Maluchi Ugokwe Jr. changed: What|Removed |Added Version|5.26.4 |5.26.5 -- You are receiving this mail

[kscreenlocker] [Bug 463379] Double Monitor: Lock-screen, after some indefinite amount of time, will fail to actually display when the machine is taken out of sleep.

https://bugs.kde.org/show_bug.cgi?id=463379 Maluchi Ugokwe Jr. changed: What|Removed |Added Ever confirmed|0 |1 Resolution|DUPLICATE

[kscreenlocker] [Bug 463379] Double Monitor: Lock-screen, after some indefinite amount of time, will fail to actually display when the machine is taken out of sleep.

https://bugs.kde.org/show_bug.cgi?id=463379 --- Comment #12 from Maluchi Ugokwe Jr. --- (In reply to Nate Graham from comment #11) > Aha, now I know what this bug is: Bug 457284. Other people in there are > reporting that it's also fixed for them with 5.26.5. > > *** This bug h

[kscreenlocker] [Bug 463379] Double Monitor: Lock-screen, after some indefinite amount of time, will fail to actually display when the machine is taken out of sleep.

https://bugs.kde.org/show_bug.cgi?id=463379 --- Comment #10 from Maluchi Ugokwe Jr. --- This issue has not occurred since I have updated to 5.26.5. Lockscreen looks good on two tests: one long term, one short term. If after a day's worth of sporadic testing with varying times I no l

[kscreenlocker] [Bug 463379] Double Monitor: Lock-screen, after some indefinite amount of time, will fail to actually display when the machine is taken out of sleep.

https://bugs.kde.org/show_bug.cgi?id=463379 --- Comment #9 from Maluchi Ugokwe Jr. --- TO ADD ON: Waking up of sleep+suspension has the bug detailed in my OP, but I can get a lock-screen by unplugging my HDMI and using my built in to log in... Unfortunately this is not really a solution, and

[kscreenlocker] [Bug 463379] Double Monitor: Lock-screen, after some indefinite amount of time, will fail to actually display when the machine is taken out of sleep.

https://bugs.kde.org/show_bug.cgi?id=463379 --- Comment #7 from Maluchi Ugokwe Jr. --- (In reply to David Edmundson from comment #4) > If you disable lock after suspend do you still have issues waking up from > sleep? > > Another test: > > Do you reliably get issues if y

[kscreenlocker] [Bug 463379] Double Monitor: Lock-screen, after some indefinite amount of time, will fail to actually display when the machine is taken out of sleep.

https://bugs.kde.org/show_bug.cgi?id=463379 --- Comment #6 from Maluchi Ugokwe Jr. --- (In reply to Nate Graham from comment #3) > Possibly a GPU issue; see similar bug 457284. > > Marking as VHI critical because this can cause data loss due to the > inability to unlock the screen u

[kscreenlocker] [Bug 463379] Double Monitor: Lock-screen, after some indefinite amount of time, will fail to actually display when the machine is taken out of sleep.

https://bugs.kde.org/show_bug.cgi?id=463379 --- Comment #5 from Maluchi Ugokwe Jr. --- (In reply to Nate Graham from comment #3) > Possibly a GPU issue; see similar bug 457284. > > Marking as VHI critical because this can cause data loss due to the > inability to unlock the screen u

[kscreenlocker] [Bug 463379] Double Monitor: Lock-screen, after some indefinite amount of time, will fail to actually display when the machine is taken out of sleep.

https://bugs.kde.org/show_bug.cgi?id=463379 --- Comment #2 from Maluchi Ugokwe Jr. --- To note: this is seemingly at random. Perhaps not even based off of time but some kind of stability. I don't know. I have tried to unlock my computer from sleep (after hours of my own sleep)... and it w

[kscreenlocker] [Bug 463379] Double Monitor: Lock-screen, after some indefinite amount of time, will fail to actually display when the machine is taken out of sleep.

https://bugs.kde.org/show_bug.cgi?id=463379 Maluchi Ugokwe Jr. changed: What|Removed |Added CC||mugokwe...@gmail.com --- Comment #1 from

[kscreenlocker] [Bug 463379] New: Double Monitor: Lock-screen, after some indefinite amount of time, will fail to actually display when the machine is taken out of sleep.

https://bugs.kde.org/show_bug.cgi?id=463379 Bug ID: 463379 Summary: Double Monitor: Lock-screen, after some indefinite amount of time, will fail to actually display when the machine is taken out of sleep. Classification: Plasma

[plasmashell] [Bug 440364] Right Click Bug On Dualhead System.

https://bugs.kde.org/show_bug.cgi?id=440364 --- Comment #11 from Maluchi Ugokwe Jr. --- Thanks, Nate. One of those DUPLICATES actually *proves* that this is an UPSTREAM issue. I appreciate the confirmation. This is now objectively not a Plasma issue. On Tue, Aug 31, 2021 at 6:20 PM Nate Graham

[plasmashell] [Bug 440364] Right Click Bug On Dualhead System.

https://bugs.kde.org/show_bug.cgi?id=440364 --- Comment #2 from Maluchi Ugokwe Jr. --- (In reply to Nate Graham from comment #1) > Please do not deliberately file duplicate or unnecessary bug reports. If we > already know it's a Qt issue, then we don't need another KDE bug r

[plasmashell] [Bug 440364] New: Right Click Bug On Dualhead System.

https://bugs.kde.org/show_bug.cgi?id=440364 Bug ID: 440364 Summary: Right Click Bug On Dualhead System. Product: plasmashell Version: 5.22.4 Platform: unspecified OS: Linux Status: REPORTED Severity: criti