Summary: | Crash in ResourceWatcher - DBusPendingCall | ||
---|---|---|---|
Product: | [Unmaintained] nepomuk | Reporter: | Hrvoje Senjan <hrvoje.senjan> |
Component: | libnepomukcore | Assignee: | Nepomuk Bugs Coordination <nepomuk-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | alexey.uvarov, bladud, fabian, ht990332, ivan.cukic, j.mairboeck, kde, me, nepomuk-bugs, plasma-bugs |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/nepomuk-core/fa9c575e368d9d99e175e0e1392989e026c99913 | Version Fixed In: | 4.10.3 |
Sentry Crash Report: |
Description
Hrvoje Senjan
2012-08-12 14:28:33 UTC
(In reply to comment #0) > Application: kactivitymanagerd (3.0) > KDE Platform Version: 4.9.00 "release 1" (Compiled from sources) > Qt Version: 4.8.2 > Operating System: Linux 3.4.6-1.1-desktop x86_64 > Distribution: "openSUSE 12.2 (x86_64)" > > -- Information about the crash: > - What I was doing when the application crashed: > > ... all of the sudden. Doing nothing much. Not true. Happens every time i right click on a file in dolphin/konqueror (this also includes right clicking on a link in koqnueror). The activity manager crashes when you click a link in konqueror? As far as I can see in the backtrace, the crash is in libnepomuk2 (ResourceWatcher does it for some reason). Nope, it crashed every time i right clicked a link/file/folder within dolphin and/or konqueror. I have in the meantime disabled activity linking service, and using s-l-c. Gonna re-enable the service and see is this still here. *** Bug 313089 has been marked as a duplicate of this bug. *** *** Bug 311526 has been marked as a duplicate of this bug. *** The above linked crashes are not line-by-line identical, but all are regarding DBus and ResourceWatcher. *** Bug 314820 has been marked as a duplicate of this bug. *** *** Bug 314700 has been marked as a duplicate of this bug. *** *** Bug 314538 has been marked as a duplicate of this bug. *** Git commit cf6a1316df282c3c7e99d952e9fc351498d5f9a4 by Simeon Bird. Committed on 12/03/2013 at 04:38. Pushed by sbird into branch 'feature/resourcemanagercleanup'. ResourceManager/ResourceWatcher: Make removeResource and addResource happen in the ResourceWatcher thread via a QAutoConnection, avoiding the thread unsafety of QDBusConnection and thus the crash. Add convenience functions to the ResourceWatcher that start and stop it if necessary, so that we don't have to jump back and forth between threads. FIXED-IN: 4.10.2 M +16 -0 libnepomukcore/datamanagement/resourcewatcher.cpp M +20 -0 libnepomukcore/datamanagement/resourcewatcher.h M +4 -14 libnepomukcore/resource/resourcemanager.cpp http://commits.kde.org/nepomuk-core/cf6a1316df282c3c7e99d952e9fc351498d5f9a4 I can't reproduce the crash myself, so it would be great if someone who can could check that the feature/resourcemanagercleanup branch does. Ideally you should use the latest kde-workspace KDE/4.10 branch as well, due to an interaction with a (fixed in 4.10.2) plasma bug. Or the easy way is to just wait until 4.10.2 is released Git commit fa9c575e368d9d99e175e0e1392989e026c99913 by Simeon Bird. Committed on 16/03/2013 at 21:27. Pushed by sbird into branch 'KDE/4.10'. Fix bad threading in ResourceManagerPrivate::addToWatcher dbus usage. Instead of doing MoveToThread, take the resourceManager mutex before talking to the ResourceWatcher. This is a lot clearer and less racy. It should not be too contended now the rm mutex is not held over the socket communication. FIXED-IN: 4.10.3 M +8 -0 libnepomukcore/resource/resourcedata.cpp M +15 -18 libnepomukcore/resource/resourcemanager.cpp http://commits.kde.org/nepomuk-core/fa9c575e368d9d99e175e0e1392989e026c99913 |