| Summary: | KRunnner autocompletion crash (DBus 1.4.0) [_dbus_abort. _dbus_warn_check_failed, q_dbus_pending_call_block, QDBusConnectionPrivate::waitForFinished, ..., KGetRunner::parseUrls] | ||
|---|---|---|---|
| Product: | [Plasma] krunner | Reporter: | Jan Essert <netz> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | andresbajotierra, diego.ml, giecrilj, kget, maarten, mat69, rdieter, xenomorph, zilti |
| Priority: | NOR | ||
| Version: | 4.6.2 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
Jan Essert
2010-12-14 18:48:25 UTC
[Comment from a bug triager] Likely to be connected with bug 240689, which also mentions the KGet runner. *** Bug 240689 has been marked as a duplicate of this bug. *** Created attachment 56184 [details]
New crash information added by DrKonqi
krunner (0.1) on KDE Platform 4.5.5 (KDE 4.5.5) using Qt 4.7.1
- What I was doing when the application crashed:
Alt+F2 -> KRunner appears -> KRunner crashes
KGet opened.
-- Backtrace (Reduced):
#8 0x0000003f390304f5 in _dbus_abort () at dbus-sysdeps.c:94
#9 0x0000003f39027435 in _dbus_warn_check_failed (format=0x3f39036628 "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
#10 0x000000336981a185 in q_dbus_pending_call_block (this=0x7152b0, pcall=0x7fa144011090) at qdbus_symbols_p.h:305
#11 QDBusConnectionPrivate::waitForFinished (this=0x7152b0, pcall=0x7fa144011090) at qdbusintegrator.cpp:1718
#12 0x0000003369858f93 in QDBusPendingCallPrivate::waitForFinished (this=0x7fa144011090) at qdbuspendingcall.cpp:242
Created attachment 56945 [details]
New crash information added by DrKonqi
krunner (0.1) on KDE Platform 4.6.00 (4.6.0) "release 376" using Qt 4.7.1
- What I was doing when the application crashed:
told KRunner to launch ~/.gpg-agent-info
Pressed the Open action using the mouse button
-- Backtrace (Reduced):
#8 0x00007f40c6283075 in _dbus_abort () from /lib64/libdbus-1.so.3
#9 0x00007f40c6279ff5 in _dbus_warn_check_failed () from /lib64/libdbus-1.so.3
#10 0x00007f40c8feaab5 in q_dbus_pending_call_block (this=0x6a22c0, pcall=0x894020) at qdbus_symbols_p.h:305
#11 QDBusConnectionPrivate::waitForFinished (this=0x6a22c0, pcall=0x894020) at qdbusintegrator.cpp:1718
#12 0x00007f40c9029fc3 in QDBusPendingCallPrivate::waitForFinished (this=0x894020) at qdbuspendingcall.cpp:242
Created attachment 57206 [details]
New crash information added by DrKonqi
krunner (0.1) on KDE Platform 4.6.00 (4.6.0) using Qt 4.7.1
- What I was doing when the application crashed:
I pressed ALT-F2 and then started typing my query. KRunner crashed before I finished typing.
Version of D-Bus installed: 1.4.1.
-- Backtrace (Reduced):
#8 0x00007fc891792075 in _dbus_abort () at dbus-sysdeps.c:94
#9 0x00007fc891788ff5 in _dbus_warn_check_failed (format=
0x7fc8917982d0 "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
#10 0x00007fc8944f8ab5 in q_dbus_pending_call_block (this=0x6e65c0, pcall=0x7fc8681037b0) at qdbus_symbols_p.h:305
#11 QDBusConnectionPrivate::waitForFinished (this=0x6e65c0, pcall=0x7fc8681037b0) at qdbusintegrator.cpp:1718
#12 0x00007fc894537fc3 in QDBusPendingCallPrivate::waitForFinished (this=0x7fc8681037b0) at qdbuspendingcall.cpp:242
Created attachment 58713 [details]
New crash information added by DrKonqi
krunner (0.1) on KDE Platform 4.6.1 (4.6.1) using Qt 4.7.1
- What I was doing when the application crashed:
Alt+F2 -> type -> crash.
Also this time KGet was opened, this still applies in KDE 4.6.1.
dbus-1.4.0-2.fc14.x86_64
-- Backtrace (Reduced):
#8 0x0000003b022304f5 in _dbus_abort () at dbus-sysdeps.c:94
#9 0x0000003b02227435 in _dbus_warn_check_failed (format=0x3b02236628 "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
#10 0x00000033f141a185 in q_dbus_pending_call_block (this=0x108ada0, pcall=0x7f5e30003b00) at qdbus_symbols_p.h:305
#11 QDBusConnectionPrivate::waitForFinished (this=0x108ada0, pcall=0x7f5e30003b00) at qdbusintegrator.cpp:1718
#12 0x00000033f1458f93 in QDBusPendingCallPrivate::waitForFinished (this=0x7f5e30003b00) at qdbuspendingcall.cpp:242
Created attachment 59911 [details]
New crash information added by DrKonqi
krunner (0.1) on KDE Platform 4.6.2 (4.6.2) using Qt 4.7.2
- What I was doing when the application crashed:
Alt+F2 - started typing "firefox" -> crash
dbus-1.4.0-2.fc14.x86_64
-- Backtrace (Reduced):
#8 0x0000003b022304f5 in _dbus_abort () at dbus-sysdeps.c:94
#9 0x0000003b02227435 in _dbus_warn_check_failed (format=0x3b02236628 "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
#10 0x000000373681a285 in q_dbus_pending_call_block (this=0x1f2fe00, pcall=0x7f22a0006570) at qdbus_symbols_p.h:305
#11 QDBusConnectionPrivate::waitForFinished (this=0x1f2fe00, pcall=0x7f22a0006570) at qdbusintegrator.cpp:1739
#12 0x0000003736858df3 in QDBusPendingCallPrivate::waitForFinished (this=0x7f22a0006570) at qdbuspendingcall.cpp:242
Created attachment 59962 [details]
New crash information added by DrKonqi
krunner (0.1) on KDE Platform 4.6.2 (4.6.2) using Qt 4.7.2
- What I was doing when the application crashed:
Started typing "it2en: tecnico installatore", but it crashed before I could type the whole string.
$ rpm -q dbus
dbus-1.4.0-2.fc14.x86_64
-- Backtrace (Reduced):
#8 0x0000003b022304f5 in _dbus_abort () at dbus-sysdeps.c:94
#9 0x0000003b02227435 in _dbus_warn_check_failed (format=0x3b02236628 "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
#10 0x000000373681a285 in q_dbus_pending_call_block (this=0xf26e00, pcall=0x7fd55401c9c0) at qdbus_symbols_p.h:305
#11 QDBusConnectionPrivate::waitForFinished (this=0xf26e00, pcall=0x7fd55401c9c0) at qdbusintegrator.cpp:1739
#12 0x0000003736858df3 in QDBusPendingCallPrivate::waitForFinished (this=0x7fd55401c9c0) at qdbuspendingcall.cpp:242
Found a way to always reproduce on my system: KRunner -> start typing "it2en: blah blah blah" and so on. Continuing writing random chars makes KRunner crash at some point. I'd like to provide a full Valgrind log, if I'm able to. Is there a way I can attach valgrind to KRunner while running or should I just kill KRunner and then start it from command line? Any option you'd like me to put in valgrind command line? Thanks. For the record, ABRT report: https://bugzilla.redhat.com/show_bug.cgi?id=704474 Thank you for the information. I think kquitapp krunner and then simply krunner should be enough. Maybe krunner --nofork is needed, though I am not sure on that. Btw. interestingly I was finally able to reproduce a crash with what you described on #9 but only with my regular account, not with the devel one. (In reply to comment #10) > Thank you for the information. > I think kquitapp krunner and then simply krunner should be enough. > Maybe krunner --nofork is needed, though I am not sure on that. Interestingly it doesn't crash under Valgrind... it should be a nasty threading issue. > Btw. interestingly I was finally able to reproduce a crash with what you > described on #9 but only with my regular account, not with the devel one. What do you mean with the "devel account"? Running 4.7 currently in development or just with another user account? What's your DBus version? Well I have 4.6.2 here and also an own account where I run master/trunk. It crashes in the first with your method but not in the later. You see the problem is that I don't know what is wrong with that line, for me it is valid code that tends to crash sometime for some users. :/ I guess I should remove the check where it crashes altogether. Better to not always correctly identify downloadable urls than having a program crashing. Ideally I'd digg into dbus to see what goes wrong, though I doubt that I'll have time for that atm. The dbus version I have is 1.4.8. Just in case this is what I get when starting krunner in the terminal and crashing it: process 13567: arguments to dbus_pending_call_block() were incorrect, assertion "pending != NULL" failed in file dbus-pending-call.c line 704. This is normally a bug in some application using the D-Bus library. D-Bus not built with -rdynamic so unable to print a backtrace SVN commit 1231749 by mfuchs: Workaround: KGet runner does not use the KGet interface anymore. That way a crash in upstream is worked around. TODO: Reenable once the bug has been fixed upstream. CCBUG:259873 M +8 -2 kgetrunner.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1231749 *** Bug 267932 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 297502 *** |