« Return to Thread: Unless tomboy is run directly from terminal, initialization assertion fails

Re: Unless tomboy is run directly from terminal, initialization assertion fails

by jimmy the saint :: Rate this Message:

Reply to Author | View in Thread


jimmy the saint wrote:
I have an up to date Arch system with openbox on which I installed tomboy.  Tomboy works quite well, so long as I either open in a terminal manually or call a script to launch it from directly in a terminal.  If I attempt to autostart it with autostart.sh using the "tomboy" command, any terminal with the -e switch, or a script calling tomboy, it fails to start with the following output (please forgive the length, I want to be complete)


(/usr/lib/tomboy/Tomboy.exe:16107): GLib-GObject-CRITICAL **: gtype.c:2458: initialization assertion failed, use IA__g_type_init() prior to this function

(/usr/lib/tomboy/Tomboy.exe:16107): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed

(/usr/lib/tomboy/Tomboy.exe:16107): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
Stacktrace:

  at (wrapper managed-to-native) GConf.Client.gconf_client_get_default () <0x00053>
  at (wrapper managed-to-native) GConf.Client.gconf_client_get_default () <0xffffffff>
  at GConf.Client..ctor () <0x0004b>
  at Tomboy.GConfPreferencesClient..ctor () <0x00027>
  at Tomboy.GnomeFactory.CreatePreferencesClient () <0x0001f>
  at Tomboy.Services..cctor () <0x0006b>
  at (wrapper runtime-invoke) object.runtime_invoke_void (object,intptr,intptr,intptr) <0xffffffff>
  at Tomboy.Application.Initialize (string,string,string,string[]) <0xffffffff>
  at Tomboy.Application.Initialize (string,string,string,string[]) <0x0001c>
  at Tomboy.Tomboy.Main (string[]) <0x000af>
  at (wrapper runtime-invoke) Tomboy.Tomboy.runtime_invoke_void_object (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

        mono [0x47e650]
        mono [0x4ae8dd]
        /lib/libpthread.so.0 [0x7f6f86e44920]
        /usr/lib/libgconf-2.so.4 [0x7f6f84fc1b31]
        /usr/lib/libgconf-2.so.4(gconf_client_get_default+0xc4) [0x7f6f84fc5834]
        [0x404a38e3]

Debug info from gdb:


=================================================================
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.
=================================================================

I am not sure what this means, but it is really irritating.  I have tried so many ways to have various programs open tomboy in the autostart script, but the ONLY way to get it to open properly is to manually open a terminal and run the tomboy command.

This is tomboy 0.14.0 with gnome-sharp 2.24.1-1
I don't know if this helps or not, but I was able to get tomboy to autostart by opening a terminator terminal session for one second during the autostart process.  I had to change another autostart app and it broke my workaround.  I have no idea why the timing of tomboy and the terminal being open is so critical.

 « Return to Thread: Unless tomboy is run directly from terminal, initialization assertion fails