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 458500 - Critical Error: Adding a GtkMessageDialo...
Critical Error: Adding a GtkMessageDialo...
Status: RESOLVED OBSOLETE
Product: glade
Classification: Applications
Component: general
3.3.x
Other All
: High major
: ---
Assigned To: Glade 3 Maintainers
Glade 3 Maintainers
Depends on:
Blocks: 595075
 
 
Reported: 2007-07-20 02:59 UTC by Vincent Geddes
Modified: 2010-12-16 19:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Vincent Geddes 2007-07-20 02:59:20 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

Thread 1 (Thread 47119581413408 (LWP 2797))

  • #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__gtk_message_dialog_set_image
    at gtkmessagedialog.c line 640
  • #6 glade_property_sync_impl
    at glade-property.c line 318
  • #7 glade_widget_sync_custom_props
    at glade-widget.c line 620
  • #8 glade_widget_constructor
    at glade-widget.c line 720
  • #9 IA__g_object_newv
    at gobject.c line 937
  • #10 IA__g_object_new_valist
    at gobject.c line 1027
  • #11 glade_widget_adaptor_create_widget_real
    at glade-widget-adaptor.c line 1768
  • #12 glade_command_create
    at glade-command.c line 1556
  • #13 on_palette_button_clicked
    at glade-app.c line 296
  • #14 IA__g_closure_invoke
    at gclosure.c line 490
  • #15 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #16 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #17 IA__g_signal_emit
    at gsignal.c line 2243
  • #18 glade_palette_on_button_toggled
    at glade-palette.c line 445
  • #19 IA__g_closure_invoke
    at gclosure.c line 490
  • #20 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #21 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #22 IA__g_signal_emit
    at gsignal.c line 2243
  • #23 gtk_toggle_button_clicked
    at gtktogglebutton.c line 438
  • #24 IA__g_closure_invoke
    at gclosure.c line 490
  • #25 signal_emit_unlocked_R
    at gsignal.c line 2370
  • #26 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #27 IA__g_signal_emit
    at gsignal.c line 2243
  • #28 gtk_toggle_button_released
    at gtktogglebutton.c line 425
  • #29 IA__g_closure_invoke
    at gclosure.c line 490
  • #30 signal_emit_unlocked_R
    at gsignal.c line 2370
  • #31 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #32 IA__g_signal_emit
    at gsignal.c line 2243
  • #33 gtk_button_button_release
    at gtkbutton.c line 1377
  • #34 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #35 IA__g_closure_invoke
    at gclosure.c line 490
  • #36 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #37 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #38 IA__g_signal_emit
    at gsignal.c line 2243
  • #39 gtk_widget_event_internal
    at gtkwidget.c line 4674
  • #40 IA__gtk_propagate_event
    at gtkmain.c line 2317
  • #41 IA__gtk_main_do_event
    at gtkmain.c line 1537
  • #42 gdk_event_dispatch
    at gdkevents-x11.c line 2351
  • #43 IA__g_main_context_dispatch
    at gmain.c line 2061
  • #44 g_main_context_iterate
    at gmain.c line 2694
  • #45 IA__g_main_loop_run
    at gmain.c line 2898
  • #46 IA__gtk_main
    at gtkmain.c line 1144
  • #47 main
    at main.c line 185
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .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.
--------------------------------------------------
Comment 1 Vincent Geddes 2007-07-20 13:23:28 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 this critical error as it a symptom of an invalid program state.
Comment 2 Bug flys 2007-07-24 09:50:47 UTC
    <property name="image"></property>
Comment 3 Tristan Van Berkom 2010-12-16 19:47:33 UTC
Old obsolete bug doesnt happen anymore.