test September 2020

test@lists.fedoraproject.org

38 participants
326 discussions

Release criteria proposal: networking requirements
by Adam Williamson 01 Mar '22

01 Mar '22

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

6 18

NVIDIA Question
by David St.Clair 17 Jan '22

17 Jan '22

This may be a dumb question, but why can't Redhat distribute NVIDIA binary drivers? In NVIDIA's licence (http://www.nvidia.com/object/nv_swlicense.html) it says: "2.1.2 Linux Exception. Notwithstanding the foregoing terms of Section 2.1.1, SOFTWARE designed exclusively for use on the Linux operating system may be copied and redistributed, provided that the binary files thereof are not modified in any way (except for unzipping of compressed files)." So, what's keeping RedHat from putting the drivers in the distribution? If it's a GPL thing, would it be easy to just download it during installation or at least give the option to the user? Thanks, -- David St.Clair dstclair(a)cs.wcu.edu

10 20

Mouse goes crazy
by Jonathan Villa 17 Jan '22

17 Jan '22

Ok, I have had Yarrow working well for a while now, but yesterday I started experiencing some odd issues with my mouse. All of a sudden it stops working correctly. The only thing that seems to fix is to kill X and run mouse-test, then restart. Any ideas? Also, I have FC 1 running on a desktop which is hooked up to a KVM switch. Whenever I go to another PC, and return, the same thing happens, the mouse goes crazy. ???

8 7

criterion proposal: prevent services timing out on system shutdown
by Kamil Paral 22 Feb '21

22 Feb '21

*Why* The recent spice-vdagent update causes all virtual machines to take 90 seconds longer on every shutdown/reboot: https://bugzilla.redhat.com/show_bug.cgi?id=1813667 The service hangs when systemd tries to stop it, and systemd then kills it after a 90 second timeout expires. This is a recurring pattern, I saw services blocking shutdown/reboot in the past, and so far we haven't been able to do anything about it from a blocker perspective. I think that for cases where the problem occurs very frequently or every time, we should have a way to block the release until it's fixed. I find it a very poor experience to wait 90+ seconds for machine reboot/shutdown. Much poorer than, say, a crashing desktop application (which we block on), because that application can be replaced with a different one. System services mostly can't be replaced, and certainly not by a general user. *Proposal* So I propose to amend the "System services" criterion [1]: ``` All system services present after installation with one of the release-blocking package sets must start properly, unless they require hardware which is not present. ``` with something like this: ``` All system services present after installation with one of the release-blocking package sets must start properly, unless they require hardware which is not present. *All system services present after installation with one of the release-blocking package sets must not time out frequently or regularly when they are being stopped during system reboot/shutdown.* ``` The way it is written, the mentioned bug would be a conditional violation of that criterion (applies only to VMs) and we'd need to use our judgement to determine whether it's a blocker. Thoughts? [1] https://fedoraproject.org/wiki/Fedora_32_Final_Release_Criteria#System_serv…

9 18

Fedora Modular 27 compose report: 20171028.n.0 changes
by Fedora Branched Report 02 Nov '20

02 Nov '20

OLD: Fedora-Modular-27-20171028.n.0 NEW: Fedora-Modular-27-20171028.n.0 ===== SUMMARY ===== Added images: 0 Dropped images: 0 Added packages: 0 Dropped packages: 0 Upgraded packages: 0 Downgraded packages: 0 Size of added packages: 0.00 B Size of dropped packages: 0.00 B Size of upgraded packages: 0.00 B Size of downgraded packages: 0.00 B Size change of upgraded packages: 0.00 B Size change of downgraded packages: 0.00 B ===== ADDED IMAGES ===== ===== DROPPED IMAGES ===== ===== ADDED PACKAGES ===== ===== DROPPED PACKAGES ===== ===== UPGRADED PACKAGES ===== ===== DOWNGRADED PACKAGES =====

1 0

Trying a upgrade from 29 to 30
by Ludovic Hirlimann 02 Nov '20

02 Nov '20

Hi all, According to https://fedoraproject.org/wiki/Releases/30/Schedule 30 has been branched. So time for me to upgrade from 29 so I can report issue with the way I use fedora. I'm using https://fedoraproject.org/wiki/DNF_system_upgrade to upgrade. Failed to synchronize cache for repo 'luminoso-Signal-Desktop', ignoring this repo. Failed to synchronize cache for repo 'athmane-gns3-extra', ignoring this repo. Failed to synchronize cache for repo 'rpmfusion-free-updates', ignoring this repo. Failed to synchronize cache for repo 'rpmfusion-free', ignoring this repo. Failed to synchronize cache for repo 'rpmfusion-nonfree-updates', ignoring this repo. Failed to synchronize cache for repo 'rpmfusion-nonfree', ignoring this repo. Modular dependency problems: Problem 1: conflicting requests - nothing provides module(platform:f30) needed by module avocado:stable:3020190213205848:a5b0195c-0.x86_64 Problem 2: conflicting requests - nothing provides module(platform:f30) needed by module bat:latest:3020190214090936:e50d0d19-0.x86_64 Problem 3: conflicting requests - nothing provides module(platform:f30) needed by module dwm:6.1:3020190213215420:a5b0195c-0.x86_64 Problem 4: conflicting requests - nothing provides module(platform:f30) needed by module exa:latest:3020190214120734:e50d0d19-0.x86_64 Problem 5: conflicting requests - nothing provides module(platform:f30) needed by module fish:3:3020190216163513:602da195-0.x86_64 Problem 6: conflicting requests - nothing provides module(platform:f30) needed by module gimp:2.10:20181223154246:a5b0195c-0.x86_64 Problem 7: conflicting requests - nothing provides module(platform:f30) needed by module libgit2:0.27:3020190128145600:a5b0195c-0.x86_64 Problem 8: conflicting requests - nothing provides module(platform:f30) needed by module meson:latest:3020190123223713:36245242-0.x86_64 Problem 9: conflicting requests - nothing provides module(platform:f30) needed by module ninja:latest:3020190131012415:a5b0195c-0.x86_64 Problem 10: conflicting requests - nothing provides module(platform:f30) needed by module ripgrep:latest:3020190214090003:a5b0195c-0.x86_64 Problem 11: conflicting requests - nothing provides module(platform:f30) needed by module standard-test-roles:3.0:3020190214144451:a5b0195c-0.x86_64 Problem 12: conflicting requests - nothing provides module(platform:f30) needed by module stratis:1:20181215204600:a5b0195c-0.x86_64 Error: Problem 1: package libibcm-16.2-3.fc28.x86_64 requires rdma-core(x86-64) = 16.2-3.fc28, but none of the providers can be installed - rdma-core-16.2-3.fc28.x86_64 does not belong to a distupgrade repository - problem with installed package libibcm-16.2-3.fc28.x86_64 Problem 2: package libopenshot-0.2.2-1.fc29.x86_64 requires libMagickCore-6.Q16.so.5()(64bit), but none of the providers can be installed - package libopenshot-0.2.2-1.fc29.x86_64 requires libMagickWand-6.Q16.so.5()(64bit), but none of the providers can be installed - ImageMagick-libs-1:6.9.9.38-3.fc29.x86_64 does not belong to a distupgrade repository - problem with installed package libopenshot-0.2.2-1.fc29.x86_64 Problem 3: package rpmfusion-free-release-29-1.noarch requires system-release(29), but none of the providers can be installed - fedora-release-29-7.noarch does not belong to a distupgrade repository - problem with installed package rpmfusion-free-release-29-1.noarch Problem 4: package vlc-core-1:3.0.6-16.fc29.x86_64 requires libprotobuf-lite.so.15()(64bit), but none of the providers can be installed - protobuf-lite-3.5.0-8.fc29.x86_64 does not belong to a distupgrade repository - problem with installed package vlc-core-1:3.0.6-16.fc29.x86_64 Problem 5: package fedora-release-29-7.noarch requires fedora-repos(29) >= 1, but none of the providers can be installed - package rpmfusion-nonfree-release-29-1.noarch requires system-release(29), but none of the providers can be installed - fedora-repos-29-2.noarch does not belong to a distupgrade repository - problem with installed package rpmfusion-nonfree-release-29-1.noarch Problem 6: problem with installed package blender-1:2.79b-9.fc29.x86_64 - package blender-1:2.79b-10.fc30.x86_64 requires libboost_locale.so.1.66.0()(64bit), but none of the providers can be installed - boost-locale-1.66.0-14.fc29.x86_64 does not belong to a distupgrade repository - blender-1:2.79b-9.fc29.x86_64 does not belong to a distupgrade repository Problem 7: problem with installed package darktable-2.6.0-2.fc29.x86_64 - package darktable-2.6.0-2.fc30.x86_64 requires libexiv2.so.26()(64bit), but none of the providers can be installed - exiv2-libs-0.26-12.fc29.x86_64 does not belong to a distupgrade repository - darktable-2.6.0-2.fc29.x86_64 does not belong to a distupgrade repository Problem 8: problem with installed package pgp-tools-2.7-3.fc29.x86_64 - package pgp-tools-2.7-3.fc29.x86_64 requires /usr/bin/pgpring, but none of the providers can be installed - mutt-5:1.10.1-1.fc29.x86_64 does not belong to a distupgrade repository Problem 9: problem with installed package gns3-server-2.1.11-1.fc29.x86_64 - package gns3-server-2.1.11-2.fc30.x86_64 requires python3.7dist(prompt-toolkit) = 1.0.15, but none of the providers can be installed - python3-prompt_toolkit-1.0.15-1.fc29.noarch does not belong to a distupgrade repository - gns3-server-2.1.11-1.fc29.x86_64 does not belong to a distupgrade repository Problem 10: problem with installed package ImageMagick-c++-1:6.9.9.38-3.fc29.x86_64 - package ImageMagick-c++-1:6.9.10.27-1.fc30.x86_64 requires libMagickCore-6.Q16.so.6()(64bit), but none of the providers can be installed - package ImageMagick-c++-1:6.9.10.27-1.fc30.x86_64 requires libMagickWand-6.Q16.so.6()(64bit), but none of the providers can be installed - package ImageMagick-c++-1:6.9.10.27-1.fc30.x86_64 requires ImageMagick-libs(x86-64) = 1:6.9.10.27-1.fc30, but none of the providers can be installed - cannot install both ImageMagick-libs-1:6.9.10.27-1.fc30.x86_64 and ImageMagick-libs-1:6.9.9.38-3.fc29.x86_64 - package python3-libopenshot-0.2.2-1.fc29.x86_64 requires libMagickCore-6.Q16.so.5()(64bit), but none of the providers can be installed - package python3-libopenshot-0.2.2-1.fc29.x86_64 requires libMagickWand-6.Q16.so.5()(64bit), but none of the providers can be installed - ImageMagick-c++-1:6.9.9.38-3.fc29.x86_64 does not belong to a distupgrade repository - problem with installed package python3-libopenshot-0.2.2-1.fc29.x86_64 Problem 11: problem with installed package ImageMagick-1:6.9.9.38-3.fc29.x86_64 - package ImageMagick-1:6.9.10.27-1.fc30.x86_64 requires libMagickCore-6.Q16.so.6()(64bit), but none of the providers can be installed - package ImageMagick-1:6.9.10.27-1.fc30.x86_64 requires libMagickWand-6.Q16.so.6()(64bit), but none of the providers can be installed - package ImageMagick-1:6.9.10.27-1.fc30.x86_64 requires ImageMagick-libs(x86-64) = 1:6.9.10.27-1.fc30, but none of the providers can be installed - cannot install both ImageMagick-libs-1:6.9.10.27-1.fc30.x86_64 and ImageMagick-libs-1:6.9.9.38-3.fc29.x86_64 - package python3-libopenshot-0.2.2-1.fc29.x86_64 requires libMagickCore-6.Q16.so.5()(64bit), but none of the providers can be installed - package python3-libopenshot-0.2.2-1.fc29.x86_64 requires libMagickWand-6.Q16.so.5()(64bit), but none of the providers can be installed - package openshot-2.4.3-2.fc29.noarch requires python3-libopenshot >= 0.2.2, but none of the providers can be installed - ImageMagick-1:6.9.9.38-3.fc29.x86_64 does not belong to a distupgrade repository - problem with installed package openshot-2.4.3-2.fc29.noarch Wondring if there is anything here worth filling has bugs ( the vlc one for instance is not worth filling as it comes from fusion and fusion as not branched yet). Ludo

5 5

Fedora 33 blocker status
by Ben Cotton 16 Oct '20

16 Oct '20

We've branched, so let's start the weekly blocker status email yayyyyy Action summary ==================== Accepted blockers ----------------- 1. libreport — abrt-server errors when processing zstd compressed core dumps produced by systemd-246~rc1-1.fc33 — POST ACTION: abrt maintainers to make a new release containing the fix 2. resteasy — FreeIPA deployment fails in current Rawhide due to various issues with Java 11 — NEW ACTION: resteasy maintainers to diagnose issue and fix or pass the buck as appropriate 3. sddm — login stuck when changing users repeatedly (log out, log in a different one) — NEW ACTION: sddm maintainers to diagnose issue and fix or pass the buck as appropriate 4. selinux-policy — SELinux is preventing systemd-machine from 'create' accesses on the sock_file io.systemd.Machine. — POST ACTION: selinux-policy maintainers to make a new release containing the fixes 5. tomcat — FreeIPA server deployment fails in Fedora-Rawhide-20200714.n.0 — MODIFIED ACTION: tomcat maintainers to investigate failed upgrade test Proposed blockers ----------------- 1. gnome-shell — Network manager started stuck when I tries connecting to VPN (openconnect) after upgrade gnome-shell to 3.37.1-1.fc33 version — NEW ACTION: gnome-shell maintainers to diagnose issue 2. systemd — systemd-resolved.service not work with DNS server placed behind VPN (openconnect) — NEW ACTION: systemd maintainers to diagnose issue 3. udisks2 — zram-setup(a)zram0.service: Failed to load configuration: No such file or directory — NEW ACTION: Someone! to figure out why udisks2-zram gets pulled in Bug-by-bug detail ============= Accepted blockers ----------------- 1. libreport — https://bugzilla.redhat.com/show_bug.cgi?id=1860616 — POST abrt-server errors when processing zstd compressed core dumps produced by systemd-246~rc1-1.fc33 abrt doesn't support core dumps compressed with zstd, which is now used by systemd. Merged upstream PR uses libarchive to add support for zstd (and other compression formats): https://github.com/abrt/libreport/pull/656. 2. resteasy — https://bugzilla.redhat.com/show_bug.cgi?id=1866570 — NEW FreeIPA deployment fails in current Rawhide due to various issues with Java 11 Deploying FreeIPA fails with a traceback in pki-tomcat. This appears to be a dependency chain issue that (currently) ends at resteasy via dogtag-pki. This may not be the last layer in the Java 11 onion. 3. sddm — https://bugzilla.redhat.com/show_bug.cgi?id=1861700 — NEW login stuck when changing users repeatedly (log out, log in a different one) This is now a blocker based on a recent approval-in-principle of a release criterion related to logout and user switching. User processes linger after logout which blocks logging in when another user has logged in between the two sessions. Or when the second user logs back in. Or when a single user logs in repeatedly. Using KillUserProcesses=Yes helps the first problem, but raises on of its own. It appears to be a race condition of some kind as the behavior is not fully consistent. 4. selinux-policy — https://bugzilla.redhat.com/show_bug.cgi?id=1862686 — POST SELinux is preventing systemd-machine from 'create' accesses on the sock_file io.systemd.Machine. librvirt VMs and systemd-machined service fail with AVC denials. Merged upstream PRs should fix the denials mentioned in this bug: https://github.com/fedora-selinux/selinux-policy/pull/405 and https://github.com/fedora-selinux/selinux-policy/pull/407 5. tomcat — https://bugzilla.redhat.com/show_bug.cgi?id=1857043 — MODIFIED FreeIPA server deployment fails in Fedora-Rawhide-20200714.n.0 due to pki-tomcat failing to run with "java.lang.ClassNotFoundException: org.apache.tomcat.util.modeler.modules.MbeansDescriptorsIntrospectionSource" An upstream commit resulted in tomcat-coyote.jar missing packages. A previous fix (FEDORA-2020-f897a68801) moved the goalposts. tomcat-9.0.37-3 should fix this. Verification is blocked on BZ1866570, but Adam's most recent upgrade test still fails with a ClassNotFoundException for com.sun.xml.internal.bind.v2.ContextFactory. Proposed blockers ----------------- 1. gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=1830343 — NEW Network manager started stuck when I tries connecting to VPN (openconnect) after upgrade gnome-shell to 3.37.1-1.fc33 version Connecting to an OpenConnect VPN using 2FA hangs after the second factor is entered. The journal contains an array.toString() message which may or may not be a red herring (it looks like a deprecation warning). 2. systemd — https://bugzilla.redhat.com/show_bug.cgi?id=1863041 — NEW systemd-resolved.service not work with DNS server placed behind VPN (openconnect) When connected to an OpenConnect VPN, host name resolution fails. Manually disabling the systemd-resolved service works around this issue. 3. udisks2 — https://bugzilla.redhat.com/show_bug.cgi?id=1861463 — NEW zram-setup(a)zram0.service: Failed to load configuration: No such file or directory Installation on armhfp and aarch64 single-board computers fails with zram-setup errors. It appears to be a conflict betwen udisks2-zram and zram-generator-defaults. Update FEDORA-2020-e143a283fb renamse the service unit file to make its origin more obvious. Removing udisks2-zram fixes the issue, but it's pulled in as a dependency of something, so that needs to be identified. -- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis

4 14

Unable to boot on Raspberry Pi 4B
by Ashish Kumar 10 Oct '20

10 Oct '20

Hi, I am trying to boot Fedora IoT aarch64 images on my Raspberry Pi 4B but failing to do so as I see an error that EFI was unable to load the image. I have tried using the raw images of the current 32 IoT and 33 Pre-release IoT. Please tell me where I am going wrong.

3 2

sort of Rawhide related
by David 30 Sep '20

30 Sep '20

My install of Rawhide had a nice update today. Below is just a screenshot showing two appimages running that I recently briefly mentioned. The beta version of Krita and Firefox. https://www.dropbox.com/s/7ri1m0uyuyr4jhz/Rawhide_9-30.png?dl=0 Along with some read-outs from inxi showing the rc7 kernel and mesa 20.2.0 along with my hardware specifications. htop looks normal with the YouTube video playing, but I didn't show it. I think somewhere on the internet, it should say that newbies should not use appimages for their web-browser, as my experience with that has been negative. But for tinkering with this beta of Krita, appimages seems like a good idea, but not for people new to Linux, at least not in 2020. However, they are no harder to use than a printer-driver, maybe even easier, than a printer-driver. David Locklear

1 0

Re: Unable to boot on Raspberry Pi 4B
by Ashish Kumar 30 Sep '20

30 Sep '20

Ok thank you for the update. On Wed, 30 Sep, 2020, 5:38 PM Klein Kravis, <kleinkravis44(a)outlook.com> wrote: > For the foreseeable future Fedora wi not run on Raspberry Pi 4. Please try > a 3B+ > On Sep 30, 2020, 7:07 AM -0500, Ashish Kumar <ashish.dav99(a)gmail.com>, > wrote: > > Hi, > I am trying to boot Fedora IoT aarch64 images on my Raspberry Pi 4B but > failing to do so as I see an error that EFI was unable to load the image. I > have tried using the raw images of the current 32 IoT and 33 Pre-release > IoT. Please tell me where I am going wrong. > _______________________________________________ > test mailing list -- test(a)lists.fedoraproject.org > To unsubscribe send an email to test-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://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org > > _______________________________________________ > test mailing list -- test(a)lists.fedoraproject.org > To unsubscribe send an email to test-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://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org >

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

test September 2020