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 337419 - Anjuta Crashes on Startup.
Anjuta Crashes on Startup.
Status: VERIFIED DUPLICATE of bug 324572
Product: anjuta
Classification: Applications
Component: core application
unspecified
Other other
: High critical
: ---
Assigned To: Anjuta maintainers
Anjuta maintainers
Depends on:
Blocks:
 
 
Reported: 2006-04-05 18:11 UTC by Martin Klaffenboeck
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description Martin Klaffenboeck 2006-04-05 18:11:01 UTC
Distribution: Gentoo Base System version 1.6.14
Package: anjuta
Severity: Normal
Version: GNOME2.12.3 unspecified
Gnome-Distributor: Gentoo
Synopsis: Anjuta Crashes on Startup.
Bugzilla-Product: anjuta
Bugzilla-Component: core application
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.12.0)
Description:
Anjuta crashes on startup.  The console output is:

martin@notebook ~$ anjuta
** Message: Initializing AP class
** Message: Initializing AP Instance

I don't know whats happeing here.

This happens every time on anjuta 1.2.4

Martin


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)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 7098)]
0xb7a85238 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 16384 (LWP 7098))

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




------- Bug created by bug-buddy at 2006-04-05 18:11 -------

Comment 1 Karsten Bräckelmann 2006-04-05 18:27:54 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.


Identical stacktrace as bug 326130, which is a duplicate of bug 324572.

*** This bug has been marked as a duplicate of 324572 ***
Comment 2 Karsten Bräckelmann 2006-04-05 18:28:59 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:41 UTC
Closing all fixed bugs. Sorry for the mass update :( ...