April 2024 - test - Fedora Mailing-Lists

changes to nouveau driver in kernel 6.8.2 and higher?

by AV

I have been trying out fedora 40 beta on a Dell XPS 15 9500 with integrated Intel UHD graphics and discrete Nvidia graphics. Everything worked perfectly with the 6.8.1 kernel and using nouveau but things started to happen after the upgrade to kernel 6.8.2 and later 6.8.4 kernel. First thing was an extremely slow boot, more than 3 minutes: systemd-analyze blame 3min 18.876s sys-module-fuse.device 3min 18.817s dev-ttyS11.device etc, etc. Looking with journalctl -k -b shows a very long list of entries for nouveau regularly containing the lines: kernel: nouveau 0000:01:00.0: disp: one-time init failed, -110 kernel: nouveau 0000:01:00.0: DRM: [DRM/00000000:drmDevice] [NEW dispc570] (ret:-110) kernel: WARNING: CPU: 11 PID: 452 at drivers/gpu/drm/nouveau/nvkm/subdev/gsp/r535.c:112 r535_gsp_msgq_wait+0x1a9/0x1d0 [nouveau]es: ---- kernel: nouveau 0000:01:00.0r -110: gsp: fini failed, -110 kernel: nouveau: probe of 0000:01:00.0 failed with error -110 I have not investigated if nouveau is the cause of these problems but it in any case appears to be implicated and there are also power management problems. Normally this laptop has a battery rate between 9-11W but now shows a rate above 25W in small task use. AV

1 month

3
3
0 / 0

Re: [Test-Announce] Fedora 40 Candidate RC-1.12 Available Now!

by Adam Williamson

On Wed, 2024-04-10 at 12:50 +0000, rawhide(a)fedoraproject.org wrote: > According to [the schedule][1], Fedora 40 Candidate RC-1.12 is now > available for testing. Please help us complete all the validation > testing! For more information on release validation testing, see: > https://fedoraproject.org/wiki/QA:Release_validation_test_plan > > Test coverage information for the current release can be seen at: > https://openqa.fedoraproject.org/testcase_stats/40 > > You can see all results, find testing instructions and image download > locations, and enter results on the Summary page: > > https://fedoraproject.org/wiki/Test_Results:Fedora_40_RC_1.12_Summary > > The individual test result pages are: > > https://fedoraproject.org/wiki/Test_Results:Fedora_40_RC_1.12_Installation > https://fedoraproject.org/wiki/Test_Results:Fedora_40_RC_1.12_Base > https://fedoraproject.org/wiki/Test_Results:Fedora_40_RC_1.12_Server > https://fedoraproject.org/wiki/Test_Results:Fedora_40_RC_1.12_Cloud > https://fedoraproject.org/wiki/Test_Results:Fedora_40_RC_1.12_Desktop > https://fedoraproject.org/wiki/Test_Results:Fedora_40_RC_1.12_Security_Lab An update on this: we have RC-1.13 coming in a few hours, but it just fixes some filenames and updates uboot-tools from the RC to the final release. Most 1.12 testing will be valid, so please continue to test 1.12 while 1.13 is cooking. At Go/No-Go tomorrow we'll decide whether to ship 1.13 based on the testing of both. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw(a)fosstodon.org https://www.happyassassin.net

1 month

1
0
0 / 0

Re: Looking for people to be stewards of rpminspect-data-fedora

by Adam Williamson

On Tue, 2024-04-09 at 14:14 -0700, Kevin Fenzi wrote: > On Tue, Apr 09, 2024 at 01:55:41PM -0400, David Cantrell wrote: > > Hello all, > > > > I am looking for multiple people to help be upstream stewards of the rpminspect-data-fedora project. This is a project that contains config files and rules for running rpminspect on Fedora builds. It is a package containing distribution policy. It needs people to look over it and review and merge contributions from other developers, do occassional releases, and ensure that it is updated as new releases of Fedora are started (and we get new dist tags). > > > > The project currently lives here: > > > > https://github.com/rpminspect/rpminspect-data-fedora > > > > But absolutely can move depending on the desires of the individuals who take over maintenance. I created these rules files in the data package for rpminspect so that different vendors can customize how rpminspect runs and reacts to findings. Maintenance of the rules is independent of the software maintenance. > > > > If you are interested, please email me directly and we can get going on the logistics. If you have general questions, feel free to ask here. > > I wonder if this isn't something we should have the QE or releng teams > manage... ie, adding new branch info (releng), adjusting tests (qe)? potentially we can be involved in this, yes. I did not have time to look at it yet because of F40 release. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw(a)fosstodon.org https://www.happyassassin.net

1 month, 1 week

1
0
0 / 0

Emacs installs are now broken for non-Wayland users

by Ian Laurie

With emacs-29.3-2.fc40 non-Wayland users will need to explicitly uninstall emacs after installing emacs-gtk+x11 because emacs is installed as a weak dependency, and its presence breaks emacs because if users launch via the desktop launcher emacs rather than emacs-gtk+x11 will launch (at least under Xfce). https://bodhi.fedoraproject.org/updates/FEDORA-2024-7985b5f326 Of course all this assumes you know in the first place that you need to install emacs-gtk+x11 and not emacs... which is another debacle. -- Ian Laurie FAS: nixuser | IRC: nixuser TZ: Australia/Sydney

1 month, 1 week

1
1
0 / 0

kernel test fail submit on second run!

by Cătălin George Feștilă

I have an error on second submit on kernel test : Test suite complete PASS Your log file is being submitted... Traceback (most recent call last): File "/home/mythcat/kernel-tests/./fedora_submit.py", line 43, in <module> submitclient.login( File "/usr/lib/python3.12/site-packages/fedora/client/openidbaseclient.py", line 303, in login response = openid_login( ^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/fedora/client/openidproxyclient.py", line 138, in openid_login raise AuthError(output['message']) fedora.client.AuthError: Invalid request The following information is not submitted with your log; it is for informational purposes only. Vulnerability status: The first run work well the second not give me that error: sudo ./runall.sh sudo ./runall.sh --performance - has that error configuration is : # submit=none # submit=anonymous submit=authenticated

1 month, 1 week

2
2
0 / 0

[Now Playing] Intel Open CL Test Day

by Sumantro Mukherjee

Hey All, We're hosting an Intel OpenCL Test Day[0] and we need your expertise! Join us on 2024-04-09 to put Intel's OpenCL through its paces. Your feedback will be invaluable in shaping the future of this technology. Together, let's push the boundaries of performance and innovation. Intel's OpenCL (Open Computing Language) is a powerful framework for parallel computing across CPUs, GPUs, and FPGAs. It enables developers to harness the full potential of Intel's hardware, optimizing performance for a wide range of applications from AI and machine learning to high-performance computing. By participating in our test day, you'll gain hands-on experience and contribute directly to the enhancement of Intel's OpenCL platform for Fedora 40. [0] http://fedoraproject.org/wiki/Test_Day:2024-04-09_Intel_Open_CL -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED

1 month, 1 week

1
0
0 / 0

Bash terminal: intermittently, significant lag up to 20 seconds for characters to be rendered on the screen

by John Lynch

Since upgrading from 39 to 40, when I issue a command in the Terminal, sometimes I have to wait for the character to be displayed. If I press another key, then the previous character shows up, but it continues thus. I am running an Asus laptop with 16GB RAM and quad-core CPU. Has anyone else encountered such behaviour with Fedora 40?

1 month, 1 week

3
2
0 / 0

2024-04-08 @ 16:00 UTC - Fedora 40 Blocker Review Meeting

by Adam Williamson

# F40 Blocker Review meeting # Date: 2024-04-08 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[elemen... Hi folks! It's time for another blocker review meeting. We have 4 proposed blockers and 5 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+40+Block... 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 tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw(a)fosstodon.org https://www.happyassassin.net

1 month, 1 week

1
0
0 / 0

[Call for Action] Testing Alibaba Cloud for Fedora CoreOS 40

by Sumantro Mukherjee

Hey folks, As many of you might know, we are currently running the Fedora 40 CoreOS Test Week.[0] We would like to have anyone with Alibaba account to run this test case[1] and report [2] under Alibaba column. Should you have any questions, please let us know via email or https://matrix.to/#/#test-day:fedoraproject.org [0] http://fedoraproject.org/wiki/Test_Day:Fedora_40_CoreOS [1] https://fedoraproject.org/wiki/QA:Testcase_CoreOS_Alibaba [2] https://testdays.fedoraproject.org/events/179 -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED

1 month, 2 weeks

1
0
0 / 0

Fedora Silverblue 40 behind a proxy

by julien.tognazzi＠gmail.com

Hello all, I wanted to try silverblue for a long time, and I have now the opportunity to try it with the release of Fedora 40 beta. I noticed some issues regarding proxy configuration. I first configured the proxy for my user via Gnome Settings. I used the full url with schema like: HTTP Proxy http://myproxy:8080 HTTPS Proxy http://myproxy:8080 but then I noticed that my bash environment was automatically populated with the relevant proxy environment variables (which is good), but then the schema appeared twice ! env | grep proxy https_proxy=http://http://myproxy:8080/ HTTPS_PROXY=http://myproxy:8080/ HTTP_PROXY=http://http://myproxy:8080/ http_proxy=http://http://myproxy:8080/ I also noticed that the rpm-ostreed service needed to know about the proxy, So I tried to configured the proxy with systemd with: cat /etc/systemd/system.conf.d/50-proxy.conf [Manager] DefaultEnvironment="HTTP_PROXY=http://myproxy:8080 DefaultEnvironment="http_proxy=http://myproxy:8080 DefaultEnvironment="HTTPS_PROXY=http://myproxy:8080 DefaultEnvironment="https_proxy=http://myproxy:8080 DefaultEnvironment="NO_PROXY=int, *.int" DefaultEnvironment="no_proxy=int, *.int" But it did not seem to make rpm-ostreed happy. So I used instead: cat /etc/systemd/system/rpm-ostreed.service.d/http-proxy.conf [Service] Environment="http_proxy=http://myproxy:8080" Environment="https_proxy=http://myproxy:8080" Then I could upgrade the rpm-ostree. another issue is that gnome-software is very slow to load/show updates. Do I need here to configured the proxy somehow ? But I would have guess that the gnome-settings configuration would be enough... Am I missing something still ?

1 month, 2 weeks

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

test April 2024