Bug 416915 – crash in Text Editor: cercando di installare h...

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 416915 - crash in Text Editor: cercando di installare h...


Summary:	crash in Text Editor: cercando di installare h...


Status:	RESOLVED INCOMPLETE

Product:	gedit
Classification:	Applications
Component:	general
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Gedit maintainers
QA Contact:	Gedit maintainers

URL:
Whiteboard:

Duplicates:	420741 422490 (view as bug list)
Depends on:
Blocks:

Reported:	2007-03-10 21:57 UTC by fabrizio_vignali
Modified:	2007-06-26 13:40 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description fabrizio_vignali 2007-03-10 21:57:06 UTC

Version: 2.16.1

What were you doing when the application crashed?
cercando di installare hamachi per linux


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 46968832 vsize: 0 resident: 46968832 share: 0 rss: 22245376 rss_rlim: 0
CPU usage: start_time: 1173563764 rtime: 0 utime: 180 stime: 0 cutime:166 cstime: 0 timeout: 14 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227331392 (LWP 5578)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 117554

Thread 1 (Thread -1227331392 (LWP 5578))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 initgc
from /usr/lib/libpython2.4.so.1.0
#5 PyGC_Collect
from /usr/lib/libpython2.4.so.1.0
#6 gedit_python_garbage_collect
#7 gedit_plugins_engine_garbage_collect
#8 _gedit_window_move_tab_to_new_window
#9 g_cclosure_marshal_VOID__OBJECT
from /usr/lib/libgobject-2.0.so.0
#10 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#11 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#15 _gedit_window_move_tab_to_new_window
#16 g_cclosure_marshal_VOID__OBJECT
from /usr/lib/libgobject-2.0.so.0
#17 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#21 gedit_module_get_path
#22 gtk_notebook_popup_enable
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_container_foreach
from /usr/lib/libgtk-x11-2.0.so.0
#24 gedit_notebook_remove_all_tabs
#25 gedit_window_close_all_tabs
#26 gedit_app_get_default
#27 _gedit_app_restore_window
#28 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#29 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#30 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#31 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#32 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#33 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#34 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#35 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#36 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#37 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#38 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#39 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#40 main
#0 __kernel_vsyscall

Comment 1 palfrey 2007-03-10 23:25:39 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. Thanks in advance!

(Probable duplicate of Bug 354347)

Comment 2 Susana 2007-03-28 11:46:21 UTC

*** Bug 422490 has been marked as a duplicate of this bug. ***

Comment 3 Susana 2007-03-28 11:47:32 UTC

*** Bug 420741 has been marked as a duplicate of this bug. ***

Comment 4 Paolo Borelli 2007-06-26 13:40:53 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!