Comment 0 for bug 1176449
Revision history for this message
| Lonnie Lee Best (launchpad-startport) wrote Need to Ensure Launches to Source Monitor | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
We need to add code (somewhere), to ensure that the Display Settings dialog, always launches into the the Monitor (and workspace) from which the launch was initiated. Here's why:
Today, after plugging in an external monitor, Ubuntu added it just fine, but the monitor complained about not having a signal; the resolution to the monitor was set too high.
I attempted to configure the monitor by going to:
System Settings > Display
However, the Display settings dialog launched into the the *non-functioning* monitor. So, I unplugged that monitor, and then the Display Settings dialog returned to my laptop's native monitor, BUT, it wouldn't show the external monitor because it was obviously now unplugged!
As soon as I again plug in the external monitor, the Display settings dialog gets moved to that non functioning monitor (again) and then it is therefore inaccessible for configuring that monitor. All I needed to do was reduce the resolution Ubuntu was telling that external monitor to display at, but Unity always moves the Display settings dialog to the non-functioning monitor I'm trying to configure!
So, in the case of the Display settings dialog, this is one dialog where we must ensure that it gets launched into a monitor that is functioning. That's why it should launch to the monitor and workspace from which the launch was initiated, because that's the one that's obviously working, right?
There are more general bug reports that discuss this type of undesired behavior in a number of other applications:
https:/
However, this bug report is explicitly emphasizing that it is crucial for the "Display Settings" dialog to remain on the monitor and workspace that it is launched from.