GNOME Bugzilla – Bug 458500
Critical Error: Adding a GtkMessageDialo...
Last modified: 2010-12-16 19:47:33 UTC
Version: 3.3.2 What were you doing when the application crashed? Adding a GtkMessageDialog to project 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: 210186240 vsize: 210186240 resident: 25198592 share: 14966784 rss: 25198592 rss_rlim: 18446744073709551615 CPU usage: start_time: 1184900312 rtime: 44 utime: 37 stime: 7 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 47119581413408 (LWP 2797)] 0x00002adadf950d15 in waitpid () from /lib/libpthread.so.0
+ Trace 149246
Thread 1 (Thread 47119581413408 (LWP 2797))
----------- .xsession-errors (26496 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. --------------------------------------------------
Oops, not really a crash. The GNOME JHBuild environment seems to set G_DEDUG=fatal_criticals as the default. Nevertheless we need to fix this critical error as it a symptom of an invalid program state.
<property name="image"></property>
Old obsolete bug doesnt happen anymore.