| Summary: | Plasma crashes in QDBusConnectionPrivate::isServiceRegisteredByThread() at login | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Gunnar <philip.e.g.andersson> |
| Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | crash | CC: | flyxman, glassy_bulb, mrvikxd, nate, plasma-bugs, rikmills, shafff |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 5.12.2 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
||
|
Description
Gunnar
2018-03-03 22:18:34 UTC
*** Bug 389806 has been marked as a duplicate of this bug. *** Created attachment 123710 [details]
New crash information added by DrKonqi
plasmashell (5.16.5) using Qt 5.12.2
- What I was doing when the application crashed:
When I log on to kde desktop it is going to crash every time, and I can't open it using: kstart plasmashell command (It crashes every time)
- Unusual behavior I noticed:
There is nothing unusual other than some errors.
- Custom settings of the application:
There is some configuration I made like: some plasmoids, some shortcuts and other minor improvements.
-- Backtrace (Reduced):
#8 0x00007f93c68f4371 in QQmlTypeLoader::Blob::addImport(QV4::CompiledData::Import const*, QList<QQmlError>*) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
[...]
#11 0x00007f93c68f11cd in QQmlTypeLoader::setData(QQmlDataBlob*, QQmlDataBlob::SourceCodeData const&) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#12 0x00007f93c68f198a in QQmlTypeLoader::setData(QQmlDataBlob*, QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#13 0x00007f93c68f1aa8 in QQmlTypeLoader::loadThread(QQmlDataBlob*) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
[...]
#17 0x00007f93c5c6b551 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
Created attachment 130030 [details]
New crash information added by DrKonqi
plasmashell (5.18.5) using Qt 5.14.2
- What I was doing when the application crashed:
Power on my machine
Waiting until I can input my password
Enter password
Login to the Plasma
I was notified about segmentation fault
no any action was done by me before I geted error
-- Backtrace (Reduced):
#4 0x00007f30fd97204b in QtPrivate::QStringList_contains(QStringList const*, QString const&, Qt::CaseSensitivity) () from /lib64/libQt5Core.so.5
#5 0x00007f30fea51b30 in QDBusConnectionPrivate::isServiceRegisteredByThread(QString const&) () from /lib64/libQt5DBus.so.5
#6 0x00007f30fea5bc18 in QDBusConnectionPrivate::sendWithReplyAsync(QDBusMessage const&, QObject*, char const*, char const*, int) () from /lib64/libQt5DBus.so.5
#7 0x00007f30fea5cff1 in QDBusConnectionPrivate::sendWithReply(QDBusMessage const&, int, int) () from /lib64/libQt5DBus.so.5
#8 0x00007f30fea4976b in QDBusConnection::call(QDBusMessage const&, QDBus::CallMode, int) const () from /lib64/libQt5DBus.so.5
> #15 0x00007fdb74eee865 in LightDMDBus::LightDMDBus (this=0x7fdb76751680) at /workspace/build/libkworkspace/kdisplaymanager.cpp:273
That looks odd, given that you're using SDDM.
Thank you for reporting this issue in KDE software. As it was reported on an older version, can we please ask you to see if you can reproduce the issue with a more recent software version? If you can confirm this issue still exists in a recent version, please change the version field and the status to "REPORTED" when replying. Thank you! 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 mark the bug 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! 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! https://bugreports.qt.io/browse/QTBUG-88498 https://code.qt.io/cgit/qt/qtbase.git/commit/src/dbus/qdbusintegrator.cpp?h=6.8&id=7e3d29f618f4fb1464327abca49a33cb00a3ac91 QDBusConnectionPrivate: Use write lock inside handleSignal() Slots like (un)registerServiceNoLock() modify shared state and should be run with write lock taken. Having only read lock results in hard to reproduce crashes. |