test October 2024

test@lists.fedoraproject.org

30 participants
33 discussions

Fedora 41 Beta iio-sensor-proxy stopped working after dnf upgrade
by manthony.nw＠gmail.com 06 Nov '24

06 Nov '24

I instaled Fedora 41 Beta workstation on a tablet and initially, iio-sensor-proxy was working to update screen orientation. The screen rotated automatically as in previous Fedora releases and the screen brightness updated based on the surrounding light levels. However, after upgrading via dnf, iio-sensor-proxy no longer updates. I tried loading the original kernel from the beta install, but it still does not work. I installed the beta to another tablet and the same thing occurred. The beta install works correctly until the dnf upgrade. I am new to this and not sure how to work out what part of the dnf update caused this or whether/how this should be reported as a bug. Any help would be appreciated.

2 1

Virtual Machine fails to load in f41
by Robert McBroom 31 Oct '24

31 Oct '24

Have two qemu/kvm virtual machines that were working in f40. Updated system to 41 and I'm getting the error that the iso for the rasberry os and the kali linux can't be accessed due to permissions. They are in /home/rm3/Downloads. The Rawhide virtual machine works with the fedora server ancestral file. What needs to be fixed? drwxr-xr-x. 2 rm3 rm3 4096 Oct 4 23:44 . drwxr-x---. 34 rm3 rm3 4096 Oct 23 22:16 .. -rw-r--r--. 1 qemu qemu 3607101440 Jan 25 2024 2022-07-01-raspios-bullseye-i386.iso -rw-r-xr--. 1 rm3 rm3 635371520 Mar 14 2023 Fedora-Server-KVM-38_Beta-1.3.x86_64.qcow2 -rw-r-xr--. 1 qemu qemu 481296384 May 21 2023 kali-linux-2023.1-installer-netinst-amd64.iso

3 3

Churning errors from selinux
by Robert McBroom 31 Oct '24

31 Oct '24

Alerts show over 100 errors SELinux is preventing systemd-tpm2-ge from 'read' accesses on the file tpm_version_major. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that systemd-tpm2-ge should be allowed read access on the tpm_version_major file by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Attempts to submit a bug give me a run around with creating an API key and then failing --- Running analyze_BodhiUpdates --- Looking for similar problems in bugzilla --- Running report_Bugzilla --- Checking for duplicates Bug search failed. Server says: 400 Bad Request Creating a new bug... Failed to create bug.

1 0

VirtualBox Guest Additions in F41
by Joachim Backes 26 Oct '24

26 Oct '24

In F41 I switched from Virtualbox.org (oracle) to the fedora edition of VirtualBox, and I learned that the past "Virtualbox guest addition" functions now have been realized by some fedora pkg called *virtualbox-guest-additions*, but I have problems to use this package (for CD or DVD or modify the guests sccreen resolution a.s.o.). Questions: Anybody knows where to get some detailed information about the usage of this package? Kind regards Joachim Backes Fedora release 41 (Forty One) 6.11.5-300.fc41.x86_64 Joachim Backes<joachim.backes(a)rhrk.uni-kl.de> https://www-user.rhrk.uni-kl.de/~backes/

4 4

Self-introduction: Niels-s
by Niels 25 Oct '24

25 Oct '24

Hi everyone, I'm joining the Fedora QA. Been using Linux for just around a year, but convinced in the meantime that Fedora's worth the effort to contribute to the community. No programming skills, more like an advanced user, focus would be beta-testing or something like that, we'll see. Thanks for your work & greetings from Germany, Niels FAS: Niels-s

2 1

Raspberry Pi 4B+ testing
by Brandon Nielsen 24 Oct '24

24 Oct '24

Hi all, I just noticed on my Pi 4B+ that display output on the second micro HDMI port (the one further from the USB-C power supply port) is corrupted. The first port is fine. The corruption is visible as rainbow halos around text during boot, and increasingly large areas of corruption after booting to a graphical desktop (green dots, color shifts, etc.). I can confirm this with the Fedora 41 1.3 RCs for both KDE and Workstation. Has anyone else seen this? I'm trying to rule out it just being a hardware fault with my unit. Brandon Nielsen

2 1

Help needed: Intel-based Mac dual boot testing
by Kamil Paral 24 Oct '24

24 Oct '24

Hi folks, if anyone has an Intel-based Mac (Macbook, Mac Mini) which could be used for dual-boot testing with Fedora 41, that would be very helpful. We don't have any such hardware at hand at the moment. The testing instructions are here: https://fedoraproject.org/wiki/QA:Testcase_dualboot_with_macOS and the latest F41 release candidate (RC) can be found here: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedorapro… If anyone has such a device and can test dual-boot, please do and report back either here, or submit the result to our test matrix: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test#Misce… Thanks!

5 4

Upgrade to 41 from 39 stays on 39 but says it is 41
by ToddAndMargo 23 Oct '24

23 Oct '24

Hi All, I do not know if this is the correct place for this, but ... Now this is weird. Really, Really WEIRD! Yesterday I did the offline upgrade from FC39 to FC41 Beta. Now a fresh "# dnf upgrade" wants to download 3000+ FC39 rpm's. And "rpm -qa" shows 39 on everything. # cat /etc/redhat-release Fedora release 41 (Forty One) # rpm -qa gcc gcc-13.3.1-3.fc39.x86_64 # rpm -qa \*release\* rpmfusion-free-release-39-1.noarch fedora-release-identity-basic-39-36.noarch fedora-release-common-39-36.noarch fedora-release-39-36.noarch fedora-release-matecompiz-39-36.noarch My upgrade procedure (yes, I like to do a little clean up first): # rpm --rebuilddb # rpm -Va --nofiles --nodigest if anything is too new, do a # dnf downgrade offender(s) # dnf update --refresh # reboot and repeat the above update until no updates registered # remove-retired-packages <-- optional # dnf autoremove # dnf install dnf-plugin-system-upgrade # dnf system-upgrade download --refresh --releasever=41 # dnf install dnf-plugin-system-upgrade # rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-41-primary # dnf system-upgrade reboot --debugsolver # dnf system-upgrade log --number=1 gives me a 31157 line report. Tons of dnf stuff with no error I could find. It shows a ton of things being upgraded. For example: dnf-3[2799]: flexiblas-netlib64 x86_64 3.4.4-3.fc41 fedora dnf-3[2799]: Upgrading: marble-common-1:24.08.2-1.fc41.noarch 98/7819 dnf-3[2799]: Running scriptlet: pcre2-10.44-1.fc41.1.x86_64 148/7819 dnf-3[2799]: Obsoleting: kf5-libkexiv2-23.08.5-1.fc39.x86_64 182/7819 dnf-3[2799]: Cleanup: libgdata-0.18.1-9.fc39.x86_64 4183/7819 dnf-3[2799]: Verifying: kf5-akonadi-contacts-23.08.5-1.fc39.x86_64 26/7819 Upgraded: dnf-3[2799]: CharLS-2.4.2-6.fc41.x86_64 dnf-3[2799]: GeoIP-1.6.12-19.fc41.x86_64 <hundreds more -- all fc41> nf-3[2799]: tlwg-waree-fonts-0.7.3-9.fc39.noarch dnf-3[2799]: Complete! dnf-3[2799]: Cleaning up downloaded data... These are the final lines: systemd-shutdown[1]: Syncing filesystems > systemd-shutdown[1]: Sending SIGTERM to r> systemd-journald[78730]: Received SIGTERM> systemd-journald[78730]: Journal stopped lines 31135-31157/31157 (END) Checking "rpm -qa" for fc39 gives 3861 lines # rpm -qa | grep fc39 | grep -v fc41 | wc -l 3861 Checking "rpm -qa" for fc41 gives 0 lines: # rpm -qa | grep fc41 | grep -v fc39 | wc -l 0 I have over 400 GB free on my combined "/" "/home" partition. Yours in ABSOLUTE CONFUSION, -T -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Computers are like air conditioners. They malfunction when you open windows ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

3 5

Fedora KDE 41 RC 1.3 needs testing!
by Neal Gompa 23 Oct '24

23 Oct '24

Hey folks, The candidate release compose for Fedora Linux 41 was released yesterday[1], and we need YOUR help to ensure Fedora KDE is the best this cycle! Kamil Paral provided some instructions on how to do this just after Fedora Linux 41 Beta went out[2] and that guidance applies here. In particular, we *definitely* need folks testing on AArch64 with supported ARM platforms[3], notably the Raspberry Pi 4 series. This is a great way to contribute to Fedora KDE without needing to do any packaging or programming work to the benefit of yourself and the community at large. :) If folks need any real-time assistance, they can get help in the Fedora Quality Matrix room: https://matrix.to/#/#quality:fedoraproject.org Thanks in advance everyone! [1]: https://fedoraproject.org/wiki/Test_Results:Fedora_41_RC_1.3_Summary [2]: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org/m… [3]: https://fedoraproject.org/wiki/Architectures/ARM#Supported_Hardware_and_Dev… -- 真実はいつも一つ！/ Always, there's only one truth!

4 6

System doesn't fully wake from sleep when VM are in use
by Alessio 23 Oct '24

23 Oct '24

Hi friends. Fedora 41 fully updated. If I have running VMs (using virt-manager or GNOME Boxes) and I suspend the system, when I wake it up, the screen stays black and the keyboard is unresponsive (the caps lock led doesn't turn on/off). BTW the system looks somewhat alive, indeed I can ping it and eventually connect with ssh. If the VMs are off, the system can go to sleep and wake up normally. I can reproduce it on different machines. Do you have the chance to reproduce this issue? Ciao, A.

2 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

test October 2024