GNOME Bugzilla – Bug 492009
crash in Deskbar: Just logged in
Last modified: 2007-10-31 11:12:05 UTC
What were you doing when the application crashed? Just logged in 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 (16 sec old) --------------------- Tracker version 0.6.3 Copyright (c) 2005-2007 by Jamie McCracken (jamiemcc@gnome.org) This program is free software and comes without any warranty. It is licensed under version 2 or later of the General Public License which can be viewed at http://www.gnu.org/licenses/gpl.txt Initialising tracker... Could not set idle IO priority...attempting best effort 7 priority Throttle level is 0 ** Message: Starter ikke tjener for eksternt skrivebord Error: Screen isn't composited. Please run compiz (-fusion) or another compositing manager. Advarsel fra vindushåndterer: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1c00027 (awn_elemen) Advarsel fra vindushåndterer: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Initializing gnome-mount extension -------------------------------------------------- Traceback (most recent call last):
+ Trace 174116
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()
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 ***