After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 616654 - Enabling lyrics or Wikipedia extension crashes Banshee
Enabling lyrics or Wikipedia extension crashes Banshee
Status: RESOLVED DUPLICATE of bug 613217
Product: banshee
Classification: Other
Component: Community Extensions
1.6.0
Other Linux
: Normal critical
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-04-23 14:39 UTC by Atri
Modified: 2010-04-24 09:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
kill -s QUIT $(pidof banshee-1); cp ~/.config/banshee-1/log ~/Desktop/banshee.log (5.53 KB, text/x-log)
2010-04-23 14:39 UTC, Atri
Details
strace log while making banshee crash (150.71 KB, application/x-gzip)
2010-04-23 14:42 UTC, Atri
Details

Description Atri 2010-04-23 14:39:44 UTC
Created attachment 159433 [details]
kill -s QUIT $(pidof banshee-1); cp ~/.config/banshee-1/log ~/Desktop/banshee.log

On openSUSE 11.2 enabling the community extension lyrics or Wikipedia crashes Banshee everytime. As a result these extensions never work.
Comment 1 Atri 2010-04-23 14:42:30 UTC
Created attachment 159434 [details]
strace log while making banshee crash

Additional information:
This is on an x86_64 system with banshee (1.6.0) from http://download.opensuse.org/repositories/Banshee/openSUSE_11.2/
Comment 2 Kevin Duffus 2010-04-23 20:06:50 UTC
Check your installation. It appears that Webkit sharp (webkit-1.0.so.1) is missing from your system.

On a side note, I'd say it would be more sane if an exception like this could be propagated back up the stack where Banshee could then unload the extension and present an error message.
Comment 3 Bertrand Lorentz 2010-04-24 09:42:55 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

It's a problem with webkit-sharp on your system. See bug #613217 for info on how to fix this manually.

*** This bug has been marked as a duplicate of bug 613217 ***