Hi,

I do not use it very often, but when I tried to launch it recently on my slackware64 current box it immediately segfaulted.

I use SlackBuilds from slackbuilds.org with sbopkg.

I tried to recompile the whole queue but It didn't change anything.

I also tried with ponce slackbuilds for current, same result.

When I launch it in a terminal I only get "segmentation fault" and that's all.

Does anybody experiment the same result ? If no, do you have any idea to solve my problem ?

Packages version :
Thanks for your help.

Did you try uninstalling all those dependencies before recompiling the queue? Otherwise, the newer builds might've picked up older libraries.

Hi Bourdieu,

the one in SBo is tested against -stable releases, not -current
I have digiKam 5.6.0 script already on my personal repository and that will become future digiKam script in the repository once KDE 5 goes into -current.

That will depends on framework5 and libkipi5 also available in my repository

FWIW I just built digikam from SBo and all of its dependencies (with no additional patches) on a clean slackware64-current full install and it seems to work fine: you could try doing the same, it should work.

That will be a sad day.


Speaking of digiKam, whatever happened to all the kipi-plugins used to extended the functionality of Gwenview?
I installed kde-5 yesterday, along with digiKam, and was quite surprised to see only a handful of plugins accessible from Gwenview.

1 members found this post helpful.

To the contrary. I can't wait for the old KDE4 to be brought to its death bed.

Your expectations of what Plasma5 should do for you are perhaps not matching with the direction its development is going, but you can always be vocal about your preferences - in the right places! Join the discussion in the KDE forums and Google+ groups, make a difference.
No KDE developer is going to read this Slackware forum for directions.

3 members found this post helpful.

That's because i didn't build the extra package which contains the kipi-plugins in the current digiKam in SBo.
In my personal script, i have added that build and it's available in digiKam's menu.

I checked Gwenview on Plasma5, and I see a lot of plugins that have their origin in the digikam package: http://imgur.com/a/QFP7n
You don't see those?

Several months ago I asked about Digikam no longer being a default app or even an "Extras" and was given an excellent explanation - for some reason Digikam is all-over-the-map with constantly changing dependencies so it is a moving target andf the cost of keeping up with it just isn't worth any benefit now that other apps more stable, do the same things. We all grow fond of certain apps and are reticent to just toss away hard won learning curves and smooth experience but I found I didn't miss Digikam more than about 5 minutes. YMMV but until such a time may come where Digikam settles down, it's just easier and of little adjustment to just wave bye bye.

The export options? Yes, but I have no need for those. I'm looking for the image and tools plugins which have almost entirely disappeared.
Under "tools" there is one option to e-mail. Under "image" there are two options. What happened to the ability to edit or delete meta-data, the image manipulation tools, batch processing, etc., etc., etc.?

I have tried digiKam several times over the years and have never cared for it.
At one time the digiKam developers made the kipi-plugins available as a separate package so you could install them if you needed them for Gwenview or other KDE applications. Most unfortunately, a few years ago (I've forgotten when) the developers, in their wisdom, HA!, decided to stop providing the plugins as standalone package and we are now required to install digiKam to get the plugins. Even if you never use digiKam, you have to install it to get the plugins.

I've been using KDE-5 since installing your packages, again, yesterday and my opinion hasn't changed a bit since the first time I tried it.
After KDE-4.13.3 was released, the first version of KDE-4 worth using, IMHO, I've been bouncing back and forth between Xfce and KDE-4. This most recent experience with KDE-5 has just cemented my plans to go completely to Xfce if and when KDE-5 is added to Slackware, and find replacements for what were my favorite KDE applications.
One thing I've noticed each time I've tried KDE-5, about 4 or 5 times, at this point, is it is just huge. The number of files and the space they require has to be far greater than KDE-4?

What do you dislike so much about Plasma 5? It was a bit buggy in the beginning but has settled down nicely, IMO. To me, it's the same as KDE 4 but better looking and less cluttered.

My opinion is just the opposite. Worst looking desktop I've seen. Even after trying to "customize" it, it has that simplistic, almost childish appearance.
I'm guessing it is just impossible to keep the same method of changing settings from one version of qt to another?
I've been trying to move something I've added to the panel from one side to the other. Doesn't work the same way as KDE-4. Why does a user need to learn how to do this over and over.
If KDE were a car, every time a new version comes out, one would have to learn how to drive all over again. I can go rent a car, something that outwardly looks different from what I own, and yet I can get into it and drive away. No problem. The desktop developers need to learn people want to be able to do what they need to get done, without the controls changing with each and every new model.

Is that a gut feeling or did you really calculate the difference?

In Slackware 14.2:

Plasma5 shows:
I.e. most of what happened is a shift of the translations from separate source tarballs into the actual program sources.

1 members found this post helpful.