GNOME Bugzilla – Bug 325348
Anjuta 2 STILL crashes on open
Last modified: 2009-08-15 18:40:50 UTC
Distribution: Debian testing/unstable Package: anjuta Severity: critical Version: GNOME2.10.2 2.0.x Gnome-Distributor: Debian Synopsis: Anjuta 2 STILL crashes on open Bugzilla-Product: anjuta Bugzilla-Component: core application Bugzilla-Version: 2.0.x BugBuddy-GnomeVersion: 2.0 (2.10.1) Description: Description of the crash: trying to start Anjuta causes an immediate crash. This appears to be similar but maybe different to an existing bug (which was never fixed on my system anyway). Steps to reproduce the crash: 1. Run Anjuta 2. Crash 3. Expected Results: I should see Anjuta and be able to open/start projects as I have in the past. How often does this happen? every fricken time. Additional Information: Upon launch from command line, I see the following: (anjuta:23252): libglade-CRITICAL **: glade_xml_build_interface: assertion `wid != NULL' failed (anjuta:23252): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed Don't know if it's related or not, but I post it. Running Debian. 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) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1223555392 (LWP 23252)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xb789a20e in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 64875
------- Bug created by bug-buddy at 2005-12-31 01:22 -------
Fixed in anjuta-1.2.4a which is availible at www.anjuta.org! 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. *** This bug has been marked as a duplicate of 324572 ***
Closing all fixed bugs. Sorry for the mass update :( ...