GNOME Bugzilla – Bug 486068
crash in Deskbar:
Last modified: 2007-10-13 16:17:11 UTC
What were you doing when the application crashed? Distribution: Red Hat Linux release 3.0 Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-386 #1 Wed Oct 10 05:26:36 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70000000 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 (61 sec old) --------------------- alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:349 (alarm_msg_received) - 0x80d1840: Received at thread b3661b90 alarm-queue.c:2003 (alarm_queue_add_async) - 0x80c71c0 alarm-notify.c:337 (alarm_msgport_replied) - 0x80cebb0: Replied to GUI thread alarm-queue.c:581 (load_alarms_for_today) - From Fri Oct 12 09:19:50 2007 to Fri Oct 12 09:19:50 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notif/usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format Loading socket FrontEnd module ... Starting SCIM as daemon ... GTK Panel of SCIM 1.4.7 PID TTY TIME CMD -------------------------------------------------- Traceback (most recent call last):
+ Trace 169765
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):
Thank you for reporting this bug. It looks like this bug is the same as bug 472134
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 ***