After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 711309 - Screens can't be inverted in the new Displays Manager
Screens can't be inverted in the new Displays Manager
Status: RESOLVED DUPLICATE of bug 715092
Product: gnome-control-center
Classification: Core
Component: Display
3.10.x
Other Linux
: Normal normal
: ---
Assigned To: Debarshi Ray
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-11-02 20:02 UTC by adria.arrufat
Modified: 2013-12-17 09:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description adria.arrufat 2013-11-02 20:02:13 UTC 
With the new Displays Manager introduced in GNOME 3.10, screens can't be inverted any more.

This was a feature I was using with my convertible ThinkPad x220T.

It would also be nice if we could set the whole configuration before applying the changes, that is: set the screens resolution, orientation and relative position before applying the changes.

Right now we have to apply the changes for each screen, and as a final step, the relative position. This, in my opinion, is a usability regression, since once we apply the changes before setting the relative position, we have to play around with the mouse to reach the screen where the confirmation dialogue appears...

Thanks

Adrià
Comment 1 Arnaud B. 2013-12-16 22:36:02 UTC 
Same (main) problem here with another convertible-laptop (HP Pavillon tx2500). To clarify the problem: the battery I have is thicker than the computer (in laptop mode, the keyboard is inclined), so it’s difficult to hold it in tablet mode with the battery near you.
Comment 2 Bastien Nocera 2013-12-17 09:02:15 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 715092 ***