GNOME Bugzilla – Bug 486310
crash in Deskbar: Opened deskbar with Alt+...
Last modified: 2007-10-13 16:21:42 UTC
What were you doing when the application crashed? Opened deskbar with Alt+F3 and started writing the name of application. After few letters deskbar crashed. This crash is happening in 50% of tries to write here something. Distribution: Debian lenny/sid Gnome Release: 2.20.0 2007-09-21 (Debian) BugBuddy Version: 2.20.0 System: Linux 2.6.22.6 #5 SMP Sun Oct 7 11:40:30 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors (1704 sec old) --------------------- /usr/share/themes/Clearlooks/gtk-2.0/gtkrc:158: error: invalid identifier `tooltip_bg_color', expected valid identifier /usr/share/themes/Clearlooks/gtk-2.0/gtkrc:158: Invalid symbolic color 'tooltip_bg_color' /usr/share/themes/Clearlooks/gtk-2.0/gtkrc:158: error: invalid identifier `tooltip_bg_color', expected valid identifier ** (gnome-cups-icon:4397): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:4397): WARNING **: IPP request failed with status 1280 seahorse nautilus module initialized Initializing gnome-mount extension /usr/share/themes/Clearlooks/gtk-2.0/gtkrc:158: Invalid symbolic color 'tooltip_bg_color' /usr/share/themes/Clearlooks/gtk-2.0/gtkrc:158: error: invalid identifier `tooltip_bg_color', expected valid identifier ** Message: drive = 0 ** Message: volume = 0 ** (gnome-cups-icon:4397): WARNING **: Could not start the printer tray icon, because the CUPS server could not be contacted. -------------------------------------------------- Traceback (most recent call last):
+ Trace 169951
cell.set_property ("has-more-actions", len(match.get_actions()) > 1)
Thank you for reporting this bug. It looks like this is the same issue as bug 471672.
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 471672 ***