Hello Michael Clark (the previous message was directed at Michael Vogt)
This problem just appears if Wine is compiled with GCC 4.9. When Wine 1.6 was released this wasn't the case. So Ubuntu (and other dists) introduced this bug when they compiled with the "wrong" GCC. Just have a look at the upstream bug report, especially https://bugs.winehq.org/show_bug.cgi?id=36139#c17 where upstream said that this should be fixed by the distros because there won't be a 1.6.3.
Anyway, this is a bug which makes Wine1.6 in Trusty unusable in many cases, while it is easy to solve with low regression potential as Michael Vogt correctly indicated.
I'm well aware of the fact that this was fixed in 1.7.20, and that you can install a recent version from the PPA.
Still I think a LTS shouldn't go with a broken Wine, even if it is just in Universe. Therefore my pledge to Michael Vogt.
Hello Michael Clark (the previous message was directed at Michael Vogt)
This problem just appears if Wine is compiled with GCC 4.9. When Wine 1.6 was released this wasn't the case. So Ubuntu (and other dists) introduced this bug when they compiled with the "wrong" GCC. Just have a look at the upstream bug report, especially https:/ /bugs.winehq. org/show_ bug.cgi? id=36139# c17 where upstream said that this should be fixed by the distros because there won't be a 1.6.3.
Anyway, this is a bug which makes Wine1.6 in Trusty unusable in many cases, while it is easy to solve with low regression potential as Michael Vogt correctly indicated.
I'm well aware of the fact that this was fixed in 1.7.20, and that you can install a recent version from the PPA.
Still I think a LTS shouldn't go with a broken Wine, even if it is just in Universe. Therefore my pledge to Michael Vogt.