GNOME Bugzilla – Bug 533504
crash in Deskbar: Ich habe Beagle Live Suc...
Last modified: 2008-05-17 09:12:44 UTC
What were you doing when the application crashed? Ich habe Beagle Live Suche aktiviert und nach einem Begriff gesucht. Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.1 2008-05-07 (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: Human-Murrine 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 (8 sec old) --------------------- Writing MailMessage to file. Subject: Flawless RX Reductions Writing MailMessage to file. Subject: during sexual intercourse Writing MailMessage to file. Subject: RedBull fur Ihr bestes Stuck Done processing 10 items Writing MailMessage to file. Subject: Office 2007 Enterprise ready to download Writing MailMessage to file. Subject: 75% discount. Code #2883 Writing MailMessage to file. Subject: Man Lebt nur einmal - probiers aus ! Writing MailMessage to file. Subject: 80% discount. Code #6765 Writing MailMessage to file. Subject: Potenzprobleme - ab heute nicht mehr Writing MailMessage to file. Subject: 75% off for matyy Writing MailMessage to file. Subject: Writing MailMessage to file. Subject: 80% off for matyy Writing MailMessage to file. Subject: 75% off for matyy Writing MailMessage to file. Subject: Immediat software downloads Done processing 10 items -------------------------------------------------- Traceback (most recent call last):
+ Trace 197925
self._on_hit_added(query, container, qstring, qmax)
self.counter[qstring][hit.get_type()] += 1
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 ***