Regarding the workflow issue: As a new confused user, it is natural to think that displayconfig-gtk would trust the perception of the hardware that the rest of the OS has (or had at installation time) -- namely the *current settings* -- so I feel it would be logical for displayconfig-gtk to use those settings as default. This would also be an instructive for the user to see what the OS hardware perception is (and what the current settings are).
But what you are saying, Bryce, is that displayconfig-gtk can use *another* auto-detection mechanism? A better one? That would obviously be helpful in cases where the "normal" OS autodetection has failed.. One could have a button that says "Special autodetection" or something, but.. wouldn't functionality like that rather belong somewhere else (in some BulletproofX dialog or something..) I realize that I am confused and have no idea what I am talking about, but hopefully "confused-user-feedback" can be helpful as well. Hugo -- displayconfig-gtk: "Test" fails (scrambled screen) even with default settings https://bugs.launchpad.net/bugs/134706 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
