Introducing Steam + video game testing criteria
by Neal Gompa
Hey all,
I would like for us to have some testing criteria around gaming and
Steam so that we can ensure we're offering a working gaming experience
in Fedora Linux releases. This is motivated by the issue we had in the
F37 cycle where glibc broke popular multiplayer games[1]. I was
reminded of this when I launched Steam today on F38 and zenity
crashed[2].
I would like to propose the following criterion for Steam itself as a
Beta Blocker bug:
"Steam MUST be able to be installed and have its basic functionality
work with no visible errors. Basic functionality for Steam includes:
logging into a Steam account and installing a Windows/Proton game and
a Linux/SteamOS native game."
For gaming itself, I would like to propose the following criterion as
a Final Blocker bug:
"Steam games identified as Deck Verified by ProtonDB.com (see
https://www.protondb.com/explore?selectedFilters=whitelisted) MUST
launch and let the user play the game. This criterion is not intended
to judge performance, merely accessibility. At least one
Windows/Proton game and one Linux/SteamOS native game MUST be tested
in this manner."
Now, the tricky issue here is how to wordsmith the check for
anti-cheat systems. I don't want to specifically call out just EAC,
but I also don't know of a good mix of games with different
anti-cheats. The important thing is to catch regressions and see if
it's something we can resolve. In the EAC case from F37, it was easy
for us to deal with, but if it's genuinely broken in a way we can't
deal with it on the Fedora side, I don't know what we're supposed to
do, so I'm wary of doing some kind of blocker criterion for that.
I'd also like this to be imposed on both release-blocking desktops:
GNOME and KDE Plasma.
Any ideas welcome and appreciated!
[1]: https://pagure.io/fesco/issue/2873
[2]: https://bugzilla.redhat.com/2177287
--
真実はいつも一つ！/ Always, there's only one truth!
1 month
fwupd problem F38 WS
by AV
Before I start investigating/reporting a "bug" I would
like to ask if there is some sort of problem with the "shim"
in Fedora 38 WS.
I get the following result using fwupdmgr:
Perform operation? [Y|n]: y
Decompressing… [ ]
Blocked executable in the ESP, ensure grub and shim are up to date:
/boot/efi/EFI/fedora/shimx64-fedora.efi Authenticode checksum
[0ce02100f67c7ef85f4eed368f02bf7092380a3c23ca91fd7f19430d94b00c19] is
present in dbx
AV
1 month
coreutils in Rawhide ~ behavior change to the -v option on cp?
by Ian Laurie
It looks to me like there has been a recent change to the verbose
reporting option on the cp command.
Previously (and still in Fedora 38) the -v option will report on files
actually copied, but ignores files not copied (for example when -v is
used with -u).
However in Rawhide the -v option now reports on files skipped when used
with -u, which has made a big mess of many of my bash scripts.
Anyone know if there is some trick to reverting traditional behavior?
Ian
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
1 month
Fwd: Broken gcc 13.0.1-0.15.fc39 (missing <amxcomplexintrin.h>)
by Luna Jernberg
---------- Forwarded message ----------
From: Mattia Verga via devel <devel(a)lists.fedoraproject.org>
Date: Sun, 23 Apr 2023 10:00:46 +0000
Subject: Re: Broken gcc 13.0.1-0.15.fc39 (missing <amxcomplexintrin.h>)
To: devel(a)lists.fedoraproject.org
Cc: Mattia Verga <mattia.verga(a)proton.me>
Il 23/04/23 11:17, Tomasz Kłoczko ha scritto:
> Hi,
>
> Looks like with latest gcc 31.0.1-0.15.fc39 many packages builds are failing with:
>
> /usr/lib/gcc/x86_64-redhat-linux/13/include/immintrin.h:135:10: fatal error: amxcomplexintrin.h: No such file or directory
> 135 | #include <amxcomplexintrin.h>
> | ^~~~~~~~~~~~~~~~~~~~
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109600
>
> kloczek
> --
> Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH
Today I was able to builda package that was previously failed,
gcc-13.0.1-0.16.fc39 has fixed the problem in Rawhide.
Mattia
1 month
Fwd: Broken gcc 13.0.1-0.15.fc39 (missing <amxcomplexintrin.h>)
by Luna Jernberg
---------- Forwarded message ----------
From: Tomasz Kłoczko <kloczko.tomasz(a)gmail.com>
Date: Sun, 23 Apr 2023 10:17:04 +0100
Subject: Broken gcc 13.0.1-0.15.fc39 (missing <amxcomplexintrin.h>)
To: Development discussions related to Fedora <devel(a)lists.fedoraproject.org>
Hi,
Looks like with latest gcc 31.0.1-0.15.fc39 many packages builds are
failing with:
/usr/lib/gcc/x86_64-redhat-linux/13/include/immintrin.h:135:10: fatal
error: amxcomplexintrin.h: No such file or directory
135 | #include <amxcomplexintrin.h>
| ^~~~~~~~~~~~~~~~~~~~
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109600
kloczek
--
Tomasz Kłoczko | LinkedIn: *http://lnkd.in/FXPWxH <http://lnkd.in/FXPWxH>*
1 month
Self-introduction Juan Carlos Quiroz jcqa24
by Juan Carlos Quiroz
Hi everyone
I'm Juan Carlos Quiroz, I'm 28 years old and live in Mexico City.
Before collaborate to Gentoo wiki as Translator.
I love to test the most new software for this reason I would like to
contribute to test Fedora, also I'm learning all about testing, test plans
and test cases.
I know some languages such as: C, C++, Rust, Python, Java, and others
languages for backend and frontend.
Thanks for letting me be part of this project.
Bye
---------------------------------
Att:
Juan Carlos Quiroz Aguilar
jcqa24
jcqa24(a)gmail.com
1 month, 1 week
Proposing a QA Classroom/Onboarding Call
by Sumantro Mukherjee
Hey Folks!
I am proposing a QA classroom to cover the following topics:
Introduction to Fedora QA: This section could provide an overview of
what Fedora QA is, what it does, and why it's important to the Fedora
community.
Fedora QA Team Structure: This section could introduce the different
roles within the Fedora QA team and explain how they work together to
ensure the quality of Fedora releases.
Getting Started with Fedora QA: This section could provide practical
information on how to get started with Fedora QA, including how to
join the team, where to find relevant documentation and resources, and
how to get in touch with other team members.
Fedora Release Process: This section could explain the Fedora release
process, including the different stages of development, testing, and
release, and how Fedora QA fits into this process.
Testing Tools and Techniques: This section could introduce the testing
tools and techniques used by Fedora QA, including automation tools,
manual testing procedures, and other testing methodologies.
Reporting Bugs and Issues: This section could explain how to report
bugs and issues found during testing, including how to use Bugzilla,
how to write good bug reports, and how to communicate effectively with
developers and other team members.
Working with the Fedora Community: This section could provide guidance
on how to work effectively with other Fedora community members,
including developers, packagers, and other QA team members.
Conclusion and Next Steps: This section could summarize the key
takeaways from the onboarding call and provide information on what to
do next, including how to get involved in specific testing projects
and how to continue learning and growing within the Fedora QA
community.
I wanted to ask what will be a good time and date?
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
1 month, 1 week
