Re: Change in latest update – suspending

Hi, I have no idea what happened or what changed, but I didn't do anything further and yet: [root@lionors ~]# su - gdm -s /bin/sh [gdm@lionors ~]$ gsettings get org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0 and the computer does not auto suspend whilst in "GDM mode".

Re: Change in latest update – suspending

On Sun, 2018-04-01 at 17:46 -0700, Samuel Sieb wrote: > On 04/01/2018 03:08 AM, Russel Winder wrote: > > [root@lavaine ~]# su - gdm -s /bin/sh > > [gdm@lavaine ~]$ gsettings get org.gnome.settings- > > daemon.plugins.power sleep-inactive-ac-timeout > > 1200 > > [gdm@lavaine ~]$ > > > > So the key

Re: Change in latest update – suspending

On 04/01/2018 03:08 AM, Russel Winder wrote: [root@lavaine ~]# su - gdm -s /bin/sh [gdm@lavaine ~]$ gsettings get org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 1200 [gdm@lavaine ~]$ So the key is there (which is wasn't initially) but the value is wrong. I am clearly missing

Re: Change in latest update – suspending

On Tue, 2018-03-20 at 20:38 +0100, Louis Lagendijk wrote: > On Tue, 2018-03-20 at 12:31 -0700, Adam Williamson wrote: > > On Tue, 2018-03-20 at 13:48 +, Russel Winder wrote: > > > On Tue, 2018-03-20 at 13:54 +0100, Kamil Paral wrote: > > > > > > > > > > […] > > > > Nope: > > > >

Re: Change in latest update – suspending

On Tue, 2018-03-20 at 12:31 -0700, Adam Williamson wrote: > On Tue, 2018-03-20 at 13:48 +, Russel Winder wrote: > > On Tue, 2018-03-20 at 13:54 +0100, Kamil Paral wrote: > > > > > > > […] > > > Nope: > > > https://bugzilla.redhat.com/show_bug.cgi?id=1558485 > > > > Exactly, thanks for

Re: Change in latest update – suspending

On Tue, 2018-03-20 at 12:31 -0700, Adam Williamson wrote: > On Tue, 2018-03-20 at 14:49 +0100, Karel Volný wrote: > > ... > > > You can configure this in the Control Center. Settings / Power / > > > Automatic suspend: turn it "off". Now you're done. > > > > beside Kamil's bug, isn't GNOME moving

Re: Change in latest update – suspending

On Tue, 2018-03-20 at 14:49 +0100, Karel Volný wrote: > ... > > You can configure this in the Control Center. Settings / Power / > > Automatic suspend: turn it "off". Now you're done. > > beside Kamil's bug, isn't GNOME moving to Wayland? > > how to configure that when I was unable to run g-c-c

Re: Change in latest update – suspending

On Tue, 2018-03-20 at 13:48 +, Russel Winder wrote: > On Tue, 2018-03-20 at 13:54 +0100, Kamil Paral wrote: > > > > […] > > Nope: > > https://bugzilla.redhat.com/show_bug.cgi?id=1558485 > > Exactly, thanks for posting the bug report. > > Extremely angry is a bit of an understatement! > >

Re: Change in latest update – suspending

... You can configure this in the Control Center. Settings / Power / Automatic suspend: turn it "off". Now you're done. beside Kamil's bug, isn't GNOME moving to Wayland? how to configure that when I was unable to run g-c-c over ssh? - ...

Re: Change in latest update – suspending

On Tue, 2018-03-20 at 13:54 +0100, Kamil Paral wrote: > […] > Nope: > https://bugzilla.redhat.com/show_bug.cgi?id=1558485 Exactly, thanks for posting the bug report. Extremely angry is a bit of an understatement! I do hope the GNOME people accept this as a problem and provide a way of

Re: Change in latest update – suspending

On Mon, 2018-03-19 at 09:16 -0700, Adam Williamson wrote: > […] > Glad to know you're being reasonable and proportional in response to > a > default configuration change! On the one hand :-), on the other hand: the current situation means I have to login to all the computers from the console so

Re: Change in latest update – suspending

On Mon, Mar 19, 2018 at 5:16 PM, Adam Williamson wrote: > > OK so Debian Sid has now fully updated GNOME and it behaves the same as > Fedora > > Rawhide. If you are not logged in on the console, GDM suspends the > computer > > after a few minutes. GNOME has just

Re: Change in latest update – suspending

On Sun, 2018-03-18 at 12:32 +, Russel Winder wrote: > On Sat, 2018-03-17 at 12:09 +, Russel Winder wrote: > > Hi, > > > > Back after a period away. > > > > On Thu, 2018-02-22 at 09:39 -0700, Michal Jaegermann wrote: > > […] > > > > > > This still leaves a question how you are going to

Re: Change in latest update – suspending

On Sat, 2018-03-17 at 12:09 +, Russel Winder wrote: > Hi, > > Back after a period away. > > On Thu, 2018-02-22 at 09:39 -0700, Michal Jaegermann wrote: > […] > > > > This still leaves a question how you are going to modify that for > > gdm on a machine of a type "server - most of the time"?

Re: Change in latest update – suspending

Hi, Back after a period away. On Thu, 2018-02-22 at 09:39 -0700, Michal Jaegermann wrote: […] > > This still leaves a question how you are going to modify that for > gdm on a machine of a type "server - most of the time"? If I understood > Russel correctly such setup is hugely affected. It

Re: Change in latest update – suspending

On Thu, 2018-02-22 at 09:39 -0700, Michal Jaegermann wrote: > On Thu, Feb 22, 2018 at 04:00:44PM +0200, Ahmad Samir wrote: > > On 22 February 2018 at 14:58, Russel Winder wrote: > > > On Thu, 2018-02-22 at 04:04 -0800, Adam Williamson wrote: > > > > […] > > > > > > > >

Re: Change in latest update – suspending

On 22 February 2018 at 18:39, Michal Jaegermann wrote: > On Thu, Feb 22, 2018 at 04:00:44PM +0200, Ahmad Samir wrote: >> On 22 February 2018 at 14:58, Russel Winder wrote: >> > On Thu, 2018-02-22 at 04:04 -0800, Adam Williamson wrote: >> >> […] >> >>

Re: Change in latest update – suspending

On Thu, Feb 22, 2018 at 04:00:44PM +0200, Ahmad Samir wrote: > On 22 February 2018 at 14:58, Russel Winder wrote: > > On Thu, 2018-02-22 at 04:04 -0800, Adam Williamson wrote: > >> […] > >> > >> Anything settable in control-center is likely backed with a dconf key > >> you

Re: Change in latest update – suspending

On 22 February 2018 at 14:58, Russel Winder wrote: > On Thu, 2018-02-22 at 04:04 -0800, Adam Williamson wrote: >> […] >> >> Anything settable in control-center is likely backed with a dconf key >> you could set. > > True. Finding the path to the key is not always obvious

Re: Change in latest update – suspending

On Thu, 2018-02-22 at 04:04 -0800, Adam Williamson wrote: > […] > > Anything settable in control-center is likely backed with a dconf key > you could set. True. Finding the path to the key is not always obvious though. I am guessing that in this case org.gnome.session-daemon may be the place. >

Re: Change in latest update – suspending

On Thu, 2018-02-22 at 11:17 +, Russel Winder wrote: > > > It should be configurable in the Power panel of the control center. > > Do you know if there is there a way of setting it without logging in to > the console device? GNOME will hopefully not then reset a value it has > no right to set

Re: Change in latest update – suspending

Adam, Thanks for the quick answer, much appreciated. I may get grumpy on this one, hopefully no-one takes offence. On Thu, 2018-02-22 at 02:25 -0800, Adam Williamson wrote: > On Thu, 2018-02-22 at 08:39 +, Russel Winder wrote: > > Hi, > > > > I have just done the 3GB update on my machines.

Re: Change in latest update – suspending

On Thu, 2018-02-22 at 08:39 +, Russel Winder wrote: > Hi, > > I have just done the 3GB update on my machines. Now I find that laptops > and workstations go into suspend mode without being told to. For me > this is not what I want. I am assuming the recent big update has > included a change of

Change in latest update – suspending

Hi, I have just done the 3GB update on my machines. Now I find that laptops and workstations go into suspend mode without being told to. For me this is not what I want. I am assuming the recent big update has included a change of setting somewhere. I am not sure where to find this. Can anyone