-
Notifications
You must be signed in to change notification settings - Fork 89
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
GDM: change sleep-inactive-ac-type default value from 'suspend' to 'nothing' #1834
Comments
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. |
I agree, I can change the default in https://github.com/getsolus/gnome-desktop-branding when we land GNOME 46. |
That would be much appreciated. |
On a related note I'd like to mention that regardless of suspend beeing turned off for GDM with |
@joebonrichie Please do this ASAP for 4.6? |
This is not being included in 4.6, deferring to 4.7 |
Please confirm there isn't an existing open bug report
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
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
The text was updated successfully, but these errors were encountered: