Summary: | Database collections are removed when docker.io is installed | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Hatl <hatl> |
Component: | Portability-Runtime | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED DOWNSTREAM | ||
Severity: | wishlist | CC: | caulier.gilles, oxdef+kde |
Priority: | NOR | ||
Version: | 4.5.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
URL: | https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762950 | ||
Latest Commit: | Version Fixed In: | 7.6.0 | |
Sentry Crash Report: |
Description
Hatl
2014-12-08 12:10:35 UTC
Docker.IO is a very specific run-time environment, never tested... Gilles Caulier Maybe I wasn't clear enough: I'm not talking about running digikam inside docker or using any docker features. I just installed docker on my desktop PC where I'm also running digikam. My setup: - Kubuntu - installed digikam, added pictures, ... - apt-get install docker.io -> digikam stops working (uses wrong path) I have no idea why digikam even changes the storage path. When I run "service docker stop" and start digikam afterwards, it works again. No idea. It sound like more a DOWSTREAM problem to report on Kubuntu team. We have nothing to deal with docker.io Gilles Caulier The problem is not within docker. The problem is that digikam determines the collection path in a wrong way. |