GNOME Bugzilla – Bug 532352
crash in Deskbar: typing a search
Last modified: 2008-05-09 18:31:39 UTC
What were you doing when the application crashed? typing a search Distribution: Gentoo Base System release 2.0.0 Gnome Release: 2.22.1 2008-05-08 (Gentoo) BugBuddy Version: 2.22.0 System: Linux 2.6.25-gentoo-r2 #1 SMP Wed May 7 13:46:34 CEST 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Gion 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 (44 sec old) --------------------- Cannot index Thunderbird contacts because a System.ArgumentNullException was thrown: Argument cannot be null. Parameter name: path Could not read Banshee database file: Unable to open the database file unable to open database file Could not read Pidgin buddy list file: Could not find a part of the path "/home/djeedjee/.purple/blist.xml". Cannot index Thunderbird contacts because a System.ArgumentNullException was thrown: Argument cannot be null. Parameter name: path Could not read Banshee database file: Unable to open the database file unable to open database file Could not read Pidgin buddy list file: Could not find a part of the path "/home/djeedjee/.purple/blist.xml". Cannot index Thunderbird contacts because a System.ArgumentNullException was thrown: Argument cannot be null. Parameter name: path Could not read Banshee database file: Unable to open the database file unable to open database file Could not read Pidgin buddy list file: Could not find a part of the path "/home/djeedjee/.purple/blist.xml". -------------------------------------------------- Traceback (most recent call last):
+ Trace 197313
run_old(*args, **kwargs)
self.__target(*self.__args, **self.__kwargs)
function(*args, **kwargs)
self.beagle.send_request_async(self.beagle_query)
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 530057 ***