Same experience as #40 after installing updates on 16.04 today. I already have the workaround from #4 applied. The workaround from #35 appears to still work, thankfully.
Same experience as #40 after installing updates on 16.04 today.
I already have the workaround from #4 applied.
The workaround from #35 appears to still work, thankfully.