kde May 2023

kde@lists.fedoraproject.org

8 participants
11 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

Discover is no longer in the tray in F38
by Jonathan Ryshpan 06 Jun '23

06 Jun '23

And I don't see any way to put it there. Is this new (lack of) functionality or am I missing something. System info (fully updated): Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.15-300.fc38.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600 Manufacturer: ASUS -- Sincerely Jonathan Ryshpan <jonrysh(a)pacbell.net> This sentence have three erors.

2 2

[Fedocal] Reminder meeting : KDE SIG
by ngompa＠fedoraproject.org 28 May '23

28 May '23

Dear all, You are kindly invited to the meeting: KDE SIG on 2023-05-29 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

change login & lock screen background
by Sbob 27 May '23

27 May '23

All; I am running Fedora 38 KDE spin, how can I change the login & lock screen background image? Thanks

2 1

Strange Message
by Robert McBroom 25 May '23

25 May '23

The network widget icon changed to a world. Instead of giving me the connections the message comes up. Fully updated f38 with Plasma X11. ---------- Sorry! There Was an Error Loading Networks <Unknown File>:95:5: Element is not creatable. ------------ nm-connection-editor shows the expected connections and networking is available. It is annoying to have to go to nmcli to access the wifi connections. What happened to the widget?

1 0

Dolphin not recovering its previous session settings
by José Abílio Matos 24 May '23

24 May '23

Hi, I am using F38 and the latest updates, and updates-testing. I am also using X11 because of the session handling. Since Thursday last week that dolphin is not able to start from the previous session. This does not seem to be a session problem but a dolphin problem because asking for dolphin to start from a specific session config file does not work. As an example if I go to ~/,config/session and pick a file from there, for example: dolphin_10cddbd766000168375387600000030090040_1684490045_935605 trying to start dolphin with the session option shows a single tab with the home dir (the default). Previously running dolphin -session 10cddbd766000168375387600000030090040_1684490045_935605 would restore the session instance of dolphin. Did anyone else noticed this issue? Best regards, -- José Abílio Matos

2 2

[Fedocal] Reminder meeting : KDE SIG
by ngompa＠fedoraproject.org 21 May '23

21 May '23

Dear all, You are kindly invited to the meeting: KDE SIG on 2023-05-22 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

[Fedocal] Reminder meeting : KDE SIG
by ngompa＠fedoraproject.org 14 May '23

14 May '23

Dear all, You are kindly invited to the meeting: KDE SIG on 2023-05-15 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

Mount filesystem
by Mark ＠ GMail 10 May '23

10 May '23

What's the best way to mount remote filesystems? I'm using nfs but it seems really slow and when I mentioned it (here? somewhere else?) there was a quite negative response about nfs itself. It's possible I'm just seeing the difference between my local (solid state) disk on a fast machine and the remote (spinny disk) filesystem on a slower remote machine (they're only about six inches apart on a 1Gb network connection, so it's not *very* remote). However, with "remote" website directories mounted locally they're much slower with my local webserver than with the one on that slower machine, so I'm inclined to suspect nfs... is that unfair? (I know this isn't a particularly KDE related issue. Please don't make me rejoin the Fedora list, they're really mean!) Both machines are running F37, both updated every week.

3 2

[Fedocal] Reminder meeting : KDE SIG
by ngompa＠fedoraproject.org 07 May '23

07 May '23

Dear all, You are kindly invited to the meeting: KDE SIG on 2023-05-08 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 May 2023