Abort on startup: "** ERROR **: Failed to register GObject with DBusConnection"

[Javier Cabezas]

Binary package hint: dia

Dia crashes on startup. I am using Ubuntu 10.04 x86-64. The full error message is:

(dia:8523): GLib-WARNING **: A group named "gtk" is already part of this GOptionContext

** ERROR **: Failed to register GObject with DBusConnection
aborting...
Aborted

The gdb backtrace is:

Program received signal SIGABRT, Aborted.
0x00007ffff25e2a75 in raise () from /lib/libc.so.6
(gdb) bt
#0 0x00007ffff25e2a75 in raise () from /lib/libc.so.6
#1 0x00007ffff25e65c0 in abort () from /lib/libc.so.6
#2 0x00007ffff402333a in g_logv () from /lib/libglib-2.0.so.0
#3 0x00007ffff40233d3 in g_log () from /lib/libglib-2.0.so.0
#4 0x00007ffff1e433e0 in dbus_g_connection_register_g_object () from /usr/lib/libdbus-glib-1.so.2
#5 0x00007ffff44cf8dd in ?? () from /usr/lib/libgobject-2.0.so.0
#6 0x00007ffff44d0841 in g_object_newv () from /usr/lib/libgobject-2.0.so.0
#7 0x00007ffff44d12ad in g_object_new_valist () from /usr/lib/libgobject-2.0.so.0
#8 0x00007ffff44d14f1 in g_object_new () from /usr/lib/libgobject-2.0.so.0
#9 0x00007fffe3af4479 in ?? () from /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so
#10 0x00007ffff44ca5de in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#11 0x00007ffff44de598 in ?? () from /usr/lib/libgobject-2.0.so.0
#12 0x00007ffff44dfa76 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#13 0x00007ffff44e0033 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#14 0x00007ffff44ce5b9 in ?? () from /usr/lib/libgobject-2.0.so.0
#15 0x00007ffff44d051c in g_object_notify () from /usr/lib/libgobject-2.0.so.0
#16 0x00007ffff62cdd65 in gtk_widget_set_parent () from /usr/lib/libgtk-x11-2.0.so.0
#17 0x00007ffff767806d in bonobo_dock_band_insert () from /usr/lib/libbonoboui-2.so.0
#18 0x00007ffff7670b69 in bonobo_dock_add_item () from /usr/lib/libbonoboui-2.so.0
#19 0x00007ffff76794c0 in bonobo_dock_layout_add_to_dock () from /usr/lib/libbonoboui-2.so.0
#20 0x00007ffff78e4b72 in ?? () from /usr/lib/libgnomeui-2.so.0
#21 0x00007ffff44ca5de in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#22 0x00007ffff44dde61 in ?? () from /usr/lib/libgobject-2.0.so.0
#23 0x00007ffff44dfa76 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#24 0x00007ffff44e0033 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#25 0x00007ffff62ce19b in gtk_widget_show () from /usr/lib/libgtk-x11-2.0.so.0
#26 0x00007ffff7bbfb5a in persistence_register_window () from /usr/lib/dia/libdia.so
#27 0x000000000043c4da in create_toolbox ()
#28 0x000000000042ef0b in app_init ()
#29 0x000000000045bf59 in main ()

[Shadow Panther (panther-ru)]

Same error when trying to start xsane. One of the recent updates seems to cause it.

[Shadow Panther (panther-ru)]

Also, removing appmenu-gtk, as suggested in https://bugs.launchpad.net/ubuntu/+source/appmenu-gtk/+bug/602229 may help for dia too.

[penalvch (penalvch)]

Javier Cabezas, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
gksudo gedit /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently.

Please do not attach your crash report manually to this report and reopen it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs