Beagle Support and Installation help

[ikshaar]

I have tried Beagle few times already, and I never find it that good. My main problem is the fact that it cannot work on partial words. SO unless you type the exact name of your file, it won't find it...

So the ability to search inside is great but for me 90% of the time, a simple "locate" will do a much better job to find my files...

My question is - is it a problem which can be address or is it a design flaw that will make Beagle just another search tool instead of THE search tool ?

[fuoco]

That is something that annoyed me too in fact. I assume it must be possible to do this. i guess one problem is that the database for beagle is much bigger than for slocate, and for a partial word it will return tons of non-relevant results...

[ikshaar]

I thought so too at first but Beagle scan already all text documents. So adding the filename cut at 3, 4, 5, etc.. letters long won't be a large relative increase.

[EDIT] I guess I am not the only one it bothers...
http://bugzilla.gnome.org/show_bug.cgi?id=332673

[bfkeats]

I decided to give beagle a try again. I ~86'd everything I needed to install beagle, but I'm getting the following error when I run beagled.

Code: Select all

** (/usr/local/lib/beagle/BeagleDaemon.exe:12766): WARNING **: The following assembly referenced from /usr/local/lib/beagle/BeagleDaemon.exe could not be loaded:
     Assembly:   dbus-sharp    (assemblyref_index=4)
     Version:    0.23.0.0
     Public Key: 9eef2692033670f5
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/local/lib/beagle).


** (/usr/local/lib/beagle/BeagleDaemon.exe:12766): WARNING **: The class DBus.DBusException could not be loaded, used in dbus-sharp, Version=0.23.0.0, Culture=neutral, PublicKeyToken=9eef2692033670f5

=================================================================
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:


Native stacktrace:

        mono-beagled(mono_handle_native_sigsegv+0xbb) [0x815224b]
        mono-beagled [0x813eae9]
        [0xffffe440]
        mono-beagled(mono_compile_create_var+0x55) [0x811b2c5]
        mono-beagled [0x813cbbc]
        mono-beagled [0x812053b]
        mono-beagled [0x813e955]
        mono-beagled(mono_runtime_exec_main+0x121) [0x80d2791]
        mono-beagled(mono_runtime_run_main+0x1ce) [0x80d29ce]
        mono-beagled(mono_main+0xf3d) [0x805d99d]
        mono-beagled [0x805c5ae]
        /lib/tls/libc.so.6(__libc_start_main+0xe1) [0xb7d84f21]
        mono-beagled [0x805c4f1]

By the way I'm running KDE, not gnome. Any clues?

[ikshaar]

Are you sure you install Beagle with portage ? beagle is not installed in /usr/local/ by the ebuild... but in /usr/lib/

If you tried before you might have some remain of a manual testing still installled. Try to clean up what you installed by hand if anything. Reinstall beagle and look where it install.

[bfkeats]

Thanks, removed /usr/local/bin/beagled and /usr/local/lib/beagle and it seems to work fine.

What is the standard way to start beagle on login since there's no init script? Put a script in ~/.kde/Autostart?

Also, can beagle be used to crawl my entire harddrive, not just home?

EDIT: Actually had to remove /usr/local/bin/beagle-* aswell.

[thomasvk]

I got a few stupid questions regarding beagle...

1) What's the use of the /etc/beagle/crawl-* files? Can I just set the CRAWL_ENABLE to "yes" to have them index what it says (for example 'applications' and 'portage')?
2) I have all my data on network shares (cifs) and want them indexed. I thought I'd do that with 'beagle-build-index' but that command doesn't exist. What's the newer method? Also, how can I do this periodically? I reckon I need to set a cronjob.
3) How do I automatically activate beagle indexing? Will my Gnome/KDE do that or do I need to set something up? There's no '/etc/init.d/beagled' or something similar.

[bfkeats]

3) How do I automatically activate beagle indexing? Will my Gnome/KDE do that or do I need to set something up? There's no '/etc/init.d/beagled' or something similar.

I put the following script in ~/.kde/Autostart/

Code: Select all

#!/bin/bash
beagled &

[fuoco]

I don't know what's going on, but for some time now beagled is trigering a kernel oops on my system in reiserfs xattr functions. This is really annoying.

[thomasvk]

I put the following script in ~/.kde/Autostart/

Code: Select all

#!/bin/bash
beagled &

Thanks for you suggestion! That indeed seems the correct way to do it. I found this on the Beagle website:

Autostarting the Beagle Daemon

You'll probably want to set the beagle daemon to be executed when your desktop environment loads. Note that its best to do it this way rather than loading it on bootup, as beagle likes to be able to connect to an X server to determine if the screensaver is running (beagle will index your files faster when it detects the system is not in use).

GNOME users can do this by clicking on the Desktop menu, going to Preferences, then Sessions. In the Sessions dialog, choose the Startup Programs tab, and add an entry which executes beagled.

So I did, and it works very fine. Beagle runs and searching works!

Now what remains are the following two questions:

I got a few stupid questions regarding beagle...

1) What's the use of the /etc/beagle/crawl-* files? Can I just set the CRAWL_ENABLE to "yes" to have them index what it says (for example 'applications' and 'portage')?
2) I have all my data on network shares (cifs) and want them indexed. I thought I'd do that with 'beagle-build-index' but that command doesn't exist. What's the newer method? Also, how can I do this periodically? I reckon I need to set a cronjob.

[mixnic]

Hi all,

Well I emerged the stable beagle and it's a beaut, I've got aim logs, webpages, email, documents, all indexed. Freaking sweet, and fast to boot (I'm not even sure if I'm inotifying and I'm still happy with performance).

The one issue is wrt evolution and gnome mime types: When double clicking on an email in beagle, I get the following error:

Error while Opening folder
email://1139305938.5482.0@hank/INBOX;uid=785.

No provider available for protocol `email'

I've added the /desktop/gnome/url-handlers/email entry to gconf with the command evolution "%s", with no effect. Anyone else have stable beagle playing nice with evolution, or experience with evolution/gnome mime issues?

Thanks -

[genus]

When beagle activates the videofilter mplayer sucks up all my system memory and gets killed. Any way to disable the videofilter?

[slashseed]

I'm using ext3, and i build my kernel with extended attributes support , but now when i start beagled it ,shows me waring that extended attributes is not enabled, why ?

Code: Select all

~ > beagled --fg --debug
Debug: Starting Beagle Daemon (version 0.2.9)
Debug: Running on Mono 1.1.17.1
Debug: Command Line: /usr/lib/beagle/BeagleDaemon.exe --fg --debug
Warn: Extended attributes are not supported on this filesystem.  Performance will suffer as a result.
Debug: Established a connection to the X server
Debug: Loading Beagle.Util.Conf+IndexingConfig from indexing.xml
Debug: Loading Beagle.Util.Conf+DaemonConfig from daemon.xml
Debug: Loading Beagle.Util.Conf+SearchingConfig from searching.xml
Debug: Loading Beagle.Util.Conf+NetworkingConfig from networking.xml
Debug: Loading Beagle.Util.Conf+WebServicesConfig from webservices.xml
Debug: Starting main loop
Debug: Beginning main loop
Debug: Starting messaging server
.......................

my mount info , u can see the xattr option

Code: Select all

/dev/hda9 on / type ext3 (rw,noatime,user_xattr)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec)
udev on /dev type tmpfs (rw,nosuid)
devpts on /dev/pts type devpts (rw,nosuid,noexec)
/dev/hda8 on /home type ext3 (rw,noatime,user_xattr)
/dev/hda5 on /mnt/d type fuse (rw,nosuid,nodev,noatime,allow_other)
shm on /dev/shm type tmpfs (rw,noexec,nosuid,nodev)
usbfs on /proc/bus/usb type usbfs (rw,noexec,nosuid,devmode=0664,devgid=85)

and my emerge info

Code: Select all

Portage 2.1.2_pre2-r1 (default-linux/x86/2006.1/desktop, gcc-4.1.1, glibc-2.4-r3, 2.6.18-gentoo i686)
=================================================================
System uname: 2.6.18-gentoo i686 Intel(R) Pentium(R) M processor 2.00GHz
Gentoo Base System version 1.12.4
Last Sync: Mon, 02 Oct 2006 18:00:01 +0000
ccache version 2.4 [enabled]
app-admin/eselect-compiler: [Not Present]
dev-java/java-config: 1.3.5-r1, 2.0.27-r1
dev-lang/python:     2.4.3-r3
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     2.4-r2
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.18.1
sys-devel/autoconf:  2.13, 2.60
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2
sys-devel/binutils:  2.17
sys-devel/gcc-config: 1.3.13-r3
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.17
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O3 -march=pentium-m -pipe -mmmx -msse -msse2 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/splash /etc/terminfo /etc/texmf/web2c"
CXXFLAGS="-O3 -march=pentium-m -pipe -mmmx -msse -msse2 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig ccache distlocks metadata-transfer sandbox sfperms strict"
GENTOO_MIRRORS="http://gentoo.channelx.biz"
LANG="en_US.UTF-8"
LINGUAS="zh_CN"
MAKEOPTS="-j16"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage /usr/local/portage/layman/gnome-experimental /usr/local/portage/layman/portage-xgl"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 X aac acpi alsa arts avi bash-completion berkdb bitmap-fonts cairo cdr chardet cjk cli crypt dbus dlloader doc dri dvd dvdr eds elibc_glibc emacs emboss encode esd fam ffmpeg firefox fontconfig fortran gdbm gif glut gnome gpm gstreamer gtk gtk2 hal input_devices_joystick input_devices_keyboard input_devices_mouse isdnlog java joystick jpeg kde kernel_linux kqemu ldap libg++ linguas_zh_CN logitech-mouse mad matroska mikmod mmx motif mp3 mpeg ncurses nls nptl nptlonly nsplugin ogg opengl oss pam pcre perl png ppds pppd python qt3 qt4 quicktime readline reflection samba sdl session spell spl sse sse2 ssl tcpd truetype truetype-fonts type1-fonts udev unicode userland_GNU video_cards_fglrx vorbis win32codecs wma xcomposite xine xml xml2 xorg xscreensaver xv xvid zlib"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS

anyone can helps me ?

[m4rl0n]

How I can activate Beagle web service?

Emerge beagle using:

Code: Select all

USE="webservices" emerge app-misc/beagle

Code: Select all

beagled --fg --debug

but webservice doesnt start:

Debug: Starting Beagle Daemon (version 0.2.7)
Debug: Running on Mono 1.1.13.6
Debug: Command Line: /usr/lib64/beagle/BeagleDaemon.exe --fg --debug
Debug: Established a connection to the X server
Debug: Starting main loop
Debug: Starting messaging server
Debug: Starting QueryDriver
Debug: Loading Beagle.Util.Conf+WebServicesConfig from webservices.xml
Debug: Found index helper at /usr/lib64/beagle/beagled-index-helper
Debug: Guessing for location of KMail folders ... found at /home/marlon/.kde3.5/share/apps/kmail/mail
Debug: Starting Inotify Backend
Debug: KonqCacheDir: /var/tmp/kdecache-marlon/http
Error: Caught exception while trying to parse Kopete contact list: Document element did not appear. file:///home/marlon/.kde/share/apps/kopete/contactlist.xml Line 1, position 1.
Debug: Found 10 backends in /usr/lib64/beagle/BeagleDaemonLib.dll
Debug: Reading mapping from filters
Debug: Loading system static indexes.
Debug: Found 0 system-wide indexes.
Debug: Loading user-configured static indexes.
Debug: Found 0 user-configured static indexes..
Debug: Waiting 60 seconds before starting queryables
Debug: Starting Scheduler thread
Debug: Starting Inotify threads
Debug: Daemon initialization finished after .51s

Code: Select all

netstat -nat | grep LISTEN
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:631             0.0.0.0:*               LISTEN

any idea?

Regards,

Marlon

[m4rl0n]

Code: Select all

beagled --web-start

doesnt work too.

[thomasvk]

It builds the indexes from /etc/beagle/crawl-* but when I search I don't get any results from there, but when I start beagled --fg --debug I do get:

Code: Select all

...
Debug: Loading system static indexes.
Debug: Initializing static queryable: /var/lib/cache/beagle/indexes/applications
Debug: Initializing static queryable: /var/lib/cache/beagle/indexes/documentation
Debug: Initializing static queryable: /var/lib/cache/beagle/indexes/portage
Debug: Found 3 system-wide indexes.
...

Is there any information about how this should work?

[manouchk]

I compiled beagle only with python support and does not seem to be aware of anything on my home!

I try to add some flags but then it needs all gnom and GTK+ or something else stuff. Is that needed to run beagle. What is the minimum flag so that to have good features. I plan tu use kerry because I have KDE installed here. What do you think?

[golding]

EDIT
Anybody??

----------
I have been having troubles with my home partition filling up for some reason.
I checked every dir and when checking the .beagle dir I found the ToIndex sub-dir is 3.5GB with about 240 thousand html files in it.

I tried deleting the files as user, then as root, with both I get this error

Code: Select all

one rob # rm /home/rob/ .beagle/ToIndex/*
bash: /usr/bin/rm: Argument list too long

I have tried to delete portions of around a thousand files a time in about five different file managers, but each block took nearly twenty minutes each to be deleted, didn't matter which FM I was using, still took this amount of time. I then tried around two hundred or so in each block, but it still took nearly ten minutes for each block.

My question,
Is there a way to LIMIT the cache sizes in Beagle/Search? As far as I am concerned anything over a hundred MB is too large, and that is really too large as well, however there is a lot of data to contain in the indexing cache, so I would live with that if needed.

I have not looked in the system beagle cache yet, too afraid of what I may find regarding total size.

As I do no video or music encoding I find no reason to increase the amount of disk space I have, one of the points I am able to promote to others is the fact Linux does not bloat, however, if this continues with Beagle, I may need to emerge -C. Pity, it is one hell of an indexing tool.

BTW
I tried extensive searches within these forums and found no joy

[manouchk]

I'm not an expert of beagle because it does not seem to work fine here but okay you may try (be extremelly carefull!!)
rm -Rf /home/rob/.beagle/ToIndex

Be carefull! On your example, it looks like there is a space between /home/rob/ and .beagle/ToIndex/* which could lead to problems...

I guess deleting with rm should be faster than most filemanager

other solutions :
cd /home/rob/.beagle/ToIndex
for file in * ; do rm $file; done

in fact :
for file in * ; do rm -f $file; done

or something

you could also try some combination between ls and xargs
....

For the size limit I didn't found anything rapidly but I think you can exclude some directories of begle searches, not shure because does not work yet here

[thomasvk]

for file in * won't work either because then it goes expanding it in the same way and doesn't want so much files. I'd try to delete the directory with -rf or perhaps a file manager like midnight commander. Or write a little script that deletes per begining char (with some for loop from a-z deleting a* b*, etc).

for letter in [a-z]; do rm $letter*; done
(Note: I don't know if this will work, I'm not really what one can call an expect bash scripter!)

[golding]

rm -Rf /home/rob/.beagle/ToIndex

for file in * won't work either because then it goes expanding it in the same way and doesn't want so much files. I'd try to delete the directory with -rf

I am SUCH an IDIOT !!

Of course you would just delete the entire directory ... I was trying to delete the files from within the directory instead, that's why the the error came back about args, the argument list was too long when it's in the hundred thousands.
I forgot that the star, or whatever variable flag used, translates into a complete list by rm, therefore it gets too long.
When I went and deleted the directory, the argument has a list of one, the directory itself.

Thankyou mates, very appreciated

[Rikz]

I'm using ext3, and i build my kernel with extended attributes support , but now when i start beagled it ,shows me waring that extended attributes is not enabled, why ?
...

I've got the same problem.
My FS is ext3 too and mount options seem to be right.
I've googled for some time and all that I've found is a advise (for Mandriva user) to install libxattr package.
sys-apps/attr from portage sounds similar, but after installing it, nothing changed.

Somebody, please, help us

[maartenstorm]

I searched the forums and couldn't find a solution for this error compiling beagle

Code: Select all

config.status: executing po/stamp-it commands

        Beagle Version:           0.2.13
        Target OS:                linux
        inotify?                  yes

        Prefix:                   /usr
        GNOME Prefix:             /usr
        KDE Prefix:               /usr/kde/3.5

        Evolution support?        no (missing dependencies)
        gsf-sharp?                yes
        wv1?                      no
        galago-sharp?             no
        libchm?                   no
        google backend?           no (Unsupported)
        Thunderbird backend?      no

        Mozilla Extension?        yes
        Epiphany Extension?       no (Epiphany not installed)

        Local SqliteClient?       yes
        Sqlite version:           3.x

        Enable libbeagle          yes
        Enable python bindings    yes
        Monitor screensaver       yes

        Enable beagle-search GUI  no
        Enable "Open With" menu   yes


make  all-recursive
make[1]: Entering directory `/var/tmp/portage/beagle-0.2.13/work/beagle-0.2.13'
Making all in po
make[2]: Entering directory `/var/tmp/portage/beagle-0.2.13/work/beagle-0.2.13/po'
make[2]: *** No rule to make target `@ALL_LINGUAS@.gmo', needed by `all-yes'.  Stop.
make[2]: Leaving directory `/var/tmp/portage/beagle-0.2.13/work/beagle-0.2.13/po'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/beagle-0.2.13/work/beagle-0.2.13'
make: *** [all] Error 2

!!! ERROR: app-misc/beagle-0.2.13 failed.
Call stack:
  ebuild.sh, line 1546:   Called dyn_compile
  ebuild.sh, line 937:   Called src_compile
  beagle-0.2.13.ebuild, line 108:   Called die

!!! Make failed
!!! If you need support, post the topmost build error, and the call stack if relevant.

Can someone help me with this?
Thanks

[charlesnadeau]

I am trying to emerge Beagle but I have a problem with dbus while emerging evolution-data-server, a beagle dependency.
The error message is:

Code: Select all

gtk-doc: Linking scanner
i686-pc-linux-gnu-gcc -march=pentium3 -O3 -msse -fomit-frame-pointer -Wall -Wmissing-prototypes -Wno-sign-compare -o .libs/libebook-scan .libs/libebook-scan.o -pthread  ../../../../addressbook/libebook/.libs/libebook-1.2.so -L/usr/lib /var/tmp/portage/gnome-extra/evolution-data-server-1.8.2/work/evolution-data-server-1.8.2/camel/.libs/libcamel-1.2.so -L/usr/lib/nspr -L/usr/lib/lib -L/usr/lib/nss -lssl3 -lsmime3 -lnss3 -lsoftokn3 /var/tmp/portage/gnome-extra/evolution-data-server-1.8.2/work/evolution-data-server-1.8.2/libedataserver/.libs/libedataserver-1.2.so -lplc4 -lplds4 -lnspr4 -ldb /usr/lib/libgnome-2.so /usr/lib/libesd.so /usr/lib/libaudiofile.so /usr/lib/libasound.so /usr/lib/libbonobo-2.so /usr/lib/libbonobo-activation.so /usr/lib/libORBitCosNaming-2.so /usr/lib/libgnomevfs-2.so /usr/lib/libxml2.so -lz /usr/lib/libdbus-glib-1.so /usr/lib/libdbus-1.so -lnsl -lssl -lcrypto -lresolv -lutil /usr/lib/libgconf-2.so /usr/lib/libpopt.so /usr/lib/libORBit-2.so /usr/lib/libgobject-2.0.so -lm /usr/lib/libgmodule-2.0.so -ldl /usr/lib/libgthread-2.0.so -lpthread /usr/lib/libglib-2.0.so -lrt
/usr/lib/gcc/i686-pc-linux-gnu/4.1.1/../../../../i686-pc-linux-gnu/bin/ld: warning: libdbus-1.so.2, needed by /usr/lib/libgnomevfs-2.so, not found (try using -rpath or -rpath-link)
creating libebook-scan
gtk-doc: Running scanner libebook-scan
/var/tmp/portage/gnome-extra/evolution-data-server-1.8.2/work/evolution-data-server-1.8.2/docs/reference/addressbook/libebook/.libs/lt-libebook-scan: error while loading shared libraries: libdbus-1.so.2: cannot open shared object file: No such file or directory
Scan failed:
make[5]: *** [scan-build.stamp] Error 127
make[5]: Leaving directory `/var/tmp/portage/gnome-extra/evolution-data-server-1.8.2/work/evolution-data-server-1.8.2/docs/reference/addressbook/libebook'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/var/tmp/portage/gnome-extra/evolution-data-server-1.8.2/work/evolution-data-server-1.8.2/docs/reference/addressbook'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/var/tmp/portage/gnome-extra/evolution-data-server-1.8.2/work/evolution-data-server-1.8.2/docs/reference'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/gnome-extra/evolution-data-server-1.8.2/work/evolution-data-server-1.8.2/docs'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/gnome-extra/evolution-data-server-1.8.2/work/evolution-data-server-1.8.2'
make: *** [all] Error 2

!!! ERROR: gnome-extra/evolution-data-server-1.8.2 failed.
Call stack:
  ebuild.sh, line 1614:   Called dyn_compile
  ebuild.sh, line 971:   Called qa_call 'src_compile'
  environment, line 3645:   Called src_compile
  evolution-data-server-1.8.2.ebuild, line 141:   Called gnome2_src_compile
  gnome2.eclass, line 71:   Called die

!!! compile failure
!!! If you need support, post the topmost build error, and the call stack if relevant.
!!! A complete build log is located at '/var/log/portage/gnome-extra:evolution-data-server-1.8.2:20070212-025508.log'.

I checked and libdbus-1.so is part of the dbus ebuild and it has been installed:

Code: Select all

*  sys-apps/dbus
      Latest version available: 1.0.2
      Latest version installed: 1.0.2
      Size of files: 1,367 kB
      Homepage:      http://dbus.freedesktop.org/
      Description:   A message bus system, a simple way for applications to talk to each other
      License:       || ( GPL-2 AFL-2.1 )

Do I have the right version? Anything I did wrong? Thanks!

[Mindstab]

To those who needed help with extended attributes: Once the support is in your kernel, you need to mount the releven FSs with extended attributes enabled. Modify your /etc/fstab accordingly adding the user_xattr flag to the options[/b]

Code: Select all

/dev/vg/home            /home           reiserfs        noatime,user_xattr                    2 2

and then remount the filesystem