GNOME Bugzilla – Bug 401268
crash in Terminal: resizing term
Last modified: 2007-01-28 03:12:37 UTC
Version: 2.17.90 What were you doing when the application crashed? I just separated 2 tabs of gnome-terminal and resized them a bit fast. It seems the bug was triggered by moving/resizing the term which had screen/irssi in it but this problem raised only since I moved from 2.16 to 2.17 and latest vte Distribution: Gentoo Base System version 1.12.9 Gnome Release: 2.17.90 2007-01-24 (Gentoo) BugBuddy Version: 2.17.3 System: Linux 2.6.17-suspend2-r6 #1 SMP PREEMPT Sun Nov 26 21:41:30 CET 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 53907456 vsize: 0 resident: 53907456 share: 0 rss: 18796544 rss_rlim: 0 CPU usage: start_time: 1169887007 rtime: 0 utime: 922 stime: 0 cutime:837 cstime: 0 timeout: 85 it_real_value: 0 frequency: 266 Backtrace was generated from '/usr/bin/gnome-terminal' Really redefine built-in command "frame"? (y or n) [answered Y; input not from terminal] Really redefine built-in command "thread"? (y or n) [answered Y; input not from terminal] Really redefine built-in command "start"? (y or n) [answered Y; input not from terminal] Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1228114224 (LWP 5129)] [New Thread -1245598832 (LWP 5329)] _______________________________________________________________________________ eax:FFFFFE00 ebx:00001602 ecx:BF809B08 edx:00000000 eflags:00000293 esi:BF80A3A0 edi:00000000 esp:BF809A24 ebp:BF809B18 eip:FFFFE410 cs:0073 ds:007B es:007B fs:0000 gs:0033 ss:007B o d I t S z A p C [007B:BF809A24]---------------------------------------------------------[stack] BF809A54 : B0 42 B2 B7 78 9A 80 BF - 00 00 00 00 F0 9B 80 BF .B..x........... BF809A44 : 08 9B 80 BF 00 00 00 00 - 3C 2E DC B7 3C 2E DC B7 ........<...<... BF809A34 : 50 FF F8 B7 00 00 00 00 - A5 9F F5 B7 02 16 00 00 P............... BF809A24 : 18 9B 80 BF 00 00 00 00 - 08 9B 80 BF EB 22 8F B7 .............".. [007B:BF80A3A0]---------------------------------------------------------[ data] BF80A3A0 : 61 00 00 00 01 00 00 00 - 01 00 00 00 01 00 00 00 a............... BF80A3B0 : 63 00 00 00 09 00 00 00 - 01 00 00 00 01 00 00 00 c............... [0073:FFFFE410]---------------------------------------------------------[ code] 0xffffe410 <__kernel_vsyscall+16>: pop %ebp 0xffffe411 <__kernel_vsyscall+17>: pop %edx 0xffffe412 <__kernel_vsyscall+18>: pop %ecx 0xffffe413 <__kernel_vsyscall+19>: ret 0xffffe414 <_fini+1208279472>: nop 0xffffe415 <_fini+1208279473>: nop ------------------------------------------------------------------------------ 0xffffe410 in __kernel_vsyscall ()
+ Trace 105624
----------- .xsession-errors (1040 sec old) --------------------- Gossip logs output --------------------------------------------------
better summary
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 348814 ***
sorry for the duplicate, I should have searched a bit before. Does bug-buddy implements some way of finding duplicates in 2.17 or is it still a future feature ?
Bruno, Gilles: this is really a dup of 400671, which is fixed in vte svn HEAD.
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 400671 ***