GNOME Bugzilla – Bug 484252
crash in Deskbar:
Last modified: 2007-10-07 08:59:19 UTC
What were you doing when the application crashed? Distribution: openSUSE 10.3 (X86-64) Gnome Release: 2.20.0 2007-09-22 (SUSE) BugBuddy Version: 2.20.0 System: Linux 2.6.22.5-31-default #1 SMP 2007/09/21 22:29:00 UTC x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Enabled GTK+ Theme: Gilouche Icon Theme: Industrial 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 --------------------- (gnome-panel:26341): libgnomevfs-CRITICAL **: gnome_vfs_get_uri_from_local_path: assertion `g_path_is_absolute (local_full_path)' failed (gnome-panel:26341): libgnomevfs-CRITICAL **: gnome_vfs_monitor_add: assertion `text_uri != NULL' failed (gnome-panel:26341): libgnomevfs-CRITICAL **: gnome_vfs_get_uri_from_local_path: assertion `g_path_is_absolute (local_full_path)' failed (gnome-panel:26341): libgnomevfs-CRITICAL **: gnome_vfs_monitor_add: assertion `text_uri != NULL' failed (gnome-panel:26341): libgnomevfs-CRITICAL **: gnome_vfs_get_uri_from_local_path: assertion `g_path_is_absolute (local_full_path)' failed (gnome-panel:26341): libgnomevfs-CRITICAL **: gnome_vfs_monitor_add: assertion `text_uri != NULL' failed ** (gnome-cups-icon:26363): WARNING **: IPP request failed with status 1030 ** (gnome-cups-icon:26363): WARNING **: IPP request failed with status 1030 -------------------------------------------------- Traceback (most recent call last):
+ Trace 168414
from deskbar.ui.DeskbarApplet import DeskbarApplet
from deskbar.ui.CuemiacWindowController import CuemiacWindowController
from deskbar.ui.preferences.DeskbarPreferences import DeskbarPreferences
from deskbar.core.updater.NewStuffUpdater import NewStuffUpdater
import dbus
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 475630 ***