GNOME Bugzilla – Bug 520604
crash in Panel: Typing email in my text ...
Last modified: 2008-03-05 22:04:10 UTC
Version: 2.20.1 What were you doing when the application crashed? Typing email in my text window using mutt. Distribution: Solaris Express Community Edition snv_84 X86 Gnome Release: 2.20.2 2008-02-13 (Sun Microsystems, Inc.) BugBuddy Version: 2.20.1 X Vendor: Sun Microsystems, Inc. X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: nimbus Icon Theme: nimbus Memory status: size: 141320192 vsize: 141320192 resident: 22097920 share: 0 rss: 22097920 rss_rlim: 0 CPU usage: start_time: 0 rtime: 307 utime: 2571562 stime: 504576 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/bin/gnome-panel' (no debugging symbols found) sol-thread active. Retry #1: Retry #2: Retry #3: Retry #4: [New LWP 1 ] [New Thread 1 (LWP 1)]
+ Trace 191426
Thread 1 (LWP 1)
Thread 1 (LWP 1 ): #-1 0xfef056d5 in __waitid () from /lib/libc.so.1 No symbol table info available. #-1 0xfef056d5 in __waitid () from /lib/libc.so.1 ----------- .xsession-errors (72761116 sec old) --------------------- kbuildsycoca: WARNING: '/usr/share/applications/ooo645writer.desktop' specifies undefined mimetype/servicetype 'text/richtext' kwin: Fatal IO error: client killed kded: Fatal IO error: client killed KWrited - Listening on Device /dev/pts/1 knotify: Fatal IO error: client killed kdeinit: Fatal IO error: client killed kdeinit: sending SIGHUP to children. *** kdesktop got signal 1 (Exiting) kicker: sighandler called kicker: Fatal IO error: client killed konsole: Fatal IO error: client killed klauncher: Exiting on signal 1 klauncher: Fatal IO error: client killed konsole: Fatal IO error: client killed kdesktop: Fatal IO error: client killed --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 504600 ***