Banshee crashing after launching

Could you follow the instructions in
https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1044842/comments/3 to
obtain the Banshee debug log and stack trace please from the crash please?

  status incomplete

--
Kind regards,
Loong Jin

I ran "banshee --debug" in a terminal but it stops responding at;

ERROR: Caught a segmentation fault while loading plugin file:
/usr/lib/x86_64-linux-gnu/gstreamer-0.10/libgsttypefindfunctions.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap --gst-disable-registry-fork and debug.

If I have done right you should find the two attached files below

The two attachments should be as per the instructions now. Let me know if you need anything else.

Thanks

Hmm, you're missing symbols in the gdb output. Could you install dbus-1-dbg and redo that please?

Installed the package, but I am still seeing a "no debugging symbols found" output in gbd.

Also instead of crashing, banshee is now freezing (going grey) and doing nothing when I run with the gbd process. Just running 'banshee --debug' causes it to launch and crash within seconds, but when I am quick enough to get into the gbd terminal it just freezes up.

I should add that once I quit the gbd process the 'banshee --debug' process continues and then crashes with the message;

Stacktrace:

Native stacktrace:

Segmentation fault (core dumped)

The segmentation fault was to be expected from that error. As for "no debugging symbols found", that's also to be expected, but you should be seeing some symbol names in the stack trace rather than ?? in the stack trace.

I have tried multiple time and have left the process running for several hours trying to get the gbd process to run simultaneously but the whole thing keeps freezing. I use the 'cont' command to move it along, but eventually banshee --debug ends and there is 'no stack' for the 'bt full' command.

The latest uploads should illustrate that. Hopefully the debug symbols are working too. Let me know if I can provide anything else

On 11/09/2012 00:11, Keith Drummond wrote:
> I have tried multiple time and have left the process running for several
> hours trying to get the gbd process to run simultaneously but the whole
> thing keeps freezing. I use the 'cont' command to move it along, but
> eventually banshee --debug ends and there is 'no stack' for the 'bt
> full' command.
>
> The latest uploads should illustrate that. Hopefully the debug symbols
> are working too. Let me know if I can provide anything else
>

You typed in one 'cont' too many. Please use 'bt full' after the SIGABRT -- if
you cont at that point, the program terminates and the stack disappears.

--
Kind regards,
Loong Jin

Thanks for pointing out my mistake! Hopefully these are what you have been looking for.

Great, thanks. Let me just whip up a small patch for you to test.

https://launchpad.net/~hyperair/+archive/test-11048341-fix <-- Try activating this PPA and testing the libgconf2-4 package there, then see if the issue persists.

You'll have to wait for a while though -- it doesn't look like the package has appeared on the PPA yet.

Got the updates from the PPA.

Banshee launches. The first time everything ran very slowly, Banshee kept freezing/unfreezing and the media keys on my keyboard would not work. I closed Banshee after about 10 mins. Opened again and now it seems to be working fine. Playing music now and it has not frozen or crashed.

Do you require any logs or other information?

Thanks again for all the help.

Great! Could you try playing with the settings a little? Just toggle a couple of settings here and there and see if it crashes. Also, if you could get the output of "banshee --debug" for the freezing/unfreezing, that would also be great.

Have restarted the computer several times now and that freeze/unfreeze effect has not reoccurred, it was just the first run after the updates.

Have added and removed a few extensions. Ticked/unticked various items, tried running all the various extensions and there has been no crashes, freezes or other instability I can see. Just been playing with playlists and so on, and all seems stable.

On 11/09/2012 12:46, Keith Drummond wrote:
> Have restarted the computer several times now and that freeze/unfreeze
> effect has not reoccurred, it was just the first run after the updates.
>
> Have added and removed a few extensions. Ticked/unticked various items,
> tried running all the various extensions and there has been no crashes,
> freezes or other instability I can see. Just been playing with playlists
> and so on, and all seems stable.
>

Great! In that case, I'll just mark the Banshee task as invalid, and attach the
patch for gconf.

  affects ubuntu/banshee
  status invalid
  subscribe ubuntu-sponsors

--
Kind regards,
Loong Jin

This bug was fixed in the package gconf - 3.2.5-0ubuntu3

---------------
gconf (3.2.5-0ubuntu3) quantal; urgency=low

  * debian/patches/call-dbus_g_thread_init.patch:
    - Initialize dbus threads before doing anything. This fixes crashes in
      multithreaded applications that don't use libdbus directly. (LP: #1048341)
 -- Chow Loong Jin <email address hidden> Tue, 11 Sep 2012 10:12:41 +0800

Janitor, on ArchLinux there is the same problem now and your patch fix the crashes.

I have opened a bug report on the gnome bugzilla before I found your patch, and now I know it fix the problem I would like to have the bug number of this bug of GConf please, a banshee developer needs it.

Thanks !

On 26/11/2012 09:41, A-ruhier wrote:
> Janitor, on ArchLinux there is the same problem now and your patch fix
> the crashes.
>
> I have opened a bug report on the gnome bugzilla before I found your
> patch, and now I know it fix the problem I would like to have the bug
> number of this bug of GConf please, a banshee developer needs it.
>
> Thanks !
>

Hey A-ruhier,

The gconf bug link is above (ctrl+f for gnome-bugs). Also, janitor is a bot.
Could you post the link to the upstream Banshee bug please?

There's also a banshee-list discussion about this at
http://thread.gmane.org/gmane.comp.gnome.mono.banshee/13247, if you weren't
already aware about this.

--
Kind regards,
Loong Jin

Here is the link for the bug report : https://bugzilla.gnome.org/show_bug.cgi?id=688845

And shame on me to answer it to a bot :p
Thanks for your answer !