soprano crashes on multiple simultaneous queries
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
soprano (Ubuntu) |
Fix Released
|
Medium
|
Jonathan Thomas | ||
Lucid |
Fix Released
|
Medium
|
Jonathan Thomas |
Bug Description
##SRU Info added by Jonathan Thomas##
Impact: Makes the bangarang package largely unusable.
Addressed by: Upstream released a fix in soprano 2.4.3. Once maverick opens, this version will be uploaded.
Patch: I took the svn commit mentioned in comment #1 from upstream svn and applied it to the current lucid package. The patch fixes the isConnected() function so that a new ClientModel is not made for each soprano query.
Testcase: Scroll through all the items in the "Media List" side-pane. Doing it too fast will cause the crash.
Regression potential: Pretty low, small patch. Non-intrusive.
#######
Binary package hint: libsoprano4
Found in Kubuntu 10.04
libsoprano4 package version 2.4.2
There is a bug in Soprano 2.4.2 that causes a crash when multiple simultaneous nepomuk queries are launched. This can be replicated in the packaged version of Bangarang (1.0.1) and in the developement version of bangarang. It may be possible in other ways, maybe by attempting to do simultaneous searches in Dolphin.
Soprano 2.4.3, released on April 24th, 2010, fixes the issue.
Related branches
Changed in soprano (Ubuntu): | |
importance: | Undecided → Medium |
status: | Triaged → In Progress |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Changed in soprano (Ubuntu Lucid): | |
assignee: | nobody → Jonathan Thomas (echidnaman) |
importance: | Undecided → Medium |
milestone: | none → lucid-updates |
Changed in soprano (Ubuntu Lucid): | |
status: | New → In Progress |
We can push through the crash fix as an Stable Release Update: http:// websvn. kde.org/ ?view=revision& revision= 1117465
(Once we get the packages into lucid-proposed, we'll need testers to test to see if the bug works/to see if there are any regressions)
We can't introduce the new version, though, since it's not absolutely certain that there won't be regressions with the other changes the new version introduces.