On Thu, 2021-04-22 at 15:14 +0800, Ed Greshko wrote:
On 20/04/2021 01:23, home user wrote:
While trying to diagnose problems as a part of another thread in this list, I discovered that wayland is not functional on my workstation. I'm currently logged in to gnome using the top "GNOME" entry in the menu of desktops that is displayed in the upper right corner of the monitor during login. Results of tests suggested in that other thread:
bash.12[~]: env | grep -i wayland bash.13[~]: ps -ef | grep -i wayland weilian+ 128352 2160 0 11:15 pts/0 00:00:00 grep -- color=auto -i wayland bash.14[~]: ps -ef | grep -i earlyoom weilian+ 128358 2160 0 11:15 pts/0 00:00:00 grep -- color=auto -i earlyoom bash.15[~]:
Also, I tried logging in to plasma with wayland. After entering my credentials, the screens went black. After 2 minutes, I hit the hard reset and rebooted.
Through 8 years of weekly patches and semi-annual upgrades, I've never done anything to block or disable wayland. Shouldn't it have been automatically installed somewhere in those 8 years?
How do I get wayland properly working on my workstation?
You have nVidia HW and are using the nVidia drivers packaged by rpmfusion.
To give any opinion about you chances to get wayland working one would need to know your HW and what version of the driver you're running. If your HW is 8 years old, then my guess would be your chances of getting wayland running are slim.
I don't currently use Wayland as I'm on KDE, but I have briefly tested it in F33 under Gnome. My hardware is of a similar age, i.e. the mobo is at least 8 years old and the GPU is a GTX-1050 from 2017, using the RPMfusion driver. It all worked fine. I sincerely hope it will continue to work under F34 when Wayland is supposed to be supported for KDE.
F33 was a clean install of Fedora Workstation, so I presume that's where Wayland came from. If the OP installed the KDE spin it may not have been installed by default.
poc