Hello,
I've been running Rawhide as a combined Xfce/MATE VM for a long while
(over a year). A few days ago an update broke networking, in that after
the next boot after the update NetworkManager was dead and died
instantly if you tried to launch it.
Yesterday I built a Rawhide Workstation from the latest ISO and
networking was working, so I did the same for MATE and out of the box
networking was non-functional.
The funny part is that I built both systems from the ISO:
Fedora-Everything-netinst-x86_64-Rawhide-20201102.n.0.iso
So in fact networking was working during the install of MATE, just not
after the first boot after installation.
I can't see anything obvious in the auto test logs that get posted. Is
networking in spins other than GNOME known to be broken?
I should add that both VMs cause 4 kernel-core crashes during boot, none
are reportable (so I haven't created a bug in Bugzilla) but the reasons
are as follows:
(for both GNOME and MATE systems)
WARNING: CPU: 0 PID: 601 at net/netfilter/nf_tables_api.c:622
nf_tables_expr_parse+0x1af/0x270 [nf_tables]
WARNING: CPU: 0 PID: 601 at net/netfilter/nf_tables_api.c:622
nf_tables_newset+0xd40/0xd90 [nf_tables]
WARNING: CPU: 0 PID: 601 at net/netfilter/nf_tables_api.c:622
nft_chain_parse_hook+0x2eb/0x310 [nf_tables]
WARNING: CPU: 0 PID: 776 at net/netfilter/nf_tables_api.c:622
nft_chain_parse_hook+0x26d/0x310 [nf_tables]
To be clear, networking in the GMOME workstation does work, but is
broken in MATE.
To ensure I am not going nuts, I just build another MATE VM from the
above ISO image (still the latest available) and after the first reboot
after the install, networking is non-functional.
--
Ian Laurie
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
