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 708112 - Crash on startup
Crash on startup
Status: RESOLVED DUPLICATE of bug 708120
Product: banshee
Classification: Other
Component: general
2.6.1
Other Linux
: Normal normal
: ---
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-09-15 13:34 UTC by CP
Modified: 2013-09-16 17:19 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
With brasero (12.76 KB, text/x-log)
2013-09-15 13:34 UTC, CP 		Details
without brasero (12.90 KB, text/x-log)
2013-09-15 13:35 UTC, CP 		Details

Description CP 2013-09-15 13:34:58 UTC 
Created attachment 254971 [details]
With brasero

Crashes on startup

Arch Linux
uname -a: Linux Donald.Arch 3.10.10-1-ARCH #1 SMP PREEMPT Fri Aug 30 11:30:06 CEST 2013 x86_64 GNU/Linux

I noticed brasero mentioned in the stacktrace, so i uninstalled it and tried again. It still crashed, but with a different stacktrace. I'm assuming the 2 are related, so i'll leave both of them here

(brasero v3.8.0)
Comment 1 CP 2013-09-15 13:35:37 UTC 
Created attachment 254972 [details]
without brasero
Comment 2 Bertrand Lorentz 2013-09-16 16:51:44 UTC 
Thank you for your bug report.

You need to use the "--debug" argument to run Banshee in debug mode, "--enable-debug" does not work.

Which version of mono do you have on your system ?
We got a report of crashes with mono 3.2.1 on Arch Linux: bug #708120
Comment 3 CP 2013-09-16 17:06:36 UTC 
ah, mono 3.2.1 indeed

sounds like it's the same

why did I think --enable-debug worked? Was it there before, but was removed or something? :L
Comment 4 Bertrand Lorentz 2013-09-16 17:19:34 UTC 
I'm marking this as a duplicate then, as the other bug has already debug stacktraces and several people involved.

*** This bug has been marked as a duplicate of bug 708120 ***