Vishesh "fixed" the KDE/4.8.x branch of kdelibs. Can you guys verify it also fixes the issues for you?
If so, what's the next step? Release an early 4.8.5? Repackage 4.8.4 kdelibs? Ideas? Cheers, Albert
--- Begin Message ---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 <[email protected]> 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üg <[email protected]> > 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 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'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.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. 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 > -- Vishesh Handa
--- End Message ---
_______________________________________________ release-team mailing list [email protected] https://mail.kde.org/mailman/listinfo/release-team
