Re: sleep/suspend

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

 



>
> On Sat, 2025-07-05 at 12:55 +0200, Patrick Dupre via users wrote:
> >> On Fri, 2025-07-04 at 11:31 +0200, Patrick Dupre via users wrote:  
> >>> Jul  4 11:01:41 Sappho systemd-logind[1868]: Error during inhibitor-
> >>> delayed operation (already returned success to client): Unit
> >>> sleep.target is masked.  
> 
> >> I don't know if that line in your log (with sleep.target is masked)
> >> in it is pertinent.  
> 
> > How could I turn it unmask?
> 
> See below.
> 
> >> I see other comments on the net about NVidia being a problem in
> >> this area.  Do you use it?
> 
> > No
> 
> > But it has been working fine in the past
> > I had to turn of because I used the laptop as a server.
> 
> > sudo -u gdm dbus-run-session gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0
> 
> > After that I did not test.
> > It is only now that I need to turn it to suspend.  
> 
> I suspect you also masked the sleep.target unit in addition of setting
> this sleep-inactive-ac-timeout to 0 for gdm
> 
> Have you noted all the actions you did to configure this laptop as a
> server?
> 
> To correct that:
> 
>   1) List the /etc/systemd/system/sleep.target link to see at what
>      time you masked sleep.target.
> 
>      Execute: ls -l /etc/systemd/system/sleep.target
> 
>   2) Unmask sleep.target.
> 
>      Execute: sudo 06
> 
> Then retry to suspend.

Thank Francis,
before I run systemctl unmask sleep.target, I had
/etc/systemd/system/sleep.target -> /dev/null
and after
ls -l /etc/systemd/system/sleep.target
ls: cannot access '/etc/systemd/system/sleep.target': No such file or directory

and 
systemctl suspend
works!

Indeed I could have guess because I previously run systemctl unmask hibernate.target

However, I did not run sudo 06
What is it supposed to do?



> 
> -- 
> francis
> -- 

-- 
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[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