Bug 1517967
| Summary: | Docked system suspended with lid closed | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Russell Doty <rdoty> |
| Component: | gnome-desktop | Assignee: | Ray Strode [halfline] <rstrode> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 27 | CC: | alexl, bnocera, caillon+fedoraproject, fmuellner, gnome-sig, john.j5live, mclasen, redhat-bugzilla, rhughes, rstrode, sandmann, warlock.cc, yselkowi |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-11-30 18:45:18 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Russell Doty
2017-11-27 18:57:20 UTC
Update: may be more external display problem than suspend problem. 1. Dock system. 2. Press power button on dock to bring system out of suspend. 3. System is live but external display remains blank until the laptop lid is opened. System accepts keyboard input - I'm able to enter a password and have a live desktop session when I open the lid. More info: 1. Laptop docked, lid open, and both laptop and external displays live 2. Close lid 3. Results: external display blanks. Laptop does not suspend. External screen remains unresponsive, even when entering <return> 4. Open laptop lid: external display comes back to life. Lock screen is showing; have to enter password to unlock session. Also, if you enter <return> and your password while the laptop is closed, the session is live when you open the laptop lid. I can confirm this on a Lenovo ThinkPad T530.
A possible clue... prior to closing the lid, systemd-inhibit lists (among other things) an lid-switch inhibitor for both the gdm and my own sessions:
"""
Who: gdm (UID 42/gdm, PID 1859/gsd-power)
What: handle-lid-switch
Why: Multiple displays attached
Mode: block
Who: mchapman (UID 1000/mchapman, PID 2605/gsd-power)
What: handle-lid-switch
Why: Multiple displays attached
Mode: block
"""
However, after closing the lid, the inhibitor for my session goes away, leaving just:
"""
Who: gdm (UID 42/gdm, PID 1859/gsd-power)
What: handle-lid-switch
Why: Multiple displays attached
Mode: block
"""
I was not able to see any point at which this inhibitor went away.
So there's a few confusing things here. First, why would my session's gsd-power think there were no longer multiple displays attached when the lid was closed? Second, why does the inhibitor for gdm session's gsd-power *not* go away when the lid is closed... perhaps because that session is in the background? Third, even with one of these inhibitors gone there's still a second one, so why would logind suspend the system?
If I add a *manual* inhibitor with:
systemd-inhibit --what handle-lid-switch cat
then logind does not the suspend the system when the lid is closed (though my external screen still turns off).
Having this exact issue. It seems to be fixed upstream although I haven't tested it myself. See https://bugzilla.gnome.org/show_bug.cgi?id=788915 (In reply to Rodolfo Granata from comment #4) > Having this exact issue. It seems to be fixed upstream although I haven't > tested it myself. > > See https://bugzilla.gnome.org/show_bug.cgi?id=788915 I just tested the patches there on mutter-3.26.2-1. They seem to fix this problem for me. (In reply to Michael Chapman from comment #5) > (In reply to Rodolfo Granata from comment #4) > > Having this exact issue. It seems to be fixed upstream although I haven't > > tested it myself. > > > > See https://bugzilla.gnome.org/show_bug.cgi?id=788915 > > I just tested the patches there on mutter-3.26.2-1. They seem to fix this > problem for me. Patched mutter myself, also seems to fix the issue. This is now working for me. Feel free to close this bug. This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |