In data lunedì 14 luglio 2014 23:22:32, Jason Newton ha scritto: Hello,

How in the world did 5.13.2 get there? I looked over the current spec file (and last 2 recent changes) and I couldn't find anything obvious.

That is the SO version of the library, which has no direct relation to the version of the package (kdelibs4). (FYI, kdecore by itself does not exist anymore in KDE Frameworks 5). -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: 6E1A4E79

On Tuesday 15 of July 2014 10:19:33 Jason Newton wrote:

Fair enough although I don't think it's normal to bump the SO version outside of the project major.minor versions (not saying I haven't seen it done but it is more bizarre here). Here's the lovely stacktrace

Do you have locally built openCV? Cheers, Hrvoje

kde:current plus kde:qt5 with 5.3 installed, all are only a few days out of date and its been doing this for a few months. I develop programs against qt5. I cant say I did anything really, gwenview window pops up and vanishes an instant later. i do use opencv for work but i dont think that has any bearing, i also build my packages in home:jenewton:science, you can test with that installed if you cant reproduce it - happens on all my machines. -Jason On Tue, Jul 15, 2014 at 1:41 AM, Luca Beltrame wrote:

In data martedì 15 luglio 2014 01:19:33, Jason Newton ha scritto:

...

Gwenview will stop crashing when I rpm -e --no-verify libqt5gui5. Looks like this is not quite a new issue: https://bugs.kde.org/show_bug.cgi?id=322558

From the backtrace, it looks to me that the fault lies entirely in KIPI, as you have suggested, and I can say I'm not too surprised (KIPI has always lots of issues).

That said, how do you trigger the crash? I couldn't do so on my KDE:Unstable:SC system. From where you got Qt 5.x installed?

-- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: 6E1A4E79 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

In data martedì 15 luglio 2014 02:54:00, Jason Newton ha scritto: (no need to CC me - I'm subscribed)

kde:current plus kde:qt5 with 5.3 installed, all are only a few days out of date and its been doing this for a few months. I develop programs against qt5.

I've been doing that myself occasionally but I've yet to see a crash in Gwenview. The main difference is that I'm not using openCV. From which repo do KIPI plugins come from? -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: 6E1A4E79

Culprit was Kipi plugin removeredeyes. I took the lazy way out after triaging the removal of highgui in the linking. They presently use 3 different cmake FindOpenCV scripts rather than the one that comes with opencv (didn't always, but they shouldn't be supporting that madness). They don't specify what components they need (esp when using MACRO_OPTIONAL_FIND_PACKAGE) which means defaults get linked in which typically include highgui. libkface and digikam also link against all these libs. From what I can tell they don't use any highgui functionality. So that looks like it'll take some time to remove out which I currently don't have for this.... so I'm just going to live with a rm'ing the removeredye plugin from the filesysem as that seems to achieve the desired affect of not crashing for a plugin I never use anyway. On Tue, Jul 15, 2014 at 3:17 AM, Jason Newton wrote:

Ugh, dll hell. Why in the world does kipi need highgui I wonder - aux imread/imwrite but highgui sucks at that anyway. That's the only library that has anything to do with gui toolkit. The others don't touch that stuff - in general at least. Well that gives me something to poke around to next I guess.

On Tue, Jul 15, 2014 at 3:01 AM, šumski wrote:

...

On Tuesday 15 of July 2014 11:54:00 Jason Newton wrote:

...

... i do use opencv for work but i dont think that has any bearing, i also build my packages in home:jenewton:science, you can test with that installed if you cant reproduce it - happens on all my machines. There's your problem - you build openCV against Qt5. One of kipi-plugins loads libopencv, which tries to load Qt5. And you can't have Qt4 and Qt5 loaded in the same process space...

Cheers, Hrvoje

...

-Jason -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org