From kde-core-devel Wed Jun 13 21:47:27 2012 From: Vishesh Handa Date: Wed, 13 Jun 2012 21:47:27 +0000 To: kde-core-devel Subject: Re: KDE SC 4.8.4 important problems Message-Id: X-MARC-Message: https://marc.info/?l=kde-core-devel&m=133962354615721 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--e89a8fb1ebce9bfdf404c2615c19" --e89a8fb1ebce9bfdf404c2615c19 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable The relevant commits have been reverted in the KDE/4.8.x branch. This should fix the issues. On Thu, Jun 14, 2012 at 2:29 AM, Albert Astals Cid wrote: > El Dimecres, 13 de juny de 2012, a les 14:47:08, Will Stephenson va > escriure: > > > On Wed, Jun 13, 2012 at 2:34 PM, Sebastian Tr=FCg > wrote: > > > > I am totally lost. What is the problem with that commit? > > > > > > AFAIK, the problem is that changes were made in both Soprano and > KDElibs > > > for 4.9, but for 4.8.4, they are using this "changed" kdelibs with th= e > old > > > soprano. > > > > 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 > 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 > starting > > > the application. > > > Backtrace: > > > > http://alioth.debian.org/~santa-guest/4.8.4_crashes/bug_gwenview_santa.kc= r > > > as > > I don't know whether there is an issue with the kdelibs commit or wheth= er > > the SC/BC issue Aaron fixed with TCPClient is relevant. I don't > understand > > why the backtraces seemingly have nothing to do with Soprano either, > unless > > (guess) a threading problem causes useless backtraces to be generated. > > > > Will > --=20 Vishesh Handa --e89a8fb1ebce9bfdf404c2615c19 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable The relevant commits have been reverted in the KDE/4.8.x branch.

Thi= s should fix the issues.

On Thu, Jun 14, = 2012 at 2:29 AM, Albert Astals Cid <aacid@kde.org> wrote:
El Dimecres, 13 de juny de 2012, a les 14:47= :08, Will Stephenson va escriure:
> > On Wed, Jun 13, 2012 at 2:34 PM, Sebastian Tr= =FCg <sebastian@trueg.de> wrote:
> > > I am totally lost. What is the problem with that commit?
> >
> > AFAIK, the problem is that changes were made in both Soprano and = KDElibs
> > for 4.9, but for 4.8.4, they are using this "changed" k= delibs with the old
> > soprano.
>
> 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= 9;s
> original mail.

Yes, that's the whole point, there is something wrong in the
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,
=A0Albert

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



--
Vishesh Handa

--e89a8fb1ebce9bfdf404c2615c19--