[kwin] [Bug 455297] Screen goes black, unresponsive, upon waking up laptop from sleep (but it blinks periodically, and system is still alive)
https://bugs.kde.org/show_bug.cgi?id=455297 --- Comment #6 from jdally987 --- Long time since last update, but wanted to close because I tried Kubuntu 23.10 (kernel 6.5.0-14-generic) and everything suddenly works great. Laptop sleeps and wakes fine, external monitor works without issue. Whatever. I'm just glad it works -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455297] Screen goes black, unresponsive, upon waking up laptop from sleep (but it blinks periodically, and system is still alive)
https://bugs.kde.org/show_bug.cgi?id=455297 jdally987 changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455297] Screen goes black, unresponsive, upon waking up laptop from sleep (but it blinks periodically, and system is still alive)
https://bugs.kde.org/show_bug.cgi?id=455297 --- Comment #4 from jdally987 --- Update: nevermind, I was wrong, it does it on Wayland too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455297] Screen goes black, unresponsive, upon waking up laptop from sleep (but it blinks periodically, and system is still alive)
https://bugs.kde.org/show_bug.cgi?id=455297 --- Comment #3 from jdally987 --- Sorry for the double post (doesn't look like there's a way to edit my previous comments on here) but I should also mention I've found it's probably related to the display itself - since I just got done reinstalling kubuntu today and redid my power settings, disabled suspend after a delay, but left screen energy saving (after 5 minutes or whatever) on - see screenshot: https://i.imgur.com/ZvOxrYM.png And it *still* does the glitchy behavior & necessitates restarting the computer when I left the laptop for 15 minutes and the screen turned off. This is with no suspend involved at all at this point. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455297] Screen goes black, unresponsive, upon waking up laptop from sleep (but it blinks periodically, and system is still alive)
https://bugs.kde.org/show_bug.cgi?id=455297 --- Comment #2 from jdally987 --- (In reply to Zamundaaa from comment #1) > Does this happen on Xorg or on Wayland, and can you see the same problem > with other desktop environments or distributions (live boot might suffice to > reproduce the problem)? Oh yeah my bad totally forgot to mention that I'm on Xorg. I just tried Wayland and I guess it appears it does not do it on that... And I actually did test a few different versions of ubuntu and kubuntu live ISO's (20.04, 21.04, 22.04...) and discovered it does indeed do it on all of them, ubuntu (gnome) included. So yeah sorry about that, guess this isn't KDE-specific after all. Still not sure where to go from here though, I don't love using wayland full-time for various reasons -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 455297] New: Screen goes black, unresponsive, upon waking up laptop from sleep (but it blinks periodically, and system is still alive)
https://bugs.kde.org/show_bug.cgi?id=455297 Bug ID: 455297 Summary: Screen goes black, unresponsive, upon waking up laptop from sleep (but it blinks periodically, and system is still alive) Product: Powerdevil Version: 5.24.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jdally...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Upon putting the laptop to sleep, and then waking it up, the screen will turn back on and display the cursor very briefly (maybe 0.25 seconds), during which time it is movable/controllable, before shutting back off to black. Then it will start blinking, at a rate of about once per second, for a tiny instant (like, even less than the 0.25s the cursor was visible before). Strangely, during the "blinks", the content of the screen *is* barely discernable for that split second - I'll see a glimpse of the lockscreen wallpaper or the chrome tabs I had open, for the infinitesimal duration that the screen has "blinked" on. Additionally, the OS seems to be alive, but barely - more like in a coma - because if I plug it into AC power, the KDE "power connected" chime plays out of the speakers just fine. However, nothing else seems to work. I tested by opening spotify, starting to play a song, locking the computer (without sleeping it) and making sure my sxhkd shortcut for media play/pause (which I bound to Meta+Z) indeed played & paused the music on the lockscreen. Then I slept the computer and woke it a couple seconds later. Following the cursor disappearing and display turning black & starting to blink, I tried Meta+Z a few times, and nothing happened. Assuming it had gotten to the lockscreen, as I have enabled lock after wake in plasma settings, the key combo should've unpaused the music like before. But it doesn't - despite the "power connected" chime functioning correctly as I mentioned. Finally, I've noticed this only happens maybe 9 out of 10 times. Sometimes the computer will awake from sleep and show the lockscreen without killing the display & blinking incessantly, and let me log back in no problem. I haven't nailed down what causes it to work or not yet, but I noted the other day it worked correctly when the battery dropped under 15% (the "low" level) and thus went to sleep on its own. When I woke it up it worked swimmingly. Since this bug has caused me a lot of grief, I set my Energy Saving settings to NOT suspend automatically, but I forgot to uncheck that on the "On Low Battery" tab, hence why it surprised me to find the laptop had slept by itself (thinking I'd now have to reboot, because of the bug), and then doubly-surprised me when I woke it and found it DIDN'T exhibit the buggy behavior. Anyway this is weird; I'd love to attach a backtrace but I'm not sure what exactly is crashing. I'm filing this under powerdevil because it seems to have something to do with suspend/wake, but I suppose it could be something with kscreen or something as well. Regardless I've scoured my syslog to try & find anything out of the ordinary after the bug occurred & I had to reboot, but haven't found anything suspicious, so if someone can provide me guidance on how to figure out what exactly needs to be backtraced in the first place, I'll gladly go ahead & do that. (ps: on the suggested How_to_create_useful_crash_reports wiki page, under the "Ubuntu-based distros" section, 2 out of the 3 links it points to are dead, which was another roadblock to me getting any kinds of debugging output) STEPS TO REPRODUCE 1. Suspend/sleep the system 2. Press power button to wake 3. Move the mouse around frantically as it wakes, to see the cursor move for 0.25s before the screen shuts off, then observe it blinking once/second OBSERVED RESULT The display goes black/unresponsive after what looks to be the OS waking from sleep normally (evidenced by the brief period where the cursor is visible and responsive). EXPECTED RESULT The display should come on about a second after pressing the power button, then the lockscreen should be displayed about another second later, and NOT turn off suddenly. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.10, Linux 5.18.3 (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION One more notable detail is the laptop I'm using is an LG Gram, 2021 model, which I just recently bought. However, I started experiencing this behavior just a few weeks *before* I bought this model - at which time I was still using my older, 2019 model LG Gram. I kind of hoped it
[klipper] [Bug 428796] /etc/xdg/autostart/klipper.desktop is marked executable
https://bugs.kde.org/show_bug.cgi?id=428796 --- Comment #5 from jdally987 --- Created attachment 133390 --> https://bugs.kde.org/attachment.cgi?id=133390=edit journald log Output upon running `nixos-rebuild switch` -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 428796] /etc/xdg/autostart/klipper.desktop is marked executable
https://bugs.kde.org/show_bug.cgi?id=428796 --- Comment #4 from jdally987 --- Hey I get this too - on NixOS 20.09 (plasma5 package ver 5.18.5 I think). I thought it might be a security concern but I have no idea - just wondering what it could be in any case. I'll attach what syslog spits out when I run `nixos-rebuild switch`, it's right there in the middle: systemd[9477]: Configuration file /run/current-system/sw/etc/xdg/autostart/klipper.desktop is marked executable. Please remove executable permission bits. Proceeding anyway. (although it looks like all the .desktop files in that directory are executable as well) -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 428796] /etc/xdg/autostart/klipper.desktop is marked executable
https://bugs.kde.org/show_bug.cgi?id=428796 jdally987 changed: What|Removed |Added CC||jdally...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425394] Latest Neon User Edition ISO image is 18.04 based, not 20.04.
https://bugs.kde.org/show_bug.cgi?id=425394 jdally987 changed: What|Removed |Added CC||jdally...@gmail.com --- Comment #2 from jdally987 --- Created attachment 130897 --> https://bugs.kde.org/attachment.cgi?id=130897=edit md5sum.txt Yep same here - attached md5sum.txt from root of "neon-user-20200813-1119.iso" (sha256: 946123A877C1514E68E910A137DFB69E69D854DD447344A9962992DA6FB3DE14) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 423180] Random Spectacle crash.
https://bugs.kde.org/show_bug.cgi?id=423180 --- Comment #3 from jdally987 --- Created attachment 130163 --> https://bugs.kde.org/attachment.cgi?id=130163=edit Crashlog before the debugging symbols were installed -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 423180] Random Spectacle crash.
https://bugs.kde.org/show_bug.cgi?id=423180 --- Comment #2 from jdally987 --- Created attachment 130160 --> https://bugs.kde.org/attachment.cgi?id=130160=edit Screenshot of the weird certificate error -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 423180] Random Spectacle crash.
https://bugs.kde.org/show_bug.cgi?id=423180 jdally987 changed: What|Removed |Added CC||jdally...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 423180] Random Spectacle crash.
https://bugs.kde.org/show_bug.cgi?id=423180 --- Comment #1 from jdally987 --- Created attachment 130158 --> https://bugs.kde.org/attachment.cgi?id=130158=edit New crash information added by DrKonqi spectacle (20.04.3) using Qt 5.14.2 - What I was doing when the application crashed: WARNING: EXCESSIVE DETAIL Had gotten a weird kernel error from Chromium which made the whole page crash. I opened the devtools but apparently that had crashed too, and I couldn't even investigate the page's contents, which showed an "Error code: RESULT_CODE_UNINSTALL_USER_CANCEL" (in a suspiciously smaller font than is usual for the various chrome error pages) and for that matter my mouse cursor didn't change to a "link" hand (pointer finger) when mousing over the "Reload" button on the page, even though I could hit the "Learn more" hyperlink. Anyway, so I started browsing around each tab of the Devtools just to see if any worked, and somehow under the Protocol Monitor tab (one of the "More tools" extra tabs, and I think maybe has to be enabled as an Experimental devtools setting) it showed a bit of history of that tab's javascript. Went to the beginning and dug a bit to find a Security.securityStateChanged event with an "unknown" value for the "displayedInsecureContentStyle" and "ranInsecureContentStyle" keys, so I knew something was fishy. Googled it, came across this old bug: https://groups.google.com/a/chromium.org/forum/#!msg/headless-dev/RqxZAsYra0Y/9D0x8UqQBgAJ Went to the "airhorner(dot)com" page the OP mentioned; noticed a redirect before it successfully got to the page and so I checked out its certificate. Found it was using the GlobalSign Root CA - R2 issued "GTS CA 1D2" intermediate cert, which I hadn't seen before, so I went on google's certificates page and found the tester links for that one; and sure enough, the "good" test worked fine but the "revoked" test marked it as still good. I'm pretty sure that should give me a warning if it was working correctly right? So THAT's (finally) when I opened Spectacle to document the bad cert, and that crashed too! WARNING: EXCESSIVE DETAIL END Alright, I only included all that above^ because I've had some kind of hellish bug or malware, who knows, I'm really not sure at this point - plaguing my machine(s) for months now, so wanted to leave any extra detail that might help anyone who has the same issues. For the Spectacle problem alone, I dunno, check out the crash log, I'm not good at interpreting the kernel stuff, still have no idea where this problem (as a whole) started from. It could well be something that LG, my laptop manufacturer, misconfigured with the CPU/platform in the bios settings instead of something malicious. Laptop is an LG Gram 17 (17z990-R.AAS7U1). Certificate issues abound in Ubuntu (vanilla, gnome) 20.04 as well, plus myriad more, which I won't get into detail about, but this is the first time I've had so many things crash on me at once so perhaps KDE aggravated it, not sure. - Unusual behavior I noticed: See wall of text above -- Backtrace (Reduced): #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #5 0x7fd7948958b1 in __GI_abort () at abort.c:79 [...] #10 0x7fd79505ce22 in qBadAlloc () at global/qglobal.cpp:3322 #11 0x7fd7950c0050 in QListData::realloc_grow (this=this@entry=0x7ffcd1515b80, growth=growth@entry=1) at tools/qlist.cpp:171 #12 0x7fd7950c00bf in QListData::append (this=0x7ffcd1515b80, n=n@entry=1) at tools/qlist.cpp:196 -- You are receiving this mail because: You are watching all bug changes.
