GNOME Bugzilla – Bug 492869
crash in Deskbar: typing "terminal" into t...
Last modified: 2007-11-03 00:36:16 UTC
What were you doing when the application crashed? typing "terminal" into the search box and pressing the down arrow to make a selection 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 23:05:12 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome 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 (123 sec old) --------------------- alarm-notify.c:393 (cal_opened_cb) file:///home/hien/.evolution/tasks/local/system - Calendar Status 0 alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80e2100: Received at thread b2dbfb90 alarm-queue.c:2003 (alarm_queue_add_async) - 0x80e0a80 alarm-queue.c:581 (load_alarms_for_today) - From Fri Nov 2 18:50:59 2007 to Fri Nov 2 18:50:59 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80e2100: 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) - 0x80e39a8: Received PID TTY TIME CMD (gnome-panel:5406): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -15 and height 24 -------------------------------------------------- Traceback (most recent call last):
+ Trace 174730
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 ***