Hi,

I have KDE 4.5 with digikam 1.5.0. I have been using digikam for some time. Recently my images stopped showing - I click on an album in the left panel and the right panel is blank.

I tried removing .kde4/share/config/digikamrc, digikam4.db and thumbnails-digikam.db.

Doesn't help. It scans all the folders and then same again - no images.

I tried as root - all works fine. So then I created a new dummy user and did the same - all works fine there too.

So what have I got in my environment that is preventing it working properly?

Hm, so you removed the rc file and it still comes up odd? Other than replacing your rc file with the one from the dummy user I can only think of complete removal of all things digikam from your home directory. Then take it from there...

Have you also tried renaming/removing .kde4/share/apps/digikam/, .kde4/share/apps/kipi/, and .kde4/share/config/kipirc ? I would also suggest uninstalling and re-installing both digikam and kipi, making sure they are from the same repo. If that still doesn't work you might want to delete these files, the files you mentioned, uninstall the program, then search your hard drive for any other files related to dikigam or kipi and remove those (be careful only to remove files really related to thse, I will take no responsibility for damage to your system), then re-install the programs (once again taking care that they are from the same repo) and see if that fixes it.

I just found that it wasn't my account per-se - but whichever account was logged in.

i.e. If I logged into X-windows with user a, digikam wouldn't work for user a. But if I used su to become user b in an xterm and ran digikam from there it worked perfectly. Or if I logged in as b, then digikam wouldn't work for b but would for a (su-ed from a shell).

I had a look at .xsession-errors and there were a number of complaints of libraries not loading with missing symbols. I tracked which packages these came from (using rpm -qf) and checked to see whether there was an update available. I found that liblqr had an update available - so I updated it.

This seems to have fixed the issue.

Glad to hear it is fixed. Could you please click the button on your latest post?