The use-case involving "open displayconfig-gtk, just hit Test and your screen will change" _may_ sound a bit contrived.. But that is pretty much what will happen in the following scenario:
I want to add a second screen to my laptop. So I plug in the cable and turn the second screen on. Then I open displayconfig-gtk. I click "Screen 2" and configure it as a Secondary screen, and enter Manufacturer and Model and all that. I hit the Test button. Now my _primary_ screen turns gray and ugly. I had not expected that, and I hear my self thinking "I didn't even touch the configuration for my primary screen. Why did it change? What did I do wrong? The primary screen settings were working well. Why didn't displayconfig-gtk just trust them, since those were the settings that were configured by ... the LiveCD-installation procedure or whatever?" So what would be a better UI solution then? Hmmm.. Should displayconfig- gtk perhaps behave _differently_ in the "normal context" (where nothing is broken), as opposed to the context of the BulletProofX "safe mode" when X has failed? -- 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
