GNOME Bugzilla – Bug 491615
crash in Deskbar: I have removed tracker t...
Last modified: 2007-10-30 09:41:37 UTC
What were you doing when the application crashed? I have removed tracker to switch to beagle 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: 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 (270 sec old) --------------------- Can not use GRE from /usr/lib/xulrunner because it's missing components/libwidget_gtk2.so. checking /usr/lib/firefox for GRE GRE found at /usr/lib/firefox. Browser check failed with: XPCOM error -2147467259, InvocationTargetException Can't create browser. Will try to set LD_LIBRARY_PATH and hope Azureus has better luck. setting LD_LIBRARY_PATH to: /usr/lib/firefox setting MOZILLA_FIVE_HOME to: /usr/lib/firefox Loading Azureus: java -Xmx128m -cp "./Azureus2.jar:./swt.jar" -Djava.library.path="/home/geo/DOWNLOADS/Programs/azureus" -Dazureus.install.path="/home/geo/DOWNLOADS/Programs/azureus" -Dazureus.script="/home/geo/DOWNLO PID TTY TIME CMD should load blocklist from: http://www.bluetack.co.uk/config/spconfig.txt (SWT:6094): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -5 and height 19 Retrieving data from: http://www.bluetack.co.uk/config/splist.zip [INFO] HttpMethodBase - Stream closed -------------------------------------------------- Traceback (most recent call last):
+ Trace 173835
self._history.load()
saved_history = cPickle.load(file(HISTORY_FILE))
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 474179 ***