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 695975 - SIGABRT crash when banshee finishes a track
SIGABRT crash when banshee finishes a track
Status: RESOLVED DUPLICATE of bug 692374
Product: banshee
Classification: Other
Component: general
2.6.0
Other Linux
: Normal major
: ---
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-03-16 20:05 UTC by cs
Modified: 2013-03-16 20:52 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
debug log (61.25 KB, text/x-log)
2013-03-16 20:05 UTC, cs 		Details

Description cs 2013-03-16 20:05:42 UTC 
Created attachment 239036 [details]
debug log

After updating banshee to 2.6.0, it started to crash with a SIGABRT every time a song finished playing and the next one started. I attached a debug log this bug report. From the log, it looks like this could have something to do with GTK or GNOME but banshee is the only application crashing after the update. Everything else works fine.

I can reproduce the crash everytime by starting banshee, playing an arbitary track and wait for the track to finish. Sometimes I can hear the next track starting already with the gapless playback but a soon as the first track finishes, banshee crashes with a SIGABRT.

Repairing the database as described in http://banshee.fm/support/faq/ also doesn't change anything.

I an running Banshee 2.6.0 on Fedora 18 (Build Date 2012-10-11 14:08:49 UTC) on a Linux i686 3.8.1-201 kernel with Mono 2.10.8 and GTK 2.24.16.

Please tell me if I can help by providing any additional information.
Comment 1 Andrés G. Aragoneses (IRC: knocte) 2013-03-16 20:52:42 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.

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