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 432698 - crash in Glade Interface Designer: Deleting an alignment wi...
crash in Glade Interface Designer: Deleting an alignment wi...
Status: RESOLVED DUPLICATE of bug 325759
Product: glade-legacy
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Damon Chaplin
Damon Chaplin
Depends on:
Blocks:
 
 
Reported: 2007-04-23 18:01 UTC by rhunnicutt
Modified: 2007-05-15 17:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description rhunnicutt 2007-04-23 18:01:41 UTC 
What were you doing when the application crashed?
Deleting an alignment widget with a scrolled window widget inside


Distribution: Red Hat Enterprise Linux Client release 5 (Tikanga)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 85622784 vsize: 0 resident: 85622784 share: 0 rss: 20725760 rss_rlim: 0
CPU usage: start_time: 1177349676 rtime: 0 utime: 2606 stime: 0 cutime:2551 cstime: 0 timeout: 55 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208191280 (LWP 9632)]
(no debugging symbols found)
0x008e5402 in __kernel_vsyscall ()

+ Trace 130063

Thread 1 (Thread -1208191280 (LWP 9632))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #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 /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #10 gail_tree_view_new
    from /usr/lib/gtk-2.0/modules/libgail.so
  • #11 g_source_is_destroyed
    from /lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #13 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #15 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #16 g_cclosure_marshal_VOID__OBJECT
  • #17 __libc_start_main
    from /lib/libc.so.6
  • #18 g_cclosure_marshal_VOID__OBJECT
  • #0 __kernel_vsyscall 






Comment 1


Christian Kirbach





          2007-05-15 17:39:54 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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