GNOME Bugzilla – Bug 557908
crash in Deskbar: estava pesquizando, apen...
Last modified: 2008-10-27 16:06:33 UTC
What were you doing when the application crashed? estava pesquizando, apenas digitei /opt/lampp/ e apareceu esta janela parabens pelo trabalho Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.1 2008-04-15 (Ubuntu) BugBuddy Version: 2.22.0 System: Linux 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Glider Icon Theme: gnome 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 (17689 sec old) --------------------- (gnome-panel:5743): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -26 and height 24 Starting gtk-window-decorator /usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format I/O warning : failed to load external entity "/home/taober/.compiz/session/default0" PID TTY TIME CMD 5723 ? 00:00:00 pulseaudio WARNING: modinfo for module fglrx failed: modinfo: could not find module fglrx WARNING: modinfo for module nvidia_new failed: modinfo: could not find module nvidia_new WARNING: modinfo for module nvidia failed: modinfo: could not find module nvidia WARNING: modinfo for module nvidia_legacy failed: modinfo: could not find module nvidia_legacy -------------------------------------------------- Traceback (most recent call last):
+ Trace 208699
run_old(*args, **kwargs)
self.__target(*self.__args, **self.__kwargs)
function(*args, **kwargs)
result += self._query_filefolder(query, False)
completions, prefix, relative = filesystem_possible_completions(query, is_file)
for f in map(lambda x: join(path, x), os.listdir(path))
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 494922 ***