GNOME Bugzilla – Bug 445209
crash in Terminal: scrolling up inside the ...
Last modified: 2007-06-08 02:12:07 UTC
Version: 2.16.0 What were you doing when the application crashed? scrolling up inside the "less" program 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.2952.fc6 #1 SMP Wed May 16 18:59:18 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Enabled Memory status: size: 99487744 vsize: 0 resident: 99487744 share: 0 rss: 38535168 rss_rlim: 0 CPU usage: start_time: 1181138116 rtime: 0 utime: 8339 stime: 0 cutime:5788 cstime: 0 timeout: 2551 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-terminal' (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 -1208953136 (LWP 9841)] [New Thread -1221006448 (LWP 9846)] (no debugging symbols found) 0x00471402 in __kernel_vsyscall ()
+ Trace 139133
Thread 1 (Thread -1208953136 (LWP 9841))
----------- .xsession-errors (493 sec old) --------------------- ** Message: ATK_ROLE_TOOLTIP object found, but doesn't look like a tooltip. ** Message: ATK_ROLE_TOOLTIP object found, but doesn't look like a tooltip. [error] DefaultInputHandler: Invalid key stroke: C+e C+BACK_QUOTE [error] DefaultInputHandler: Invalid key stroke: C+e C+BACK_QUOTE [error] DefaultInputHandler: Invalid key stroke: C+e C+BACK_QUOTE [error] DefaultInputHandler: Invalid key stroke: C+e C+BACK_QUOTE GLib-ERROR **: gmem.c:135: failed to allocate 4294967259 bytes aborting... GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized ** (bug-buddy:16543): WARNING **: Couldn't load icon for Open Folder --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 389538 ***