FS#21351 - [banshee] [mono] compile broken, banshee will not start

Attached to Project: Arch Linux
Opened by Ryan Peters (sloshy) - Tuesday, 19 October 2010, 19:17 GMT
Last edited by Isenmann Daniel (ise) - Thursday, 17 March 2011, 06:49 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Isenmann Daniel (ise)
Hugo Doria (hdoria)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
I get the following error when I try to launch the recently-released Banshee 1.8:

Unhandled Exception: System.TypeInitializationException: An exception was thrown by the type initializer for Hyena.ApplicationContext ---> System.TypeInitializationException: An exception was thrown by the type initializer for System.TimeZone ---> System.ExecutionEngineException: SIGILL
at System.Collections.Hashtable..ctor (Int32 capacity, Single loadFactor, IHashCodeProvider hcp, IComparer comparer) [0x00000] in <filename unknown>:0
at System.Collections.Hashtable..ctor (Int32 capacity, Single loadFactor) [0x00000] in <filename unknown>:0
at System.Collections.Hashtable..ctor (Int32 capacity) [0x00000] in <filename unknown>:0
at System.CurrentSystemTimeZone..ctor (Int64 lnow) [0x00000] in <filename unknown>:0
at System.TimeZone..cctor () [0x00000] in <filename unknown>:0
--- End of inner exception stack trace ---
at Hyena.ApplicationContext..cctor () [0x00000] in <filename unknown>:0
--- End of inner exception stack trace ---
at Booter.Booter.CheckHelpVersion () [0x00000] in <filename unknown>:0
at Booter.Booter.Main () [0x00000] in <filename unknown>:0

After asking around at #banshee on irc.gnome.org, they suggested that mono might have not been compiled correctly, and that whoever maintains the mono package should run the "Mono test suite" to ensure that it was compiled correctly.

Additional info:
* package versions:
mono 2.8, banshee 1.8

Steps to reproduce:
1) Install Mono and Banshee.
2) Attempt to launch Banshee.
This task depends upon

Closed by  Isenmann Daniel (ise)
Thursday, 17 March 2011, 06:49 GMT
Reason for closing:  No response
Additional comments about closing:  No response the last 3 weeks. I close this bug since it works for me.
Comment by Isenmann Daniel (ise) - Wednesday, 20 October 2010, 05:38 GMT
banshee 1.8 runs without a problem on my computer. Tested with various plugins and songs. Can't reproduce it.

Can you please post the output with the following settings:

$ export MONO_ENV_OPTIONS="--trace=program"
$ banshee-1

That will set the trace output to log more. If you close the console session, the setting is gone, so you have to set it everytime you want that output.
Comment by Ryan Peters (sloshy) - Wednesday, 20 October 2010, 13:24 GMT
I tried that just now, and my results are exactly the same. I'm using the i686 architecture if that helps. I probably should have said that in the "details" section now that I think about it. My bad.
Comment by Isenmann Daniel (ise) - Wednesday, 20 October 2010, 13:29 GMT
I tried it with i686 and x86_64 version and both works fine here. Can you post the log output of the above command, normally there should be a lot more of output than posted in details?
Comment by Ryan Peters (sloshy) - Wednesday, 20 October 2010, 16:14 GMT
[0xb76f36f0: 0.00000 0] ENTER: Booter.Booter:Main ()()
[0xb76f36f0: 0.01804 1] ENTER: Booter.Booter:CheckHelpVersion ()()
[0xb76f36f0:] EXCEPTION handling: System.ExecutionEngineException: SIGILL
[0xb76f36f0:] EXCEPTION handling: System.TypeInitializationException: An exception was thrown by the type initializer for System.TimeZone
[0xb76f36f0:] EXCEPTION handling: System.TypeInitializationException: An exception was thrown by the type initializer for Hyena.ApplicationContext

Unhandled Exception: System.TypeInitializationException: An exception was thrown by the type initializer for Hyena.ApplicationContext ---> System.TypeInitializationException: An exception was thrown by the type initializer for System.TimeZone ---> System.ExecutionEngineException: SIGILL
at System.Collections.Hashtable..ctor (Int32 capacity, Single loadFactor, IHashCodeProvider hcp, IComparer comparer) [0x00000] in <filename unknown>:0
at System.Collections.Hashtable..ctor (Int32 capacity, Single loadFactor) [0x00000] in <filename unknown>:0
at System.Collections.Hashtable..ctor (Int32 capacity) [0x00000] in <filename unknown>:0
at System.CurrentSystemTimeZone..ctor (Int64 lnow) [0x00000] in <filename unknown>:0
at System.TimeZone..cctor () [0x00000] in <filename unknown>:0
--- End of inner exception stack trace ---
at Hyena.ApplicationContext..cctor () [0x00000] in <filename unknown>:0
--- End of inner exception stack trace ---
at Booter.Booter.CheckHelpVersion () [0x00000] in <filename unknown>:0
at Booter.Booter.Main () [0x00000] in <filename unknown>:0
Comment by Rémy Oudompheng (remyoudompheng) - Wednesday, 20 October 2010, 16:32 GMT
Aborting with "SIGILL" looks very very bad... I am pretty sure banshee was built using standard CFLAGS.
Comment by Isenmann Daniel (ise) - Thursday, 21 October 2010, 07:30 GMT
@Rémy: Does Banshee start at your computer? I have no problems here and works fine.

@Ryan: Do you have installed some plugins from some 3rd party? Maybe these are broken.
Comment by Ryan Peters (sloshy) - Thursday, 21 October 2010, 13:47 GMT
@Isenmann: As far as I can tell, no other plugins are installed.
Comment by Isenmann Daniel (ise) - Thursday, 21 October 2010, 19:01 GMT
@Hugo: Can you please have a look at this bug. Maybe you have some ideas about this bug with banshee.
Comment by Ionut Biru (wonder) - Thursday, 21 October 2010, 19:37 GMT
maybe we should implement  FS#21376 
Comment by Marty (thefatprecious) - Friday, 22 October 2010, 14:13 GMT
See here:
https://bugzilla.gnome.org/show_bug.cgi?id=620461

As suggested running it with this workaround it does not crash.
XLIB_SKIP_ARGB_VISUALS=1 banshee-1

I posted this in the forums as well:
https://bbs.archlinux.org/viewtopic.php?pid=843581#p843581
Comment by Ryan Peters (sloshy) - Monday, 25 October 2010, 19:07 GMT
@Marty: The bug you linked to deals with RGBA support, which I do not use. The workaround does not work and I get the same error.
Comment by Isenmann Daniel (ise) - Wednesday, 27 October 2010, 07:57 GMT
There are some commits to the banshee git to fix compilation errors.

http://osdir.com/ml/general/2010-10/msg29191.html
http://osdir.com/ml/general/2010-10/msg29188.html
http://osdir.com/ml/general/2010-10/msg33153.html

Maybe this fix the whole situation with compilation. But I don't know if these fixes were in the 1.8.0 release. Maintainer of banshee should give more details on this.
Nevertheless it runs here without recompilation, so the other part of the bug can't be fixed by me.
Comment by Alejandro (alez) - Monday, 29 November 2010, 09:09 GMT
I can add that I was having the same problem but recompiled mono (yeah, on i686, go grab a coffee :D ) and now banshee is working.
Comment by Isenmann Daniel (ise) - Monday, 29 November 2010, 09:30 GMT
@Alejandro: You recompiled mono? This is not a problem of mono like I mentioned it some comments above.

EDIT: I have tested it again on a newly installed Arch Linux. Everything works like expected. Can't reproduce this bug.
Comment by Alejandro (alez) - Monday, 29 November 2010, 09:51 GMT
I knew there was a new banshee release but since (i think) odd releases aren't stable ones i wasn't counting to have that one on official repos. If it gets there i won't complain, promise! I recompiled since i wanted to try something (although i wasn't thinking it was mono what broke the package, who knows why it's working now) and was also having trouble with anything mono-related in the AUR (I.E. google-gdata-sharp which btw just managed to install this morning after several failed attempts before the mono source building) so I wasn't able to try neither banshee-git nor the unstable releases on AUR. To sum it up, official (1.8.0-1) works now, and i was also able to build and install the unstable one (1.9.0-1) which also works after I did a yaourt -Sb mono. If there's anything i can do to help, just let me know.
Comment by Ryan Peters (sloshy) - Wednesday, 01 December 2010, 02:30 GMT
I can confirm that re-compiling mono fixes the problem entirely. Weird.
Comment by Isenmann Daniel (ise) - Wednesday, 01 December 2010, 06:19 GMT
This is more than weird. I don't have any issues on two computers.

@alez: Is it possible that you compare both packages if they have the same files and same sizes?
Comment by Alejandro (alez) - Wednesday, 01 December 2010, 12:04 GMT
Ok, I recompiled again since i didn't really know how to recompress the package once installed (you can tell i'm a noob :D ) It's a bit bigger (31,2 M) than the official on french repos (30,9 M). With Meld i can't find a file in the new version that isn't in the official (again, I really don't know how to do all of this and I'm everything but sure that i'm comparing the two packages the right way) In any case and in view of my difficulties I've uploaded the built from source one to MU (sorry, it's the one I know better) here: http://www.megaupload.com/?d=GZW6PUNG

Is there anything else i can do? Or maybe someone can guide me to do better than this. Thanks
Comment by Ionut Biru (wonder) - Saturday, 01 January 2011, 19:12 GMT
please check banshee 1.8.0-2
Comment by Alejandro (alez) - Sunday, 09 January 2011, 15:39 GMT
Hi, i'm getting exactly the same crash with banshee 1.8.0-2 and official mono. Currently trying to recompile it (mono) to see if it fixes the problem again.

Edit: recompiling fixed the problem indeed.
Comment by Eric Belanger (Snowman) - Saturday, 19 February 2011, 06:39 GMT
Please try with banshee-1.8.1-1
Comment by Ryan Peters (sloshy) - Saturday, 19 February 2011, 17:44 GMT
As of the latest banshee and mono packages, it doesn't run still. The error is the same as above, and recompiling mono from ABS fixes the problem. Here's my makepkg.conf(.txt, for web browser compatibility): http://dl.dropbox.com/u/807039/makepkg.conf.txt
Comment by Isenmann Daniel (ise) - Monday, 21 February 2011, 06:51 GMT
Mono (x86 version) was built the same way as the x86_64 version. So there is no difference in my makepkg.conf. Banshee is working on my system on my second computer. I will release mono 2.10 the next days, maybe its fixed with this release.
Comment by Isenmann Daniel (ise) - Sunday, 27 February 2011, 11:35 GMT
I have just uploaded Mono 2.10.1 to the repos. Wait until your mirror synced and then please try again if banshee doesn't work. Thanks.
Comment by Isenmann Daniel (ise) - Wednesday, 09 March 2011, 14:23 GMT
If there is no response until a week, I will close this bug as fixed. I can't reproduced this bug from the start so I can't do anything here.

Loading...