Bug 687996 – Glom crashes at startup

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 687996 - Glom crashes at startup


Summary:	Glom crashes at startup


Status:	RESOLVED FIXED

Product:	glom
Classification:	Other
Component:	general
Version:	unspecified
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Murray Cumming
QA Contact:	Murray Cumming

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2012-11-09 15:10 UTC by Ignacio Casal Quinteiro (nacho)
Modified:	2012-11-13 14:38 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Ignacio Casal Quinteiro (nacho) 2012-11-09 15:10:35 UTC

(glom:9753): glibmm-ERROR **: 
unhandled exception (type std::exception) in signal handler:
what: Could not add namespace declaration with URI=http://glom.org/glom_document, prefix=


Program received signal SIGTRAP, Trace/breakpoint trap.
0x000000365f04eca7 in g_logv () from /lib64/libglib-2.0.so.0
(gdb) t a a bt

+ Trace 231148

Thread 1 (Thread 0x7ffff371da00 (LWP 9753))

#0 g_logv
from /lib64/libglib-2.0.so.0
#1 g_log
from /lib64/libglib-2.0.so.0
#2 Glib::exception_handlers_invoke()
from /lib64/libglibmm-2.4.so.1
#3 Gio::Application_Class::activate_callback(_GApplication*)
from /lib64/libgiomm-2.4.so.1
#4 _g_closure_invoke_va
from /lib64/libgobject-2.0.so.0
#5 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#6 g_signal_emit
from /lib64/libgobject-2.0.so.0
#7 Glom::Application::on_command_line(Glib::RefPtr<Gio::ApplicationCommandLine> const&)
#8 Gio::Application_Class::command_line_callback(_GApplication*, _GApplicationCommandLine*)
from /lib64/libgiomm-2.4.so.1
#9 ffi_call_unix64
from /lib64/libffi.so.5
#10 ffi_call
from /lib64/libffi.so.5
#11 g_cclosure_marshal_generic_va
from /lib64/libgobject-2.0.so.0
#12 _g_closure_invoke_va
from /lib64/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#14 g_signal_emit
from /lib64/libgobject-2.0.so.0
#15 g_application_run
from /lib64/libgio-2.0.so.0
#16 main

Comment 1 Murray Cumming 2012-11-09 20:12:11 UTC

This is probably caused by a recent bad release of libxml++. The libxml++ 2.36.0 release should fix that.

Is this an official package on some distro?

Comment 2 Ignacio Casal Quinteiro (nacho) 2012-11-10 09:07:44 UTC

This is in F18.

Comment 3 Ignacio Casal Quinteiro (nacho) 2012-11-10 09:08:25 UTC

And you are right. I do not have yet 2.36.0.
libxml++-2.35.4-1.fc18.x86_64

Thanks for the info.

Comment 4 Murray Cumming 2012-11-11 19:26:19 UTC

So, could you please file a bug for Fedora, and link to it from here? Thanks.

Comment 5 Ignacio Casal Quinteiro (nacho) 2012-11-13 14:38:35 UTC

After checking with the libxml++ maintainer he is going to get it landed in the next major update which will happen in the upcoming days. So soon this will be no problem anymore.