test September 2023

test@lists.fedoraproject.org

23 participants
30 discussions

Kernel 6.5 Test Week 2023-09-10 to 2023-09-17
by Sumantro Mukherjee 10 Sep '23

10 Sep '23

Hey All, I would like to invite all of you to participate in the Kernel 6.5 Test week is happening from 2023-09-10 to 2023-09-17. It's fairly simple, head over to the wiki [0] and read in detail about the test week and simply run the test case mentioned in[1] and enter your results. As usual, the Fedora QA team will hangout at #fedora-test-day(a)libera.chat for questions and discussion. [0] http://fedoraproject.org/wiki/Test_Day:2023-09-10_Kernel_6.5_Test_Week [1] https://testdays.fedoraproject.org/events/166 -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED

1 0

[PSA] Toolbx is now marked as crit-path by Workstation
by Sumantro Mukherjee 08 Sep '23

08 Sep '23

Hey All, As a part of the changeset[0] we had infra help us out with Images and QA help us out with criterion [1] and OpenQA test[2]. As a final step, we have finally added Toolbx as a crit-path under "workstation" [3] . We have a Toolbx Test day on 2023-09-14 [4] , come and help us iron out any rough edges before release Thanks to Infra and Rel-eng for all the help here :) [0] https://fedoraproject.org/wiki/Changes/ToolbxReleaseBlocker [1] https://fedoraproject.org/wiki/Fedora_39_Beta_Release_Criteria#Toolbx_Funct… [2] https://pagure.io/fedora-qa/os-autoinst-distri-fedora/blob/main/f/tests/too… [3] https://pagure.io/fedora-comps/pull-request/885 [4] https://testdays.fedoraproject.org/events/167 -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED

1 0

F38: GNOME on XORG: Some apps have Windows titlebar with Minimize/Maximize Buttons
by Dario Lesca 07 Sep '23

07 Sep '23

I use "GNOME on Xorgs", today I have try to update f38 to f39. Like occur on F38, also into f39 some apps, like Firefox or Libreoffice, have top bar size different from gnome native apps like gnome-terminal or nautilus. Also the Middle-Click mouse button set to "lower" click on top bar do not work on the apps with different top bar You can try this problem also use the last F39 Workstation live version (Fedora-Workstation-Live-x86_64-39-20230907.n.0.iso), if you set password to liveuser then logoff and logon with "GNOME on Xorgs" you can see this problem. If you use default GNOME on Wayland, lower function work on all top bar type I have also fill this bug: https://bugzilla.redhat.com/show_bug.cgi?id=2192180 See also In GNOME 44, window top bar doesn't work properly under Xorg https://www.reddit.com/r/gnome/comments/12ubuya/in_gnome_44_window_top_bar_… There is a workaround to resolve this annoying issue? Many thanks -- Dario Lesca (Inviato dal mio Linux Fedora 38 Workstation) _______________________________________________ users mailing list -- users(a)lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- Dario Lesca (Inviato dal mio Linux Fedora 38 Workstation)

1 0

freeze exceptions for FTI bugs
by Kamil Paral 05 Sep '23

05 Sep '23

Lately we've seen a surge of FTI (fails to install) bugs being proposed as freeze exceptions [1] [2]. We generally grant them, because we want the base repo to be in a consistent and buildable state. However, I wonder, isn't this approach mostly relevant for the Final release? Does it make sense to also have this approach for Beta? The reason why I'm thinking about this is because of course there's some work connected with granting and processing these freeze exceptions (FEs). But at the same time, updates-testing is enabled by default, so users can get the fixed versions immediately, and the fixes can be pushed stable right after the Beta freeze is over. Is the extra FE-related work justified? One reason I can think of is when the package A in question needs to be used for rebuilding/installing another package B. In that case, if package A is not pushed stable, you can't prepare an update for package B into updates-testing (or can you? Can you build several inter-connected packages together and make a Bodhi update for them? What if you have access rights to just package B but not A?). I do understand that in this case waiting until the freeze lifts might be inconvenient. What if we granted FEs for Beta just in these justified cases but not in general, in order to decrease the processing-work? Is that a good/bad idea? Or perhaps we can grant FTI FEs automatically? Either always, or in some cases? What are your thoughts on this? Thanks, Kamil [1] https://qa.fedoraproject.org/blockerbugs/milestone/39/beta/buglist [2] https://pagure.io/fedora-qa/blocker-review/issues?status=all&search_pattern…

4 7

Re: Donate 1 minute of your time to test upgrades from F38 to F39
by Luna Jernberg 04 Sep '23

04 Sep '23

Did this on my Thinkpad Edge a couple of days ago, and it went fine :) Den ons 23 aug. 2023 kl 20:23 skrev Miroslav Suchý <msuchy(a)redhat.com>: > > Do you want to make Fedora 39 better? Please spend 1 minute of your time and try to run: > > # Run this only if you use default Fedora modules > # next time you run any DNF command default modules will be enabled again > sudo dnf module reset '*' > > dnf --releasever=39 --setopt=module_platform_id=platform:f39 \ > --enablerepo=updates-testing \ > $(rpm -q fedora-repos-modular >/dev/null && echo --enablerepo=updates-testing-modular) \ > --assumeno distro-sync > > > This command does not replace `dnf system-upgrade`, but it will reveal potential problems. > > You may also run `dnf upgrade` before running this command. > > > The `--assumeno` will just test the transaction, but does not make the actual upgrade. > > > In case you hit dependency issues, please report it against the appropriate package. > > Or against fedora-obsolete-packages if that package should be removed in Fedora 39. Please check existing reports against fedora-obsolete-packages first: > > https://red.ht/2kuBDPu > > and also there is already bunch of "Fails to install" (F39FailsToInstall) reports: > > https://bugzilla.redhat.com/buglist.cgi?bug_id=2168845&bug_id_type=anddepen… > > > Two notes: > > * you may want to run the same command with dnf5 to help test new dnf. > > * this command found zero issues on my personal system - great work all everybody! > > > Thank you > > Miroslav > _______________________________________________ > devel mailing list -- devel(a)lists.fedoraproject.org > To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

1 1

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 2023