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 335800 - startup crash
startup crash
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-03-24 07:37 UTC by chris
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Description chris 2006-03-24 07:38:09 UTC 
Distribution: Debian 3.1
Package: anjuta
Severity: major
Version: GNOME2.10.2 1.2.4
Gnome-Distributor: Debian
Synopsis: startup crash
Bugzilla-Product: anjuta
Bugzilla-Component: core application
Bugzilla-Version: 1.2.4
BugBuddy-GnomeVersion: 2.0 (2.8.1)
Description:
Description of the crash:
I just installed on Debian.  When I run it, it shows a splash image,
then prints:
** Message: Initializing AP class
** Message: Initializing AP Instance

Then a dialogue pops up saying "The Application "Anjuta" has quit
unexpectedly."

Steps to reproduce the crash:
0. On Debian, kernel 2.6.8-2-k7, stable branch.
1. Install Anjuta from stable branch.
2. Various problems insue when trying to create a project via the
wizard.
3. Install extras (automake, libtool, autogen, indent, ctags) from
stable branch.
4. Upgrade anjuta via Debian testing branch.
5. Run anjuta from command line.

Expected Results:
Crash.

How often does this happen?
Every time.

Additional Information:



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/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 1091169696 (LWP 28042)]
(no debugging symbols found)
0x404e220e in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 67201

Thread 1 (Thread 1091169696 (LWP 28042))

  • #0 __waitpid_nocancel
    from /lib/tls/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_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #5 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #6 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #9 _gtk_tree_selection_emit_changed
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 gtk_tree_view_set_model
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 anjuta_encodings_init
  • #12 anjuta_new
  • #13 main
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0 




------- Bug created by bug-buddy at 2006-03-24 07:38 -------
Comment 1 Karsten Bräckelmann 2006-03-24 19:24:08 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 324572 and its duplicates.

*** This bug has been marked as a duplicate of 324572 ***
Comment 2 Karsten Bräckelmann 2006-03-24 19:25:04 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 :( ...