GNOME Bugzilla – Bug 423253
crash in Panel: I was just running the a...
Last modified: 2007-03-29 15:36:16 UTC
Version: 2.18.0 What were you doing when the application crashed? I was just running the applications of the System-->Preferences menu, specifically Main Menu did generate this bug warning but it looks working Distribution: Frugalware 0.6 (Terminus) Gnome Release: 2.18.0 2007-03-13 (Frugalware) BugBuddy Version: 2.18.0 System: Linux 2.6.20-fw4 #1 SMP PREEMPT Wed Mar 14 11:00:59 CET 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Mist Memory status: size: 47734784 vsize: 47734784 resident: 23478272 share: 15048704 rss: 23478272 rss_rlim: 4294967295 CPU usage: start_time: 1174983167 rtime: 1275 utime: 1154 stime: 121 cutime:0 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' (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 -1226840384 (LWP 2647)] (no debugging symbols found) 0xb7ef5410 in __kernel_vsyscall ()
+ Trace 122550
Thread 1 (Thread -1226840384 (LWP 2647))
----------- .xsession-errors (34 sec old) --------------------- Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x44 non valido per 0x1600007 (Configura ). Launched ok, pid = 3311 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x1600350 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x1600350 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 18 Minor opcode: 0 Resource id: 0x1600350 ICE default IO error handler doing an exit(), pid = 3308, errno = 11 --------------------------------------------------
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 422966 ***