| Summary: | kcminit crash on startup | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Alessandro <alessandro.sturniolo> |
| Component: | kcm_mouse | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | christiandehne, dap.darkness, fabian, fodrek.p, hbs, kde, kde, michael, nate, raul.malea, smetz3, software, suhn, unassigned-bugs |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=395765 | ||
| Latest Commit: | https://commits.kde.org/plasma-desktop/ead2c3e859dcb8531df99e87c0fe6eff64650952 | Version Fixed In: | 5.13.1 |
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Alessandro
2018-05-21 18:48:47 UTC
Crashes in Mouse KCM init *** Bug 395121 has been marked as a duplicate of this bug. *** *** Bug 395482 has been marked as a duplicate of this bug. *** *** Bug 395539 has been marked as a duplicate of this bug. *** All duplicates from openSUSE. (In reply to Christoph Feck from comment #5) > All duplicates from openSUSE. Likely a red herring because of different compiler or environment options for additional hardening. This looks like wrong use of KConfig to me, it creates a dangling pointer: https://cgit.kde.org/plasma-desktop.git/tree/kcms/mouse/backends/x11/x11_backend.cpp#n126 Yep. Never crashes here but a minimal test of the same code does produce a valgrind warning. Writing the correct version which keeps the lifespan of the KConfig object does nto produce the warning. Will fix this. I reported my duplicate 395539 less than 24 hours ago. Great to see that you're on top of it. Thanks a lot, keep it up! Git commit ead2c3e859dcb8531df99e87c0fe6eff64650952 by David Edmundson. Committed on 19/06/2018 at 08:02. Pushed by davidedmundson into branch 'Plasma/5.13'. Ref KConfig whilst we're using it Summary: In current code we would have a KConfigGroup with a dangling KConfig deleted after the RHS for the group fetch has finished. Test Plan: Wrote minimal test case of code It produced a valgrind warning (weirdly didn't crash though) Modified to correct version No longer any warnings Reviewers: #plasma Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D13599 M +3 -1 kcms/mouse/backends/x11/x11_backend.cpp https://commits.kde.org/plasma-desktop/ead2c3e859dcb8531df99e87c0fe6eff64650952 *** Bug 395613 has been marked as a duplicate of this bug. *** Created attachment 113521 [details]
New crash information added by DrKonqi
kdeinit5 () using Qt 5.11.0
- What I was doing when the application crashed:
Logging in via sddm.
Happens with all users on this system, even with new created ones.
-- Backtrace (Reduced):
#6 0x00007f21e87e11ea in QMapData<KEntryKey, KEntry>::findNode (this=0x4545454545454545, akey=...) at /usr/include/qt5/QtCore/qmap.h:284
#7 0x00007f21e87e639b in QMap<KEntryKey, KEntry>::constFind (this=0x561798ad0500, akey=...) at /usr/include/qt5/QtCore/qmap.h:874
#8 QMap<KEntryKey, KEntry>::find (akey=..., this=0x561798ad0500) at /usr/include/qt5/QtCore/qmap.h:876
#9 KEntryMap::findEntry (this=this@entry=0x561798ad0500, group=..., key=..., flags=...) at /usr/src/debug/kconfig-5.46.0-1.2.x86_64/src/core/kconfigdata.cpp:74
#10 0x00007f21e87e64bb in KEntryMap::getEntry (this=this@entry=0x561798ad0500, group=..., key=..., defaultValue=..., flags=..., flags@entry=..., expand=0x7ffd1aba4b27) at /usr/src/debug/kconfig-5.46.0-1.2.x86_64/src/core/kconfigdata.cpp:224
*** Bug 395779 has been marked as a duplicate of this bug. *** *** Bug 395869 has been marked as a duplicate of this bug. *** We also get the same crash for Akregator on Tumbleweed, see bug 384134. Could anyone understanding the Plasma fix propose a fix for Akregator? *** Bug 395913 has been marked as a duplicate of this bug. *** Okular is also affected, see bug 395765. (In reply to Christoph Feck from comment #16) > Okular is also affected, see bug 395765. The backtraces are basically identical, seems to be caused by KMainWindow. I don't see anything wrong with a first glance though. *** Bug 395691 has been marked as a duplicate of this bug. *** |