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 464226 - crash in Glade Interface Designer: just playing with the gl...
crash in Glade Interface Designer: just playing with the gl...
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-08-07 04:09 UTC by catesjay
Modified: 2007-09-02 16:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description catesjay 2007-08-07 04:09:02 UTC 
What were you doing when the application crashed?
just playing with the glade interface designer for the first time, trying to see if i could view source code of selected objects


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 86831104 vsize: 0 resident: 86831104 share: 0 rss: 19513344 rss_rlim: 0
CPU usage: start_time: 1186458997 rtime: 0 utime: 397 stime: 0 cutime:369 cstime: 0 timeout: 28 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 -1208314160 (LWP 14423)]
(no debugging symbols found)
0x00437402 in __kernel_vsyscall ()

+ Trace 153376

Thread 1 (Thread -1208314160 (LWP 14423))

  • #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


Pascal Terjan





          2007-09-02 16:08:41 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 ***