Bug 2073406 - Win+P (or the multimedia key) doesn't configure monitors properly, always switches to Mirror and native resolution
Summary: Win+P (or the multimedia key) doesn't configure monitors properly, always swi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Florian Müllner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedFreezeException
Depends On:
Blocks: F36FinalFreezeException
TreeView+ depends on / blocked
 
Reported: 2022-04-08 12:18 UTC by Kamil Páral
Modified: 2023-08-16 13:35 UTC (History)
8 users (show)

Fixed In Version: gnome-shell-42.0-3.fc36
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-19 22:04:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME gnome-control-center issues 1748 0 None opened Win+P (or the multimedia key) doesn't configure monitors properly, always switches to Mirror and native resolution 2022-04-08 12:23:35 UTC

Description Kamil Páral 2022-04-08 12:18:41 UTC
Description of problem:
When running GNOME 42, I can no longer configure monitors using Win+P (Super+P, laptop multimedia key) shortcut. Even though I see 4 options called Mirror, Join Displays, External Only and Built-in Only, choosing any those always changes the layout to Mirror.

Additionally, if you have a different resolution configured for your display (other than the native, highest one), it also resets your resolution to the native one.

Overall, Win+P can't be used at all. This is a regression from GNOME 41, where Win+P worked correctly.

Note: Configuring monitors directly in GNOME Settings -> Displays works correctly. It's only the Win+P shortcut which is broken.

See the upstream issue for full description:
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1748

Comment 1 Kamil Páral 2022-04-08 12:23:35 UTC
Proposing as a prioritized bug. While I don't think this can be a release blocker, this is likely going to bite a lot of dual-monitor users. Especially on laptops, it is common to configure your displays using the multimedia key, e.g. to enable/disable the internal display when presenting, after docking, etc.

Comment 2 Kamil Páral 2022-04-11 08:13:05 UTC
The issue is already fixed in https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2245 . We just need it updated in Fedora, ideally before F36 Final. Removing PrioritizedBug nomination and instead proposing as a Freeze Exception.

@Florian, could you please include this patch in Fedora?

Comment 3 František Zatloukal 2022-04-11 18:27:37 UTC
Discussed during the 2022-04-11 blocker review meeting: [1]

The decision to classify this bug as an AcceptedFreezeException was made:

"It is a noticeable issue that cannot be fixed with an update."

[1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2022-04-11/f36-blocker-review.2022-04-11-16.00.log.txt

Comment 4 Fedora Update System 2022-04-18 22:03:58 UTC
FEDORA-2022-d0c4cc0d54 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d0c4cc0d54

Comment 5 Kamil Páral 2022-04-19 11:59:35 UTC
(In reply to Fedora Update System from comment #4)
> FEDORA-2022-d0c4cc0d54 has been submitted as an update to Fedora 36.
> https://bodhi.fedoraproject.org/updates/FEDORA-2022-d0c4cc0d54

Win+P now works as expected, thanks!

Comment 6 Fedora Update System 2022-04-19 17:27:41 UTC
FEDORA-2022-d0c4cc0d54 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-d0c4cc0d54`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d0c4cc0d54

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2022-04-19 22:04:20 UTC
FEDORA-2022-d0c4cc0d54 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.