Comment 9 for bug 262152

@ Dmik: Simple is a relative word, but here goes: The first workaround I did to restore 0.6 behavior was to add Hardy's repositories back into software sources, then use aptitude to downgrade all five related packages to 0.6.x and mark them Held at the older version. That worked fine, but it was annoying to have update-manager and synaptic keep telling me there were upgrades available to 0.7. Once I realized how many 0.7 bugs have been reported, and thus how long it is likely to be before I would want to try an allegedly fixed 0.7, I decided to just get the five binary .deb packages, unpack them, change the version numbers to 0.7+0.6.x, re-deb them, and install those "newer" packages. That worked fine too, but of course will be a problem as soon as 0.7 gets into a high enough version to supersede my 0.7+0.6.x versions. My full rant page on 0.7 vs 0.6 is http://www2.nau.edu/wal2/NetworkManager/Readme.html . Admittedly, my main problems were with the pptp plugin, but I confirm the specific issue(s) addressed by Bug 262152. There are dozens upon dozens of bugs reported for 0.7, some of which are being actively worked upon, some not, and some not confirmed. I wonder whether, for the bugs that ARE being worked on, is all of that work being coordinated and merged. I wonder if it is possible, and whether it would make any sense, to create a much more inclusive bug for 0.7 and start marking the dozens upon dozens of existing bugs as duplicates of the new all-inclusive bug. Each of those other bugs seems to be nibbling around the edges of the much larger problem. I wonder how much QA was done on 0.7 before it was decided to put it, rather than 0.6, into 8.10 Intrepid and 9.04 Jaunty.