GNOME Bugzilla – Bug 539572
crash in Anjuta IDE: Crashed when minimizing ...
Last modified: 2008-06-22 10:41:18 UTC
Version: 2.4.0 What were you doing when the application crashed? Crashed when minimizing terminal. Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 134832128 vsize: 134832128 resident: 60104704 share: 19382272 rss: 60104704 rss_rlim: 4294967295 CPU usage: start_time: 1214118446 rtime: 26953 utime: 25227 stime: 1726 cutime:982 cstime: 135 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/anjuta' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6e73720 (LWP 3043)] [New Thread 0xb665ab90 (LWP 3046)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 201067
Thread 1 (Thread 0xb6e73720 (LWP 3043))
----------- .xsession-errors --------------------- OPENING /home/joan/mud/cfmud/src/interp.c as C language file OPENING /home/joan/mud/cfmud/src/db.c as C language file OPENING /home/joan/mud/cfmud/src/handler.c as C language file OPENING /home/joan/mud/cfmud/src/act_wiz.c as C language file OPENING /home/joan/mud/cfmud/src/build.c as C language file OPENING /home/joan/mud/cfmud/src/boards.c as C language file OPENING /home/joan/mud/cfmud/src/collections.c as C language file OPENING /home/joan/mud/cfmud/src/mud.h (anjuta:3043): Gdk-CRITICAL **: gdk_colormap_get_screen: assertion `GDK_IS_COLORMAP (cmap)' failed (anjuta:3043): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (anjuta:3043): Gdk-CRITICAL **: gdk_colormap_get_visual: assertion `GDK_IS_COLORMAP (colormap)' failed warning: .dynamic section for "/usr/lib/libfreetype.so.6" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
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 467698 ***