Comments
mattf
Problems with kf5-kwayland-5.111.0-2.fc39 and kf5-akonadi-server-23.08.2-2.fc39 and the Qt 5.15.11 update were shown that prevent them from being updated https://bugzilla.redhat.com/show_bug.cgi?id=2244760 F39 has kf5 5.110.0 and KDE Gear 23.08.1, but kf5-kwayland-5.111.0-2.fc39, kf5-frameworkintegration-5.111.0-2.fc39 and kf5-akonadi-server-23.08.2-2.fc39 were in the update. This problem might be fixed by rebuilding kf5-kwayland-5.110.0, kf5-frameworkintegration-5.110.0 and kf5-akonadi-server-23.08.1 and adding them to the update. Otherwise, building the rest of KF5 5.111.0 in F39 and adding it to the update might fix this. Problems with qadwaitadecorations-0.1.2-5.fc39 and the Qt 5.15.11 and Qt 6.6.0 updates were also shown https://bugzilla.redhat.com/show_bug.cgi?id=2244757
I don't see the crashes when starting System Monitor https://bugzilla.redhat.com/show_bug.cgi?id=2244246 and marble https://bugzilla.redhat.com/show_bug.cgi?id=2244320 in GNOME after I updated to qadwaitadecorations-0.1.2-5.fc39.
This is one of at least five F39 updates from around the time of the beta freeze on 2023-8-22 marked testing in bodhi which weren't pushed to updates-testing as I reported at https://pagure.io/releng/issue/11641 This update might need to be submitted to testing manually.
This is one of at least five F39 updates from around the time of the beta freeze on 2023-8-22 marked testing in bodhi which weren't pushed to updates-testing as I reported at https://pagure.io/releng/issue/11641 This update might need to be submitted to testing manually.
This is one of at least five F39 updates from around the time of the beta freeze on 2023-8-22 marked testing in bodhi which weren't pushed to updates-testing as I reported at https://pagure.io/releng/issue/11641 This update might need to be submitted to testing manually.
This is one of at least five F39 updates from around the time of the beta freeze on 2023-8-22 marked testing in bodhi which weren't pushed to updates-testing as I reported at https://pagure.io/releng/issue/11641 This update might need to be submitted to testing manually.
This is one of at least five F39 updates from around the time of the beta freeze on 2023-8-22 marked testing in bodhi which weren't pushed to updates-testing as I reported at https://pagure.io/releng/issue/11641 This update might need to be submitted to testing manually.
This is one of at least five F39 updates from around the time of the beta freeze on 2023-8-22 marked testing in bodhi which weren't pushed to updates-testing as I reported at https://pagure.io/releng/issue/11641 This update might need to be submitted to testing manually.
When I've logged into Plasma 5.27.6 on Wayland from sddm after booting 6.3.10, the Plasma splash screen appeared for around a second and then the screen went black indefinitely. This problem happened each time with 6.3.10, but it didn't happen with 6.3.9 or earlier. amdgpu errors and warnings were shown in the journal as I reported at https://bugzilla.redhat.com/show_bug.cgi?id=2218414 I bisected the problem to 1ca399f127e0a372537625b1d462ed586f5d9139 "drm/amd/display: Add wrapper to call planes and stream update"
After an update containing aide-0.18.4-2.fc38.x86_64, aide --check was denied execmem 2/2 times when started as a cron job. I reported the denial in more detail at https://bugzilla.redhat.com/show_bug.cgi?id=2217165
I ran sudo dnf offline-upgrade download with updates-testing enabled in a Fedora 38 KDE Plasma installation. Qt 5.15.9 is installed from the update FEDORA-2023-e78d433635 in updates-testing. dnf had a problem because kf5-frameworkintegration-5.105.0-2.fc38.x86_64 requires qt5-qtbase(x86-64) = 5.15.8, but none of the providers can be installed. I reported this problem at https://bugzilla.redhat.com/show_bug.cgi?id=2187131 dnf couldn't update to kf5-frameworkintegration-5.105.0-2.fc38 due to that problem. kf5-frameworkintegration-5.105.0-2.fc38 might need to be rebuilt with Qt 5.15.9
ksysguardd didn't crash after I updated to ksysguardd-5.22.0-9.fc38. Thanks.
I ran sudo dnf offline-upgrade download with updates-testing enabled in a Fedora 38 KDE Plasma installation. dnf showed a problem because kf5-kcalendarutils-22.12.3-1.fc38.x86_64 requires grantlee-qt5(5.2), but grantlee-qt5-5.3.1-1.fc38 provides grantlee-qt5(5.3) = 5.3.1-1.fc38. I reported this problem at https://bugzilla.redhat.com/show_bug.cgi?id=2180667
Fedora-KDE-Live-x86_64-38_Beta-1.3.iso with 6.2.2-301 booted normally with the default kernel command line parameters on the system which had the black screen problem at https://bugzilla.redhat.com/show_bug.cgi?id=2156691 Thanks.
Switching VTs from sddm on Wayland with kwin_wayland compositor with ctrl+alt+f2 etc. doesn't seem to work any longer after updating to plasma-workspace-5.27.0-4.fc37. Is that intentional or not?
I searched for systemd-userdbd in the systemd-stable repository and found a commit units: allow systemd-userdbd to change process name which makes the following change adding the CAP_SYS_RESOURCE capability to the systemd-userdbd.service file https://github.com/systemd/systemd-stable/commit/9357d2342981a8b4fcfa2d170b7749c27d364fdd
- CapabilityBoundingSet=CAP_DAC_READ_SEARCH
- CapabilityBoundingSet=CAP_DAC_READ_SEARCH CAP_SYS_RESOURCE
That change might be where these denials are coming from.
On the next 2 boots after an update including systemd-251.11-1.fc37.x86_64, processes like sd-worker and systemd-userwork were denied using the sys_resource capability when systemd-userdbd.service was started. I also saw SELinux denial notifications at various times while using Plasma. The same sorts of sys_resource denials were shown in the journal at those times. I reported these denials in more detail at https://bugzilla.redhat.com/show_bug.cgi?id=2166509
dnf problems occurred when updating to webkitgtk-2.38.3-1.fc37 from koji involving nothing provides javascriptcoregtk6.0(x86-64) = 2.38.3-1.fc37 needed by webkit2gtk5.0-2.38.3-1.fc37.x86_64 I reported the problem at https://bugzilla.redhat.com/show_bug.cgi?id=2155975
xdg-desktop-portal-kde crashed when run by sddm on Wayland with kwin_wayland compositor during each boot with sddm-0.19.0^git20221025.fc24321-1.fc37 with the same trace and errors in the journal as I reported at https://bugzilla.redhat.com/show_bug.cgi?id=2129479. The commit "disable automatic portal launching" at https://github.com/sddm/sddm/commit/fc24321541f6f65b7d1aac89cd82336ffd53e1a0 looks like it's intended to fix this problem, but it might not be sufficient to do so. sddm ran normally otherwise. Logging out of Plasma 5.26.2 on Wayland showed sddm on Wayland at least some of the time instead of the text login on VT2 as in https://bugzilla.redhat.com/show_bug.cgi?id=2073725 Since sddm-0.19.0^git20221025.fc24321-1.fc36 was pushed to stable FEDORA-2022-24b141d508 I think it's better if this one is too at least to avoid downgrades even though xdg-desktop-portal-kde still crashes when run by sddm for me.
The 6.5.8 kernel booted to a dracut emergency shell because all but the first of its kernel command line parameters were removed https://bugzilla.redhat.com/show_bug.cgi?id=2245372