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 441227 - crash in Text Editor: save as...
crash in Text Editor: save as...
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-25 16:33 UTC by jim.pelton
Modified: 2007-05-25 16:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description jim.pelton 2007-05-25 16:33:11 UTC 
Version: 2.15.9

What were you doing when the application crashed?
save as...


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.2948.fc6 #1 SMP Fri Apr 27 19:48:40 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 70836224 vsize: 0 resident: 70836224 share: 0 rss: 24625152 rss_rlim: 0
CPU usage: start_time: 1180104230 rtime: 0 utime: 974 stime: 0 cutime:898 cstime: 0 timeout: 76 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 -1208780032 (LWP 22396)]
(no debugging symbols found)
0x00e13402 in __kernel_vsyscall ()

+ Trace 136023

Thread 1 (Thread -1208780032 (LWP 22396))

  • #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 (177130 sec old) ---------------------
beryl: Couldn't bind redirected window 0x1000204 to texture
beryl: pixmap 0x1c000a4 can't be bound to texture
beryl: Couldn't bind redirected window 0x100022a to texture
beryl: pixmap 0x1c000a6 can't be bound to texture
beryl: Couldn't bind redirected window 0x1000204 to texture
beryl: pixmap 0x1c000a4 can't be bound to texture
beryl: Couldn't bind redirected window 0x100022a to texture
beryl: pixmap 0x1c000a4 can't be bound to texture
beryl: Couldn't bind redirected window 0x100022a to texture
beryl: pixmap 0x1c000a6 can't be bound to texture
beryl: Couldn't bind redirected window 0x1000204 to texture
beryl: pixmap 0x1c000a4 can't be bound to texture
beryl: Couldn't bind redirected window 0x100022a to texture
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Pedro Villavicencio 2007-05-25 16:45:01 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 ***