command line - Komodo Edit: GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed

21
2014-04
  • pzanetti631

    when i try to run Komodo Edit 8.0 from terminal, it returns me this error:

    (process:9508): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed
    

    how can i fix this?

    note: nevertheless, the application lauches and runs properly.

  • Answers
  • D.W.

    This is being tracked on the Mozilla bug tracker at

    https://bugzilla.mozilla.org/show_bug.cgi?id=833117

    At the moment there is no fix, but the error/warning can be ignored.


  • Related Question

    indicator - What causes critical glib errors (when coding using messaging menu)?
  • fluteflute

    If I run the python code below (almost entirely from this useful blog post) then I get three identical nasty looking error messages in the terminal. What might be causing them?

    I note the number (5857 in the example below) changes slightly on each run. What does this number signify? Is it a memory location or something similar?

    (messaging-menu.py:5857): GLib-GIO-CRITICAL **: g_dbus_method_invocation_return_dbus_error: assertion `error_name != NULL && g_dbus_is_name (error_name)' failed

    (messaging-menu.py:5857): GLib-GIO-CRITICAL **: g_dbus_method_invocation_return_dbus_error: assertion `error_name != NULL && g_dbus_is_name (error_name)' failed

    (messaging-menu.py:5857): GLib-GIO-CRITICAL **: g_dbus_method_invocation_return_dbus_error: assertion `error_name != NULL && g_dbus_is_name (error_name)' failed

    I'm running this on Natty, I should probably find out if I get the same errors in 10.10 though...

    import gtk
    
    def show_window_function(x, y):
        print x
        print y
    
    # get the indicate module, which does all the work
    import indicate
    
    # Create a server item
    mm = indicate.indicate_server_ref_default()
    # If someone clicks your server item in the MM, fire the server-display signal
    mm.connect("server-display", show_window_function)
    # Set the type of messages that your item uses. It's not at all clear which types
    # you're allowed to use, here.
    mm.set_type("message.im")
    # You must specify a .desktop file: this is where the MM gets the name of your
    # app from.
    mm.set_desktop_file("/usr/share/applications/nautilus.desktop")
    # Show the item in the MM.
    mm.show()
    
    # Create a source item
    mm_source = indicate.Indicator()
    # Again, it's not clear which subtypes you are allowed to use here.
    mm_source.set_property("subtype", "im")
    # "Sender" is the text that appears in the source item in the MM
    mm_source.set_property("sender", "Unread")
    # If someone clicks this source item in the MM, fire the user-display signal
    mm_source.connect("user-display", show_window_function)
    # Light up the messaging menu so that people know something has changed
    mm_source.set_property("draw-attention", "true")
    # Set the count of messages in this source.
    mm_source.set_property("count", "15")
    # If you prefer, you can set the time of the last message from this source,
    # rather than the count. (You can't set both.) This means that instead of a
    # message count, the MM will show "2m" or similar for the time since this
    # message arrived.
    # mm_source.set_property_time("time", time.time())
    mm_source.show()
    
    gtk.main()
    

  • Related Answers
  • fluteflute

    Testing on Maverick suggests this is a Natty bug, so I reported a bug.