Re: Beagle 0.1.1
On Tue, 04 Oct 2005 11:43:59 -0400 Jon Trowbridge [EMAIL PROTECTED] wrote: On Tue, 2005-10-04 at 15:36 +, Charlie Law wrote: Has the Beagle wiki site been hijacked? I get a page about Banshee music file sharing. www.beagle-project.org looks OK to me. Is anyone else seeing this? It must have been a local reroute of some kind. If I log on through a VPN, I get a good beagle page. When I log on to the site without the VPN, I get a page about Banshee file sharing. I'm on an unfamiliar network right now, so I suspect there's something strange. But it appears to be local, not general. ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Holmes already works!
Though I'm not a programmer, I was interested in the Beagle hackfest that went on last weekend. I just downloaded the Holmes source from CVS, and I was amazed to see that it already works. In fact, on my system, it's faster and stabler than Best or the Firefox plugin. It's also not bad aesthetically, even though they've only just started working on that aspect. If you're interested in checking out Holmes, go to http://beagle-project.org/Beagle_UI_Hackfest and follow the CVS instructions on that page. Great job, you folks. We really appreciate it. - ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Unhandled Exception in Best
Hi, I'm getting this error in Best with both Beagle 0.1.0 and Beagle CVS-16sept05: === Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object in 0x0 unknown method in (wrapper managed-to-native) Gtk.Application:gtk_main () in 0x7 Gtk.Application:Run () in 0x7 Gnome.Program:Run () in 0x001b8 Best.Best:Main (System.String[] args) === It seems to happen after I attempt three or four searches. Best crashes, disappears, and this message appears in the console (from which I've launched Best). Thanks. BTW, Beagle is truly an app with tremendous potential. Thanks for your work. -Charlie Law On Thu, 15 Sep 2005 17:20:34 -0500 Jon Trowbridge [EMAIL PROTECTED] wrote: I'm pleased to announce the release of Beagle 0.1.0. When you've been working on a project for a while, it is easy to lose perspective. And I recognize that some might accuse me of being biased. But still, I am confident that this Beagle release is one of the most important events in all of human history. I'm happy to let future historians bicker about the precise details of whether it is more or less important than, say, the discovery of penicillin or the Napoleonic Wars... but let there be no doubt: the age of the Beagle has arrived. The list of enhancements in this version of Beagle is daunting --- the only way to truly appreciate the scope of this release is to read the detailed notes below. Highlights include: * Faster indexing * Substantially improved querying * A smarter file system backend * More and better filters * UI improvements * Better APIs for client applications * A huge number of bug fixes * An adorable cartoon dog who fights crime Well, there was a small problem with the adorable cartoon dog, so he didn't quite make it into this release. Maybe next version. But you are going to love the little guy --- he's cute as a button! The only way to fully appreciate it is to run it. Use it. Live it. And yes, there are bugs --- and who among us can claim that our software is perfect and hassle-free? Even this milestone in the human struggle for enduring happiness and prosperity has some glitches. The nastier ones are described at the end of these notes, but there are certainly all sorts of little annoyances lurking just below the surface. So please don't integrate Beagle into the space shuttle's navigation system quite yet. But if you find a bug, file it at bugzilla.gnome.org. We'll fix it. Honest. OUR MANY URLS - To download the 0.1.0 tarball or learn more, visit the Beagle wiki at: http://www.beagle-project.org Joe Gasiorek writes a Beagle newsletter. You can read it at: http://www.beagle-project.org/Newsletter The latest gossip is available at: http://www.planetbeagle.org Nat Friedman made some cool movies that demonstrate Beagle in action: http://nat.org/demos We still talk about Beagle on the dashboard-hackers mailing list: http://mail.gnome.org/mailman/listinfo/dashboard-hackers Anthony Trollope, the great (and alarmingly prolific) Victorian novelist, was also the inventor of the free-standing mailbox: http://en.wikipedia.org/wiki/Anthony_Trollope WHAT IS BEAGLE? --- Beagle is a tool for indexing and searching your data. 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: * Mono 1.1.7 or better, along with the full Mono stack * gtk-sharp 1.9.5 or better * Gecko-sharp 2.0 * Gmime 2.1.16 * Libexif 0.5.7 or better For the best possible Beagle experience, you should also have: * Evolution-sharp 0.10.2 * A *patched* wv 1.0.3 --- the patch is available from http://users.avafan.com
Re: Unhandled Exception in Best
On Fri, 16 Sep 2005 19:31:27 -0500 Jon Trowbridge [EMAIL PROTECTED] wrote: This is gtk-sharp related. As of 0.1.0, we require gtk-sharp 2. You might have old or broken gtk-sharp dlls lying around on your system, and some components of Beagle might be building against those dlls. That sounds like a relatively easy fix. Should I uninstall gtk-sharp-1.0.7, then? And should I rebuild Beagle? Do you think I need to rebuild the other Beagle software prerequisites as well (e.g., Mono)? Thanks very much. ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Unhandled exception in Beagle CVS 27may05
I just compiled Beagle CVS from today (27 May 05). The Beagle daemon seems to be working well, but best crashes with this message: [EMAIL PROTECTED]:~$ best *** Registering -webcal handler. *** Registering text/calendar handler. *** Registering webcal protocol handler. Unhandled Exception: GConf.NoSuchKeyException: Key '/desktop/gnome/interface/font_name' not found in GConf in 0x000e5 GConf.Client:Get (string) in 0x00018 Beagle.Util.GeckoUtils:SetFonts () in 0x00077 Beagle.Util.GeckoUtils:SetSystemFonts () in 0x0008a Best.Best:Main (string[]) Does anybody know of a fix, or should I revert to a release version. Thanks! ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle and D-BUS
One question: does the CVS version still need dbus-sharp to compile? Somebody asked me today, and I couldn't answer him. I know that Beagle doesn't depend on dbus, but I didn't know if it would compile without having dbus-sharp installed. Thanks. On Wednesday 18 May 2005 09:55 pm, Logic wrote: I also compiled the cvs version today and i can say, it runs very stable. I also got the feeling that it is running at a faster speed, especially i got the feeling that best is running faster. Keep up the great work! On Tue, 2005-05-17 at 12:47 +, Charlie Law wrote: I just compiled and installed the new D-BUS-free Beagle from CVS, and I can attest that it runs more stably. Before I was having to go through the dbus-launch --auto-syntax routine, including exporting DBUS_SESSION_BUS_ADDRESS, etc. This is much easier to use. I'm running Slackware 10.1 (current) on a 2.6.11 kernel. So far, so good. Thanks for detaching the Beagle from its D-BUS leash. -C.L. On Tuesday 17 May 2005 12:53 am, Jon Trowbridge wrote: In his recent State of the Pooch e-mail, Joe described our work to remove D-BUS from Beagle: http://mail.gnome.org/archives/dashboard-hackers/2005-May/msg00011.html This morning I merged the beagle-no-dbus-branch into CVS HEAD. We are still trying to chase down some bugs, but Beagle from CVS should now be substantially more robust. All sorts of essentially-unfixable race conditions related to our use of D-BUS for IPC between the Beagle daemon and the indexing helper process have now been eliminated. Unless calamity strikes, we'll release a D-BUS-free Beagle 0.0.10 sometime this week. -J ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle and D-BUS
I just compiled and installed the new D-BUS-free Beagle from CVS, and I can attest that it runs more stably. Before I was having to go through the dbus-launch --auto-syntax routine, including exporting DBUS_SESSION_BUS_ADDRESS, etc. This is much easier to use. I'm running Slackware 10.1 (current) on a 2.6.11 kernel. So far, so good. Thanks for detaching the Beagle from its D-BUS leash. -C.L. On Tuesday 17 May 2005 12:53 am, Jon Trowbridge wrote: In his recent State of the Pooch e-mail, Joe described our work to remove D-BUS from Beagle: http://mail.gnome.org/archives/dashboard-hackers/2005-May/msg00011.html This morning I merged the beagle-no-dbus-branch into CVS HEAD. We are still trying to chase down some bugs, but Beagle from CVS should now be substantially more robust. All sorts of essentially-unfixable race conditions related to our use of D-BUS for IPC between the Beagle daemon and the indexing helper process have now been eliminated. Unless calamity strikes, we'll release a D-BUS-free Beagle 0.0.10 sometime this week. -J ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
making progress, but Beagle still breaking
With help from several of you, I've finally got Beagle working fairly well on my Slackware 10.1 system, but it still breaks down after a while. Here's the error message that I get: Unhandled Exception: System.IO.IOException: Win32 IO returned ERROR_NO_MORE_FILES. Path: /proc/loadavg in [0x002be] System.IO.FileStream:.ctor (string,System.IO.FileMode,System.IO.FileAccess,System.IO.FileShare,int,bool,bool) in [0xd] (at /home/ftp/mono/mono-1.1.4/mcs/class/corlib/System.IO/FileStream.cs:115) System.IO.FileStream:.ctor (string,System.IO.FileMode,System.IO.FileAccess,System.IO.FileShare) in 0x0004b (wrapper remoting-invoke-with-check) System.IO.FileStream:.ctor (string,System.IO.FileMode,System.IO.FileAccess,System.IO.FileShare) in 0x000a7 Beagle.Util.SystemInformation:CheckLoadAverage () in 0x7 Beagle.Util.SystemInformation:get_LoadAverageOneMinute () in 0x00103 Beagle.Util.Scheduler:ComputeDelay (Beagle.Util.Scheduler/Priority,double) in 0x00348 Beagle.Util.Scheduler:Worker () in 0x00037 (wrapper delegate-invoke) System.MulticastDelegate:invoke_void () Any ideas? Thanks! -C. Law ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: making progress, but Beagle still breaking
Joe, I hope this info is helpful. Thanks for your reply. I really like Beagle and am hoping the best for it. According to System Monitor, the PID for mono-beagled is 3027. Indented below that process is another mono-beagled listing, with the PID 3029. (More PID info is below.) Yes, from what I can tell my problem looks the same as the one reported in 165819. My error messages are nearly identical, and the behavior seems to be, too. FYI, I'm using the Beagle built from CVS on 5 April 2005. The crash seems to occur when I'm using Best, but, then, I've not had Beagle running without Best, though I can do this if you like. I can't figure out what's triggering the crash, however. It does seem to happen when I ask Best to show me search results from something that apparently isn't in the index yet. Please let me know how I can help pinpoint this problem further. I'm running Slackware current, dbus 0.23.4, gtk-sharp-1.0.5, mono-1.1.4, gecko-sharp-0.6 FYI, the PIDs for the following processes are: dbus-daemon-1 = 2990 dbus-launch = 2988 sh (under mono-beagled 3029 under mono-beagled 3027) = 3036 mon (under sh) = 3037. I looked at /proc/3027/fd and all I see is a bunch of @1, @2, etc., listings on up to @999. On 04/06/2005 05:39:55 PM, Joe Shaw wrote: Hi, On Wed, 2005-04-06 at 15:39 +, Charlie Law wrote: With help from several of you, I've finally got Beagle working fairly well on my Slackware 10.1 system, but it still breaks down after a while. Here's the error message that I get: Unhandled Exception: System.IO.IOException: Win32 IO returned ERROR_NO_MORE_FILES. Path: /proc/loadavg Hmm, this could be a dup of bug 165819 and/or 171516. Can you find out the pid of the beagled process (the one with a controlling tty, not the helper process that mono spawns) and look at /proc/pid/fd and see if you notice a trend? Check out the attachment in 165819 and see if it's similar with a bunch of index segment files open but marked as (deleted). If this is it, and you can duplicate this reliably that's great. We haven't been able to track this bug down for some time. We're counting on you, Charlie! Thanks, Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Beagle problem on Slackware 10.1
I've built and installed Beagle (from CVS 31mar05) on my Slackware 10.1 system. I think I'm getting close, but I still get this type of error message (see below) when I launch the Beagle daemon. Any suggestions would be greatly appreciated. screen output from beagled --fg --debug [EMAIL PROTECTED]:~$ beagled --fg --debug INFO: Starting Beagle Daemon (version 0.0.9) DEBUG: Command Line: /usr/local/lib/beagle/BeagleDaemon.exe --debug --fg DEBUG: Initializing D-BUS DEBUG: Acquiring com.novell.Beagle D-BUS service DEBUG: Found index helper at /usr/local/lib/beagle/beagled-index-helper DEBUG: Launching helper process! DEBUG: D-BUS registered obj=Beagle.IndexHelper.RemoteIndexerImpl path=/com/novell/BeagleIndexHelper/Factory owner=(none) DEBUG: Helper Size: VmRSS=9.4 MB, size=1.00, 0.0% DEBUG: Connecting to com.novell.BeagleIndexHelper DEBUG: Initializing RemoteControl DEBUG: D-BUS registered obj=Beagle.Daemon.RemoteControlImpl path=/com/novell/Beagle/RemoteControl owner=(none) DEBUG: D-BUS registered obj=Beagle.Daemon.FactoryImpl path=/com/novell/Beagle/Factory owner=(none) DEBUG: Starting QueryDriver Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object in 0x0 unknown method in (wrapper managed-to-native) Gtk.Application:gtk_main () in 0x7 Gtk.Application:Run () in 0x002c1 Beagle.IndexHelper.IndexHelperTool:Main (System.String[] args) DEBUG: Starting Inotify Backend DEBUG: Pre-populated UniqueIdStore cache with 1 items in .01s INFO: Loaded 0 records from /home/claw/.beagle/FileSystemIndex/FileAttributesStore.db in 0.000s INFO: Loaded 0 records from /home/claw/.beagle/LauncherIndex/FileAttributesStore.db in 0.000s DEBUG: Found 10 types in BeagleDaemonLib, Version=1.4.3.3, Culture=neutral DEBUG: Adding root /home/claw ioctl: Bad address WARN: Exception caught while executing Beagle.Daemon.FileSystemQueryable.FileSystemQueryable:Void StartWorker() WARN: System.Exception: Attempt to watch /home/claw failed! in 0x00133 Beagle.Util.Inotify:Watch (System.String path, EventType mask, EventType initial_filter) in 0xf Beagle.Util.Inotify:Watch (System.String path, EventType mask) in 0x00023 Beagle.Daemon.FileSystemQueryable.InotifyBackend:WatchDirectories (System.String path) in 0x000ba Beagle.Daemon.FileSystemQueryable.FileSystemModel:ScanOne_Unlocked (Beagle.Daemon.FileSystemQueryable.Directory dir) in 0x000df Beagle.Daemon.FileSystemQueryable.FileSystemModel:ScanAll () in 0xd Beagle.Daemon.FileSystemQueryable.FileSystemQueryable:OnModelNeedsScan (Beagle.Daemon.FileSystemQueryable.FileSystemModel source) in (wrapper delegate-invoke) System.MulticastDelegate:invoke_void_FileSystemModel (Beagle.Daemon.FileSystemQueryable.FileSystemModel) in 0x003ef Beagle.Daemon.FileSystemQueryable.FileSystemModel:AddRoot (System.String path) in 0x00035 Beagle.Daemon.FileSystemQueryable.FileSystemQueryable:StartWorker () in (wrapper delegate-invoke) System.MulticastDelegate:invoke_void () in 0x00018 Beagle.Util.ExceptionHandlingThread:ThreadStarted () ioctl: Bad address WARN: Exception caught while executing Beagle.Daemon.BlamQueryable.BlamQueryable:Void StartWorker() WARN: System.Exception: Attempt to watch /home/claw/.gnome2/blam failed! in 0x00133 Beagle.Util.Inotify:Watch (System.String path, EventType mask, EventType initial_filter) in 0xf Beagle.Util.Inotify:Watch (System.String path, EventType mask) in 0x00077 Beagle.Daemon.BlamQueryable.BlamQueryable:StartWorker () in (wrapper delegate-invoke) System.MulticastDelegate:invoke_void () in 0x00018 Beagle.Util.ExceptionHandlingThread:ThreadStarted () INFO: Starting Evolution mail backend DEBUG: D-BUS registered obj=Beagle.Daemon.WebHistoryQueryable.WebHistoryQueryable+WebHistoryIndexerImpl path=/com/novell/Beagle/WebHistoryIndexer owner=(none) INFO: Starting launcher backend INFO: Scanning Launchers ioctl: Bad address Unhandled Exception: System.Exception: Attempt to watch /usr/share/applications failed! in 0x00133 Beagle.Util.Inotify:Watch (System.String path, EventType mask, EventType initial_filter) in 0xf Beagle.Util.Inotify:Watch (System.String path, EventType mask) in 0x00167 Beagle.Daemon.LauncherQueryable.LauncherQueryable:Watch (System.String path) in 0x00158 Beagle.Daemon.LauncherQueryable.LauncherQueryable:Start () in 0x00016 Beagle.Daemon.Queryable:Start () in 0x0012d Beagle.Daemon.QueryDriver:Start () in 0x00ac6 Beagle.Daemon.BeagleDaemon:Main (System.String[] args) end of screen output ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
