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 790687 - Screen Settings lost after logging in from lock screen
Screen Settings lost after logging in from lock screen
Status: RESOLVED OBSOLETE
Product: mutter
Classification: Core
Component: general
3.26.x
Other Linux
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
triaged
Depends on:
Blocks:
 
 
Reported: 2017-11-21 23:33 UTC by Andy
Modified: 2021-07-05 13:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
modetest (807 bytes, text/plain)
2017-11-23 19:56 UTC, Andy
Details
gdbus call -e -d org.gnome.Mutter.DisplayConfig -o /org/gnome/Mutter/DisplayConfig -m org.gnome.Mutter.DisplayConfig.GetResources (4.80 KB, text/plain)
2017-11-23 19:57 UTC, Andy
Details
gdbus call -e -d org.gnome.Mutter.DisplayConfig -o /org/gnome/Mutter/DisplayConfig -m org.gnome.Mutter.DisplayConfig.GetCurrentState (3.18 KB, text/plain)
2017-11-23 19:57 UTC, Andy
Details
modetest when issue occurred (12.44 KB, application/octet-stream)
2018-04-16 22:36 UTC, Andy
Details
gdbus … GetCurrentState when issue occurred (2.21 KB, application/octet-stream)
2018-04-16 22:37 UTC, Andy
Details
gdbus … GetResources when issue occurred (3.60 KB, application/octet-stream)
2018-04-16 22:38 UTC, Andy
Details

Description Andy 2017-11-21 23:33:51 UTC
My screen settings were:

* External Screen ON
* Internal Screen Off

After locking my screen and then logging back in, these settings are lost. Both screens are ON, which is my main issue.

Before a recent minor upgrade somehow the internal screen would be on, but not display anything. It's backlight would be on and I'd have the glitches that you see when using a high resolution screen on a two weak graphics card in Wayland.

The main issue occurred only after upgrading to Gnome 3.26 along with F27.
Comment 1 Rui Matos 2017-11-22 11:01:30 UTC
X or wayland session?
Comment 2 Andy 2017-11-22 19:54:24 UTC
thanks for looking into it.

I'm running wayland
Comment 3 Rui Matos 2017-11-23 14:18:50 UTC
Please attach a file with the output of the command "sudo modetest"
And also, please attach the output of the following two commands:

gdbus call  -e -d org.gnome.Mutter.DisplayConfig -o /org/gnome/Mutter/DisplayConfig -m org.gnome.Mutter.DisplayConfig.GetResources


and


gdbus call  -e -d org.gnome.Mutter.DisplayConfig -o /org/gnome/Mutter/DisplayConfig -m org.gnome.Mutter.DisplayConfig.GetCurrentState
Comment 4 Andy 2017-11-23 19:56:39 UTC
Created attachment 364289 [details]
modetest
Comment 5 Andy 2017-11-23 19:57:13 UTC
Created attachment 364290 [details]
gdbus call  -e -d org.gnome.Mutter.DisplayConfig -o /org/gnome/Mutter/DisplayConfig -m org.gnome.Mutter.DisplayConfig.GetResources
Comment 6 Andy 2017-11-23 19:57:32 UTC
Created attachment 364291 [details]
gdbus call  -e -d org.gnome.Mutter.DisplayConfig -o /org/gnome/Mutter/DisplayConfig -m org.gnome.Mutter.DisplayConfig.GetCurrentState
Comment 7 Andy 2017-11-23 20:00:05 UTC
Hm I tried quickly reproducing the problem for these commands, but I couldn't.

Maybe the problem is when the screen goes to standby after some minutes.

I'm also seeing the problem that the external screen is suddenly configured for a really low resolution, I think 1024. I need to re-plug it to be recognized with the right settings.
Comment 8 Andy 2018-04-16 22:07:58 UTC
Actually the too low resolution is 1600, and I'm still seeing the issue.

Recently I noticed that I've been running X instead of Wayland for a while, and I think the issue occurred even there.

Could you make sense of the logs?

Thanks
Comment 9 Andy 2018-04-16 22:34:34 UTC
I just could reproduce the issue, I'll attach again the output of the files while my external screen shows 1600 only.
Comment 10 Andy 2018-04-16 22:36:50 UTC
Created attachment 371002 [details]
modetest when issue occurred
Comment 11 Andy 2018-04-16 22:37:36 UTC
Created attachment 371003 [details]
gdbus … GetCurrentState when issue occurred
Comment 12 Andy 2018-04-16 22:38:08 UTC
Created attachment 371004 [details]
gdbus … GetResources when issue occurred
Comment 13 GNOME Infrastructure Team 2021-07-05 13:43:38 UTC
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
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/mutter/-/issues/

Thank you for your understanding and your help.