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 532894 - crash in Anjuta IDE: closed all message windo...
crash in Anjuta IDE: closed all message windo...
Status: RESOLVED DUPLICATE of bug 467698
Product: anjuta
Classification: Applications
Component: unknown
2.4.x
Other All
: High critical
: ---
Assigned To: Anjuta maintainers
Anjuta maintainers
Depends on:
Blocks:
 
 
Reported: 2008-05-13 05:39 UTC by Brian Fransioli
Modified: 2008-05-13 09:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Brian Fransioli 2008-05-13 05:39:50 UTC 
Version: 2.4.1

What were you doing when the application crashed?
closed all message windows (right after a build project) then right clicked on msgs tab and clicked hide


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 92848128 vsize: 92848128 resident: 36708352 share: 15204352 rss: 36708352 rss_rlim: 4294967295
CPU usage: start_time: 1210610491 rtime: 17220 utime: 14165 stime: 3055 cutime:2540 cstime: 708 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/anjuta'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6e32980 (LWP 5936)]
[New Thread 0xb5fbab90 (LWP 5965)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 197598

Thread 1 (Thread 0xb6e32980 (LWP 5936))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (9 sec old) ---------------------
OPENING /home/terranpro/GSniff/src/main.c as C language file
OPENING /home/terranpro/GSniff/src/gsniff.h as C++ language file
OPENING /home/terranpro/GSniff/src/gsniff.h as C++ language file
OPENING /home/terranpro/GSniff/src/filtering.c as C language file
OPENING /home/terranpro/GSniff/src/filtering.c as C language file
OPENING /home/terranpro/GSniff/src/network.c as C language file
OPENING /home/terranpro/GSniff/src/network.c as C language file
OPENING /home/terranpro/GSniff/src/filtering.c as C language file
OPENING /home/terranpro/GSniff/src/gsniff.h as C++ language file
OPENING /home/terranpro/GSniff/src/gsni
(anjuta:5936): Gdk-CRITICAL **: gdk_colormap_get_screen: assertion `GDK_IS_COLORMAP (cmap)' failed
(anjuta:5936): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
(anjuta:5936): Gdk-CRITICAL **: gdk_colormap_get_visual: assertion `GDK_IS_COLORMAP (colormap)' failed
--------------------------------------------------
Comment 1 Johannes Schmid 2008-05-13 09:11:28 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 467698 ***