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 531144 - crash in Anjuta IDE: Anjuta crashed when tyin...
crash in Anjuta IDE: Anjuta crashed when tyin...
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-02 23:22 UTC by patrick.zanon
Modified: 2008-05-03 08:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description patrick.zanon 2008-05-02 23:22:30 UTC 
Version: 2.4.0

What were you doing when the application crashed?
Anjuta crashed when tying to generate the project (Shift+F11). I that moment two other files from an external project were displayed in the Documents area. Crashes are systematic.


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

System: Linux 2.6.24-1-686 #1 SMP Sat Apr 19 00:37:55 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 69406720 vsize: 69406720 resident: 36950016 share: 20336640 rss: 36950016 rss_rlim: 4294967295
CPU usage: start_time: 1209770256 rtime: 674 utime: 612 stime: 62 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6e4f720 (LWP 18586)]
[New Thread 0xb550fb90 (LWP 18587)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 196721

Thread 1 (Thread 0xb6e4f720 (LWP 18586))

  • #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 ??
    from /usr/lib/libgtkembedmoz.so.0d
  • #6 ??
  • #7 __pthread_mutex_unlock_usercnt
    from /lib/i686/cmov/libpthread.so.0
  • #8 <signal handler called>
  • #9 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
(anjuta:18320): Gdk-CRITICAL **: gdk_colormap_get_screen: assertion `GDK_IS_COLORMAP (cmap)' failed
(anjuta:18320): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
(anjuta:18320): Gdk-CRITICAL **: gdk_colormap_get_visual: assertion `GDK_IS_COLORMAP (colormap)' failed
** Message: Spawning script
(anjuta:18586): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(anjuta:18586): Gdk-CRITICAL **: gdk_colormap_get_screen: assertion `GDK_IS_COLORMAP (cmap)' failed
(anjuta:18586): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
(anjuta:18586): Gdk-CRITICAL **: gdk_colormap_get_visual: assertion `GDK_IS_COLORMAP (colormap)' failed
--------------------------------------------------
Comment 1 Johannes Schmid 2008-05-03 08:17:26 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 ***