kde November 2022

kde@lists.fedoraproject.org

12 participants
16 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

1 2

Konsole Profile not saving
by Sbob 29 Nov '22

29 Nov '22

Hi all; I can create a new profile in Konsole: Settings -> Manage Profiles -> New and the new profile shows up for : Settings -> Switch Profile But it only shows for the current Konsole window, If I open another Konsole window then the new profile is not there Thanks in advance for any advice

2 1

[Fedocal] Reminder meeting : KDE SIG
by ngompa＠fedoraproject.org 27 Nov '22

27 Nov '22

Dear all, You are kindly invited to the meeting: KDE SIG on 2022-11-28 from 13:00:00 to 14:00:00 US/Eastern At https://meet.kde.org/b/ale-swq-39j The meeting will be about: Regular meeting for the KDE SIG Current Topics: https://pagure.io/fedora-kde/SIG/issues?status=Open&tags=meeting More information available at: [https://fedoraproject.org/wiki/SIGs/KDE](https://fedoraproject.org/wiki/SIG… Source: https://calendar.fedoraproject.org//meeting/9876/

1 0

adding a kernel parameter permanently?
by Sbob 22 Nov '22

22 Nov '22

All; I want to add a permanent kernel setting: intremap=nosid What is the easiest way to do this? Fedora 36 - KDE Thanks in advance

4 3

[Fedocal] Reminder meeting : KDE SIG
by ngompa＠fedoraproject.org 20 Nov '22

20 Nov '22

Dear all, You are kindly invited to the meeting: KDE SIG on 2022-11-21 from 13:00:00 to 14:00:00 US/Eastern At https://meet.kde.org/b/ale-swq-39j The meeting will be about: Regular meeting for the KDE SIG Current Topics: https://pagure.io/fedora-kde/SIG/issues?status=Open&tags=meeting More information available at: [https://fedoraproject.org/wiki/SIGs/KDE](https://fedoraproject.org/wiki/SIG… Source: https://calendar.fedoraproject.org//meeting/9876/

1 0

KDE Connect: Can't Transfer Files With Dolphin
by Bryce Hardy 17 Nov '22

17 Nov '22

2 2

KDE on a touchscreen - how to activate virtual keyboard
by Sbob 15 Nov '22

15 Nov '22

I have a new touchscreen laptop, installed Fedora 36 - KDE spin on it. Can I set it up so when I open Konsole, or firefox that the virtual keyboard will pop up? Thanks in advance

1 0

Fedora 36 - KDE Spin on a microsoft surface pro 8
by Sbob 15 Nov '22

15 Nov '22

All; I just picked up a surface prom 8, tried an install of F36 / Gnome but the touch screen does not work. Anyone know if KDE has better support? anthing else I need to install? Thanks in advance

1 1

Increase fonts / size of login screen
by Sbob 15 Nov '22

15 Nov '22

All; I'm running Fedora 36 KDE spin, how do I increase the font size / display size of the login screen? Thanks in advance

1 0

[Fedocal] Reminder meeting : KDE SIG
by ngompa＠fedoraproject.org 13 Nov '22

13 Nov '22

Dear all, You are kindly invited to the meeting: KDE SIG on 2022-11-14 from 13:00:00 to 14:00:00 US/Eastern At https://meet.kde.org/b/ale-swq-39j The meeting will be about: Regular meeting for the KDE SIG Current Topics: https://pagure.io/fedora-kde/SIG/issues?status=Open&tags=meeting More information available at: [https://fedoraproject.org/wiki/SIGs/KDE](https://fedoraproject.org/wiki/SIG… Source: https://calendar.fedoraproject.org//meeting/9876/

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

kde November 2022