Federa 35 Server default editor
by Peter Boy
In Fedora 34 the default editor was nano, for Workstation and also for Server. In my latest default F35 Server installation I noticed vim-default-editor was installed.
Did some good soul take pity and bring vim back to us or did something go wrong with my installation?
1 week, 1 day
Fwd: [Test-Announce] Fedora 37 Candidate RC-1.2 Available Now!
by Adam Williamson
Hi folks, just a heads-up that the second RC for 37 Final is out now
and we need to get through the testing by Thursday.
There are a few potential blockers to work through, but so far I kinda
suspect we may decide to reject or waive the ones that have arisen, so
I still want to treat this as a 'viable' candidate for now and get all
the tests run on it. This particularly includes the Active Directory
tests (pinging sgallagh, thanks as always...) and testing Cloud on real
The forwarded email has links to the results pages, which have links to
the images (including AMIs on the Cloud results page). You can edit
results into the wiki pages directly or use `relval report-results`
(after `dnf -y install relval`) which is a CLI that edits the pages for
you and makes the process slightly less annoying. :D
Thanks a lot folks!
IRC: adamw | Twitter: adamw_ha
Fedora 37 Final status update
by Adam Williamson
Hi, folks! Just wanted to make sure everyone's aware of the current
status with regards to the Fedora 37 release.
We are waiting on a couple of key things to build a release candidate:
a new glibc build for
https://bugzilla.redhat.com/show_bug.cgi?id=2129358 , and improved
upstream fixes for the gnome-calendar recurring event bugs. Both of
those are being actively worked on and I'm hoping they'll arrive today
or tomorrow; as soon as they do, I'll request a candidate compose.
In the mean time, it'd be great if folks can test and karma the pending
updates for blocker and FE bugs, which are listed on blockerbugs:
especially it'd be great to have as much testing as possible of the
kernel update. It'd also be great if folks can help fill out the
validation matrices for the current compose:
even though we won't ship that compose, it's pretty similar to what we
will ship, and it'd be very good to have the tricky tests like Active
Directory, unusual storage, and Cloud tests run now just in case there
are any lurking issues. And if necessary, we'll be able to transfer
results forward to the RC for tests that shouldn't be affected by
anything changed in it.
Thanks a lot, folks!
IRC: adamw | Twitter: adamw_ha
5 months, 1 week
Re: Agenda Items on 2022-10-05 17:00 ==UTC== meeting
Wow, I hope you feel better soon, Jason. I'm going to miss part of the meeting, because I'm heading to the doctor to get my leg looked at. I'm in a lot of pain after a bicycle accident last night (my own dumb fault, not with a car). I hoping that surgery isn't needed, and that I just pulled a bunch of muscles and stretched some tendons, but I soon find out.
On Wednesday 05 October 2022 11:17:11 AM (-04:00), J Beard wrote:
Unfortunately, I’m going to miss today's meeting. I’m recovering from surgery I had on Monday. I completely tore my bicep tendon from my foreman last week.
From: Peter Boy <pboy(a)uni-bremen.de>
Sent: Wednesday, October 5, 2022 10:14:03 AM
To: server(a)lists.fedoraproject.org <server(a)lists.fedoraproject.org>
Subject: Agenda Items on 2022-10-05 17:00 ==UTC== meeting
The meeting date
Fedora Server IRC meeting Wednesday, Oct. 05 17:00 ==UTC==
Please, check your local time using date -d ‘2022-10-05 17:00UTC’
The agenda as agreed upon last meeting:
== Agenda ==
1. = Follow up actions =
2. = Release 37 Beta testing =
- Follow up: Who is doing what
3. = Documentation update Release 37 =
- Follow up: Current state
4. = Using Ansible to install and configure Wildfly =
Goal: Discussion how to proceed further
5. = Open floor =
For any additions or changes, please reply to this email.
For an overview about current tasks look at:
Vor an overview about previous meetings:
server mailing list -- server(a)lists.fedoraproject.org
To unsubscribe send an email to server-leave(a)lists.fedoraproject.org
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://firstname.lastname@example.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com
5 months, 2 weeks
Possible Networking Bug in F37 Server Beta
I may only be at the Fedora Server WG meeting today for a short time,
because of a doctor's appointment, so I wanted to mention something that
came up when I was reviewing the documentation for Fedora Server
Installation and Post Install Tasks.
I tested the Fedora Server Standard ISO image install on the following
TOSHIBA product: Satellite C650 v: PSC2EU-001027
Mobo: TOSHIBA model: Portable PC serial: <filter> BIOS: INSYDE
CPU: Topology: Dual Core model: Intel Core i3-2310M bits: 64 type: MT
arch: Sandy Bridge
Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated
vendor: Toshiba America Info Systems driver: i915
Network: Device-1: Qualcomm Atheros AR8152 v2.0 Fast Ethernet
vendor: Toshiba America Info Systems driver: atl1c
Device-2: Realtek RTL8188CE 802.11b/g/n WiFi Adapter driver:
Since, the laptop has a built in wifi adapter, I decided to set up
networking during the install using that device. Fedora Server installed
without issue, but when I tried to connect to it remotely I could not.
- The system had received an internal IP address from my DHCP server. My
DHCP server could see the system connected to the network at the address it
was assigned. The Fedora Server login prompt correctly displayed the
internal IP address that it had been given.
- Yet, I could not ssh to the system. Cockpit would not come up when I
tried to access Cockpit from my workstation on the same LAN. I was unable
to ping the system as well.
- However, when I logged into the system directly, I had the correct IP
address connected through the wireless adapter, and I could do a "sudo dnf
update" without any problems.
I tried plugging in an Ethernet cable, which still didn't allow me to
connect remotely to the system, until I rebooted. After a reboot, I was
able to ssh, connect to Cockpit, and ping the system. However, when I
closed the lid of the laptop (putting the system to sleep) and then opened
the lid again later, once again coming out of sleep I have all of the same
connection issues that I had before. I'm not sure what is happening during
sleep that causes the remote connections to be lost. When I run "ip
address" it looks the same when I reboot and have the ethernet cable
plugged in as when I wake the system from sleep and run the command again.
I realize that connecting Fedora Server with wifi is not the most common
way to network a server, but I didn't find anything in the documentation
that mentioned that wifi connections would not allow remote access. So, I
believe this is a bug in Fedora Server 37 Beta, and one that would be good
to address before release of Fedora 37.
5 months, 2 weeks