From kde-core-devel  Wed Jun 13 20:59:41 2012
From: Albert Astals Cid <aacid () kde ! org>
Date: Wed, 13 Jun 2012 20:59:41 +0000
To: kde-core-devel
Subject: Re: KDE SC 4.8.4 important problems
Message-Id: <2891977.KVKYrj7QF8 () xps>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=133962138814820

El Dimecres, 13 de juny de 2012, a les 14:47:08, Will Stephenson va esc=
riure:
> > On Wed, Jun 13, 2012 at 2:34 PM, Sebastian Tr=FCg <sebastian@trueg.=
de>=20
wrote:
> > > I am totally lost. What is the problem with that commit?
> >=20
> > AFAIK, the problem is that changes were made in both Soprano and KD=
Elibs
> > for 4.9, but for 4.8.4, they are using this "changed" kdelibs with =
the old
> > soprano.
>=20
> Not correct - at openSUSE, we are using Soprano 2.7.6 with kdelibs 4.=
8.4
> (and virtuoso 4.1.5) and we get the crashes mentioned in Jose Maria's=

> original mail.

Yes, that's the whole point, there is something wrong in the=20
Soprano 2.7.6 + kdelibs 4.8.4 combination
Soprano 2.7.6 + kdelibs 4.8.3 works
Soprano 2.7.57 + kdelibs 4.8.4 works

Cheers,
  Albert

> Particularly the gwenview crash is very easy to reproduce:
> > #2 gwenview
> > I can reproduce it just clicking an image and sometimes even just s=
tarting
> > the application.
> > Backtrace:
> > http://alioth.debian.org/~santa-guest/4.8.4_crashes/bug_gwenview_sa=
nta.kcr
> > as
> I don't know whether there is an issue with the kdelibs commit or whe=
ther
> the SC/BC issue Aaron fixed with TCPClient is relevant.  I don't unde=
rstand
> why the backtraces seemingly have nothing to do with Soprano either, =
unless
> (guess) a threading problem causes useless backtraces to be generated=
.
>=20
> Will