desktop March 2023

desktop@lists.fedoraproject.org

11 participants
25 discussions

Plan / proposal: enable openQA update testing and potentially gating on Rawhide updates
by Adam Williamson 09 Jun '23

09 Jun '23

Hi folks! We've had openQA testing of updates for stable and branched releases, and gating based on those tests, enabled for a while now. I believe this is going quite well, and I think we addressed the issues reported when we first enabled gating - Bodhi's gating status updates work more smoothly now, and openQA respects Bodhi's "re-run tests" button so failed tests can be re-triggered. A few weeks ago, I enabled testing of Rawhide updates in the openQA lab/stg instance. This was to see how smoothly the tests run, how often we run into unexpected failures or problems, and whether the hardware resources we have are sufficient for the extra load. So far this has been going more smoothly than I anticipated, if anything. The workers seem to keep up with the test load, even though one out of three worker systems for the stg instance is currently out of commission (we're using it to investigate a bug). We do get occasional failures which seem to be related to Rawhide kernel slowness (e.g. operations timing out that usually don't otherwise time out), but on the whole, the level of false failures is (I would say) acceptably low, enough that my current regime of checking the test results daily and restarting failed ones that don't seem to indicate a real bug should be sufficient. So, I'd like to propose that we enable Rawhide update testing on the production openQA instance also. This would cause results to appear on the Automated Tests tab in Bodhi, but they would be only informational (and unless the update was gated by a CI test, or somehow otherwise configured not to be pushed automatically, updates would continue to be pushed 'stable' almost immediately on creation, regardless of the openQA results). More significantly, I'd also propose that we turn on gating on openQA results for Rawhide updates. This would mean Rawhide updates would be held from going 'stable' (and included in the next compose) until the gating openQA tests had run and passed. We may want to do this a bit after turning on the tests; perhaps Fedora 37 branch point would be a natural time to do it. Currently this would usually mean a wait from update submission to 'stable push' (which really means that the build goes into the buildroot, and will go into the next Rawhide compose when it happens) of somewhere between 45 minutes and a couple of hours. It would also mean that if Rawhide updates for inter-dependent packages are not correctly grouped, the dependent update(s) will fail testing and be gated until the update they depend on has passed testing and been pushed. The tests for the dependent update(s) would then need to be re- run, either by someone hitting the button in Bodhi or an openQA admin noticing and restarting them, before the dependent update(s) could be pushed. In the worst case, if updated packages A and B both need the other to work correctly but the updates are submitted separately, both updates may fail tests and be blocked. This could only be resolved by waiving the failures, or replacing the separate updates with an update containing both packages. All of those considerations are already true for stable and branched releases, but people are probably more used to grouping updates for stable and branched than doing it for Rawhide, and the typical flow of going from a build to an update provides more opportunity to create grouped updates for branched/stable. For Rawhide the easiest way to do it if you need to do it is to do the builds in a side tag and use Bodhi's ability to create updates from a side tag. As with branched/stable, only critical path updates would have the tests run and be gated on the results. Non-critpath updates would be unaffected. (There's a small allowlist of non-critpath packages for which the tests are also run, but they are not currently gated on the results). I think doing this could really help us keep Rawhide solid and avoid introducing major compose-breaking bugs, at minimal cost. But it's a significant change and I wanted to see what folks think. In particular, if you find the existing gating of updates for stable/branched releases to cause problems in any way, I'd love to hear about it. Thanks folks! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

3 8

Bug in Software app?
by John Mellor 03 Apr '23

03 Apr '23

I'm in the habit of running the Gnome Software updater when I power up and login every morning on my stone-stock and fully up-to-date F37 machines, as it generally sees a half-dozen updates on average every day. I do not normally use the CLI dnf update mechanism, as it is more cumbersome. I've been noticing lately when I switch to the updates panel, that it reports that everything is up-to-date, checked just now. I have 4 machines exhibiting this same incorrect behaviour. If I click the recheck button to check again, I see the updates that it is missing without manual intervention. So, there is a faulty short-circuit somewhere in it, and there is clearly a bug in the normal update path in this package. Is there an unreleased or in-test fix for this defect? Or am I the first reporter of this fault and a bugzilla is required? How many people are missing critical security updates because of this fault? Is this error corrected in F39? -- John Mellor

2 2

2023-04-03 @ 16:00 UTC - Fedora 38 Blocker Review Meeting
by Adam Williamson 31 Mar '23

31 Mar '23

# F38 Blocker Review meeting # Date: 2023-04-03 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.libera.chat Hi folks! We have 2 proposed Final blockers and 2 proposed Final freeze exception issues to review, so let's have a review meeting. 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 F38 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

Fedora Workstation WG minutes, 2023-03-28
by Chris Murphy 30 Mar '23

30 Mar '23

============================================== #fedora-meeting-2: Workstation WG (2023-03-28) ============================================== Meeting started by brainycmurf at 00:55:13 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2023-03-31/workstation.2… . Meeting summary --------------- * Present members: Michael, Tomas, Matthias, Kalev, Jens, Chris, Allan, Neal (late) (brainycmurf, 00:55:33) * Guests: Martin Kolman, Jonas Adahl, Carlos Garnacho (brainycmurf, 00:55:33) * Regrets: Owen (brainycmurf, 00:55:33) * Missing: (brainycmurf, 00:55:33) * Secretary: Tomas (brainycmurf, 00:55:33) * Fedora 38 final blockers (brainycmurf, 00:55:34) * LINK: https://qa.fedoraproject.org/blockerbugs/milestone/38/final/buglist (brainycmurf, 00:55:36) * 1: crypto-policies: Insecure installed RPMs (like Google Chrome) prevent system updates in F38, can't be removed - ASSIGNED (brainycmurf, 00:55:42) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2170878 (brainycmurf, 00:55:45) * Discuss proposal of having Web UI installer for Fedora 39 Workstation (brainycmurf, 00:55:54) * LINK: https://pagure.io/fedora-workstation/issue/362 (brainycmurf, 00:55:56) * ACTION: FWWG needs to identify whether we will have the capacity to implement the keyboard layout handling for Fedora 39 (brainycmurf, 00:56:10) * Fractional scaling (brainycmurf, 00:56:13) * LINK: https://pagure.io/fedora-workstation/issue/357 (brainycmurf, 00:56:15) * ACTION: Allan will investigate design where to put the option into GNOME Control Center (is enough what Ubuntu does?) (brainycmurf, 00:56:34) * ACTION: Allan will look into how to pass a message on the user that the low DPI applications might be broken if the experimental gsetting is turned on (brainycmurf, 00:56:37) * Broadcom wireless (brainycmurf, 00:56:40) * LINK: https://pagure.io/fedora-workstation/issue/116 (brainycmurf, 00:56:42) * Announcements and status updates (brainycmurf, 00:56:46) * Last week's meeting minutes posted (brainycmurf, 00:56:50) * LINK: https://meetbot.fedoraproject.org/fedora-meeting-2/2023-03-22/workstation.2… (brainycmurf, 00:56:52) Meeting ended at 01:42:20 UTC. Action Items ------------ * FWWG needs to identify whether we will have the capacity to implement the keyboard layout handling for Fedora 39 * Allan will investigate design where to put the option into GNOME Control Center (is enough what Ubuntu does?) * Allan will look into how to pass a message on the user that the low DPI applications might be broken if the experimental gsetting is turned on Action Items, by person ----------------------- * **UNASSIGNED** * FWWG needs to identify whether we will have the capacity to implement the keyboard layout handling for Fedora 39 * Allan will investigate design where to put the option into GNOME Control Center (is enough what Ubuntu does?) * Allan will look into how to pass a message on the user that the low DPI applications might be broken if the experimental gsetting is turned on People Present (lines said) --------------------------- * brainycmurf (36) * zodbot (7) * Michael (0) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions

1 0

April 4, 2023 Workstation WG Meeting
by Michael Catanzaro 28 Mar '23

28 Mar '23

Hi all, The next meeting of the Fedora Workstation Working Group is planned for Tuesday, April 4, at 10:00 AM EDT (14:00 UTC). Please note the join link has changed again! We will try openSUSE's Jitsi Meet instance this time. Join link: https://meet.opensuse.org/FedoraWorkstationWG Agenda: #topic Fedora 38 final blockers #link https://qa.fedoraproject.org/blockerbugs/milestone/38/final/buglist #topic systemd-oomd seems overly aggressive (tentatively scheduled) #link https://pagure.io/fedora-workstation/issue/358 #topic Discuss proposal of having Web UI installer for Fedora 39 Workstation #link https://pagure.io/fedora-workstation/issue/362 #topic Broadcom wireless #link https://pagure.io/fedora-workstation/issue/116 #topic Announcements and status updates

1 0

[Fedocal] Reminder meeting : Workstation WG
by catanzaro＠fedoraproject.org 27 Mar '23

27 Mar '23

Dear all, You are kindly invited to the meeting: Workstation WG on 2023-03-28 from 10:00:00 to 10:50:00 US/Eastern At https://bluejeans.com/395383051/ The meeting will be about: Regular meeting for the Workstation Working Group Current Topics: https://pagure.io/fedora-workstation/issues?status=Open&tags=meeting Etherpad: https://etherpad.opensuse.org/p/fedora-workstation-wg More information available at: https://fedoraproject.org/wiki/Workstation Source: https://calendar.fedoraproject.org//meeting/10448/

1 0

2023-03-27 @ **16:00** UTC - Fedora 38 Blocker Review Meeting
by Adam Williamson 26 Mar '23

26 Mar '23

# F37 Blocker Review meeting # Date: 2023-03-27 # Time: **16:00** UTC # Location: #fedora-blocker-review on irc.libera.chat Hi folks! We have 3 proposed Final blockers and 1 proposed Final freeze exception issue to review, so let's have a review meeting. 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 F38 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

March 28, 2023 Workstation WG Meeting (secretary: Owen)
by Michael Catanzaro 23 Mar '23

23 Mar '23

Hi all, The next meeting of the Fedora Workstation Working Group is planned for Tuesday, March 28, at 10:00 AM EDT (14:00 UTC). Join link: https://meet.jit.si/FedoraWorkstationWG Agenda: #topic Fedora 38 final blockers #link https://qa.fedoraproject.org/blockerbugs/milestone/38/final/buglist #topic Fractional scaling #link https://pagure.io/fedora-workstation/issue/357 #topic Discuss proposal of having Web UI installer for Fedora 39 Workstation #link https://pagure.io/fedora-workstation/issue/362 #topic Broadcom wireless #link https://pagure.io/fedora-workstation/issue/116 #topic Announcements and status updates

2 1

Fedora Workstation WG minutes, 2023-03-21
by Chris Murphy 21 Mar '23

21 Mar '23

============================================== #fedora-meeting-2: Workstation WG (2023-03-21) ============================================== Meeting started by brainycmurf at 01:47:16 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2023-03-22/workstation.2… . Meeting summary --------------- * Present members: Tomas, Matthias, Jens, Owen, Michael, Kalev, Allan, Chris (brainycmurf, 01:47:26) * Guests: Jiri Konecny & Martin Kolman (Anaconda team), Ondrej Budai (brainycmurf, 01:47:26) * Regrets: Neal (brainycmurf, 01:47:26) * Missing: (brainycmurf, 01:47:26) * Secretary: Jens (brainycmurf, 01:47:26) * Discuss proposal of having Web UI installer for Fedora 39 Workstation (brainycmurf, 01:47:27) * LINK: https://pagure.io/fedora-workstation/issue/362 (brainycmurf, 01:47:29) * Fedora 38 final blockers (brainycmurf, 01:48:09) * Broadcom wireless (brainycmurf, 01:48:15) * LINK: https://pagure.io/fedora-workstation/issue/116 (brainycmurf, 01:48:17) * Announcements and status updates (brainycmurf, 01:48:21) * GUADEC 2023 call for papers is open until March 27th (brainycmurf, 01:48:23) * LINK: https://foundation.gnome.org/2023/02/24/guadec-2023-cfp/ (brainycmurf, 01:48:25) * Last week's meeting minutes posted (brainycmurf, 01:48:27) * LINK: https://meetbot.fedoraproject.org/fedora-meeting-2/2023-03-16/workstation.2… (brainycmurf, 01:48:29) Meeting ended at 01:48:32 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * brainycmurf (38) * zodbot (7) * Michael (0) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions

1 0

[Fedocal] Reminder meeting : Workstation WG
by catanzaro＠fedoraproject.org 21 Mar '23

21 Mar '23

Dear all, You are kindly invited to the meeting: Workstation WG on 2023-03-21 from 10:00:00 to 10:50:00 US/Eastern At https://bluejeans.com/395383051/ The meeting will be about: Regular meeting for the Workstation Working Group Current Topics: https://pagure.io/fedora-workstation/issues?status=Open&tags=meeting Etherpad: https://etherpad.opensuse.org/p/fedora-workstation-wg More information available at: https://fedoraproject.org/wiki/Workstation Source: https://calendar.fedoraproject.org//meeting/10448/

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

desktop March 2023