GNOME Bugzilla – Bug 454766
crash in Deskbar: typing into the search b...
Last modified: 2007-07-09 16:46:18 UTC
What were you doing when the application crashed? typing into the search box. Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21-2-amd64 #1 SMP Mon Jun 25 22:01:38 CEST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Mist 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 (8550 sec old) --------------------- (gnome-theme-manager:25057): Gtk-WARNING **: Unable to locate theme engine in module_path: "lighthouseblue", (gnome-panel:6283): Gtk-WARNING **: Unable to locate theme engine in module_path: "lighthouseblue", (gnome-theme-manager:25058): Gtk-WARNING **: Unable to locate theme engine in module_path: "lighthouseblue", (xchat:6474): Gtk-WARNING **: Unable to locate theme engine in module_path: "lighthouseblue", Window manager warning: Log level 16: Unable to locate theme engine in module_path: "lighthouseblue", (nautilus:6290): Gtk-WARNING **: Unable to locate theme engine in module_path: "lighthouseblue", sound-properties-Message: Error running pipeline 'gconfaudiosrc ! audioconvert ! audioresample ! gconfaudiosink profile=chat': Could not open resource for writing. [gstalsasrc.c(600): gst_alsasrc_open Recording open error on device 'default:1': Broken pipe] sound-properties-Message: Error running pipeline 'gconfaudiosrc ! audioconvert ! audioresample ! gconfaudiosink profile=chat': Could not open resource for writing. [gstalsasrc.c(600): gst_alsasrc_open Recording open error on device 'default:1': Broken pipe] -------------------------------------------------- TypeError: function takes exactly 0 arguments (1 given)
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 453902 ***