| Summary: | Kwin crashed during resume | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Michał Dybczak <michal.dybczak> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | Keywords: | drkonqi |
| Priority: | NOR | ||
| Version: | 5.15.1 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Michał Dybczak
2019-02-23 14:20:32 UTC
Unfortunately the backtrace is lacking debug symbols. If you are able to reproduce please install debug packages and attach a new backtrace. Ach, I thought that since I was showed that the info is useful, it already has debug symbols. Frankly, this is the first time I saw this "useful" description. For the past few years, I always got that it's not enough/not useful. So I hoped the change happened because Arch finally added debug symbols. If that is not the case, I'm not sure what I can do or if there is something I can do. I'm not technical enough to understand all of it. I posted the bug because I really believed that this is useful stuff, but it isn't, then maybe it's better to close it to keep bugtracker clean and I will know for the future to not use it, till I won't know for sure that debug symbols are available. Additionally, the crash happened just now, for the probably first time under those circumstances, so I can't reproduce it unless some update made it will happen again. Kwin just restarted itself so this was harmless for the system, but I got the usual crash-icon with a crash window (not sure how to name it) which I used to report this bug. If only getting debug symbols were as easy as to install certain packages, I would add them long ago, but it looks it's a matter of upstream, in this case, Arch. So if I can't get debug symbols in any reasonable time to make this bug report really useful, feel free to close it. I would, but I'm not sure which closed status would be suitable for everlasting "needsinfo". Sorry to bother you. It looks like the crash GUI fooled me and maybe that is a bug worth reporting (no debug symbols but still shows this as useful?)? I'm unable to trigger that crash intentionally and I don't have the debug symbols and from what I know, I won't have them any time soon. I don't see a point of keeping this thread opened. Which status would work for this case? Or simply it will linger in "needsinfo" indefinitely? What is the right policy in such cases? Is there any? Do you have NVIDIA GPU? Yes, I have intel/nvidia hybrid GPU setup and it's very, very likely my session was on nvidia then, or at least I remember being on nvidia at that moment. Usually, I'm on intel and I don't see kwin crashes but on nvidia I rarely suspend, so that is may be the reason why I didn't see another instance of that bug. I can try to do suspend/resume on nvidia to see if that is a persistent or just occasional crash. However, I'm suspecting that if you already asking about nvidia, this is not so unknown problem. I'll let you know if I know more. *** This bug has been marked as a duplicate of bug 399499 *** |