found out that digikam 0.10.x can’t display RAW files from my Canon EOS 7D
upgraded to 1.0.0 from some community repo -> problem solved
Sep 2010
errors in thumbnail generation: newly generated thumbnail occasionally “spreads” to other images in the same folder
attempt to upgrade to digikam 1.4.x fails
going back to 1.0.0 turns out to be impossible because it’s not offered in any repo anymore
now stuck with 0.10.x again (see above)
Some background concerning the upgrade failure:
1.4.x is offered in repo KDE:Backports. It installs without complaining but crashes upon start (crash always occurs when “read database” is displayed).
It’s also offered in several other repos, but trying to install it from there triggers a lot of dependency conflicts in yast. These conflicts seem to hint at KDE needing to be upgraded. So, I went to kde.org and found that they even offer a *.ymp package for OpenSuse 11.2 to upgrade KDE to the latest version. But, trying to apply this again triggers tons of dependency conflicts and I have a feeling that I’m in danger of messing up my hole system if I proceed any further from there.
So, what’s going on here?
Am I missing something easy?
Could it be that it’s impossible to upgrade to digikam 1.4 in OpenSuse 11.2?
Did I do something harmful by upgrading from 0.10.x to 1.0.0 in February?
@ah7013: negative again: I opened digikam 0.10 to see what the path to the database files would be, then renamed that directory, then installed 1.4 and launched it. It askes me for my collections (no database file to be found, obviously). I click “Cancel”, program crashes like before.
@ah7013: the 1.2 rpm gets me dependency conflicts again, although considerably fewer than 1.4 (7 as opposed to 50+). However, these conflicts grow in number, once you follow the suggestions offered (most of which require a provider change (??, “Anbieterwechsel” in German)).
I have it installed on mine and I’m running openSUSE 11.2 64. All is working fine for me. Now when I look at what I have installed and when I do a search for Digi here is what I see and the packages that I have installed
dcraw Raw Digitial Photo Decoding
gphoto A Digitial Camera Utility
libdc1394-22 1394 Based Digitial Camera Control Library
lib1394 coontrol12 1394 Based Digitial Camera Control Library
libexif An EXIF Tag Parsing Library for Digitial Cameras
libgphoto2 A Digitial Camera Library
raw-thumbnailer Thumbnailer for Digitial Camera RAW
I pulled all these from the Community Repositories.
At work right now, so I can’t check, but iirc, it suggests to upgrade several libraries to newer versions, which is only possible by changing the vendor. I think it also wants to uninstall a few things.
Many of the suggested libs had version numbers like “4.5.70.xxx”, that’s why I thought it requires a KDE upgrade (4.5.1 seems to be current, I have 4.3.5).
Strange, though, that it works on your system but doesn’t on ah7013’s fresh install.
I can confirm this on my opensuse 11.2 install, I used kde update apps repo, and installed digikam 1.4, just after indexing the database it crashes, last things it says in konsole are from marble (maybe marble should be updated too?)
Could it be that Gnome is the key here? Digikam is a KDE application, so upgrading it requires several kde-libs to be upgraded as well. This can get you in trouble on a KDE system, but probably not on a Gnome system.
I found a few hints in this German forum. One guy reports that he got digikam 1.4 to run after manually upgrading the following libs: libkdcraw8, libkexiv2-8, libkipi7.
I tried the same. I had to click myself through tons of required dependency resolutions, almost all of them requiring a vendor change. It was not successful in the end, even worse: Right now, the X-Server on my machine crashes right after login. I think, I reached that state after upgrading a few qt-related libs. Hope to get that fixed when I get home from work today. Not fun…
I know that Digikam is made for KDE and I like a lot of KDE apps, plus I have run KDE for a long time but I’m starting to like Gnome a little bit more so thats one reason I have both Desktops. I will try something out for you so we can track the problem down. I have a Laptop and another Desktop with just openSUE 11.2 KDE and a Laptop with openSUSE 11.1. I will see if I can install Digikam 1.4 and get it running on them.
Just a note tho when I install openSUSE now days I just do a plain install then update video drivers (nvidia) for my main then I put pacman’s repository in and install my music drivers, plus VLC’s repository, then I do a update for the rest of the system. This way I do not have to change to many vendors. I will try it out on my other copmuters and post back today.
Oh if you go to RPM Search and do a search for the RPM it will give you the option to check for the required lib’s, just click the check requires button, this might save you some time.
Well my other computers would not upgrade to the 1.4 with out giving me a long list to fix. I think I know what happen that made it work for me or at least this might be a fix. Take a look at this site because this is kind what I did to my main and thats the one working. I did zypper dup.
Here is the site. .:. ANL4U .:. LiNuX Addicted » Upgrade to 11.3 via zypper dup through Terminal – openSUSE –](http://anl4u.com/?p=795)
Thanks Brad, I always wanted to look a little deeper into zypper. Maybe now is a good time to do so. But did you really upgrade your system to 11.3 as described in the article?
In the meantime, I was able to recover my system using yast from the console. That got me back to digikam 0.10.0 again, and - surprise! - it can now display my RAW files correctly! Don’t know what happened there, but this eliminates the reason why I wanted to move away from 0.10.0 in the first place.
However, I gave 1.4 one last shot and tried to install it one more time from KDE:Backports. Again, it installed without problem, I could for the first time launch it without the program crashing, it even found my image collections - but: no thumbnails displayed. So, I made it rescan one collection. After a few seconds the program crashed. It also crashed on every subsequent attempt to start it.
So, more research is needed, but I will probably slow down a little bit on this because 0.10.0 now does what I want it to do.
Thanks to all who contributed to this thread!
Frank