Got this error when updating, but everything seems to be working fine
Problem 1: cannot install the best update candidate for package plasma-oxygen-5.26.2-1.fc37.x86_64
- nothing provides oxygen-sound-theme = 5.26.3-1.fc37 needed by plasma-oxygen-5.26.3-1.fc37.x86_64
Problem 2: problem with installed package plasma-oxygen-5.26.2-1.fc37.x86_64
- package plasma-oxygen-5.26.2-1.fc37.x86_64 requires oxygen-cursor-themes = 5.26.2-1.fc37, but none of the providers can be installed
- cannot install both oxygen-cursor-themes-5.26.3-1.fc37.noarch and oxygen-cursor-themes-5.26.2-1.fc37.noarch
- cannot install the best update candidate for package oxygen-cursor-themes-5.26.2-1.fc37.noarch
- nothing provides oxygen-sound-theme = 5.26.3-1.fc37 needed by plasma-oxygen-5.26.3-1.fc37.x86_64
This update's test gating status has been changed to 'failed'.
Here at my VM (kvm/virt-manager) it worked fine, no freezes or problems at lock screen.
That's what journalctl logs when locking and unlocking:
nov 14 10:10:03 Fedora37-17 systemsettings[2967]: QLayout::removeWidget: Cannot remove a null widget.
nov 14 10:10:06 Fedora37-17 systemsettings[2967]: QQmlEngine::setContextForObject(): Object already has a QQmlContext
nov 14 10:10:06 Fedora37-17 systemsettings[2967]: file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:203:9: QML MouseArea: Binding loop detected for property "implicitHeight"
nov 14 10:10:06 Fedora37-17 systemsettings[2967]: file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:203:9: QML MouseArea: Binding loop detected for property "implicitHeight"
nov 14 10:10:10 Fedora37-17 kwin_wayland[1070]: This plugin does not support raise()
nov 14 10:10:11 Fedora37-17 systemd[1006]: app-systemsettings-8b0cd60bf855429aad30d906fca15ebc.scope: Consumed 11.445s CPU time.
nov 14 10:12:14 Fedora37-17 kwin_wayland_wrapper[3092]: libEGL warning: egl: failed to create dri2 screen
nov 14 10:12:14 Fedora37-17 kscreenlocker_greet[3092]: kscreenlocker_greet: Lockscreen QML outdated, falling back to default
nov 14 10:12:14 Fedora37-17 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
nov 14 10:12:14 Fedora37-17 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
nov 14 10:12:14 Fedora37-17 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
nov 14 10:12:14 Fedora37-17 kscreenlocker_greet[3092]: kf.kirigami: Failed to find a Kirigami platform plugin
nov 14 10:12:14 Fedora37-17 kscreenlocker_greet[3092]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
nov 14 10:12:15 Fedora37-17 kscreenlocker_greet[3092]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
nov 14 10:12:15 Fedora37-17 kscreenlocker_greet[3092]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
nov 14 10:12:48 Fedora37-17 audit: BPF prog-id=80 op=LOAD
nov 14 10:12:48 Fedora37-17 systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
nov 14 10:12:49 Fedora37-17 systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
nov 14 10:12:49 Fedora37-17 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
nov 14 10:12:59 Fedora37-17 audit[3151]: USER_AUTH pid=3151 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:chkpwd_t:s0-s0:c0.c1023 msg='op=PAM:unix_chkpwd acct="tester" exe="/usr/sbin/unix_chkpwd" hostname=? addr=? terminal=? res=success'
nov 14 10:13:18 Fedora37-17 systemd[1]: fprintd.service: Deactivated successfully.
nov 14 10:13:18 Fedora37-17 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
nov 14 10:13:18 Fedora37-17 audit: BPF prog-id=0 op=UNLOAD
@marcdeop I've already been running that mesa update. As per matrix chat, removing qt5-qtwebengine-freeworld-5.15.10-2.fc37.x86_64 unblocked this update and fixed the lockscreen
Ignorer les paquets en conflit :
(ajouter « --best --allowerasing » à la ligne de commande pour forcer leur mise à niveau):
oxygen-cursor-themes noarch 5.26.3-1.fc37 updates-testing 1.0 M
Ignorer les paquets ayant des dépendances cassées :
plasma-oxygen x86_64 5.26.3-1.fc37 updates-testing 1.4 M
This update's test gating status has been changed to 'waiting'.
Problem: package kf5-kimageformats-5.100.0-1.fc37.x86_64 requires libavif.so.14()(64bit), but none of the providers can be installed
- cannot install both libavif-0.10.1-3.fc37.x86_64 and libavif-0.11.1-1.fc37.x86_64
- cannot install the best update candidate for package kf5-kimageformats-5.99.0-4.fc37.x86_64
- problem with installed package libavif-0.11.1-1.fc37.x86_64
===========================================================================
This update's test gating status has been changed to 'waiting'.
This update has been submitted for testing by bodhi.
Got this error when updating, but everything seems to be working fine
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'passed'.
Lock screen is broken after this update, getting "The screen locker is broken and unlocking is not possible anymore..."
This update has been pushed to testing.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
SDDM doesn't show up. Screen locker also broken as well (when invoke screen lock it points me to tty (loginctl unlock-session X) command
I was able to also see
(dnf install plasma-oxygen)
Works for me, not seeing any issues with SDDM.
Can confirm that plasma-oxygen has dependency issues as reported above. Not affecting me because I use Breeze.
Lock screen is broken for me too.
No issues noted.
Here at my VM (kvm/virt-manager) it worked fine, no freezes or problems at lock screen. That's what journalctl logs when locking and unlocking:
jgrulich edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by jgrulich.
Lock screen is still broken for me even with a new update
KF5-100 update fixed crashes for me.
@agurenko could you please try in combination with: https://bodhi.fedoraproject.org/updates/FEDORA-2022-f1d65a5247?
@marcdeop I've already been running that mesa update. As per matrix chat, removing qt5-qtwebengine-freeworld-5.15.10-2.fc37.x86_64 unblocked this update and fixed the lockscreen
All fıxed for me as well. LGTM
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
Ignorer les paquets en conflit : (ajouter « --best --allowerasing » à la ligne de commande pour forcer leur mise à niveau): oxygen-cursor-themes noarch 5.26.3-1.fc37 updates-testing 1.0 M Ignorer les paquets ayant des dépendances cassées : plasma-oxygen x86_64 5.26.3-1.fc37 updates-testing 1.4 M
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
All good after removing
qt5-qtwebengine-freeworld.This update has been submitted for stable by jgrulich.
This update has been submitted for stable by jgrulich.
This update has been submitted for stable by jgrulich.
This update has been submitted for stable by jgrulich.
This update has been submitted for stable by jgrulich.
Working fine
adamwill edited this update.
This update has been pushed to stable.
Solves https://bugzilla.redhat.com/show_bug.cgi?id=2141237 . Thanks.
Problem: package kf5-kimageformats-5.100.0-1.fc37.x86_64 requires libavif.so.14()(64bit), but none of the providers can be installed - cannot install both libavif-0.10.1-3.fc37.x86_64 and libavif-0.11.1-1.fc37.x86_64 - cannot install the best update candidate for package kf5-kimageformats-5.99.0-4.fc37.x86_64 - problem with installed package libavif-0.11.1-1.fc37.x86_64 ===========================================================================