GNOME Bugzilla – Bug 530260
crash in Deskbar: actualizar el sistema
Last modified: 2008-04-28 11:02:05 UTC
What were you doing when the application crashed? actualizar el sistema 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 (300 sec old) ---------------------
+ Trace 196283
file = open(os.path.join(MANAGER_ROOT, name), "w")
** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) /usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet warnings.warn("apt API not stable yet", FutureWarning) /usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet warnings.warn("apt API not stable yet", FutureWarning) -------------------------------------------------- Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/deskbar/gtkexcepthook.py", line 67, in run run_old(*args, **kwargs) File "threading.py", line 440, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib/python2.5/site-packages/deskbar/core/ThreadPool.py", line 67, in _worker function(*args, **kwargs) File "/usr/lib/deskbar-applet/modules-2.20-compatible/history.py", line 52, in query if text.startswith(query): AttributeError: 'NoneType' object has no attribute 'startswith'
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 475351 ***