| Summary: | Amarok crashes after disabling nepomuk | ||
|---|---|---|---|
| Product: | nepomuk | Reporter: | Attilio Scotolati <nexor> |
| Component: | general | Assignee: | Nepomuk Bugs Coordination <nepomuk-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | matej, me |
| Priority: | NOR | ||
| Version: | 4.9 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Nepomuk collection shown as a disconnected removable drive in config
Backtrace with more debugging symbols |
||
|
Description
Attilio Scotolati
2012-12-25 20:12:40 UTC
Hi Attilio, (In reply to comment #0) > I've been trying out the nepomuk sync feature on the 2.7 beta (self compiled > from source package), and it doesn't work for me: the nepomuk collection is > not shown in "local music" and appears as a normal removable drive int the > "metadata" section of the settings. This is just perhaps a wrong icon, but all "Local Music" collections normally appear in the Metadata section Amarok Config. Please attach a screenshot if I didn't understand you properly. > At first I had tried the beta with nepomuk disabled, then enabled it (all > settings) and got no results because my music directory was linked through a > symlink, which aren't followed by current nepomuk. A Nepomuk bug/behaviour, not Amarok one. > Furthermore I can trigger a repetable crash by disabling the semantyc > desktop while amarok is running, then closing amarok: that gives the > attached backtrace. The backtrace contains unresolved symbols. Please install debugging symbols for qt-gui (qt-core seems to be already present), kdelibs and perhaps any other libraries that show up in the backtrace without line numbers and re-post the backtrace. Thanks. Created attachment 76021 [details] Nepomuk collection shown as a disconnected removable drive in config > This is just perhaps a wrong icon, but all "Local Music" collections > normally appear in the Metadata section Amarok Config. Please attach a > screenshot if I didn't understand you properly. Here's the screenshot. After a reboot the integration worked again: the nepomuk icon was shown next to the config entry, and the collection was visible in the left pane, though with only ~20 tracks, due to some problem with the scanner I believe... Disabling and re-enabling nepomuk in systemsettings caused the integration to fail again or, probably, it was nepomuk failing? The index service was reported as "not running", but desktop search was OK. Created attachment 76022 [details]
Backtrace with more debugging symbols
Attached a better backtrace. It looks different to me, but the trigger is the same:
1) enable nepomuk
2) start amarok
3) disable nepomuk
4) close amarok
Yes, the backtrace is indeed completely different, and indicates a problem with Soprano which Nepomuk uses: Please always paste backtraces in the comment, else those are not searchable: Thread 1 (Thread 0x7f3b25cf9780 (LWP 6824)): [KCrash Handler] #6 Soprano::Client::ClientConnection::isConnected (this=0x0) at /usr/src/debug/soprano-2.8.0/client/clientconnection.cpp:775 #7 0x00007f3b120c2d6e in Soprano::Client::ClientModel::~ClientModel (this=0x2df1aa0, __in_chrg=<optimized out>) at /usr/src/debug/soprano-2.8.0/client/clientmodel.cpp:53 #8 0x00007f3b120c2f69 in Soprano::Client::ClientModel::~ClientModel (this=0x2df1aa0, __in_chrg=<optimized out>) at /usr/src/debug/soprano-2.8.0/client/clientmodel.cpp:58 #9 0x00007f3af5c8a37e in ~GlobalModelContainer (this=0x1d3f830, __in_chrg=<optimized out>) at /usr/src/debug/nepomuk-core-4.9.4/libnepomukcore/resource/nepomukmainmodel.cpp:63 #10 destroy () at /usr/src/debug/nepomuk-core-4.9.4/libnepomukcore/resource/nepomukmainmodel.cpp:125 #11 0x00007f3b225048b1 in __run_exit_handlers () from /lib64/libc.so.6 #12 0x00007f3b22504935 in exit () from /lib64/libc.so.6 #13 0x00007f3b224ee45c in __libc_start_main () from /lib64/libc.so.6 #14 0x000000000040bdbd in _start () at ../sysdeps/x86_64/elf/start.S:113 Adapt bug summary. We're not sure what causes this, but we think our changes should have fixed it. Lets see if we get any bugs reports for 4.10 RC2. *** This bug has been marked as a duplicate of bug 305312 *** |