Re: beagle problem
Oh ... beagle-search explicitly excludes documentation index while searching. The documentation index is used by yelp (gnome help browser). Apparently documentation results in beagle-search was confusing users and so it was blacklisted from general search. I'm now of the mind that we should probably re-enable documentation as a separate category in the search. The UI can handle it reasonably well, whereas Best definitely could not. I tried to enable the search-documentation-by-default in beagle-search but finally had to keep it disabled in 0.3.2 for to two reasons: 1) Documentation results are shown in the Documents category in beagle-search which does not look right. 2) The docbook files have no information about which language they are in. As a result searching for something returns multiple hits for the same documentation, one for each language. And they are all displayed with the same title in beagle-search. E.g. searching for nautilus returned 4 or 5 results titled nautilus - there is no way to know which one of them is the English one without opening them one by one. Unless there is any way to infer the langauage from the docbook xml or the support for deducing language from text is completed, seaching documentation might have to remain disabled by default. However, I added a --search-docs option to beagle-search which will turn on searching the documentation index. By default, its turned off. - dBera -- - Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem
On Tue, 18 Dec 2007 22:03:37 -0500
Debajyoti Bera [EMAIL PROTECTED] wrote:
Remove the earlier changes and instead do the following:
Just before the first (line 550)
if (beagle_client != NULL) {
add this,
if (beagle_client == NULL)
beagle_client = beagle_client_new (NULL);
So it will look like:
#ifdef ENABLE_BEAGLE
if (beagle_client == NULL)
beagle_client = beagle_client_new (NULL);
if (beagle_client != NULL) {
query = beagle_query_new (); ... etc.
Hello,
I made that changes, but now yelp dies with a Segmentation fault
error message when I start a search. Thank you very much for your help,
but I'll wait for upstream to adapt yelp to the new beagle version.
I'm going to report a wishlist bug for Hardy in Launchpad, they still
have the 0.2.18 version in the repos.
Regards.
--
***
* Giuseppe Borzi, Assistant Professor at the *
* University of Messina - Department of Civil Engineering *
* Address: Contrada di Dio, Messina, I-98166, Italy *
* Tel: +390903977323 *
* Fax: +390903977480 *
* email: [EMAIL PROTECTED]*
* url: http://www.webalice.it/gborzi1 *
***
signature.asc
Description: PGP signature
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem
On Tue, 18 Dec 2007 16:48:28 -0500 D Bera [EMAIL PROTECTED] wrote: I modified the yelp code in yelp-search-parser.c using beagle_client_new(NULL) instead of NULL in the if clauses that check beagle_client. Now yelp finds beagled but when I search for something I don't get any result and this error message ** (yelp:19374): CRITICAL **: beagle_client_send_request_async: assertion `BEAGLE_IS_CLIENT (client)' failed Can you send me the changes ? I might be able to spot the problem. Of course, it's a small patch, I changed only 3 lines. Please note that I have modified yelp version 2.20.0. -- *** * Giuseppe Borzi, Assistant Professor at the * * University of Messina - Department of Civil Engineering * * Address: Contrada di Dio, Messina, I-98166, Italy * * Tel: +390903977323 * * Fax: +390903977480 * * email: [EMAIL PROTECTED]* * url: http://www.webalice.it/gborzi1 * *** yelp-search-parser.c.patch.gz Description: GNU Zip compressed data signature.asc Description: PGP signature ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem
On Fri, 14 Dec 2007 21:07:58 -0500 Debajyoti Bera [EMAIL PROTECTED] wrote: noticed that yelp is not able to use beagle daemon, when a search is launched it warns: (yelp:11000): Yelp-WARNING **: beagled not running, using basic search support. but beagled is running. This happens with beagle 0.3.1 and yelp 2.20.0 under Ubuntu 7.10. This is probably the same issue as libbeagle0 vs libbeagle1. yelp needs to be rebuilt with libbeagle1 [1]. - dBera [1] Some distributions have patched yelp to build with libbeagle1 by commenting out beagle_query_add_source (query, documentation); This is incorrect; the API was removed and should be *replaced* by (as described in http://mail.gnome.org/archives/dashboard-hackers/2007-December/msg4.html): beagle_query_add_text (query, source:documentation); I compiled yelp with the suggested correction, but it still complains that beagled is not running. Perhaps there is something else to change in the yelp's source, but at this point I think it's a task for yelp's developers. -- *** * Giuseppe Borzi, Assistant Professor at the * * University of Messina - Department of Civil Engineering * * Address: Contrada di Dio, Messina, I-98166, Italy * * Tel: +390903977323 * * Fax: +390903977480 * * email: [EMAIL PROTECTED]* * url: http://www.webalice.it/gborzi1 * *** signature.asc Description: PGP signature ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem
(yelp:11000): Yelp-WARNING **: beagled not running, using basic search support. but beagled is running. This happens with beagle 0.3.1 and yelp 2.20.0 under Ubuntu 7.10. This is probably the same issue as libbeagle0 vs libbeagle1. yelp needs to be rebuilt with libbeagle1 [1]. I compiled yelp with the suggested correction, but it still complains that beagled is not running. Perhaps there is something else to change in the yelp's source, but at this point I think it's a task for yelp's developers. Hmm... I tried yelp on gutsy and it was refusing to see the running beagled. Then I tried $ nm -D /usr/bin/yelp | grep beagle_ and it listed a lot of functions but not the crucial one beagle_client_new (which, according to the websvn code, is inside a #ifdef). I have no idea what it means since some of the other functions inside the #ifdef do show up in the symbol list. I suggest filing a bug with yelp. Most likely something is wrong there. - dBera -- - Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem
Hi, On 12/13/07, Debajyoti Bera [EMAIL PROTECTED] wrote: I've made some other test, and I've seen that beagle-search does find files in the applications static index, but fails in the documentation static index. beagle-query and nautilus work fine. Oh ... beagle-search explicitly excludes documentation index while searching. The documentation index is used by yelp (gnome help browser). Apparently documentation results in beagle-search was confusing users and so it was blacklisted from general search. I'm now of the mind that we should probably re-enable documentation as a separate category in the search. The UI can handle it reasonably well, whereas Best definitely could not. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem
Oh ... beagle-search explicitly excludes documentation index while searching. The documentation index is used by yelp (gnome help browser). Apparently documentation results in beagle-search was confusing users and so it was blacklisted from general search. I'm now of the mind that we should probably re-enable documentation as a separate category in the search. The UI can handle it reasonably well, whereas Best definitely could not. Ok. I filed a bug to track the progress. Up for grabs, http://bugzilla.gnome.org/show_bug.cgi?id=503629 - dBera -- - Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem
On Fri, 14 Dec 2007 12:00:12 -0500 Joe Shaw [EMAIL PROTECTED] wrote: Hi, Oh ... beagle-search explicitly excludes documentation index while searching. The documentation index is used by yelp (gnome help browser). Apparently documentation results in beagle-search was confusing users and so it was blacklisted from general search. I'm now of the mind that we should probably re-enable documentation as a separate category in the search. The UI can handle it reasonably well, whereas Best definitely could not. Joe Just a suggestion, you can make it optional for users, i.e. if someone finds the Documentation results confusing can disable them. I've noticed that yelp is not able to use beagle daemon, when a search is launched it warns: (yelp:11000): Yelp-WARNING **: beagled not running, using basic search support. but beagled is running. This happens with beagle 0.3.1 and yelp 2.20.0 under Ubuntu 7.10. Regards. -- *** * Giuseppe Borzi, Assistant Professor at the * * University of Messina - Department of Civil Engineering * * Address: Contrada di Dio, Messina, I-98166, Italy * * Tel: +390903977323 * * Fax: +390903977480 * * email: [EMAIL PROTECTED]* * url: http://www.webalice.it/gborzi1 * *** signature.asc Description: PGP signature ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem
noticed that yelp is not able to use beagle daemon, when a search is launched it warns: (yelp:11000): Yelp-WARNING **: beagled not running, using basic search support. but beagled is running. This happens with beagle 0.3.1 and yelp 2.20.0 under Ubuntu 7.10. This is probably the same issue as libbeagle0 vs libbeagle1. yelp needs to be rebuilt with libbeagle1 [1]. - dBera [1] Some distributions have patched yelp to build with libbeagle1 by commenting out beagle_query_add_source (query, documentation); This is incorrect; the API was removed and should be *replaced* by (as described in http://mail.gnome.org/archives/dashboard-hackers/2007-December/msg4.html): beagle_query_add_text (query, source:documentation); -- - Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
beagle problem
Sorry for sending again this mail, my email address at ieee.org is only an alias for the address at gmail.com. Hello to everyone, I have beagle 0.3.1 installed on Ubuntu 7.10 Gutsy. Gutsy comes with beagle and libbeagle 0.2.18 in the repositories, so I made my own packages for the newest version, installed them and created the indexes, including the static ones. However some other programs (nautilus and beaglefs) depend on libbeagle0 (i.e. the 0.2.18 version of the library) so I left this package installed and didn't install libbeagle1 (the name I gave to the package for the 0.3.0 version of the library). I have noticed some problems with the searches: beagle-search only finds files in my home directory, while nautilus finds files in my home directory *and* those listed in the static indexes. beagle-search seems to ignore the static indexes, although these are listed by beagle-index-info. Another problem is related to beaglefs that doesn't work at all. When I run it with this command: beaglefs -d Figaro /home/my home dir/gb it gives the following output unique: 1, opcode: INIT (26), nodeid: 0, insize: 56 INIT: 7.8 flags=0x0003 max_readahead=0x0002 INIT: 7.8 flags=0x max_readahead=0x0002 max_write=0x0002 unique: 1, error: 0 (Success), outsize: 40 ** (process:22088): WARNING **: could not handle IsPersistent ** (process:22088): WARNING **: could not handle IsPersistent repeat this line many times ** (process:22088): WARNING **: could not handle IsPersistent ** CRITICAL **: beagle_inode_new: assertion `mime_type *mime_type != '\0'' failed aborting... and doing an ls of the /home/my home dir/gb returns ls: /home/my home dir/gb: Transport endpoint is not connected Please note that fuse is correctly installed and configured, in fact I can use encfs. What is wrong in my setup of beagle? Regards. -- *** * Giuseppe Borzi, Assistant Professor at the * * University of Messina - Department of Civil Engineering * * Address: Contrada di Dio, Messina, I-98166, Italy * * Tel: +390903977323 * * Fax: +390903977480 * * email: [EMAIL PROTECTED]* * url: http://www.webalice.it/gborzi1 * *** signature.asc Description: PGP signature ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem
However some other programs (nautilus and beaglefs) depend on libbeagle0 (i.e. the 0.2.18 version of the library) so I left this package installed and didn't install libbeagle1 (the name I gave to the package for the 0.3.0 version of the library). I have noticed some problems with the searches: beagle-search only finds files in my home directory, while nautilus finds files in my home directory *and* those listed in the static indexes. beagle-search seems to ignore the static indexes, although these are listed by beagle-index-info. Thats pretty weird! Are you sure about this ? What happens when you query using beagle-query ? Do a $ tailf -f ~/.beagle/Log/current-Beagle, then start a query in beagle-search - what gets printed in current-Beagle ? Another problem is related to beaglefs that doesn't work at all. When I run it with this command: libbeagle1 is needed for beagle-0.3.x. libbeagle0 might work in some cases but not guaranteed. - dBera -- - Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem
On Thu, 13 Dec 2007 18:33:44 -0500 Debajyoti Bera [EMAIL PROTECTED] wrote: However some other programs (nautilus and beaglefs) depend on libbeagle0 (i.e. the 0.2.18 version of the library) so I left this package installed and didn't install libbeagle1 (the name I gave to the package for the 0.3.0 version of the library). I have noticed some problems with the searches: beagle-search only finds files in my home directory, while nautilus finds files in my home directory *and* those listed in the static indexes. beagle-search seems to ignore the static indexes, although these are listed by beagle-index-info. Thats pretty weird! Are you sure about this ? What happens when you query using beagle-query ? Do a $ tailf -f ~/.beagle/Log/current-Beagle, then start a query in beagle-search - what gets printed in current-Beagle ? This is the output of searching for gfortran that is in the static indexes (6 hits) and in my homedir (4 hits). I searched with both beagle and nautilus. 20071214 01:09:56.3106 05816 Beagle DEBUG: Parsed query 'gfortran' as text_query 20071214 01:09:56.3111 05816 Beagle DEBUG EX: Caught an exception sending Beagle.SearchTermResponse. Shutting down socket. 20071214 01:09:56.3111 05816 Beagle DEBUG EX: System.IO.IOException: Write failure --- System.Net.Sockets.SocketException: The socket has been shut down 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.Net.Sockets.Socket.Send (System.Byte[] buf, Int32 offset, Int32 size, SocketFlags flags) [0x0] 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) [0x0] --- End of inner exception stack trace --- 20071214 01:09:56.3111 05816 Beagle DEBUG EX: 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) [0x0] 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at Beagle.Util.UnclosableStream.Write (System.Byte[] buffer, Int32 offset, Int32 count) [0x0] 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.IO.BufferedStream.Flush () [0x0] 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.IO.StreamWriter.Flush () [0x0] 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.Xml.XmlTextWriter.Flush () [0x0] 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.Xml.Serialization.XmlSerializer.Serialize (System.Xml.XmlWriter writer, System.Object o, System.Xml.Serialization.XmlSerializerNamespaces namespaces) [0x0] 20071214 01:09:56.3184 05816 Beagle DEBUG: Parsed query 'gfortran' as text_query 20071214 01:09:56.3996 05816 Beagle DEBUG EX: Caught an exception sending Beagle.HitsAddedResponse. Shutting down socket. 20071214 01:09:56.3996 05816 Beagle DEBUG EX: System.IO.IOException: Write failure --- System.Net.Sockets.SocketException: The socket has been shut down 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.Net.Sockets.Socket.Send (System.Byte[] buf, Int32 offset, Int32 size, SocketFlags flags) [0x0] 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) [0x0] --- End of inner exception stack trace --- 20071214 01:09:56.3996 05816 Beagle DEBUG EX: 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) [0x0] 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at Beagle.Util.UnclosableStream.Write (System.Byte[] buffer, Int32 offset, Int32 count) [0x0] 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.IO.BufferedStream.Flush () [0x0] 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.IO.StreamWriter.Flush () [0x0] 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.Xml.XmlTextWriter.Flush () [0x0] 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.Xml.Serialization.XmlSerializer.Serialize (System.Xml.XmlWriter writer, System.Object o, System.Xml.Serialization.XmlSerializerNamespaces namespaces) [0x0] 20071214 01:10:14.2454 05816 Beagle DEBUG: Parsed query 'gfortran' as text_query Another problem is related to beaglefs that doesn't work at all. When I run it with this command: libbeagle1 is needed for beagle-0.3.x. libbeagle0 might work in some cases but not guaranteed. Ok, I'll try to recompile beaglefs with libbeagle1 and report the result. -- *** * Giuseppe Borzi, Assistant Professor at the * * University of Messina - Department of Civil Engineering * * Address: Contrada di Dio, Messina, I-98166, Italy * * Tel: +390903977323 * * Fax: +390903977480 * * email: [EMAIL PROTECTED]* * url: http://www.webalice.it/gborzi1 *
Re: beagle problem
libbeagle1 is needed for beagle-0.3.x. libbeagle0 might work in some cases but not guaranteed. I tried to compile beaglefs with libbeagle 0.3.0, but it fails because beaglefs sources include some calls to beagle_query_add_hit_type which doesn't seem to be available in the new library version. Possibly this explains why beaglefs doesn't work, but in this case it is a beaglefs bug. -- *** * Giuseppe Borzi, Assistant Professor at the * * University of Messina - Department of Civil Engineering * * Address: Contrada di Dio, Messina, I-98166, Italy * * Tel: +390903977323 * * Fax: +390903977480 * * email: [EMAIL PROTECTED]* * url: http://www.webalice.it/gborzi1 * *** signature.asc Description: PGP signature ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem
However some other programs (nautilus and beaglefs) depend on libbeagle0 (i.e. the 0.2.18 version of the library) so I left this package installed and didn't install libbeagle1 (the name I gave to the package for the 0.3.0 version of the library). I have noticed some problems with the searches: beagle-search only finds files in my home directory, while nautilus finds files in my home directory *and* those listed in the static indexes. beagle-search seems to ignore the static indexes, although these are listed by beagle-index-info. Thats pretty weird! Are you sure about this ? What happens when you query using beagle-query ? Do a $ tailf -f ~/.beagle/Log/current-Beagle, then start a query in beagle-search - what gets printed in current-Beagle ? This is the output of searching for gfortran that is in the static indexes (6 hits) and in my homedir (4 hits). I searched with both beagle and nautilus. 20071214 01:09:56.3106 05816 Beagle DEBUG: Parsed query 'gfortran' as text_query 20071214 01:09:56.3111 05816 Beagle DEBUG EX: Caught an exception sending Beagle.SearchTermResponse. Shutting down socket. 20071214 01:09:56.3111 05816 Beagle DEBUG EX: System.IO.IOException: Write failure --- System.Net.Sockets.SocketException: The socket has been shut down 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.Net.Sockets.Socket.Send (System.Byte[] buf, Int32 offset, Int32 size, SocketFlags flags) [0x0] 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) [0x0] --- End of inner exception stack trace --- 20071214 01:09:56.3111 05816 Beagle DEBUG EX: 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) [0x0] 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at Beagle.Util.UnclosableStream.Write (System.Byte[] buffer, Int32 offset, Int32 count) [0x0] 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.IO.BufferedStream.Flush () [0x0] 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.IO.StreamWriter.Flush () [0x0] 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.Xml.XmlTextWriter.Flush () [0x0] 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.Xml.Serialization.XmlSerializer.Serialize (System.Xml.XmlWriter writer, System.Object o, System.Xml.Serialization.XmlSerializerNamespaces namespaces) [0x0] 20071214 01:09:56.3184 05816 Beagle DEBUG: Parsed query 'gfortran' as text_query 20071214 01:09:56.3996 05816 Beagle DEBUG EX: Caught an exception sending Beagle.HitsAddedResponse. Shutting down socket. 20071214 01:09:56.3996 05816 Beagle DEBUG EX: System.IO.IOException: Write failure --- System.Net.Sockets.SocketException: The socket has been shut down 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.Net.Sockets.Socket.Send (System.Byte[] buf, Int32 offset, Int32 size, SocketFlags flags) [0x0] 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) [0x0] --- End of inner exception stack trace --- 20071214 01:09:56.3996 05816 Beagle DEBUG EX: 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) [0x0] 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at Beagle.Util.UnclosableStream.Write (System.Byte[] buffer, Int32 offset, Int32 count) [0x0] 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.IO.BufferedStream.Flush () [0x0] 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.IO.StreamWriter.Flush () [0x0] 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.Xml.XmlTextWriter.Flush () [0x0] 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.Xml.Serialization.XmlSerializer.Serialize (System.Xml.XmlWriter writer, System.Object o, System.Xml.Serialization.XmlSerializerNamespaces namespaces) [0x0] 20071214 01:10:14.2454 05816 Beagle DEBUG: Parsed query 'gfortran' as text_query It still does not make sense :( I am surprised nautilus actually worked since it uses incompatible libbeagle0, but I am more surprised that nautilus worked and beagle-search did not! You built and installed everything correctly - right ? Do you get all the results when you do $ beagle-query gfortran -- - Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem
On Thu, 13 Dec 2007 19:51:06 -0500 Debajyoti Bera [EMAIL PROTECTED] wrote: However some other programs (nautilus and beaglefs) depend on libbeagle0 (i.e. the 0.2.18 version of the library) so I left this package installed and didn't install libbeagle1 (the name I gave to the package for the 0.3.0 version of the library). I have noticed some problems with the searches: beagle-search only finds files in my home directory, while nautilus finds files in my home directory *and* those listed in the static indexes. beagle-search seems to ignore the static indexes, although these are listed by beagle-index-info. Thats pretty weird! Are you sure about this ? What happens when you query using beagle-query ? Do a $ tailf -f ~/.beagle/Log/current-Beagle, then start a query in beagle-search - what gets printed in current-Beagle ? This is the output of searching for gfortran that is in the static indexes (6 hits) and in my homedir (4 hits). I searched with both beagle and nautilus. It still does not make sense :( I am surprised nautilus actually worked since it uses incompatible libbeagle0, but I am more surprised that nautilus worked and beagle-search did not! You built and installed everything correctly - right ? Do you get all the results when you do $ beagle-query gfortran beagle-query gfortran gives the correct results, i.e. 4 hits in my homedir, 6 in the static indexes and a new one from the webpages, because I have the firefox-beagle extension installed. I think the install is ok, I modified the debian files of the beagle 0.2.18 package, splitting them in two because of the separation of libbeagle from beagle. But if you think it can be useful, I'll uninstall the beagle packages and install from source. I've made some other test, and I've seen that beagle-search does find files in the applications static index, but fails in the documentation static index. beagle-query and nautilus work fine. BTW, beagle-index-info reports the static indexes as Name: windows (I don't have a windows partition) Count: 0 Crawling: False Name: applications Count: 319 Crawling: False Name: documentation Count: 53585 Crawling: False Thanks for helping me so fast! -- *** * Giuseppe Borzi, Assistant Professor at the * * University of Messina - Department of Civil Engineering * * Address: Contrada di Dio, Messina, I-98166, Italy * * Tel: +390903977323 * * Fax: +390903977480 * * email: [EMAIL PROTECTED]* * url: http://www.webalice.it/gborzi1 * *** signature.asc Description: PGP signature ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem
I've made some other test, and I've seen that beagle-search does find files in the applications static index, but fails in the documentation static index. beagle-query and nautilus work fine. Oh ... beagle-search explicitly excludes documentation index while searching. The documentation index is used by yelp (gnome help browser). Apparently documentation results in beagle-search was confusing users and so it was blacklisted from general search. - dBera -- - Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem
On Thu, 13 Dec 2007 20:30:29 -0500 Debajyoti Bera [EMAIL PROTECTED] wrote: I've made some other test, and I've seen that beagle-search does find files in the applications static index, but fails in the documentation static index. beagle-query and nautilus work fine. Oh ... beagle-search explicitly excludes documentation index while searching. The documentation index is used by yelp (gnome help browser). Apparently documentation results in beagle-search was confusing users and so it was blacklisted from general search. - dBera Thanks for the explanation and I'm sorry for wasting your tim. I didn't know this feature of beagle and got confused :-) . -- *** * Giuseppe Borzi, Assistant Professor at the * * University of Messina - Department of Civil Engineering * * Address: Contrada di Dio, Messina, I-98166, Italy * * Tel: +390903977323 * * Fax: +390903977480 * * email: [EMAIL PROTECTED]* * url: http://www.webalice.it/gborzi1 * *** signature.asc Description: PGP signature ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem with indexing pdf files
ps aux | grep pstotext doesn't show the filename? thanks, simply didn't knew about this command. jan ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem with indexing pdf files
On Tue, Apr 25, 2006 at 02:12:29PM -0400, D Bera wrote: On Mon, 2006-04-24 at 21:11 +0200, Jan Falkenhagen wrote: i've got a problem with beagle indexing pdf documents. Sometimes pdf indexing causes very high cpu and memory consumption of the pdftotext process (1.5 GB of RAM). however i guess that this occurs only with some broken pdf files. is there any simple way to track down this behaviour to the files that are causing this problem? This is a bug in the xpdf software (from which pdftotext comes), and I'd suggest you report a bug to their developers. If you'd like, you can attach a broken PDF to a beagle bug and we can see what we can do to work around it. Or if someone wants to write a managed PDF parser (in C#), that would be cool too :). There are some C# pdf libraries out there that can be used e.g. itextsharp (its under LGPL, is that compatible with beagle licensing ?) Or poppler-sharp. -- Tomasz Torcz RIP is irrevelant. Spoofing is futile. [EMAIL PROTECTED] Your routes will be aggreggated. -- Alex Yuriev pgpkIbsMl5fJM.pgp Description: PGP signature ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem with indexing pdf files
Hi, On Wed, 2006-04-26 at 18:53 +0200, Tomasz Torcz wrote: On Tue, Apr 25, 2006 at 02:12:29PM -0400, D Bera wrote: Or if someone wants to write a managed PDF parser (in C#), that would be cool too :). There are some C# pdf libraries out there that can be used e.g. itextsharp (its under LGPL, is that compatible with beagle licensing ?) Or poppler-sharp. Poppler is GPL so unfortunately it can't be used (in process, anyway) in Beagle. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem with indexing pdf files
On Mon, 2006-04-24 at 21:11 +0200, Jan Falkenhagen wrote: i've got a problem with beagle indexing pdf documents. Sometimes pdf indexing causes very high cpu and memory consumption of the pdftotext process (1.5 GB of RAM). however i guess that this occurs only with some broken pdf files. is there any simple way to track down this behaviour to the files that are causing this problem? This is a bug in the xpdf software (from which pdftotext comes), and I'd suggest you report a bug to their developers. If you'd like, you can attach a broken PDF to a beagle bug and we can see what we can do to work around it. Or if someone wants to write a managed PDF parser (in C#), that would be cool too :). There are some C# pdf libraries out there that can be used e.g. itextsharp (its under LGPL, is that compatible with beagle licensing ?) http://itextsharp.sourceforge.net/ -- - Debajyoti Bera @ http://dbera.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem with indexing pdf files
hi This is a bug in the xpdf software (from which pdftotext comes), and I'd suggest you report a bug to their developers. well thats certainly true, but my problem is that i don't know which pdffiles are damaged because beagle-status doesn't show this kind of information and when im trying to use beagled --fg --debug in this case the log fills with millions of errormessages per second (illegal hex string ...) . so i'd really appreciate any help that could help to locate the problem as a first step. If you'd like, you can attach a broken PDF to a beagle bug and we can see what we can do to work around it as is said above, i certainly would if i knew their names ;). regards jan ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem with indexing pdf files
Hi, On Tue, 2006-04-25 at 21:51 +0200, Jan Falkenhagen wrote: well thats certainly true, but my problem is that i don't know which pdffiles are damaged because beagle-status doesn't show this kind of information and when im trying to use beagled --fg --debug in this case the log fills with millions of errormessages per second (illegal hex string ...) . so i'd really appreciate any help that could help to locate the problem as a first step. ps aux | grep pstotext doesn't show the filename? Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem with indexing pdf files
itextsharp cannot do what we need. Some extensive searching has turned up PdfSharp, a lib which shows promise. It can do what we need, but has not undergone and Linux/Mono testing. While the project imports into Monodevelop without issue, building seems to use some Windows build system specific pre-processing stuff. If anyone wants to give it a look and can get a makefile working, then actual implementation of text extraction is pretty easy. Cheers, Kevin Kubasik On 4/25/06, D Bera [EMAIL PROTECTED] wrote: On Mon, 2006-04-24 at 21:11 +0200, Jan Falkenhagen wrote: i've got a problem with beagle indexing pdf documents. Sometimes pdf indexing causes very high cpu and memory consumption of the pdftotext process (1.5 GB of RAM). however i guess that this occurs only with some broken pdf files. is there any simple way to track down this behaviour to the files that are causing this problem? This is a bug in the xpdf software (from which pdftotext comes), and I'd suggest you report a bug to their developers. If you'd like, you can attach a broken PDF to a beagle bug and we can see what we can do to work around it. Or if someone wants to write a managed PDF parser (in C#), that would be cool too :). There are some C# pdf libraries out there that can be used e.g. itextsharp (its under LGPL, is that compatible with beagle licensing ?) http://itextsharp.sourceforge.net/ -- - Debajyoti Bera @ http://dbera.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers -- Cheers, Kevin Kubasik http://blog.kubasik.net/ ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Fedora Core 5 Beagle Problem
beagle-0.2.3-4 running on Fedora Core 5. beagled starts up and runs for a minute or so, belches (with --debug): 20050722T13 is a recurrence instance 20050722T13 is a recurrence instance [EMAIL PROTECTED] has recurrences ** (/usr/lib/beagle/IndexHelper.exe:1051): WARNING **: process_set_current: error looking up process handle 0x Unhandled Exception: System.SystemException: Can't find current process in [0x0002b] (at /usr/src/build/720715-i386/BUILD/mono-1.1.13.4/mcs/class/System/System.Diagnostics/Process.cs:647) System.Diagnostics.Process:GetCurrentProcess () in [0x000bd] (at /usr/src/build/724867-i386/BUILD/beagle-0.2.3/Util/Log.cs:216) Beagle.Util.Log:WriteLine (LogLevel level, System.String format, System.Object[] args, System.Exception ex) in [0x4] (at /usr/src/build/724867-i386/BUILD/beagle-0.2.3/Util/Log.cs:315) Beagle.Util.Log:Error (System.String message, System.Object[] args) in [0x2] (at /usr/src/build/724867-i386/BUILD/beagle-0.2.3/Util/Logger.cs:95) Beagle.Util.Logger:Error (System.String message, System.Object[] args) in [0x0001c] (at /usr/src/build/724867-i386/BUILD/beagle-0.2.3/beagled/IndexHelper/IndexHelper.cs:52) Beagle.IndexHelper.IndexHelperTool:Main (System.String[] args) The bottom block (debug output) is repeated periodically (60 seconds) ad infinitum. Under FC4, I had mono and beagle working, indexing the same homedirectory with no problems. I wiped out ~/.beagle after the problem first cropped up, thinking it may have been an insert plausible explanation here related to old/corrupted data. It didn't help, unfortunately. The beagle logs are all 0 byte, as well. Thoughts? Ideas for further testing? Would an strace help? Thank you for your time, -- Matthew Keller ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Fedora Core 5 Beagle Problem
Hi, On Wed, 2006-03-29 at 10:26 -0500, Matthew Keller wrote: beagle-0.2.3-4 running on Fedora Core 5. beagled starts up and runs for a minute or so, belches (with --debug): ** (/usr/lib/beagle/IndexHelper.exe:1051): WARNING **: process_set_current: error looking up process handle 0x Unhandled Exception: System.SystemException: Can't find current process in [0x0002b] This looks like a Mono bug. Under FC4, I had mono and beagle working, indexing the same homedirectory with no problems. I wiped out ~/.beagle after the problem first cropped up, thinking it may have been an insert plausible explanation here related to old/corrupted data. It didn't help, unfortunately. The beagle logs are all 0 byte, as well. Thoughts? Ideas for further testing? Would an strace help? Can you try shutting down all mono apps and moving your ~/.wapi directory out of the way and try again? If it persists, you may want to file a bug at bugzilla.ximian.com against the mono runtime. They would have a better idea of how to debug it than I would, unfortunately. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Fedora Core 5 Beagle Problem
Joe- Moving .wapi out didn't help so I'll get this into bugzilla. Thanks for your help! On Wed, 2006-03-29 at 12:37 -0500, Joe Shaw wrote: Hi, On Wed, 2006-03-29 at 10:26 -0500, Matthew Keller wrote: beagle-0.2.3-4 running on Fedora Core 5. beagled starts up and runs for a minute or so, belches (with --debug): ** (/usr/lib/beagle/IndexHelper.exe:1051): WARNING **: process_set_current: error looking up process handle 0x Unhandled Exception: System.SystemException: Can't find current process in [0x0002b] This looks like a Mono bug. Under FC4, I had mono and beagle working, indexing the same homedirectory with no problems. I wiped out ~/.beagle after the problem first cropped up, thinking it may have been an insert plausible explanation here related to old/corrupted data. It didn't help, unfortunately. The beagle logs are all 0 byte, as well. Thoughts? Ideas for further testing? Would an strace help? Can you try shutting down all mono apps and moving your ~/.wapi directory out of the way and try again? If it persists, you may want to file a bug at bugzilla.ximian.com against the mono runtime. They would have a better idea of how to debug it than I would, unfortunately. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: compileing beagle, problem in ver 0.0.11.1
Στις 04-07-2005, ημέρα Δευ, και ώρα 07:40 +0300, ο/η regatta έγραψε: Hi Here what I got when I tried to compile beagle , I hope this can help you Making all in Tiles make[2]: Entering directory `/root/beagle-0.0.11.1/Tiles' mcs -debug -out:Tiles.dll -target:library -warn:4 -define:ENABLE_EVO_SHARP ./HitFlavor.cs ./HitToHitFlavor.cs ./SimpleRootTile.cs ./Template.cs ./TileActionAttribute.cs ./Tile.cs ./TileBlog.cs ./TileBugzilla.cs ./TileCalendar.cs ./TileCanvas.cs ./TileContact.cs ./TileDocs.cs ./TileFile.cs ./TileFolder.cs ./TileFromHitTemplate.cs ./TileFromTemplate.cs ./TileGoogle.cs ./TileHitCollection.cs ./TileImLog.cs ./TileLauncher.cs ./TileMailMessage.cs ./TileMonodoc.cs ./TileMusic.cs ./TileNote.cs ./TilePicture.cs ./TilePresentation.cs ./TileRenderContext.cs ./TileSpreadsheet.cs ./TileStyleAttribute.cs ./TileWebHistory.cs -r:/usr/lib/mono/evolution-sharp/evolution-sharp.dll -r:/usr/lib/mono/gtk-sharp/glib-sharp.dll -r:/usr/lib/mono/gtk-sharp/pango-sharp.dll -r:/usr/lib/mono/gtk-sharp/atk-sharp.dll -r:/usr/lib/mono/gtk-sharp/gdk-sharp.dll -r:/usr/lib/mono/gtk-sharp/gtk-sharp.dll -r:/usr/lib/mono/gtk-sharp/glade-sharp.dll -r:/usr/lib/mono/gecko-sharp/gecko-sharp.dll -r:/usr/lib/mono/gtk-sharp/gnome-sharp.dll -r:/usr/lib/mono/gtk-sharp/art-sharp.dll -r:/usr/lib/mono/gtk-sharp/gconf-sharp.dll -r:/usr/lib/mono/gtk-sharp/gconf-sharp-peditors.dll -r:/usr/lib/mono/gmime-sharp/gmime-sharp.dll -r:../Util/Util.dll -r:../images/Images.dll -r:../BeagleClient/Beagle.dll -r:Mono.Posix -resource:./template-page.css,template-page.css -resource:./template-head.html,template-head.html -resource:./template-foot.html,template-foot.html -resource:./template-contact.html,template-contact.html -resource:./template-file.html,template-file.html -resource:./template-folder.html,template-folder.html -resource:./template-google.html,template-google.html -resource:./template-bugzilla.html,template-bugzilla.html -resource:./template-im-log.html,template-im-log.html -resource:./template-mail-message.html,template-mail-message.html -resource:./template-music.html,template-music.html -resource:./template-note.html,template-note.html -resource:./template-picture.html,template-picture.html -resource:./template-web-history.html,template-web-history.html -resource:./template-blog.html,template-blog.html -resource:./template-monodoc.html,template-monodoc.html -resource:./template-docs.html,template-docs.html -resource:./template-presentation.html,template-presentation.html -resource:./template-launcher.html,template-launcher.html -resource:./template-calendar.html,template-calendar.html -resource:./template-spreadsheet.html,template-spreadsheet.html ./TileMailMessage.cs(78) error CS0117: `GMime.InternetAddress' does not contain a definition for `ParseString' Compilation failed: 1 error(s), 0 warnings make[2]: *** [Tiles.dll] Error 1 make[2]: Leaving directory `/root/beagle-0.0.11.1/Tiles' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/beagle-0.0.11.1' make: *** [all] Error 2 --- lnx3w069 beagle-0.0.11.1 # mono --version Mono JIT compiler version 1.1.8.1, (C) 2002-2005 Novell, Inc and Contributors. www.mono-project.com TLS: __thread GC:Included Boehm (with typed GC) SIGSEGV : normal Globalization: normal lnx3w069 beagle-0.0.11.1 # gmime-config --version 2.1.15 Hi, gmime 2.1.15 is only supported in the CVS version of Beagle and not in 0.0.11.1. That is the problem. It has been discussed in this list before. ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
compileing beagle, problem in ver 0.0.11.1
Hi Here what I got when I tried to compile beagle , I hope this can help you Making all in Tiles make[2]: Entering directory `/root/beagle-0.0.11.1/Tiles' mcs -debug -out:Tiles.dll -target:library -warn:4 -define:ENABLE_EVO_SHARP ./HitFlavor.cs ./HitToHitFlavor.cs ./SimpleRootTile.cs ./Template.cs ./TileActionAttribute.cs ./Tile.cs ./TileBlog.cs ./TileBugzilla.cs ./TileCalendar.cs ./TileCanvas.cs ./TileContact.cs ./TileDocs.cs ./TileFile.cs ./TileFolder.cs ./TileFromHitTemplate.cs ./TileFromTemplate.cs ./TileGoogle.cs ./TileHitCollection.cs ./TileImLog.cs ./TileLauncher.cs ./TileMailMessage.cs ./TileMonodoc.cs ./TileMusic.cs ./TileNote.cs ./TilePicture.cs ./TilePresentation.cs ./TileRenderContext.cs ./TileSpreadsheet.cs ./TileStyleAttribute.cs ./TileWebHistory.cs -r:/usr/lib/mono/evolution-sharp/evolution-sharp.dll -r:/usr/lib/mono/gtk-sharp/glib-sharp.dll -r:/usr/lib/mono/gtk-sharp/pango-sharp.dll -r:/usr/lib/mono/gtk-sharp/atk-sharp.dll -r:/usr/lib/mono/gtk-sharp/gdk-sharp.dll -r:/usr/lib/mono/gtk-sharp/gtk-sharp.dll -r:/usr/lib/mono/gtk-sharp/glade-sharp.dll -r:/usr/lib/mono/gecko-sharp/gecko-sharp.dll -r:/usr/lib/mono/gtk-sharp/gnome-sharp.dll -r:/usr/lib/mono/gtk-sharp/art-sharp.dll -r:/usr/lib/mono/gtk-sharp/gconf-sharp.dll -r:/usr/lib/mono/gtk-sharp/gconf-sharp-peditors.dll -r:/usr/lib/mono/gmime-sharp/gmime-sharp.dll -r:../Util/Util.dll -r:../images/Images.dll -r:../BeagleClient/Beagle.dll -r:Mono.Posix -resource:./template-page.css,template-page.css -resource:./template-head.html,template-head.html -resource:./template-foot.html,template-foot.html -resource:./template-contact.html,template-contact.html -resource:./template-file.html,template-file.html -resource:./template-folder.html,template-folder.html -resource:./template-google.html,template-google.html -resource:./template-bugzilla.html,template-bugzilla.html -resource:./template-im-log.html,template-im-log.html -resource:./template-mail-message.html,template-mail-message.html -resource:./template-music.html,template-music.html -resource:./template-note.html,template-note.html -resource:./template-picture.html,template-picture.html -resource:./template-web-history.html,template-web-history.html -resource:./template-blog.html,template-blog.html -resource:./template-monodoc.html,template-monodoc.html -resource:./template-docs.html,template-docs.html -resource:./template-presentation.html,template-presentation.html -resource:./template-launcher.html,template-launcher.html -resource:./template-calendar.html,template-calendar.html -resource:./template-spreadsheet.html,template-spreadsheet.html ./TileMailMessage.cs(78) error CS0117: `GMime.InternetAddress' does not contain a definition for `ParseString' Compilation failed: 1 error(s), 0 warnings make[2]: *** [Tiles.dll] Error 1 make[2]: Leaving directory `/root/beagle-0.0.11.1/Tiles' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/beagle-0.0.11.1' make: *** [all] Error 2 --- lnx3w069 beagle-0.0.11.1 # mono --version Mono JIT compiler version 1.1.8.1, (C) 2002-2005 Novell, Inc and Contributors. www.mono-project.com TLS: __thread GC:Included Boehm (with typed GC) SIGSEGV : normal Globalization: normal lnx3w069 beagle-0.0.11.1 # gmime-config --version 2.1.15 -- Best Regards, -*- If Linux doesn't have the solution, you have the wrong problem -*- ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Beagle problem on Slackware 10.1
I've built and installed Beagle (from CVS 31mar05) on my Slackware 10.1 system. I think I'm getting close, but I still get this type of error message (see below) when I launch the Beagle daemon. Any suggestions would be greatly appreciated. screen output from beagled --fg --debug [EMAIL PROTECTED]:~$ beagled --fg --debug INFO: Starting Beagle Daemon (version 0.0.9) DEBUG: Command Line: /usr/local/lib/beagle/BeagleDaemon.exe --debug --fg DEBUG: Initializing D-BUS DEBUG: Acquiring com.novell.Beagle D-BUS service DEBUG: Found index helper at /usr/local/lib/beagle/beagled-index-helper DEBUG: Launching helper process! DEBUG: D-BUS registered obj=Beagle.IndexHelper.RemoteIndexerImpl path=/com/novell/BeagleIndexHelper/Factory owner=(none) DEBUG: Helper Size: VmRSS=9.4 MB, size=1.00, 0.0% DEBUG: Connecting to com.novell.BeagleIndexHelper DEBUG: Initializing RemoteControl DEBUG: D-BUS registered obj=Beagle.Daemon.RemoteControlImpl path=/com/novell/Beagle/RemoteControl owner=(none) DEBUG: D-BUS registered obj=Beagle.Daemon.FactoryImpl path=/com/novell/Beagle/Factory owner=(none) DEBUG: Starting QueryDriver Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object in 0x0 unknown method in (wrapper managed-to-native) Gtk.Application:gtk_main () in 0x7 Gtk.Application:Run () in 0x002c1 Beagle.IndexHelper.IndexHelperTool:Main (System.String[] args) DEBUG: Starting Inotify Backend DEBUG: Pre-populated UniqueIdStore cache with 1 items in .01s INFO: Loaded 0 records from /home/claw/.beagle/FileSystemIndex/FileAttributesStore.db in 0.000s INFO: Loaded 0 records from /home/claw/.beagle/LauncherIndex/FileAttributesStore.db in 0.000s DEBUG: Found 10 types in BeagleDaemonLib, Version=1.4.3.3, Culture=neutral DEBUG: Adding root /home/claw ioctl: Bad address WARN: Exception caught while executing Beagle.Daemon.FileSystemQueryable.FileSystemQueryable:Void StartWorker() WARN: System.Exception: Attempt to watch /home/claw failed! in 0x00133 Beagle.Util.Inotify:Watch (System.String path, EventType mask, EventType initial_filter) in 0xf Beagle.Util.Inotify:Watch (System.String path, EventType mask) in 0x00023 Beagle.Daemon.FileSystemQueryable.InotifyBackend:WatchDirectories (System.String path) in 0x000ba Beagle.Daemon.FileSystemQueryable.FileSystemModel:ScanOne_Unlocked (Beagle.Daemon.FileSystemQueryable.Directory dir) in 0x000df Beagle.Daemon.FileSystemQueryable.FileSystemModel:ScanAll () in 0xd Beagle.Daemon.FileSystemQueryable.FileSystemQueryable:OnModelNeedsScan (Beagle.Daemon.FileSystemQueryable.FileSystemModel source) in (wrapper delegate-invoke) System.MulticastDelegate:invoke_void_FileSystemModel (Beagle.Daemon.FileSystemQueryable.FileSystemModel) in 0x003ef Beagle.Daemon.FileSystemQueryable.FileSystemModel:AddRoot (System.String path) in 0x00035 Beagle.Daemon.FileSystemQueryable.FileSystemQueryable:StartWorker () in (wrapper delegate-invoke) System.MulticastDelegate:invoke_void () in 0x00018 Beagle.Util.ExceptionHandlingThread:ThreadStarted () ioctl: Bad address WARN: Exception caught while executing Beagle.Daemon.BlamQueryable.BlamQueryable:Void StartWorker() WARN: System.Exception: Attempt to watch /home/claw/.gnome2/blam failed! in 0x00133 Beagle.Util.Inotify:Watch (System.String path, EventType mask, EventType initial_filter) in 0xf Beagle.Util.Inotify:Watch (System.String path, EventType mask) in 0x00077 Beagle.Daemon.BlamQueryable.BlamQueryable:StartWorker () in (wrapper delegate-invoke) System.MulticastDelegate:invoke_void () in 0x00018 Beagle.Util.ExceptionHandlingThread:ThreadStarted () INFO: Starting Evolution mail backend DEBUG: D-BUS registered obj=Beagle.Daemon.WebHistoryQueryable.WebHistoryQueryable+WebHistoryIndexerImpl path=/com/novell/Beagle/WebHistoryIndexer owner=(none) INFO: Starting launcher backend INFO: Scanning Launchers ioctl: Bad address Unhandled Exception: System.Exception: Attempt to watch /usr/share/applications failed! in 0x00133 Beagle.Util.Inotify:Watch (System.String path, EventType mask, EventType initial_filter) in 0xf Beagle.Util.Inotify:Watch (System.String path, EventType mask) in 0x00167 Beagle.Daemon.LauncherQueryable.LauncherQueryable:Watch (System.String path) in 0x00158 Beagle.Daemon.LauncherQueryable.LauncherQueryable:Start () in 0x00016 Beagle.Daemon.Queryable:Start () in 0x0012d Beagle.Daemon.QueryDriver:Start () in 0x00ac6 Beagle.Daemon.BeagleDaemon:Main (System.String[] args) end of screen output ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle problem on Slackware 10.1
On Fri, 2005-04-01 at 11:30 +, Charlie Law wrote: Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object in 0x0 unknown method in (wrapper managed-to-native) Gtk.Application:gtk_main () in 0x7 Gtk.Application:Run () It is hard to say for sure, but that sort of exception usually means that your gtk-sharp is broken. It is probably not a beagle bug. ioctl: Bad address You are using the wrong version of inotify. CVS requires Inotify 0.21. Good luck, -J ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
