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
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
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
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.
IRC: adamw | Twitter: adamw_ha
Since my last system update my screen locker doesn't lock me out while asking for my password. I've hd the idle timeout set for 12 minutes and the powere off timeout set to 13 minutes since I first installed Fedora on this machine.
It looks like the screen power off does happen, but I am never asked for a password and the screen comes back on as soon as I touch the keyboard or move the mouse.
It did some searching and found a couple of mentioned abut chrome holding off the screen locker for certain web pages. I tested that by closing all chrome sessions before leaving my desk af a hour or so, and still, when I came back the screen was dark, but pressing any key or moving the mouse brought it back up without asking for my password.
Any suggestons where to look to find the problem?
This has been happening for IIRC) several months now at least:
$ journalctl --boot=-1 --reverse
May 01 10:44:26 Bree systemd: plasma-kded.service: Consumed 18.380s CPU time.
May 01 10:44:26 Bree systemd: Stopped KDE Daemon.
May 01 10:44:26 Bree systemd: plasma-kded.service: Failed with result 'timeout'.
May 01 10:44:26 Bree systemd: plasma-kded.service: Main process exited, code=killed, status=9/KILL
May 01 10:44:26 Bree systemd: plasma-kded.service: Killing process 1791 (ProfilesWatcher) with signal SIGKILL.
May 01 10:44:26 Bree systemd: plasma-kded.service: Killing process 1722 (kded5) with signal SIGKILL.
May 01 10:44:26 Bree systemd: plasma-kded.service: State 'stop-sigterm' timed out. Killing. <-----------------------*
May 01 10:43:03 Bree systemd: Unmounted /run/user/0.
May 01 10:43:03 Bree systemd: run-user-0.mount: Deactivated successfully.
May 01 10:43:03 Bree systemd: Unmounted /run/user/990.
May 01 10:43:03 Bree systemd: run-user-990.mount: Deactivated successfully.
May 01 10:43:03 Bree systemd: Stopped Network Manager Wait Online.
Any idea why? I see some apparently related BZ entries dating back a
couple of years, but nothing recently.
Not sure how long this has not been possible in dolphin. I first noticed it a few days ago and assumed it was a configuratinn issue.
Today I attemted to fix it and found no way to do it. The context menu choices do not include paste actions. For now I am using Duplicate here as a work around.
I am a recently updated Fedora 36 workstation.
Any ideas on how to proceed?
How can the sound generated when evolution reports the arrival to mail
to KDE be suppressed?
* System Settings->Notifications : Shows no obvious way to suppress all
sounds. I don't need sound from any application and am happy to
suppress them all to get rid of the sounds from evolution.
* System Settings->Notifications->Applications Configure->Evolution :
Produces the message "This application does not support notifications
on a per event basis" — I don't want to control notifications on a
per event basis; I want to suppress sound for all events reported by
Many Thanks - Jonathan Ryshpan <jonrysh(a)pacbell.net> If God lived on
earth, people would break all his windows.
I've found a rather peculiar problem recently introduced in Rawhide.
Running KDE Live Image under virt-manager, when OpenGL and 3D acceleration are enabled, the cursors are showed upside down and out of position (it is hard to click on the selected point).
To reproduce the problem:
- download a Rawhide KDE Live Image (I used Fedora-KDE-Live-x86_64-Rawhide-20220702.n.0.iso)
- set up a new machine under virt-manager
- at the first run, the live image will be run with OpenGL and 3D acceleration disabled, so you should not notice the problem
- shutdown the machine and change the following settings: Spice Screen -> Listen type: None + OpenGL flag enabled; Virtio Video -> 3D Acceleration flag enabled
- run the machine with the new settings and see the upside down cursors
It may be possible it is related to specific hardware configurations. In my case the OpenGL under Spice is using AMD/ATI Cezanne render.
I'm unsure if this should be reported as virt-manager problem, or under some KDE component... this isn't reproducible with Gnome Live image, so I'd guess it is Plasma Wayland related?
The major pain point, when using kde, for has been the session handling.
I use session restore, that means that the windows, with all the associated
properties, are remembered and restored on login.
The issue we had was the windows were remembered correctly but not its
placement and other properties. This has happened for some time, since Fedora
Now finally the issue was identified and a solution should come to plasma
It will be nice to have this fixed, finally. :-)