Bug 325031 – can't open anjuta

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 325031 - can't open anjuta


Summary:	can't open anjuta


Status:	VERIFIED DUPLICATE of bug 324572

Product:	anjuta
Classification:	Applications
Component:	core application
Version:	unspecified
Hardware:	Other other

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2005-12-27 00:39 UTC by Pablo Olivarez
Modified:	2009-08-15 18:40 UTC

See Also:
GNOME target:	---
GNOME version:	2.11/2.12

Description Pablo Olivarez 2005-12-27 00:39:19 UTC

Distribution: Slackware Slackware 10.2.0
Package: anjuta
Severity: Normal
Version: GNOME2.12.2 unspecified
Gnome-Distributor: Dropline GNOME
Synopsis: can't open anjuta
Bugzilla-Product: anjuta
Bugzilla-Component: core application
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.12.0)
Description:
Description of the crash:


Steps to reproduce the crash:
1. click in the menu
2. show tje window
3. 

Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

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

Using host libthread_db library
"/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1228589376 (LWP 16122)]
0xb78463ee in __waitpid_nocancel () from
/lib/tls/libpthread.so.0

+ Trace 64816

Thread 1 (Thread -1228589376 (LWP 16122))

#0 __waitpid_nocancel
from /lib/tls/libpthread.so.0
#1 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 ??
#3 ??
#4 ??
#5 ??
#6 ??
#7 vfprintf
from /lib/tls/libc.so.6
#8 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#9 ??
from /usr/lib/libgobject-2.0.so.0
#10 ??
#11 ??
#12 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#13 ??
#14 ??
#15 ??
#16 ??
#17 ??
#18 ??
#19 g_param_spec_override
from /usr/lib/libgobject-2.0.so.0
#20 ??
#21 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#22 ??
#23 ??
#24 ??
#25 ??
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
#31 g_object_steal_data
from /usr/lib/libgobject-2.0.so.0
#32 ??
#33 ??
#34 ??
#35 ??
#36 ??
#37 ??
#38 g_value_set_instance
from /usr/lib/libgobject-2.0.so.0
#39 ??
#40 ??
#41 ??
#42 ??
#43 ??
#44 ??
#45 ??
from /usr/lib/libgobject-2.0.so.0
#46 ??
#47 ??
#48 ??
#49 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#50 ??
#0 __waitpid_nocancel
from /lib/tls/libpthread.so.0





Monosoft Soluciones Inform\xE1ticas
Tucapel Jim\xE9nez 56 Depto. 407 Santiago Centro.
Fono: 6887885.
Http://monosoft.no-ip.com


		
______________________________________________ 
Renovamos el Correo Yahoo! 
Nuevos servicios, m\xE1s seguridad 
http://correo.yahoo.es




------- Bug created by bug-buddy at 2005-12-27 00:39 -------

Comment 1 Teppo Turtiainen 2005-12-27 14:46:49 UTC

Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Comment 2 Johannes Schmid 2005-12-27 23:45:10 UTC


*** This bug has been marked as a duplicate of 324572 ***

Comment 3 Pablo Olivarez 2005-12-28 07:10:42 UTC

i fixed the problem with this patch http://bugzilla.gnome.org/attachment.cgi?id=56260&action=diff, thanks anyway

Comment 4 Naba Kumar 2006-12-04 10:03:39 UTC

Closing fixed bugs. Sorry about mass update :( ...