From kde-core-devel Sun Jun 10 09:30:13 2012 From: "Aaron J. Seigo" Date: Sun, 10 Jun 2012 09:30:13 +0000 To: kde-core-devel Subject: Re: KDE SC 4.8.4 important problems Message-Id: <10980843.QbemdahQ0H () freedom> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=133932081808312 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart1921603.8HBJXxDqld" --nextPart1921603.8HBJXxDqld Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="ISO-8859-1" On Sunday, June 10, 2012 11:20:09 Aaron J. Seigo wrote: > On Sunday, June 10, 2012 03:23:04 Jos=E9 Manuel Santamar=EDa Lema wro= te: > > #1 dolphin: > > #2 gwenview > > #6 kontact executing various components: calendar, to-do list, jour= nal > > #7 kmail links >=20 > these are all the same crash, or at least related to each other. it i= s > crashing in KServiceTypeTrader::defaultOffers or KMimeTypeTrader::que= ry > apparently at times in KSycocaDict::find_string. curious: on an affected system, if you delete=20 =09`kde4-config --localprefix`/cache-freedom/ksycoca4*=20 do the crashes go away? possible culprit commits: =091a07fea2eaa69d571d5818812502edcc1d680d9c =09e91e5fed6b1aad365e12e919f430c3e8147552d3 neither are super recent, but they both touch the relevant code. there = was one=20 change to kmimetype by dfaure but it is not implicated by the backtrace= s nor=20 can i see how it would be (it added a required method, did not change e= xisting=20 code paths and definitely not the ksycoca code underneath it) --=20 Aaron J. Seigo --nextPart1921603.8HBJXxDqld Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEABECAAYFAk/UaSUACgkQ1rcusafx20PbDwCeJ+zeZtZm3/faqiCxHlcPQLUM w1kAn0GO5ddbtf8rNIOZOjr5kbv+DpG3 =VF5v -----END PGP SIGNATURE----- --nextPart1921603.8HBJXxDqld--