| Summary: | plasma-runner-solid crash, maybe udisks2 related | ||
|---|---|---|---|
| Product: | [Unmaintained] solid | Reporter: | Rex Dieter <rdieter> |
| Component: | libsolid-udisks2 | Assignee: | Lukáš Tinkl <lukas> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | christiandehne, jirislaby, lukas, paulo.fidalgo.pt, wilderkde |
| Priority: | NOR | ||
| Version: | 4.9.1 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | http://commits.kde.org/kde-workspace/06c934efdcdf3a8bb18982f53f9abcf2c67049d0 | Version Fixed In: | 4.10.1 |
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
||
|
Description
Rex Dieter
2012-09-26 16:58:38 UTC
reproducible with qt-4.8.2 too, so we can probably discount any blame on qt-4.8.3 Shouldn't this be assigned to solid? yes *** Bug 309949 has been marked as a duplicate of this bug. *** Adding what the assertion is actually about: #9 0x00007f0b5465ade5 in _dbus_warn_check_failed (format=0x7f0b5466a5c0 "arguments to %s() were incorrect, assertion \"%s\" failed in file %s line %d.\nThis is normally a bug in some application using the D-Bus library.\n") at dbus-internals.c:290 Created attachment 76658 [details]
New crash information added by DrKonqi
krunner (0.1) on KDE Platform 4.9.5 using Qt 4.8.4
- What I was doing when the application crashed:
Just launched Krrunner, and tried to start an app.
By the backtraces it looks the same bug as reported... although this is the first time it happens on my system.
-- Backtrace (Reduced):
#6 0x0000003171235ba5 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:63
#7 0x0000003171237358 in __GI_abort () at abort.c:90
#8 0x0000003177e30ab5 in _dbus_abort () at dbus-sysdeps.c:94
#9 0x0000003177e27545 in _dbus_warn_check_failed (format=0x3177e36ee0 "arguments to %s() were incorrect, assertion \"%s\" failed in file %s line %d.\nThis is normally a bug in some application using the D-Bus library.\n") at dbus-internals.c:290
#10 0x0000003e7fc1c4b6 in q_dbus_pending_call_block (pending=<optimized out>) at qdbus_symbols_p.h:309
Created attachment 77209 [details]
New crash information added by DrKonqi
krunner (0.1) on KDE Platform 4.10.00 using Qt 4.8.4
- What I was doing when the application crashed:
I was simply typing a search term in krunner.
I am only adding this to tell that the bug still exists in 4.10
-- Backtrace (Reduced):
#8 0x00007f6200905415 in _dbus_abort () at dbus-sysdeps.c:94
#9 0x00007f62008fbee5 in _dbus_warn_check_failed (format=0x7f620090b840 "arguments to %s() were incorrect, assertion \"%s\" failed in file %s line %d.\nThis is normally a bug in some application using the D-Bus library.\n") at dbus-internals.c:290
#10 0x00007f6203b7c2e6 in q_dbus_pending_call_block (pending=<optimized out>) at qdbus_symbols_p.h:309
#11 QDBusConnectionPrivate::waitForFinished (this=0x2343770, pcall=0x7f61d00e74a0) at qdbusintegrator.cpp:1781
#12 0x00007f6203bbbc17 in QDBusPendingCallPrivate::waitForFinished (this=0x7f61d00e74a0) at qdbuspendingcall.cpp:245
This could be fixed by 06c934efdcdf3a8bb18982f53f9abcf2c67049d0 (in 4.10git and master) Basically, the runner was accessing the device from another thread, which can cause unexpected issues. Could anybody please check? If this is the case, I could backport to 4.9… Thanks Rex, did you have time to verify this? Interestingly, seems I had this krunner plugin enabled already on my unpatched 4.10.0, and hadn't experienced any related crashes. Unfortunately, that doesn't help explain the crash reported against 4.10.0 in comment #7 I tested with the aforementioned kde-workspace patch too, and no crash/regressions either. my laptop doesn't currently have any "removable devices", so let me put my cd/dvd drive back, and see if that makes any difference... no problems after adding drive with or without media in it now (patched). Let's go with this being fixed. thanks all. |