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 507379 - crash in Glade Interface Designer: Choosing a toplevel wind...
crash in Glade Interface Designer: Choosing a toplevel wind...
Status: RESOLVED DUPLICATE of bug 480495
Product: glade
Classification: Applications
Component: general
3.4.x
Other All
: High critical
: ---
Assigned To: Glade 3 Maintainers
Glade 3 Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-04 22:54 UTC by ikshaar
Modified: 2008-01-05 01:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description ikshaar 2008-01-04 22:54:37 UTC 
Version: 3.4.0

What were you doing when the application crashed?
Choosing a toplevel window GtkInputDialog


Distribution: Gentoo Base System release 1.12.10
Gnome Release: 2.20.1 2007-11-27 (Gentoo)
BugBuddy Version: 2.20.1

System: Linux 2.6.20-gentoo-r8 #3 SMP Mon Sep 17 15:59:22 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: etiquette-icons-0.6

Memory status: size: 213946368 vsize: 213946368 resident: 29978624 share: 15466496 rss: 29978624 rss_rlim: 18446744073709551615
CPU usage: start_time: 1199487229 rtime: 119 utime: 100 stime: 19 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/glade-3'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
0x00002b8369ed89e5 in waitpid () from /lib/libpthread.so.0

+ Trace 184107

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 gtk_widget_region_intersect
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 gtk_container_propagate_expose
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #13 ??
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #16 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #19 gdk_window_process_all_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #20 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #22 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #23 ??
    from /usr/lib/libglib-2.0.so.0
  • #24 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #25 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 main
  • #27 __libc_start_main
    from /lib/libc.so.6
  • #28 _start 


----------- .xsession-errors (27429 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 ikshaar 2008-01-05 00:22:41 UTC 
Sorry for the report. Already fixed in 3.4.1.
Comment 2 Juan Pablo Ugarte 2008-01-05 01:07:27 UTC 
no problem :)

*** This bug has been marked as a duplicate of 480495 ***