GNOME Bugzilla – Bug 488287
crash in Deskbar: Just typed something in....
Last modified: 2007-10-19 15:12:35 UTC
What were you doing when the application crashed? Just typed something in. I think our network just died, though... 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: 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 (83 sec old) --------------------- Checking for Xgl: not present. Detected PCI ID for VGA: 00:02.0 0300: 8086:2772 (rev 02) (prog-if 00 [VGA]) Checking for texture_from_pixmap: not present. Trying again with indirect rendering: Checking for texture_from_pixmap: present. Checking for non power of two support: present. Checking for Composite extension: present. Comparing resolution (1280x1024) to maximum 3D texture size (2048): Passed. Checking for nVidia: not present. Checking for FBConfig: present. Checking for Xgl: not present. Starting gtk-window-decorator /usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format -------------------------------------------------- Traceback (most recent call last):
+ Trace 171424
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 ***