Bug 115906 - Beagle daemon won't start
Summary: Beagle daemon won't start
Status: VERIFIED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Other (show other bugs)
Version: RC 1
Hardware: Other All
: P5 - None : Critical
Target Milestone: ---
Assignee: Jon Trowbridge
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-08 16:18 UTC by Joe Harmon
Modified: 2008-05-22 18:19 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Joe Harmon 2005-09-08 16:18:50 UTC 
I try and start the beagle daemon and it fails.

Unhandled Exception: System.ApplicationException: file is encrypted or is not a
database
in <0x00120> Mono.Data.SqliteClient.SqliteConnection:Open ()
in <0x00062> Beagle.Daemon.FileAttributesStore_Sqlite:Open (string)
in <0x000b4> Beagle.Daemon.FileAttributesStore_Sqlite:.ctor (string,string)
in <0x00048> Beagle.Daemon.FileAttributesStore_Mixed:.ctor (string,string)
in <0x0003c>
Beagle.Daemon.FileSystemQueryable.FileSystemQueryable:BuildFileAttributesStore ()
in <0x0001a> Beagle.Daemon.LuceneQueryable:get_FileAttributesStore ()
in <0x00155> Beagle.Daemon.FileSystemQueryable.FileSystemQueryable:AddDirectory
(Beagle.Daemon.FileSystemQueryable.DirectoryModel,string)
in <0x000c8> Beagle.Daemon.FileSystemQueryable.FileSystemQueryable:AddRoot (string)
in <0x0003c>
Beagle.Daemon.FileSystemQueryable.FileSystemQueryable:LoadConfiguration ()
in <0x0002e> Beagle.Daemon.FileSystemQueryable.FileSystemQueryable:Start ()
in <0x00016> Beagle.Daemon.Queryable:Start ()
in <0x00101> Beagle.Daemon.QueryDriver:Start ()
in <0x0012e> Beagle.Daemon.BeagleDaemon:StartupProcess ()
in <0x00048> (wrapper delegate-invoke) System.MulticastDelegate:invoke_bool ()
in <0x0002a> IdleProxy:Handler ()
in <0x00036> (wrapper native-to-managed) IdleProxy:Handler ()
in (unmanaged) 0x40062940
in <0x00004> (wrapper managed-to-native) Gtk.Application:gtk_main ()
in <0x00007> Gtk.Application:Run ()
in <0x00503> Beagle.Daemon.BeagleDaemon:Main (string[])
Comment 1 Andreas Jaeger 2005-09-09 05:06:14 UTC 
Please supply the latest log file from ~/.beagle
Comment 2 Andreas Jaeger 2005-09-09 08:47:15 UTC 
The log file needed is ~/.beagle/Log/current-Beagle

Btw. it works for me.
Comment 3 JP Rosevear 2005-09-09 12:07:48 UTC 
Is the sqlite (not sqlite2) package installed?
Comment 4 JP Rosevear 2005-09-09 12:13:06 UTC 
Sorry, reverse that is sqlite2 installed.
Comment 5 Joe Harmon 2005-09-09 13:19:44 UTC 
(In reply to comment #2)
> The log file needed is ~/.beagle/Log/current-Beagle

The file is empty.
Comment 6 Joe Harmon 2005-09-09 13:35:24 UTC 
(In reply to comment #4)
> Sorry, reverse that is sqlite2 installed.

They are both installed. (sqlite and sqlite2)
Comment 7 Joe Shaw 2005-09-09 14:06:14 UTC 
Were you trying to run it as root?
Comment 8 Joe Harmon 2005-09-09 14:23:45 UTC 
(In reply to comment #7)
> Were you trying to run it as root?

No. But I am starting to wonder if the fact that I installed iFolder 3.x (mono
based) that it had an affect on beagle. I have since removed it because it was
starting to have problems. but I know someone with the same machine that isn't
having a problem. However, they only have KDE installed and not both GNOME and KDE.
Comment 9 Joe Shaw 2005-09-09 15:21:46 UTC 
Is this an upgrade from a previous SUSE installation?  Can you try moving your
~/.beagle directory out of the way and restart the daemon?
Comment 10 Joe Harmon 2005-09-09 15:48:26 UTC 
(In reply to comment #9)
> Is this an upgrade from a previous SUSE installation? Can you try moving your
> ~/.beagle directory out of the way and restart the daemon?

Well, it was a fresh install, but I did keep my home directory. Renaming the
.beagle directory did allow it to start.
Comment 11 Joe Shaw 2005-09-09 16:04:19 UTC 
Ok, closing this then.  There was a brief period in there where we were using
sqlite3, so your database was upgraded automatically, but we reverted back to
sqlite2 because of reliability problems.