Banshee quite often crashes on load or on next track or on import track

[Andrew Gee]

Banshee is crashing quite often under various actions. These actions don't always trigger the crash, but they quite often do. I have tried removing ~/.config/banshee-1 but the issues still occur on a new config.

From what I've found, a crash seems to be triggered when:
* Banshee is loading
* Banshee is moving from one track to another
* Banshee is importing a track (attempted with different working files)

Attached is a `banshee --debug` log when importing a track that triggers the crash.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: banshee 2.4.1-3ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic x86_64
ApportVersion: 2.5.1-0ubuntu4
Architecture: amd64
Date: Sat Sep 1 23:10:27 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: banshee
UpgradeStatus: Upgraded to quantal on 2012-08-19 (13 days ago)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Chow Loong Jin (hyperair)]

It looks like it's crashing due to a segfault in native code. Could you try getting a stack trace from gdb please? It won't be very straightforward to run Banshee in gdb, so I suggest attaching gdb to Banshee once it has started running:

1. Start Banshee in a terminal with "banshee --debug"
2. Open another terminal
3. Hook gdb onto the running Banshee process: gdb -p `pidof banshee`
4. Once gdb's prompt appears, get it to allow the Banshee process to continue by typing "cont"
5. Reproduce the crash
6. The gdb prompt should appear. Type "bt full" to get the full stack trace. Then type "quit" to quit gdb.
7. Copy the outputs from both terminals and save them into separate text files
8. Attach both files to this bug.

[Andrew Gee (andrewgee)]

I had a lot of SIGPWR and SIGXCPU signals, which I just continued past, but I ran the `bt full` on the SIGSEGV signal.

See attached logs. Looks like it may be a dbus problem?

[Chow Loong Jin (hyperair)]

On 09/09/2012 16:36, Andrew Gee wrote:
> ** Attachment added: "gdb-debug.log"
> https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1044842/+attachment/3302829/+files/gdb-debug.log
>

Yeah looks like it. Could you retry those steps with the dbus-1-dbg package
installed, please?

--
Kind regards,
Loong Jin

[Andrew Gee (andrewgee)]

Hi,

Find attached the two files after installing dbus-1-dbg

Thanks.

[Chow Loong Jin (hyperair)]

Well it looks like a libdbus problem, so I'm reassigning this bug to that package instead.

[Chow Loong Jin (hyperair)]

This bug might be a duplicate of Bug #1048341. Could you check if the libgconf2-4 package from https://launchpad.net/~hyperair/+archive/test-11048341-fix fixes the issue you're facing please?

[Andrew Gee (andrewgee)]

That fix worked perfectly. Haven't experienced any issues at all yet!

Thank you!

[Chow Loong Jin (hyperair)]

On 11/09/2012 18:01, Andrew Gee wrote:
> That fix worked perfectly. Haven't experienced any issues at all yet!
>
> Thank you!
>

Great, thanks for confirming.

  duplicate 1048341

--
Kind regards,
Loong Jin