https://bugs.kde.org/show_bug.cgi?id=483243
Méven Car <meve...@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REPORTED |CONFIRMED Ever confirmed|0 |1 --- Comment #5 from Méven Car <meve...@gmail.com> --- (In reply to andy from comment #4) > (In reply to Méven Car from comment #3) > > @andy, did you use spectacle or other screenshot application in your session > > previous to the crash ? > > I do have a script that periodically takes screenshots with spectacle. > I'll try disabling that overnight tonight to see if it makes a difference. I am about 95% sure that it will. You can try disabling it as you lock you session. > In my first comment in the backtrace there was no QImage mention so I wonder > if > it's unrelated. Given so many threads in the core dump log, which does `gdb > bt full` show? The first trace ends with `#0 0x00005a39fb8aa812 in ??? ()` i.e couldn't display more information, Meaning it could end in the same place as before, we had the mention of `QFutureWatcherBase::finished` which hints that way. Between the two traces you must have installed better debug symbols that allowed to read that. -- You are receiving this mail because: You are watching all bug changes.