test October 2024

test@lists.fedoraproject.org

30 participants
33 discussions

nomodeset kernel parameter appears to cause startx failure
by George R Goffe 14 Oct '24

14 Oct '24

Hi, I've been having a consistent failure of startx apparently due to the addition of "nomodeset" to the kernel boot parameters. I have been using "nomodeset" for several years. This has been happening for about 2 weeks. See startx log below. Has anyone else seen this problem? Best regards, George... xauth: file /root/.serverauth.136471 does not exist xauth: (stdin):2: unknown command "3cf149665e8d99e82510d31544f1a594" X.Org X Server 1.21.1.13 X Protocol Version 11, Revision 0 Current Operating System: Linux fc42 6.12.0-0.rc0.20240927git075dbe9f6e3c.14.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Sep 27 17:02:57 U TC 2024 x86_64 Kernel command line: BOOT_IMAGE=(hd0,msdos1)/vmlinuz-6.12.0-0.rc0.20240927git075dbe9f6e3c.14.fc42.x86_64 root=UUID=6ef3dfc3-32ed-4f01 -bebb-64f66a016d37 ro resume=UUID=e3537362-f3a8-48f3-94e7-f7b4de63fe42 nomodeset vga 791 net.ifnames=0 biosdevname=0 audit=0 selinux= 0 Build ID: xorg-x11-server 21.1.13-4.fc42 Current version of pixman: 0.43.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct 2 10:37:28 2024 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) Fatal server error: (EE) no screens found(EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. (EE) (EE) Server terminated with error (1). Closing log file. xinit: giving up xinit: unable to connect to X server: Connection refused xinit: server error

6 12

2024-10-14 @ 16:00 UTC - Fedora 41 Blocker Review Meeting
by Adam Williamson 13 Oct '24

13 Oct '24

# F10 Blocker Review meeting # Date: 2024-10-14 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for a Fedora 41 blocker review meeting! We have 3 proposed blockers and 6 proposed freeze exceptions for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+41+Blocker… The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

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

13 Oct '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.

1 0

dnf5-command(repomanage)
by Robert McBroom 11 Oct '24

11 Oct '24

I maintain a local repository of the rpms on my systems. In earlier versions the commands dnf repomanage --old . |xargs rm -rf cd ../ createrepo_c --update -c cachedir Packages executed from the directory ..../Packages would clean out superseded rpm files and set up the repository. What replaces dnf repomanage in the dnf5 system in fc42?

3 2

[Test Days] Fedora Virt and Upgrade happening NOW!
by Sumantro Mukherjee 10 Oct '24

10 Oct '24

Hey Folks, As the GA date comes closer; we are trying to test the last few bits in Fedora. Fedora takes pride in smooth upgrades and to ensure this we host Upgrade Test Day[0]. This time we are hosting it from 2024-10-11 through 2024-10-15. This installment of test day is, however, a bit special, we are not only looking for experience with Upgrade but also if things like DNF5 plugins remain functional after upgrading to F41 from F39 and F40. Some plugin functionalities are WIP[1] and feedback about the rest will be highly appreciated. Virt is a very integral part of the OS. QA team is hosting a Virt Test Days starting 2024-10-11 through 2024-10-13. Please participate and help us iron out bugs before the release date. As usual, we will be addressing questions over the test day channel and you can find the events on fedocal too a) Upgrade Test Day[3] b) Virt Test Day[4] [0] http://fedoraproject.org/wiki/Test_Day:2024-10-11_F41_Upgrade_Test_Day [1] https://github.com/rpm-software-management/dnf5/issues/389 [2] http://fedoraproject.org/wiki/Test_Day:2024-10-11_Virtualization [3] https://calendar.fedoraproject.org/QA/#m10913 [4]https://calendar.fedoraproject.org/QA/#m10912 -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED <https://redhat.com/trusted>

1 0

Proposing Beta UT package set enable Release Criteria
by Sumantro Mukherjee 10 Oct '24

10 Oct '24

Hey folks, A few moons ago, I volunteered to write a Beta Release Criteria. The idea is to set a "criteria" to have Beta images with Updates Testing enabled by default. Note, we *do* this and have been doing this for some time and nothing has broken badly due to keeping UT repos enabled. This IMO will encourage our community to try to test more Beta images and package sets which will be served to them when they upgrade to Beta or install beta from various installation sources. Proposed Beta Criteria: Release identification A fedora-release package containing the correct names and information and a fedora-repos package containing the correct repository configuration for a Beta Fedora release must be present on release-blocking images and the appropriately versioned generic-release package must be available in the release repository. updates-testing enabled One specific expectation is that the updates-testing repository and any corresponding repositories (e.g. updates-testing-modular) must be enabled for upgrades to beta and fresh installs. Please let me know your thoughts. -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED <https://redhat.com/trusted>

6 8

Re: Removal of vesa and fbdev X.org drivers from Rawhide
by Sérgio Basto 08 Oct '24

08 Oct '24

On Tue, 2024-10-08 at 11:02 +0200, Javier Martinez Canillas wrote: > Peter Robinson <pbrobinson(a)gmail.com> writes: > > Hello Peter and Adam, > > > Hi Adam, > > > > > I noticed that the vesa and fbdev X.org drivers were recently > > > retired > > > from Rawhide. There appears to be no Change for this. The commit > > I remember that there was a Change for this filed by Ajax some time > ago: > > https://fedoraproject.org/wiki/Changes/LegacyXorgDriverRemoval > > but I see now that FESCo didn't approve it at the time: > > https://pagure.io/fesco/issue/3059#comment-875144 > > So I guess that Peter's commit needs to be reverted... > > This is partially my fault, because Peter did ask me if I thought > that it > is time to drop the xorg-x11-drv-{vesa,fbdev} DDX drivers and I said > yes. This information is interesting , but remove of vesa , fbdev on Fedora was not Peter ... As stated in F37 Change: Legacy Xorg Driver Removal (System-Wide Change proposal) https://fedoraproject.org/wiki/Changes/LegacyXorgDriverRemoval nomodeset can be replaced by vga=ask and vesa and fbdev drivers can be an alias of modesetting drive That is the point for me, if we have an replacement there is no point on keeping old code. we are revisiting https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… and after reading a bit, I support Adam's decision and I'm convinced that is the correct > > > messages for the retirements refer to this old Change: > > > > > > https://fedoraproject.org/wiki/Changes/ReplaceFbdevDrivers#Detailed_Descrip… > > > > > > but that Change was for Fedora 36, and was considered "completed" > > > at > > > the time with no removal of any X.org drivers. The scope of that > > > Change > > > says nothing about retiring X.org drivers. > > > > > > This has had at least one substantial impact that somebody > > > noticed: > > > https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/… > > > > > > booting with 'nomodeset', which has decades of history as a > > > standard > > > workaround for having some kind of issue with the native driver > > > for > > > your hardware, no longer works, it seems. > > > > > Yes, agreed that we shouldn't break that. > > > > To me this is a significant change which maybe should be a > > > Change, not > > > just slipped in with reference to a Change from six releases ago > > > which > > > did not have this in its scope. > > > > Yeah, probably Ajax's proposal could be revisited. > > > In all fallback cases it should be using simpledrm and the > > associated > > mesa driver. There's been a number of changes since the original F- > > 36 > > change that has moved a bunch of that stuff forward to the point > > that > > there's little to no fbdev left, did you mean vesa? > > > > I don't see enough info on that thread to tell. > > > > I believe this could be a problem for x86 legacy BIOS systems that > are not > setting a VGA mode using the "vga=" kernel cmdline parameter. Since > in that > case a VESA mode isn't set and so a "simple-framebuffer" device won't > be > registered and match the simpledrm driver. > > In those cases, probably just goes from vgacon -> Xorg + xorg-x11- > drv-vesa. > The user won't have a fbcon/VT, but at least will get Xorg working > with the > user-space vesa driver. > > A solution could be for Anaconda to add a "vga=ask" or "vga=795" (a > default > resolution of 1920x1080) to the kernel cmdline or the "safe graphics > mode" > entry. That way, a "simple-framebuffer" device will be registered by > sysfb > and the simpledrm driver probed. > > Then users will have both a fbcon/VT and could even start a wayland > session > even in the "safe graphics mode". > > > P > > -- > > -- > Best regards, > > Javier Martinez Canillas > Core Platforms > Red Hat > -- Sérgio M. B.

1 0

Announcing FCOS 41 Test Week 2024-10-07 through 2024-10-11
by Sumantro Mukherjee 06 Oct '24

06 Oct '24

Hey All, During the week of Oct 7-11, the Fedora 41 CoreOS Test Week will be happening. The test week is an opportunity for the community to test FCOS based on Fedora 41 content before it is released as part of the `testing` and `stable` streams. As part of the Test Week, we'll host a virtual in-person session on Tuesday October 8 from 10:00 AM - 11:30 AM EDT (2:00 PM - 3:30PM UTC) where you can drop in, ask questions and get help from members of the Fedora CoreOS team. If you want to participate in the Test Week, check out the Fedora Wiki page for details and log your results on the Test Day page. - Wiki: https://fedoraproject.org/wiki/Test_Day:Fedora_41_CoreOS - Test Day Results: https://testdays.fedoraproject.org/events/198 - FCOS Tracker: https://github.com/coreos/fedora-coreos-tracker/issues/1801 - QA Ticket: https://pagure.io/fedora-qa/issue/790 - Tue April 2 Video Meeting Link: https://meet.google.com/uwb-enhy-evg?authuser=0 - HackMD: https://hackmd.io/VGSXqQE1Qe2QUOKLQdcS-w?view Thanks for your interest and we hope to see you online! -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED <https://redhat.com/trusted>

1 0

Upgrade error problem in F41
by Joachim Backes 06 Oct '24

06 Oct '24

Having a problem when upgrading an installed F41: ... sudo dnf upgrade Breaks with: transaction failed: Rpm transaction failed. - file /usr/lib64/libtesseract.so.5.4.1 from install of tesseract-libs-5.4.1-4.fc41.x86_64 conflicts with file from package tesseract-5.4.1-2.fc41.x86_64 Anybody could solve this problem?? Kind regards Joachim Backes -- Fedora release 41 (Forty One) 6.11.2-300.fc41.x86_64 Joachim Backes <joachim.backes(a)rhrk.uni-kl.de> https://www-user.rhrk.uni-kl.de/~backes/

3 5

2024-10-07 @ 16:00 UTC - Fedora 41 Blocker Review Meeting
by Adam Williamson 04 Oct '24

04 Oct '24

# F10 Blocker Review meeting # Date: 2024-10-07 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for a Fedora 41 blocker review meeting! We have 5 proposed blockers and 1 proposed freeze exception for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+41+Blocker… The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

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