desktop October 2022

desktop@lists.fedoraproject.org

11 participants
24 discussions

F32, Automatic suspend isn't working.
by Chris Murphy 26 Apr '25

26 Apr '25

cross-posting test@ and desktop@ Fedora Workstation 32 (upgraded from f31) Laptop on battery power set aside, 12 hours later it's dead instead of sleeping. On F31 it reliably would sleep after 20 minutes. Sleep still happens when pressing the power button and closing the lid. It seems to be a GNOME automatic suspend timer problem. Using dconf editor, I changed the /org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-timeout Custom value 30 and the problem doesn't happen. Is there a way to increase debug messages somehow to find out whether this timeout is being reached? And what process or policy is causing it to be reset? With the available information I can't figure out what's preventing sleep. -- Chris Murphy

2 1

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

Workstation WG meeting, 1 November (secretary: Kalev)
by Allan Day 01 Nov '22

01 Nov '22

Hi all, The next meeting of the Fedora Workstation Working Group is planned for Tuesday 1 November, at 10:00 EDT. Join links: - https://bluejeans.com/395383051/ - https://www.bluejeans.com/numbers See below for the agenda. Allan -- Agenda #topic F37 release status An OpenSSL critical vulnerability has pushed the release back. The next go/no-go meeting will be held 1700 UTC on Thursday 10 November. The current target release date is 15 November. #topic Consider limiting journal size #link https://pagure.io/fedora-workstation/issue/213 Are there any takeaways from the mailing list thread that Chris started? Does this still need testing, or can we decide on a new proposal? #topic Workstation QA arrangements Allan had a call with Fedora QA on 13th October: * QA plan to prioritise testing the beta, and will aim to cover all the preinstalled apps in the beta testing. * Open questions about the usefulness of the RC test day: https://pagure.io/fedora-workstation/issue/334 * Concerns remain about the quality of Maps, Contacts, Calendar, Photos. #topic GNOME Software format preference #topic Working group chair for F38 #link https://pagure.io/fedora-workstation/issue/338 #topic Announcements, Status Updates #info F37 Online Release Party Friday-Saturday 4-5th November 2022 :: https://hopin.com/events/fedora-linux-37-release-party/registration #info The minutes from last week have been posted. #link https://meetbot.fedoraproject.org/fedora-meeting-2/2022-10-25/workstation.2…

2 2

[Fedocal] Reminder meeting : Workstation WG
by catanzaro＠fedoraproject.org 31 Oct '22

31 Oct '22

Dear all, You are kindly invited to the meeting: Workstation WG on 2022-11-01 from 10:00:00 to 11:00: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.gnome.org/p/fedora-workstation-wg More information available at: https://fedoraproject.org/wiki/Workstation Source: https://calendar.fedoraproject.org//meeting/10142/

2 1

2022-10-31 @ 16:00 UTC - Fedora 37 Blocker Review Meeting
by Adam Williamson 28 Oct '22

28 Oct '22

# F36 Blocker Review meeting # Date: 2022-10-31 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.libera.chat Hi folks! We have 1 proposed Final freeze exception to review, but also we can probably kick around the plans for the release process over the next couple of weeks (hence the wide distribution on this mail - come along if you want to talk about that!), 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 F36 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 Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

1 0

Fedora Workstation WG minutes, 2022-10-25
by Chris Murphy 25 Oct '22

25 Oct '22

============================================== #fedora-meeting-2: Workstation WG (2022-10-25) ============================================== Meeting started by brainycmurf at 17:28:10 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2022-10-25/workstation.2… . Meeting summary --------------- * Present members: Tom,Michael,Thomas, Matthias, Zac, Kalev, Jens, Owen, Neal (brainycmurf, 17:32:03) * Guests:Luna(bittin) (brainycmurf, 17:32:03) * Regrets: Allan, Chris (brainycmurf, 17:32:03) * Missing: (brainycmurf, 17:32:03) * Secretary: Matthias (brainycmurf, 17:32:03) * F37 release status (brainycmurf, 17:32:04) * F37 Online Release Party Friday-Saturday (next week) 4-5th November 2022 (brainycmurf, 17:32:09) * LINK: https://hopin.com/events/fedora-linux-37-release-party/registration (brainycmurf, 17:32:13) * One accepted blocker remaining: calendar recurrent events issues. (brainycmurf, 17:32:15) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2135772 https://pagure.io/fedora-qa/blocker-review/issue/977 (brainycmurf, 17:32:17) * May get waived. Noone working on it. (brainycmurf, 17:32:20) * Announcements, Status Updates (brainycmurf, 17:32:22) * David King <amigadave> is taking over GNOME builds for the next 6 months for the GNOME 43/44 cycle from Kalev. (brainycmurf, 17:32:24) * toolboxes are failing to build for a while (brainycmurf, 17:32:29) * LINK: https://pagure.io/releng/issue/11092 (brainycmurf, 17:32:31) * Add VS Code to the 3rd party repos (brainycmurf, 17:32:35) * LINK: https://pagure.io/fedora-workstation/issue/283 (brainycmurf, 17:32:37) * Consider limiting journal size (brainycmurf, 17:32:49) * LINK: https://pagure.io/fedora-workstation/issue/213 (brainycmurf, 17:32:51) * fedora-autofirstboot (brainycmurf, 17:32:59) * LINK: https://pagure.io/fedora-workstation/issue/84 (brainycmurf, 17:33:03) * LINK: https://pagure.io/fedora-workstation/issue/242 (brainycmurf, 17:33:05) * ACTION: Neal to write a change proposal for the autoremoval of Anaconda on firstboot (brainycmurf, 17:33:09) * ACTION: Neal to build ffmpeg for EPEL 9 for RHEL 9.1 (brainycmurf, 17:33:15) * GNOME Software format preference (brainycmurf, 17:33:17) * dst ends in europe next weekend. so next meeting is 1 hour earlier for people in Europe (brainycmurf, 17:33:21) * The minutes from last week have been posted. (brainycmurf, 17:33:23) * LINK: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-10-21/workstation.2… (brainycmurf, 17:33:25) Meeting ended at 17:34:16 UTC. Action Items ------------ * Neal to write a change proposal for the autoremoval of Anaconda on firstboot * Neal to build ffmpeg for EPEL 9 for RHEL 9.1 Action Items, by person ----------------------- * **UNASSIGNED** * Neal to write a change proposal for the autoremoval of Anaconda on firstboot * Neal to build ffmpeg for EPEL 9 for RHEL 9.1 People Present (lines said) --------------------------- * brainycmurf (46) * zodbot (7) * 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 25 Oct '22

25 Oct '22

Dear all, You are kindly invited to the meeting: Workstation WG on 2022-10-25 from 10:00:00 to 11:00: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.gnome.org/p/fedora-workstation-wg More information available at: https://fedoraproject.org/wiki/Workstation Source: https://calendar.fedoraproject.org//meeting/10142/

2 1

2022-10-24 @ 16:00 UTC - Fedora 37 Blocker Review Meeting
by Adam Williamson 21 Oct '22

21 Oct '22

# F36 Blocker Review meeting # Date: 2022-10-24 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.libera.chat Hi folks! We have 1 proposed Final blocker and 1 proposed Final freeze exception 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 F36 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 Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

1 0

Fedora Workstation WG minutes, 2022-10-18
by Allan Day 21 Oct '22

21 Oct '22

Full logs are available at: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-10-21/workstation.2… # Meeting summary Present members: Allan, Owen, Chris, Michael, Tomas, Matthias, Jens (aday, 08:28:18) Guests: Arnaud (aday, 08:28:18) Regrets: Kalev (aday, 08:28:20) Missing: (aday, 08:28:22) Secretary: Jens (aday, 08:28:24) F37 release status (aday, 08:28:28) * ACTION: Allan to review the "what's new" Fedora Magazine post (aday, 08:28:45) * ACTION: Neal to check on the upgrade banner in Software (aday, 08:28:47) F37 blockers (aday, 08:28:56) * fontconfig brokenness on Silverblue (aday, 08:29:43) * https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/330 (aday, 08:29:45) * https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/331 (aday, 08:29:47) Give ABRT some love (aday, 08:29:55) * https://pagure.io/fedora-workstation/issue/130 (aday, 08:29:57) Work on a new appindicator protocol (aday, 08:30:06) * https://pagure.io/fedora-workstation/issue/264 (aday, 08:30:10) * https://gitlab.freedesktop.org/xdg/xdg-specs/-/issues/84 (aday, 08:30:15) * ACTION: Michael to ensure that there's a comment on the protocol ticket, with a summary of what still needs to be done (aday, 08:30:23) * ACTION: Allan to investigate who might be interested in taking the shell UI forward on the GNOME side (aday, 08:30:26) Announcements, Status Updates (aday, 08:30:31) * The minutes from last week have been posted. (aday, 08:30:37) * https://meetbot.fedoraproject.org/fedora-meeting-2/2022-10-13/workstation.2… (aday, 08:30:41)

1 0

Workstation WG meeting, 18 October (secretary: Jens) **NEW TIME**
by Allan Day 19 Oct '22

19 Oct '22

Hi all, The next meeting of the Fedora Workstation Working Group is planned for Tuesday 18 October, at 10:00 EDT. Note the new time: we are now meeting at 10:00 EDT, as opposed to the previous time of 9:30 EDT. This will be the new regular time going forward. Join links: - https://bluejeans.com/395383051/ - https://www.bluejeans.com/numbers See below for the agenda. Allan -- Agenda #topic F37 release status Kalev on vacation 10-24 October #topic F37 blockers gnome-calendar - Changes to recurring events don't redraw correctly - https://bugzilla.redhat.com/show_bug.cgi?id=2132769 gnome-calendar - Editing a recurring event moves it forward in time - https://bugzilla.redhat.com/show_bug.cgi?id=2132772 For the Calendar issues, Ray posted workarounds. There are also potential fixes upstream. contacts - Link Contacts feature completely broken - https://bugzilla.redhat.com/show_bug.cgi?id=2130661 Niels seems to have a partial fix. In the meantime, Michael pushed a change to hide contact linking. glibc - glibc 2.36+ breaks EAC with removal of DT_HASH (and other game libraries), making games fail to load - https://bugzilla.redhat.com/show_bug.cgi?id=2129358 Carlos O'Donell has a patch, but it doesn't seem to be ready. Neal has a separate patch to revert the upstream commit that caused the issue. There's also a fair number of workstation-related freeze exceptions: https://qa.fedoraproject.org/blockerbugs/milestone/37/final/buglist #topic fontconfig brokenness on Silverblue #link https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/330 #link https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/331 Did this get tested yet? #topic Give ABRT some love #link https://pagure.io/fedora-workstation/issue/130 #topic Work on a new appindicator protocol #link https://pagure.io/fedora-workstation/issue/264

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

desktop October 2022