> On 4/28/25 5:23 PM, Patrick Dupre via users wrote:
> > ○ sleep.target
> > Loaded: masked (Reason: Unit sleep.target is masked.)
> > Active: inactive (dead)
> >
> > ○ suspend.target
> > Loaded: masked (Reason: Unit suspend.target is masked.)
> > Active: inactive (dead)
>
On 4/28/25 5:24 PM, Patrick Dupre via users wrote:
On 4/28/25 4:15 PM, Patrick Dupre via users wrote:
I do not have the suspend option available in the gnome menu
for a while now.
How can I recover it ?
It's not in the power button menu?
What kind of computer is it?
What happens i
On 4/28/25 5:23 PM, Patrick Dupre via users wrote:
○ sleep.target
Loaded: masked (Reason: Unit sleep.target is masked.)
Active: inactive (dead)
○ suspend.target
Loaded: masked (Reason: Unit suspend.target is masked.)
Active: inactive (dead)
○ hibernate.target
Loade
>
> On 4/28/25 4:15 PM, Patrick Dupre via users wrote:
>
> > I do not have the suspend option available in the gnome menu
> > for a while now.
> > How can I recover it ?
>
> It's not in the power button menu?
> What kind of computer is it?
> What ha
: "Patrick Dupre"
> Subject: Re: suspend option
>
> On Mon, Apr 28, 2025 at 7:16 PM Patrick Dupre via users
> wrote:
> >
> > I do not have the suspend option available in the gnome menu
> > for a while now.
> > How can I recover it ?
>
> Show t
On Mon, Apr 28, 2025 at 7:16 PM Patrick Dupre via users
wrote:
>
> I do not have the suspend option available in the gnome menu
> for a while now.
> How can I recover it ?
Show the output of `systemctl status sleep.target suspend.target
hibernate.target hybrid-sleep.ta
On 4/28/25 4:15 PM, Patrick Dupre via users wrote:
I do not have the suspend option available in the gnome menu
for a while now.
How can I recover it ?
It's not in the power button menu?
What kind of computer is it?
What happens if you click the physical power b
Hello,
I do not have the suspend option available in the gnome menu
for a while now.
How can I recover it ?
Thank.
===
Patrick DUPRÉ | | email: pdu...@gmx.com
Hello!
I have an HP lt4111. After suspend to ram, it only works every 2/3
times I suspend the system. It works if I suspend and wake it up
again.
It also works immediately after a reboot.
If it doesn't work, it is being detected by lsusb, but not mmcli.
Bus 001 Device 004: ID 03f0:4e1d HP
Le 2024-12-16 17:50, Patrick O'Callaghan a écrit :
On Mon, 2024-12-16 at 17:33 +0100, François Patte wrote:
Bonjour,
Since I installed f40 on my computer, it is impossible to suspend: the
screen does not resume and stay black...
Don't you mean it's impossible to resume?
On Mon, 2024-12-16 at 17:33 +0100, François Patte wrote:
> Bonjour,
>
> Since I installed f40 on my computer, it is impossible to suspend: the
> screen does not resume and stay black...
>
>
Don't you mean it's impossible to resume?
> kernel: 6.11.11-200.fc40.x8
Bonjour,
Since I installed f40 on my computer, it is impossible to suspend: the
screen does not resume and stay black...
kernel: 6.11.11-200.fc40.x86_64
driver: 560.35.03
cuda: 12.6
Is there a fix?
Thank you.
--
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5
%
etc.), but when I turn the system on again, it loads the image (10% ... 20%
... 30% etc.) but the resume fails and it comes back to the login screen.
Suspend also behaves weirdly; if I suspend, it all goes black, but the
system stays fully powered (light on power button solid on rather than
blinking
al web service. This
> works.
>
> 2. I suspend my system overnight and wake it automatically in the
> morning). This turns out to be irrelevant, because the problem reported
> here occurs even when I do it manually.
>
> 3. On resuming, everything is up *except* httpd.
>
> 4
On Mon, 2024-09-23 at 14:31 +0930, Tim via users wrote:
> On Sun, 2024-09-22 at 15:16 +0100, Patrick O'Callaghan wrote:
> > All other network functions are working, including DNS. The problem
> > is exclusively with Apache, not because it's failing (nothing in the
> > journal suggests that and ther
-Where is this coming
> > from?
> > Sep 09 07:55:05 Bree systemd[1]: Finished systemd-suspend.service - System
> > Suspend.
>
> Surely that's just the suspend service being logged, not Apache.
Yes, I see that now.
poc
--
_
oming from the systemd-suspend.service stopping (because you
> resumed). That's a normal part of resume.
I see. After the resume, the suspend service is stopped.
poc
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send a
On Sun, 2024-09-22 at 15:16 +0100, Patrick O'Callaghan wrote:
> All other network functions are working, including DNS. The problem
> is exclusively with Apache, not because it's failing (nothing in the
> journal suggests that and there's nothing in its own error.log) but
> because the system is ex
md[1]: Finished systemd-suspend.service - System
> Suspend.
Surely that's just the suspend service being logged, not Apache.
--
uname -rsvp
Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically dele
e systemctl consistently as for
> other services. And for a small, personal webserver, any
> benefits of using graceful are hard to imagine as important.
Yeah, graceful on suspend is kind of a waste of time, just kill it ded.
> But I don't _think_ it should cause httpd to be unm
Chris Adams wrote:
> Once upon a time, Patrick O'Callaghan said:
>> On suspend:
>> Sep 09 01:01:44 Bree systemd[1]: Starting systemd-suspend.service - System
>> Suspend...
>> Sep 09 01:01:44 Bree systemd[1]: httpd.service: Sent signal SIGWINCH to main
>> pr
Once upon a time, Patrick O'Callaghan said:
> On suspend:
> Sep 09 01:01:44 Bree systemd[1]: Starting systemd-suspend.service - System
> Suspend...
> Sep 09 01:01:44 Bree systemd[1]: httpd.service: Sent signal SIGWINCH to main
> process 332400 (httpd) on client request.
On Sun, 2024-09-22 at 09:49 -0500, Chris Adams wrote:
> For any service that doesn't handle active network changes, you should
> stop it before suspend and start it after resume, after the network is
> back online. I don't think network-online.target is sufficient for
>
se the system is explicitly halting it.
It's been a bit since I ran Apache httpd, but it was not reactive to
network interface changes. On suspend, NetworkManager effectively downs
all interfaces, and re-ups them on resume. In my past experience, httpd
did not handle this cleanly; it saw the i
On Sun, 2024-09-22 at 12:38 +0100, Barry Scott wrote:
>
> > On 22 Sep 2024, at 12:00, Patrick O'Callaghan wrote:
> >
> > Tried that with this drop-in:
> >
> > # cat /etc/systemd/system/httpd.service.d/override.conf
> >
> > [Unit]
> > After=network-online.target
> > Wants=network-onlin
On Sun, 2024-09-22 at 21:45 +0930, Tim via users wrote:
> Barry Scott:
> > > Does httpd recover if you unplug the network cable and then plug it back
> > > in?
>
> Patrick O'Callaghan:
> > It does. The problem only ever occurs on suspend (or hibernate)/resum
On Sun, 2024-09-22 at 09:41 -0400, Todd Zullinger wrote:
> If using the socket activation doesn't work for some reason,
> it's probably worth adding a script to restart httpd on
> resume via /usr/lib/systemd/system-sleep. A number of
> packages do this.
It's working now. My bad. I had enabled it
On Sun, 2024-09-22 at 09:46 -0400, Jonathan Billings wrote:
> On Sep 21, 2024, at 09:35, francis.montag...@inria.fr wrote:
> >
> > HI.
> >
> > > On Sat, 21 Sep 2024 13:16:49 +0100 Patrick O'Callaghan wrote:
> > > 4. The journal (see below) shows that httpd does resume with the rest
> > > of the
On Sun, 2024-09-22 at 14:29 +0200, francis.montag...@inria.fr wrote:
> On Sun, 22 Sep 2024 12:16:59 +0100 Patrick O'Callaghan wrote:
>
> > I enabled httpd.socket (and made no other changes), did a daemon-
> > reload, then manually stopped Apache, but connecting to it doesn't
> > restart it again.
On Sep 21, 2024, at 09:35, francis.montag...@inria.fr wrote:
>
> HI.
>
>> On Sat, 21 Sep 2024 13:16:49 +0100 Patrick O'Callaghan wrote:
>> 4. The journal (see below) shows that httpd does resume with the rest
>> of the system, but then is immediately deactivated. The reason for this
>> is not st
francis.montag...@inria.fr wrote:
> On Sun, 22 Sep 2024 12:16:59 +0100 Patrick O'Callaghan wrote:
>
>> I enabled httpd.socket (and made no other changes), did a daemon-
>> reload, then manually stopped Apache, but connecting to it doesn't
>> restart it again.
>
> You need to start httpd.socket,
On Sun, 22 Sep 2024 12:16:59 +0100 Patrick O'Callaghan wrote:
> I enabled httpd.socket (and made no other changes), did a daemon-
> reload, then manually stopped Apache, but connecting to it doesn't
> restart it again.
You need to start httpd.socket, not only enable it (enable is for
starting it
Barry Scott:
> > Does httpd recover if you unplug the network cable and then plug it back in?
Patrick O'Callaghan:
> It does. The problem only ever occurs on suspend (or hibernate)/resume.
> In fact it occasionally doesn't happen then either, which suggests a
> race
> On 22 Sep 2024, at 12:00, Patrick O'Callaghan wrote:
>
> Tried that with this drop-in:
>
> # cat /etc/systemd/system/httpd.service.d/override.conf
>
> [Unit]
> After=network-online.target
> Wants=network-online.target
>
> It made no difference.
That only changes what happens when
On Sun, 2024-09-22 at 12:00 +0100, Patrick O'Callaghan wrote:
> > You might also consider using the httpd.socket activation
> > method. Then httpd will be started when a request for the
> > web service arrives.
> >
> >
>
> I'll take a look at that.
I enabled httpd.socket (and made no other cha
On Sun, 2024-09-22 at 13:42 +0930, Tim via users wrote:
> On Sat, 2024-09-21 at 13:16 +0100, Patrick O'Callaghan wrote:
> > Here's the relevant section from the journal:
> >
> > Sep 21 13:04:12 Bree systemd[1]: httpd.service: Deactivated successfully.
> > Sep 21 13:04:12 Bree systemd[1]: httpd.ser
On Sat, 2024-09-21 at 15:35 +0200, francis.montag...@inria.fr wrote:
> HI.
>
> On Sat, 21 Sep 2024 13:16:49 +0100 Patrick O'Callaghan wrote:
>
> > 4. The journal (see below) shows that httpd does resume with the rest
> > of the system, but then is immediately deactivated. The reason for this
> >
ish this.
>
> Once the service is started systemd is not involved.
> It is responsibility of httpd to handle the network events while it is
> running.
>
> Does httpd recover if you unplug the network cable and then plug it back in?
It does. The problem only ever occurs on su
On Sat, 2024-09-21 at 09:49 -0400, Todd Zullinger wrote:
> Patrick O'Callaghan wrote:
> > 1. I run httpd via systemd for a small personal web service. This
> > works.
> >
> > 2. I suspend my system overnight and wake it automatically in the
> > morning). Th
;
> I run Apache on my CentOS PC, and although I don't suspend it, I don't
> ever recall Apache not working after a cold/warm boot.
This only ever happens on suspend/resume, never on a reboot.
poc
--
___
users mailing list -- users@lis
On Sat, 2024-09-21 at 13:16 +0100, Patrick O'Callaghan wrote:
> Here's the relevant section from the journal:
>
> Sep 21 13:04:12 Bree systemd[1]: httpd.service: Deactivated successfully.
> Sep 21 13:04:12 Bree systemd[1]: httpd.service: Consumed 2.980s CPU time.
> Sep 21 13:04:14 Bree NetworkMana
On Sat, 2024-09-21 at 13:16 +0100, Patrick O'Callaghan wrote:
> I assume there's a systemd mechanism for getting httpd to wait for the
> network before resuming, but I've no idea how to accomplish this.
I run Apache on my CentOS PC, and although I don't suspend it, I do
> On 21 Sep 2024, at 13:16, Patrick O'Callaghan wrote:
>
> I assume there's a systemd mechanism for getting httpd to wait for the
> network before resuming, but I've no idea how to accomplish this.
Once the service is started systemd is not involved.
It is responsibility of httpd to handle the
Patrick O'Callaghan wrote:
> 1. I run httpd via systemd for a small personal web service. This
> works.
>
> 2. I suspend my system overnight and wake it automatically in the
> morning). This turns out to be irrelevant, because the problem reported
> here occurs even when I
HI.
On Sat, 21 Sep 2024 13:16:49 +0100 Patrick O'Callaghan wrote:
> 4. The journal (see below) shows that httpd does resume with the rest
> of the system, but then is immediately deactivated. The reason for this
> is not stated (there's no error message), but may be because on the
> system resume
[Rather than adding to an existing thread (which discusses AVCs from
crontab among other things, this is starting from a clean slate to
reduce confusion.]
1. I run httpd via systemd for a small personal web service. This
works.
2. I suspend my system overnight and wake it automatically in the
On Sat, Sep 7, 2024 at 6:45 AM Barry Scott wrote:
>
>
> On 7 Sep 2024, at 08:59, François Patte <
> francois.pa...@mi.parisdescartes.fr> wrote:
>
> No more exlanation (as usual with journalctl...)
>
>
> journalctl does not decide what is logged that is up to the application
> developer.
> In this
> On 7 Sep 2024, at 08:59, François Patte
> wrote:
>
> No more exlanation (as usual with journalctl...)
journalctl does not decide what is logged that is up to the application
developer.
In this case nvidia I assume.
Barry
--
___
users mailing l
Le 2024-09-07 08:21, francis.montag...@inria.fr a écrit :
Hi.
On Wed, 04 Sep 2024 16:44:51 +0200 François Patte wrote:
When I suspend my system, it is impossible to resume with the nvidia
module (works with nouveau and was working with f36)
kernel: 6.10.6-200.fc40.x86_64
nvidia
Hi.
On Wed, 04 Sep 2024 16:44:51 +0200 François Patte wrote:
> When I suspend my system, it is impossible to resume with the nvidia
> module (works with nouveau and was working with f36)
> kernel: 6.10.6-200.fc40.x86_64
> nvidia stuff:
> xorg-x11-drv-nvidia-power-560.35.0
Bonjour,
When I suspend my system, it is impossible to resume with the nvidia
module (works with nouveau and was working with f36)
kernel: 6.10.6-200.fc40.x86_64
nvidia stuff:
nvidia-gpu-firmware-20240811-2.fc40.noarch
xorg-x11-drv-nvidia-kmodsrc-560.35.03-3.fc40.x86_64
xorg-x11-drv
On Sun, 2024-08-25 at 20:09 -0700, Samuel Sieb wrote:
> On 8/25/24 12:51 AM, Barry wrote:
> >
> >
> > > On 24 Aug 2024, at 12:18, Patrick O'Callaghan
> > > wrote:
> > >
> > > If the RTC can wake
> > > the system from hibernation, why can't it wake it from
> > > suspension?
> >
> > The RTC wake
On Sun, 2024-08-25 at 08:51 +0100, Barry wrote:
> The RTC wake powers on the system. But a suspended system is
> already powered up and kernel is in charge.
I wouldn't say so. It's barely powered up, and you're relying on
firmware to control waking it up.
--
uname -rsvp
Linux 3.10.0-1160.119
On 8/25/24 12:51 AM, Barry wrote:
On 24 Aug 2024, at 12:18, Patrick O'Callaghan wrote:
If the RTC can wake
the system from hibernation, why can't it wake it from suspension?
The RTC wake powers on the system. But a suspended system is
already powered up and kernel is in charge.
Sort of.
On Sun, 2024-08-25 at 11:13 +0930, Tim via users wrote:
> Doug Herr:
> > > I also enabled the "Magic" check box for the Network Manager
> > > config
> > > for my Ethernet port.
>
> Patrick O'Callaghan:
> > Not sure what that is. I don't see any such box.
>
>
> In the Network Manager open up the
On Sat, 2024-08-24 at 12:17 +0100, Patrick O'Callaghan wrote:
> Having failed to get hibernation working (see recent posts about
> Secure
> Boot getting in the way), I tried to fall back to suspending the
> system
> overnight. That works of course.
>
> What doesn't work is waking it up automatical
s on the system. But a suspended system is
> already powered up and kernel is in charge.
>
> You need to use a systemd timer to schedule the wake up.
I've actually managed to get the RTC to work now (it needed another
UEFI setting). I agree a systemd timer would be preferable in gene
On Sat, 2024-08-24 at 20:22 -0700, Doug Herr wrote:
> On Sat, Aug 24, 2024, at 2:23 PM, Patrick O'Callaghan wrote:
> > I use UEFI mode and don't want to change it. I'm pretty sure the
> > UEFI
> > settings have toggles for WOL but I'll need to check. The Android
> > app I
> > have is called WolOn a
> On 24 Aug 2024, at 12:18, Patrick O'Callaghan wrote:
>
> If the RTC can wake
> the system from hibernation, why can't it wake it from suspension?
The RTC wake powers on the system. But a suspended system is
already powered up and kernel is in charge.
You need to use a systemd timer to sched
On Sat, Aug 24, 2024, at 2:23 PM, Patrick O'Callaghan wrote:
> I use UEFI mode and don't want to change it. I'm pretty sure the UEFI
> settings have toggles for WOL but I'll need to check. The Android app I
> have is called WolOn and includes a scheduler, but I'll take a look at
> LanDroid to compa
Doug Herr:
>> I also enabled the "Magic" check box for the Network Manager config
>> for my Ethernet port.
Patrick O'Callaghan:
> Not sure what that is. I don't see any such box.
In the Network Manager open up the editing window for a connection, go
into the ethernet tab, the wake-on LAN section
On Sat, 2024-08-24 at 10:49 -0700, Doug Herr wrote:
> On Sat, Aug 24, 2024, at 9:25 AM, Patrick O'Callaghan wrote:
> > On Sat, 2024-08-24 at 08:15 -0700, Doug Herr wrote:
> > > I found that RTC wakeup did work to wake from suspend, but I also
> > > had
> >
7;t want to have to be in front of the system to wake it up.
> >
>
> I have used WOL with Fedora Workstation by LAN when I didn't want to
> go outside to wake-up a suspended box in an outbuilding during sa
> storm.
>
> Wireless WOL (WWOL) is a recent innovation, so may not
t; > > What doesn't work is waking it up automatically. If the RTC can
> > > > wake
> > > > the system from hibernation, why can't it wake it from
> > > > suspension?
> > > > I
> > > > don't want to have to be in f
a suspended box in an outbuilding during sa storm.
Wireless WOL (WWOL) is a recent innovation, so may not be supported on
older
hardware. Some Fedora systems have issues with WiFI when waking from
suspend
by keyboard, so I wouldn't expect WWOL to work for those.
--
George N. White III
--
ending the
system
overnight. That works of course.
What doesn't work is waking it up automatically. If the RTC can
wake
the system from hibernation, why can't it wake it from suspension?
I
don't want to have to be in front of the system to wake it up.
I found that RTC wakeup did
On Sat, Aug 24, 2024, at 9:25 AM, Patrick O'Callaghan wrote:
> On Sat, 2024-08-24 at 08:15 -0700, Doug Herr wrote:
>> I found that RTC wakeup did work to wake from suspend, but I also had
>> a number of issues with it which I can't really remember right now.
>> My s
> system
> > overnight. That works of course.
> >
> > What doesn't work is waking it up automatically. If the RTC can
> > wake
> > the system from hibernation, why can't it wake it from suspension?
> > I
> > don't want to have to be in fron
aking it up automatically. If the RTC can wake
> the system from hibernation, why can't it wake it from suspension? I
> don't want to have to be in front of the system to wake it up.
I found that RTC wakeup did work to wake from suspend, but I also had a number
of issues with it wh
Having failed to get hibernation working (see recent posts about Secure
Boot getting in the way), I tried to fall back to suspending the system
overnight. That works of course.
What doesn't work is waking it up automatically. If the RTC can wake
the system from hibernation, why can't it wake it fr
On Tue, Dec 19, 2023 at 7:21 PM Chris Adams wrote:
> Once upon a time, Tim said:
> > I got the impression that only laptops seem to have reasonably well
> > working suspend, and suspect that little effort is put into designing
> > and testing desktops to suspend well. T
ver.
>
> When I resume from suspend, no video shows. I can still ssh to the
> machine, though. If I issue 'sudo shutdown -r now' from an ssh session,
> the machine freezes. I can still ping, but I can't ssh (connection
> refused errors). The only way I can regain
I doubt anyone here will be able to help if you don't provide error
messages that usually a system provides when things go wrong. So "man
journalctl" might help ...
Plus: To shut down a more or less frozen system maybe look for sysrq
keys.
Extra fine: 'powerconf' et al. is shutting down my machi
Tim:
>> Certain suspend modes require a suitable power supply, too. They don't
>> switch off fully, some power circuits are required to stay up, and
>> supply sufficient current to the motherboard. It also requires all the
>> hardware to support suspending, some will
Once upon a time, Tim said:
> I got the impression that only laptops seem to have reasonably well
> working suspend, and suspect that little effort is put into designing
> and testing desktops to suspend well. That may have improved with
> increasing demands for so-called green tech
On Tue, 2023-12-19 at 14:26 -0500, Jeffrey Walton wrote:
> Don't suspend. I find it is hit or miss whether things work correctly
> with ACPI Sleep States (S0 - S5). In particular, S3 and above.
I got the impression that only laptops seem to have reasonably well
working suspend, and s
ver.
>
> When I resume from suspend, no video shows. I can still ssh to the
> machine, though. If I issue 'sudo shutdown -r now' from an ssh session,
> the machine freezes. I can still ping, but I can't ssh (connection
> refused errors). The only way I can regain
On 12/19/2023 10:46 AM, Matthew Saltzman wrote:
The proprietary nVidia driver doesn't exhibit the same problem.
You're better off removing those and using the akmods from rpmfusion as
you don't have to reinstall the drivers every time you install a new kernel.
--
_
I have a Dell Precision 5820 Xeon with nVidia GeForce GT 1030 graphics
for video and a Quadro 4000 that I was playing with for GPU algorithms.
I have a fresh (fully updated) install of Fedora 39 with the nouveau
driver.
When I resume from suspend, no video shows. I can still ssh to the
machine
On Tue, 2023-10-17 at 23:19 +0200, Patrick Dupre via users wrote:
> Sorry:
>
> KVM: keyboard, video, mouse
> >
I know. That's what I'm talking about. I only mentioned the virtual
machine as an example of when I needed the (physical) KVM switch.
poc
__
Sorry:
KVM: keyboard, video, mouse
>
> On Tue, 2023-10-17 at 22:14 +0200, Patrick Dupre via users wrote:
> > > It's very possible that your BIOS doesn't support waking up from
> > > the
> > > keyboard.
> > Actually, it works fine, except when I go through a KVM
>
> KVMs are not all created equal.
On Tue, 2023-10-17 at 22:14 +0200, Patrick Dupre via users wrote:
> > It's very possible that your BIOS doesn't support waking up from
> > the
> > keyboard.
> Actually, it works fine, except when I go through a KVM
KVMs are not all created equal.
When I set up my VM system for gaming, I had a vir
On 10/17/23 13:14, Patrick Dupre via users wrote:
It's very possible that your BIOS doesn't support waking up from the
keyboard.
Actually, it works fine, except when I go through a KVM
I think this is the first time a KVM has been mentioned.
It's also likely that the BIOS won't read devices th
>
> It's very possible that your BIOS doesn't support waking up from the
> keyboard.
Actually, it works fine, except when I go through a KVM
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.
It's very possible that your BIOS doesn't support waking up from the
keyboard.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraprojec
Patrick Dupre wrote:
> OK, I checked the Bios options:
> These what I have (3 options)
> AC Recovery:
> Power Off, Power On, Last Power State
> Right now I Power Off is set, maybe I should set Last Power State
This is what you want the PC to do if the power fails while it's
running. Do you want i
===
> Sent: Tuesday, October 17, 2023 at 8:00 AM
> From: "Tim via users"
> To: users@lists.fedoraproject.org
> Cc: "Tim"
> Subject: Re: wake up from suspend
>
> On Mon, 2023-10-16 at 18:08 +0200, Patrick Dupre wrote:
> >
On Mon, 2023-10-16 at 18:08 +0200, Patrick Dupre wrote:
> On one computer I can wake up the computer in suspend mode by pressing
> escape, on the other one, I have to push the ON/OFF button.
> How can I manage this behavior?
You may have BIOS options, or jumpers on older motherboar
On 10/16/23 17:08, Patrick Dupre wrote:
> On one computer I can wake up the computer in suspend mode by pressing
> escape, on the other one, I have to push the ON/OFF button.
> How can I manage this behavior?
Hey
I think the firmware handles the wake-up event. There should be an
opti
Hello,
On one computer I can wake up the computer in suspend mode by pressing
escape, on the other one, I have to push the ON/OFF button.
How can I manage this behavior?
Thank.
===
Patrick DUPRÉ
On Apr 26, 2023, at 18:00, Tom Horsley wrote:
>
> On Wed, 26 Apr 2023 15:49:46 -0600
> Joe Zeff wrote:
>
>> And if you're not going to be using a GUI, why install one in the first
>> place? Wouldn't it be easier to do a server install that doesn't have one?
>
> On systems I use like that, I
On Wed, 26 Apr 2023 15:49:46 -0600
Joe Zeff wrote:
> And if you're not going to be using a GUI, why install one in the first
> place? Wouldn't it be easier to do a server install that doesn't have one?
On systems I use like that, I kind of like the GUI installed so I
can run GUI tools via ssh X
On 04/26/2023 03:44 PM, Tom Horsley wrote:
If I'm just using it as a firewall, I'd also do:
systemctl set-default multi-user.target
To run without an active GUI system.
And if you're not going to be using a GUI, why install one in the first
place? Wouldn't it be easier to do a server instal
On Wed, 26 Apr 2023 17:32:25 -0400
Tim Evans wrote:
> And, for those like me using F38 for a firewall or who otherwise need
> their systems to not suspend EVER, down a ways in this document:
>
> # systemctl mask sleep.target suspend.target hibernate.target
> hybrid-sleep.targ
se like me using F38 for a firewall or who otherwise need
their systems to not suspend EVER, down a ways in this document:
# systemctl mask sleep.target suspend.target hibernate.target
hybrid-sleep.target
___
users mailing list -- users@lists.fedoraproj
On Wed, Apr 26, 2023 at 3:21 PM Todd Zullinger wrote:
>
> Tim Evans wrote:
> > This was an in-place dnf upgrade. The existing setting in Gnome shouldn't
> > have been changed, right?
>
> The default did change which affects the gdm user. Unless
> you're logged into a Gnome session on this firewa
Tim Evans wrote:
> This was an in-place dnf upgrade. The existing setting in Gnome shouldn't
> have been changed, right?
The default did change which affects the gdm user. Unless
you're logged into a Gnome session on this firewall, it
would pick up the new default.
https://discussion.fedoraproj
On 4/26/23 14:12, Barry wrote:
On 26 Apr 2023, at 19:04, Tim Evans wrote:
Upgraded my firewall machine F37->F38 today, with no apparent errors or
issues...
EXCEPT that I found it on power suspend twice in the first hour after finishing the
upgrade. Checked power settings and fo
> On 26 Apr 2023, at 19:04, Tim Evans wrote:
>
> Upgraded my firewall machine F37->F38 today, with no apparent errors or
> issues...
>
> EXCEPT that I found it on power suspend twice in the first hour after
> finishing the upgrade. Checked power settings and
Upgraded my firewall machine F37->F38 today, with no apparent errors or
issues...
EXCEPT that I found it on power suspend twice in the first hour after
finishing the upgrade. Checked power settings and found "Automatic
Suspend" ON and set to 15 minut
1 - 100 of 661 matches
Mail list logo
