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 330843 - Crash on startup.
Crash on startup.
Status: VERIFIED DUPLICATE of bug 324572
Product: anjuta
Classification: Applications
Component: core application
1.2.4
Other other
: High critical
: ---
Assigned To: Anjuta maintainers
Anjuta maintainers
Depends on:
Blocks:
 
 
Reported: 2006-02-11 23:32 UTC by cmetzler
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Description cmetzler 2006-02-11 23:32:20 UTC 
Distribution: Debian testing/unstable
Package: anjuta
Severity: critical
Version: GNOME2.10.2 1.2.4
Gnome-Distributor: Debian
Synopsis: Crash on startup.
Bugzilla-Product: anjuta
Bugzilla-Component: core application
Bugzilla-Version: 1.2.4
BugBuddy-GnomeVersion: 2.0 (2.10.1)
Description:
Description of the crash:
Starting anjuta from the command line with "anjuta", the messages:

** Message: Initializing AP class
** Message: Initializing AP Instance

are written to the terminal window and the Anjuta splash screen
appears;
then, the Gnome Error / crash window appears, giving the opportunity to
quit
or send this message.

Steps to reproduce the crash:
1. Type "anjuta" at a command line.
2. Watch the two messages appear in the terminal window, and the splash
screen appear over the desktop.
3. Watch the crash.

Expected Results:
Normal startup.

How often does this happen?
Every time.

Additional Information:
AMD64 machine running AMD64 port of Anjuta under Debian.




Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912586896608 (LWP 25368)]
(no debugging symbols found)
0x00002aaaace70355 in waitpid () from /lib/libpthread.so.0

+ Trace 66103

Thread 1 (Thread 46912586896608 (LWP 25368))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 anjuta_encoding_get_encodings
  • #4 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #5 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #6 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #8 gtk_tree_view_set_model
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 anjuta_encodings_init
  • #10 anjuta_new
  • #11 main
  • #0 waitpid
    from /lib/libpthread.so.0 




------- Bug created by bug-buddy at 2006-02-11 23:32 -------
Comment 1 Karsten Bräckelmann 2006-02-11 23:54:06 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


Same stacktrace as bug 324572.

*** This bug has been marked as a duplicate of 324572 ***
Comment 2 Karsten Bräckelmann 2006-02-11 23:55:41 UTC 
quoting bug 324572 comment 3:
> Fixed in anjuta-1.2.4a which is availible at www.anjuta.org!
Comment 3 Naba Kumar 2006-12-04 09:58:36 UTC 
Closing all fixed bugs. Sorry for the mass update :( ...