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 611201 - crash in Anjuta IDE: I was just editing the f...
crash in Anjuta IDE: I was just editing the f...
Status: RESOLVED DUPLICATE of bug 605881
Product: gtksourceview
Classification: Platform
Component: General
git master
Other All
: High critical
: ---
Assigned To: GTK Sourceview maintainers
GTK Sourceview maintainers
Depends on:
Blocks:
 
 
Reported: 2010-02-26 17:38 UTC by Jonh Wendell
Modified: 2010-02-27 12:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Description Jonh Wendell 2010-02-26 17:38:38 UTC 
Version: 2.29.91.0

What were you doing when the application crashed?
I was just editing the file when it crashed


Distribution: Ubuntu 9.10 (karmic)
Gnome Release: 2.28.1 2009-11-03 (Ubuntu)
BugBuddy Version: 2.28.0

System: Linux 2.6.31-19-generic #56-Ubuntu SMP Thu Jan 28 01:26:53 UTC 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10604000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: globalmenu-plugin, gnomebreakpad, canberra-gtk-module

Memory status: size: 101904384 vsize: 101904384 resident: 36556800 share: 17620992 rss: 36556800 rss_rlim: 18446744073709551615
CPU usage: start_time: 1267193269 rtime: 4983 utime: 4756 stime: 227 cutime:1184 cstime: 270 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb54a8b70 (LWP 7114)]
0x002c2422 in __kernel_vsyscall ()

+ Trace 220738

Thread 1 (Thread 0xb770a720 (LWP 7076))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 idle_scan_regions
    at gtksourcecompletionwordsbuffer.c line 287
  • #7 ??
    from /lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #9 ??
    from /lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #11 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 main
    at main.c line 248 

	Inferior 1 [process 7076] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (68 sec old) ---------------------
** (evolution:1812): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
** (evolution:1812): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
** (evolution:1812): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
** (evolution:1812): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
** (evolution:1812): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
** (evolution:1812): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
(anjuta:7076): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkMenu'
(anjuta:7076): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
--------------------------------------------------
Comment 1 Johannes Schmid 2010-02-26 21:46:40 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 Jonh Wendell 2010-02-27 01:19:11 UTC 
perhaps it's a bug in gtksourceview... let's see what's their developers think.
Comment 3 Jonh Wendell 2010-02-27 11:26:22 UTC 
why NEEDINFO? the backtrace clearly shows the symbols from gtksourceview...
Comment 4 Johannes Schmid 2010-02-27 12:00:53 UTC 
Sorry, the backtrace looked incomplete in the bug mail and I didn't check closely. Anyway, this was already reported...

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 bug 605881 ***