FS#31218 - [banshee, gstreamer0.10-ffmpeg] crashes after song advance

Attached to Project: Arch Linux
Opened by George (gh403) - Tuesday, 21 August 2012, 03:48 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 31 October 2012, 09:23 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Isenmann Daniel (ise)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Banshee segfaults with no warning when the song advances, typically within a couple of seconds of advance. The choice of song does not affect the behaviour, and I've tried deleting all config/cache directories.

Additional info:
* package version: 2.4.1-1
* banshee terminal output is attached


Steps to reproduce:
1. Launch Banshee
2. Play any song
3. Banshee will either crash within a few seconds or after song advances
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 31 October 2012, 09:23 GMT
Reason for closing:  Fixed
Additional comments about closing:  This was a bug in gconf. Should be fixed in 3.2.5-3.
Comment by Tanner Danzey (arkaniad) - Tuesday, 21 August 2012, 05:22 GMT
Interesting.

Look here:

> warning: File "/usr/bin/mono-gdb.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
> warning: Could not load shared library symbols for linux-vdso.so.1.
> Do you need "set solib-search-path" or "set sysroot"?

Do you have anything special set up? I'm running the same version of Banshee on the same architecture and this isn't happening to me.

Comment by George (gh403) - Tuesday, 21 August 2012, 05:29 GMT
"Do you have anything special set up?" -- No, not that I'm aware. Everything is stock--just "pacman -S banshee" and launch, doing all config within Banshee itself. I am using KDE 4.9.00 but Banshee should pull everything it needs when it installs. I also have gdb installed, which may be what it is complaining about in the lines you quoted.

Possibly (based on the error log) this is a mono bug instead, but I don't know enough about it to diagnose it correctly.

Interestingly, that particular backtrace doesn't seem to be repeated. I tried it again and got the wildly different output, attached.

Would you like a list of installed software?
Comment by Tanner Danzey (arkaniad) - Tuesday, 21 August 2012, 05:41 GMT
No, but try the command "pacman -Qs gconf" to see what gconf-related packages are installed.

I'm by far not an expert on debugging so if someone with a better idea comes along, take their advice.. however, if you look at the top part of the stack trace:

> Stacktrace:

at (wrapper managed-to-native) GConf.Client.gconf_client_get (intptr,string,intptr&) <0xffffffff>
at GConf.Client.Get (string) <0x0003f>

Assuming the trace runs the way i assume it does, it looks like it's having problems with GConf.

But yeah, shot in the dark.
Comment by Tanner Danzey (arkaniad) - Tuesday, 21 August 2012, 05:42 GMT
Whoa, interesting. New stack trace looks like a GTK failure of some sort.

The plot thickens.

Do you get different errors every single time? If you do it could very well be a mono bug / discrepancy.
Comment by George (gh403) - Tuesday, 21 August 2012, 05:51 GMT
Yup, again it's different, although this time it resembles the first. The new trace is attached, if you're interested.

The only gconf-related packages are:
local/gconf 3.2.5-2
A configuration database system
local/gconf-sharp 2.24.2-2
Mono bindings for GConf
local/pkg-config 0.27-1 (base-devel)
A system for managing library compile/link flags

pkg-conf seems to be a false positive (matching the pkG-CONF and ignoring the dash).
Comment by Tanner Danzey (arkaniad) - Tuesday, 21 August 2012, 05:55 GMT
Good grief. GConf looks fine, but should DBus be running / is it running? Is it enabled in /etc/rc.conf?

>(Banshee:15455): GConf-WARNING **: The connection to DBus was broken. Can't reinitialize it.
[Warn 00:46:10.920] Could not read GConf key sources.MusicLibrarySource-Library.separate_by_type - GLib.GException: No D-BUS daemon running
Comment by George (gh403) - Tuesday, 21 August 2012, 06:04 GMT
Dbus is running; it's set in rc.conf to start at boot (besides, KDE doesn't get too far without it :-) . I tried "sudo rc.d restart dbus" but it doesn't help.
Comment by Tanner Danzey (arkaniad) - Tuesday, 21 August 2012, 06:12 GMT
Hm. I'm at a loss, but I believe that somewhere the glue between Mono and GTK/Gnome/GConf is broken. Which really sucks, because Banshee is amazing.

I hope someone else has an idea. Sorry for my lack of help :P
Comment by George (gh403) - Tuesday, 21 August 2012, 06:26 GMT
I'm now out of ideas too... The only other thing I tried was (superstitiously?) reinstalling all the dbus-related packages and then just rebooting. The problem persists, with yet another interesting trace (attached). This one just plain has no information, like the program died too quickly to leave a will :D.

Tanner (and anyone else who looks at this), thanks for your time... Hopefully I can nail this down.
Comment by Xeno Daphron (Daphron) - Wednesday, 22 August 2012, 15:15 GMT
Try removing gstreamer0.10-ffmpeg and see if that does it. It still yells about the dbus connection but I can play local music without segfaults.
Comment by George (gh403) - Thursday, 23 August 2012, 02:01 GMT
Weird. Now I can't make it crash--it is working properly! Adding/removing gstreamer0.10-ffmpeg has no effect (of course, it's working right now and I couldn't get it to crash...).

However. Looking at the banshee log from a normal run [attached], it looks way different than one of the logs when it crashed... There is no mention whatsoever of dbus. (The album art messages are me skipping songs trying to get it to crash.) Based on this I'd say this is almost certainly related to dbus somehow.

Edit: Well, maybe not... After looking back over the logs not all of them mention dbus either. Is there a way to do the equivalent of a gdb on banshee (it's a Mono application, so is it different)? It would be nice to be able to figure out exactly where this is going wrong.
Comment by Alexander F. Rødseth (xyproto) - Tuesday, 11 September 2012, 05:35 GMT
Here is some information about debugging with mono: http://www.mono-project.com/Debugging

Loading...