Fix for crashes due to ubuntu-specific accessibility patch

The attachment "kubuntu_98_a11y_crash_fix.diff" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

For reference, this is a fresh stack trace from a crash on Ubuntu 14.04.

Thanks for filing the bug, I'm working on getting the SRU paperwork done

FTR: patch approved by the original a11y patch author on kubuntu-devel

https://lists.ubuntu.com/archives/kubuntu-devel/2014-March/008097.html.

This bug was fixed in the package qt4-x11 - 4:4.8.5+git192-g085f851+dfsg-2ubuntu4

---------------
qt4-x11 (4:4.8.5+git192-g085f851+dfsg-2ubuntu4) trusty; urgency=medium

  [ Jonathan Riddell ]
  * Add kubuntu_glib-honor-ExcludeSocketNotifiers-flag.diff from LiMux
    fix crash in LibreOffice with KDE theme LP: #1290514

  [ Rohan Garg ]
  * Add kubuntu_98_a11y_fix_crash.diff to fix plasma crashing due to
    ubuntu-specific accessibility patch LP: #1289600
 -- Jonathan Riddell <email address hidden> Tue, 11 Mar 2014 13:29:27 +0000

Fix uploaded as part of bug 1290514, awaiting approval from ~ubuntu-sru

Hello Alexey, or anyone else affected,

Accepted qt4-x11 into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/qt4-x11/4:4.8.4+dfsg-0ubuntu18.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Alexey, or anyone else affected,

Accepted qt4-x11 into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/qt4-x11/4:4.8.3+dfsg-0ubuntu3.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Alexey, or anyone else affected,

Accepted qt4-x11 into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/qt4-x11/4:4.8.1-0ubuntu4.7 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Scott, I have confirmed that the crash was fixed when it was in trusty-proposed (sorry for not saying so back then). I also just checked with my saucy vm, plasma with 4:4.8.4+dfsg-0ubuntu18.1 reconfirmed to crash and (hurray!) plasma with 4:4.8.4+dfsg-0ubuntu18.2 confirmed NOT to crash. Hope this hits saucy-updates soon. :)

I don't have any good vm with precise right now, so can't test 4:4.8.1-0ubuntu4.7 yet.

Just installed and tested precise. For whatever reason I couldn't reproduce plasma-desktop crash with neither 4:4.8.1-0ubuntu4.6, nor 4:4.8.1-0ubuntu4.7, no matter how many times I switch between Activities and Add widgets. Maybe there's something different about 12.04 that makes it not crash like it was for saucy and trusty. Not sure whether it means verified or not...

Just tested quantal:

4:4.8.3+dfsg-0ubuntu3.2 crashes
4:4.8.3+dfsg-0ubuntu3.3 doesn't crash

Reuploaded without patch to bug 1290514 so that this one can proceed

Please reconfirm the new builds, sorry for the hassle.

For saucy under VirtualBox with resolution 1280x960:

4:4.8.4+dfsg-0ubuntu18.1 crashes
4:4.8.4+dfsg-0ubuntu18.3 doesn't crash

I just read quantal release notes and it seems support period is 18 months, so isn't support over for quantal? It also seems odd that update package is for Quantal and not for Raring...

On Sunday, April 27, 2014 18:09:58 you wrote:
> I just read quantal release notes and it seems support period is 18
> months, so isn't support over for quantal? It also seems odd that update
> package is for Quantal and not for Raring...

Raring was the first release to drop to a 9 month support window. Quantal will
be retired shortly, but hasn't quite yet.

Quantal under VMWare Player, 1280x800:

-0ubuntu3.2 crashes
-0ubuntu3.4 doesn't crash

Tried again, but still couldn't reproduce plasma crash on precise.

I can confirm that I can't reproduce the crash on 12.04.4, with/without the update. Not sure how to proceed here.

This bug was fixed in the package qt4-x11 - 4:4.8.4+dfsg-0ubuntu18.3

---------------
qt4-x11 (4:4.8.4+dfsg-0ubuntu18.3) saucy; urgency=medium

  [ Rohan Garg ]
  * Add kubuntu_98_a11y_fix_crash.diff to fix plasma crashing due to
    ubuntu-specific accessibility patch LP: #1289600
 -- Rohan Garg <email address hidden> Wed, 12 Mar 2014 16:33:21 +0100

The verification of the Stable Release Update for qt4-x11 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

This bug was fixed in the package qt4-x11 - 4:4.8.1-0ubuntu4.8

---------------
qt4-x11 (4:4.8.1-0ubuntu4.8) precise; urgency=medium

  [ Rohan Garg ]
  * Add kubuntu_98_a11y_fix_crash.diff to fix plasma crashing due to
    ubuntu-specific accessibility patch LP: #1289600
 -- Rohan Garg <email address hidden> Wed, 12 Mar 2014 18:13:21 +0100

This bug was fixed in the package qt4-x11 - 4:4.8.3+dfsg-0ubuntu3.4

---------------
qt4-x11 (4:4.8.3+dfsg-0ubuntu3.4) quantal-proposed; urgency=medium

  [ Rohan Garg ]
  * Add kubuntu_98_a11y_fix_crash.diff to fix plasma crashing due to
    ubuntu-specific accessibility patch LP: #1289600
 -- Rohan Garg <email address hidden> Wed, 12 Mar 2014 16:33:21 +0100