After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 493199 - crash in Deskbar: I hit the hotkey, typed ...
crash in Deskbar: I hit the hotkey, typed ...
Status: RESOLVED DUPLICATE of bug 475351
Product: deskbar-applet
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Deskbar Applet Maintainer(s)
Deskbar Applet Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-11-03 22:42 UTC by mrelephant
Modified: 2007-11-04 10:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description mrelephant 2007-11-03 22:42:08 UTC
What were you doing when the application crashed?
I hit the hotkey, typed "tilda" and enter and then this window popped up.  Tilda still started, though.  It was all in quick sucession; I did not wait for anything to register before hitting enter.

I have noticed that there is a delay between typing and when you can hit enter to execute the command you want.


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 (129 sec old) ---------------------
alarm-notify.c:393 (cal_opened_cb) file:///home/grant/.evolution/tasks/local/system - Calendar Status 0
alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task
alarm-notify.c:349 (alarm_msg_received) - 0x80e1cc8:  PID TTY          TIME CMD
ERROR: decompression failed
Debug: [11/3/2007 5:31:04 PM] (Loading audio profiles) - /usr/share/banshee/audio-profiles
Debug: [11/3/2007 5:31:04 PM] (Default player engine) - GStreamer 0.10
Debug: [11/3/2007 5:31:04 PM] (Audio CD Core Initialized) - 
Warning: [11/3/2007 5:31:05 PM] (Power Management Call Failed) - Cannot find GNOME Power Manager: Name org.gnome.PowerManager has no owner
Debug: [11/3/2007 5:31:05 PM] (Enabled multimedia keys support) - Using org.gnome.SettingsDaemon
Window manager warning: last_user_time (136153008) is greater than comparison timestamp (128556692).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_
Window manager warning: 0xc00003 (Bottom Exp) appears to be one of the offending windows with a timestamp of 136153008.  Working around...
Window manager warning: last_user_time (136313856) is greater than comparison timestamp (128565532).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_
Window manager warning: 0xc00003 (Bottom Exp) appears to be one of the offending windows with a timestamp of 136313856.  Working around...
Window manager warning: last_user_time (134780176) is greater than comparison timestamp (128568256).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_
Window manager warning: 0xc00003 (Bottom Exp) appears to be one of the offending windows with a timestamp of 134780176.  Working around...
--------------------------------------------------
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'

Comment 1 Sebastian Pölsterl 2007-11-04 10:52:32 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 475351 ***