https://bugs.kde.org/show_bug.cgi?id=423180
--- Comment #1 from jdally987 <jdally...@gmail.com> --- Created attachment 130158 --> https://bugs.kde.org/attachment.cgi?id=130158&action=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 0x00007fd7948958b1 in __GI_abort () at abort.c:79 [...] #10 0x00007fd79505ce22 in qBadAlloc () at global/qglobal.cpp:3322 #11 0x00007fd7950c0050 in QListData::realloc_grow (this=this@entry=0x7ffcd1515b80, growth=growth@entry=1) at tools/qlist.cpp:171 #12 0x00007fd7950c00bf 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.
