[Pkg-kde-extras] Bug#340567: digikam: fails to start with "albumtreestate.bin not found"

Achim Bohnet ach at mpe.mpg.de
Thu Nov 24 12:30:03 UTC 2005


On Thursday 24 November 2005 12:57, you wrote:
[...]
> >I famd running?
> 
> Yes, of course it's running, otherwise digikam couldn't connect to it:
>  4985 ?        Ss     0:01 /usr/sbin/famd -T 0
> 
> >Which version
> 
> ii  fam            2.7.0-6        File Alteration Monitor
> 
> >> (Note: I'm not using KDE per se, but Enlightenment, and pulled in
> >> digikam via simple apt-get install from stable)
> 
> >Well, I guess here's the culprit. The mixture pkgs from unstable with
> >some stable.
> 
> In this case the bug would be an improper dependency - but which one?

Good question ;)  Do you have any other app that uses famd?  Do they work?

One possibility is to install konqueror (remember the additional pkgs
installed). Start

	konqueror $HOME

create from the command line a file in $HOME.   Does konqueror  update
it's view and shows the new file?  If yes, does digikam now work? If
yes,  via removing the newly installed pkgs one by one, it is maybe
possibile to find out what's goes wrong.

My sid is currently pretty useless due to c++ trans.  But maybe
I manage to get a similar setup like your.

Achim
> 
> cheers,
> &rw
> -- 
> -- OS/X: Because making Unix user-friendly
> -- was easier than debugging Windows.
> 
> 
> 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- reddy at lion.austin.ibm.com




More information about the pkg-kde-extras mailing list