[Digikam-users] Digikam-users Digest, Vol 33, Issue 40

[Gilles Caulier]

2008/2/29, Duffields <dhltd at telus.net>:
>
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Thu, 28 Feb 2008 11:38:53 -0800
> > From: Duffields <dhltd at telus.net>
> > Subject: [Digikam-users] Crash recovery
> > To: digikam-users at kde.org
> > Message-ID: <47C70DCD.3090405 at telus.net>
> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> >
> > I just completed an evaluation of Photo Management applications for
> Ubuntu (Ver
> > 7.10) and had settled on DigiKam as the best. BUT today I hooked up an
> NAS to
> > see how DigiKam would perform and when I was editing some photos,
> DigiKam
> > stalled when deleting a photo.
> >
> > The NAS was churning madly for a long time so I re-booted the Ubuntu Box
> and
> > when I tried to re-start DigiKam, a message displayed "Failed to update
> old
> > Database to new Database format" and DigiKam would not load.
> >
> > I tried un-installing DigiKam and deleting all related data files that I
> could
> > find, then re-installing DigiKam but I still get the same error message
> when
> > trying to run it.
> >
> > Can someone tell me how I can re-start DigiKam and if this is a known
> problem is
> > there a work-around?
> >
> > Thanks
> >
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Thu, 28 Feb 2008 20:42:07 +0100
> > From: "Gilles Caulier" <caulier.gilles at gmail.com>
> > Subject: Re: [Digikam-users] Crash recovery
> > To: "digiKam - Digital Photo Management for the masses"
> >       <digikam-users at kde.org>
> > Message-ID:
> >       <b4b1230e0802281142r33ecba6du24d77c8d917cd255 at mail.gmail.com>
> > Content-Type: text/plain; charset="iso-8859-1"
> >
> > Hi,
> >
> > What do you mean by "NAS" exactly ? A network file system ?
> >
>
> Sorry, I hate it myself when people use acronyms and contractions when
> communicating with others who may not know the jargon.
>
> NAS - "Network Accessible Storage".  I have a D-Link DNS-323 Network drive
> that
> is configured with two hard drives with mirror imaging.  All my computers
> are
> connected to it and all the shared files are kept on it rather than on the
> individual computers.  It works well on a network composed of both Windows
> and
> Linux computers.
>
> I was testing Digikam on local files on an Ubuntu Box and when I decided
> on
> which photo management application to keep (Digikam) I pointed Digikam to
> the
> NAS device by changing the Digikam setup.
>
> It seemed to work perfectly until I started moving and deleting photo
> files.
> After deleting a couple of files, Digikam froze and the drive indicator
> lights
> on the NAS began blinking furiously, and access from other computers
> slowed to a
> crawl.  That went on for for about five minutes until I lost my nerve.  I
> could
> not kill Digikam so I re-booted the Ubuntu computer.
>
> When I restarted it and tried to re-start Digikam, I got the error message
> described above.  I re-tried with no success so then I tried to un-install
> Digikam, deleted all residual files that I could find that contained
> digikam,
> and re-installed Digikam.
>
> Despite doing all that, when I try to re-start Digikam, I still get the
> same error.
>
> I would like to keep Digikam and find a work-around if possible, but I
> need to
> know where Digikam keeps the database that the message referred to and how
> I can
> re-build it without being able to start Digikam.
>
> Is there a "safe mode" to start Digikam?
>
> Any advice or information you can provide would be much appreciated.  I am
> quite
> new to Linux, having only played with it for a few months, but it looks
> like it
> is a viable replacement for Windows although perhaps we will still need
> one or
> two virtual Windows machines for a few Windows dependent applications.
>
> Thanks
>
> Mac
>
>
Duing a problem with QSlite against remote file system, digiKam 0.9.x is not
compatible by default with NAS, because sqlite file used by digiKam is
hosted on root album.

There is a way to wrap around this problem using file-link. Look here :

http://www.digikam.org/?q=node/219

Of course with future 0.10.0 release (KDE4 port), this problem have been
fixed (plus a lots of new features) :

http://digikam3rdparty.free.fr/Screenshots/digikamKDE4_15.png

Best

Gilles Caulier
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20080229/e8ecfb6d/attachment.html>