Am 08.03.2015 um 20:22 schrieb Patrick Shanahan: > > Warning: following will delete your library.db, you might want to back it up > cp .config/darktable/library.db <some-where> > (if you have specific config alterations you wish to save): > cp .config/darktable/darktablerc <some-where> > cp .config/darktable/darktable.gtkrc <some-where> > > > as user: > rm -rf .config/darktable/* .cache/darktable/* > > as root: > rpm -e darktable > zypper ar -r > http://download.opensuse.org/repositories/multimedia:/photo/openSUSE_13.2/multimedia:photo.repo > zypper ref multimedia_photo > zypper -v in -r multimedia_photo darktable-1.6.3-99.1 > > multimedia_photo contains 1.6.3-99.1 which may be the same as 1.6.3-89.1 > as the ##s folloing the dash are build number particular to *that* repo. > (so I have been told). > > advise:
I did so. There are no errors nor warnings: "Selecting 'darktable-1.6.3-99.1.x86_64' from repository 'Tools for viewing and editing photos (openSUSE_13.2)' for installation. Resolving package dependencies... Force resolution: No The following application is going to be installed: Darktable The following NEW package is going to be installed: darktable 1.6.3-99.1 1 new package to install. Overall download size: 2.8 MiB. Already cached: 0 B After the operation, additional 13.0 MiB will be used. Continue? [y/n/? shows all options] (y): y committing Retrieving package darktable-1.6.3-99.1.x86_64 (1/1), 2.8 MiB ( 13.0 MiB unpacked) Retrieving: darktable-1.6.3-99.1.x86_64.rpm ........[done (3.8 MiB/s)] Checking for file conflicts: .......................[done] (1/1) Installing: darktable-1.6.3-99.1 .............[done] committingCommitResult (total 1, done 1, error 0, skipped 0, updateMessages 0)" Starting DT showed no peculiarities (starting from terminal showed no errors). But when I imported the directory with the photos I worked on last, the same weird behavior returned: some photos were displayed in lighttable, the rest remained solid gray. No editing in darkroom. DT crashed. So I removed the sidecar files from the directory. Voilá, everything runs as fine. This was no real testing. But at least at the first glance DT behaves as it should. Does this mean that I cannot use the old database together with the sidecar files any more? Will I have to retain a copy of DT 1.4.2 in a VM for ever in case I need to make some amendments to older photos? Or is there a way to transfer the data? Maybe the whole problem derives from the "sharpen" problem I used to experience with 1.4.2. I described it in my posting from 8 Mar 2015 12:02:41 +0100. I do hope that solving this problem could make DT 1.6.3 work with the old data. Volker ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Darktable-users mailing list Darktable-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-users
