Release criteria proposal: networking requirements
by Adam Williamson
Hi folks!
So at this week's blocker review meeting, the fact that we don't have
explicit networking requirements in the release criteria really started
to bite us. In the past we have squeezed networking-related issues in
under other criteria, but for some issues that's really difficult,
notably VPN issues. So, we agreed we should draft some explicit
networking criteria.
This turns out to be a big area and quite hard to cover (who'd've
thought!), but here is at least a first draft for us to start from. My
proposal would be to add this to the Basic criteria. I have left out
some wikitext stuff from the proposal for clarity; I'd add it back in
on actually applying the proposed changes. It's just formatting stuff,
nothing that'd change the meaning. Anyone have thoughts, complaints,
alternative approaches, supplements? Thanks!
=== Network requirements ===
Each of these requirements apply to both installer and installed system
environments. For any given installer environment, the 'default network
configuration tools' are considered to be those the installer documents
as supported ways to configure networking (e.g. for anaconda-based
environments, configuration via kernel command line options, a
kickstart, or interactively in anaconda itself are included).
==== Basic networking ====
It must be possible to establish both IPv4 and IPv6 network connections
using DHCP and static addressing. The default network configuration
tools for the console and for release-blocking desktops must work well
enough to allow typical network connection configuration operations
without major workarounds. Standard network functions such as address
resolution and connections with common protocols such as ping, HTTP and
ssh must work as expected.
Footnote titled "Supported hardware": Supported network hardware is
hardware for which the Fedora kernel includes drivers and, where
necessary, for which a firmware package is available. If support for a
commonly-used piece or type of network hardware that would usually be
present is omitted, that may constitute a violation of this criterion,
after consideration of the [[Blocker_Bug_FAQ|hardware-dependent-
issues|normal factors for hardware-dependent issues]]. Similarly,
violations of this criteria that are hardware or configuration
dependent are, as usual, subject to consideration of those factors when
determining whether they are release-blocking
==== VPN connections ====
Using the default network configuration tools for the console and for
release-blocking desktops, it must be possible to establish a working
connection to common OpenVPN, openconnect-supported and vpnc-supported
VNC servers with typical configurations.
Footnote title "Supported servers and configurations": As there are
many different VPN server applications and configurations, blocker
reviewers must use their best judgment in determining whether
violations of this criterion are likely to be encountered commonly
enough to block a release, and if so, at which milestone. As a general
principle, the more people are likely to use affected servers and the
less complicated the configuration required to hit the bug, the more
likely it is to be a blocker.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
1 year, 6 months
Problems with kmail on F35
by José Abílio Matos
After updating to F35 I have problems seeing the messages content on kmail.
I get the dreadful
"org.kde.pim.webengine viewer: WebEngine render process crashed"
This only applies to seeing the messages, everything else works. I see the
folders, the messages list and so on.
I can select the messages and view the source.
Is there any suggestion to fix this?
Best regards,
--
José Abílio
2 years
thermald: No temp sysfs for reading raw temp
by sbob
All;
I am running Fedora 34 on an LG Gram 17, I was having shutdown issues,
likely due to cpu overheating issues... So I installet thermald, then I
enabled it in systemctl, but when I look at /var/log/messages I see
entries like this:
messages-20210829:Aug 27 20:33:10 F34host systemd[1]: thermald.service:
Consumed 2min 26.227s CPU time.
messages-20210829:Aug 27 20:33:42 F34host audit[1]: SERVICE_START pid=1
uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=thermald comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
messages-20210829:Aug 27 20:33:42 F34host thermald[2462]: 27 CPUID
levels; family:model:stepping 0x6:7e:5 (6:126:5)
messages-20210829:Aug 27 20:33:42 F34host thermald[2462]: 27 CPUID
levels; family:model:stepping 0x6:7e:5 (6:126:5)
messages-20210829:Aug 27 20:33:42 F34host thermald[2462]: Polling mode
is enabled: 4
messages-20210829:Aug 27 20:33:42 F34host thermald[2462]: sensor id 10 :
No temp sysfs for reading raw temp
messages-20210829:Aug 27 20:33:42 F34host thermald[2462]: sensor id 10 :
No temp sysfs for reading raw temp
messages-20210829:Aug 27 20:33:42 F34host thermald[2462]: sensor id 10 :
No temp sysfs for reading raw temp
Thoughts?
Thanks in advance
2 years
List server mis-configured?
by Emmett Culley
I noticed recently that each time I send an email to the kde(a)lists.fedoraproject.org mailing list I get up to three failed DMARC reports from other email servers.
The list is sending email "from" me with the source address:
Source-IP: 38.145.60.11 (bastion-iad01.fedoraproject.org)
Which, of course, does not match up with my email server's IP address, so SPF fails, It also appears that DKIM signature also does not match.
I've had my server's DNS set up to request DMARK failure reports for a few years and haven't seen any reports lately except via this list. So I am wondering if something is mis-configured on this list server.
Emmett
2 years
WTF "Executing Dolphin with kdesu is not possible due to unfixable
security vulnerabilities"
by Emmett Culley
I updated my workstation (fedora 34) this morning and when I tried to run dolphin as root I saw the above message.
What are the KDE developers thinking? I am a developer (30 years) and am often needing to alter something on my workstation as root. What possible reason would the dophin devloper have to prevent me from doing that?
It is not as if a new KDE user might accidentally enable that functionality. Who the heck (putting it extremely mildly) are they trying to protect?
I used to use Konqueror until this same thing happened. Konqueror had advantages, like profiles, that made it hard to give up, but I did give it up because I needed occasional root access more than I needed profiles. Why should I have to change my ways because some developers have a nanny complex.
Emmett
2 years
cannot mount the same device twice without a reboot
by sbob
All;
I am seeing an odd behavior.
I am running Fedora 34 KDE spin
I plug in an external USB drive and the KDE disks & devices app on the
task bar shows the device and allows me to click "Mount and Open"
However if I click the "safely remove" in the KDE "disks & devices"
dialog, and unplug the drive, then later plug the same drive in again
(same or different USB port) then the "disks & devices" dialog never
comes up, and if I go to it it says "No Devices Available"
I can still mount it manually via the mount command, but the KDE dialog
refuses to show me any drives (for this drive) until I reboot
If I execute dmesg I see this (see below) - thanks in advance for any help
[59102.483693] usb-storage 4-2:1.0: USB Mass Storage device detected
[59102.483778] scsi host0: usb-storage 4-2:1.0
[59103.547117] scsi 0:0:0:0: Direct-Access WD Elements 25A3
1030 PQ: 0 ANSI: 6
[59103.547469] sd 0:0:0:0: Attached scsi generic sg0 type 0
[59103.548769] sd 0:0:0:0: [sda] Spinning up disk...
[59104.569633] .................ready
[59120.954263] sd 0:0:0:0: [sda] Very big device. Trying to use READ
CAPACITY(16).
[59120.954439] sd 0:0:0:0: [sda] 15627986944 512-byte logical blocks:
(8.00 TB/7.28 TiB)
[59120.954446] sd 0:0:0:0: [sda] 4096-byte physical blocks
[59120.955166] sd 0:0:0:0: [sda] Write Protect is off
[59120.955175] sd 0:0:0:0: [sda] Mode Sense: 47 00 10 08
[59120.955754] sd 0:0:0:0: [sda] No Caching mode page found
[59120.955760] sd 0:0:0:0: [sda] Assuming drive cache: write through
[59121.020690] sda: sda1
[59121.048512] sd 0:0:0:0: [sda] Attached SCSI disk
2 years
Random laptop shutdowns
by sbob
All;
I am experiencing random laptop shutdowns, I'll be working and it just
turns off, not a real shutdown just the screen goes black and it's
powered off instantly.
I suspect it may be a hardware issue but I have no idea how to debug it.
I'm running Fedora 34 - KDE Spin on a LG Gram 17
Below is the output of lspci, thanks in advance for any help debugging this
# lspci
00:00.0 Host bridge: Intel Corporation Ice Lake-LP Processor Host
Bridge/DRAM Registers (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics
G7 (rev 07)
00:04.0 Signal processing controller: Intel Corporation Device 8a03 (rev 03)
00:07.0 PCI bridge: Intel Corporation Ice Lake Thunderbolt 3 PCI Express
Root Port #0 (rev 03)
00:0d.0 USB controller: Intel Corporation Ice Lake Thunderbolt 3 USB
Controller (rev 03)
00:0d.2 System peripheral: Intel Corporation Ice Lake Thunderbolt 3 NHI
#0 (rev 03)
00:14.0 USB controller: Intel Corporation Ice Lake-LP USB 3.1 xHCI Host
Controller (rev 30)
00:14.2 RAM memory: Intel Corporation Ice Lake-LP DRAM Controller (rev 30)
00:14.3 Network controller: Intel Corporation Ice Lake-LP PCH CNVi WiFi
(rev 30)
00:15.0 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP
Serial IO I2C Controller #0 (rev 30)
00:15.1 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP
Serial IO I2C Controller #1 (rev 30)
00:16.0 Communication controller: Intel Corporation Ice Lake-LP
Management Engine (rev 30)
00:1d.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port
#9 (rev 30)
00:1d.4 PCI bridge: Intel Corporation Device 34b4 (rev 30)
00:1e.0 Communication controller: Intel Corporation Ice Lake-LP Serial
IO UART Controller #0 (rev 30)
00:1e.3 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP
Serial IO SPI Controller #1 (rev 30)
00:1f.0 ISA bridge: Intel Corporation Ice Lake-LP LPC Controller (rev 30)
00:1f.3 Audio device: Intel Corporation Ice Lake-LP Smart Sound
Technology Audio Controller (rev 30)
00:1f.4 SMBus: Intel Corporation Ice Lake-LP SMBus Controller (rev 30)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP SPI
Controller (rev 30)
2b:00.0 Non-Volatile memory controller: Micron/Crucial Technology Device
5412
2c:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe
SSD Controller SM981/PM981/PM983
2 years, 1 month
