GNOME Bugzilla – Bug 491709
crash in Deskbar: when network connection fails
Last modified: 2007-10-31 01:45:05 UTC
What were you doing when the application crashed? I was typing a second keyword in the deskbar input zone while the tracker client + web clients were starting to display the results for the first key word 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 (14097 sec old) --------------------- Error: can't open /var/run/openct/status: Permission non accordée Error: can't open /var/run/openct/status: Permission non accordée Error: can't open /var/run/openct/status: Permission non accordée Error: can't open /var/run/openct/status: Permission non accordée Error: can't open /var/run/openct/status: Permission non accordée Error: can't open /var/run/openct/status: Permission non accordée Error: can't open /var/run/openct/status: Permission non accordée Error: can't open /var/run/openct/status: Permission non accordée Error: can't open /var/run/openct/status: Permission non accordée Error: can't open /var/run/openct/status: Permission non accordée Error: can't open /var/run/openct/status: Permission non accordée Error: can't open /var/run/openct/status: Permission non accordée Error: can't open /var/run/openct/status: Permission non accordée Error: can't open /var/run/openct/status: Permission non accordée ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 173902
run_old(*args, **kwargs)
self.__target(*self.__args, **self.__kwargs)
function(*args, **kwargs)
'results': 15}), proxies=get_proxy())
return opener.open(url)
return getattr(self, name)(url)
h.endheaders()
self._send_output()
self.send(msg)
self.connect()
raise socket.error, msg
'Le r\xc3\xa9seau n'est pas accessible.' means network is not available in french and indeed my wifi connection was very bad when the crash occurred.
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. And thanks for providing a translation! *** This bug has been marked as a duplicate of 472134 ***
Created attachment 98218 [details] [review] patch ThreadPool to catch nework related errors while calling handlers
#9828 is a patch against ThreadPool.py against the trunk to catch network related errors. I could not find how you fixed the bug in the trunk therefor I submit the patch even though you marked the issue resolved. I have a problem with autogen.sh so that I cannot really test the developer version but I suspect there are still bug lurking around when unplugging the network while using the deskbar and most strangely some of those bugs where not catched by the bug-buddy callback (maybe a segfault?). [update] I just found that installing libgconf2-dev solve the autogen.sh issue. I will try to reproduce my bugs with pdb on the trunk version some time tomorrow of the week to try and find whether those bugs are still around.
It seems the fix is in the respective handlers (desklicios/yahoo/other network related handlers) instead of ThreadPool.py. I can't comment on which approach is better, since I'm not a developer, just a triager. Thank you for your interest in and work to improve GNOME! It's always nice to have people contribute, and if you find more network related bugs in up to date versions, please tell us. :)