Comments

536 Comments

Problem: package python3-aiohttp-3.7.4-3.fc35.x86_64 requires (python3.10dist(async-timeout) < 4 with python3.10dist(async-timeout) >= 3), but none of the providers can be installed - cannot install both python3-async-timeout-4.0.1-1.fc35.noarch and python3-async-timeout-3.0.1-14.fc35.noarch - cannot install the best update candidate for package python3-async-timeout-3.0.1-14.fc35.noarch - cannot install the best update candidate for package python3-aiohttp-3.7.4-3.fc35.x86_64

BZ#1768164 python-async-timeout-4.0.1 is available
karma

Much better! Thanks for the quick response in getting this fixed.

BZ#2016788 sddm-0.19.0-17.fc35 didn't allow logging in to the Plasma on Wayland desktop session
karma

This needs to be immediately rolled back. See #2016788. We can't have users upgrading to F35 and not having Plasma Wayland available.

karma

Problem reported a month ago still exists: https://bugzilla.redhat.com/show_bug.cgi?id=1981039

@mattf Thanks for the update. I tested with amdgpu.dc=0 and it circumvents the issue. I closed 1984686 as a duplicate of your ticket: 1981039. @jforbes, thanks for the update!

Opened bug for black screen issue reported above: 1984686 Also, this bug is occurring regardless of whether you are using SDDM or GDM, or Wayland GNOME or Wayland Plasma.

Noticed from a comment above that this had a AMD fix... it appears that this fix may have broken other things with AMD. I'm using: CPU: AMD A10-8700P Radeon R6 4C+6G (4) @ 1.800GHz GPU: AMD ATI Radeon R5/R6/R7 Graphics

Breaks KDE Wayland. After SDDM all you get is a black screen with intermittent white flashes. KDE X11 appears to work properly however.

works for me

karma

works for me

karma

works for me

karma

works for me

works for me

karma

works for me

karma

works for me

works for me

works for me

works for me

works for me

works for me