Hi, On Mon, 2005-09-19 at 22:14 +0100, Darren Davison wrote: > Hi guys, congrats on the 0.1.0 release!
Thanks! > Now, I'm not yet running a 2.6.13 kernel, so have the wrong inotify version, > but I'm not sure that's at fault here. My understanding is that inotify won't > affect the indexer much when it's starting from scratch. I could be very > wrong there, hence my post here and not bugzilla. I don't think that'd affect this. > Unhandled Exception: System.ArgumentNullException: null key > Parameter name: key > in [0x000c7] System.Collections.Hashtable:Find (System.Object key) > in [0x00002] (at > /tmp/portage/mono-1.1.9/work/mono-1.1.9/mcs/class/corlib/System.Collections/Hashtable.cs:449) > System.Collections.Hashtable:Contains (System.Object key) > in <0x003c9> Beagle.Util.Scheduler:Worker () > in (wrapper delegate-invoke) System.MulticastDelegate:invoke_void () > INFO: Kopete log backend worker thread done in 1.23s > INFO: Gaim log backend worker thread done in 1.91s Someone else was seeing this too. The most helpful thing would be if you could track this down to a specific backend, by using --allow-backend as an argument to beagled. I'd suggest blowing away ~/.beagle each time so that you recreate a controlled environment each time. Thanks, Joe _______________________________________________ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers