GNOME Bugzilla – Bug 442959
crash in Panel: opening kmail, while 2 s...
Last modified: 2007-06-02 12:00:21 UTC
Version: 2.18.0 What were you doing when the application crashed? opening kmail, while 2 su gnome consoles opened in gaim and wifi conection and an xterm open in ping Distribution: Unknown Gnome Release: 2.18.0 2007-03-19 (Archlinux) BugBuddy Version: 2.18.0 System: Linux 2.6.20.4 #3 SMP Thu Apr 12 17:36:47 CLT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Enabled GTK+ Theme: Glider Icon Theme: Crux Memory status: size: 33112064 vsize: 33112064 resident: 22437888 share: 13283328 rss: 22437888 rss_rlim: 4294967295 CPU usage: start_time: 1180715451 rtime: 366 utime: 337 stime: 29 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/opt/gnome/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 -1225115968 (LWP 2786)] (no debugging symbols found) 0xb7fcf822 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 137286
Thread 1 (Thread -1225115968 (LWP 2786))
----------- .xsession-errors --------------------- Major opcode: 20 Minor opcode: 0 Resource id: 0x3600147 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 18 Minor opcode: 0 Resource id: 0x3600147 konsole: WARNING: Unable to use /opt/kde/share/apps/konsole/mc.desktop konsole: WARNING: Unable to use /opt/kde/share/apps/konsole/sumc.desktop GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized ** (bug-buddy:3012): WARNING **: Failed to initialize inotify: Función no implementada --------------------------------------------------
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 413921 ***