GNOME Bugzilla – Bug 491125
crash in Deskbar: Well, I hit F12, did a s...
Last modified: 2007-10-28 21:50:41 UTC
What were you doing when the application crashed? Well, I hit F12, did a search and this Bug-Buddy popped up. Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-rt #1 SMP PREEMPT RT Mon Oct 15 01:05:51 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: UbuntuStudio 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 (1204 sec old) --------------------- Checking for Xgl: not present. Starting gtk-window-decorator ** Message: Entfernter Desktop-Server wird nicht gestartet /usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format (gnome-panel:32755): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -11 and height 24 ** (nm-applet:409): WARNING **: <WARN> nma_dbus_device_properties_cb(): dbus returned an error. (org.freedesktop.NetworkManager.DeviceNotFound) The requested network device does not exist. FG: isPreferred(application/zip,[object Object]) FG: _shouldIntercept(application/zip) (nautilus:32756): libgnomevfs-WARNING **: gnome-vfs-monitor.c: A monitor handle was destroyed before it was added to the method hash table. This is a bug in the application and can cause crashes. It i -------------------------------------------------- Traceback (most recent call last):
+ Trace 173473
self._on_hit_added(query, container, qstring, qmax)
match = BeagleLiveMatch(result, category=cat_type, priority=self.get_priority())
display_name=basename(unescaped_uri)
mime = gnomevfs.get_mime_type(uri)
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 474131 ***