Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GDM: change sleep-inactive-ac-type default value from 'suspend' to 'nothing' #1834

Open
2 tasks done
sebo505 opened this issue Mar 9, 2024 · 6 comments · May be fixed by getsolus/gnome-desktop-branding#22
Open
2 tasks done
Assignees
Labels
Bug Something isn't working Edition: GNOME Issues related to the GNOME Desktop Environment Priority: Normal Normal priority

Comments

@sebo505
Copy link

sebo505 commented Mar 9, 2024

Please confirm there isn't an existing open bug report

  • I have searched open bugs for this issue

Summary

This is tightly related to (T10537) #193

With GDM as login manager, if you don't login right away after boot, after a certain amount of inactivity, computer suspends automatically, regardless of users energy/suspend settings. For GDM, these settings can be changed via gesettings run as gdm user:
su - gdm -s /bin/sh
dbus-launch --exit-with-session gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'nothing'
or via the config file in /etc/dconf/db/gdm.d/ as described in the above mentioned issue.

My personal stance is that auto-suspend-on-inactivity should be deactivated per default in GDM, at least if you are on ac.
I understand the value of auto-suspend if you run on battery, but given that there are users for who wakeup after suspend does not work properly, for instance graphics not initalizing correctly, I would rather deactivate this.
You can still trigger suspend manually in GDM, and I think suspend is also still triggered if you close lid.

Steps to reproduce

boot computer
on login-screen (GDM), don't login right away, wait like 6 min

Expected result

suspend should not be triggered

Actual result

suspend is triggered

Environment

  • Is system up to date?

Repo

Shannon (stable)

Desktop Environment

GNOME

System details

Hardware Information:

Hardware-Modell: Hewlett-Packard HP EliteBook 6930p
Speicher: 8,0 GiB
Prozessor: Intel® Core™2 Duo T9550 × 2
Grafik: AMD RV620
Festplattenkapazität: 250,1 GB

Software Information:

Firmware-Version: 68PCD Ver. F.16
Name des Betriebssystems: Solus 4.5 Resilience
Betriebssystem-Build: (null)
Betriebssystem-Typ: 64-bit
GNOME-Version: 45.3
Fenstermanager: X11
Kernel-Version: Linux 6.6.12-271.current

Other comments

No response

@sebo505 sebo505 added the Bug Something isn't working label Mar 9, 2024
@github-project-automation github-project-automation bot moved this to Triage in Solus Mar 9, 2024
@sebo505
Copy link
Author

sebo505 commented Mar 9, 2024

Just to give a further explanation why I think current GDM behaviour is no good: I think for example of my parents, 70 and 80 years old. Scenario is the following: They start computer, then, while it's booting, they decide to go make a tea, or to check washing machine, or whatever, and then, when they return after a short while, before they even had the chance to login, computer is already in suspend and they don't understand whats going on.

@joebonrichie
Copy link
Contributor

I agree, I can change the default in https://github.com/getsolus/gnome-desktop-branding when we land GNOME 46.

@sebo505
Copy link
Author

sebo505 commented Mar 9, 2024

That would be much appreciated.

@sebo505
Copy link
Author

sebo505 commented Apr 2, 2024

On a related note I'd like to mention that regardless of suspend beeing turned off for GDM with
su - gdm -s /bin/sh
dbus-launch --exit-with-session gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'nothing'
GDM screen will go blank after some time.
If screen blanking in GDM is undesired, this can be changed with
su - gdm -s /bin/sh
dbus-launch --exit-with-session gsettings set org.gnome.desktop.session idle-delay '0'

@ermo ermo moved this from Triage to Ready in Solus May 4, 2024
@ermo ermo added this to the Solus 4.6 milestone May 4, 2024
@ermo
Copy link
Contributor

ermo commented May 4, 2024

@joebonrichie Please do this ASAP for 4.6?

@TraceyC77
Copy link
Contributor

This is not being included in 4.6, deferring to 4.7

@TraceyC77 TraceyC77 modified the milestones: Solus 4.6, Solus 4.7 Oct 13, 2024
@TraceyC77 TraceyC77 added the Edition: GNOME Issues related to the GNOME Desktop Environment label Nov 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Edition: GNOME Issues related to the GNOME Desktop Environment Priority: Normal Normal priority
Projects
Status: Ready
Development

Successfully merging a pull request may close this issue.

4 participants