[SRU]full-screen switching is broken

I don't plan to fix zesty, should I?

Yes, this should be fixed in Zesty as an upgrade from Xenial to Zesty is supported.

uploaded for zesty too

Hello stsp, or anyone else affected,

Accepted libsdl2 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libsdl2/2.0.4+dfsg1-2ubuntu2.16.04.1 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 on 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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 stsp, or anyone else affected,

Accepted libsdl2 into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libsdl2/2.0.5+dfsg1-2ubuntu3.17.04.1 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 on 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-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. 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!

The fix for this bug has been awaiting testing feedback in the -proposed repository for xenial for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository.

Isn't it just a packaging of a more recent SDL?
Should I indeed test it explicitly so that it
not to be removed?
I tested this fix directly from SDL repository
before reporting the problem here.

@stsp please test the proposed package, thanks

So I have 2.0.6+dfsg1-3ubuntu1 already installed,
and there seem to be no bug. But I have not used
the -proposed repo for this.
So is it possible that the fixed packages are
already in the main Artful repo and we don't have
to care?

Well its definitely in 2.0.6.
It was released in 17 Sep 2017:
https://discourse.libsdl.org/t/sdl-2-0-6-released/23109
and the fix was committed at 2017-04-03.
So my suggestion is to just mark this as fixed.

@stsp can you please test the xenial proposed package on a xenial machine?
thanks!

What's the status of the verification here? The libsdl2 xenial SRU has been marked for removal due to the lack of fix verification. Could someone test it by any chance? If not, I'll have to remove the package from -proposed.

Feel free to remove the patched package.
The fix was applied 2 years ago.

nobody (including me) reported new bugs in the xenial-proposed package, so I guess it can land safely now.

I used the package for some time when I built it, and then I switched to bionic, but I never encountered regressions.

We would need someone to perform real testing on this. Can you or someone else actually pick up a xenial machine/kvm, upgrade the package from -proposed and see if the original bug can be reproduced (with e.g. dosemu2)?

But why not to have the unpatched new upstream
version that already contains the fix? Or is
xenial in a freeze mode and updated packages
are not accepted?

@stsp is it not possible to release new versions in stable Ubuntus. (not usually permitted)

@sil2100, I had troubles in setup a virtual machine, but I think everything went fine in my testing (I tried xmonad/dosemu2)!

@costamagnagianfranco - "I think everything went fine" does not install a lot of confidence in me so I'm setting it back to verification-needed.

Thank you for taking the time to verify this stable release fix. We have noticed that you have used the verification-done tag for marking the bug as verified and would like to point out that due to a recent change in SRU bug verification policy fixes now have to be marked with per-release tags (i.e. verification-done-$RELEASE). Please remove the verification-done tag and add one for the release you have tested the package in. Thank you!

https://wiki.ubuntu.com/StableReleaseUpdates#Verification

fullscreen dosemu2 running

This bug was fixed in the package libsdl2 - 2.0.4+dfsg1-2ubuntu2.16.04.1

---------------
libsdl2 (2.0.4+dfsg1-2ubuntu2.16.04.1) xenial; urgency=medium

  * Cherry-pick upstream fix for full-screen switching mode
    LP: #1679573

 -- Gianfranco Costamagna <email address hidden> Sat, 11 Nov 2017 10:55:43 +0100

The verification of the Stable Release Update for libsdl2 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 regressions.