Banshee simply doesnt work.q

[Mark McClary]

Binary package hint: banshee

I tried disabling all plugins, tried changing the settings to the bare minimum and it still crashes. Usually upon playing a song then trying to change it.

Description: Ubuntu maverick (development branch)
Release: 10.10

I expect to play without crashing literally every time I use, instead, it crashes way to easily.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: banshee 1.7.6-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Tue Sep 28 15:59:12 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: banshee

[Mark McClary (markmcclary)]

I have created my own work-around.

Under Edit > Preferences > Extensions tab
 - I had the BMP Detection extension enabled

Under Edit > Preferences
 - I had BPM for my music option `unticked`

Fix:
Disable the BPM Detection under extensions.

[Chow Loong Jin (hyperair)]

On Wednesday 29,September,2010 10:28 AM, Mark McClary wrote:
> I have created my own work-around.
>
> Under Edit > Preferences > Extensions tab
> - I had the BMP Detection extension enabled
>
> Under Edit > Preferences
> - I had BPM for my music option `unticked`
>
> Fix:
> Disable the BPM Detection under extensions.
>

Could you install "banshee-dbg" and run "banshee --debug" without the workaround
to get a backtrace, please?

  status incomplete

--
Kind regards,
Chow Loong Jin

[Mark McClary (markmcclary)]

I uninstalled it, it was too much of a pain. There were no warnings or errors in the debug output anyways. It was 90% full of loading coverart messages. The above workaround did not work permanently.

[Victor Vargas (kamus)]

Mark, have you checked if this behaviour is still occurring with release 1.8.0?

[Victor Vargas (kamus)]

Mark, any news about it?

[Victor Vargas (kamus)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!