Bug 423601 – crash in Text Editor: gedit a file in /usr/sha...

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 423601 - crash in Text Editor: gedit a file in /usr/sha...


Summary:	crash in Text Editor: gedit a file in /usr/sha...


Status:	RESOLVED DUPLICATE of bug 364620

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:

Depends on:
Blocks:

Reported:	2007-03-28 06:05 UTC by foddyy
Modified:	2007-04-28 07:03 UTC

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

Description foddyy 2007-03-28 06:05:20 UTC

Version: 2.16.1

What were you doing when the application crashed?
gedit a file in /usr/share/applications/


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

Memory status: size: 64147456 vsize: 0 resident: 64147456 share: 0 rss: 22577152 rss_rlim: 0
CPU usage: start_time: 1175061820 rtime: 0 utime: 104 stime: 0 cutime:92 cstime: 0 timeout: 12 it_real_value: 0 frequency: 78

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 -1227675984 (LWP 6186)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 122813

Thread 1 (Thread -1227675984 (LWP 6186))

#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 FcFreeTypeCharIndex
from /usr/lib/libfontconfig.so.1
#5 pango_fc_font_lock_face
from /usr/lib/libpangoft2-1.0.so.0
#6 pango_fc_font_get_glyph
from /usr/lib/libpangoft2-1.0.so.0
#7 script_engine_init
from /usr/lib/pango/1.5.0/modules/pango-hangul-fc.so
#8 script_engine_init
from /usr/lib/pango/1.5.0/modules/pango-hangul-fc.so
#9 pango_coverage_new
from /usr/lib/libpango-1.0.so.0
#10 pango_shape
from /usr/lib/libpango-1.0.so.0
#11 pango_layout_set_width
from /usr/lib/libpango-1.0.so.0
#12 pango_layout_iter_get_char_extents
from /usr/lib/libpango-1.0.so.0
#13 pango_layout_iter_get_char_extents
from /usr/lib/libpango-1.0.so.0
#14 pango_layout_iter_get_char_extents
from /usr/lib/libpango-1.0.so.0
#15 gtk_text_layout_get_line_display
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_text_layout_new
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_text_layout_wrap
from /usr/lib/libgtk-x11-2.0.so.0
#18 _gtk_text_btree_validate_line
from /usr/lib/libgtk-x11-2.0.so.0
#19 gtk_text_layout_validate_yrange
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_text_view_set_cursor_visible
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_text_view_move_mark_onscreen
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_text_view_move_mark_onscreen
from /usr/lib/libgtk-x11-2.0.so.0
#23 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#24 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#25 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#26 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#27 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#28 main
#0 __kernel_vsyscall

Comment 1 Pascal Terjan 2007-04-28 07:03:07 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 364620 ***