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 437769 - crash in Text Editor: opening an existing file...
crash in Text Editor: opening an existing file...
Status: RESOLVED DUPLICATE of bug 375496
Product: gedit
Classification: Applications
Component: general
2.15.x
Other All
: High critical
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2007-05-11 21:09 UTC by raymondf
Modified: 2007-05-12 01:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description raymondf 2007-05-11 21:09:28 UTC 
Version: 2.15.9

What were you doing when the application crashed?
opening an existing file for editing, when I click when the vertical scroll bar at the right hand side during choosing the file to edit, "gedit" crashed.


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.20-1.2944.fc6 #1 SMP Tue Apr 10 17:27:49 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 177459200 vsize: 0 resident: 177459200 share: 0 rss: 27209728 rss_rlim: 0
CPU usage: start_time: 1178711087 rtime: 0 utime: 20476 stime: 0 cutime:19298 cstime: 0 timeout: 1178 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 -1208349952 (LWP 13137)]
(no debugging symbols found)
0x00a5c402 in __kernel_vsyscall ()

+ Trace 133699

Thread 1 (Thread -1208349952 (LWP 13137))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/libc.so.6
  • #5 gtk_file_info_render_icon
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 gtk_file_chooser_button_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 fs_module_init
    from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
  • #8 fs_module_init
    from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
  • #9 fs_module_init
    from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
  • #10 g_source_is_destroyed
    from /lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #12 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #14 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (354256 sec old) ---------------------
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Christian Kirbach 2007-05-12 01:25:56 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 375496 ***