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 536609 - crash in Deskbar: Recherche dans Deskbar a...
crash in Deskbar: Recherche dans Deskbar a...
Status: RESOLVED DUPLICATE of bug 527023
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: 2008-06-04 14:01 UTC by isikra
Modified: 2008-06-05 10:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description isikra 2008-06-04 14:01:21 UTC 
What were you doing when the application crashed?
Recherche dans Deskbar applet


Distribution: Mandriva Linux release 2008.1 (Official) for i586
Gnome Release: 2.22.0 2008-03-26 (Mandriva)
BugBuddy Version: 2.22.0

System: Linux 2.6.24.5-desktop586-1mnb #1 SMP Tue May 27 12:31:39 EDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Ia Ora Blue
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

Traceback (most recent call last):

+ Trace 199560

  • File "/usr/lib/deskbar-applet/modules-2.20-compatible/beagle-live.py", line 361 in _on_snippet_received 
    self._on_hit_added(query, container, qstring, qmax)
  • File "/usr/lib/deskbar-applet/modules-2.20-compatible/beagle-live.py", line 393 in _on_hit_added 
    self.counter[qstring][hit.get_type()] += 1
KeyError: 'File' 






Comment 1


Gianluca Borello





          2008-06-05 10:04:33 UTC
        



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 527023 ***