GNOME Bugzilla – Bug 405239
crash in Terminal: 새로운 터미널 설정을 만드려고 했음
Last modified: 2007-11-27 02:32:05 UTC
Version: 2.16.0 What were you doing when the application crashed? 새로운 터미널 설정을 만드려고 했음 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.19-1.2895.fc6 #1 SMP Wed Jan 10 18:32:37 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled Memory status: size: 141918208 vsize: 0 resident: 141918208 share: 0 rss: 18944000 rss_rlim: 0 CPU usage: start_time: 1170825981 rtime: 0 utime: 797 stime: 0 cutime:726 cstime: 0 timeout: 71 it_real_value: 0 frequency: 1 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 -1208621360 (LWP 449)] [New Thread -1234420848 (LWP 455)] (no debugging symbols found) 0x003c6402 in __kernel_vsyscall ()
+ Trace 108649
Thread 1 (Thread -1208621360 (LWP 449))
Reporter, could you explain how did happened in English? Also, can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
*** Bug 409553 has been marked as a duplicate of this bug. ***
*** Bug 420615 has been marked as a duplicate of this bug. ***
*** Bug 435196 has been marked as a duplicate of this bug. ***
*** Bug 435978 has been marked as a duplicate of this bug. ***
*** Bug 441187 has been marked as a duplicate of this bug. ***
(In reply to comment #6) > *** Bug 441187 has been marked as a duplicate of this bug. *** > Here's a stack trace with debugging symbols as requested. Let me if there's more you need: 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 18:46:45 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 122974208 vsize: 0 resident: 122974208 share: 0 rss: 26439680 rss_rlim: 0 CPU usage: start_time: 1180098272 rtime: 0 utime: 2440 stime: 0 cutime:2116 cstime: 0 timeout: 324 it_real_value: 0 frequency: 193 Backtrace was generated from '/usr/bin/gnome-terminal' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1209076016 (LWP 28446)] [New Thread -1227555952 (LWP 28451)] 0x00a51402 in __kernel_vsyscall ()
+ Trace 136022
Thread 1 (Thread -1209076016 (LWP 28446))
----------- .xsession-errors (5389 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 ...Too much output, ignoring rest... --------------------------------------------------
*** Bug 447576 has been marked as a duplicate of this bug. ***
last trace is good. could you please retry with Gnome 2.18 ?
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 499797 ***