Summary: | KRunner crash when launching program. program still launches after big delay (massive random crashes) [invalid [_dbus_pthread_mutex_lock], _dbus_connection_lock, _dbus_pending_call_get_connection_and_lock, reply_handler_timeout (Thread 1)] | ||
---|---|---|---|
Product: | [Plasma] krunner | Reporter: | matthias sweertvaegher <matthias.sweertvaegher> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED UPSTREAM | ||
Severity: | crash | CC: | andresbajotierra, assyr, bugs.kde.org, chgonzalezg, grosser.meister.morti, grzesiu.gostomski, lapinkiller, Maxim.Prohorenko, ndbecker2, null, paul.f.fee, petrielmjr, sebastian, yiorgos-lists |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
Description
matthias sweertvaegher
2010-01-24 23:51:08 UTC
Created attachment 40231 [details]
New crash information added by DrKonqi
Tried a couple of times to use the calculator pluin. In all cases, krunner simply hanged while I was typing the numbers.
In each of the cases, krunner closed after 30-45 seconds without crashing.
After the third time, I open okular from konsole, and krunner crashed. (Which most likely had nothing to do with okular, and everything to do with some inside timer that went bust...)
We will be tracking similar bugs at bug 230520. From bug 224368: -- Information about the crash: I've used krunner to fire up urxvt and after some time (5~15 s) it crashed. From bug 231365: -- Information about the crash: alt+F2 typed "ssh -l root -X anothersystem quanta" + pressed <enter> (this a system that I can login via passphrase-locked keys. keys were currently unlocked. command succeded but after krunned crashed not always replicable From bug 228889: -- Information about the crash: I just started kopete through krunner and then hit alt+f2 again in order to start another program. But instead of the krunner window I got a crash. Also ever since KDE 4.4 krunner randomly hangs: no reaction to any imput, no redraw but also no high cpu or harddisk usage. Usually it unhangs after a (long) while. So under KDE 4.4 krunner became practically unusable and I more often use yakuake to start applications. *** Bug 224368 has been marked as a duplicate of this bug. *** *** Bug 231365 has been marked as a duplicate of this bug. *** *** Bug 228889 has been marked as a duplicate of this bug. *** From bug 229138: -- Information about the crash: I was using the calculator (simple expression) when KRunner crashed. Trying a related expression again did not trigger a crash. Also, when editing KRunner would sometimes take a long time finding an answer, and sometimes become completely unresponsive for perhaps 30 seconds. *** Bug 229138 has been marked as a duplicate of this bug. *** This could be also related to bug 209436... Thiago suggested to upgrade to D-Bus 1.2.22 to fix those issues *** Bug 231779 has been marked as a duplicate of this bug. *** *** Bug 232067 has been marked as a duplicate of this bug. *** *** Bug 232201 has been marked as a duplicate of this bug. *** From bug 233810: -- Information about the crash: Reboot, login to KDE, first run alt+f2 type man:git enter or type man and select line from list by mouse. Crash I try to reproduce crash, type 'man' and when type ':' dialog freeze (5-10 s.) Can't reproduce now. *** Bug 233810 has been marked as a duplicate of this bug. *** From bug 233810 Name : dbus Arch : x86_64 Epoch : 1 Version : 1.2.16 Release : 9.fc12 Size : 471 k Repo : installed From repo : updates Name : kdelibs Arch : x86_64 Epoch : 6 Version : 4.4.2 Release : 1.fc12 Size : 46 M Repo : installed From repo : kde-testing *** Bug 234431 has been marked as a duplicate of this bug. *** Created attachment 42917 [details]
New crash information added by DrKonqi
Krunner crashed just after launching kate...
kate has been correctly launched
it's not the first time krunner chrash, but i don't rember which commands i have executed ...
PS : sorry for my bad englsih im' french...
I get the same stack trace with Fedora 13, KDE 4.4.3, dbus 1.2.24. This bug is marked resolved upstream, is there info on which component causes the crash and which release (if any) contains the fix? Thanks. |