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 394428 - crash in Glade Interface Designer: Closing the app
crash in Glade Interface Designer: Closing the app
Status: RESOLVED INCOMPLETE
Product: glade
Classification: Applications
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Glade 3 Maintainers
Glade 3 Maintainers
Depends on: 432019
Blocks:
 
 
Reported: 2007-01-08 22:21 UTC by Jeremies Pérez
Modified: 2007-07-02 23:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Jeremies Pérez 2007-01-08 22:21:54 UTC
What were you doing when the application crashed?
Closing the app


Distribution: Gentoo Base System version 1.12.6
Gnome Release: 2.17.2 2006-12-18 (Gentoo)
BugBuddy Version: 2.17.3

System: Linux 2.6.17-gentoo-r4 #6 SMP PREEMPT Sat Aug 5 18:53:09 GMT 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 135512064 vsize: 0 resident: 135512064 share: 0 rss: 21356544 rss_rlim: 0
CPU usage: start_time: 1168294861 rtime: 0 utime: 772 stime: 0 cutime:724 cstime: 0 timeout: 48 it_real_value: 0 frequency: 109

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)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1220999504 (LWP 30734)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1220999504 (LWP 30734))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libc.so.6
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_return_if_fail_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 gtk_container_remove
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 glade_gtk_container_remove_child
    from /usr/lib/glade3/modules/libgladegtk.so
  • #12 glade_widget_adaptor_remove
    from /usr/lib/libgladeui-1.so.4
  • #13 glade_widget_set_project
    from /usr/lib/libgladeui-1.so.4
  • #14 glade_widget_remove_child
    from /usr/lib/libgladeui-1.so.4
  • #15 glade_project_open
    from /usr/lib/libgladeui-1.so.4
  • #16 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #17 glade_app_remove_project
    from /usr/lib/libgladeui-1.so.4
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
** CRITICAL **: Cannot embed a window that is already realized or embedded
aborting...
** (glade-3:30734): WARNING **: Instantiatable class 'GtkMenuShell' built without a 'generic-name'
Gdk-CRITICAL **: gdk_display_get_n_screens: assertion `GDK_IS_DISPLAY (display)' failed
aborting...
** (glade-3:30734): WARNING **: devhelp had bad return code: '6'
running command line:  /usr/bin/python2.4 -u /home/jere/workspace/Chaos/src/chaosmain.py
running command line:  /usr/bin/python2.4 -u /home/jere/workspace/Chaos/src/chaosmain.py
running command line:  /usr/bin/python2.4 -u /home/jere/workspace/Chaos/src/chaosmain.py
Gtk-CRITICAL **: gtk_container_remove: assertion `GTK_IS_TOOLBAR (container) || widget->parent == GTK_WIDGET (container)' failed
aborting...
--------------------------------------------------
Comment 1 Juan Pablo Ugarte 2007-04-24 21:23:54 UTC
i have committed a fix in svn trunk and gnome 2.18 branch that make not to hold references to internal widget!

can you check if this bug is still present?

thanks

Juan Pablo
Comment 2 Bruno Boaventura 2007-07-02 23:59:50 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!