| Summary: | KWin crash on startup | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | RJVB <rjvbertin> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | Keywords: | drkonqi, triaged |
| Priority: | NOR | ||
| Version First Reported In: | 5.8.4 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
RJVB
2016-12-07 11:57:18 UTC
This was reproducible, and I think it was caused by the fact I had configured an icon theme which inherits the gnome icon theme. My KaOS install had only a partial version of that, just the 32x32 directory. I don't think that should lead to a crash, though (nor an abort). Unfortunately the backtrace is lacking debug infos and we don't see where it crashes. It looks like being an OpenGL driver crash. You're right, damn. DrKonqi gave 3 starts to the backtrace so I didn't look any further. I'll have to figure out if KaOS has something equivalent to Debuntu's dbg packages. Not for everything, it seems. Annoyingly I haven't yet been able to reproduce the crash. I'll update this ticket if/when I can, but it certainly seems likely that the crash had something to do with compositing. In fact I'm surprised that I got acceptable desktop behaviour at all with compositing active; I have another system that I run both on real silicon and under VirtualBox and I keep having to toggle the feature (and that's VirtualBox under MSWin, which usually has better support for "advanced graphics"). Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |