Bug 1738264 - "External only" monitor setting forgotten after reboot
Summary: "External only" monitor setting forgotten after reboot
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-06 15:53 UTC by Sören Möller
Modified: 2019-08-12 21:57 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-12 21:57:13 UTC
Type: Bug


Attachments (Terms of Use)

Description Sören Möller 2019-08-06 15:53:58 UTC
Description of problem:
When restarting my computer (it seems enough to restart just Wayland) my external monitor setting is not remembered.

Version-Release number of selected component (if applicable):
chrome-gnome-shell-0:10.1-5.fc31.x86_64
libwayland-client-0:1.17.0-2.fc31.x86_64
libwayland-server-0:1.17.0-2.fc31.x86_64

How reproducible:
Happens after each boot and after at least some Wayland crashes.

Steps to Reproduce:
1. Boot Fedora, it ends up in "Mirrored" mode, which same image on both monitors (laptop and external)
2. Change to "External only" (by Super/Windows key + P)
3. Reboot Fedora

Actual results:
Back at "Mirrored mode"

Expected results:
Still in "External only" mode

Additional info:
I recently updated from Fedora 30 to Rawhide. It worked in Fedora 30.

I also noticed that my Num Lock is reset to diabled at every boot, this might be related, but I am not sure.

Comment 1 Sören Möller 2019-08-12 21:57:13 UTC
The bug disappeared for me after one of the last rawhide updates. As I am still on
chrome-gnome-shell-0:10.1-5.fc31.x86_64
libwayland-client-0:1.17.0-2.fc31.x86_64
libwayland-server-0:1.17.0-2.fc31.x86_64
I am not entirely sure which package changed, but the problem did not occur for the last few boots.


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