On 3/9/21 7:43 AM, Matthew Miller wrote:
2. Why Linux and not GNU/Linux? Linux is just a kernel. GNU/Linux is an OS.
Fedora Linux is an OS. Although GNU project utilities are indeed essential,
Fedora Linux consists of more than those plus Linux, and the contributions
of many of those other proje
On Sun, Mar 21, 2021 at 1:47 PM Jonathan Dieter wrote:
>
> On Sun, 2021-03-21 at 17:52 +, Jonathan Dieter wrote:
> > I'm really hoping that I'm missing something obvious here, but I fear
> > that a good chunk of our Fedora systems will be unbootable if they're
> > rebooted without disabling ra
On 22/03/2021 03:46, Jonathan Dieter wrote:
On Sun, 2021-03-21 at 17:52 +, Jonathan Dieter wrote:
I'm really hoping that I'm missing something obvious here, but I fear
that a good chunk of our Fedora systems will be unbootable if they're
rebooted without disabling raid-check.timer.
Just to
On Sun, 2021-03-21 at 17:52 +, Jonathan Dieter wrote:
> I'm really hoping that I'm missing something obvious here, but I fear
> that a good chunk of our Fedora systems will be unbootable if they're
> rebooted without disabling raid-check.timer.
Just to follow up on this, it appears that the pr
On 21/03/2021 17:52, Jonathan Dieter wrote:
There is a workaround: disabling raid-check.timer, but, if you can't
boot due to this bug, you have to boot into single-user mode (which
requires a root password to have been set).
Adding systemd.mask=raid-check.timer to the kernel command line
when
Yes, it is my bugreport.
Sorry for my english. Next is the google translate:
It is easy to imagine the situation (as it was with me in general): a
person works, launches something that eats up memory, it falls, the
person starts it again in bewilderment, and then his other working
application is
The bug https://bugzilla.redhat.com/show_bug.cgi?id=1941340
пн, 22 мар. 2021 г. в 03:12, Vascom :
>
> Hi all.
>
> I want to draw your attention to the bug in systemd-oomd in F34.
> This oomd kills my work application during the second run of the stress test.
> And I create this ticket:
> https://b
On Sun, 2021-03-21 at 17:52 +, Jonathan Dieter wrote:
> There is a workaround: disabling raid-check.timer, but, if you can't
> boot due to this bug, you have to boot into single-user mode (which
> requires a root password to have been set).
As Tom Hughes just pointed out to me, if you're stuck
Only this
мар 21 15:19:14 milkyway.localdomain systemd-oomd[1538]: Swap used
(7957565440) / total (8489267200) is more than 90.00%
мар 21 15:19:51 milkyway.localdomain systemd-oomd[1538]: Swap used
(8081399808) / total (8489267200) is more than 90.00%
вс, 21 мар. 2021 г. в 21:18, Alexey A. :
>
>
What is in the journal?
пн, 22 мар. 2021 г. в 03:12, Vascom :
>
> Hi all.
>
> I want to draw your attention to the bug in systemd-oomd in F34.
> This oomd kills my work application during the second run of the stress test.
> And I create this ticket:
> https://bugzilla.redhat.com/show_bug.cgi?id=1
Hi all.
I want to draw your attention to the bug in systemd-oomd in F34.
This oomd kills my work application during the second run of the stress test.
And I create this ticket:
https://bugzilla.redhat.com/show_bug.cgi?id=1941340
Can anybody confirm that behaviour?
Also I don't see any logs about
Hey everyone,
For reference, a bug report has been filed at
https://bugzilla.redhat.com/show_bug.cgi?id=1941335
I just wanted to give a heads up that I came across a bug today that
renders Fedora 33 systems unbootable, even after a clean install. If
systemd starts raid-check.timer, it gets stuck
No missing expected images.
Failed openQA tests: 9/187 (x86_64), 13/126 (aarch64)
New failures (same test not failed in Fedora-34-20210320.n.1):
ID: 823877 Test: x86_64 KDE-live-iso desktop_login
URL: https://openqa.fedoraproject.org/tests/823877
ID: 823905 Test: aarch64 Minimal-raw_xz
No missing expected images.
Compose PASSES proposed Rawhide gating check!
All required tests passed
Failed openQA tests: 12/187 (x86_64), 23/126 (aarch64)
New failures (same test not failed in Fedora-Rawhide-20210320.n.0):
ID: 823534 Test: x86_64 KDE-live-iso desktop_notifications_live
URL
No missing expected images.
Failed openQA tests: 4/16 (x86_64), 2/15 (aarch64)
New failures (same test not failed in Fedora-IoT-34-20210319.0):
ID: 824147 Test: x86_64 IoT-dvd_ostree-iso podman
URL: https://openqa.fedoraproject.org/tests/824147
ID: 824148 Test: x86_64 IoT-dvd_ostree-is
Missing expected images:
Iot dvd x86_64
Iot dvd aarch64
Failed openQA tests: 1/16 (x86_64), 5/15 (aarch64)
Old failures (same test failed in Fedora-IoT-35-20210320.0):
ID: 824112 Test: x86_64 IoT-dvd_ostree-iso base_services_start
URL: https://openqa.fedoraproject.org/tests/824112
ID: 8241
OLD: Fedora-34-20210320.n.1
NEW: Fedora-34-20210321.n.0
= SUMMARY =
Added images:0
Dropped images: 0
Added packages: 3
Dropped packages:0
Upgraded packages: 26
Downgraded packages: 0
Size of added packages: 7.40 MiB
Size of dropped packages:0 B
Size of
OLD: Fedora-Rawhide-20210320.n.0
NEW: Fedora-Rawhide-20210321.n.0
= SUMMARY =
Added images:1
Dropped images: 0
Added packages: 2
Dropped packages:1
Upgraded packages: 37
Downgraded packages: 0
Size of added packages: 606.85 KiB
Size of dropped packages
Thank you all for the kind words!
clime
On Thu, 18 Mar 2021 at 14:49, David Duncan wrote:
>
> Great News! Much appreciated!
>
> David Duncan
> http://about.me/davdunc
>
>
> On Wed, Mar 17, 2021 at 9:37 PM Christoph Karl wrote:
> >
> > Am 14.03.21 um 23:32 schrieb clime:
> > > Hello,
> > >
> > >
No missing expected images.
Failed openQA tests: 1/7 (aarch64)
New failures (same test not failed in Fedora-Cloud-32-20210320.0):
ID: 823455 Test: aarch64 Cloud_Base-qcow2-qcow2 base_system_logging@uefi
URL: https://openqa.fedoraproject.org/tests/823455
Soft failed openQA tests: 1/7 (x86_6
No missing expected images.
Soft failed openQA tests: 1/7 (x86_64), 1/7 (aarch64)
(Tests completed, but using a workaround for a known bug)
Old soft failures (same test soft failed in Fedora-Cloud-33-20210320.0):
ID: 823439 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://op
21 matches
Mail list logo
