Re: 0.2.0 indexing
On Tue, 2006-01-24 at 11:10 -0500, Jose daLuz wrote: I didn't notice until reading this thread, but my Tomboy searches are not working either. The index-info indicates my notes are indexed, but entering text from the notes into beagle-search doesn't return any results. The command-line beagle-query does work, though. Ah, ok, this is a known bug. beagle-search doesn't have a tomboy tile yet. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Error starting up Beagle 0.2.0 for first time
Hi, On Tue, 2006-01-24 at 10:30 -0700, Jared Smith wrote: Error: Unhandled exception thrown. Exiting immediately. Error: System.DllNotFoundException: glibsharpglue-2 Not sure what to do with this one. I tried compiling and installing gtk-sharp2 2.4 to see if that would help and it gave this same error. Any more suggestions? You should have a libglibsharpglue-2.so file in the prefix you installed mono into. That path needs to be in either your /etc/ld.so.conf file or your LD_LIBRARY_PATH. You can set the MONO_LOG_LEVEL=debug MONO_LOG_MASK=dll environment variables to see additional debugging information about from where it is trying to load that library. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: 0.2.0 compile - sqlite2
Hi, On Sat, 2006-01-21 at 07:46 -0800, Ron Pellegrino wrote: The docs say sqlite3 is not yet supported, and compiling 0.2.0 fails for me with requires sqlite2...have been using 0.1.4 mandriva cooker rpm with no problems, so I'm a bit baffled as to how to solve this, especially after looking high low for sqlite2 which I cannot find anywhere. Any ideas? It's looking for the sqlite.pc file, which is usually included in the devel package. Do you have sqlite2-devel (or something similar) installed? Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Block indexing of entire mail domains in Firefox extension?
Hi, On Sun, 2006-01-22 at 13:41 -0800, Jeffrey Dick wrote: * In Preferences of Beagle 0.1.2 extension for Firefox 1.5 (Deer Park, Gecko/20060117), I add domains mail.google.com, mail.yahoo.com and hotmail.msn.com to the do not index list. * At the login screens (i.e., after typing the above addresses into the location bar) of each site, the Beagle is leashed. But after logging in, whether indexing happens depends on the current location: http://mail.google.com/... leashed http://us.f510.mail.yahoo.com/... sniffing http://by909fd.bay909.hotmail.msn.com/...sniffing Right now the extension is only checking exact hostnames. Also blocking subdomains would probably also be a good idea. Can you file a bug about this? Better yet, send a patch. :) Thanks, Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle-search Max number of results displayed setting
Hi, On Sat, 2006-01-21 at 11:02 -0500, Jose daLuz wrote: I have the Maximum number of results displayed setting at 5. Beagle-search displays top 4 results, More document results displays 8 at a time. Changing max results doesn't change either of these. Is the max results setting a holdover from best, or will it be updated in the future to match beagle-search's behavior? This is a holdover from best, but it probably should still be used with beagle-search. Can you file a bug on this please? Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: in Beagle 0.20 some backends stops indexing after some time,
Hi, On Mon, 2006-01-23 at 10:46 +, Raghu GS wrote: it is work fine, but not for a long time, actually, file system backend is always working. but IndexingService backend, KMail backend and Kopete back all are stops indexing after some time, they indexes unindexed contents only after restarting beagle deamon, then indexes for some time and then those would stops indexing again and those would index only after restarting beagled, With the indexing service backend, can you start beagle with only that backend enabled and in the foreground (beagled --fg --debug --allow-backend indexingservice) and look for errors in the log? At what point does it stop indexing web pages? Is it easy to reproduce this case? Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Another beagle-search 0.2.0 crash
On Mon, 2006-01-23 at 14:41 -0500, Carlos Moffat wrote: No ideas? Is there any other information that I can gather to help debug this problem? Looking at the code, it looks like this was fixed (or at least worked around) in CVS. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: compiling beagle0.1.4
Hi, On Tue, 2006-01-17 at 11:07 +0100, GK wrote: I read that I can give the configure option --enable-webservice=yes while compile beagle from source. The webservices interface has been disabled since the 0.1.3 release. See my earlier email about that. But that's not related to your build problems... /Lucene.Net/QueryParser/QueryParserTokenManager.cs(1268,1): warning CS0162: Unreachable code detected /Lucene.Net/QueryParser/QueryParserTokenManager.cs(1178,8): warning CS0219: The variable `kind' is assigned but its value is never used /Lucene.Net/QueryParser/QueryParserTokenManager.cs(1179,10): warning CS0219: The variable `specialToken' is assigned but its value is never used /EvolutionMailDriver/EvolutionMailIndexableGenerator.cs(367,4): error CS1502: The best overloaded method match for `GMime.Object.WriteToStream(GMime.Stream)' has some invalid arguments /EvolutionMailDriver/EvolutionMailIndexableGenerator.cs(367,4): error CS1503: Argument 1: Cannot convert from `System.IO.MemoryStream' to `GMime.Stream' Compilation failed: 2 error(s), 62 warnings make[2]: *** [BeagleDaemonLib.dll] Fehler 1 What version of gmime do you have installed? Beagle 0.1.4 requires gmime 2.1.16 or 2.1.17. It won't work with 2.1.18 due to a different API. If you're building CVS Beagle, it requires gmime 2.1.18. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle on Debian AMD64
Hi, On Tue, 2006-01-17 at 20:57 +0100, Jack Malmostoso wrote: I read the thread regarding Beagle on Debian AMD64 and I would like to confirm the bug. The error I get is: Does the error happen immediately after startup? Is there anything else printed immediately before this segfault? In a previous email it was suggested that it could be mono horribly broken, but right now I am playing mp3s with Muine... Ok, that's good to know. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 1.3-1 configuration on Debian AMD64?
Hi, On Wed, 2006-01-11 at 21:03 +0100, Joost Kraaijeveld wrote: I assume that if I add directories outside my home directory (e.g. /usr/src and /usr/share/doc) that after dismissing the applet en reopening the applet again my added entries should still be visible. They are not. I think they should be stored in one of the config files but I am unsure which one and what syntax. That is probably this bug: http://bugzilla.gnome.org/show_bug.cgi?id=324904 Which is fixed in CVS now. I will do that later, probably tomorrow but I almost always get the following message in my term: = Got a SIGSEGV while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. = Stacktrace: in 0xb (wrapper managed-to-native) System.Runtime.InteropServices.Marshal:PtrToStringAnsi (intptr) Native stacktrace: mono-beagled(mono_handle_native_sigsegv+0x88) [0x511138] mono-beagled [0x4dffc8] /lib/libpthread.so.0 [0x2b1827a0] /lib/libc.so.6(strlen+0x30) [0x2b58ce60] mono-beagled(mono_string_new+0x39) [0x4a5f79] [0x42b62023] A segfault makes me think that this isn't a bug in Beagle, but I don't have a x86-64 box so I can't really check up on this. Do other mono-based apps like Tombody, F-Spot, etc. run? Is anyone else out there running Beagle on an Opteron? (Preferably Debian) Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: best segfault with firefox 1.5
Hi, On Sat, 2006-01-07 at 16:32 -0500, George Sherwood wrote: On Thu, 2006-01-05 at 18:18 -0500, George Sherwood wrote: Is any one else seeing problems with best and firefox 1.5? I am using Sourcemage GNU/Linux and building beagle 0.1.4 and firefox 1.5 from source. If I build firefox 1.0.7 then best runs fine, if I build firefox 1.5 then when I run best it segfaults. I meant to reply to the original mail, I must have forgotten. My recommendation was to rebuild beagle against FF 1.5 and see if that has an effect. I am not sure the two versions are binary compatible for library consumers. Just to add a little more information, if I run mono Best.exe I get this error: [EMAIL PROTECTED]:/usr/lib/beagle$ mono Best.exe Unhandled Exception: System.DllNotFoundException: libbeagleuiglue in (wrapper managed-to-native) Beagle.Util.GeckoUtils:blam_gecko_utils_init_services () in 0x7 Beagle.Util.GeckoUtils:Init () in 0x0006c Best.Best:Main (System.String[] args) Try running best with MONO_LOG_LEVEL=debug MONO_LOG_MASK=dll and look for errors in the output, like a missing symbol or something like that. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Hi all, and help please.
Hi, On Sun, 2006-01-08 at 22:58 -0600, David Uvalle wrote: Im trying to use the text-indexer but i got the next error. [EMAIL PROTECTED]: mono text-indexer.exe -i ../../example1.txt no such file (/home/davor/.dashboard/backend-data/text-index/basis.db) and a lot of unhandled exceptions, how do i generate the basis.db file ? I have Mono.Data.SqliteClient.dll and use mono version 1.1.8.3 What am I doing wrong ? That code hasn't been touched in 2.5 years, so it's no wonder it doesn't work. :) Right now dashboard is on hold in favor of finishing Beagle, which will be the indexer for dashboard going forward. What are you looking to do, exactly? Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Beagle will require CVS gmime for a bit
Hi, I am about to commit a change which will require a CVS gmime. Sorry about the inconvenience, but it will mean reduced memory usage both in the daemon and in the index helper. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle will require CVS gmime for a bit
Hi, On Sun, 2006-01-08 at 20:58 +0100, Joel Mandell wrote: Hey, I did a cvs up in beagle folder - but forget to do the output to a file(to see what files that was updated). What files are updated(affected yadda yadda)? http://cia.navi.cx/stats/project/gnome/beagle/.message/24447 Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle will require CVS gmime for a bit
On Mon, 2006-01-09 at 15:06 -0500, Joe Shaw wrote: Hi, On Sun, 2006-01-08 at 20:58 +0100, Joel Mandell wrote: Hey, I did a cvs up in beagle folder - but forget to do the output to a file(to see what files that was updated). What files are updated(affected yadda yadda)? http://cia.navi.cx/stats/project/gnome/beagle/.message/24447 Also http://cia.navi.cx/stats/project/gnome/beagle/.message/2460b Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Another error compiling Beagle 0.1.4
Hi, On Thu, 2006-01-05 at 12:04 -0700, Chad Scholes wrote: I get the following error trying to compile Beagle 0.1.4. I installed the patch mentioned in other lists but this doesn't seem to have anything to do with that. Any ideas what the problem is? The version of gmime-sharp you have installed needs to be built against the version of glib-sharp you have installed. Your best bet is to make sure you installed gmime and gtk-sharp2 from the same place. Or if you built gmime yourself, simply rebuild it. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.1.4 build failing
Hi, On Tue, 2006-01-03 at 16:58 -0500, George Sherwood wrote: My build of beagle 0.1.4 is failing with the following error: Please read the release announcement: http://mail.gnome.org/archives/dashboard-hackers/2005-December/msg00086.html Thanks, Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Away for a little bit
Hey, I'm going to be on vacation until January 3rd, so I won't be on IRC and I'll have limited access to email, so if I'm a little slow getting back to you, that's why. But please keep sending patches and filing bugs at bugzilla.gnome.org! Thanks, Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
ANNOUNCE: Beagle 0.1.4
Hi, I'm pleased to announce the release of Beagle 0.1.4. The focus of this release has been bug fixing. A number of bugs related to limiting searches by source, getting snippets for results, searching for files by extension, ID3 tags within audio files, among many others have been fixed. IMPORTANT NOTE ABOUT MONO 1.1.12 This version of Beagle will not build unpatched against Mono 1.1.12 as currently released. This is because of an incompatible API change in one of the assemblies Beagle uses. The Mono developers will be fixing this issue soon. In the meantime, you can apply the following patch to your beagle source tree: http://bugzilla.gnome.org/attachment.cgi?id=56272action=view OUR MANY URLS - To download the 0.1.4 tarball or learn more, visit the Beagle wiki at: http://www.beagle-project.org 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 Mercury is a liquid at room temperature because its valence electrons are not easily shared, weakening mercury-mercury bonding: http://antoine.frostburg.edu/chem/senese/101/periodic/faq/why-is-mercury-liquid.shtml 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 also provides Firefox and Epiphany extensions that allow web pages to be indexed as the user visits them. 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.10 or better, along with the full Mono stack * Gecko-sharp 2.0 * gtk-sharp 2.3.90 or better * 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 * libgsf 1.12.1 and gsf-sharp 0.6 * Either wv 1.2.0, or a *patched* wv 1.0.3 --- the patch is available from http://users.avafan.com/~fredrik/beagle/wv-libole2-readonly.patch * An inotify 0.24-enabled kernel. Inotify is in the mainline Linux kernel as of 2.6.13. CHANGES SINCE 0.1.3 --- Daemon/Infrastructure: * Clean up snippet requesting API to be much simpler for clients. (Joe Shaw, Jon Trowbridge) * Fix libbeagle to allow snippets to be requested. (Joe) * Fix date range queries in libbeagle. (D Bera, Joe) * Fix filtering by source in libbeagle. (Joe) * Fix file extension queries. ie, ext:jpg. (Bera) * Pre-initialize the serializer in connection handler. Removes the slight lag in the first response. (Bera) * Added beagle:NoPunctFilename property to files. (Jon) * Clean up error handling in the message passing code to aid debugging. (Joe) * Add unstored properties, so that indexables can send hints to filters. (Bera) * Fix properties to be both searched and stored by default in libbeagle. (Joe) * Wait up to a minute for the index helper process to start, as it may take longer than the previous 4 seconds to respond to messages. (Bera, Joe) * Fix an unlikely race in the messaging server which would throw an exception if the daemon was shut down before it had finished starting. (Joe) * Remove the unused cancelled query response. (Joe) Backends: * Enable the Konqueror history backend by default. (Bera) * Use indexable hints in KonqQueryable to pass charset information to the filter. (Bera) * Check for additional inotify events when indexing Gaim logs, so that they are indexed whenever a message is received and not only when the conversation is closed. (Joe) * Add progress percentages to the Evolution mail backend. (Joe) Filters: * Fix a bug which caused the daemon to hang when indexing certain Powerpoint files
Re: Best crashes when rendering results from mail backend
Hi, On Thu, 2005-12-15 at 09:45 +0100, Jens Auer wrote: Here is what I get with dpkg -l: ii evolution 2.5.3-0ubuntu1 ii libevolution-cil 0.10.2-1ubuntu2 ii evolution-data-server 1.5.3-0ubuntu1 I think evolution-sharp is called libevolution-cil in Debian/Ubuntu, since there are no evolution-sharp packages available. I upgraded to the 1.5.3 version because of problems with my IMAP account, but it didn't work with 1.4 either. Ok, evolution-sharp isn't compatible with e-d-s 1.5.x yet. When you said it didn't work with 1.4, is the crash the same? Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Best crashes when rendering results from mail backend
Hi, On Wed, 2005-12-14 at 13:15 +0100, Jens Auer wrote: I just installed beage 0.1.3 on my Ubuntu Linux system by using the packages provided from the dapper repository. What version of evolution-sharp, evolution and evolution data server do you have installed? Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Wiki attack again
On Tue, 2005-12-13 at 09:09 +0100, David Coeurjolly wrote: Hi all, Same attack as yesterday on the wiki pages by users : Kynilyator and Qolyan... Funny game... Working on reverting it. I'm going to lock down the wiki afterward until I can figure out a solution. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle and nautilus
Hi, On Fri, 2005-12-09 at 08:33 -0500, D Bera wrote: PS: One of the places where C#-search api might be slower that libbeagle is XML serialization. Creating an XML serializer is costly and serializing/deserialing is slow in C#. Apparently the tools like genxs.exe and sgen.exe http://www.mono-project.com/XML#genxs.exe are helpful in these scenarios. If anybody has experience using them or knows how useful are they, please let me know. genxs is only for customizing the serialization process. It doesn't result in any precompiled code, so that wouldn't really affect performance in any appreciable way. In the simplest case, it looks like the biggest overhead in creating an XmlSerializer is that it calls into the System.Configuration.ConfigurationSettings code, which causes a bunch of XML to be parsed (ironic, yes). Removing that code reduces overhead by about 65%, but this is only on the order of 100ms. For us, in creating the XmlSerializer, it looks like the overhead is in getting type information for all of the various different Request classes. It's a one-time cost -- for me about half a second -- so in long-living applications like Best or Holmes it won't be noticeable. It's only in short-lived apps (like the now-unused beagle-index-url) that it's a problem. Actual deserialization speed I haven't measured, but it doesn't surprise me that the C version is faster. It's a lower-level implementation, and it ends up being a lot more code to parse. Moreover, I'm not sure if moving to a specialized parser in C# would gain us that much, and I certainly don't think it's worth the effort at this point. Generally speaking, I'm rather happy with the *querying speed* of Beagle. What I'm not satisfied with is the *rendering speed* of Best. Just using Holmes, you can see that it's much, much better. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle and nautilus
Hi, On Fri, 2005-12-09 at 16:44 +, Joel M wrote: Hmm, the fact about beagle - it's a great product - but.. Beagle is the best opensource indexing service out there, the sad thing is that it's depends on gnome libs - it whould been much more fun if it where freedesktop kinda thing :) Yeah, this would be a nice thing to do. Ignoring the UIs, the only real GNOME (not gtk!) dependency is the mime detection we're doing with gnome-vfs. It would be a great starting project for someone to get us ported over to the xdgmime stuff, because that code is all pretty self-contained. Off of the top of my head, I think the main thing we're using gtk for in the daemon is the main loop. Porting this over to just using our own main loop and threads would probably allow us to drop that dependency, but that's a lot more work. Anyway, it's something to work toward. Thanks, Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: ANNOUNCE: Beagle 0.1.3
Hi, On Tue, 2005-12-06 at 01:23 +0100, federico wrote: ** (/usr/lib/mono/1.0/mcs.exe:4850): WARNING **: The following assembly referenced from /usr/lib/mono/gecko-sharp-2.0/gecko-sharp.dll could not be loaded: Assembly: gtk-sharp(assemblyref_index=2) Version:2.6.0.0 Public Key: 35e10195dab3c99f The assembly was not found in the Global Assembly Cache, a path listed in the MONO_PATH environment variable, or in the location of the executing assembly (/usr/lib/mono/gecko-sharp-2.0). This means your gecko-sharp and gtk-sharp are out-of-sync. The gecko-sharp DLL is expecting version 2.6 of the gtk-sharp DLL. You'll have to update your gtk-sharp package. (Probably you should get it from wherever you got the gecko-sharp package) Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: ANNOUNCE: Beagle 0.1.3
On Tue, 2005-12-06 at 09:38 +0100, Tomasz Torcz wrote: That's because mono have terrible (read: non-existant) backward compatibility. You problably have compiled gmime-2.1.16 with older gtk-sharp (which includes glib-sharp). When you upgraded gtk-sharp, you removed glib-sharp which gimem-sharp was linked to. The situation isn't great, but it's improving. The problem isn't with mono so much as with the DLLs themselves. Mono is still a fairly new technology and we don't have all of the kinks worked out yet. We're finally to the point now where gtk-sharp's versioning is straightened out and (at least Novell and SUSE's) packages take mono versioning into account. I get similar problem anytime I upgrade dbus (and dbus-sharp). Every normal app (C ones and Python ones) works OK with newer version of library. But I have to recompile Tomboy everytime, because Tomboy don't want dbus-sharp, it wants dbus-sharp-0.50 and I have only dbus-sharp-0.60. dbus is a poor example. 0.60 is API incompatible with 0.50, so even C apps need to be rebuilt. And the dbus-sharp DLL doesn't do it's versioning correctly, so that needs to be fixed too. Again, chalk this up to us being novices rather than any inherent problem in mono's (and .Net's, really) versioning system. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: FF extension
On Tue, 2005-12-06 at 17:27 +, Robin Haswell wrote: Heads up guys, I just tried to install the beagle indexer 0.4 from cvs and was told it was incompatible with Firefox, any chance someone could take a look at it? I tried adjusting install.rdf a bit but to no avail. FF 1.5 obviously Hmm, works okay for me. What does Help - About Firefox say? Did you try setting the maxVersion in install.rdf to 1.5, 1.5.0, what? Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Need help with Firefox 1.5 on other distributions
Hi, With the release of Firefox 1.5, we can hopefully finally close bug 158101 and install the Firefox beagle extension by default. However, I need some help from you. I need to know how various distributions install Firefox. I have it for SUSE, but I need it for Fedora, Ubuntu and Debian, Gentoo, and any other distros you guys are running out there. I need to know the following information: * The distribution you are running, including version. * The exact package version of Firefox, if you're installing from packages. * From where you got the package or source, if it's from a third-party * The full directory structure of the Firefox installation. On RPM-based distros, rpm -ql will give me what I need. For Debian-based distros, dpkg -L. For other distros, you're on your own. ;) Please add the information to this bug: http://bugzilla.gnome.org/show_bug.cgi?id=158101 Thanks, Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: To modify a property
Hi, On Fri, 2005-12-02 at 21:22 +0100, Norvig Norvig wrote: It is possible to modify a property of an element? For example, in a photography we added numberOfViewer and from another application to be able to modify it. Properties are stored in the index, and the index cannot be changed without refiltering and reindexing the file. So adding properties like this to the index are generally not a great idea. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle thinks Im running windows?
Hi, On Wed, 2005-11-30 at 08:36 +0100, Jonas Karlsson wrote: Error: System.DllNotFoundException: libglib-2.0-0.dll The dll is mapped to a shared library at runtime so that you can have programs which run on both Linux and Windows without any source changes. The mappings are stored in dll.config files. For this one, it's in /usr/lib/mono/gac/glib-sharp/2.4.0.0__35e10195dab3c99f/glib-sharp.dll.config (or something similar), and should say this (or something similar): configuration dllmap dll=libglib-2.0-0.dll target=libglib-2.0.so.0/ dllmap dll=libgobject-2.0-0.dll target=libgobject-2.0.so.0/ dllmap dll=libgthread-2.0-0.dll target=libgthread-2.0.so.0/ /configuration Make sure that you have that file, and that the targets are available on your system. You can also run with environment variables MONO_LOG_LEVEL=debug MONO_LOG_MASK=dll,asm to see mono's debugging output when trying to look up those assemblies and libraries to see if there is anything obviously wrong. You can also try running other gtk-based mono apps like Tomboy or F-Spot to see if they also have this problem. Typically this is something handled by the packages in the distro, so you might want to report this upstream. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle thinks Im running windows?
Hi, On Wed, 2005-11-30 at 17:40 +0100, Jonas Karlsson wrote: Yes, both are true. The file is there (exaclty same path), with exact same contents and the targets are available (after all I linked to them earlier and that worked). Is there a path I have missed that has to be set? You could try setting MONO_GAC_PREFIX=/usr:$MONO_GAC_PREFIX but I bet this isn't the issue. Well, I think it looks suspect: Mono-INFO: DllImport loading location: 'libglib-2.0-0'. Mono-INFO: DllImport error loading library: 'libglib-2.0-0: cannot open shared object file: No such file or directory'. Yeah, it's failing to find the mapping, or else it'd say loading location: 'libglib-2.0.so.0' What does it have to say about glib-sharp? You can also add cfg to the MONO_LOG_MASK to see info specifically about loading the .config files. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle thinks Im running windows?
Hi, On Wed, 2005-11-30 at 18:08 +0100, Jonas Karlsson wrote: Mono-INFO: Config attempting to parse: '/usr/lib/mono/gtk-sharp-2.0/glib-sharp.dll.config'. Mono-INFO: Config attempting to parse: '/etc/mono/assemblies/glib-sharp/glib-sharp.config'. Mono-INFO: Config attempting to parse: '/home/jonas/.mono/assemblies/glib-sharp/glib-sharp.config'. What about when MONO_LOG_MASK=asm? When I run with it set to asm,dll,cfg, I get these lines: Mono-INFO: Assembly Loader probing location: '/usr/lib/mono/gac/glib-sharp/2.8.0.0__35e10195dab3c99f/glib-sharp.dll'. Mono-INFO: Assembly Loader loaded assembly from location: '/usr/lib/mono/gac/glib-sharp/2.8.0.0__35e10195dab3c99f/glib-sharp.dll'. Mono-INFO: Config attempting to parse: '/usr/lib/mono/gac/glib-sharp/2.8.0.0__35e10195dab3c99f/glib-sharp.dll.config'. Is it probing the glib-sharp assembly in the GAC? Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Error building beagle 0.1.2
Hi, On Thu, 2005-11-17 at 14:09 -0500, George Sherwood wrote: ** (/usr/lib/mono/1.0/mcs.exe:15460): WARNING **: The following assembly referenced from /usr/lib/mono/gmime-sharp/gmime-sharp.dll could not be loaded: Assembly: glib-sharp(assemblyref_index=1) Version:2.0.0.0 Public Key: 35e10195dab3c99f The assembly was not found in the Global Assembly Cache, a path listed in the MONO_PATH environment variable, or in the location of the executing assembly (/usr/lib/mono/gmime-sharp). Your gmime-sharp assembly requires gtk-sharp 1.9.5. You'll need to upgrade your gmime-sharp to one which requires 2.3.90. If you built it yourself, a simple rebuild will fix the problem. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: New to Beagle
Hi, On Sat, 2005-11-19 at 21:38 +0100, Alberto Mardegan wrote: The feature of eligante that I care most is the possibility of associating all the identities a user might have (I am 4469906 in ICQ, mardy78 in skype, Alberto Mardegan in emails...) into a single one, and in this way it's possible to see in a unified style all the conversations you had with this user, independently from where they took place (Gaim ICQ, Gaim, Yahoo, e-mail...). Indeed, these can be sorted by date, so you can actually follow the conversations as they happened. Dashboard (http://nat.org/dashboard), which was the precursor to Beagle, did this as well. Beagle has some very rudimentary support for this when it benefits the user interface, but it's not sophisticated or integrated into the engine. The plan is/was to use the rich metadata that Beagle indexes to create an RDF graph that would allow us to do this sort of interesting infomration collation. It might be a good programming project for someone to resurrect Dashboard to test some of these ideas out. As my first impression, I would say that they both can index e-mails and chat conversations, but there are not many other common features. Beagle is somehow more filesystem oriented (please correct me if I'm wrong), and it can index files on the fly, as they are created (does it make use of some advanced capability in the FS?), while eligante is just meant for messages, and retrieves its informations upon the execution of a command. I wouldn't say this is 100% accurate. Beagle has been designed to be able to use a variety of sources other than files. For example, we query the Evolution Data Server without touching any of its files. There are also experimental Bugzilla and Google drivers for getting results from a remote server. There are all kinds of interesting opportunities for this kind of association of data... it's one of the main reasons why we started Beagle in the first place. While we've been mostly focusing on creating a search infrastructure, we're at a point now with Beagle's maturity that it can really be applied in these ways. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
ANNOUNCE: Beagle 0.1.2
[ Jon is having some email problems, so I'm sending this out on his behalf. -j ] I'm pleased to announce the release of Beagle 0.1.2. Since 0.1.1, we've been focusing on fixing bugs and reducing our memory consumption. We still use too much memory, but the situation is definitely improving. This is, without a doubt, our best release yet. This release does contain one major new feature: date-range queries are now supported. A side effect of this change is that Beagle's search indexes will need to be rebuilt. But no need to worry... everything will happen automatically when you run the new daemon. Also, this version of Beagle requires the just-released Mono 1.1.10. Upgrading is definitely worth your while: all earlier versions of Mono contained serious bugs in the io-layer that could cause Beagle to crash or lock up, and 1.1.10 also has optimizations that help reduce Beagle's memory consumption. All of the cool kids are running it, so why aren't you? OUR MANY URLS - To download the 0.1.2 tarball or learn more, visit the Beagle wiki at: http://www.beagle-project.org 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 It is possible to find the k-th largest element of a unsorted list of N numbers in O(N) time: http://en.wikipedia.org/wiki/Selection_algorithm 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.10 or better, along with the full Mono stack * gtk-sharp 2.3.90 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 * libgsf 1.12.1 and gsf-sharp 0.6 * Either wv 1.2.0, or a *patched* wv 1.0.3 --- the patch is available from http://users.avafan.com/~fredrik/beagle/wv-libole2-readonly.patch * An inotify 0.24-enabled kernel. Inotify is in the mainline Linux kernel as of 2.6.13. CHANGES SINCE 0.1.1 --- Daemon/Infrastructure: * Added date range searches. (Joe Shaw, Jon Trowbridge) * Fixed a bug where sending a query to the daemon would cause a helper process to start. (Joe) * Fixed a bug in libbeagle to use our query parser rather than plain text. (Joe) * Added keyword based query support e.g. title:beagle. (D Bera) * Updated pruning of old log files. (Lukas Lipka) * Updated to dotLucene 1.9 RC1. (Daniel Drake) * Lucene locking bug fix. (Daniel) * Small lucene optimizations. (Daniel) * Consolidated glue code into two libraries: libbeagleglue and libbeagleuiglue. (Daniel) * Fixed two scheduler-related crashes associated with a null task source. (Daniel) * New Uri serialization scheme. (Daniel) * Allow inotify to be build conditionally. (Daniel) * Updated our local copy of SqliteClient with recent upstream changes. (Daniel) * Switched from Mono.Posix (which is deprecated) to Mono.Unix. (Daniel) * Fixed some possible instances of unhandled exceptions in the inotify and scheduler code. (Joe) * Fixed a bug in the scheduler's immediate priority throttling code. (Joe) * Added catch-all exception handlers to beagled, the index helper, and beagle-build-index so that if an unhandled exception happens, the program exits immediately and doesn't leave around a hung process. (Joe) * Fixed a race in which the user could start a query against an empty index, documents could be added to the index, but live queries would never be updated until the query was rerun. (Joe) * Fixed a bug in which the document count
Re: Can't build CVS/0.1.1 on Slackware
Hi, On Sun, 2005-10-30 at 11:05 -0800, Taj Morton wrote: I'm running Slackware 10.1 with Mono 1.1.9.2 from the official Bitrock installer binary. Beagle configures just fine, but when I run make, I get this: make[2]: Entering directory `/home/taj/beagle-0.1.1/Util' wsdl -namespace:Beagle.Util -out:GoogleSearch.cs GoogleSearch.wsdl ** (/opt/mono-1.1.9.2/lib/mono/1.0/wsdl.exe:11161): WARNING **: Missing method get_Values in assembly /opt/mono-1.1.9.2/lib/mono/1.0/wsdl.exe, type DiscoveryClientDocumentCollection Looks like your mono build is out of sync. This is an internal error to wsdl.exe, which is a part of the mono distribution. Also, is there some way to confirm that Beagle will be built with inotify support? I'm running a 2.4 kernel with the backported inotify. Not at configure-time, because Beagle will always try to use inotify support at runtime if it's available. Once you run Beagle, though, you can check the log (~/.beagle/Log/current-Beagle), which will say if inotify support isn't available. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Problem/Patch regarding wv1
On Mon, 2005-10-31 at 09:58 +, Daniel Drake wrote: D Bera wrote: http://wvware.sourceforge.net/#news wv-1.2.0 was released on Oct-13th. They explicitly mention ... This release uses libgsf instead of libole2, libxml2 instead of Expat, and glib instead of libiconv. wvSummary is much more useful, the Beagle folks can stop distributing a patched version of 1.0.3 because of the switch to libgsf... So the doc filter should work correctly if I switch to the new wv ? Our glue code no longer compiles against 1.2.0. As they have switched to GSF, the API has changed a lot. Argh. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: PPT filter fixed
Hi, On Fri, 2005-10-28 at 15:33 -0400, Joe Shaw wrote: Those of you blessed with nobility and fortunate enough to be running SUSE Linux 10.0 can get a package here: http://primates.ximian.com/~joe/gsf-sharp-0.5-1.i586.rpm If you try to install this package, you might get a dependency error like: mono(blahblah) = something is needed by gsf-sharp-0.5-1 I couldn't figure out how to turn that off (it's not in 10.0 by default, but it will be in 10.1), but it's safe to install --nodeps. And I am not one to say that lightly. So much for the divine right of kings. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle on Gentoo
Hi, On Thu, 2005-10-27 at 00:36 +0200, federico wrote: i get this error while launching best: ** (/usr/lib/beagle/Best.exe:13223): WARNING **: The following assembly referenced from /usr/lib/mono/gac/gnome-sharp/2.0.0.0__35e10195dab3c99f/gnome-sharp.dll could not be loaded: Assembly: glib-sharp(assemblyref_index=1) Version:2.0.0.0 Public Key: 35e10195dab3c99f The assembly was not found in the Global Assembly Cache, a path listed in the MONO_PATH environment variable, or in the location of the executing assembly (/usr/lib/mono/gac/gnome-sharp/2.0.0.0__35e10195dab3c99f). It looks like your gnome-sharp and glib-sharp are out of sync. I'm not sure how the Gentoo packaging works, but make sure your glib-sharp and gnome-sharp DLLs are the same version. Specifically, your gnome-sharp is probably 1.9.5 and looking for glib-sharp 1.9.5 (but it is probably either 2.3.x or 2.5.x) Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagled stuck, won't shutdown -- debugging suggestions?
Hi, On Fri, 2005-10-21 at 14:47 +0100, Darren Davison wrote: don't know if the same issue, but I regularly see beagle consuming close to 1GB of memory (RSS) after around 3 hours use. --debug seems to show that at some point it always gets stuck in a loop re-indexing the same 2 files. Removing the files never helps - it will just get stuck on two others instead. If these are MS Word documents, you probably don't have a fixed (patched) wv1. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagled stuck, won't shutdown -- debugging suggestions?
Hi, On Fri, 2005-10-21 at 17:07 +0100, Darren Davison wrote: On Fri, Oct 21, 2005 at 11:54:41AM -0400, Joe Shaw wrote: If these are MS Word documents, you probably don't have a fixed (patched) wv1. Thanks Joe - I'll check (can't recall if they were off the top of my head). I do have a few on this machine so it could have been. Is the memory usage issue related to this too, or is that separate? It's entirely possible, but I suspect there are a lot of other memory issues in there that are fixable as well. Jon wrote a great tool for profiling that info and has been going through identifying and (when it's in our code) fixing them. Some of them are inefficiencies in the Mono class libraries, though. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Error in Ubuntu
Hi, On Mon, 2005-10-17 at 23:28 -0400, Rajiv Vyas wrote: I get the following error when I beagled in Ubuntu Breezy: (beagled:17717): WARNING **: _wapi_connect: Need to translate 2 [No such file or directory] into winsock error Not sure what this means or impacts the performance of the search/indexing. That's an errant warning from mono. I believe it's fixed in 1.1.9. It has no impact on Beagle whatsoever. Thanks, Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Glib malloc exception
Hi, On Tue, 2005-10-18 at 08:09 -0400, Kevin Kubasik wrote: Hey, I recently updated to the latest mono (1.1.9.2) and am still getting this error, can anyone offer any direction as to the problem? When run without the File backend, this does not occur, my best guess is that one of the 'glue' libs is not compatible glibc 2.5.3 Can anyone offer insight, or at least, the glibc versions that they have had success with? Does a make clean and remake fix things? What distribution do you use? Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Liferea and IndexingService backends not working in 0.1.1?
Hi,
On Wed, 2005-10-12 at 00:42 +0100, Darren Davison wrote:
DEBUG: Caught ResponseMessageException: Exception has been thrown by the
target of an invocation.
I can't duplicate this, so tracking this down is going to take some
hacking of the code.
In BeagleClient/Client.cs, in the Send() method (the last one in the
file), there's a block of code like this:
try {
ResponseWrapper wrapper;
wrapper = (ResponseWrapper) resp_serializer.Deserialize
(this.buffer_stream);
resp = wrapper.Message;
} catch (Exception e) {
throw_me = new ResponseMessageException (e);
}
Before the throw_me line, add this:
Logger.Log.Debug (CAUGHT: {0}, e);
Rebuild, see if this line is printed, and post the output here.
Joe
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: emails in MH format by mua like sylpheed
Hi, On Sun, 2005-10-16 at 19:36 +0200, Martin Bretschneider wrote: My mua is sylpheed-(claws) for some years and sylpheed does store emails in the so called MH mailbox format¹ that is like the Maildir format and stores each email in one file. So these emails are recognized by beagle as files. Could you use the Maildir backend to index this files as emails as well? I'm not familiar with the file format, and the brief browsing I did from your link didn't really help out there. Do you know the difference between MH and maildir? If it's simple, it'd probably take no time at all to adapt the Maildir filter. If not, it'd probably be a fairly simple project for someone who is itching to get involved in Beagle development. :) Another issue is that beagle seems to use Evolution as the default mua instead of using the default gnome-mua. Could you please use this one? Probably not. There isn't any standard URI scheme when it comes to viewing or replying to mails, and since support for Evolution came first and is arguably the predominant mailer on Linux, we went with that. We do try to work around it a bit, though, by trying to index where the mail came from and then run the right thing based on that. So if you're not running Evolution at all, it probably won't come up. joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Firefox trickiness
Hi, On Mon, 2005-10-17 at 14:27 -0400, Andrew Conkling wrote: On 10/17/05, Joe Shaw [EMAIL PROTECTED] wrote: If Beagle was originally built against an older version of Gecko and then Gecko is updated without rebuilding Beagle, this is going to cause us a lot of problems with upgrades. (And is the reason why you change library versions when interfaces break, damn it.) Are you sighing at Dan and me for not rebuilding Beagle to use Firefox 1.5's Gecko? And will that solve both of our problems? I'm not sure. I'm sighing because this problem could have been avoided with proper library versioning by the Mozilla folk. But yeah, rebuilding Beagle to use the updated gecko will probably fix it. Unfortunately it won't build out of the box, apparently. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Firefox trickiness
Hi, On Wed, 2005-10-12 at 13:23 -0400, Andrew Conkling wrote: I just had a general question: is it possible to prevent errors like this happening? It doesn't seem ideal to require Mozilla/FF to use best, or to be restricted to using a certain version or hand-editing /usr/bin/best (and maybe those are just temporary solutions) and it would be nice if best didn't care which version you had or could figure it out on your own. The new Beagle UI won't depend on gecko, so we'll be able to drop the dependency. At the very least, could an environment variable be set that would be used in best? It'd still have to be edited by the user, but that's no worse than right now, and it wouldn't be in a file that would be overwritten on a reinstall of best, for example. It's hard to say, because I don't know exactly what your error is. Obviously the best choice is to just use packages if they're available, but other than that Beagle doesn't do anything special with regards to libraries... you're likely to see similar errors with other software you built. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagled ctrl-z + fg?
On Thu, 2005-10-13 at 11:06 +0200, Albert Vilella wrote: Hi all, Is there any compromising situation that would break beagled from doing a: beagled --fg # after some minutes/hours Ctrl-z # after some minutes/hours fg This would cause the daemon to suspend, but not the index helper process that it spawns. So any messages that the helper tries to send to the daemon will time-out. That's probably this error. Can you file this as a bug? We should probably be able to handle this exception. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Firefox 1.5 extension
On Mon, 2005-10-10 at 09:45 +0100, Robin Haswell wrote: If I submit a patch which alters the version number on the Firefox extension, do you think it will work? It may, but I doubt it. Give it a try and let us know if it works! I haven't looked at it in any depth, but there is a new site for building extensions for Firefox 1.5. If it doesn't work, it'd be good if you (or someone) can look through it and make sure we do the right thing: http://developer.mozilla.org/en/docs/Building_an_Extension Thanks, Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.1.1
Hi, 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. The Beagle and Banshee wikis are hosted off the same machine. This might be vhost/caching issue on either the server or (since you mentioned later that you're using a VPN) your client. Try shift-clicking refresh. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagled: Sharing violation
Hi, On Fri, 2005-09-23 at 18:18 +0200, Maciej Bliziński wrote: If you fix those, don't worry, I already have some more issues related to web pages indexing with Mozilla Firefox and diacritic characters. Now let's just start off with this sharing violation. This may be fixed with CVS. We fixed a problem with things not being sent in UTF-8 a few days ago. But diacritic characters aren't stripped in searching, so that's still an issue. There's a bug open about that. Do you want a larger chunk of beagled output? Is there anything more that I can provide you with? Yes, please send it to me privately. I think I have a quick fix for it, but there might be an uglier bug behind it. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle search tool - best crashes frequently
Hi, On Thu, 2005-09-22 at 15:55 +0200, Maciej Bliziński wrote: I observe frequent crashes of best. Typical behavior: launch best, type one query, enter, stare at result, type second query, enter, crash. Does this happen universally on the second time, or only with a specific search? I see the immediate problem, but I'm trying to figure out why it happens. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Mail indexer
On Wed, 2005-09-21 at 11:18 +0200, Nils Erik Svangård wrote: OK, I'll try to learn mono by making a licq backend. I'll probably borrow tons of lines of code from the other backends, what do I write on the top of every file I produce. I have checked the source and everything I have seen i copyright novell. Since Im not an employee there I probably should put something else there :) If you're basing your code on existing Novell code, just copy the header, keep the Novell copyright, and add your own, ie: Copyright (C) 2005 Novell, Inc. Copyright (C) 2005 Nils Erik Svangård or whatever. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.1.0 crash
Hi, On Tue, 2005-09-20 at 10:08 +0100, Darren Davison wrote: It's the IMLog backend. Thanks a lot for tracking this down, I just checked in a fix for it into CVS. It is related to the fact that you're running without inotify. If you are building from source you can add the line: task.Source = this; inside the if (!Inotify.Enabled) brace, before the ThisScheduler.Add (task); line in beagled/GaimLogQueryable/GaimLogQueryable.cs. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Memory usage
Hi, On Mon, 2005-09-19 at 20:47 -0400, Gregory Pierce wrote: Well, I did as you suggested (beagled --allow-backend Files) and mono-beagled is up to 601 MB of resident memory! So, as you suspected, it is the Files backend that is at least partly responsible. Is there any other information that I could provide that may help in tracking down what is causing this runaway memory usage? Did you also run it with --debug-memory? If so, please email the ~/.beagle/Log/current-Beagle log to me. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Files backend problem
Hi, On Tue, 2005-09-20 at 13:07 +0300, Aviram Jenik wrote: Here is the last snippet of the IndexHelper log. After that no indexing is done and best freezes. If I kill beagle and restart it while disabling the files backend, everything works ok: It's a bug in the Powerpoint filter. Can you open a bug and (if you can) attach that ppt file to the bug? As a workaround you can make that file unreadable or disable gsf-sharp support at configure-time. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: System.NullReferenceException Beagle CVS
Hi, On Thu, 2005-09-08 at 22:17 -0400, Kevin Kubasik wrote: WARN: Caught exception calling DoQuery on 'Files' WARN: System.NullReferenceException: Object reference not set to an instance of an object in 0x0068f Beagle.Daemon.FileSystemQueryable.FileNameFilter:Ignore (Beagle.Daemon.FileSystemQueryable.DirectoryModel parent, System.String name, Boolean is_directory) in 0x000f7 Beagle.Daemon.FileSystemQueryable.FileSystemQueryable:HitFilter (Beagle.Hit hit) I just checked in a fix for this. Thanks go out to Lukas Lipka who tracked this down. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: e_book_load_uri: no factories available?
Hi, On Sat, 2005-09-17 at 12:59 +0200, Tomasz Torcz wrote: Current Beagle from CVS won't start: (beagled:2164): libebook-WARNING **: Can't find installed BookFactories Unhandled Exception: GLib.GException: e_book_load_uri: no factories available for uri `file:///home/zdzichu/.evolution/addressbook/local/system' What does mean? I have installed evolution-2.4.0, evolution-data-server-1.4, evolution-sharp-0.9. And I use Evolution as calendaring application. This exception shouldn't be fatal. I have no idea what it means, but I checked in a fix so that it won't block the startup of the daemon. If I had to guess, it would be that you have multiple versions of e-d-s on your system and Beagle is loading the wrong one. But either way, it appears to be an issue with libebook (the evolution addressbook library) and not Beagle directly. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.1.0 - problem compiling
Hi, ** (/usr/lib/mono/1.0/mcs.exe:21547): WARNING **: The following assembly referen ced from /usr/lib/mono/gecko-sharp-2.0/gecko-sharp.dll could not be loaded: Assembly: gtk-sharp(assemblyref_index=2) Version:2.0.0.0 Public Key: 35e10195dab3c99f The assembly was not found in the Global Assembly Cache, a path listed in the MO NO_PATH environment variable, or in the location of the executing assembly (/usr /lib/mono/gecko-sharp-2.0). It looks like you don't have gtk-sharp 1.9.x or newer installed. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Some 0.1.0 questions
Hi, On Sun, 2005-09-18 at 12:25 +0200, Andreas Wasserman wrote: Q: I have a large archive of movie trailers, where Beagle could be very handy in handing me results quickly, but I rarely use beagle for this since it seems to produce weird results depending on what I search for. Q: Some search words (like The Rock) throw Best into loading mode not giving any results and making my cursor indicate it's loading until I give it a new search word that doesn't produce this behaviour. Best throws this exception but doesn't crash : Did you run previous versions of Beagle? You may want to delete your indexes (in ~/.beagle/Indexes) and have them rebuilt, since certain specifics of how files are indexed may have changed. Q: Window position for best, could it be saved from session to session? first thing I do every first launch after a startup is move the window to my prefered location. This is #304775. Just need someone to hack it up. :) Q: There is a feature request in bugzilla about Categories, any thoughts on this? For me it would be a godsend, now when Best shows results by date I usually get e-mails first and often end up having to scroll multiple pages to get to what I want, so if I find 110 E-Mails, 2 Video Files and 1 Audio file, having categories would even things out and show my hit on the very first page. I know I can search in specific categories but first of all it's a bunch of extra clicks I have to do before doing the actual search and second of all it doesn't cover categories, just types so I'm screwed there. The whole UI is going to get reworked here soon, including sorting by type, so hopefully this will be fixed before too long. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle memory
Hi, On Mon, 2005-09-19 at 15:50 +0200, Nico Kaiser wrote: @devs: Could this be because of shutdown issues? Whenever I shutdown beagle (via beagle-shutdown) *or* whenever beagle tries to shutdown one of its helpers (when they consume too much memory), I get Zombie processes. Beagle stays intact, but the number of its zombie children grows over time, and if there are such zombies I can't exit beagled without kill-9 it... The zombie processes are a bug in mono. If you upgrade to mono 1.1.8.3 or 1.1.9 these should go away. (I also think we worked around a lot of them in 0.1.0 but I might be wrong about that.) That won't really fix the memory problem though for a singular instance. The index helper process can end up taking a large amount of memory, but it's a short-lived process and we closely monitor its memory usage and shut it down when that happens. That's because of the size and nature of people's data. If beagled grows large, like it has in Gregor's case, that's obviously a bug. And like D Bera said, it would be good if it can be narrowed down to a specific backend. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle memory
Hi, On Mon, 2005-09-19 at 13:00 -0400, Joe Shaw wrote: Can you run beagled with the --debug-memory flag and then file a bug with the logs from ~/.beagle/Log attached? That might give us an idea of what is causing the memory usage to get out of hand. Also, like D Bera suggested, can you narrow it down to one specific backend? That would help quite a bit. I suggest trying the file and mail backends first. They're the most likely culprits. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Memory usage
Hi, On Mon, 2005-09-19 at 15:33 -0400, Gregory Pierce wrote: Beagle has been working great. I am very pleased with it overall; however, I am concerned about its memory usage. The gnome system monitor indicates that it is up to 1.1 GB of memory and that swap space (~1GB) is at 100% usage. Is this normal? I do have a great many files but can I expect the memory usage to decline after it finishes indexing all the files? Is this resident size (RSS) or virtual size (Vsize)? The latter is effectively a meaningless number. But if RSS size is anywhere near 1 gig or even, say, 100 megs, that's too big and there is probably a bug in there. If the main beagle process is that big (beagled), then it probably won't ever go down unless you restart the daemon. Sizes that big are a bug. If it's in the helper process (beagled-index-helper), then it should shut itself down and restart when memory usage gets high. This can happen with a particularly large, misbehaving file (often HTML or MS Word). Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.1.0 crash
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 [0x2] (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
Re: Memory usage
Hi, On Mon, 2005-09-19 at 17:55 -0400, Gregory Pierce wrote: I am not sure what to look for. I just typed beagled --debug-memory --allow-backend and before this I deleted the .beagle directory. Will this restart the indexing process again? And how can I tell whether the problem is in Files and Mail? Sorry, I should have been more clear. If you run beagled --list-backends, it will show you a list of backends that beagled starts up by default. By providing --allow-backend backend name you can limit it to one or more backends. So beagled --allow-backend Files would allow only the file backend. What I suggest doing is starting with just the files backend and then just the mail backend and see if you see the kind of memory spike you have been seeing. If it's in one and not the other (or in both or neither) then that helps narrow down the problem. Thanks, Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: System.NullReferenceException Beagle CVS
Hi, On Fri, 2005-09-16 at 11:27 +0200, Nico Kaiser wrote: WARN: Caught exception calling DoQuery on 'Files' WARN: System.NullReferenceException: Object reference not set to an instance of an object in 0x0068f Beagle.Daemon.FileSystemQueryable.FileNameFilter:Ignore (Beagle.Daemon.FileSystemQueryable.DirectoryModel parent, System.String name, Boolean is_directory) in 0x000f7 Beagle.Daemon.FileSystemQueryable.FileSystemQueryable:HitFilter (Beagle.Hit hit) I've seen this in the past, but not recently. You might want to try bumping up your inotify limits. If that doesn't work, you probably want to purge your file index, since the fixes that have gone in to 0.1.0 wouldn't have applied when you built your index on some earlier version. (You can blow away only your file index by deleting ~/.beagle/Indexes/FileSystemIndex; that way only your files will get reindexed.) Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Indexing errors with beagle 0.1.0 / question concerning io-priority
Hi, On Fri, 2005-09-16 at 14:16 +0200, Jan Taegert wrote: on indexing my data, beagle from time to time brings the following reproducible error messages: 1.) When some file (here: /home/mochila/media/abspiellisten/Unbetitelt.m3u) is trashed: - Slightly different, when the same file is deleted: Can you file a bug for this, and attach the file? 2.) Everytime (!), when filesystem crawling is done: I suspect this is related to #1. 3.) Certain files (The other titels of this album are indexed without errors): 05-09-16 13.27.19.62 31524 Beagle DEBUG: *** Add '/home/.medien/mugge/Sigur Rós/Ágætis byrjun' 'Sigur Rós - Ágætis byrjun - 06 - Hjartað hamast (bamm bamm bamm).ogg' (file) I assume the file name is in UTF-8? If not, things just won't work. Maybe one more bug: best, beagle-query or beagled itself seem to have problems with multiple tagged mp3. - If there is only a idv1 OR a idv2 tag, the content of this tag is displayed correctly in best, but if a file has both, best shows only the filename and - as description: Title 2 of Unknown Album Please file this as well. Bonus points if you can attach a file which has both kinds of tags (but I understand if for legal reasons you can't.) Finally, I have a question: as Tomasz Torcz wrote: Beagle already ionice itself (grep for ioprio). Unfortunately vanilla kernel doesn't allow non-root processess to set self priority to idle, due some priority-inheritance problems. That explains what I get from IndexHelper (I am using cfq-scheduler): 05-09-16 12.59.49.37 31565 IndexH WARN: Unable to set IO-priority for process to idle Is there a workaround for this problem? You'd have to run something like ionice -c 3 su user -c beagled as root, unfortunately. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Firefox 1.5 beta
Hi, On Wed, 2005-09-14 at 18:05 +0200, Andreas Wasserman wrote: It's the Best part ofcourse that fails during compile with some glue stuff to gecko, beagled still run but Best doesn't start nor recompile with Firefox 1.5 beta 1. I haven't tried building with it yet. What's the error? Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.0.12 fails to compile with Mono 1.1.9
Hi, On Mon, 2005-09-12 at 00:31 -0400, Tom McLaughlin wrote: Hi I jut updated to Mono 1.1.9 and wanted to let you guys know building Beagle 0.0.12 with the latest Mono fails. Currently the build is failing with the following errors: SVN is compiling just fine fine though. Maybe time for new release? Thanks. Hmm, I remember fixing compile issues like these a while ago. Yeah, I'd say it's definitely time for a new release. ;) Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: reveal in file manager does not highlight the file.
Hi, On Mon, 2005-09-12 at 21:36 +0200, Lukas Lipka wrote: I know this is possible since Nautilus stores info about the selected file in ~/.nautilus/metadata/ and then selects it when you reopen the window. So this is probably just a matter of adding and hooking up a new command line option. Interesting. Ideally though I'd prefer if you just passed a file URI into nautilus on the command-line and have it highlight the file. If you do it now, you get the error Couldn't display path. The location is not a folder. That would make things dead simple. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle Build Error, CVS Sept, 8 2005
Hi, On Wed, 2005-09-07 at 20:22 -0400, Kevin Kubasik wrote: [EMAIL PROTECTED]:~/src/beagle$ make cd . /bin/sh /home/kevin/src/beagle/missing --run automake-1.9 --gnu automake-1.9: cannot open Filters/entagged-sharp/entagged-sharp.sources: No such file or directory make: *** [Makefile.in] Error 1 Always make sure you cvs update -d. You probably want to add something like this to your ~/.cvsrc: cvs -z3 diff -uNp up -dP Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle Build Error, CVS Sept, 8 2005
Hi, On Thu, 2005-09-08 at 08:02 -0400, Kevin Kubasik wrote: A recent CVS update resolved this issue, there are still run time errors and exceptions being thrown from the evolution bindings, but this is most likely an issue on my part, as I have had issues with the mono bindings for eds since the start, and had to make a few dirty patches to get it to compile. You should probably upgrade to evolution-sharp 0.10. It has compile-time support for both evolution-data-server 1.2 and 1.3. If you post the exceptions, we can diagnose the problem. Thanks, Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle turns my terminal to gobbledegook :s
Hi, On Wed, 2005-08-17 at 11:07 +0100, Joshua Lock wrote: http://incandescant.net/~josh/files/beagle-term.png I'm not certain this is a beagle problem but I only see this when running beagled and as you can see from the screenshot other tabs in the same gnome-terminal are still in English. You can get something like this too if you cat a binary file, so something similar to that is going on. Take a look at the log files in ~/.beagle/Log. You can reset the terminal by doing echo ^V^O BTW. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: wv-1.0.3 doesn't seem to work
Hi, On Tue, 2005-08-16 at 18:47 +0200, Marco Giovanardi wrote: Ok, I've done it, and in fact I got the following error: checking for wv-1.0... Package wv-1.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `wv-1.0.pc' to the PKG_CONFIG_PATH environment variable No package 'wv-1.0' found So, I've reconfigured and remaderemade installed the package wv-1.0.3; the configure report says: config.status: creating wv-1.0.pc Then, trying again with beagle, the configure throws the same error as before... Ok, you need to add $prefix/lib/pkgconfig to your PKG_CONFIG_PATH when you configure beagle. $prefix is probably /usr/local for you, unless you changed it. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Upcoming move to gtk-sharp 2
Hey gang, We planning on moving to gtk-sharp 2 soon, now that it has entered beta and the final stable release will be coming soon. Unfortunately this is going to mean dependency hell for a little while as we get the supporting modules brought up to date (gtk-sharp 1 and 2 don't play well together in the same app). You will need to update: * gtk-sharp (duh) * gecko-sharp * gmime-sharp * evolution-sharp * gsf-sharp gtk-sharp 2 is available from the mono site. Get the 2.3.90 releases, and not the 2.5.x releases (although the latter should also work). gecko-sharp already has a gtk-sharp 2-based release out there that's actively developed. The latest version (AFAIK) is 0.10. You can get source and packages from the mono download page (http://mono-project.org/Downloads) gmime-sharp, evolution-sharp, and gsf-sharp all need to be ported to the new code and re-released. My plan is to land the changes necessary for gmime-sharp and evolution-sharp today or tomorrow, and gsf-sharp shortly thereafter and do releases of each. Then, later in the week, we'll switch beagle over to requiring gtk-sharp 2 and the new versions of all of the modules. Hopefully we'll have packages out there for the SUSE 10.0 beta 2 release and in the SUSE 9.3 gnome supplemental repo. And tseng, if you can get Ubuntu packages out there, you would be my hero. ;) Anyway, any questions, comments, etc. Let em rip. Thanks, Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: kmailqueryable
Hi, You're making all of my points for me. :) On Thu, 2005-08-04 at 11:10 -0400, D Bera wrote: Mostly true. However, * There will be a hure repetition of code in each queryable - regarding setting up inotify, crawler, etc. Yes, but every queryable has to do this anyway. We used to have a general crawler class. It turned out to not be very useful. You have to do this whether you have a queryable class or a crawler class. * Dot-folders, tmp files, hidden-files are widely used in these maildir stores. So, just cant handle every directory and file created in the same way. Exactly, which is why when we need specialized queryables, we can add them. * Naming convention is different in different cases - and they store the mail-folder name in different ways. Ditto. Conceptually, it looks to me like two separate entity - a minimal, simple queryable which just checks the presence of a crawler and asks the specific crawler (which would also be small - just informs the queryable what to do with a new directory/file) what to do the files and directories it sees. It would just look a bit cleaner and easily extensible. The Queryable is the thing which generates the Indexable objects with backend-specific properties on them and adds them to the index. That's work that needs to be done either way, whether it's in the queryable class or a crawler class (I don't think it should even be a separate class...), so it doesn't really save any code and it breaks the existing model we have. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle-cvs as from 20050803 and /dev/inotify + libebook-1.2.so.0
Hi, On Wed, 2005-08-03 at 13:10 +0200, Serge Eric Thiam wrote: 2 - beagled is complaining about not finding libebook-1.2.so.0 and can't do adressbook searching. I have evolution-2.3.6.1 and evolution-data-server-1.3.6.1 as well as evolution-sharp-0.6 installed. When I go to /usr/lib and link libebook-1.2.so.3.1.5 to libebook-1.2.so.0, beagled then crasched as shown in the output (see second attachment) You can't do this. Those numbers (3 vs. 0) are different for a reason. e-d-s 1.3 isn't supported quite yet, although it will be soon. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Maildir support status
Hi, On Fri, 2005-07-29 at 23:03 +0300, Aviram Jenik wrote: Also, I suggest considering Bera's integration with KDE as well: http://dbera.blogspot.com/2005/07/beagle-and-kde.html It works nicely for me (KDE, Debian SID). Perhaps the best course of action would be to add a ./configure option (something like --enablekdesupport), and that will include Bera's KDE code instead of the gnome code. This just changes one hardcoded value for another, and doesn't take into account what environment the user is currently running. I commented on it here: http://mail.gnome.org/archives/dashboard-hackers/2005-July/msg00071.html The right thing to do is abstract the differences away in some sort of interface rather than crufting up the code with #ifdefs. (Incidentally, this is something that has come up on the GNOME lists recently. See: http://mail.gnome.org/archives/desktop-devel-list/2005-July/msg00579.html ... for more info.) Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Maildir support status
Hi, On Thu, 2005-07-28 at 00:34 -0400, D Bera wrote: Where exactly is the difficulty in creating a MaildirIndexable and MailCrawler for indexing maildir files ? In my opinion they can be just wrappers around the FilterMail filter. That would index them as mails and the hits would behave as mails too. A specialized backend (like the EvolutionMailQueryable) makes sense if where you are getting the files from is a data source. For example, a KMailQueryable makes a lot of sense, because there is additional information that you can get from a KMail data source, like the names of folders. It's also necessary for finding out what directories actually have the mail files to crawl. The problems with maildir files showing up and behaving as files rather than mails are just bugs in the tiles and Best. That's where those should be fixed. I made a rough attempt at doing that and created a simple MaildirQueryable. It seems to work for me. Note that it is quite basic (and no crawler support yet) and assumes that your mail directory is ~/.Mail. If anybody wants to give it a try, get it from http://dbera.blogspot.com/2005/07/beagle-maildir-try-1.html If this is not the write method, then it would be helpful if somebody can explain the proper steps or problems with this approach, then it will be extremely helpful. It looks okay from a first glance, but there's not really any interesting logic here. * You've hardcoded ~/.Mail. Where does that come from? Could it be different? How do other mail folders work? * Is there extra information that can be extracted from the data source that isn't handled by the MailFilter? Things like folder name, account name, etc. To see a good distinction, look at the differences between beagled/EvolutionMailDriver/*.cs and Filters/FilterMail.cs. * If there isn't anything to add, does it make more sense to just tell the file system backend to crawl this directory? Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Upgrading Beagle
Hi, On Fri, 2005-07-22 at 14:12 -0400, Rajiv Vyas wrote: I tried upgrading to Beagle's latest version from 0.8, which cam e bundled with SuSE 9.3. YaST said I need to get a newer version of Mono. So I tried installing Mono and ran into dependencies issue with Mono data, etc. So the question is: How do I upgrade Mono without the Red Carpet and not face the depency issue? The mono team distributes updated packages for SUSE 9.3 through Red Carpet. You just need to add the service: rug sa http://go-mono.com/download subscribe to the channel: rug sub mono-1.1-official and then I think just updating everything in that channel should work fine: rug up mono-1.1-official Alternatively, you can download the RPMs directly from their site: http://mono-project.com/Downloads Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: indexing Maildir mails
Hi, On Wed, 2005-07-20 at 22:51 +0300, Aviram Jenik wrote: The problem I'm experiencing is quite different. The mail *is* rfc822, but it does not show up in the results. In fact, when I add a first line to screw the mime detection (make the mail file a 'text/plain') it *does* appear in the results - so the problem is definitely in the FilterMail object. Are you having a problem with body searches, or names of people? I noticed a problem where names were being indexed as keywords and not regular text. Which meant in a mail from me, Joe would match, but Shaw wouldn't. I just fixed this in CVS, but it will require you to reindex the mail. In my tests, I haven't had any problem searching for text in bodies of emails. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: indexing Maildir mails
Hi, On Wed, 2005-07-20 at 12:59 -0400, Ian Soboroff wrote: I have a similar problem... I use Emacs Gnus for mail, which stores a single email per file, but since gnomevfs-info doesn't correctly identify the file type, it doesn't come up as mail: What are the first 4 lines of the file? Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: indexing Maildir mails
Hi, On Wed, 2005-07-20 at 13:15 -0400, Ian Soboroff wrote: $ head -4 ~/Mail/mail/misc/8225 X-From-Line: imap Fri Jul 5 16:33:27 2002 Received: from nist-i.nist.gov (nist1.nist.gov [129.6.94.1]) by email.nist.gov (8.12.2/8.12.2) with SMTP id g65KV3FN011792 for [EMAIL PROTECTED]; Fri, 5 Jul 2002 16:31:03 -0400 (EDT) The X-From-Line is throwing off the MIME sniffer. Most sniffers (including gnome-vfs and Apache) expect one of From, Received, Relay-Version, or Return-Path. They're not technically required to start the file, but it's generally a good, easy to detect convention. Some KMail users are seeing something similar. You could argue that the bug is in freedesktop.org's mime magic database, but realistically it's impossible to detect every possible first line that would be a compliant message. It's generally good behavior for mailers to append their headers rather than prepend them. For this reason you may want to file an interoperability bug against Gnus. See http://bugzilla.gnome.org/show_bug.cgi?id=310462 Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle and galago
Hi, On Tue, 2005-07-19 at 12:18 -0500, Steev wrote: I have seen people with screenshots of the integration so I know its possible to compile, what am I missing? Nothing. You were building with galago support but not evolution-sharp support, and you're apparently the first person to do that. :) I'll fix it in CVS, but you can work around it (and get a better experience) by installing evo-sharp. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle and gdesklets
Hi, On Fri, 2005-06-24 at 12:51 +0100, Adam Lofts wrote: As part of my plan to implement http://www.student.livjm.ac.uk/cmsphend/gnome/scoop.html in gdesklets i've written a desklet to do beagle searches. It is in a primitive state, but can do searches and seems relatively stable. See what you think of it (my artistic skills are limited, and i'm new to python!) Hey, this is pretty neat! I'm happy to see people extended Beagle into other areas. Even if you don't go the Scoop route, I think that just having a Beagle gdesklet is a great thing. I also noticed that you're using the XML API directly. Nicely done. Soon we'll have a C API... one could either bind that into python or also write a native python interface. Once you get it into a state you feel good about releasing, you should definitely add a page for it to the Wiki. Thanks! Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
New filtering changes landed
Hi, I just landed code which adds some flexibility to the filtering system. Expect delays. Filters can now themselves create Indexables which the daemon will in turn filter and index (and so on). This will allow us, when someone actually writes it, to index the contents of archives like zip and tarballs. In a similar vein, the mail backend can now create child Indexables and as a result now filters and indexes all of your mail attachments. In a pretty neat demo I successfully searched for my cousin's name and got a hit of the wedding invitation in MS Word format that my father sent me as an attachment in 1999. The Best tile still needs a fair amount of work to nicely handle these things, but it's a start. Because of these changes, things might be a little unstable for a few days. I had to bump up the minor index version on the mail backend, which means that Beagle has to reindex all of your mail. It also means an updated GMime requirement. We now require 2.1.15. As always, you can download gmime source from here: http://spruce.sourceforge.net/gmime/sources/v2.1/ Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: New filtering changes landed
Hi, On Wed, 2005-06-15 at 17:04 -0400, Joe Shaw wrote: It also means an updated GMime requirement. We now require 2.1.15. I built packages that should work for NLD and SUSE 9.2 and 9.3: http://primates.ximian.com/~joe/gmime-2.1.15.0.200506152050-0.snap.novell.0.1.i586.rpm http://primates.ximian.com/~joe/gmime-devel-2.1.15.0.200506152050-0.snap.novell.0.1.i586.rpm Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: What does --with-thunderbird option do in configure?
Hi, On Sat, 2005-05-28 at 20:06 -0400, Abbas Faiq wrote: I was under the impression that beagle did not search Thunderbird email/address book. It doesn't. See below. Then I noticed the following as one of the configure options: --with-mozilla[=mozilla|firefox|thunderbird] Whether to use mozilla, firefox or thunderbird so I went ahead and used --with-firefox --with-thunderbird as options for ./autogen. Note that the option is actually --with-mozilla=firefox or --with-mozilla=thunderbird. This just tells Beagle from where to get the gecko rendering engine, which is what Best uses to display its UI. Also, how do I get Best to put the right icons on the search results - Word icon for .doc, Excel for .xls, Star office/Open Office for .sxw etc? It should do it automatically. It extracts the icons using gnome-vfs. Are the right icons shown in Nautilus? Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: No reconnect after Process too big
On Thu, 2005-05-26 at 10:37 +0200, Nico Kaiser wrote: Beagle seems to have a memory leak workaround which shuts down the process when it's too big. Well, something seems to be shut down, however it's not the process that consumes memory. mono-beagled still grows constantly from 100 to about 400 MB (where I have to kill it manually)... The helper process is restarted as necessary. The daemon has a failsafe which kills itself once it gets to some insanely large size (I thought it was 100 or 200 megs). Either way, that kind of memory usage is a bug. It doesn't really surprise me, though. We haven't profiled the new message stuff at all yet. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Run tim error in CVS beagle as of May 26
Hi, On Thu, 2005-05-26 at 22:04 -0400, Abbas Faiq wrote: After compiling cvs beagle as of May 26 - I am getting the following run time error: Unhandled Exception: System.IndexOutOfRangeException: Array index is out of range. I just checked in a fix for this. Thanks, Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Serious Beagle Bugs - Best and Web Services
Hi, On Fri, 2005-05-27 at 06:17 -0600, Vijay KN wrote: And yes I too was getting the Best Segmentation fault and checked in a fix in Template.cs file y'day. Your fix is right, but what concerns me is that this bug has existed forever, but is only being triggered now. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle CVS and Evolution Address book
Hi, On Sun, 2005-05-22 at 22:30 +0200, MDK wrote: I had to: $ ln -s /opt/gnome/lib/libebook-1.2.so.3.1.1 /usr/lib/libebook-1.2.so.0 Just a general FYI: This isn't a safe change to make. The major so number (3 vs. 0 in this case) are different for a reason. :) It indicates that the library interface is incompatible. So if you do this there is no guarantee that things will work... there's a good chance it'll crash. What is strange, is that: $ln -s /opt/gnome/lib/libebook-1.2.so.3.1.1 \ /opt/gnome/lib/libebook-1.2.so.0 ..does not work. Since archlinux installs evolution (and all the gnome stuff) in /opt/gnome this should be right way to do that. Anyways, I suppose this is rather an evolution-sharp problem. Is /opt/gnome/lib in your /etc/ld.so.conf or LD_LIBRARY_PATH? Mono just looks in those places for libraries like any other application. But yeah, this looks like an evo-sharp issue. It looks like the version you're using doesn't handle the newer libebook interface. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: MailDir
Hi, On Fri, 2005-05-20 at 06:29 -0400, Nat Friedman wrote: The next step, if someone wants a good project, is to build a driver that can index unmanaged[1] mbox files as well. Filter, not driver. A driver is something else, so I don't want to confuse people with the terminology. :) As I understand it, this has the additional difficulty of requiring that a single file map to multiple MailMessage indexables, and I'm not even sure if Beagle can do this sort of thing yet (the same architectural changes would be required to, for example, index the contents of Zip files and other archives). The biggest problem is referring to these individual messages. Maildir files are easy because it's one message per file, and apps like KMail and Evolution can pretty easily open the mail based on a file URI. No such scheme exists for mbox files. Do you refer to the mbox as a whole with a file URI? Do you tweak the file URI scheme to be something like file:///home/joe/my-mbox?offset=101555 and hope that apps adopt it? This is actually a similar problem for us with archive files or email attachments. Do we want matches to actually refer to the file inside the archive or just the archive itself? We may end up having to pull apart archives (or mboxes), putting files in temporary locations and feeding them to apps. That becomes a slippery slope: do modifications to documents get saved back to the archive? What about email attachments, which are immutable in the mail? I'm not sure what the right thing to do here is. Of course, that stuff aside, I think The Right Way To Do This would be to move the bulk of the message parsing code (using GMime) out of the EvolutionMailIndexableGenerator class and into a more general class that can be reused by a bunch of things. Probably a class in Util is the right way to go, or perhaps we should just do an EmailFilter class. Then the Evo code, the (unused) Mozilla/Thunderbird code, and Noam's maildir code could all use the same mail backend. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Use of extended attributes has issues.
On Thu, 2005-05-19 at 17:13 -0400, Nat Friedman wrote: Whenever I try to copy a Beagle-indexed file onto a filesystem which does not support EAs (for example, a memory stick), horrible, frightening things happen. At the command line, I get this kind of nonsense: [EMAIL PROTECTED] Desktop]$ cp NovellCongres.nl.keynote.odp /media/USB_DISK/ cp: setting attribute `user.Beagle.Uid' for `/media/USB_DISK/NovellCongres.nl.keynote.odp': Operation not supported I don't think this is an issue. I would prefer to see these things, because it means that the filesystem I am copying to doesn't support EAs. And if I am copying around files with cp, that's probably important info to me. It probably doesn't need to do it once for each EA though. cp: setting attribute `user.Beagle.Fingerprint' for `/media/USB_DISK/NovellCongres.nl.keynote.odp': Operation not supported [EMAIL PROTECTED] Desktop]$ It is not even clear to me if the file copied (it did). Exit code aside, how do you ever know if cp sucessfully copied? I don't really think we should be arguing the usability of cp. :) In Nautilus, I get a dialog box telling me that the copy failed because There is not enough space on the destination. And the copy does fail. This happens to me for all files on SUSE 9.3 using subfs, unless I explicitly remount it as vfat, regardless of whether it has EAs or not. (When I remount it as vfat and copy a file with EAs, it copies without warning.) This appears to be a bug in subfs or gnome-vfs' interaction with it, and not related to Beagle. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle forgets indexes, files backend broken
On Tue, 2005-05-17 at 11:21 +0200, Nico Kaiser wrote: - The files backend indexes my files correctly, but seems to be stuck in some directories (no special files, no special file names). It walks this directory over and over again even when there is no open file at all. That's odd. Do you have write access to the directory? Are there any errors in the logs? - When I disable the files backend, all other elements are indexed correctly and Beagle works quite nice. However when I quit and restart beagled, it randomly forgets indexes and re-indexes e.g. all my mail (which is a pain for 40.000 mails). Beagle has to recrawl the mail files to make sure there haven't been any changes since it last checked. It's probably just crawling the mail files, not reindexing them. Unfortunately Evolution's data files makes this an expensive operation, which is something they are fixing for 2.4 I believe. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle forgets indexes, files backend broken
Hi, I haven't looked at the file backend log yet, but... On Tue, 2005-05-17 at 18:15 +0200, Nico Kaiser wrote: The logfile says: - - - - 8 - - - - 05-05-17 18.13.34.04 14799 IndexH DEBUG: Found dangling locks in /home/nico/.beagle/MailIndex/Locks 05-05-17 18.13.34.04 14799 IndexH DEBUG: Purging /home/nico/.beagle/MailIndex This implies that the daemon isn't being shut down correctly. It can't ensure that the index is safe on disk so it starts over. How are you shutting down the daemon? BTW, I'm getting Beagle DEBUG: Caught SocketException -- we probably need to launch a helper: Connection refused every now and then when I try to start beagled That's normal debug spew... nothing to worry about. It just means that the daemon can't connect to a helper process (because one hasn't been spawned yet) and then launches one. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle disregards .noindex
Addendum. On Sun, 2005-05-15 at 13:56 -0400, Joe Shaw wrote: The use of extended attributes is central to the entire indexing infrastructure, so the check done unconditionally. the check is done unconditionally, obviously. What you can do is use the BEAGLE_HOME environment variable to point beagle at a different place to index. You could set up a fake home directory somewhere in /tmp and point BEAGLE_HOME there. I forgot to mention it, but you'll need extended attributes on /tmp or wherever you decide to do this. :) So follow the instructions on the wiki for adding user_xattr to whichever mount point you use. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: State of the Pooch
On Sun, 2005-05-08 at 16:58 +0100, Daniel Drake wrote: If we move away from GNOME CVS, will we lose out on the translations side? Right now, it looks like random gnome translators are stumbling onto our project and and translating it into all kinds of languages, which I'm very impressed by. Yeah, we probably would. I hadn't thought of that. Other GNOME-related projects like Rhythmbox and AbiWord get translations and they're not developed in GNOME CVS. I'll bring it up on gnome-i18n like Enver suggested. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
State of the Pooch
Hi, It's been a while since we sent out an email detailing what we're doing, what our plans are, what all this means, so I thought now would be a good time to fill you in. The big stuff: * Removal of D-BUS from Beagle If you've been hanging around on IRC lately you've probably seen Jon or I talk about this. We are completely removing D-BUS from Beagle because it is by far the #1 barrier to entry for our users. Also, over the course of Beagle's development the way it uses IPC has changed and D-BUS really doesn't make a whole lot of sense for our needs. So what we've done is use the very nice XmlSerialization framework in the .Net platform to construct simple messages that we're sending over Unix domain sockets for both client-daemon and daemon-helper communication. This work is nearly complete and in the beagle-no-dbus-branch branch in CVS. I am hoping we can work out the remaining kinks and get that merged into HEAD this weekend or early next week and get a 0.0.10 release out late next week. * New wiki The wiki is a great resource, but it's not a pretty web page, and a lot of the content is inconsistent and some plainly outdated. We've set up a MediaWiki on some Novell hardware here and I've started migrating a lot of the content over to the new wiki. The plan is that this new Wiki will replace both the Beagle home page (http://gnome.org/projects/gnome) and the existing Wiki (http://beaglewiki.org) and be the central home page that the community can help edit. You can check out the work-in-progress new wiki here: http://segfault.cam.novell.com/~beagle Please do not edit it yet or advertise the site. I don't want to take it live until a core amount of the content has been migrated, like all of the pages linked off the front page and the installation instructions. If you want to help with that, please let me know. * New Best UI This one hasn't been started yet, but our plan is to experiment a bit with the Best UI to see what works well and what doesn't. Obviously we'll be studying existing UIs like Google and Apple's Spotlight. Novell is setting up a permanent usability testing lab here in Boston and we plan to make use of it on a continual basis as we make UI changes. * New filter architecture The current filtering architecture is a little limiting in that for each Indexable object there is only one possible filtering method. This is fine for the majority of content, but in cases where multiple pieces of data are contained in a single object (think an email with multiple attachments, or a tarball) we end up doing pretty much nothing at all with this data. Jon has already committed a good cleanup of much of the code as a side-effect of his work on porting the index helper on the beagle-no-dbus-branch. Unless you're following the day-to-day development of Beagle this probably won't interest you a whole lot, but it will mean that things like PDFs in emails will be indexed, and point you back at the email when you do a search. Pretty neat. * Improving search results Beagle currently ranks results by relevancy. Unfortunately this relevancy hasn't been tuned. At all. So a large part of what we'll be doing is improving the quality of the search results. We'll also be adding other ways to search and sort, such as by date and by type. That's the bulk of it. These tasks are going to be carrying us through the summer. It's still too early to tell whether we'll be at a 1.0 release by then, but either way Beagle will be better than ever. Thanks, Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: NFS
Hi Kyle, On Tue, 2005-05-03 at 11:55 -0400, Kyle Ellrott wrote: I'm looking to see if I can get beagle to work with NFS mounted home directories. Looking through the archives and google, I've seen this question asked a few times, but haven't really heard any success stories. Beagle doesn't work on NFS home directories today. We plan to support it at some point in the future, but performance will probably be pretty poor, without support for extended attributes or inotify in NFS. I haven't seen it mentioned yet, but I was wondering if I could do do the indexing on the NFS server, and then have the searches be done on the client machines? This might be possible with the experimental network backend, but this isn't something that has been addressed. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
