Launchpad has imported 15 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=121005.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Changed in: digikam
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to digikam in ubuntu.
https://bugs.launchpad.net/bugs/48282
Title:
digikam will not start with pictures stored on either an NFS or a CIFS
Closing as Fixed, as Digikam 0.10.0 (in Jaunty) provides better support
for network shares.
** Changed in: digikam (Ubuntu)
Status: Confirmed = Fix Released
--
digikam will not start with pictures stored on either an NFS or a CIFS disk
https://bugs.launchpad.net/bugs/48282
You received
Yes, for ME, that solution would be sufficient - and I could go back to
using digikam (after waiting for 2 years)
--
digikam will not start with pictures stored on either an NFS or a CIFS disk
https://bugs.launchpad.net/bugs/48282
You received this bug notification because you are a member of
This is partially addressed in KDE4 version of digikam (0.10.0), which is now
in Jaunty (and you can try it on Intrepid from digikam-experimental PPA). Is
the following implementation acceptable for you:
http://bugs.kde.org/show_bug.cgi?id=137694#c13
--
digikam will not start with pictures
** Changed in: digikam (Ubuntu)
Status: New = Confirmed
--
digikam will not start with pictures stored on either an NFS or a CIFS disk
https://bugs.launchpad.net/bugs/48282
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
I'm desperately waiting for a fix of this kind in Ubuntu. I bought a
NAS to specifically store my pictures on, and then digikam refused to
work with it. In case dot lock files have a performance issue for local
filesystems, the sqlite implementation could try to find out if unix
locking is
Hi,
Some people here could be interested in testing the following patch with
0.9.4svn version :
http://mail.kde.org/pipermail/digikam-devel/2008-July/019511.html
This makes sqlite use .lock files for locking the database which is
supported on all platforms and filesystems. Use at your own
If you still have an NFS filesystem try using the mount option nolock. This
will lead to loclal locks only, so be sure to not work from two machines at the
same time. I do not know if CIFS knows this option too.
Another option would be to move the database to a local filesystem (your home)
and
digikam 0.10 is based on KDE4 and more or less a rewrite.
IMHO it's not something to consider for hardy. If nothing goes wrong
digikam 0.10 will be ready together for KDE 4.1 in Juli and there will be
backports, either officiall ones or in my repo.
Achim
--
digikam will not start with
** Changed in: digikam (upstream)
Status: Unknown = Rejected
--
digikam will not start with pictures stored on either an NFS or a CIFS disk
https://launchpad.net/bugs/48282
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Bug watch added: KDE Bug Tracking System #121005
http://bugs.kde.org/show_bug.cgi?id=121005
** Also affects: digikam (upstream) via
http://bugs.kde.org/show_bug.cgi?id=121005
Importance: Unknown
Status: Unknown
--
digikam will not start with pictures stored on either an NFS
Bug 121005 does not say that. If there is a solution presented by sqlite
it will probably be implemented.
You can use a compile time option to store the db in your home folder
instead of near the album folder. If that's a solution for you use that.
Although not supported by the developers.
--
13 matches
Mail list logo
