GNOME Bugzilla – Bug 616993
crash in Terminal: i started it up
Last modified: 2010-04-28 03:29:18 UTC
Version: 2.30.0 What were you doing when the application crashed? i started it up Distribution: Gentoo Base System release 2.0.1 Gnome Release: 2.30.0 2010-04-06 (Gentoo) BugBuddy Version: 2.30.0 System: Linux 2.6.33-gentoo-r1 #1 SMP Tue Apr 13 09:42:00 EDT 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10706000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 122523648 vsize: 122523648 resident: 26923008 share: 13746176 rss: 26923008 rss_rlim: 18446744073709551615 CPU usage: start_time: 1272404024 rtime: 22 utime: 19 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-terminal' [Thread debugging using libthread_db enabled] 0xffffe424 in __kernel_vsyscall ()
+ Trace 221575
Thread 1 (Thread 0xb5cae820 (LWP 14080))
Inferior 1 [process 14080] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (216 sec old) --------------------- ERR:Ecore ecore.c:225 _ecore_magic_fail() Input handle is wrong type Expected: 76543210 - <UNKNOWN> Supplied: 00000000 - <UNKNOWN> ERR:Ecore ecore.c:228 _ecore_magic_fail() *** NAUGHTY PROGRAMMER!!! *** SPANK SPANK SPANK!!! *** Now go fix your code. Tut tut tut! ERR:Ecore ecore.c:215 _ecore_magic_fail() *** ECORE ERROR: Ecore Magic Check Failed!!! *** IN FUNCTION: ecore_job_del() ERR:Ecore ecore.c:225 _ecore_magic_fail() Input handle is wrong type Expected: 76543210 - <UNKNOWN> Supplied: 081fde78 - <UNKNOWN> ERR:Ecore ecore.c:228 _ecore_magic_fail() *** NAUGHTY PROGRAMMER!!! *** SPANK SPANK SPANK!!! *** Now go fix your code. Tut tut tut! --------------------------------------------------
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 bug 615232 ***