Running an Acer Aspire 5332 with 16.04 pretty much a fresh install from last week.
The patch did fix the problem, eventually, but on the first boot none of the X clients connected to the display, so all I had was a mouse pointer.
logged in via Alt-F1 console and ran an Xterm with :0 DISPLAY env var, but that didn't connect (although it showed no errors on stderr).
Then rebooted once more, and it all started working OK.
So - if it doesn't work first time, you might want to try another reboot.
P.S. love all the "dependency" problems above - NOT - oh for the good old days where libraries had fixed API's and you could mix and match different version.
Running an Acer Aspire 5332 with 16.04 pretty much a fresh install from last week.
The patch did fix the problem, eventually, but on the first boot none of the X clients connected to the display, so all I had was a mouse pointer.
logged in via Alt-F1 console and ran an Xterm with :0 DISPLAY env var, but that didn't connect (although it showed no errors on stderr).
Then rebooted once more, and it all started working OK.
So - if it doesn't work first time, you might want to try another reboot.
P.S. love all the "dependency" problems above - NOT - oh for the good old days where libraries had fixed API's and you could mix and match different version.