GNOME Bugzilla – Bug 488556
crash in Deskbar: searching a text string ...
Last modified: 2007-10-20 10:24:01 UTC
What were you doing when the application crashed? searching a text string "kaos", Deskbar crashed after searching a few results. 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-generic #1 SMP Sun Oct 14 21:45:15 GMT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Human 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 (352 sec old) --------------------- alarm-queue.c:581 (load_alarms_for_today) - From Sat Oct 20 12:02:39 2007 to Sat Oct 20 12:02:39 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x6ca280: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0 alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x6b3460: Rece ** (nm-applet:5988): WARNING **: <WARN> nma_dbus_device_properties_cb(): dbus returned an error. (org.freedesktop.NetworkManager.DeviceNotFound) The requested network device does not exist. lcms: Error #4096; Read from memory error. Got 0 bytes, block should be of 128 bytes lcms: Error #12288; Corrupted memory profile -------------------------------------------------- Traceback (most recent call last):
+ Trace 171647
run_old(*args, **kwargs)
self.__target(*self.__args, **self.__kwargs)
function(*args, **kwargs)
posts = self._delicious.get_posts_by_tag(tag)
stream = urllib.urlopen(url, proxies=deskbar.core.Utils.get_proxy())
return opener.open(url)
return getattr(self, name)(url)
h.endheaders()
self._send_output()
self.send(msg)
self.connect()
socket.SOCK_STREAM):
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 472134 ***