Summary: | Crashed after another app crashed | ||
---|---|---|---|
Product: | [Applications] drkonqi | Reporter: | Justin Zobel <justin> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | REPORTED --- | ||
Severity: | crash | CC: | bugseforuns, christophe, sitter |
Priority: | NOR | ||
Version: | master | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Justin Zobel
2024-03-10 05:47:52 UTC
Did the compositor crash maybe? This isn't really a crash but qapplication failing to start. Yes the session was destroyed. The starting bug/crash was applying settings in systemsettings: https://bugs.kde.org/show_bug.cgi?id=483072 *** Bug 482251 has been marked as a duplicate of this bug. *** I don't have a clear way to reproduce but each time I see this crash, it happens when restoring an application using the tray icon if the screens were turned off due to inactivity before (not immediately before, but I don't think I ever had the crash if the screens didn't turn off before) coredumpctl always saves bt for gmenudbusmenuproxy, kwalletd6 and kwin_x11 in this case (and sometimes xembedsniproxy) *** Bug 484108 has been marked as a duplicate of this bug. *** |