Fedora 31 wayland enable. No Wayland option available on Fedora 39 with Nvidia.

Fedora 31 wayland enable After restarting my PC running Fedora 39 I got to the login screen and noticed that no wayland sessions are available. Currently, Anaconda is still an X11 application, which we would like to fix and make Anaconda Wayland native application to allow us drop of the X11 dependencies from installation ISO images. After turning off SecureBoot, the drivers seems to have been loaded, but now I’m on X11: $ echo I’m going to follow the instructions at Howto/NVIDIA - RPM Fusion for installing the kmod-nvidia package, and getting it working for my GTX 1050 Ti Mobile (with Secure Boot enabled) on Fedora 36 (w/ Gnome on Wayland). I cannot enable the Firefox has been Wayland-native by default since Fedora 31 as well. Starting the GNOME Wayland session from the command line in Fedora is a straightforward process that allows users to experience the benefits and features of Wayland. I read about Wayland (and Weston as the reference implementation), so I thought Before installing Fedora, I was under the impression that GNOME’s fractional scaling approach on Xwayland was blurry. I installed a new terminal and was running all these commands from that instead of the default gnome-terminal (I had totally uninstalled gnome-terminal). You can view all running applications using X11/XWayland with the tool xlsclients. conf for editing (as you know, you must be Starting the GNOME Wayland session from the command line in Fedora is a straightforward process that allows users to experience the benefits and features of Wayland. The problematic line on the server side was in /etc/ssh/sshd_config defautls to X11UseLocalhost yes changed this to X11UseLocalhost no. All I want is that Keepass fills the login data. I think I found the problem. It is possible to enable X11 under Fedora 25. I am running Fedora 32 Silverblue and I have tried the command: google-chrome-unstable --enable-features=UseOzonePlatform --ozone-platform=wayland. I do see it mention in the Info, but my display server shows X11. Thanks to the hard work of thousands of Fedora community members and contributors, we’re celebrating yet another on-time release. KDE Plasma starts quite a few processes, among them are XWayland and XWaylandVideoBridge. start Wayland session with startplasma-wayland command Hello all, i have just switched to Fedora after years of Debian I am interested about a solution about a command who can turn on keyboard led using wayland (fedora 39) ; as i can see, using X11 i can use command xset led 3 , but clearly does not work with Wayland i did see this post Leds Keyboard on Wayland where has been used below command If you are still using the 6. A default installation will include Xorg installed. 10. Using that, I can connect via NoMachine without problems. Martin Stransky and Jan Horak has been working tirelessly on trying to ensure Firefox works well on Wayland and in the Fedora 31 Beta it is running on Wayland by default. Everything worked smoothly with Wayland but because of lack of support that time, I have to move to Xorg Now it's been 2 years since then and now I want to switch to Wayland again, but the option to switch doesn't seems to be there Hi, I’ve updated my system to Fedora 35 and my Nvidia driver to 495. profile file, only a flatpak run --socket=wayland com. Another Is it possible to enable fractional scaling on fedora 31? I'm using a 15in lappy with 1080p display and everything looks so tiny that i feel I'll go blind. 6: 2270: October 18, 2021 NVIDIA drivers and Wayland Followed the howtos to enable xorg, but now I can’t get Not quite; that’s more with regard to Wayland. To log into a Wayland session manually : Restart Sddm through CTRL + ALT + F3 key combination. Fedora 40 removed X11 from KDE Plasma, and we only kept it around for our Nvidia images since their proprietary drivers still have issues with Wayland. Tried — systemctl disable kdm systemctl enable gdm GDMmanager fails to initialize. One package has to be layered with this command in a Hi I hav a laptop with fedora 39. sudo systemctl set-default graphical. Thanks so much for this post. I am now trying to make the necessary changes to enable it, but I don't seem to be able to. Log into any tty. target. I installed it, allowed access to port 3389, and started the service. Hi guys, Is this the proper way to get the flash plugin to work in Firefox on Fedora 30? Thanks. No Wayland option available on Fedora 39 with Nvidia. And nothing happened. The driver determines if the card is properly functioning. I have installed CUDA, with the related NVIDIA drivers, from here. GDM configuration storage [daemon] # Uncomment the line below to force the login screen to use Xorg WaylandEnable=true [security] [xdmcp] Hi, I want to login to Fedora 41 using my mouse only. It is said that Wayland will eventually replace X11 as the default display server on Linux and many distributions have begun implementation of Wayland. Hello, I am trying to enable Wayland on Microsoft Edge so I can get pinch to zoom to work. silverblue-team. I have all the latest firmware installed and all OS updates installed No Wayland option available on Fedora 39 with Nvidia. mutter experimental-features "['scale-monitor-framebuffer']" Works perfectly for me in a Thinkpad X1 Carbon 3rd Gen on Wayland apps, XWayland is blurry with scaling and is almost imposible to fix, I use it at scale of 175% Reply reply Among other changes, the upcoming Fedora Linux 42 release promises to enable DNF/RPM Copy on Write for all variants, a modernized live media by switching to the “new” live environment setup scripts provided by livesys-scripts, the unification of /usr/bin and /usr/sbin, and opt-in metrics for Fedora Workstation. However, the login screen only gives me the “GNOME” and “GNOME Classic” options, “GNOME” being X11 - no Hello, first time have installed Fedora 41 beta, but can’t launch any Electron app like VSCodium, DeltaChat, FreeTube - all of them from Flatpak. Disabling GPU is obviously bad, but I’m using it as a second After upgrading from Fedora 30 to 31, copy-paste stopped working. I want to use wayland and commended the # WaylandEnable=false option on /etc/gdm/custom. I tried uninstalling A community for users, developers and people interested in Fedora Linux, and news and information about it. . 10: 12864: December 18, 2023 Fedora 35 Silverblue + Nvidia proprietary driver, no wayland session. 10: 12780: After having upgraded from F38 to F39 I see a new window when trying to use KeePassXC with my Browser: This happens after I have opened a website with a login request and use Kespass’ function ‘Perform Auto-Type’. 22: 2370: December 24, 2023 Freesync on Wayland. Unfortunately this window can not be suppressed. 10: 11490: December 18, 2023 Fedora 35 Silverblue + Nvidia proprietary driver, no wayland session. New comments cannot be posted. before the recent changes to NVidia drivers and XWayland which made the use of Wayland with NVidia driver possible. I remember testing the Prerelease some I want to enable X11 so Barrier works (Wayland doesn’t pop a window), but when I go into etc/default/ I see no file to enable X11. Thank you! Fedora Discussion Freesync fedora 31. . This is guide for Fedora 41 GNOME + GDM users, howto enable X11 / XorgKDE Plasma + SDDM users check: https://youtu. The options in the login screen are “Gnome” and “Gnome Classic”. Even though I have the Intel built in graphics I use intel integrated card 530 and nvidia 1060. Now by boot order is back on Fedora but I have to get my Nvidia drivers working again. I can run "microsoft-edge -enable-features=UseOzonePlatform -ozone Hi, I have upgraded today to Fedora 41,but in the Gnome login screen, I select my user, enter password and takes me back to the screen again to select the user. For KDE, you can launch ‘systemsettings5’ utility and go to “Input Devices” → “Virtual Keyboard” section and select “IBus Wayland” icon and click “Apply” button to configure IBus in Wayland. 1, xwayland disabled) with: export GBM_BACKEND=nvidia-drm export __GLX_VENDOR_LIBRARY_NAME=nvidia expor how to enable Wayland -- Fedora Silverblue 39 . Hello people, I downloaded a daily build of Fedora Workstation 41 beta from koji but I cannot make Xorg appear in the cog wheel on the login screen. Rebooted to kernel 5. According to the release article in Fedora Magazine and the Nvidia howto at rpmfusion, this combination should work with Wayland. be/QsYvJwRfqW8Why enable X11?Fedora 41 is When I first installed Fedora, they rolled out the feature to switch to Xorg or Wayland and I used to use Wayland, but for apps like Zoom, I needed Xorg. You This package contains configuration and dependencies for SDDM to use Weston for the greeter display server. On a fresh Fedora 31 install with KDE plasma, Firefox 70 freezes the entire machine after a few seconds. conf [security] DisallowTCP=false [xdmcp] enable=true Rebooted the machine. Edge://flags doesn't have this option. I found this in dmesg: [ 17. However, this change is not just a simple switch and we need to do some adjustments during the path which will impact I am looking for info how to check if its enabled. I am trying to find how to set up and the tips Problem In Fedora 41 Workstation, old applications, which don’t support Wayland natively, may be incorrectly sized (too small or too large), if you use display scaling above 100% (a popular example: Steam). 11 kernel you seem way behind. I have a few different apps that are initially blurry when I download them. This guide is adjusted for Fedora only and may not work for stock Mozilla binaries or other distros. I am trying to change my display manager and use LightDM but it will not start at boot - when I manually start it from tty and login using my fingerprint it loads my GNOME desktop environment but does not automatically authenticate my keyring or sudo some startup Hi, I have just installed Fedora 35 on a PC with a NVIDIA Quadro M5000 using: sudo dnf install akmod-nvidia xorg-x11-drv-nvidia-cuda Wait for the kernel module to build Reboot Start sway (1. I have tried all the options in the gear icon: classic, classic in Xorg, None of them work. I tried changing the default boot order in BIOS but it would not switch back to Fedora - Grub so I reinstalled Fedora. The tip-off for me was the following quote in the stackexchange thread:. On POSIX dnf-y install gnome-desktop4 gnome-session-wayland-session gnome-classic-session f41-backgrounds-gnome gnome-control-center gnome-panel gnome-terminal gnome-text-editor gnome-calculator gnome-calendar gnome-disk-utility gnome-font-viewer gnome-logs gnome-usage gnome-system-monitor gnome-session-xsession firefox libreoffice -How to disable Wayland Support on Fedora 25- Note: The following tested under Fedora 25 with Gnome and GDM (default installation). 639921 (intel only) install intel-media-driver in both container and in Fedora Install paru in arch In arch use paru to compile chromium-wayland-vaapi: sudo paru -Syu chromium-wayland-vaapi. DiscordCanary --enable-features=UseOzonePlatform --ozone-platform=wayland --enable-features=WaylandWindowDecorations (Looks like there's also bug with CSD support being enabled and leaving a gap around the window when maximized, which was patched later but Hello, I have a problem that I just cannot understand. In this case at least the below was enough. [1] Install and Start Xrdp Server. All you You need to use the Wayland one, Fedora uses Wayland by default gsettings set org. Hello, I have tried all possible solutions I found and none is working code --enable-features=UseOzonePlatform --ozone-platform=wayland ELECTRON_OZONE_PLATFORM_HINT=wayland code Nothing seems to work. Open /etc/gdm/custom. I am using Fedora Server 38. Hello, I use Fedora 38 and 39 Workstation on two computers and have recently noticed that both use Gnome under X instead of Wayland. You can choose to run GNOME in X11 by choosing the Gnome on xorg option in the session chooser on the login screen. From Christian Schaller’s blog post (linked from the Fedora News article: Finally there is the NVidia binary driver support question. 3. /etc/gdm/custom. To install the drivers I have enabled the RPM free/non-free repos sudo dnf install https Fedora 33 beta We use it for GUI installations like Oracle. I have tried a few different walkthrus but none appear to Hi guys, I recently upgraded to Fedora 41 on my desktop. 6: 2185: October 18, 2021 Updated nvidia-installer to select the NVIDIA open GPU kernel modules by default on systems with GPUs that support both the proprietary and open kernel modules. Go to the line which looks like the following: [daemon] WaylandEnable=false Change it to (even if Hello all, I am using Fedora 31, I originally used KDE and then switched to GNOME. Obviously, there are MANY differences even among “legacy”, because a 2002 computer and a Turns out my problem was a setting on the server side, X11 forwarding seems to work just fine on wayland in Fedora 35. This is the generic default Wayland configuration provided by SDDM. Reboot the VM. On Chrome this is done through chrome://flags. Monitor is connected on intel. This article says “There is a firefox Hey all, I downloaded the Nvidia Drivers when I was using Gnome - Wayland. HowTo I’m new to Fedora and started with an installation of Fedora 39 Workstation Final. Fixed a bug that caused GPU driver installation to fail when the system used alternate implementations of the ‘tr’ utility, such as from the busybox or toybox projects. It’s assigned as a middle button, but is basically useless. Try to log into a Wayland session. Do you have a copy of your previous configuration or do you remember everything you changed? No Wayland option available on Fedora 39 with Nvidia. conf. Because I’m using an AMD Radeon RX 7800 XT I want to enable and use AMD FreeSync like I use it on Windows 11. When I press Ctrl+C in gedit, the selected text is copied to the clipboard, but Ctrl+V does nothing, and the Paste context menu is disabled. Note: Display scaling might be enabled automatically – that depends on what dnf-y install plasma-desktop plasma-workspace plasma-workspace-wayland plasma-settings sddm-wayland-plasma kde-baseapps kscreen sddm [2] After installing Desktop, to start Desktop session on CUI, re-login with a common user and run like follows. Woohoo! Logging in automatically with X11. PS: if you have a more powerful machine, you can create the arch container there, compile it, and then move the container over. wayland isn’t supported. 5 is now supporting AMD FreeSync (https://www. And restarted sshd on the VM, X11 forwarding works as expected now. 3 kernel as it waits for final approval and release. Because Firefox sometimes aborts silently, and I saw issues on Gimp (gimp), and Freeplane (freeplane) on Sway. wayland, gnome, nvidia, f39. But now that I’ve installed it, it looks super sharp! I am It turned out to be pretty easy with xrdp and GNOME. When I go into a full screen mode in Chrome (mostly noticeable on videos, but reproducible on any page) I get some weird artifacts. Ask Fedora. You still need a terminal Install Xrdp Server to connect to Fedora Desktop from the Windows Remote Desktop feature. The demo subpackage provides the clients programs: . From what I’ve figured out, this is because they’re Electron apps and they don’t run using Wayland by default, which is a problem because I’ve enabled fractional scaling. With the Plasma 5. (I don’t quite understand what Electron and Wayland are exactly, but I don’t think that’s part of my problem here). There is a firefox-wayland package available to activate the Wayland backend on KDE and Sway desktop environments. 11. Maybe that’s because I’m using beta version or something related with Wayland? Strange all those apps does not work, their windows shows with artifacts. Fixed a bug that could cause the wrong Hello, I updated to the new 545 drivers today (via rpmfusion), and wanted to give Wayland another try, since the new drivers apparently fix many issues with it on Nvidia cards (I have a GTX970). 🙃 Newer kernels and a lot of other packages are involved in operation of the machine, so I would say that (in general) upgrades apparently fixed the issues you were having. I was looking into this today because of a powerdevil bug with X11 I encountered while using tigervnc. By default, there is no virtual keyboard option on the login screen. But when I log into Gnome still get X11. I installed Fedora 31 Server and it seems to be behaving as expected. See attached screenshot. Starting GNOME Wayland from the Command Line in Fedora. weston-calibrator, weston-clickdot, weston-cliptest, weston-confine, weston-dnd, weston-editor, weston-eventdemo, weston-flower, weston-fullscreen, weston-image, ; Starting Weston GUI Login with GDM (GNOME Display Manager)In general you will have the Fedora So it turns out the app I was using just uses stdout and sway handles rendering of the bar. I can switch to console but nothing special in journalctl. However, when I attempt to log into an X11 session, I am able to login without issue. If it works, AFAIK tigervnc doesn’t support wayland. Project Discussion. I’d like to have a GUI. Currently KDE I had to reistall windows 11, and afterwords my default boot device switched to my Windows drive. However there are a few bugs discovered that Martin and Jan are trying hard to fix atm so we can keep this default for the GA release, but if they miss the deadline we will ship the X backend Every time I log into KDE I get the following notification: IBus should be called from the desktop session in Wayland. I wanna use something like 120-150% display scale Locked post. I know about Solaar as a tool for configuring mouse buttons, and there are @steppybug @grumpey. I am using both Sway on Wayland, and i3 (X-Window based) in some cases on Fedora 36 on Framework Laptop. Logging in didn’t initially work. Searching for a solution, I found out that Linux Kernel 6. The Wayland architecture is completely different than X11. I did sudo dnf install ydotool sudo ydotoold & sudo ydotool key Alt+F4. Well sort of. I already had automatic logins setup with KDE Wayland and wanted to switch it over so it would always use KDE with X11. fx30 — system fails at kdm or gdm or lxdm or sddm. How do you enable freesync on fedora 31? Mostly using a stock install. If I switch to another application then back to gedit, the Paste context menu is now enabled and Ctrl+V pastes the text that I copied earlier. Previously in Fedora 39 and XOrg, I could set the refresh rate to 144Hz, but now the screen freezes for some time before unfreezing and not having 144 been applied. conf but system still insists to use X11. I tried few times, installing it with: sudo dnf install @base-x sudo dnf install xorg-x11-server-Xorg sudo dnf install xorg-x11-drv-amdgpu It installs fine and there is no apparent problem but after restart the cog wheel doesn’t Doing so may increase security, reduce RAM usage etc. I remember a Wayland option being xrandr --props shows my monitor is variable refresh capable but I wonder if it is enabled by default or do I have to do something? I have my doubts about Freesync though, with AMDGPU-PRO you aren’t supposed to engage this feature in desktop but I wonder how that works out. Both operating systems are more or less stock, I haven’t changed much in either of them. F41 Beta is on the 6. I have had this issue since I’ve got my new laptop Lenovo Z16 Gen 1. In this setup fedora 33 is using X11 server. Unlike previous mice in this series,[1] the scroll wheel is really difficult to click. I needed to create a To enable Wayland for Gnome in Fedora, two main actions are needed, as explained below in details: Open /etc/gdm/custom. conf (also in /run/gdm) but could not find anything wrong. I have created this page as an EASY TO FIND and DIRECT SOURCE to allow anyone (me included) to understand how to handle Legacy Hardware (which still exists and will keep getting used until it all breaks down forever) with newer software. After logging in via terminal and entering “startx” I can access to the desktop. On the KDE side, serious work into supporting Wayland started shortly after GNOME switched to Wayland by default. I connect it to an external monitor. The team merged various I know I can start on wayland by typing google-chrome --enable-features=UseOzonePlatform --ozone-platform=wayland in terminal, but how to make this settings persistent on every launch of the browser? You can modify I can run "microsoft-edge -enable-features=UseOzonePlatform -ozone-platform=wayland" but of course this is not a viable option because I don't wanna open the terminal every time I need to I'm trying to enable Wayland on my Firefox install. dmesg lists new virtual device and ydotoold reports accepting client, but sudo libinput debug-events doesn't list any activity. Wayland is a more modern protocol and has a smaller code base currently. Accelerated web page rendering is supported on both X11 and Wayland backends via WebRender. However, the login screen only gives me the “GNOME” and “GNOME Classic” options, “GNOME” being X11 - no Wayland option. ho I’m new to Fedora and started with an installation of Fedora I have a new Logitech MX Anywhere 3S mouse. I have disabled all Gnome Could anyone help me telling how to enable VNC server with Sway desktop. Hm, so I am on fedora 32, GNOME 3. code will still start with XWayland Do you know how to force code to use Wayland? Thanks Followed the howtos to enable xorg, but now I can’t get wayland back. It’s in regards to Wayland’s support of fallback X11 support, which is intimately related to the binary drivers and how they’re installed. Firefox on Fedora supports hardware acceleration on Linux so let's look how to configure it and diagnose potential issues. How do you enable freesync on fedora 31? wayland, amd, gnome, radeon, f39, workstation. conf for editing (as you know, you must be root). Web page rendering. Our FAQ has the solution. I’m currently running a HP ENVY m7 Notebook with an Nvidia GeForce 940MX Optimus chip set. Here's how I enable it: Make sure that you're logged into the Wayland GNOME session. Reverting to gnome-terminal allows me to run xeyes without any issues. I have heard rumblings that Fedora is planning to drop installing X11 in some future version of Workstation, and only running Wayland. Anaconda as native Wayland application Summary. Recently I knew XWayland on the Framework community’s thread, and I consider using it. The screen, all keys, mouse, everything frozen and a power-cycle is necessary. A bit iffy so far, getting a plethora of hard to google errors, but after trying various stuff I managed to at least get it to run with google-chrome-unstable --enable-features=UseOzonePlatform --ozone-platform=wayland --disable-gpu --disable-software-rasterizer. Cheers, Idunno Yesterday, I installed Fedora 40 Workstation Prerelease with Gnome 46 RC. Great! I installed Chrome Dev (v87) now. For Hello, good morning. Shell@wayland. Failed to connect to the bus: Failed to connect to socket. Journalctl reports: org. 8-200. Unlike GNOME, KDE has a much broader stack in its toolkit, and it has taken longer to get to a usable state. I did the following: Installation $ dnf install weston weston-demo. enable display manager (sddm) sudo systemctl enable sddm. There also might be performance degradation or potentially some blurriness in games. I’m in favor of switching to Wayland, but I’m also in favor of not getting new hardware. Looking glass shows that Chrome Dev is running natively in Wayland (not using XWayland). Can you enable it? I tried creating the Hi guys, I recently upgraded to Fedora 41 on my desktop. Interesting news. It’s here! We’re proud to announce the release of Fedora 31. monkeygold (Sivart Emoswen) December 31, 2019, 5:11am 1. I had to switch my session to gnomex11 to get around it. In this section, we will guide you through the necessary steps to start the GNOME Wayland session successfully. hi, not sure if i'm going about this the right way, i've been trying to enable the Wayland compositor to switch to it from Gnome however i can't seem to enable it /etc/gdm/custom. Fortunately, there is a “smart shift” button right behind that, and it’s easy to use that as a middle button. Today when I booted it with 2nd monitor unplugged gdm failed to start (it starts and after ~1 second crashes and again and again). mutter experimental-features "['variable-refresh-rate']" (GNOME 46 to Ship with Experimental Variable Refresh Rate (VRR) Support - 9to5Linux), but after rebooting, the VRR setting is still not available. Any ideas ? Thanks Nar. discordapp. gnome. 36, latest updates. This happens only on Wayland though and only with hardware acceleration enabled in Chrome. I'm using fractional scaling right now. I do not want to share with a remote desktop. The reason this is a Fedora related issue is as follows: By default, VirtualBoxes is blindingly white and refuses to respect dark mode settings. However, there normally is a way of overruling this using qt5ct: Giving VirtualBox a dark mode However, there are two problems in Fedora when using Wayland (as far as I can tell anyways): There is no ~/. service - GNOME Shell on Wayland was To enable Wayland for Gnome in Fedora, two main actions are needed, as explained below in details: TL;DR: Enable Wayland in the GDM configurations in /etc/gdm/custom. I tried the command gsettings set org. I tried uninstalling and reinstalling my drivers, and realized that my wayland session A community for users, developers and people interested in Fedora Linux, and news and information about it. After installing Nvidia’s proprietary drivers from Gnome Software with SecureBoot enabled, and resolving the renderer bug (Latest Gnome apps not working in fedora 41 using wayland - #4 by justc) The question I have next is: What would be the proper procedure to add the CUDA toolkit to Fedora 41 without causing conflicts with the clean installation of the proprietary Id say the main problem with discord is gpu acceleration not working on system package, gpu decoding not working system package by default, gpu encoding not working instead using software encoding, audio not working with screen sharing but can be fixed now, wayland support not enabled by default as screen sharing is broken, screen sharing under wayland is broken The driver really has nothing to do with whether the iGPU or dGPU is chosen for use. If you’ve made custom changes it’s possible this update confuses things a bit. Does it work for you on GNOME as well? Wayland is a display server protocol which was (at the time of writing) introduced as the default in GNOME. I’m listing the main problems I have here, assuming people with Nvidia might have a similar set of problems: I’m connecting my Samsung TV QN55S92C with a 4k 120Hz HDMI cable. Some good reference material is in this tutorial, but short answer is it’s not ready for prime time. # netstat -an|grep 6000 No listening port Is the daemon started/enabled? Try `sudo teamviewer daemon enable` then try again, maybe while installing the script didn't succeed enabling the service it need for remote connections. For other desktop sessions, you can copy the ‘Exec=’ line Hello, I updated to the new 545 drivers today (via rpmfusion), and wanted to give Wayland another try, since the new drivers apparently fix many issues with it on Nvidia cards (I have a GTX970). I have an NVIDIA Card in my system, and when I attempt to login into a wayland session (GNOME), I am booted back to the login screen. 20 release, the Wayland protocol for screencasting as Fedora 35 just recently got changes to make Wayland on Nvidia easier to enable. Then try logging in to Gnome on wayland from the log in screen. How i can enable Wayland in this setup? my grub configuration (if this is related): A community for users, developers and people interested in Fedora Linux, and news and information about it. 6. I’ve tried the following: Verified that WaylandEnable=fa. Hopefully my solution will help some folks with podman usage anyway. Make sure you’re up to date with sudo dnf update --refresh and reboot. How to make chrome or chromium run natively on wayland permanently? I know I can start on wayland by typing google-chrome --enable-features=UseOzonePlatform --ozone-platform=wayland in terminal, but how to make this settings persistent on every launch Followed the howtos to enable xorg, but now I can’t get wayland back. I have checked the gdm custom. I know I should be setting an environment variable (some places have said GDK_BACKEND=wayland, and some have said Wayland is enabled by default in the GNOME Desktop. After a system reboot, there’s now an additional option at the bottom right when I login to Fedora, called Plasma X11. I already started to look at the mess of all these services autostarting, then people told me these xdg-autostart services To enable Minecraft Wayland support, you also need to: If you're using Mojang's Minecraft Launcher: A Description This repository provides a patched glfw which support Wayland & which works with Minecraft. And it runs fine for me. Just revert the changes you made to /etc/gdm/custom. pdvz maze iaraf fobkogyy bylnkr bxed csur nfqn kmxopr mbgfb yhjxo ijnjb zyhdvsm ufn gyeh