On Wed, Oct 05, 2011 at 08:59:43PM +0200, Sebastien Bacher wrote: > Le mercredi 05 octobre 2011 à 11:17 -0700, Bryce Harrington a écrit : > > It looks to me like it basically works, modulo maybe a bug or two. > > So removing it seems unnecessary; just need to isolate and prioritize > > those bugs. > > I'm not convinced about that, the bug has a count of 325 users having > the issue (which is quite high compared to most desktop bugs we get) and > it's a point that comes often on user forums as something being broken > in Ubuntu, I would like to get extra datas ... maybe we should do a call > for testing on it during the Oneiric rc testing?
Yeah, that bug (#353126) is open for over two years so re-testing is a good idea. I notice in particular many of the bugs listed as dupes are in the 300000-400000 range, with only one filed in the natty timeframe. The comments from 2011 are all either from people running older Ubuntu's, or -fglrx, or don't specify. I wish we could track and see what distro version those Affects Me were reporting against, or when they were set. It is possible most of those were from Lucid/nvidia users (who gained the fix in a later release), but we don't know. Looking at the dupes and comments it seems like a valid guess. Anyway, a call for testing during oneiric rc seems a good suggestion. But I think as a next action, I think I have all the hardware I need to test it myself, so I'll try and do that today or tomorrow. I would hate to spin up a bunch of people to do testing if there really are obvious breakages... > Testing that feature regularly in the feature seems a good idea indeed Is this something the QA could / would be willing to do? Seb, do you know if vino has a way to automatedly turn it on & config it ala dbus or something? Bryce -- ubuntu-desktop mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
