On Sun, 2025-07-06 at 10:49 -0300, George N. White III wrote:
> Circuit breakers were in a locked closet.
Is that legal? How would you cut power in an emergency?
--
uname -rsvp
Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64
(yes, this is the output from uname
Here I am away for the weekend and I again lost access to USB drives.
I tried this and it did not fix things.
Oh, well. But rebooting until I get back tomorrow night.
On 6/23/25 8:29 AM, Robert Moskowitz via users wrote:
On 6/23/25 4:02 AM, Francis Montagnac wrote:
Hi
On Sun, 22 Jun 2025
On Sun, 6 Jul 2025 17:04:34 +0200 Patrick Dupre wrote:
>> 2) Unmask sleep.target.
>>
>> Execute: sudo 06
>>
>> Then retry to suspend.
> Thank Francis,
> before I run systemctl unmask sleep.target, I had
> /etc/systemd/system/sleep.target -> /dev/null
"ls -l" would have given the dat
On Sat, 5 Jul 2025 20:43:22 +0200
Marco Moock wrote:
> On 05.07.2025 20:33 wrote:
>
> > Since a couple of day I'm not receiving new mail messages from the
> > list.
> > Checking the archives, some messages are present.
> > I've seen a note on "fedorastatus.org" regarding "Datacenter Move",
> >
> >
> >>
> >> On 7/5/25 1:00 AM, Patrick Dupre via users wrote:
> >>> I do not understand this:
> >>>
> >>> Jul 05 09:37:08 Sappho touchegg.desktop[4301]: Error connecting to
> >>> Touchégg daemon: Could not connect: Connection refused
> >>> Jul 05 09:37:03 Sappho touchegg.desktop[4301]: Reconnec
>
> On Sat, 2025-07-05 at 12:55 +0200, Patrick Dupre via users wrote:
> >> On Fri, 2025-07-04 at 11:31 +0200, Patrick Dupre via users wrote:
> >>> Jul 4 11:01:41 Sappho systemd-logind[1868]: Error during inhibitor-
> >>> delayed operation (already returned success to client): Unit
> >>> sleep.ta
On Sat, Jul 5, 2025 at 3:21 PM Ranjan Maitra via users <
users@lists.fedoraproject.org> wrote:
> On Sat Jul05'25 08:42:50AM, Community Support for Fedora Users wrote:
> > From: Ranjan Maitra via users
> > Date: Sat, 5 Jul 2025 08:42:50 -0500
> > To: Community support for Fedora users
> > Cc: Ran
On 6/7/25 21:13, George N. White III wrote:
On Sat, Jul 5, 2025 at 10:07 PM mailto:fed...@eyal.emu.id.au>> wrote:
Today I did the usual 'dnf update' on a VM system.
As part of the update I received kernel-6.15.4-200.fc42.x86_64
"VM System" is too vague: which VM?
QEMU/KVM.
Both the h
On Sat, Jul 5, 2025 at 10:07 PM wrote:
> Today I did the usual 'dnf update' on a VM system.
> As part of the update I received kernel-6.15.4-200.fc42.x86_64
>
"VM System" is too vague: which VM?
>
> However, after the upgrades were done, the last console message was
> >>> Running post-t
On Sun, 2025-07-06 at 08:49 +0100, Barry wrote:
>
> > On 6 Jul 2025, at 02:07, fed...@eyal.emu.id.au wrote:
> >
> > However, after the upgrades were done, the last console message was
> >>>> Running post-transaction scriptlet:
> > kernel-core-0:6.15.4-200.fc42.x86_64
> > after which the syst
> On 6 Jul 2025, at 02:07, fed...@eyal.emu.id.au wrote:
>
> However, after the upgrades were done, the last console message was
>>>> Running post-transaction scriptlet:
> kernel-core-0:6.15.4-200.fc42.x86_64
> after which the system was hard locked (about 45m...).
No one else has reported
11 matches
Mail list logo
