Bug 528316 – crash in Anjuta IDE:

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 528316 - crash in Anjuta IDE:


Summary:	crash in Anjuta IDE:


Status:	RESOLVED DUPLICATE of bug 467698

Product:	anjuta
Classification:	Applications
Component:	unknown
Version:	2.4.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Anjuta maintainers
QA Contact:	Anjuta maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-04-15 22:48 UTC by soria.jesus
Modified:	2008-04-16 07:09 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description soria.jesus 2008-04-15 22:48:17 UTC

Version: 2.4.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu Mar 27 17:45:04 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Cillop
Icon Theme: gartoon

Memory status: size: 60063744 vsize: 60063744 resident: 24260608 share: 15941632 rss: 24260608 rss_rlim: 4294967295
CPU usage: start_time: 1208299590 rtime: 472 utime: 440 stime: 32 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 0xb6e1c720 (LWP 15275)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 195326

Thread 1 (Thread 0xb6e1c720 (LWP 15275))

#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 ---------------------
** (anjuta:15275): CRITICAL **: anjuta_view_set_font: assertion `font_name != NULL' failed
(anjuta:15275): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
(anjuta:15275): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
(anjuta:15275): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
(anjuta:15275): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed
(anjuta:15275): Gdk-CRITICAL **: gdk_colormap_get_screen: assertion `GDK_IS_COLORMAP (cmap)' failed
(anjuta:15275): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
(anjuta:15275): Gdk-CRITICAL **: gdk_colormap_get_visual: assertion `GDK_IS_COLORMAP (colormap)' failed
--------------------------------------------------

Comment 1 Johannes Schmid 2008-04-16 07:09:21 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 ***