Bug 423827

Summary: It crashed when I tried to logout, but had been buggy for a little while beforehand
Product: [Websites] www.kde.org Reporter: J <jlerossignol>
Component: generalAssignee: kde-www mailing-list <kde-www>
Status: RESOLVED NOT A BUG    
Severity: crash CC: nate
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Crash report

Description J 2020-07-03 07:52:37 UTC
Created attachment 129863 [details]
Crash report

SUMMARY
Don't know. It just crashed

STEPS TO REPRODUCE
1. I doubt I could reproduce it 
2. 
3. 

OBSERVED RESULT
Desktop not responding, used terminal to reboot.
It did so to windows, fucking Windows! I'd previously removed the possibility of booting into that but if found an old patrician. 
After fixing the BIOS to booting back into Linux (PopOS 19), the mouse had a 1/2 second sluggish response, like a drunk hamster staggering across my desktop. No I don't remember how I fixed it last time, but usbutils appeared to do the trick this time. Anyhow, the drunk gerbil's gone, but I'd like to now, WTF is going on  with KDE Plasma


EXPECTED RESULT
Not much

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  tick
(available in About System)
KDE Plasma Version: 5.0 I think

ADDITIONAL INFORMATION
Don't know what you'd want
Comment 1 Nate Graham 2020-07-13 18:05:00 UTC
Crash report contains QSGRenderLoop::handleContextCreationFailure in it. This means you forgot to revbot after updating your graphics drivers.
Comment 2 Nate Graham 2020-07-13 18:06:19 UTC
But let me know if you ever figure out what was up with the old patrician lol