GNOME Bugzilla – Bug 503250
crash in Panel: тупили в экран
Last modified: 2008-08-16 10:52:35 UTC
Version: 2.20.1 What were you doing when the application crashed? тупили в экран Distribution: Unknown Gnome Release: 2.20.1 2007-11-24 (FreeBSD GNOME Project) BugBuddy Version: 2.20.1 System: FreeBSD 6.2-STABLE FreeBSD 6.2-STABLE #8: Tue Nov 6 16:30:09 MSK 2007 vugluscr@splus.sovintel.ru:/usr/src/sys/i386/compile/SPLUS i386 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 44956 vsize: 44956 resident: 19596 share: 43940143 rss: 19596 rss_rlim: 4899 CPU usage: start_time: 1197461549032655 rtime: 0 utime: 48 stime: 3078528 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 128 Backtrace was generated from '/usr/local/bin/gnome-panel' (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New LWP 100180] [Switching to LWP 100180] 0x291b34d9 in wait4 () from /lib/libc.so.6
+ Trace 181655
Thread 1 (LWP 100180)
----------- .xsession-errors --------------------- Throttle level is 0 /usr/local/share/themes/Clearlooks/gtk-2.0/gtkrc:170: Invalid symbolic color 'tooltip_bg_color' /usr/local/share/themes/Clearlooks/gtk-2.0/gtkrc:170: error: invalid identifier `tooltip_bg_color', expected valid identifier /usr/local/share/themes/Clearlooks/gtk-2.0/gtkrc:170: Invalid symbolic color 'tooltip_bg_color' /usr/local/share/themes/Clearlooks/gtk-2.0/gtkrc:170: error: invalid identifier `tooltip_bg_color', expected valid identifier /usr/local/share/themes/Clearlooks/gtk-2.0/gtkrc:170: Invalid symbolic color 'tooltip_bg_color' /usr/local/share/themes/Clearlooks/gtk-2.0/gtkrc:170: error: invalid identifier `tooltip_bg_color', expected valid identifier (gnome-panel:2361): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (gnome-panel:2361): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (gnome-panel:2361): GLib-CRITICAL **: g_hash_table_remove: assertion `hash_table != NULL' failed warning: Unable to get location for thread creation breakpoint: generic error --------------------------------------------------
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 518086 ***