Based on #16, I submit the same question as I asked in #14... "Ready for me to test another 12.04 --> 14.04 LTS upgrade at this point?" Please confirm and I will kick one off.
Since it says "Please test proposed package" in #16, is there any special steps I need to perform when doing the LTS upgrade to insure I actually test the proposed package? -- You received this bug notification because you are a member of Mythbuntu Bug Team, which is subscribed to Mythbuntu. https://bugs.launchpad.net/bugs/1307546 Title: dist-upgrade from 12.04 -> 14.04 axes /etc/X11/xorg.conf Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Confirmed Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “ubuntu-release-upgrader” package in Ubuntu: Invalid Status in “ubuntu-drivers-common” source package in Trusty: Fix Committed Status in “ubuntu-release-upgrader” source package in Trusty: Invalid Bug description: [Impact] * Upon upgrading to Ubuntu 14.04 from an earlier LTS release the user's xorg.conf is renamed. Any custom settings they've made will be removed. * Specifically for Mythbuntu 12.04 LTS users with NVIDIA graphics, they have a custom DPI setting that gets removed upon upgrade to 14.04. * This has been fixed in utopic by testing if it's the first time that ubuntu-drivers has ran. If so, it sets a first boot flag so that no settings are removed. [Test Case] * This can be reproduced by installing a 12.04 based release, creating an xorg.conf and upgrading to 14.04. If the xorg.conf is renamed then the bug is hit. * This can also be reproduced directly on 14.04 by removing /var/lib /ubuntu-drivers-common/last_gfx_boot, creating an xorg.conf and rebooting. This would simulate the same behavior. [Regression Potential] * Part of the intention of ubuntu-drivers-common is to prevent problems on people who have upgraded and now have hybrid graphics supported cards. This won't make their situation any worse than previously it would have been before ubuntu-driver-common existed. * Any functional users in the field should still remain functional. This only affects the first boot scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1307546/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mythbuntu-bugs Post to : mythbuntu-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~mythbuntu-bugs More help : https://help.launchpad.net/ListHelp
