GNOME Bugzilla – Bug 491898
crash in Deskbar: Crashes after deinstalla...
Last modified: 2007-10-31 01:03:24 UTC
What were you doing when the application crashed? Crashes after deinstallation if tracker. Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: SmoothGNOME-Green Icon Theme: Lush 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 (35 sec old) --------------------- alarm-notify.c:349 (alarm_msg_received) - 0x81096d0: Received at thread b55b7b90 alarm-queue.c:2003 (alarm_queue_add_async) - 0x80f9e40 alarm-queue.c:581 (load_alarms_for_today) - From Tue Oct 30 00:00:00 2007 to Tue Oct 30 00:00:00 2007 alarm-queue.c:518 (load_alarms) alarm-notify.c:337 (alarm_msgport_replied) - 0x80fc8b8: Replied to GUI thread alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x81096d0: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0x80f99c0: Received at thread b55b7b90 alarm-queue.c:2003 (alarm_queue_add_asyncNautilus-Share-Message: returned from spawn: SUCCESS: Nautilus-Share-Message: exit code 255 Nautilus-Share-Message: ------------------------------------------ Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: usershares are currently disabled -------------------------------------------------- Traceback (most recent call last):
+ Trace 174039
self._history.load()
saved_history = cPickle.load(file(HISTORY_FILE))
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 474179 ***