[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 121005] digikam won´t start when the album-path stays on nfs-volume
From:       "René" Fritz <rene () colorcube ! de>
Date:       2006-08-15 14:48:20
Message-ID: 20060815144820.3715.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=121005         




------- Additional Comments From rene colorcube de  2006-08-15 16:48 -------
I'm not shure if it's only a sqlite problem. But also when it is so I agree a message \
for the user is better than quietly do nothing or just crash.

Anyway, maybe I have a little more information which might help.

I tested with an nfs mount and also (the same album folder) with a samba share \
mounted with cifs. The behaviour of digikam is the same. I can't say if file locking \
(and that seems to be the problem with sqlite) is working with samba or not. 

I can work with V. 0.8.x and 0.9b1 having the album on the network mount. Importing \
images from the camera works, creating album folder and adding comments or tags - no \
problem.

What's not working is ...

1. to enable the option "Search for new photos on startup" (don't know the exact \
wording) 

This will bring up a box on startup with a progress bar which goes to 99% and that's \
it. Nothing happens. Starting digikiam in the shell gives no output. Interestingly \
this worked once with V.0.8.?. (By the way, would be nice to have an "update album" \
function to search for new photos.)

Disabling the option makes digikam work again.
~/.kde/share/config/digikamrc:
[General Settings]
Scan At Start=false

2. importing files or folder into the album.

This start a copy process with a normal kde copy box. The box does not change and \
stays at 0% forever. Surprisingly the files are copied into the right place.


It's said that nfs and sqlite doesn't work, but that's not true. Even digikam works. \
What's not working are the import function of digikam. This might be related to \
sqlite, I don't know. In my opinion, sqlite on an nfs share shouldn't make any \
difference when only one user access the db - it's just slower. It would be nice if \
that get fixed in 0.9


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic