GNOME Bugzilla – Bug 712325
Don't show a confirmation dialogue for primary screen change
Last modified: 2021-07-05 14:30:47 UTC
The new design in the 3.10 display configuratrion tool requires that the user do many things one step at a time, apply the changes then do the next step.
Here is a video of setting up a complex display that required 4 apply and confirm steps.
I started with just a single monitor turned on, and then needed the 4 apply and confirm steps to achieve my desired layout of:
An approach of setting up all display options in a dialog like the arrangement one, and then applying the changes would reduce the number of apply and confirm steps to 1
*** Bug 712327 has been marked as a duplicate of this bug. ***
The change of primary shouldn't popup a confirmation dialogue, which is a gnome-shell bug.
For the 3 other applies, we could apparently detect whether applications are successful, so it should be instant apply. See bug 635564 for the instant apply without confirmation.\
I'll reassign to gnome-shell for the original bug.
The original bug was that i have to apply 3-4 times. (instant apply is simply a solution to the issue). The behaviour in pre- 3.10 was that the UI allowed me to essentially stage up the changes, then only press apply once.
(In reply to Ryan Lerch from comment #3)
> The original bug was that i have to apply 3-4 times. (instant apply is
> simply a solution to the issue). The behaviour in pre- 3.10 was that the UI
> allowed me to essentially stage up the changes, then only press apply once.
That's covered by bug 773147.
Regarding the confirmation dialog, I've had issues with it being shown on the opposite display from my pointer, which is obviously annoying as you have to find your way to the other display to interact with it.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).
If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
and create a new ticket at
Thank you for your understanding and your help.