On 2/18/25 4:06 AM, Patrick Dupre via users wrote:
Hello,
Does something change since the last update of fedora 40?
I have a laptop running applications from itself or/and from ssh.
Now it falls to sleep after a few minutes despite that I have
org.gnome.settings-daemon.plugins.power sleep-ina
| | email: pdu...@gmx.com
===
> Sent: Tuesday, February 18, 2025 at 3:36 PM
> From: "Jeffrey Walton"
> To: "Community support for Fedora users"
> Cc: "Patrick Dupre"
> S
On Tue, Feb 18, 2025 at 7:07 AM Patrick Dupre via users
wrote:
>
> Hello,
>
> Does something change since the last update of fedora 40?
>
> I have a laptop running applications from itself or/and from ssh.
>
> Now it falls to sleep after a few minutes despite that I have
>
> org.gnome.settings-dae
On 18 Feb 2025 at 13:06, Patrick Dupre via users wrote:
To: fedora
Subject:Sleeping
Date sent: Tue, 18 Feb 2025 13:06:40 +0100
Send reply to: Community support for Fedora users
From: Patrick Dupre via users
Copies to
Hello,
Does something change since the last update of fedora 40?
I have a laptop running applications from itself or/and from ssh.
Now it falls to sleep after a few minutes despite that I have
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0
org.gnome.settings-daemon.plugins.
On 7/25/23 00:57, Dario Lesca wrote:
Il giorno sab, 22/07/2023 alle 02.06 -0700, Samuel Sieb ha scritto:
You are only looking at the settings for your user. When no one is
logged in, the active user for the login screen is gdm. That's the
user that you need to change the settings for.
How ca
https://docs.dwservice.net/docs/site/remote-access/how-to-use-the-shell-application/
>
> Il giorno sab, 22/07/2023 alle 02.06 -0700, Samuel Sieb ha scritto:
> > You are only looking at the settings for your user. When no one is
> > logged in, the active user for the login screen is gdm. That's
Il giorno sab, 22/07/2023 alle 02.06 -0700, Samuel Sieb ha scritto:
> You are only looking at the settings for your user. When no one is
> logged in, the active user for the login screen is gdm. That's the
> user that you need to change the settings for.
How can I change the settings for user g
On Sat, Jul 22, 2023 at 5:51 AM Patrick Dupre wrote:
> I am sorry, but I do not understand.
>
> Right now, I have Automatic Suspend Off
> This makes sense, but the computer sleep after a while.
> It say "Pauses the computer afer a period of inactivity", and it is set at
> 1 hour
> Some
>
> Also
>
OK
Thank.
> >
> > Also
> > org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 900
> > org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'suspend'
> > org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 900
> > org.gnome.settings-daemon.plugins.power
On 7/22/23 01:45, Patrick Dupre wrote:
I am sorry, but I do not understand.
Right now, I have Automatic Suspend Off
This makes sense, but the computer sleep after a while.
It say "Pauses the computer afer a period of inactivity", and it is set at 1
hour
Some
Also
org.gnome.settings-daemon.plug
suspend
Jul 21 21:15:51 homere NetworkManager[1408]: [1689966951.3028] manager:
sleep: sleep requested (sleeping: no enabled: yes)
Jul 21 21:15:51 homere NetworkManager[1408]: [1689966951.3030] manager:
NetworkManager state is now ASLEEP
Jul 21 21:15:51 homere gnome-shell[319391]: Screen lock is locke
> On 21 Jul 2023, at 21:16, Patrick Dupre wrote:
>
> This behavior is just not acceptable.
> It means that any of the services run under cron can be started.
>
> Could you please send quickly a patch?
>
> May by running a cron that every 14 mn starts a test?
You must set your power saving
On 7/21/23 13:16, Patrick Dupre wrote:
This behavior is just not acceptable.
It means that any of the services run under cron can be started.
Could you please send quickly a patch?
May by running a cron that every 14 mn starts a test?
There are instructions around for how to disable the setting
"Community support for Fedora users"
Subject: Re: sleeping machine?
On 21 Jul 2023, at 11:59, Patrick Dupre wrote:
In f38 gnome defaults to going to sleep when idle. Is that the problem?
On 21 Jul 2023, at 09:06, Patrick Dupre wrote:
Hello,
On 21 Jul 2023, at 11:59, Patrick Dupre wrote:In f38 gnome defaults to going to sleep when idle. Is that the problem?On 21 Jul 2023, at 09:06, Patrick Dupre wrote:Hello,Since I update from fedora36 to 38, I am in trouble to connect to mymachine by using dwagent.One reason could be that when I am
UPRÉ | | email: pdu...@gmx.com
===
Sent: Friday, July 21, 2023 at 2:03 PM
From: "Grumpey"
To: "Community support for Fedora users"
Subject: Re: sleeping machine?
On Fri, Jul 21, 2023 at 8:01 AM Richard Shaw <hobbes1...@gmail.com> wrote:
On Fri, Jul
On Fri, Jul 21, 2023 at 7:04 AM Grumpey wrote:
>
> On Fri, Jul 21, 2023 at 8:01 AM Richard Shaw wrote:
>
>> On Fri, Jul 21, 2023 at 5:35 AM Barry wrote:
>>
>>>
>>> > On 21 Jul 2023, at 09:06, Patrick Dupre wrote:
>>> >
>>> > Hello,
>>> >
>>> > Since I update from fedora36 to 38, I am in troub
On Fri, Jul 21, 2023 at 8:01 AM Richard Shaw wrote:
> On Fri, Jul 21, 2023 at 5:35 AM Barry wrote:
>
>>
>> > On 21 Jul 2023, at 09:06, Patrick Dupre wrote:
>> >
>> > Hello,
>> >
>> > Since I update from fedora36 to 38, I am in trouble to connect to my
>> > machine by using dwagent.
>> > One re
On Fri, Jul 21, 2023 at 5:35 AM Barry wrote:
>
> > On 21 Jul 2023, at 09:06, Patrick Dupre wrote:
> >
> > Hello,
> >
> > Since I update from fedora36 to 38, I am in trouble to connect to my
> > machine by using dwagent.
> > One reason could be that when I am not logged on the machine, it falls
Enabling WOL (wake on lan) should wake it up from sleep. If WOL is
supported depends on the hardware and possibly bios settings so is
slightly different for each hardware combination.
You basically use a utility to send a WOL packet to the machine and
the network card wakes it up.
Search the ar
>
>
> > On 21 Jul 2023, at 09:06, Patrick Dupre wrote:
> >
> > Hello,
> >
> > Since I update from fedora36 to 38, I am in trouble to connect to my
> > machine by using dwagent.
> > One reason could be that when I am not logged on the machine, it falls to
> > sleep, and it does not accept to s
> On 21 Jul 2023, at 09:06, Patrick Dupre wrote:
>
> Hello,
>
> Since I update from fedora36 to 38, I am in trouble to connect to my
> machine by using dwagent.
> One reason could be that when I am not logged on the machine, it falls to
> sleep, and it does not accept to serve dwagent.
> 1) I
Hello,
Since I update from fedora36 to 38, I am in trouble to connect to my
machine by using dwagent.
One reason could be that when I am not logged on the machine, it falls to
sleep, and it does not accept to serve dwagent.
1) Is it possible?
2) It is possible, how can I keep the service (dwagent)
On Tue, Oct 20, 2020 at 1:09 PM Samuel Sieb wrote:
> On 10/20/20 10:22 AM, Richard Shaw wrote:
> > I recently purchased the Ryzen 5 4500U version of the HP ENVY X360
> > laptop. For the most part I love it. It's fast, slim, and overall runs
> > Fedora great but...
> >
> > The power button is loca
On 10/20/20 10:22 AM, Richard Shaw wrote:
I recently purchased the Ryzen 5 4500U version of the HP ENVY X360
laptop. For the most part I love it. It's fast, slim, and overall runs
Fedora great but...
The power button is located on the side and I frequently press it by
accident. This would be
I recently purchased the Ryzen 5 4500U version of the HP ENVY X360 laptop.
For the most part I love it. It's fast, slim, and overall runs Fedora great
but...
The power button is located on the side and I frequently press it by
accident. This would be just annoying but when I press the power button
On Sun, 17 May 2020 08:24:30 -0500
Richard Shaw wrote:
> Since the logs are going to the journal now I just remembered where
> the log was and locked and unlocked my system and copied the delta...
> Why in the heck is it doing all that just for a lock/unlock sequence?
>
> May 17 08:19:01 /usr/li
Since the logs are going to the journal now I just remembered where the log
was and locked and unlocked my system and copied the delta... Why in the
heck is it doing all that just for a lock/unlock sequence?
May 17 08:19:01 /usr/libexec/gdm-x-session[2326]: (II) AMDGPU(0): EDID
vendor "GSM", prod
> On 15 May 2020, at 13:31, Richard Shaw wrote:
>
> After upgrading to Fedora 32 my monitors no longer turn off after timeout or
> locking the display.
>
> Interestingly, they do for a few seconds after I lock the screen but then
> turn back on. The display is blank/black but the backlightin
After upgrading to Fedora 32 my monitors no longer turn off after timeout
or locking the display.
Interestingly, they do for a few seconds after I lock the screen but then
turn back on. The display is blank/black but the backlighting is
definitely on.
AMD RX580 and a LG & Acer 1080p IPS monitors.
On 08/29/19 05:57, Robert Moskowitz wrote:
Oh, your sig says you also use Xfce.
It is right there on the Systems tab in Power Manager.
Mine is set so on AC it never suspends. Battery it is set for 20 min
to suspend on no activity.
.
Yes xfce always, before that, perhaps 20 years ago, Window
On 8/29/19 4:22 AM, Bob Goodwin wrote:
This Fedora 29 computer"goes to sleep" with no keyboard input for a
rather short time and I don't know how to "wake it?" I really don't
know what mode is causing it, suspect something like suspend/hibernate
which i don't need or want.
Oh, your sig says
On 8/29/19 4:22 AM, Bob Goodwin wrote:
This Fedora 29 computer"goes to sleep" with no keyboard input for a
rather short time and I don't know how to "wake it?" I really don't
know what mode is causing it, suspect something like suspend/hibernate
which i don't need or want.
What every your G
This Fedora 29 computer"goes to sleep" with no keyboard input for a
rather short time and I don't know how to "wake it?" I really don't know
what mode is causing it, suspect something like suspend/hibernate which
i don't need or want.
When that happens I only know to press the computer on/off
I have a Bluetooth mouse (Sondstrom) which after a fairly short period
of inactivity - a minute or two - becomes unresponsive, i.e. it takes a
few seconds of jiggling for the cursor to move, whereupon it's fine
until it goes to sleep again. As far as I can tell, the mouse itself
isn't asleep (the s
On 07/14/2011 04:15 PM, Hugh Caley wrote:
Subject:
FC14, sleeping forever
From:
Tod Thomas <mailto:fr33z...@gmail.com>
Date:
06:07 AM
To:
Community support for Fedora users
<mailto:users@lists.fedoraproject.org>
I've got a virtual FC14 image running under virtual box
Subject:
FC14, sleeping forever
From:
Tod Thomas
Date:
06:07 AM
To:
Community support for Fedora users
I've got a virtual FC14 image running under virtual box on a win7
laptop. Something hung it up yesterday and I had to hard boot the
image. Now when I try and restart it progresses
I've got a virtual FC14 image running under virtual box on a win7 laptop.
Something hung it up yesterday and I had to hard boot the image. Now when
I try and restart it progresses to a point of almost completing and stops
with the message "No root device found. Boot has failed, sleepi
On Sunday 26 December 2010 05:11 AM, Antonio Olivares wrote:
> Yes, that was not the problem:(, the problem was for the monitor to wake up
> and play the music (monitor with built in speakers); still I like to have
> xterm to change songs, or o q(quit) faster:)
>
Ah ok! Its a matter of convenie
--- On Sun, 12/26/10, Suvayu Ali wrote:
> From: Suvayu Ali
> Subject: Re: how to wake up sleeping monitor using batch script/command
> To: users@lists.fedoraproject.org
> Date: Sunday, December 26, 2010, 2:36 AM
> On Saturday 25 December 2010 09:03
> PM, Antonio Olivares w
On 12/26/2010 06:36 PM, Suvayu Ali wrote:
> This is rather strange and unnecessary. mplayer is perfectly capable of
> playing audio without an xterm. You can replace all the xterm stuff by just,
Go back and read the OP's email. His speakers are built in to his flat
panel display. What is happen
On Saturday 25 December 2010 09:03 PM, Antonio Olivares wrote:
> /usr/bin/xterm -display :0 -bg white \
> -e /usr/bin/mplayer --really-quiet -shuffle -playlist ~/.playlist
> -stop-xscreensaver& PID=$!> /dev/null 2>&1
This is rather strange and unnecessary. mplayer is perfectly capable of
playi
--- On Sat, 12/25/10, Ed Greshko wrote:
> From: Ed Greshko
> Subject: Re: how to wake up sleeping monitor using batch script/command
> To: "Community support for Fedora users"
> Date: Saturday, December 25, 2010, 7:45 PM
> On 12/26/2010 11:24 AM, Antonio
> Oli
On 12/26/2010 12:06 PM, Antonio Olivares wrote:
> Will try to put into script. Do I put it before xset dpms force on; command
> or after? in case it is important.
needs to go before all other display related commands as it sets the
environment variable needed by all the commands related to the
--- On Sat, 12/25/10, Ed Greshko wrote:
> From: Ed Greshko
> Subject: Re: how to wake up sleeping monitor using batch script/command
> To: "Community support for Fedora users"
> Date: Saturday, December 25, 2010, 7:45 PM
> On 12/26/2010 11:24 AM, Antonio
> Oli
On 12/26/2010 11:24 AM, Antonio Olivares wrote:
> Will report back if I can get it to work, otherwise I will have to get Ed's
> solution.
Another FYI
If you run this from a cron job you'll need to add "export DISPLAY=:0".
--
QOTD: "She's about as smart as bait." 葛斯克 愛德華 / 台北市八德路四段
signat
On 12/25/10 8:24 PM, Antonio Olivares wrote:
>
> --- On Sat, 12/25/10, Ed Greshko wrote:
>
>> From: Ed Greshko
>> Subject: Re: how to wake up sleeping monitor using batch script/command
>> To: "Community support for Fedora users"
>> Date: Saturday, Dec
On 12/26/2010 11:24 AM, Antonio Olivares wrote:
> Will report back if I can get it to work, otherwise I will have to get Ed's
> solution.
I did finally fire up my F14 system and verified that xdotool is
available with F14.
--
The truth is what is; what should be is a dirty lie. -- Lenny Bruce 葛斯
On 12/25/10 7:35 PM, JB wrote:
> James McKenzie earthlink.net> writes:
>
>> ...
>> You know I say "Doc it hurts when I do this."
>> My doctor says "Don't do that."
>>
>> It looks like the redirects are causing the command to not work
>> properly, so don't use them.
>>
>> James McKenzie
>>
> Now t
--- On Sat, 12/25/10, Ed Greshko wrote:
> From: Ed Greshko
> Subject: Re: how to wake up sleeping monitor using batch script/command
> To: "Community support for Fedora users"
> Date: Saturday, December 25, 2010, 6:05 PM
> On 12/26/2010 10:00 AM, JB wrote:
> >
James McKenzie earthlink.net> writes:
> ...
> You know I say "Doc it hurts when I do this."
> My doctor says "Don't do that."
>
> It looks like the redirects are causing the command to not work
> properly, so don't use them.
>
> James McKenzie
>
Now the hard part may be to send Antonio to t
On 12/26/2010 10:12 AM, JB wrote:
> There is a possibility that BIOS / monitor / APM settings make a difference.
Which would not be a problem with xdotool and which is why I feel that
would be the preferred "universal" solution.
--
The only certainty is that nothing is certain. -- Pliny the Elde
Ed Greshko greshko.com> writes:
> >>>
> Neither of these incantations will turn my screen on
>
> xset dpms force off ; sleep 10 ; xdotool mousemove_relative 1 1
>
> works fine...
>
There is a possibility that BIOS / monitor / APM settings make a difference.
JB
--
users mailing list
u
On 12/25/10 7:00 PM, JB wrote:
> Antonio Olivares yahoo.com> writes:
>
>> ...
>> I tried adding a command to wake up the monitor like
>> 48 04 * * 1-5 sleep 2; xset dpms force on> /dev/null 2&>1
>> ...
> Some observations when done on a command line.
> - the screen does not come up when
>$ x
On 12/26/2010 10:00 AM, JB wrote:
> Some observations when done on a command line.
> - the screen does not come up when
> $ xset dpms force off ; sleep 10 ; xset dpms force on > /dev/null 2&>1
> - the screen DOES come up after 10s when
> $ xset dpms force off ; sleep 10 ; xset dpms force on
N
Antonio Olivares yahoo.com> writes:
> ...
> I tried adding a command to wake up the monitor like
> 48 04 * * 1-5 sleep 2; xset dpms force on > /dev/null 2&>1
> ...
Some observations when done on a command line.
- the screen does not come up when
$ xset dpms force off ; sleep 10 ; xset dpms fo
Ed Greshko greshko.com> writes:
> ...
> xset dpms force off ; sleep 20 ; xrandr --output ... --auto
>
> fails to turn on my screen. When you test it in your environment, it works?
>
On my notebook it works, but it takes 1 min plus.
JB
--
users mailing list
users@lists.fedoraproject.org
--- On Sat, 12/25/10, Ed Greshko wrote:
> From: Ed Greshko
> Subject: Re: how to wake up sleeping monitor using batch script/command
> To: users@lists.fedoraproject.org
> Date: Saturday, December 25, 2010, 4:34 PM
> On 12/26/2010 08:24 AM, JB wrote:
> >
> &
On 12/26/2010 08:24 AM, JB wrote:
>
> Would that do the trick ?
>
> man xrandr
> Per-output options
>
> xrandr --output ... --auto
>
FWIW
xset dpms force off ; sleep 20 ; xrandr --output ... --auto
fails to turn on my screen. When you test it in your environment, it works?
--
We are cur
Antonio Olivares yahoo.com> writes:
> ...
Would that do the trick ?
man xrandr
Per-output options
xrandr --output ... --auto
JB
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelin
On 12/26/2010 06:37 AM, Antonio Olivares wrote:
> I have a Flat Panel Monitor with built in speakers. If the monitor is on(not
> sleeping), the speakers work. When the Monitor goes to sleep, the speakers
> no longer work :(, I have a cron job that plays music in the morning, but
&g
Dear folks,
I have a Flat Panel Monitor with built in speakers. If the monitor is on(not
sleeping), the speakers work. When the Monitor goes to sleep, the speakers no
longer work :(, I have a cron job that plays music in the morning, but since
the monitor is sleeping the music does not play
By "current" I mean kernel-PAE-2.6.32.12-115.fc12.i686. Otherwise
up-to-date Fedora 12 on an ASUS laptop. What's been happening since
kernel-PAE-2.6.31.12-174.2.3.fc12.i686 is that when I suspend (to RAM)
the system "goes to sleep" normally and them immediately wakes up. Same
behavior whether I
64 matches
Mail list logo
