| Summary: | KRunner randomly crashing | ||
|---|---|---|---|
| Product: | [Unmaintained] solid | Reporter: | Steffen Buechner <steffen.buechner> |
| Component: | libsolid-udisks2 | Assignee: | Lukáš Tinkl <lukas> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | crash | CC: | afiestas, dima, evgenyi, jlp, kde, mail, marcel.wiesweg, nico.kruber, richard.llom, robert, ry, shaunteasdale+kde, spiderbill, sven.burmeister, victor.sverdlin |
| Priority: | NOR | ||
| Version: | 4.10.0 | ||
| Target Milestone: | 4.11 | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| See Also: | https://bugreports.qt-project.org/browse/QTBUG-27809 | ||
| Latest Commit: | Version Fixed In: | qt-4.8.6 | |
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
||
|
Description
Steffen Buechner
2013-03-08 13:05:54 UTC
Can you reproduce this from time to time or happened just once? I ask because you said randomly while in the report say every time. Hi, it happens almost every time. It occurs right before krunner displays its suggestions. Sometimes i think it depends on how fast i type. However, the first entered characters have to make sense to reproduce the error. If i type smth. like "asdfuaji" nothing happens because there are no items that start with this String. If i Enter nothing, krunner doesnt crash. Unfortunately, right now, i have no access to the machine, where the error has eben reported from (next on Sunday this week). Hope that helps. *** Bug 317610 has been marked as a duplicate of this bug. *** update report status Created attachment 79539 [details]
New crash information added by DrKonqi
krunner (0.1) on KDE Platform 4.10.2 using Qt 4.8.4
- What I was doing when the application crashed:
Typed in deleted and retyped several words in krunner. Then crash whilst typing.
-- Backtrace (Reduced):
#10 0x00007f527064104b in q_dbus_pending_call_block (pending=<optimized out>) at qdbus_symbols_p.h:309
#11 QDBusConnectionPrivate::waitForFinished (this=0x1513640, pcall=0x7f5230081040) at qdbusintegrator.cpp:1781
#12 0x00007f52706855c0 in QDBusPendingCallPrivate::waitForFinished (this=0x7f5230081040) at qdbuspendingcall.cpp:245
#13 0x00007f527068726e in QDBusPendingReplyData::argumentAt (this=0x7f52468c5b20, index=0) at qdbuspendingreply.cpp:264
[...]
#16 0x00007f52686e5a3e in Plasma::AbstractRunner::performMatch (this=0x19e8ee0, localContext=...) at /chakra/desktop-testing/kdelibs/src/kdelibs-4.10.2/plasma/abstractrunner.cpp:136
This is a bug in Qt, confirmed with fix WIP: https://bugreports.qt-project.org/browse/QTBUG-27809 Fix will be released in Qt 4.8.6 Thanks for reporting ! *** Bug 313114 has been marked as a duplicate of this bug. *** *** Bug 308320 has been marked as a duplicate of this bug. *** *** Bug 297385 has been marked as a duplicate of this bug. *** *** Bug 254034 has been marked as a duplicate of this bug. *** *** Bug 211503 has been marked as a duplicate of this bug. *** *** Bug 314014 has been marked as a duplicate of this bug. *** *** Bug 297502 has been marked as a duplicate of this bug. *** *** Bug 279066 has been marked as a duplicate of this bug. *** *** Bug 300246 has been marked as a duplicate of this bug. *** *** Bug 322335 has been marked as a duplicate of this bug. *** Created attachment 85571 [details]
New crash information added by DrKonqi
krunner (4.10.5) on KDE Platform 4.10.5 using Qt 4.8.4
- What I was doing when the application crashed:
ALT+F2
type symbol: =
98798+987987+987987+987987+987987+
the last typing of mathematic sign "plus" was the reason of mistake
-- Backtrace (Reduced):
#8 0x4d4b694f in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#9 0x4d4b82a3 in __GI_abort () at abort.c:91
#10 0x43a6f645 in _dbus_abort () at dbus-sysdeps.c:94
#11 0x43a64e36 in _dbus_warn_check_failed (format=0x43a754dc "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:289
#12 0x43a5b0fe in dbus_pending_call_block (pending=0x0) at dbus-pending-call.c:704
|