@treba, thanks for the explanation. would be nice in the future (especially for things as critical as Fx and for such a noticeable defect) there would be a warning or notification posted on the change so when people are testing they would be aware. I understand that everyone can't be warned of everything, but if we're aware, it would be nice to make an attempt so people don't spin their wheels for nothing.
There is an unbelievable atrocious slowness when trying to use Fx Wayland on KDE - which is additionally very concerning since F34 is slated to have Plasma Wayland as the default. Previous version worked fine. Workaround is to use X11 version, which appears to run fine. I see from the comments in the spec file that the wayland backend was disabled... which would imply to me that folks that are on kde wayland that were using fx-wayland wouldn't be affected... that whatever would be done in the background - but that doesn't appear to be the case.
Thanks for your work on getting this applied so quickly. Much appreciated! Circumvents the current issue, but concerned it does not appear to be a long term solution. I updated BZ#1912046. When this issue surfaces, it is extremely disruptive.
Guys, this update needs to be pulled immediately - it simply isn't acceptable to delay and have a discussion about it. It's wreaking havoc. It is completely unacceptable to have something causing such disruption still in updates-testing going on 48 hours now.
opened addon bug here: https://bugzilla.redhat.com/show_bug.cgi?id=1899331
@ngompa, @jgrulich, @rdieter, @michaeltunnell - Found the issue... it's when using 5.20 in combination with sddm ...
sddm-0.18.1-8.fc33.x86_64, sddm-themes-0.18.1-8.fc33.noarch, sddm-kcm-5.20.3-1.fc33.x86_64, sddm-breeze-5.20.3-1.fc33.noarch
Would be interesting to know if if the people who reported wayland working were using GDM or SDDM.
If I change to gdm, wayland appears to work (so far) just fine. My understanding however is that sddm is the default displaymanager for kde, so this is a bit of an issue.
Leaving: https://bugzilla.redhat.com/show_bug.cgi?id=1897717 assigned as a plasma issue, because don't who has the bug... feel free to reassign as appropriate - but obviously some coordination is needed.
@michaeltunnell so plasma-wayland is working fine for you?
I have the update on two machines and I am getting a black screen with wayland:
OS: Fedora 33 (Workstation Edition) x86_64 Kernel: 5.9.8-200.fc33.x86_64 Uptime: 16 hours, 10 mins Packages: 4217 (rpm), 9 (flatpak) Shell: bash 5.0.17 Resolution: 1920x1080 DE: Plasma WM: KWin Theme: Breeze [Plasma], Adwaita [GTK2/3] Icons: breeze [Plasma], breeze [GTK2/3] Terminal: konsole CPU: AMD FX-8350 (8) @ 2.490GHz GPU: AMD ATI Radeon HD 7850 / R7 265 / R9 270 1024SP Memory: 5963MiB / 32006MiB
OS: Fedora 33 (Workstation Edition) x86_64 Host: 80K4 Lenovo ideapad 500-15ACZ Kernel: 5.9.8-200.fc33.x86_64 Uptime: 16 hours, 3 mins Packages: 2580 (rpm) Shell: bash 5.0.17 Resolution: 1920x1080 DE: Plasma 5.20.3 WM: kwin Theme: Breeze [Plasma], Adwaita [GTK2/3] Icons: [Plasma], breeze [GTK2/3] Terminal: konsole CPU: AMD A10-8700P Radeon R6 4C+6G (4) @ 1.800GHz GPU: AMD ATI Radeon R5/R6/R7 Graphics Memory: 1509MiB / 7477MiB
@ngompa Thanks! It appears to be limited to AMD/Radeon so hopefully it will be easy to fix. As I mentioned above X appears to work fine, but wayland not so much. Previous release (5.19.5) had cosmetic/functional issues - but was workable. This isn't.
Just finished install on Lenovo Laptop with AMD Processor and Radeon. Same thing... Black screen when trying to use Wayland. Those who are mentioning "works great" can you please advise what kind of CPU and Graphics card you are using. That may help debug this issue. Otherwise, we aren't going to be able to make much progress on getting this to be the default, if it can't clear AMD/Radeon.
When trying to use Plasma Wayland, desktop is a completely black background. I have to reboot and luckily so far everything appears to be fine with X. Since I believe the whole idea of this is to get Plasma ready to be a default, this is a big fail.
Yeah, it's a known problem and still happening to some people with 1.60 - I'm going to open a rhbz on it and reference the upstream bug. 1.7 has it's faults, but it's nice to see the app come back with some greatly needed enhancements. Here is an article that discusses it: https://www.omgubuntu.co.uk/2020/02/qt-twitter-client-choqok-first-update-forever