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 382727 - crash in Text Editor: nothing. the harddrive ...
crash in Text Editor: nothing. the harddrive ...
Status: RESOLVED DUPLICATE of bug 352099
Product: gedit
Classification: Applications
Component: general
2.15.x
Other All
: High critical
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2006-12-05 20:10 UTC by rdboon
Modified: 2006-12-05 21:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description rdboon 2006-12-05 20:10:24 UTC 
Version: 2.15.9

What were you doing when the application crashed?
nothing.  the harddrive has been crunching for hours.  I disconnected the lan cable. this popped up			


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:45:28 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 1167462400 vsize: 0 resident: 1167462400 share: 0 rss: 386473984 rss_rlim: 0
CPU usage: start_time: 1165348999 rtime: 0 utime: 570 stime: 0 cutime:323 cstime: 0 timeout: 247 it_real_value: 0 frequency: 0

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

(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 -1209058752 (LWP 7278)]
(no debugging symbols found)
0x00fc0402 in __kernel_vsyscall ()

+ Trace 91845

Thread 1 (Thread -1209058752 (LWP 7278))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 g_malloc
    from /lib/libglib-2.0.so.0
  • #10 g_strndup
    from /lib/libglib-2.0.so.0
  • #11 gedit_convert_from_utf8
  • #12 gedit_convert_to_utf8
  • #13 gedit_document_new
  • #14 gedit_document_new
  • #15 g_source_get_current_time
    from /lib/libglib-2.0.so.0
  • #16 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #17 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #19 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 main
  • #0 __kernel_vsyscall 






Comment 1


Susana





          2006-12-05 21:34:43 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 352099 ***