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 355795 - Crash at startup
Crash at startup
Status: RESOLVED FIXED
Product: f-spot
Classification: Other
Component: General
CVS
Other Linux
: Normal critical
: ---
Assigned To: F-spot maintainers
F-spot maintainers
Depends on:
Blocks:
 
 
Reported: 2006-09-13 15:08 UTC by Stephane Delcroix
Modified: 2006-09-17 10:46 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Stephane Delcroix 2006-09-13 15:08:39 UTC 
I'm no longer able to run F-Spot at all !!!

=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

Stacktrace:

  at (wrapper managed-to-native) DBus.Connection.dbus_connection_setup_with_g_main (intptr,intptr) <0x00004>
  at (wrapper managed-to-native) DBus.Connection.dbus_connection_setup_with_g_main (intptr,intptr) <0xffffffff>
  at DBus.Connection.SetupWithMain () <0x0001a>
  at DBus.Bus.GetBus (DBus.Bus/BusType) <0x00059>
  at DBus.Bus.GetSessionBus () <0x00009>
  at FSpot.Core.get_Connection () <0x00013>
  at FSpot.Core.FindInstance () <0x0000d>
  at FSpot.Driver.Main (string[]) <0x0030c>
  at (wrapper runtime-invoke) System.Object.runtime_invoke_void_string[] (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

        f-spot(mono_handle_native_sigsegv+0xe6) [0x8155b96]
        f-spot [0x8122998]
        [0xffffe440]
        [0xa62389c5]
        [0xa623897b]
        [0xa6237462]
        [0xa62373d2]
        [0xa623739c]
        [0xa62372fe]
        [0xa72a15d5]
        [0xa72a07c3]
        f-spot(mono_runtime_exec_main+0x60) [0x80995b0]
        f-spot(mono_runtime_run_main+0x1b3) [0x8099893]
        f-spot(mono_main+0xe54) [0x805d3b4]
        f-spot [0x805c082]
        /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0xa7cd9ea8]
        f-spot [0x805bfd1]
Aborted

It happens every time.

If you have any clue...
Comment 1 Larry Ewing 2006-09-13 16:30:58 UTC 
I'm pretty much at a loss on this one, nothing has changed about startup, have you tried dbus-launch or logging out and retrying?
Comment 2 Stephane Delcroix 2006-09-14 08:52:03 UTC 
For the records:
- problem was not an F-Spot issue, but a dbus-sharp one.
- banshee has exactly the same issue

Solved using the git version of dbus-sharp, available as a debian package in experimental.
Comment 3 Andrew Mitchell 2006-09-17 10:46:34 UTC 
Yes, dbus-sharp should have gone straight to unstable, but didn't due to archive bugs in Debian. I also had this reported a few times in Debian for the same reason :)