FS#37228 - Banshee won't start after recent Gnome updates

Attached to Project: Arch Linux
Opened by John Piers (johnpiers) - Monday, 07 October 2013, 17:21 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 16 October 2013, 09:24 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 7
Private No

Details

Description:


Additional info:
* package version(s)banshee 2.6.1-1
* config and/or log files etc.


Steps to reproduce: Run Banshee normally or from the terminal!
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 16 October 2013, 09:24 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 2.6.1-2 by compiling with dmcs.
Comment by Anthony Ruhier (Anthony25) - Monday, 07 October 2013, 17:30 GMT
I have the same problem, and I created a topic on the forum : https://bbs.archlinux.org/viewtopic.php?id=170958
Comment by Claire Farron (clfarron4) - Monday, 07 October 2013, 23:02 GMT
I'm the same here. I've attached what happens if I run banshee in the terminal.
Comment by John Piers (johnpiers) - Tuesday, 08 October 2013, 00:23 GMT
The workaround for this is to downgrade "gtk-sharp-2-2.12.22-1-x86_64.pkg.tar.xz" to "gtk-sharp-2-2.12.11-1-x86_64.pkg.tar.xz" This should be found in /var/cache/pacman/pkg/ if not and like me, you could only find the new version "gtk-sharp-2-2.12.22-1-x86_64.pkg.tar.xz" here is a link to the older file: http://www.mediafire.com/download/9qvn9 … pkg.tar.xz Once the file is downloaded just run (from the folder that you have saved the file in) "sudo pacman -U gtk-sharp-2-2.12.11-1-x86_64.pkg.tar.xz" you will get a message: warning: downgrading package gtk-sharp-2 (2.12.22-1 => 2.12.11-1) and the older version of the file will install and Banshee behaves again! Thanks to Anthony Ruhier for the advise and the link!
Comment by Anthony Ruhier (Anthony25) - Tuesday, 08 October 2013, 12:40 GMT Comment by John Piers (johnpiers) - Thursday, 10 October 2013, 07:21 GMT
Thanks Anthony, I must have copied your link incorrectly, appreciate you fixing it. Any news on this? Or is it not really considered very important? Thanks to all the dudes that work their buts off to fix these problems, keep up the hard work!
Comment by Anthony Ruhier (Anthony25) - Thursday, 10 October 2013, 12:40 GMT
No news, sorry :(
I'm going to search if there is a bugreport on the banshee bugzilla, or to create one if there isn't.

The problem is that only a few distributions are on gnome 3.10 (with the new package gtk-sharp for mono, created specially for gnome 3.10), so I don't think there are a lot of users who experience crashes at launch in Banshee. That's why it's better to submit a bugreport directly to the Banshee team (imo).

Edit : done ! https://bugzilla.gnome.org/show_bug.cgi?id=709813
Comment by Scott Garrett (Wintervenom) - Saturday, 12 October 2013, 20:43 GMT
Hi,

It seems the Banshee in [extra] is compiled against the wrong runtime profile (all of the other Mono/Sharp libraries it uses in are compiled against the 4.0 profile).
In order for Banshee to work, it needs to be built with the ``dmcs`` (4.0 profile) compiler instead of the ``gmcs`` (2.0 profile) compiler that it chooses by default.
Adding ``MCS=/usr/bin/dmcs`` to the ``./autogen.sh`` line in Banshee's PKGBUILD and rebuilding should resolve the problem.
Comment by Anthony Ruhier (Anthony25) - Sunday, 13 October 2013, 00:05 GMT
Thank you Scott, it works !
Comment by Morgan (Morgan) - Sunday, 13 October 2013, 06:37 GMT
I can also confirm this works. Thank you.
Comment by Jean-Patrick Simard (jpsimard) - Tuesday, 15 October 2013, 13:10 GMT
I've been monitoring this thread and adding ``MCS=/usr/bin/dmcs`` works for me too.

Perhaps this is a stupid question, but will this change go into the official package in the repos?

Loading...