After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 682326 - 2.4.1-alpha5 crashes on startup on Mountain Lion
2.4.1-alpha5 crashes on startup on Mountain Lion
Status: RESOLVED FIXED
Product: banshee
Classification: Other
Component: general
2.4.1
Other Mac OS
: Normal major
: ---
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-08-21 03:03 UTC by Ross A. Baker
Modified: 2012-11-02 10:17 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Console output (1.79 KB, text/plain)
2012-08-21 03:03 UTC, Ross A. Baker 		Details
Console output, with --debug (4.42 KB, text/plain)
2012-08-21 06:24 UTC, Ross A. Baker 		Details
console with --debug (4.42 KB, application/octet-stream)
2012-08-23 19:02 UTC, Igor K. 		Details
DiagnosticReports (75.61 KB, text/plain)
2012-08-23 21:48 UTC, Igor K. 		Details

Description Ross A. Baker 2012-08-21 03:03:09 UTC 
Created attachment 221952 [details]
Console output

2.4.1-alpha5 crashes on startup on Mountain Lion (10.8).  Banshee 2.3.4 starts without any problems.  Extracted the app to my home directory and ran it from terminal.  The output is attached.
Comment 1 Timo Dörr 2012-08-21 06:01:49 UTC 
Thanks for your work but for some reason, the backtrace was not dumped. could you retry running banshee from console and adding the --debug flag?
Comment 2 Ross A. Baker 2012-08-21 06:24:14 UTC 
Created attachment 221965 [details]
Console output, with --debug

Not much more informative than the last, but hopefully the last successful debug message is a clue.
Comment 3 Timo Dörr 2012-08-21 06:30:53 UTC 
Something is wrong, there is no segfault message or backtrace with the log. I don't know if this has to be enabled somewhere in mountain lion or is a mono issue, but mono usually spits out the backtrace of the segfault, like i.e. here http://bugzilla-attachments.gnome.org/attachment.cgi?id=206383 (log unrelated to the bug).
Comment 4 Igor K. 2012-08-23 19:02:39 UTC 
Created attachment 222254 [details]
console with --debug

returns:
Segmentation fault: 11
Comment 5 Igor K. 2012-08-23 19:04:16 UTC 
I've attached another log.... hope it helps...
Comment 6 Timo Dörr 2012-08-23 19:40:26 UTC 
no actually it is the same problem. it seems mountain lion or mono have changed their behavour on segfault. when mono is run with --debug it usually dumps a usefull stacktrace (of the native code). the logs here only show the banshee output, which is not usefull (as not banshee is crashing but most likely gtk).
Comment 7 Igor K. 2012-08-23 21:48:57 UTC 
Created attachment 222264 [details]
DiagnosticReports

Diagnostic Report attached, it dosen't say much but I'm not mono developer...
Comment 8 Bertrand Lorentz 2012-11-02 10:17:11 UTC 
This should now be fixed by the updated version of our OS X binary:
http://ftp.gnome.org/pub/GNOME/binaries/mac/banshee/banshee-2.6.0-1.macosx.intel.dmg

Feel free to re-open this bug if it is not the case, and please open new bugs for any other issue you might have.