Comments
gbcox
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.
Created bug: https://bugzilla.redhat.com/show_bug.cgi?id=1897717
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.
Closed as duplicate. Original report here: https://bugzilla.redhat.com/show_bug.cgi?id=1893474
GMAIL stops working with this update, additionally FVD speed dial - and that was what I noticed immediately. Backout restores functionality. Sad that this got pushed so quickly to stable.
Here is the rhbz: https://bugzilla.redhat.com/show_bug.cgi?id=1861171
It references the upstream, which is: https://bugs.kde.org/show_bug.cgi?id=400117
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
Works for me! Thanks for the quick response!
works for me
works for me
Works for me
Works for me
Works for me
Works for me
Works for me
Finding out issues like this is what the testing stage is for. I assume it's just a matter of upping the "allowed maximum Bodhi version" in fedpkg, though I can't say why this hard lock exists (without a corresponding package version conflict) > in the first place.
To an extent, but you're not suppose to push something without ANY testing - and fedpkg is an important dependency - and this issue is exposed quite easily. In fact, this issue was first reported 3 days ago - almost immediately after the change was pushed. If you don't want to respond to messages over the weekend, then you should push your changes on a Monday.
I'm receiving the same message and opened a bug here:
Could not execute update: This system has bodhi v5, which is unsupported.
https://bugzilla.redhat.com/show_bug.cgi?id=1796972
Major fail. You need to immediate rollback this update or get it to work with the current processes.
Yes, I believe that was installed 20 days ago and I left positive karma. The problem I mentioned above occurred with this update and I backed out. I did notice however that the following failed (as others mentioned above):
Skipping packages with conflicts: (add '--best --allowerasing' to command line to force their upgrade): plasma-systemsettings i686 5.17.3-1.fc31 updates-testing 359 k plasma-systemsettings x86_64 5.17.3-1.fc31 updates-testing 349 k Skipping packages with broken dependencies: plasma-desktop x86_64 5.17.3-1.fc31 updates-testing 5.3 M
I didn't force their upgrade by --best --allowerasing. I thought it best to wait until the issue was corrected.
When trying to login to plasma from sddm userid and password not accepted. Am able to login fine to GNOME. By process of elimination found that kscreenlocker was causing the issue. Had to downgrade kscreenlocker to be able to login.
@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.