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 368988 - crash in Text Editor:
crash in Text Editor:
Status: RESOLVED DUPLICATE of bug 354046
Product: gedit
Classification: Applications
Component: general
Other All
: High critical
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Reported: 2006-11-01 17:58 UTC by markussutter
Modified: 2006-11-01 18:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16

Description markussutter 2006-11-01 17:58:55 UTC
Version: 2.16.1

What were you doing when the application crashed?

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

Memory status: size: 58785792 vsize: 0 resident: 58785792 share: 0 rss: 22441984 rss_rlim: 0
CPU usage: start_time: 1162403929 rtime: 0 utime: 54 stime: 0 cutime:47 cstime: 0 timeout: 7 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/".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227016528 (LWP 11054)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1227016528 (LWP 11054))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/
  • #2 gnome_gtk_module_info_get
    from /usr/lib/
  • #3 <signal handler called>
  • #4 g_utf8_validate
    from /usr/lib/
  • #5 gedit_convert_from_utf8
  • #6 gedit_convert_to_utf8
  • #7 gedit_document_new
  • #8 gedit_document_new
  • #9 g_source_get_current_time
    from /usr/lib/
  • #10 g_main_context_dispatch
    from /usr/lib/
  • #11 g_main_context_check
    from /usr/lib/
  • #12 g_main_loop_run
    from /usr/lib/
  • #13 gtk_main
    from /usr/lib/
  • #14 main
  • #0 __kernel_vsyscall

Comment 1 Paolo Maggi 2006-11-01 18:47:52 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 (bug #354046) in order to help the

In particular, the attached 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 for more information on how to do so. 

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