desktop September 2022

desktop@lists.fedoraproject.org

18 participants
31 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

F32, Automatic suspend isn't working.
by Chris Murphy 02 Nov '22

02 Nov '22

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

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

03 Oct '22

# F36 Blocker Review meeting # Date: 2022-10-03 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.libera.chat Hi folks! We have 6 proposed Final blockers and 3 proposed Final freeze exceptions to review, so let's have a review meeting. Note, I will be away on Monday, so Geoff (coremodule) will run the 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 Geoff will 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

2 1

Fedora Workstation WG minutes, 2022-09-27
by Chris Murphy 27 Sep '22

27 Sep '22

============================================== #fedora-meeting-2: Workstation WG (2022-09-27) ============================================== Meeting started by brainycmurf at 16:18:44 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2022-09-27/workstation.2… . Meeting summary --------------- * Present members: Tomas, Michael, Kalev, Allan, Matthias, Jens, Neal, Chris (brainycmurf, 16:18:57) * Guests: (brainycmurf, 16:18:57) * Regrets: (brainycmurf, 16:18:57) * Missing: (brainycmurf, 16:18:57) * Secretary: Tomas (brainycmurf, 16:18:57) * F37 release status (brainycmurf, 16:18:58) * Final freeze: 4 October (brainycmurf, 16:19:00) * Early target release date: 18 October (brainycmurf, 16:19:02) * Kalev will be on vacation in October: 10 - 24 (brainycmurf, 16:19:04) * LINK: https://github.com/fedora-silverblue/issue-tracker/issues/120 (brainycmurf, 16:19:13) * LINK: https://github.com/fedora-silverblue/issue-tracker/issues/305 (brainycmurf, 16:19:18) * LINK: https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/330 (brainycmurf, 16:19:20) * Accepted blockers (brainycmurf, 16:19:24) * VERIFIED - [abrt] totem: nouveau_pushbuf_data(): totem killed by SIGABRT (brainycmurf, 16:19:26) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2123274 (brainycmurf, 16:19:28) * mesa multithreading issue. Looks like the upstream fixes have been backported. (brainycmurf, 16:19:30) * NEW - Windows with bitlocker enabled can't be booted, needs to use bootnext instead of chainloader (brainycmurf, 16:19:34) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2049849 (brainycmurf, 16:19:37) * No update from last week (brainycmurf, 16:19:41) * ASSIGNED - Abrt does not report a segfault which is reported in journalctl. (brainycmurf, 16:19:43) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2128662 (brainycmurf, 16:19:45) * No update, but some progress (brainycmurf, 16:19:49) * VERIFIED - gnome-software: Correct property name in GsRemovalDialog .ui file (brainycmurf, 16:19:53) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2125569 (brainycmurf, 16:19:55) * Done! (brainycmurf, 16:19:57) * ON_QA - Gnome-Maps crashes when searching for locations. (brainycmurf, 16:19:59) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2129914 (brainycmurf, 16:20:01) * In testing (brainycmurf, 16:20:05) * Proposed blockers (brainycmurf, 16:20:07) * NEW - Nautilus thumbnailing doesn't work on hidpi screens (brainycmurf, 16:20:09) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2127618 (brainycmurf, 16:20:11) * LINK: https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/977 (revert of the offending change) (brainycmurf, 16:20:16) * ACTION: Matthias to follow-up on this one. (brainycmurf, 16:20:20) * Approved Freeze exceptions (brainycmurf, 16:20:24) * POST - systemd returns an empty string for the chassis type (brainycmurf, 16:20:26) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2129343 (brainycmurf, 16:20:28) * Pending MR, Tomas will ping at the end of the week if no action by then (brainycmurf, 16:20:38) * NEW - GNOME keeps activating airplane mode on startup [when wi-fi and bluetooth are disabled] (brainycmurf, 16:20:40) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2129533 (brainycmurf, 16:20:43) * ACTION: Matthias will look for a volunteer to dig (brainycmurf, 16:20:51) * Give ABRT some lurve (brainycmurf, 16:20:57) * LINK: https://pagure.io/fedora-workstation/issue/130 (brainycmurf, 16:20:59) * ACTION: Tomas to get in touch with project owners to figure out the current resources that are allocated to the project. (brainycmurf, 16:21:05) * Consider limiting journal size (brainycmurf, 16:21:08) * LINK: https://pagure.io/fedora-workstation/issue/213 (brainycmurf, 16:21:10) * ACTION: Chris to evaluate the current state (brainycmurf, 16:21:17) * Announcements, Status Updates (brainycmurf, 16:21:19) * The minutes from last week have been posted. (brainycmurf, 16:21:21) * LINK: https://meetbot.fedoraproject.org/fedora-meeting-2/2022-09-20/workstation.2… (brainycmurf, 16:21:25) Meeting ended at 16:21:28 UTC. Action Items ------------ * Matthias to follow-up on this one. * Matthias will look for a volunteer to dig * Tomas to get in touch with project owners to figure out the current resources that are allocated to the project. * Chris to evaluate the current state Action Items, by person ----------------------- * **UNASSIGNED** * Matthias to follow-up on this one. * Matthias will look for a volunteer to dig * Tomas to get in touch with project owners to figure out the current resources that are allocated to the project. * Chris to evaluate the current state People Present (lines said) --------------------------- * brainycmurf (73) * zodbot (7) * Allan (0) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions

2 1

Fwd: Fedora Workstation WG minutes, 2022-09-20
by Luna Jernberg 27 Sep '22

27 Sep '22

---------- Forwarded message ---------- From: Luna Jernberg <droidbittin(a)gmail.com> Date: Tue, 27 Sep 2022 14:57:41 +0200 Subject: Re: Fedora Workstation WG minutes, 2022-09-20 To: Discussions about development for the Fedora desktop <desktop(a)lists.fedoraproject.org>, lists <lists(a)colorremedies.com>, lists <lists(a)coliris.com>, catanzaro <catanzaro(a)fedoraproject.org>, Allan Day <aday(a)redhat.com>, Luna Jernberg <bittin(a)fedoraproject.org>, Luna Jernberg <droidbittin(a)gmail.com>, Neal Gompa <ngompa13(a)gmail.com>, bittin <bittin(a)opensuse.org>, ngompa <ngompa(a)fedoraproject.org> Looked at the notes now missed the meeting as i was travelling, will miss the meeting this week too as i am helping out at the openSUSE Asia Summit 2022, will try to join again in October On Wed, Sep 21, 2022 at 12:48 AM Chris Murphy <lists(a)colorremedies.com> wrote: > ============================================== > #fedora-meeting-2: Workstation WG (2022-09-20) > ============================================== > > > Meeting started by brainycmurf at 22:40:00 UTC. The full logs are > available at > > https://meetbot.fedoraproject.org/fedora-meeting-2/2022-09-20/workstation.2… > . > > > > Meeting summary > --------------- > * Present members: Chris, Kalev, Allan, Michael, Jens, Owen, Neal > (brainycmurf, 22:40:19) > * Guests: (brainycmurf, 22:40:19) > * Regrets: Tomáš (brainycmurf, 22:40:19) > * Missing: (brainycmurf, 22:40:19) > * Secretary: Owen (brainycmurf, 22:40:20) > * F37 release status (brainycmurf, 22:40:20) > > * Blockers discussed last week (brainycmurf, 22:40:28) > * Update gnome-shell-extension-background-logo to 43.0 (brainycmurf, > 22:40:32) > * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2127192 > (brainycmurf, 22:40:34) > * Unable to set up enterprise account with gnome-initial-setup, > clicking continue does not join the domain (brainycmurf, 22:40:38) > * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2123494 > (brainycmurf, 22:40:41) > * Initial Setup uses the English keyboard, instead of the default > keyboard (brainycmurf, 22:40:49) > * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2121110 > (brainycmurf, 22:40:51) > * Windows with bitlocker enabled can't be booted, needs to use > bootnext instead of chainloader (brainycmurf, 22:40:56) > * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2049849 [have to > work around by changing boot order in the bios or using efibootmgr] > (brainycmurf, 22:40:59) > * Adam's proposing that we drop the release criteria for this > (brainycmurf, 22:41:02) > * LINK: > > https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/… > (brainycmurf, 22:41:04) > * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2123274 > (brainycmurf, 22:41:23) > * Correct property name in GsRemovalDialog .ui file (brainycmurf, > 22:41:28) > * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2125569 > (brainycmurf, 22:41:30) > * System menu shows only 8 VPN connections even if you have more > (brainycmurf, 22:41:36) > * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2125426 > (brainycmurf, 22:41:38) > * When a single contact is edited, it results in multiple contacts of > the same name (brainycmurf, 22:41:46) > * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2111003 > (brainycmurf, 22:41:48) > * screencast doesn't record the top layer (brainycmurf, 22:41:52) > * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2125439 > (brainycmurf, 22:41:54) > > * Improve the user feedback for OOM situations (brainycmurf, 22:41:58) > * LINK: https://pagure.io/fedora-workstation/issue/202 (brainycmurf, > 22:42:00) > > * Announcements, Status Updates (brainycmurf, 22:42:05) > * The minutes from last week have been posted. (brainycmurf, > 22:42:07) > * LINK: > > https://meetbot.fedoraproject.org/fedora-meeting-2/2022-09-13/workstation.2… > (brainycmurf, 22:42:09) > * Matthias will be at the Ubuntu Summit in early November in Prague > (brainycmurf, 22:42:12) > * GNOME Asia will be happening in early December in Malaysia - Call > for papers is currently open (brainycmurf, 22:42:16) > > Meeting ended at 22:47:40 UTC. > > > > > Action Items > ------------ > > > > > > Action Items, by person > ----------------------- > * **UNASSIGNED** > * (none) > > > > > People Present (lines said) > --------------------------- > * brainycmurf (57) > * zodbot (7) > * Allan (0) > > > > > Generated by `MeetBot`_ 0.4 > > .. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions > _______________________________________________ > desktop mailing list -- desktop(a)lists.fedoraproject.org > To unsubscribe send an email to desktop-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/desktop@lists.fedoraproject.o… > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue >

1 0

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

26 Sep '22

Dear all, You are kindly invited to the meeting: Workstation WG on 2022-09-27 from 09:30:00 to 10:30: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/

1 0

Workstation WG meeting, 27 September (secretary: Neal)
by Allan Day 26 Sep '22

26 Sep '22

Hi all, The next meeting of the Fedora Workstation Working Group is planned for Tuesday 27 September, at 9.30 EDT. Join links: - https://bluejeans.com/395383051/ - https://www.bluejeans.com/numbers See below for the agenda. Allan -- Agenda #topic F37 release status #topic Accepted blockers [abrt] totem: nouveau_pushbuf_data(): totem killed by SIGABRT #link https://bugzilla.redhat.com/show_bug.cgi?id=2123274 mesa multithreading issue. Looks like the upstream fixes have been backported. Windows with bitlocker enabled can't be booted, needs to use bootnext instead of chainloader #link https://bugzilla.redhat.com/show_bug.cgi?id=2049849 No developments since last week. Adam proposal to drop the release criteria still stands. Abrt does not report a segfault which is reported in journalctl. #link https://bugzilla.redhat.com/show_bug.cgi?id=2128662 Issue from last Wednesday. Unclear how much progress has been made on a fix. gnome-software: Correct property name in GsRemovalDialog .ui file #link https://bugzilla.redhat.com/show_bug.cgi?id=2125569 Milan is working on this. #topic Proposed blockers systemd returns an empty string for the chassis type #link https://bugzilla.redhat.com/show_bug.cgi?id=2125569 This is the missing Device Security panel issue. We're waiting on Richard's downstream systemd PR to be merged and released. Votes are currently -2 Nautilus thumbnailing doesn't work on hidpi screens #link https://bugzilla.redhat.com/show_bug.cgi?id=2127618 Matthias has an open GLib MR for this. Votes are currently -2 GNOME keeps activating airplane mode on startup [when wi-fi and bluetooth are disabled] #link https://bugzilla.redhat.com/show_bug.cgi?id=2129533 No signs of this getting attention, so far. Currently on +1 votes #topic Give ABRT some lurve #link https://pagure.io/fedora-workstation/issue/130 Where is this at? #topic Consider limiting journal size #link https://pagure.io/fedora-workstation/issue/213 Latest action was to create a concrete proposal, but who should do this, and where would the proposal go? #topic Announcements, Status Updates #info The minutes from last week have been posted. #link https://meetbot.fedoraproject.org/fedora-meeting-2/2022-09-20/workstation.2…

1 0

2022-09-26 @ 16:00 UTC - Fedora 37 Blocker Review Meeting
by Adam Williamson 25 Sep '22

25 Sep '22

# F36 Blocker Review meeting # Date: 2022-09-26 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.libera.chat Hi folks! We have 3 proposed Final blockers and 3 proposed Final freeze exceptions to review, so let's have a review meeting. If you have time today, 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 day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

1 0

Loud PC speaker beep during reboot, sometimes
by Kamil Paral 23 Sep '22

23 Sep '22

Completely randomly, my laptop sometimes emits a loud PC speaker beep while rebooting/powering off Fedora 37. The beep is very strong, and as a PC speaker sound, it of course ignores any configured volume level, mute status, and even headphones plugged in. I fortunately am in a different room than the rest of my family sleeps in, but if I were in the same room, and were I just a regular user, this would probably be the last day of Fedora on that laptop. The beep is that loud and uncomfortable, especially at night. I wonder if somebody else running F37 noticed it as well? Any hints what might cause it and how we can fix it? It never happened on F36 on the same laptop. Thanks, Kamil

4 6

Heads up: GNOME 43.0 megaupdate is in testing
by Kalev Lember 22 Sep '22

22 Sep '22

Hi all, Just a quick heads up that the GNOME 43.0 final release megaupdate is now in F37 updates-testing: https://bodhi.fedoraproject.org/updates/FEDORA-2022-0bd68bbb43 This is the GNOME version that's we'll be shipping F37 Final with, so please make sure to test it and file issues for things that would need fixing before F37 GA. I'd suggest starting upstream at gitlab.gnome.org for most issues, and then letting me (and other people) know in #fedora-workstation if anything needs backporting to Fedora (since there won't be any more upstream releases before F37 Final). If anything looks to be release blockery, then please also file issues downstream at bugzilla.redhat.com as soon as possible and mark them as blockers using the blockerbugs page, https://qa.fedoraproject.org/blockerbugs/milestone/37/final/buglist At the same time, please don't block the update with -1 karma unless there's something really amiss: We need the megaupdate to go stable and we can iterate from there. It all passed my own smoke testing and things were calm upstream and it's mostly just bug fixes at this point, compared to 43.rc. Thanks everybody and let's make this a good release! -- Kalev

3 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

desktop September 2022