Re: hybrid-sleep with Gnome

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 10/5/18 6:11 AM, Wolfgang Pfeiffer wrote:
Short version: Suspend works perfectly here (except when a 2nd monitor
is attached) on a laptop with a running GDM 3.26.2.1, kernel
4.18.7-250.vanilla.knurd.1.fc27.x86_64. Window manager is awesome v4.2.
Simply closing the lid suspends the machine to S3 sleep) [1].

I think you are misunderstanding. Suspend works fine for me as well. However, the laptop hardware seems to have a problem where pressing the power button sometimes doesn't resume. I would like to use hybrid-sleep instead as a workaround.

In your first message I saw something I don't understand:

Quote:
Sure enough, from "systemd-inhibit":
     Who: samuel (UID 1000/samuel, PID 1667/gsd-media-keys)
    What: handle-power-key:handle-suspend-key:handle-hibernate-key
     Why: GNOME handling keypresses
    Mode: block

Could it be you block samuel from putting the system to sleep because
Gnome is handling keypresses? - Yes, I know that sounds weird. But
maybe it's that situation that confuses the system.

Not sure what you're saying here. My user is "samuel", so gsd (Gnome Settings Daemon) is running as my user. It is handling the keys, so that logind can't handle them. Then Gnome will only do suspend because there's no way to tell it otherwise.

And I don't find any UID 1000 listings here with
"systemd-inhibit --list"

But this:
% systemd-inhibit --list | grep -A4 -i gdm
     Who: gdm (UID 42/gdm, PID 2173/gsd-media-keys)
    What: handle-power-key:handle-suspend-key:handle-hibernate-key
     Why: GNOME handling keypresses
    Mode: block

     Who: gdm (UID 42/gdm, PID 2176/gsd-power)
    What: sleep
     Why: GNOME needs to lock the screen
    Mode: delay

(Note: no Gnome is used for locking the screen here: awesome, as
mentioned, is running ..)

You're using gdm as the login manager, so that's where those come from.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux