GNOME Bugzilla – Bug 491938
crash in Deskbar:
Last modified: 2007-10-31 08:23:08 UTC
What were you doing when the application crashed? 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 (137 sec old) --------------------- Checking if there is an instance already running... No other instances are running. Loading temp files from /home/bert/.aMule/Temp. Loading PartFile 1 of 14 Loading PartFile 2 of 14 Loading PartFile 3 of 14 Loading PartFile 4 of 14 Loading PartFile 5 of 14 Loading PartFile 6 of 14 Loading PartFile 7 of 14 Loading PartFile 8 of 14 All PartFiles Loaded. ListenSocket: Ok. External connections disabled in config file *** Server UDP socket (TCP+3) at 0.0.0.0:4665 *** TCP socket (TCP) listening on 0.0.0.0:4662 *** Client UDP socket (extended eMule) at 0.0.0.0:4672 Adding file /home/bert/.aMule/Temp/004.part.met to shares Adding file /home/bert/.aMule/Temp/009.part.met to shares Adding file /home/bert/.aMule/Temp/014.part.met to shares Adding file /home/bert/.aMule/Temp/019.part.met to shares Adding file /home/bert/.aMule/Temp/024.part.met to -------------------------------------------------- Traceback (most recent call last):
+ Trace 174071
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
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 ***