desktop July 2022

desktop@lists.fedoraproject.org

7 participants
14 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

Computer
by Alejandro López 21 Sep '22

21 Sep '22

Greetings, my name is Alejandro Lopez from Slimbook Computers and I'm writing this email following Matthew's advice. We are hardware company committed to the flawless integration and improvement of the end user experience with the Linux OS and the hardware it runs on. We were given the chance to work together with the KDE team back in 2016 when other laptop brands didn't even think about it, and after getting the approval from both parties, the objective of our collaboration was the birth of a modern and sleek device that excelled in performance and provided a flawless user experience for the community. The intent of this email is to let you know that the current demand for your amazing Fedora distribution is 2% from all our orders, and we think that this should change. I've sent to Matthew some general reports on which distros are currently in demand from our customers, and KDE Neon had an exponential growth versus other distros. What are your thoughts on this situation? I believe that we should work something out together to fix this. I think we should do more than offer Fedora as just another operating system (the user can choose up to 12 distributions). Thank you, -- *Alejandro López* /CEO/ <https://slimbook.es/?utm_source=mailfirma&utm_medium=free&utm_campaign=logo…> *The BEST GNU/Linux computers since 2015* alejandrolopez(a)slimbook.es www.slimbook.es <https://slimbook.es/?utm_source=mailfirma&utm_medium=free&utm_campaign=enla…> Este mensaje y sus archivos adjuntos van dirigidos exclusivamente a su destinatario, pudiendo contener información confidencial sometida a secreto profesional. No está permitida su reproducción o distribución sin la autorización expresa de Grupo Odin Soluciones Informáticas, S.L.N.E. Si usted no es el destinatario final por favor elimínelo e infórmenos por esta vía. De acuerdo con lo establecido por la Ley Orgánica 15/1999, de 13 de diciembre, de Protección de Datos de Carácter Personal (LOPD), le informamos que sus datos están incorporados en un fichero del que es titular Grupo Odin Soluciones Informáticas, S.L.N.E. con la finalidad de realizar la gestión administrativa, contable y fiscal, así como enviarle comunicaciones comerciales sobre nuestros productos y/o servicios. Asimismo, le informamos de la posibilidad de ejercer los derechos de acceso, rectificación, cancelación y oposición de sus datos en el correo electrónico: info(a)slimbook.es

8 14

Workstation WG meeting, 2 August (secretary: Neal)
by Allan Day 02 Aug '22

02 Aug '22

Hi all, The next meeting of the Fedora Workstation Working Group is planned for Tuesday 2 August, 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 GNOME 43 beta will start to appear this week GNOME 43 release notes are starting to be assembled: https://gitlab.gnome.org/Teams/Engagement/release-notes/-/issues/41 #topic Continuously available rawhide+GNOME mainline test images #link https://pagure.io/fedora-workstation/issue/311 #topic Update the QA tests cases for the preinstalled workstation apps #link https://pagure.io/fedora-workstation/issue/310 #topic Evaluate the state of gnome-contacts #link https://pagure.io/fedora-workstation/issue/307 #topic Announcements, Status Updates #info The minutes from last week have been posted. #link https://meetbot.fedoraproject.org/fedora-meeting-2/2022-07-27/workstation.2…

2 1

Fedora Workstation WG minutes, 2022-07-26
by Chris Murphy 27 Jul '22

27 Jul '22

============================================== #fedora-meeting-2: Workstation WG (2022-07-26) ============================================== Meeting started by brainycmurf at 01:31:53 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2022-07-27/workstation.2… . Meeting summary --------------- * Present members: Michael, Kalev, Tom, Chris, Jens, Owen, Allan (brainycmurf, 01:32:16) * Guests: Zac, Maira (brainycmurf, 01:32:16) * Regrets: Matthias, Neal (brainycmurf, 01:32:16) * Missing: (brainycmurf, 01:32:16) * Secretary: Tomáš (brainycmurf, 01:32:16) * Work on a new appindicator protocol (brainycmurf, 01:32:17) * LINK: https://pagure.io/fedora-workstation/issue/264 (brainycmurf, 01:32:19) * Announcements, Status Updates (brainycmurf, 01:32:27) * The minutes from last week have been posted. (brainycmurf, 01:32:32) * LINK: https://meetbot.fedoraproject.org/fedora-meeting-2/2022-07-20/workstation.2… (brainycmurf, 01:32:34) Meeting ended at 01:33:04 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * brainycmurf (17) * zodbot (7) * Allan (0) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions

2 1

Workstation WG meeting today, 26 July (secretary: Tomáš)
by Allan Day 26 Jul '22

26 Jul '22

The next meeting of the Fedora Workstation Working Group is planned for today (Tuesday 26 July), at 9.30 EDT. Join links: - https://bluejeans.com/395383051/ - https://www.bluejeans.com/numbers See below for the agenda. Allan -- Agenda #topic Work on a new appindicator protocol #link https://pagure.io/fedora-workstation/issue/264 #topic Announcements, Status Updates #info The minutes from last week have been posted. #link https://meetbot.fedoraproject.org/fedora-meeting-2/2022-07-20/workstation.2…

1 0

GNOME 43.alpha builds in rawhide
by Kalev Lember 20 Jul '22

20 Jul '22

Hi all, I'm back from my vacation and taking over GNOME builds and coordination again this cycle (David King handled GNOME 42 builds during the last cycle). Upstream is busily releasing 43.alpha and we need to get our downstream builds done as well. We have a f37-gnome side tag for builds, which should help make sure we keep rawhide breakage minimum (we can verify that things roughly work before merging it). This cycle the complicating elements seem to be: - continued porting from gtk 3 to gtk 4 - libsoup to libsoup3 transition - gnome-desktop3 and gnome-desktop4 soname bumps The last two in particular affect much more consumers than just GNOME so we need to be a bit careful here. Michael already filed a Change Proposal for libsoup3 and it should hopefully get approved by FESCo soon: https://pagure.io/fesco/issue/2829 Once we have FESCo approval for libsoup3 transition, I intend to go full steam ahead with GNOME 43.alpha and libsoup3 builds. I have already done a few in the side tag, but the rest is so tangled up that I think it's easier to wait a bit. If you are helping with builds, please use 'fedpkg build --target f37-gnome'. There's no need to use it if the update really is stand alone, but if it's tangled up in the rest of the GNOME update in some way, please use the side tag so we can ensure we don't break rawhide. Thanks for attention and thanks for the help! Kalev

3 3

Fedora Workstation WG minutes, 2022-07-19
by Chris Murphy 19 Jul '22

19 Jul '22

============================================== #fedora-meeting-2: Workstation WG (2022-07-19) ============================================== Meeting started by brainycmurf at 00:29:44 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2022-07-20/workstation.2… . Meeting summary --------------- * Present members: Michael, Chris, Owen, Allan, Kalev (brainycmurf, 00:29:59) * Guests: Luna (bittin) (brainycmurf, 00:29:59) * Regrets: Matthias, Neal, Jens, Tomáš (brainycmurf, 00:29:59) * Missing: (brainycmurf, 00:29:59) * Secretary: Chris (brainycmurf, 00:29:59) * Unfiltered Flathub (brainycmurf, 00:30:00) * LINK: https://pagure.io/fedora-workstation/issue/300 (brainycmurf, 00:30:04) * LINK: https://meetbot.fedoraproject.org/fedora-meeting/2022-07-12/fesco.2022-07-1… (brainycmurf, 00:30:06) * Status update: FESCO rejected the change, we'll revisit and address the issues, and is deferred until F38. (brainycmurf, 00:30:08) * F37 release schedule (brainycmurf, 00:30:11) * LINK: https://pagure.io/fedora-workstation/issue/312 (brainycmurf, 00:30:13) * This is a bit early, but useful to review and make sure we're on the same page with GNOME and Fedora QA folks being available. (brainycmurf, 00:30:21) * Improve the user feedback for OOM situations (brainycmurf, 00:30:45) * LINK: https://pagure.io/fedora-workstation/issue/202 (brainycmurf, 00:30:47) * ACTION: Chris will ask around, systemd folks for a dbus api, and for a desktop developer for advice on other next steps. (brainycmurf, 00:30:57) * LINK: https://github.com/systemd/systemd/issues/23606 (brainycmurf, 00:31:00) * Stale pending-action tickets (brainycmurf, 00:31:04) * Automatically install the OpenH264 codecs (brainycmurf, 00:31:06) * LINK: https://pagure.io/fedora-workstation/issue/84 (brainycmurf, 00:31:08) * Broadcom wireless (brainycmurf, 00:31:14) * LINK: https://pagure.io/fedora-workstation/issue/116 (brainycmurf, 00:31:16) * ACTION: Chris still plans to do a quickdoc on a subset of the issue (brainycmurf, 00:31:18) * 2m shutdown timer is too long (brainycmurf, 00:31:20) * LINK: https://pagure.io/fedora-workstation/issue/163 (brainycmurf, 00:31:22) * AGREED: should be 15 seconds, and we'll ask systemd devs how to do this for Workstation/desktops (brainycmurf, 00:31:26) * ACTION: Michael to comment in the ticket (brainycmurf, 00:31:28) * Announcements, Status Updates (brainycmurf, 00:31:30) * The minutes from last week have been posted. (brainycmurf, 00:31:34) * LINK: https://meetbot.fedoraproject.org/fedora-meeting-2/2022-07-12/workstation.2… (brainycmurf, 00:31:36) * GUADEC week this week in Mexico and Online with talks and the GNOME AGM (brainycmurf, 00:31:39) * LINK: https://events.gnome.org/event/77/ (brainycmurf, 00:31:41) Meeting ended at 02:06:05 UTC. Action Items ------------ * Chris will ask around, systemd folks for a dbus api, and for a desktop developer for advice on other next steps. * Chris still plans to do a quickdoc on a subset of the issue * Michael to comment in the ticket Action Items, by person ----------------------- * **UNASSIGNED** * Chris will ask around, systemd folks for a dbus api, and for a desktop developer for advice on other next steps. * Chris still plans to do a quickdoc on a subset of the issue * Michael to comment in the ticket People Present (lines said) --------------------------- * brainycmurf (49) * zodbot (7) * Allan (0) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions

1 0

Workstation WG meeting, 19 July (secretary: Tomáš)
by Allan Day 19 Jul '22

19 Jul '22

Hi all, The next meeting of the Fedora Workstation Working Group is planned for Tuesday 19 July, at 9.30 EDT. Join links: - https://bluejeans.com/395383051/ - https://www.bluejeans.com/numbers See below for the agenda. Allan -- Agenda #topic Unfiltered Flathub #link https://pagure.io/fedora-workstation/issue/300 Status update: this has been deferred until F38. #topic F37 release schedule #link https://pagure.io/fedora-workstation/issue/312 Does the F37 schedule look OK? Assignees for F37 tasks (do we want to have a named workstation release person?) Does the schedule template look OK? #topic Improve the user feedback for OOM situations #link https://pagure.io/fedora-workstation/issue/202 This seems to have stalled. Anything we can do? #topic Stale pending-action tickets #topic Automatically install the OpenH264 codecs #link https://pagure.io/fedora-workstation/issue/84 #topic Broadcom wireless #link https://pagure.io/fedora-workstation/issue/116 #topic 2m shutdown timer is too long #link https://pagure.io/fedora-workstation/issue/163 #topic Announcements, Status Updates #info The minutes from last week have been posted. #link https://meetbot.fedoraproject.org/fedora-meeting-2/2022-07-12/workstation.2…

2 1

Fedora Workstation WG minutes, 2022-07-12
by Chris Murphy 12 Jul '22

12 Jul '22

============================================== #fedora-meeting-2: Workstation WG (2022-07-12) ============================================== Meeting started by brainycmurf at 19:51:43 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2022-07-12/workstation.2… . Meeting summary --------------- * Present members: Michael, Neal, Allan, Kalev, Tomas, Jens, Matthias, Chris (brainycmurf, 19:52:04) * Guests: Zac, Maira (brainycmurf, 19:52:04) * Regrets: (brainycmurf, 19:52:04) * Missing: (brainycmurf, 19:52:04) * Secretary: Jens (brainycmurf, 19:52:04) * Drop Flathub filtering (brainycmurf, 19:52:05) * LINK: https://pagure.io/fedora-workstation/issue/300 (brainycmurf, 19:52:07) * Improve GTK4 font rendering by default for 1080p displays (brainycmurf, 19:52:22) * LINK: https://pagure.io/fedora-workstation/issue/295 (brainycmurf, 19:52:24) * LINK: https://gitlab.gnome.org/GNOME/gtk/-/issues/3787 (brainycmurf, 19:52:26) * ACTION: Michael to update the ticket with comparison screenshots using latest GTK (brainycmurf, 19:52:49) * Review stale pending-action tickets (brainycmurf, 19:52:51) * Remove photos from the default apps (brainycmurf, 19:52:53) * LINK: https://pagure.io/fedora-workstation/issue/164 (brainycmurf, 19:52:55) * Add VS Code to the 3rd party repos (brainycmurf, 19:53:01) * LINK: https://pagure.io/fedora-workstation/issue/283 (brainycmurf, 19:53:03) * Graphical recovery environment (brainycmurf, 19:53:09) * LINK: https://pagure.io/fedora-workstation/issue/288 (brainycmurf, 19:53:11) * ACTION: Chris to take over research to come up with use cases, technical design options. (brainycmurf, 19:53:32) * Enable full-preemption (brainycmurf, 19:53:34) * LINK: https://pagure.io/fedora-workstation/issue/228 (brainycmurf, 19:53:36) * ACTION: Chris to dig into it and see about how we can do testing. (brainycmurf, 19:53:45) * LINK: https://pagure.io/fedora-workstation/issue/261 (brainycmurf, 19:53:53) * LINK: https://src.fedoraproject.org/rpms/gnome-console (brainycmurf, 19:54:01) * ACTION: Michael to talk to the maintainer about the lack of stable release (brainycmurf, 19:54:03) * ACTION: Allan to continue pushing to get the features we want (brainycmurf, 19:54:05) * Automatically install the OpenH264 codecs (brainycmurf, 19:54:07) * LINK: https://pagure.io/fedora-workstation/issue/84 (brainycmurf, 19:54:09) * Broadcom wireless (brainycmurf, 19:54:13) * LINK: https://pagure.io/fedora-workstation/issue/116 (brainycmurf, 19:54:15) * 2m shutdown timer is too long (brainycmurf, 19:54:21) * LINK: https://pagure.io/fedora-workstation/issue/163 (brainycmurf, 19:54:23) * Announcements, Status Updates (brainycmurf, 19:54:27) * The minutes from last week have been posted. (brainycmurf, 19:54:29) * LINK: https://meetbot.fedoraproject.org/fedora-meeting-2/2022-07-05/workstation.2… (brainycmurf, 19:54:31) * LINK: https://pagure.io/fedora-hatch-2022-rochester (brainycmurf, 19:54:36) Meeting ended at 19:54:42 UTC. Action Items ------------ * Michael to update the ticket with comparison screenshots using latest GTK * Chris to take over research to come up with use cases, technical design options. * Chris to dig into it and see about how we can do testing. * Michael to talk to the maintainer about the lack of stable release * Allan to continue pushing to get the features we want Action Items, by person ----------------------- * Allan * Allan to continue pushing to get the features we want * **UNASSIGNED** * Michael to update the ticket with comparison screenshots using latest GTK * Chris to take over research to come up with use cases, technical design options. * Chris to dig into it and see about how we can do testing. * Michael to talk to the maintainer about the lack of stable release People Present (lines said) --------------------------- * brainycmurf (78) * zodbot (7) * Allan (0) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

desktop July 2022