Summary: | kwin crash when saving VirtualBox settings | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Ed Greshko <Ed.Greshko> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | Keywords: | drkonqi |
Priority: | NOR | ||
Version: | 5.9.3 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | backtrace after installing kwin-debuginfo-5.9.3-1.fc25.x86_64 |
Description
Ed Greshko
2017-03-05 05:43:12 UTC
Unfortunately the backtrace is lacking debug symbols. If you are able to reproduce please install the debug packages provided by your distribution (please ask the distribution support channel on how to install them) and attach a new backtrace. Created attachment 104374 [details]
backtrace after installing kwin-debuginfo-5.9.3-1.fc25.x86_64
I have added the requested backtrace after installing the corresponding debuginfo package. This bugzilla system seems a bit different from fedora's as I don't see a place to indicate that the status "needsinfo" should be removed. OK.... I see I can just change it to "unconfirmed". Sorry for the noise. Martin, do you really need more backtraces? It is clear that all these https://bugs.kde.org/buglist.cgi?product=kwin&bug_status=NEEDSINFO&longdesc=QScriptEngine%3A%3AnewQObject&longdesc_type=casesubstring are duplicates of bug 363224. I suggest to ask reporters for exact steps to reproduce. Additionally, pointing them to the duplicate allows them to follow what has been investigated so far, e.g. which effects are causing it. Am 2017-03-06 23:49, schrieb Christoph Feck:
> COMMENT # 5 [2] ON BUG 377225 [3] FROM CHRISTOPH FECK
>
> Martin, do you really need more backtraces?
I'm not seeing to duplicate without knowing that it is truly the same.
If I get a bug report with lacking debug symbols I all for a newer
backtrace. In fact I don't even look at the backtrace if it's lacking
debug symbols.
FWIW, I have reviewed the comments of https://bugs.kde.org/show_bug.cgi?id=363224 and I can confirm that if I block compositing when starting the VirtualBox manager the crash does not occur while closing/saving the settings dialog. *** This bug has been marked as a duplicate of bug 363224 *** |