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
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
|
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.
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.
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.
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?
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.
The plot thickens.
Do you get different errors every single time? If you do it could very well be a mono bug / discrepancy.
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).
>(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
I hope someone else has an idea. Sorry for my lack of help :P
Tanner (and anyone else who looks at this), thanks for your time... Hopefully I can nail this down.
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.