GNOME Bugzilla – Bug 514902
crash in Panel: Running pkg-get from bla...
Last modified: 2008-02-07 16:00:40 UTC
Version: 2.20.1 What were you doing when the application crashed? Running pkg-get from blastware Distribution: Solaris Express Community Edition snv_82 X86 Gnome Release: 2.20.2 2008-01-15 (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: 17985536 share: 393216 rss: 17985536 rss_rlim: 0 CPU usage: start_time: 0 rtime: 117 utime: 1058005 stime: 116402 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 188362
Thread 1 (LWP 1)
Thread 1 (LWP 1 ): #-1 0xfef13477 in _waitid () from /usr/lib/libc.so.1 No symbol table info available. #-1 0xfef13477 in _waitid () from /usr/lib/libc.so.1 ----------- .xsession-errors (7951760 sec old) --------------------- Warning: No symbols defined for <I7F> (keycode 255) ** Message: Querying Xkb extension ** Message: Xkb extension found The application 'xfce4-session' lost its connection to the display :0.0; most likely the X server was shut down or you killed/destroyed the application. The application 'xfce-mcs-manager' lost its connection to the display :0.0; most likely the X server was shut down or you killed/destroyed the application. alsa: Mixer attach default error: No such device The application 'gnome-screensaver' lost its connection to the display :0.0; most likely the X server was shut down or you killed/destroyed the application. kdeinit: Fatal IO error: client killed kdeinit: sending SIGHUP to children. --------------------------------------------------
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 ***