Yes I was thinking that... My development desktop (which is always a
fresh install) does not experience this bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1874219
Ti
I've just set up a brand new workstation with Ubuntu Desktop 20.04, and
it does not seem to be affected. It has been sitting at the login
screen for 8 hours and has not suspended.
Is it possible that only upgrades could be affected by this?
--
You received this bug notification because you are
@vanvugt: Thanks, 'sudo systemctl isolate multi-user.target' does
prevent the autosuspend.
Although it doesn't survive a reboot, so maybe if one needs something
more persistent:
sudo systemctl set-default multi-user.target
--
You received this bug notification because you are a member of Desk
A better workaround might be to turn off the graphical login screen (and
GNOME everything) while you're working remotely:
sudo systemctl isolate multi-user.target
Then later to turn it back on run:
sudo systemctl isolate graphical.target
--
You received this bug notification because you ar
@vanvugt: Enabling automatic login might do the trick, thanks.
Ideally, I'd like to figure out exactly which setting needs to be changed.
I'll poke some more.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubu
@seb128: As you wrote in LP: #1868260, having autosuspend on AC by
default is not a great user experience.
It's frustrating for those who want to leave their workstations running
and access them remotely during lockdown.
--
You received this bug notification because you are a member of Desktop
P
I don't experience this problem on my server, which is always running.
Perhaps because I am always logged in and the screen is locked when I'm
away. Is that a suitable workaround?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-sett
@marcustomlinson: Thanks, that seemed to copy over the settings, but that
didn't help.
I guess then this is not quite the same as LP: #1759325, although the behaviour
is similar.
I've also tried the following, to no avail:
sudo -u gdm dbus-launch gsettings set org.gnome.desktop.screensaver
loc
Surely it is a bug in gnome-control-center if it's something people
would like to configure? Or a wishlist enhancement?
** Changed in: gnome-control-center (Ubuntu)
Status: Invalid => Opinion
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Wishlist
--
You receiv
Thank you for your bug report but that's not a bug, just modern industry
energy standards. gdm isn't respecting your user settings since it's not
a process owned by your user, it would be nice if it provided a
configuration tools but that's not a bug in gnome-control-center
** Changed in: gnome-co
If your user account is configured to not suspend, you could copy the
settings over to GDM like this:
IFS=$'\n'; for x in $(sudo -u username gsettings list-recursively
org.gnome.settings-daemon.plugins.power); do eval "sudo -u gdm dbus-
launch gsettings set $x"; done; unset IFS
where 'username' i
** Tags added: focal
** Also affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-control-center (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://
13 matches
Mail list logo
