I had to reload openSuSE 11.1 after a failed attempt installing version 11.2. (different story).
I setup repositories again to use Stable KDE 4.3.4 release and loaded digikam and kipi plugins from the Core Repository as usual.
However, now when I attempt to start digikam, it takes an extremely long time to launch sitting at the loading kipi-plugins. That’s one problem.
Second issue is when I open an album, the thumbnails load as normal, but then if I move the mouse over the thumbnails, the whole album starts randomly blinking on and off all of the thumbnails. The rest of the desktop is not affected, only the thumbnails.
Neither of these issues ever happened on my prior install of 11.1 so I’m at a loss as to what’s going on.
For the love of god man… Why do you have so many repos! Your probably getting multiple versions with different builds.
If you don’t mind having to reconfigure digikam… Try deleting the digikam package and IT’S dependencies. Search ~ for any directories involving digikam; more than likely it’s going to be .digikam. Disable the VLC repo that you have and prioritize the repos so that the PACKMAN repos have a lower number (i.e. higher priority). Open up Software Management and change the view selection to the packman repo. Search for the digikam package and install it. If it’s not in there then change the view selection to OpenSuse OSS repo and search for it in there. I also recommend the same with kipi.
What are you using digikam for? Download photos from camera or photo management? Webcam?
Digikame is “A KDE application which acts as a frontend to gphoto2 for photo downloads from a digital camera. News, overview, screenshots and software download.”
Kipi is a more or less a plug-in environment to help render the images in applications; like digikam or gwenview.
If it takes a while to load the kipi plug-in’s then either (a) you have A LOT of plugins or (b) digikam is having difficulty loading them due to some type of config problem. When you mouse over an image/thumbnail (rendered via kipi) the applications (digikam) “refreshes” the view (again using kipi). The flicker is due to a latency or misconfig with kipi. Depending on the app; normally the actual flicker is faster than the video output or is updated every couple of seconds. Think of monitor refresh rates or how video works. To fix the problem you should address the interaction with kipi. And, instead of prying through config files looking for an error. It’s easiest to just delete the config’s stored in your profile so that the app can properly re-write the config files; hence the deleting of the ~/.app files. If it’s system wide, it’s a problem with the interaction between the packages; hence the deleting of the packages.
Thanks for the reply. I thought that the KDE repositories were the best source for the openSuSE if the stuff was there and I use Packman for multimedia stuff and other packages not supplied in the openSuSE repositories primarily. I use NVIDIA for the driver and Mozilla for the latest versions along with Open Office stable since the openSuSE are a little slow to update if at all for those.
I use Digikam for my photo album management, printing, tagging, geo tagging, etc. I find it quicker than gwenview and more stable, at least I did.
I removed all digikam packages I had loaded (both the KDE 3.5 and 4 versions even though the 3.5 version worked fine). I moved priority around, disabled the KDE 4 Backport and VLC repositories.
I don’t see Digikam on the packman repo at all. I am running openSuSE 11.1 x86_64.
The repos that are in there by default are the best to use. However, OpenSuse has had to break some packages due to legal issues. Like MP3 playing and making to DVD movie players.
That I can understand. However, the way that Suse (as in Novell Suse) gives us Opensuse is different. The reason it takes so long is that it hasn’t been rigorously tested in the *Suse environment; i.e. it’s stable & SUPPORTED by Suse. Since Novell bought Suse it has become a legitimate consumer product that must have customer satisfaction and support. They gave us OpenSuse for the GPL and keep the linux community happy. OpenSuse is presented to us as more or less a “beta” version of the Novell Suse. In essence, we get their OS for free in exchange for “testing” software on it.
You should give Picasa from Google a run. I’ve never had any problems with it; and it has a beta linux version.
Did you do the same with KIPI? Did you search the Default repo from suse for digikam and kipi?
Yeah, you kind of have to be a little knowledgeable on software development with this kind of stuff.
Maybe a different issue, and certainly does not explain the slow load, but…
After I migrated distros and moved my picture directory, I got strange behavior where the thumbnails would flash, or go blank when I hovered over them. Anything with a thumbnail view was very slow.
I fixed it by dumping my db and rebuilding by adding as if new albums. I store info in the file as meta data (ratings, tags, etc.) so I didn’t loose any data, but be careful if your data is only in the db. That fixed it for me. I didn’t look into to much, but I think that digikam ended up looking in the wrong place for the thumbnails - basically confused by the move.
Since you did a re-install, that could be part of your issue.
Thanks very much I will try that. I had removed digikam and kipi and reinstalled from KDE4 Core and still have the issue. I will try this first when I get home. I had also removed my digikamrc config file and let it rebuild and still have the flashing thumbnails. I’ll let you know later today how it works out.
Thanks for the info. I think I store my data in the meta data as well but need to check. If everything else fails I may have to do this. Don’t quite get it since it was working fine before I had to do the reinstall after the failed 11.2 attempt. Thank you. I’ll let you know how it goes.
System Path: “/usr/share/kde4/apps/marble/data”
Plugin System Path: “/usr/lib64/kde4/plugins/marble”
render plugin found “/usr/lib64/kde4/plugins/marble/CompassFloatItem.so”
render plugin found “/usr/lib64/kde4/plugins/marble/CrosshairsPlugin.so”
render plugin found “/usr/lib64/kde4/plugins/marble/GeoRendererPlugin.so”
render plugin found “/usr/lib64/kde4/plugins/marble/GraticulePlugin.so”
render plugin found “/usr/lib64/kde4/plugins/marble/MapScaleFloatItem.so”
render plugin found “/usr/lib64/kde4/plugins/marble/NavigationFloatItem.so”
render plugin found “/usr/lib64/kde4/plugins/marble/OverviewMap.so”
render plugin found “/usr/lib64/kde4/plugins/marble/Photo.so”
network plugin found “/usr/lib64/kde4/plugins/marble/QNamNetworkPlugin.so”
render plugin found “/usr/lib64/kde4/plugins/marble/StarsPlugin.so”
render plugin found “/usr/lib64/kde4/plugins/marble/Wikipedia.so”
Time elapsed: 6 ms
PhotoPlugin: Initialize
Use workaround: 0
Starting to load Plugins.
=== MarbleDirs: ===
Local Path: “/home/dmc55/.marble/data”
Plugin Local Path: “/home/dmc55/.marble/plugins”
Marble Data Path (Run Time) : “”
Marble Data Path (Compile Time): “/usr/share/kde4/apps/marble/data”
System Path: “/usr/share/kde4/apps/marble/data”
Plugin System Path: “/usr/lib64/kde4/plugins/marble”
render plugin found “/usr/lib64/kde4/plugins/marble/CompassFloatItem.so”
render plugin found “/usr/lib64/kde4/plugins/marble/CrosshairsPlugin.so”
render plugin found “/usr/lib64/kde4/plugins/marble/GeoRendererPlugin.so”
render plugin found “/usr/lib64/kde4/plugins/marble/GraticulePlugin.so”
render plugin found “/usr/lib64/kde4/plugins/marble/MapScaleFloatItem.so”
render plugin found “/usr/lib64/kde4/plugins/marble/NavigationFloatItem.so”
render plugin found “/usr/lib64/kde4/plugins/marble/OverviewMap.so”
render plugin found “/usr/lib64/kde4/plugins/marble/Photo.so”
network plugin found “/usr/lib64/kde4/plugins/marble/QNamNetworkPlugin.so”
render plugin found “/usr/lib64/kde4/plugins/marble/StarsPlugin.so”
render plugin found “/usr/lib64/kde4/plugins/marble/Wikipedia.so”
Time elapsed: 18 ms
PhotoPlugin: Initialize
Use workaround: 0
Starting to load Plugins.
=== MarbleDirs: ===
Local Path: “/home/dmc55/.marble/data”
Plugin Local Path: “/home/dmc55/.marble/plugins”
Marble Data Path (Run Time) : “”
Marble Data Path (Compile Time): “/usr/share/kde4/apps/marble/data”
I tried keyBangingMonkey’s suggestion and finally renamed my existing digikam db to save it and then restarted again. That seems to have corrected both the slow load and the flickering thumbnails. Thanks everyone for the help on this. Much appreciated.
The unconditional update seems to have created an issue with two plasmoids I use that no longer work, get the message component cannot be found when I choose it. In Yast it shows they are installed. I uninstalled them and reinstalled them with the same result. The plasmoids are yasp and yaWp for hardware status and weather info. They worked fine prior to the update. This is just weird.
It may be that they were being supplied by a different repository - one that I had you remove.
Not sure that’s the case.
You would need to check if they did indeed supply those packages in addition to the repos that are currently supplying them.
I don’t recommend the Backports or Playground. I know they are there to be used, but you really need some experience to manage them. Generally the Community repo is enough to satisfy. You may well find you actually have a number of packages showing red in Software Management (these are roll backs) due to the removal of those repos. So it’s up to you. You could add them back and see. But it’s not my recommendation.
I did check to see if either was supplied by one of those two and both are in the Community Repo only. The yasp one did come back to life after removing and reinstalling again, but yawp is still missing in action. Very strange, it’s the best one there too for weather in my opinion.
Thank you so much for your time, patience and help!
I don’t use any plasmoids so I can’t check. But I guess somewhere in .kde4 there must be a config file/folder (look to delete). Maybe someone else can help if they use plasmoids
