Bug 458502 – Critical Error: Adding a GtkTreeView to ...

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 458502 - Critical Error: Adding a GtkTreeView to ...


Summary:	Critical Error: Adding a GtkTreeView to ...


Status:	RESOLVED OBSOLETE

Product:	glade
Classification:	Applications
Component:	general
Version:	3.3.x
Hardware:	Other All

Importance:	High major
Target Milestone:	---
Assigned To:	Glade 3 Maintainers
QA Contact:	Glade 3 Maintainers

URL:
Whiteboard:

Depends on:
Blocks:	595075

Reported:	2007-07-20 03:01 UTC by Vincent Geddes
Modified:	2010-12-16 19:49 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description Vincent Geddes 2007-07-20 03:01:40 UTC

Version: 3.3.2

What were you doing when the application crashed?
Adding a GtkTreeView to GtkWindow
GTK+ 2.11.x


Distribution: Ubuntu 7.04 (feisty)
Gnome Release: 2.19.5 2007-07-18 (JHBuild)
BugBuddy Version: 2.18.1

System: Linux 2.6.20-16-generic #2 SMP Thu Jun 7 19:00:28 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Gummy
Icon Theme: gnome

Memory status: size: 213835776 vsize: 213835776 resident: 26689536 share: 15368192 rss: 26689536 rss_rlim: 18446744073709551615
CPU usage: start_time: 1184900468 rtime: 64 utime: 59 stime: 5 cutime:2 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/glade-3'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47480611831840 (LWP 2899)]
0x00002b2eeeac0d15 in waitpid () from /lib/libpthread.so.0

+ Trace 149248

Thread 1 (Thread 47480611831840 (LWP 2899))

#0 waitpid
from /lib/libpthread.so.0
#1 libgnomeui_segv_handle
at gnome-ui-init.c line 865
#2 <signal handler called>
#3 IA__g_logv
at gmessages.c line 503
#4 IA__g_log
at gmessages.c line 517
#5 IA__g_object_get_property
at gobject.c line 659
#6 glade_widget_constructor
at glade-widget.c line 704
#7 IA__g_object_newv
at gobject.c line 937
#8 IA__g_object_new_valist
at gobject.c line 1027
#9 glade_widget_adaptor_create_widget_real
at glade-widget-adaptor.c line 1768
#10 glade_command_create
at glade-command.c line 1556
#11 glade_placeholder_button_press
at glade-placeholder.c line 335
#12 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 84
#13 IA__g_closure_invoke
at gclosure.c line 490
#14 signal_emit_unlocked_R
at gsignal.c line 2478
#15 IA__g_signal_emit_valist
at gsignal.c line 2209
#16 IA__g_signal_emit
at gsignal.c line 2243
#17 gtk_widget_event_internal
at gtkwidget.c line 4674
#18 IA__gtk_propagate_event
at gtkmain.c line 2317
#19 IA__gtk_main_do_event
at gtkmain.c line 1537
#20 gdk_event_dispatch
at gdkevents-x11.c line 2351
#21 IA__g_main_context_dispatch
at gmain.c line 2061
#22 g_main_context_iterate
at gmain.c line 2694
#23 IA__g_main_loop_run
at gmain.c line 2898
#24 IA__gtk_main
at gtkmain.c line 1144
#25 main
at main.c line 185
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors (26653 sec old) ---------------------
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
Bonobo accessibility support initialized
GTK Accessibility Module initialized
(gnome-panel:12811): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
(gnome-panel:12811): atk-bridge-WARNING **: IOR not set.
(gnome-panel:12811): atk-bridge-WARNING **: Could not locate registry
The application 'gnome-session' lost its connection to the display :20.0;
most likely the X server was shut down or you killed/destroyed
the application.
Window manager warning: Lost connection to the display ':20.0';
most likely the X server was shut down or you killed/destroyed
the window manager.
--------------------------------------------------

Comment 1 Vincent Geddes 2007-07-20 13:21:34 UTC

Oops, not really a crash. The GNOME JHBuild environment seems to set G_DEDUG=fatal_criticals as the default.

Nevertheless we need to fix these critical errors as they are a symptom of an invalid program state.

Comment 2 Tristan Van Berkom 2010-12-16 19:49:06 UTC

This doesnt happen anymore either, treeviews have better support now.