| Summary: | kcmshell5 kcm_sddm dumps core everytime it is executed | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Bob Wya <bob.mt.wya> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | crash | CC: | arichardson.kde, asturm, kde, matej, simonandric5 |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.9.5 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Bob Wya
2016-06-20 05:36:51 UTC
Still present in 5.7.2 ... Sigh... kcmshell5 kcm_sddm QDBusArgument: read from a write-only object Aborted (core dumped) Is it safe to assume you have built Qt with USE=debug? (In reply to andreas.sturmlechner from comment #2) > Is it safe to assume you have built Qt with USE=debug? You presume correctly. You may also presume, that building with Qt 5.7.0 with USE=-debug, fixes the issue! I am able launch kcm_sddm without any issues in this instance. I might have forgotten to report this fact - I stumbled upon a month or two ago (cough). :-) Allow me to link back to the related Gentoo bug, then: https://bugs.gentoo.org/show_bug.cgi?id=589780#c6 Also happens to me with more KDE components: org_kde_powerdevil (5.9.5) polkit-kde-authentication-agent-1 (5.9.5) Qt Version: 5.7.1 Frameworks Version: 5.34.0 polkit-qt-1: 0.112.0 Operating System: Linux 4.9.16-gentoo x86_64 Distribution (Platform): Gentoo Packages All the crashes have common end of the backtrace: Thread 1 (Thread 0x7f5a98552840 (LWP 3681)): [KCrash Handler] #6 0x00007f5a96b13128 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x00007f5a96b1457a in __GI_abort () at abort.c:89 #8 0x00007f5a97306999 in qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1682 #9 QMessageLogger::fatal (this=this@entry=0x7ffd00abfaa0, msg=msg@entry=0x7f5a986b0098 "QDBusArgument: read from a write-only object") at global/qlogging.cpp:793 #10 0x00007f5a98645e08 in QDBusArgumentPrivate::checkRead (d=<optimized out>) at qdbusargument.cpp:142 #11 0x00007f5a98693ee8 in QDBusArgumentPrivate::checkRead (d=<optimized out>) at qdbusargument.cpp:166 #12 QDBusArgumentPrivate::checkReadAndDetach (d=@0x7ffd00abfc50: 0x2503980) at qdbusargument.cpp:152 #13 0x00007f5a98696ea9 in QDBusArgument::beginMapEntry (this=0x7ffd00abfc50) at qdbusargument.cpp:1069 #14 0x00007f5a7edba93f in operator>><QString> (list=..., arg=...) at /usr/include/qt5/QtDBus/qdbusargument.h:275 #15 PolkitQt1::Authority::Private::init (this=0x24e1090) at /var/tmp/portage/sys-auth/polkit-qt-0.112.0-r1/work/polkit-qt-1-0.112.0/core/polkitqt1-authority.cpp:226 ...and appear indeed only when QtDBus is compiled in debug mode: https://code.qt.io/cgit/qt/qtbase.git/tree/src/dbus/qdbusargument.cpp?h=5.7#n141 The assertion has been however probably fixed in polkit-qt master in this commit: https://cgit.kde.org/polkit-qt-1.git/commit/?id=fb1667ac9a5437b4784d2806a3e816cbdbe404a5 Alex, maybe this warrants releasing new polkit-qt-1 with the fix? |