GNOME Bugzilla – Bug 484532
crash in Deskbar: I started it.
Last modified: 2007-10-08 11:10:45 UTC
What were you doing when the application crashed? I started it. Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-10-generic #1 SMP Wed Aug 22 08:11:52 GMT 2007 i686 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 (19 sec old) --------------------- [DEBUG]: Opening url 'file:///home/robin/Studier/DOMScripting'... Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2400082 specified for 0x2400e2a (). [DEBUG]: Saving 'JavaScriptImageGallery'... [DEBUG]: Matching Note title 'JavaScriptSyntax' at 1-17... [DEBUG]: Opening url 'file:///home/robin/Studier/'... [DEBUG]: Saving 'JavaScriptImageGallery'... ** (update-notifier:12996): WARNING **: no cdrom: sd_mmc closing Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3600003 (Export Fil) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. [DEBUG]: Opening note 'JavaScriptSyntax' on click... Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3800061 (OpenOffice) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. -------------------------------------------------- Traceback (most recent call last):
+ Trace 168630
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 ***