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 326294 - Can't run Anjuta 1.2.4
Can't run Anjuta 1.2.4
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-01-09 12:45 UTC by ktomx
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Description ktomx 2006-01-09 12:45:21 UTC 
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.10.0
Subject: Can't run Anjuta

Distribution: Debian testing/unstable
Package: anjuta
Severity: normal
Version: GNOME2.10.2 1.2.4
Gnome-Distributor: Debian
Synopsis: Can't run Anjuta
Bugzilla-Product: anjuta
Bugzilla-Component: core application
Bugzilla-Version: 1.2.4
BugBuddy-GnomeVersion: 2.0 (2.10.1)
Description:
Description of the crash:
After upgrade debian/linux Anjuta 1.2.4 can't run
Before upgrade was OK

Steps to reproduce the crash:
1.
2.
3.

Expected Results:


How often does this happen?
always

Additional Information:
reinstall anjuta 1.2.4 dosen't work


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 16384 (LWP 2197)]
(no debugging symbols found)
0x404d62a8 in waitpid () from /lib/libpthread.so.0

+ Trace 65063

Thread 1 (Thread 16384 (LWP 2197))

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



----------------------------------------------------------------------
Jedyny taki CZAT! >>> http://link.interia.pl/f18ee




------- Bug created by bug-buddy at 2006-01-09 12:45 -------
Comment 1 Victor Andrade 2006-02-23 21:41:57 UTC 
Anjuta crashed in the function on_stock_selection_changed() in anjuta-encodings.c . The function needs the member add_button in the structur anjuta_encodings_dialog. The member is initialized in anjuta_encodings_init(). 

I don't understand the code completely but I can see that on_stock_selection_changed() is called implicitely by gtk_tree_view_set_model() in line 716 of anjuta-encodings.c some lines before add_button and the structure itself is initialized. 

I copied the lines: 

anjuta_encodings_dialog = g_new0 (AnjutaEncodingsDialog, 1); 
anjuta_encodings_dialog->pref = pref; 
anjuta_encodings_dialog->add_button = add_button; 
anjuta_encodings_dialog->remove_button = remove_button; 
anjuta_encodings_dialog->up_button = up_button; 
anjuta_encodings_dialog->down_button = down_button; 
anjuta_encodings_dialog->supported_treeview = supported_treeview; 
anjuta_encodings_dialog->stock_treeview = stock_treeview; 
 
before the call to 
gtk_tree_view_set_model (GTK_TREE_VIEW (stock_treeview), model); 
 
I recompiled and now Anjuta works well.
Comment 2 Martin Stransky 2006-04-05 09:20:02 UTC 
I can reproduce it on FC5, proposed change works for me.
Comment 3 Johannes Schmid 2006-04-05 09:44:39 UTC 

*** This bug has been marked as a duplicate of 324572 ***
Comment 4 Naba Kumar 2006-12-04 09:58:34 UTC 
Closing all fixed bugs. Sorry for the mass update :( ...