From kde-core-devel Sun Jun 10 01:23:04 2012 From: =?utf-8?q?Jos=C3=A9_Manuel_Santamar=C3=ADa_Lema?= Date: Sun, 10 Jun 2012 01:23:04 +0000 To: kde-core-devel Subject: KDE SC 4.8.4 important problems Message-Id: <201206100323.06359.panfaust () gmail ! com> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=133931384906792 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart7504129.uGtxpd9U2P" --nextPart7504129.uGtxpd9U2P Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, firstly, to be honest, let me say I'm doing huge effort to write this mail = in a=20 way that I don't look like a clueless cretin who reports bugs to the mailin= g=20 lists instead of the proper place (bugs.kde.org) just to "cheat" and get "m= y"=20 bugs fixed. I promise I'm not that kind of person, I have a git/svn KDE acc= ount=20 and I'm already doing a very modest contribution. In my honest opinion I kn= ow=20 a bit how things work in KDE with regarding to the bug reporting stuff. Also I'm packaging KDE for Debian in a team collaborating with other people= =20 since some time ago (I've been involved in 4.5.x, 4.6.x, 4.7.x and 4.8.x) a= nd=20 that's why I am writing here: when testing the latest point release of KDE = SC=20 (4.8.4), we are getting several crashes, and most of them are the kind of b= ugs=20 (called release-critical in Debian) which would prevent us to release packa= ges=20 in the next stable release or migrate them to the "testing" branch.=20 Most of these crashes follow this pattern (sorry for the vagueness, I=20 hope to gather more information this night or so, I'll try to keep you post= ed=20 but I can't promise anything): 1. Can't be reproduced with Nepomuk disabled. 2. Can't be reproduced with kdelibs 4.8.3 3. Can't be reproduced with KDE SC 4.9. 4. Could also be reproduced by various users and developers from other=20 distributions. 5. They are not 100% reproducible; however they happen everytime in some=20 computers, on others just very often; so often that make certain KDE progra= ms=20 unusuable. 6. I _feel_ backtraces might be invalid. Since I have been packaging KDE (more or less since 4.5 as said above) I ne= ver=20 got 7 potential RC bugs in a release (not even a .0 one) after just ~2 days= of=20 use. Read again the characteristics 2. 3. and .4; that in conjunction with = the=20 fact that some people just discovered today how you are managing git=20 branches/freeze for kdelibs (myself included) is why I think we are getting= =20 some people in other thread questioning -with or without reason- the kdelib= s=20 development model. I don't want to discuss the kdelibs development model in= =20 this thread (I would really prefer to keep any possible "omfg kdelibs=20 developers are using the same branch for 4.9 and 4.8" messages in the other= =20 thread) I'm just explaining the situation, I hope you get now why you are=20 reading the things you are reading in the other thread. That being said, in this thread I want to focus on the actual grave problem= (s)=20 of 4.8.4, this is the list of crashes I have been experiencing: #1 dolphin: I can reproduce it right now in one of my computers just opening it, in oth= er=20 sometimes it crashes just clicking a file or folder. Eshat Cakar -a fellow= =20 Debian packager- also got other crash just clicking a folder, however he ca= n't=20 reproduce it anymore after he rebooted his computer. Backtraces: http://alioth.debian.org/~santa-guest/4.8.4_crashes/bug_dolphin_santa.kcras= h. http://alioth.debian.org/~santa-guest/4.8.4_crashes/bug_dolphin_eshat.txt #2 gwenview=20 I can reproduce it just clicking an image and sometimes even just starting = the=20 application. Backtrace: http://alioth.debian.org/~santa-guest/4.8.4_crashes/bug_gwenview_santa.kcra= sh #3 kontact executing the kaddressbook component I can reproduce it very oftenly just clicking the kaddressbok component in= =20 kontact. Backtrace: http://alioth.debian.org/~santa-guest/4.8.4_crashes/bug_kontact_santa.kcrash #4 kmail executed outside kontact I can reproduce it just executing kmail outside kontact Backtrace: http://alioth.debian.org/~santa-guest/4.8.4_crashes/bug_kmail_santa.kcrash #5 kmail marking messages as read I think this one got fixed by a commit in kdepimlibs, which I included in t= he=20 debian packaging. Please ignore for now. #6 kontact executing various components: calendar, to-do list, journal When clicking on various kontact component I'm getting a segmentation fault= ,=20 always with the same backtrace: http://alioth.debian.org/~santa-guest/4.8.4_crashes/bug2_kontact_santa.kcra= sh #7 kmail links I can reproduce this one just opening a message with an url. Just clicking= =20 that url, which would it open it in konqueror given my local configuration= =20 crashes kmail: Backtrace: http://alioth.debian.org/~santa-guest/4.8.4_crashes/kmail_links.kcrash --nextPart7504129.uGtxpd9U2P Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAABAgAGBQJP0/b6AAoJEMhgx1pzqF8xsWkQAIOpNXpExpZhrxYE5d9KR13d 2+D8Ih84GizdUO/0BePG+RRN1FbdZw5XwXwS90a6encBUkAu1vxZSVEdNWS1kZUY q6AMAq86YANdtl+Z5GtXcQigsSoQ6Rnj8el0PM7dnF2kKrWcPhJcpHMDLFIZGzTp p/JAXLTATtN75kwaGdMHv/1VCEjQrOrlvS+koDX2yVXh+SZH6pU0l/Q1upZCg1yM 2/9mLS2suha0Leg+lsNRa0y213ImbNpB90PBZpSNIsjZYGJkFFTOMXYgl8HKTJEn RnfQHlxqyVY73/lARAVxwYX7rTzBCgnBjuglJMSI254DcO9e+h5IXfveRX2x9GbK 0wyhvs9/sAm90EGabBRQru3s9jkM5Td97sTijE+1TsqbmLGCrdPVcnjot76PZNi3 I9lO6WnrON+ichjppOnHxSp+csv8JlHjaVbG2l9sfnvZV2+5E6AZz8GFg1Q7YSZw aJ9LrIWzz7gVQbJLTSFKkCysxuakTdtGLujyMAL0e1AnwhiCZb4oDa2AqAETBSBi wZ94ux4nuF33EMB6nBVmpmQNn5FKBPp3/l2owxncyrsqpcTSAXstivSP80yzClWg K9uD+w2Z/Fjfe+dLDH8uo6aWkFgScIM62IF0lbFB4LswjgM+10f865xWkVZSivcM 4KjjoRfevEJdRUzItowX =8NDX -----END PGP SIGNATURE----- --nextPart7504129.uGtxpd9U2P--