Re: Problems with current CVS version
On Wed, 2005-03-23 at 22:09 +0100, Daniel KÃb wrote: > I'm using Debian unstable with mono 1.0.5. The "lock obtain timed out" problem is caused by a bug in mono 1.0.5. Upgrade to 1.0.6. Or just take the plunge and upgrade to 1.1.4... you'll be glad you did. -J ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Problems with current CVS version
Hi! I have some problems using the current CVS version of beagle (0.7 works fine). I compiled and installed beagle without problems. But when I run "beagled" I get the following error message for every backened in my log file and best doesn't report any results: 05-03-23 21.56.35.12 17472 Beagle ERROR: Caught exception while instantiating Files backend 05-03-23 21.56.35.13 17472 Beagle ERROR: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.IOException: Lock obtain timed out: Lock@/home/daniel/.beagle/FileSystemIndex/Locks/lucene-91ae8670c91c3ad975c8bbc615dc8a62-write.lock in [0x0003b] (at /home/daniel/gnome-dev/beagle/beagled/Lucene.Net/Store/Lock.cs:75) Lucene.Net.Store.Lock:Obtain (long) [...] I'm using Debian unstable with mono 1.0.5. I can't see any problems with permissions on the file system or such. Do I need to upgrade some libraries? Thanks in advance for any help, Daniel ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
trigger the indexing of a specific directory without inotify
Hi, I'm testing beagle-0.0.8 in a non-inotify 0.20-enabled FC3 kernel, And I would like to know if it is possible to trigger the indexing of a specific directory in any way. As I don't have 0.20-inotify, neither "ls" nor "touch" methods work for me, Thanks in advance, Bests, Albert. ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.0.8
On Wednesday 23 March 2005 19:52, Jon Trowbridge wrote: > I'm pleased to announce the release of Beagle 0.0.8. Is it possible to provide distribution-agnostic binaries, something like what .jar is for Java? I'm asking because I tried an installation on Suse 9.1, as described in the Wiki: http://beaglewiki.org/index.php/SuseInstall The "rug sub mdes" command just says "Subscribed to channel 'Mono Desktop Extensions Snapshots'" and then nothing seems to happen (as you can probably see, I have never used "rug" before). When I call "rug pa mdes" it just says "No packages found". Regards Daniel -- http://www.danielnaber.de ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.0.8
On Wed, 2005-03-23 at 22:00 +, James Ogley wrote: > > It is not. > > Packages are available > > Presumably I'll need to rebuild beagle too? No, not for the kernels to which I linked. For the newer kernels, yes. But the kernels in old/ are for the Beagle we shipped in 9.3 Robert Love ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.0.8
Hi, On Wed, 2005-03-23 at 22:00 +, James Ogley wrote: > > It is not. > > Packages are available > > Presumably I'll need to rebuild beagle too? Nope, shouldn't need to. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.0.8
> It is not. > Packages are available Presumably I'll need to rebuild beagle too? -- James Ogley [EMAIL PROTECTED] GNOME for SuSE: http://usr-local-bin.org/rpms ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
beagle inotify ABI change
Everyone, Starting right now, with current CVS and henceforth all Beagle releases after 0.0.8, Beagle is updated to the inotify 0.21 patch, which introduces an ABI and API change. Hear ye, hear ye: *** Beagle 0.0.8 requires inotify 0.20 *** Beagle CVS (0.0.9 and on) requires inotify 0.21 Kernels for SUSE 9.3 are available: http://primates.ximian.com/~rml/kernel-rml/suse-93-i586/ Kernels for SUSE 9.1, SUSE 9.2, SLES9, and NLD9 are available: http://primates.ximian.com/~rml/kernel-rml/suse-92-i586/ Kernel patches: http://www.kernel.org/pub/linux/kernel/people/rml/inotify/v2.6/0.21/ If you use CVS, please make sure you use these updated packages/patches. If you use the 0.0.8 release or what is included in SUSE 9.3, please use the older kernels or 0.20 patch. Thanks. Robert Love ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.0.8
On Wed, 2005-03-23 at 20:15 +, James Ogley wrote: > Is SuSE 9.3's kernel inotify 0.20-enabled as far as you know? It is not. Packages are available http://primates.ximian.com/~rml/kernel-rml/suse-93-i586/old/ Best, Robert Love ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.0.8
> 0.0.8 is essentially identical to the version of Beagle that will be included > in SuSE 9.3. > For the best possible Beagle experience, you should also have: > * An inotify 0.20-enabled kernel Is SuSE 9.3's kernel inotify 0.20-enabled as far as you know? -- James Ogley [EMAIL PROTECTED] GNOME for SuSE: http://usr-local-bin.org/rpms ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Beagle 0.0.8
I'm pleased to announce the release of Beagle 0.0.8. Beagle 0.0.8 represents a huge step forward in stability, and contains fixes for a multitude of bugs and memory leaks. This is the first version of Beagle that is really suitable for everyday use. It also includes a brand new web services API to the Beagle daemon, developed by KN Vijay. 0.0.8 is essentially identical to the version of Beagle that will be included in SuSE 9.3. OUR MANY URLS - To download the 0.0.8 tarball, visit the Beagle web page at http://www.gnome.org/projects/beagle There is lots of useful information about compiling and using Beagle on the wiki: http://www.beaglewiki.org If you are running SuSE or the Novell Linux Desktop, we have an open carpet server with snapshots and packages for all of the dependencies: http://segfault.cam.novell.com Joe Gasiorek writes a regular Beagle newsletter. You can read it at: http://www.beaglewiki.org/index.php/Newsletters Nat Friedman made some cool movies that demonstrate Beagle in action: http://nat.org/demos The latest gossip is available at: http://www.planetbeagle.org We still talk about Beagle on the dashboard-hackers mailing list: http://mail.gnome.org/mailman/listinfo/dashboard-hackers Jack Kerouac didn't want anything to slow down his writing, so he typed the first draft of "On The Road" onto a 120-foot scroll. That original manuscript is now on a multi-year, multi-city tour: http://www.emptymirrorbooks.com/kerouac-on-the-road-scroll.html WHAT IS BEAGLE? --- Beagle is a tool for indexing and searching your data. It is in an early stage of development and should be considered experimental. Beagle is improving rapidly on many fronts, and should work well enough for everyday use. The Beagle daemon transparently monitors your data and updates the index to reflect any changes. On an inotify-enabled system, these updates happen more-or-less in real time. So for example, * Files are immediately indexed when they are created, are re-indexed when they are modified, and are dropped from the index upon deletion. * E-mails are indexed upon arrival. * IM conversations are indexed as you chat, a line at a time. Beagle uses the Lucene indexing system from the prodigious Doug Cutting. Best is a graphical tool for searching the index that the daemon creates. Best doesn't query the index directly; it passes the search terms to the daemon and the daemon sends any matches back to Best. Best then renders the results and allows you to perform useful actions on the matching objects. Indexing your data requires a fair amount of computing power, but the Beagle daemon tries to be as unobtrusive as possible. It contains a scheduler that works to prioritize tasks and control CPU usage, based on whether or not you are actively using your workstation. DEPENDENCY HECK --- Beagle has many dependencies, and thus can be difficult to compile. It requires: * The full Mono stack, including Gtk#. (We all use 1.1.4, and you probably should too, but 1.0.6 will also work. 1.0.5 and earlier will NOT work.) * D-BUS 0.23.4 * Evolution-sharp 0.6 * Gecko-sharp * Gsf-sharp * Gmime 2.1.13 For the best possible Beagle experience, you should also have: * An inotify 0.20-enabled kernel CHANGES SINCE 0.0.7 --- Daemon/Infrastructure: * Added a new web services interface to beagled (KN Vijay) * Better support for Move events in the Inotify bindings (Robert Love) * Deal with unmatched Move events (Robert) * Properly catch exceptions if we try to watch a directory that has just been deleted (Robert) * Handle filenames containing funny characters (Daniel Drake) * Allow beagled to be started even if X isn't running (Daniel) * Better handling of GConf exceptions (Daniel) * Check for null URIs in HitRegulator.Subtract() (Veerapuram Varadhan) * Lots of snippet fixes and improvements (Fredrik Hedberg) * Fixed numerous shutdown-related deadlocks (Jon Trowbridge) * Uri serialization fixes (Jon, Daniel) * Throw the right exception if we can't set EAs on a file (Jon) * Removed inotify dependency from the code that processes gaim's buddy list (Jon) * Use Mono.Posix functions to create Lucene's lockfiles (Jon) * Construct our lucene queries in a more reasonable way (Jon) * Fixed deadlocks and races in our D-BUS work-arounds (Jon) * Better disposal/clean-up of unregistered D-BUS objects (Jon) * Disable broken indexing of nautilus emblems and notes (Jon) * Don't cache the ignore state of files -- it uses too much memory (Jon) * When possible, re-use GLib.IdleHandlers to avoid allocations (Jon) * If a hit is filtered out of the query results because HitIsValid returns false, schedule it for removal from the index (Jon) * Work around dropped FlushComplete signals by polling the flush status in a timeout (Jon) * Added a new property type: properties that are stored but not searched by standard queries (Jon) * Don't allow beagled to run as root (Daniel)
Re: finding nothing...
I found this in the current-Indexhelper log: 05-03-22 10.44.33.36 03190 IndexH DEBUG: Couldn't acquire d-bus service 'com.novell.BeagleIndexHelper' Here's the entire output from current-Beagle before the error. 05-03-22 10.44.33.01 03187 Beagle INFO: Starting Beagle Daemon (version 0.0.7) 05-03-22 10.44.33.02 03187 Beagle DEBUG: Command Line: /usr/local/lib/beagle/BeagleDaemon.exe --debug --fg 05-03-22 10.44.33.05 03187 Beagle DEBUG: Initializing D-BUS 05-03-22 10.44.33.14 03187 Beagle DEBUG: Acquiring com.novell.Beagle D-BUS service 05-03-22 10.44.33.15 03187 Beagle DEBUG: Found index helper at /usr/local/lib/beagle/beagled-index-helper 05-03-22 10.44.33.16 03187 Beagle DEBUG: Launching helper process! 05-03-22 10.44.33.44 03187 Beagle DEBUG: Connecting to com.novell.BeagleIndexHelper 05-03-22 10.44.33.90 03187 Beagle DEBUG: Initializing RemoteControl 05-03-22 10.44.33.91 03187 Beagle DEBUG: D-BUS registered obj=Beagle.Daemon.RemoteControlImpl path=/com/novell/Beagle/RemoteContr$05-03-22 10.44.33.94 03187 Beagle DEBUG: D-BUS registered obj=Beagle.Daemon.FactoryImpl path=/com/novell/Beagle/Factory owner=(no$05-03-22 10.44.33.94 03187 Beagle DEBUG: Starting QueryDriver 05-03-22 10.44.34.07 03187 Beagle DEBUG: Starting Inotify Backend 05-03-22 10.44.34.14 03187 Beagle DEBUG: Pre-populated UniqueIdStore cache with 334 items in .01s 05-03-22 10.44.34.16 03187 Beagle INFO: Loaded 53 records from /home/sbishop/.beagle/FileSystemIndex/FileAttributesStore.db in 0.$05-03-22 10.44.34.19 03187 Beagle INFO: Loaded 112 records from /home/sbishop/.beagle/LauncherIndex/FileAttributesStore.db in 0.0$05-03-22 10.44.34.29 03187 Beagle DEBUG: Found 10 types in BeagleDaemonLib, Version=1.4.3.3, Culture=neutral, PublicKeyToken=null 05-03-22 10.44.34.31 03187 Beagle DEBUG: Adding root /home/sbishop 05-03-22 10.44.34.40 03187 Beagle INFO: Starting Evolution mail backend 05-03-22 10.44.34.40 03187 Beagle DEBUG: D-BUS registered obj=Beagle.Daemon.WebHistoryQueryable.WebHistoryQueryable+WebHistoryInd$05-03-22 10.44.34.43 03187 Beagle INFO: Starting Evolution mail backend 05-03-22 10.44.34.43 03187 Beagle INFO: Starting launcher backend 05-03-22 10.44.34.45 03187 Beagle INFO: Scanning Launchers 05-03-22 10.44.34.63 03187 Beagle INFO: Scanning Weblogs 05-03-22 10.44.34.68 03187 Beagle INFO: Found 80 items in 4 weblogs in .05s 05-03-22 10.44.34.90 03187 Beagle INFO: Found 173 Launchers in .45s 05-03-22 10.44.34.73 03187 Beagle DEBUG: Starting mail crawl 05-03-22 10.44.35.09 03187 Beagle INFO: Starting Gaim log backend 05-03-22 10.44.35.58 03187 Beagle INFO: Gaim log backend worker thread done in .47s 05-03-22 10.44.35.65 03187 Beagle INFO: Launcher backend worker thread done in 1.20s 05-03-22 10.44.35.65 03187 Beagle DEBUG: Starting Scheduler thread 05-03-22 10.44.35.66 03187 Beagle INFO: Scanning Tomboy notes... 05-03-22 10.44.35.67 03187 Beagle INFO: Scanned 15 notes in .02s 05-03-22 10.44.35.68 03187 Beagle DEBUG: Starting Inotify threads 05-03-22 10.44.35.69 03187 Beagle DEBUG: Starting task feed:http://www.imendio.com/archive/index.rss;item=http://www.imendio.com/$05-03-22 10.44.35.71 03187 Beagle DEBUG: Mail crawl finished 05-03-22 10.44.35.71 03187 Beagle INFO: Evolution mail driver worker thread done in 1.28s 05-03-22 10.44.35.98 03187 Beagle DEBUG: Ready to accept requests after 2.07s 05-03-22 10.44.35.98 03187 Beagle DEBUG: Starting main loop 05-03-22 10.44.36.12 03187 Beagle DEBUG: Scanned 331 subdirs in 1.79s 05-03-22 10.44.36.12 03187 Beagle INFO: FileSystemQueryable start-up thread finished 05-03-22 10.44.36.13 03187 Beagle DEBUG: Requesting new proxy 'BlamIndex' 05-03-22 10.44.36.13 03187 Beagle DEBUG: Waiting for proxy 'BlamIndex' 05-03-22 10.45.01.14 03187 Beagle DEBUG: Caught exception fetching proxy 'BlamIndex' 05-03-22 10.45.01.14 03187 Beagle DEBUG: DBus.DBusException: No reply within specified time in [0x0005d] (at /home/sbishop/dbus-0.23.2/mono/Message.cs:205) DBus.Message:SendWithReplyAndBlock () in <0x000cd> Beagle.Daemon.RemoteIndexerProxy.Proxy:NewRemoteIndexerPath (string) in [0x00038] (at /home/beagle/beagled/IndexHelperFu.cs:183) GetProxyClosure:ActuallySetProxy () Joe Shaw wrote: On Tue, 2005-03-22 at 09:05 -0600, Shane Bishop wrote: DEBUG: DBus.DBusException: No reply within specified time in [0x0005d] (at /home/sbishop/dbus-0.23.2/mono/Message.cs:205) DBus.Message:SendWithReplyAndBlock () in <0x000cd> Beagle.Daemon.RemoteIndexerProxy.Proxy:NewRemoteIndexerPath (string) in [0x00038] (at /home/beagle/beagled/IndexHelperFu.cs:183) GetProxyClosure:ActuallySetProxy () It's quite probable that there is an exception being thrown on the other side which is hanging the dbus listener and causing this error. Can you make sure that there are no other exceptions thrown in the logs for either beagled or the IndexHelper prior to this one? Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mai
Re: Beagle: Consumes lots of memory making the system unusable
On Mon, 21 Mar 2005 22:36:18 -0500, Lukin <[EMAIL PROTECTED]> wrote: > FWIW - libgmime doesn't seem to be considered 'stable' for the hoary > version of ubuntu. For some reason libgmime-cil installed without > problem, but I couldn't find libgmime via the update manager. > certainly on all my hoary machines, libgmime-cil correctly depends on libgmime2.1 Both packages are in the universe repository. Cheers, -Thom ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
