GNOME Bugzilla – Bug 492006
crash in Deskbar: I do not know
Last modified: 2007-10-31 11:11:54 UTC
What were you doing when the application crashed? I do not know Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (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: Mist 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 (10 sec old) ---------------------
+ Trace 174113
pageData = self._retrievePage(req)
resp = self.opener.open(req)
response = self._open(req, data)
'_open', req)
result = func(*args)
return self.do_open(httplib.HTTPSConnection, req)
raise URLError(err)
-------------------------------------------------- Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/deskbar/gtkexcepthook.py", line 67, in run run_old(*args, **kwargs) File "threading.py", line 440, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib/python2.5/site-packages/deskbar/core/ThreadPool.py", line 67, in _worker function(*args, **kwargs) File "/usr/lib/deskbar-applet/modules-2.20-compatible/yahoo.py", line 59, in query 'results': 15}), proxies=get_proxy()) File "urllib.py", line 82, in urlopen return opener.open(url) File "urllib.py", line 190, in open return getattr(self, name)(url) File "urllib.py", line 325, in open_http h.endheaders() File "httplib.py", line 856, in endheaders self._send_output() File "httplib.py", line 728, in _send_output self.send(msg) File "httplib.py", line 695, in send self.connect() File "httplib.py", line 663, in connect socket.SOCK_STREAM): IOError: [Errno socket error] (-2, 'Name or service not known')
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 ***