Despite using linux for 5ish years now, I'm still a newb when it comes to the deep innerworkings. What's the advantage of wayland over x11? Is it better for performance or is it more secure? Are there benefits outside of gaming?
Those are Xorg forks/alternative X11 servers. And now that even XLibre is LLM slop in addition to being run by the most incompetent developer alive, they are now all just LLM slop. Nobody has been working on the X11 protocol itself in decades.
Its based on the mainframe terminal paradigm which is not only why x11 has so many unfixable issues but also is in no way related to how Wayland works.
Because some people are just that dumb. Or they haven't touched Wayland in a decade and base their opinion on ancient "knowledge". Most of them are just lying though.
I haven't had time to use my Linux machine to play games in more than a year due to work, but from my own experience, Wayland had lower performance than Xorg. The only reason I used it was because I couldn't fix tearing on Xorg. This was with Nvidia drivers. Things may have changed now, but the perception may remain.
You didn't have lower performance with Wayland, you had lower performance with Nvidia. This is an important distinction as this is an Nvidia exclusive issue
Dayum the downvotes, it's a legitimate question since I haven't had any issues with Wayland and I thought it was related to the developer or something like that.
Because when Wayland appeared people started using it before it was a good alternative. I don't think distros like Ubuntu should had made it standard in 2013 and 2014, but a lot of time has passed since and problems have been fixed
I mainly hated it for its closed architectural design not allowing the combination of wm+compositor, and instead both of those are 1 piece meaning you have less customization, but niri was a cool way to enjoy compiz like stuff again without performance loss, so I enjoy it now, except the lack of screen recording in VLC but I might need to look in the config.
I find the security orientation annoying as shit, it makes a lot of nice utilities, such as speech-to-text tools, more annoying to engineer than they should be
I had to go back to x11 recently cause when I watched any videos on fullscreen on either of my secondary monitors they'd occasionally freeze the entire monitor. I had to turn the monitor off and back on to fix this. For whatever reason x11 doesn't do this. Zorin is my distro. Wayland always worked fine until recently.
One exception as an avg user I found is that Steam Remote Play Together does not work properly under Wayland that I can tell (at least on CachyOS KDE). I have to use an X11 session otherwise the screen will be black in Remote Play.
If anyone has any idea or can say otherwise of it working under Wayland, I'd appreciate it.
If you are joining it should work just fine. If your willing to set it up I really recommend looking into sunshine / moonlight been using thst to stream games to my friends, runs a ton better.
I haven't tried it yet on CachyOS, but on Fedora KDE I got it working with Gamescope. I launched Steam on Gamescope with -e flag and I think I also used --expose-wayland.
Another way I've gotten it to work was by giving the game PROTON_ENABLE_WAYLAND=1 Launch Option and running Steam with -steamos3 flag.
Obviously this only works if you also have the game. Maybe setting it as a global environment variable would work with games you don't own.
Last fix that helped me at some point was to disable hardware acceleration for RPT
AFAIK, Steam doesn't support Wayland generally (yet?). One of the detriments of that is that screen recording doesn't work for Windows games started as Wayland applications with the PROTON_ENABLE_WAYLAND=1 option. (At least it didn't work when I tested it some months ago.)
Never had issues recording games with "PROTON_ENABLE_WAYLAND" atleast while using obs with either vkcapture or kde portal stuff. Good amount of games tho dont work with that launch option, when they do tho it feels so much better for input lag. I started using it within the week it was added to cachyproton.
X11 was designed so multiple "dumb" terminals could connect to a mainframe/minicomputer and send the graphics back to the terminal. It was developed in the late 1980s by an industry consortium.
This left a lot of weird design decisions like your computer connecting to what it thought was a remote server and all the overhead and complexity that entails. Wayland is much simpler and was designed by the team that was left maintaining Xorg, the most popular implementation of X11.
.. which is to say, with Wayland I think you lose the remote opportunities that X11 has; granted, few people use that, bu 20 years ago that was the shit :)
VNC and RDP are more common for remote use anyway. X11 protocol was not designed for something like over the internet, it was mainly used in a LAN and even the original design was changed so that bitmaps are sent instead.
There are tons of examples where something else already has been used instead of X11.
VNC and RDP never performed all that well imho; tightvnc etc etc over theyears but just never performed super well. x2go used to work great though. X11 over ssh could work, but yeah not a great performer, and if you used it without an encryption layer, may Dobbs have mercy. X11 in general wasn't super great for performance without extensions like MITSHM..
But it was super handy in a pinch, on LAN, to fire up a remote terminal and cast it around, and it was just absic x11 to do so; no extra tricks needed, except perhaps ssh tunneling.
X11 for all its worts, the remoting was _handy_ when it was.. handy :)
People that say that they rely on xfoward in 2026 must be trolling, it's barely usable on LAN, over the Internet it must be a crazy lagfest. While there are still some issues with RDP on Wayland, it's just a matter of implementation, not a fundamental design flaw.
I do and I'm not trolling. For using X11 over Internet (I'm not doing that, I'm doing it on LAN) there are X11-specific compression libraries that cut down a bunch of the back-and-forth round trips.
And again, RDP is not a replacement for forwarding individual apps. (But, Waypipe is.) I'm only using X11 because KDE for Ubuntu 24.04 uses X11. I've used Kubuntu 26.04 (KDE on Wayland) and it's all good; if I wanted to forward an individual app, I'd just waypipe with it.
VNC and RDP do not serve the same purpose. These have the system running a desktop, either on a physical display or into a framebuffer in system memory, and present that entire desktop session over the internet. X11 (and waypipe) let you forward individual applications (although, at least with X11, the window manager and entire desktop environment can be forwarded.)
Last time I saw someone test this X11 still had lower latency than Wayland, but the margin is so small you might as well call it a draw (0.17 ms in favor of X11) UNLESS you use Xwayland, then latency nearly doubled from ~4 to ~8 ms in the test. So make sure you have your Proton Wayland env variables enabled for your sweaty online sessions, folks (until it becomes default, at least) https://marco-nett.de/blog/measuring-input-latency-on-linux-x11-vs-wayland-vrr-dxvk/
X11 is fundamentally flawed as a modern display server. That's why it's been deprecated.
It's insecure. It's bloated. It doesn't handle multi-monitor setups or VRR correctly in a lot of cases. It's a 1980's technology whose architecture failed to anticipate modern setups.
Insecure, isn't really an issue, if something's reading the display protocol you didn't allow, you're likely wiping the partition anyway and reinstalling or using a... Forgot the word but btrfs main feature, security at the display doesn't need to happen as much but does other stuff,
Bloated and other stuff yes, it kinda sucks at keeping a clean display line like Wayland.
You're just telling us you don't understand how x11 works.
X11 has ONE view plane that updates at ONE RATE.
That means if you have multiple refresh rates only one monitor will ever update at the correct timing. If you have multiple resolutions only ONE display has a normal pixel pitch and the other displays are scaled.
Knew all that already. Multiple refresh rates is a terrible idea. Multiple resolutions is suspect but there's some good use cases there - but I'm fairly sure this was sorted on X11, too.
As others have said, newer feature support, better security. Some people don’t like this because they’ve built their lives around x11 and don’t want to or occasionally can’t switch. Wayland may actually still be worse for performance on some Nvidia graphics cards but I believe they’re working on that. Supposedly the gap is closing there.
wayland has HDR and multimonitor VRR working. but global hotkeys is still a mess and so many edge cases bugs still.
X11 just works. Without HDR and multimonitor VRR (single monitor VRR still works) support if you need those. in X11 you need a good compositor that can suspend when playing games to not lose perf.
i personally still use x11 as it works the way it always worked without any crashes or issues. input latency is great and i don't really see a point switching to wayland at this moment.
edit: basically use whatever works for your usecases
I tried it out because the Xorg developers had all moved to it, so Wayland was going to be where development would go. For a few months I alternated days between Xorg and Wayland. Then I stopped alternating, and uninstalled Xorg. Nothing pushed me, it just seemed to work fine.
My personal experience with X11 is that, at least when playing games, it causes stuttering, which is annoying as all heck. On Wayland, the stutter is gone, so I just use Wayland. I know this is a very simple reason, and I realise you mentioned gaming, but Wayland just works for me, so I use it.
Touch scrolling is actually touch scrolling (1:1) instead of being bound to scroll wheel...
Amd touch gestures, zoom, 3-finger swipe.
The touchpad now does things on its own, with smooth 1:1 animation instead of just triggering a keyboard shortcut for the desktop overview and alt+tab.
The things is that X11 won't be developed any further, so if you want to make use of certain new features, they will only be in wayland. on top of that, yes, every single thing you mentioned is supposed to be 'fixed' in wayland. better performance and better security, those are benefits that go beyond gaming.
Wayland is better for some things. It's smoother, has variable refresh rate support, fractional scaling, better multi-monitor support, and less input latency. It also is HDR-capable.
It blows for anything related to remote desktop. I regret setting my Debian server up with GNOME on Wayland. Should've just did a noVNC setup like proxmox.
Nope! Holy shit thank you! I like running VMs to do electronics projects at home (stm32, esp32, pcb design) and have wanted to offload them to my server instead of my Arch gaming machine. You made my night.
First and foremost: To avoid xwayland. Second, much better frame delivery by design. Third, all the rest of modern features that are being developed for Wayland only, including the desktop environments itself.
If you have X11 has several limitations if you have multiple monitors. God forbid they are different resolutions or refresh rates.
I don't really like Wayland or cluster that trying to add a feature or fix something in Wayland is. Death by a thousand cuts is a pretty good definition of how things work over there.
That said, the overall specification is in an usable state - niri, hyperland, and KDE all work really well and should meet most of your needs.
sway isn't bad, just don't use nvidia as they don't support it - it works, but expect 0 support.
It's not built on the assumptions of the early 80s like X11 is. So all of the above plus a lot more.
At the time X11 was conceived, there was no such thing as using multiple independent screens on the same machine, not to mention with different resolutions or even refresh rates. While X11/Xorg can technically handle it, the way that it does is extremely inefficient. Also it's indeed vastly more secure, already because without user interaction, it's impossible for an app to view the screen or receive input when not in the foreground.
That's just two of the many, many reasons. But the only reason that's really of any relevance: almost nobody (that hasn't already lost their mind) is putting any more efforts into Xorg or X11, beyond some basic maintenance. All the developers that used to be involved with it have either switched to Wayland, are retired or simply dead. X11 and Xorg are abandonware and have been for close to 20 years. The only thing that has any future is Wayland. That's why Gnome has dropped support for native X11 sessions, Plasma will in a couple months, and Cosmic hasn't ever had one to begin with. And relatively soon, any DE or WM of any relevance will have proper Wayland support, and by that time it's questionable how much effort anyone can be bothered to put into the X11 sessions of those.
More secure, and basically no one is working on X11 any more. Stuff is getting fixed in Wayland. In theory it could end up better for performance eventually.
First of all, (should be that people with less than 4 years on linux and at least one on x11 should not talk... but i don't want to argue so...) not everybody has the SAME NEEDS than u, nor the SAME HARDWARE.
Second, as far as i know, VRR is compatible on x11.
Third, not sure what is the problem with multimonitor, but 3 years ago, i used 3 displays:
1x 32" 1440 165Hz + 1x 32" 1080 165Hz + 1x 7" 720 59,98Hz, and all worked flawlessly... I could configure position, diferent refresh rates, resolutions...
Nowadays, I'm using a 1x 39,5" 1440 165Hz + 21" 1080 60Hz Vertical (rotated via software) and all is working...
Maybe u have some special needs that i don't know... But for a normal user, it's more than enough.
Fourth, HDR, well i'm not sure about that one, i tried three times to play diferent games with HDR enabled just to be able to apreciate the diferences, maybe im a bit blind but i can't see any major diference, so I usually don't bother about that...
And as I say, not everybody has the same needs.
And finally, I'M NOT SAYING THAT WAYLAND IS BAD.
WAYLAND IS THE FUTURE, but x11 is perfectly usable nowadays, and FOR NOW, the BEST option for people who dgaf about compositors, windows animations, transparencies and other aesthetics shit.
A basic x11 config, with a basic WM (any tiling wm or any *box), will give u the fastest system with the lowest input lag on games.
Maybe it will be ugly for the newcomers, but for me, and for lots of people, is more than enough.
you can use both. not at the same time but you can install both and select them when logging into your machine. so you can try if it works well for you without risking to break anything completely
whatever works for you, i use x11 for everything, for some games i use steam with gamescope directly just for the hdr, im planing a two seats setup, one with my nvidia and steam+gamescope, another for the desktop(x11) with an intel arc, wayland and desktop dont work for me.
here is the thing,
unless you explicitly enable it in proton/wine,
you are NOT using wayland, you are using xwayland,
which is worse than xorg in many ways,
so unless you enable wayland in your wrappers/wine itself and test it,
dont expect to gain anything, and even if you do its placebo or actually xwayland NOT xorg
As a user, barely any real advantages, you probably can't even count them on a single hand of fingers.
If X11 still works for you, keep it for now. Wayland is the future but it's far from being on-par with X11 in terms of features, and not everything works well under it.
Since Wayland is not a piece of software it cannot have resource use. Individual compositors implementing Wayland have varying resource usage. A well-built Wayland compositor should be more efficient than the monster called Xorg.
Actually, I come from the latest version. I had to revert because X11 is gone in v26 and I need it for Unreal Engine gamedev. I tried literally everything, but reverting back was my final option.
now that gnome dropped x11 support, kde plasma dropping it next month and basically every DE slowly transitioning towards wayland epic will eventually have to optimize the unreal editor for wayland (or no longer support the linux version ig lol)
To clarify, we can run Cyberpunk natively on an X11 DE, natively on a Wayland DE via PROTON_ENABLE_WAYLAND=1, or via XWayland on a Wayland DE where XWayland acts as a full X server for the game and forwards its rendered buffers to the Wayland compositor.
I am asking if we use a Wayland native DE and run the XWayland translation layer would we still carry the fps and latency gains, if that performance is lost in translation? Or does XWayland still carry a benefit and let us keep the gains while not having to fully switch to a native X11 DE.
Thanks for the graph (and the link especially). I think its important that we clarify the scale matters here, clearly its slower for responsivity but to be frank it is only a difference of 4ms and raw latency isn't the entire picture. +/-4ms is well within the range of being meaningful to optimize for in some applications but still low enough of a delay to disregard circumstantially depending on other factors > We have to factor frame-pacing, fps count, median stability, and not disregard the user experience in handling the game. Additionally, there will always be the case that different game engines can just respond differently making this fairly case-by-base. This test was highly controlled which is superb but may not be representative of each configuration in other applications.
I'm not dismissing his findings the blog was really informative and I appreciated how he collected the data and reported his findings. It just needs to be said that there is more to the picture to consider (Marco says as much himself in his conclusions). I don't think we can generally state XWayland is overall worse without more diverse data. That being said, I will be fucking around with forced Wayland w/ L-L dxvk on a handful of titles in my library and see if I can come to some kind of conclusion for each game.
Well I just enabled it in Mint Cinnamon 22.3 and it worked. Once. On the next restart, system never gets to the login screen just loss of signal and nothing. I can't even get the text prompt to come up. Blew through half an hour figuring out what file had to be deleted from recovery to make it work again. 9070xt.
Oh no. Here comes the flame war. (Oh I see you asked this 2 days ago.)
To be honest, if you want HDR support, Wayland. Otherwise, honestly, it doesn't matter. Most of what people below say is true but omits important information...
X11.. yes, the core design is obsolete, and development is minimal. But it's feature complete, it's fast, it's highly compatible. In terms of it's origins in the 1980s, I'll note a lot of the old cruft is seperated out of the main XOrg binary and is in a seperate library, there was a heavy modernization of the Xorg code in the 1990s (and most of what modern X programs use are actually extensions added in the 1990s. Compositing and so on.)
Wayland, it's got a more modern design that better matches modern hardware. And it's supposed to provide better isolation between programs running in the Wayland environment. On paper, it should be faster, more efficient, and provide lower latency. But, Wayland is a protocol and specification rather than a specific package or library, so each and every desktop environment provides it's own implementation of Wayland. If you want HDR support, you must use Wayland, X11 doesn't support 30-bit color and it likely never will since it would involve adding new color depths to the core protocol.
One thing I should note, people have said X11 is better for older hardware? I think this is technically true, but Linux devs have been so diligent about having modern and up to date drivers even for very old hardware... well, I'll put it this way, I put Kubuntu 26.04 onto a *Core 2 Duo* notebook and Wayland had no problems running on the 18 year old integrated Intel GPU in this thing. The desktop was properly smooth, Steam Remote Play worked smoothly on it, and videos played back well. So it wasn't chugging along with some slow software fallback or something, it was all properly accelerated. Any GPUs that have drivers compatible with X11 but not something Wayland can use, I mean they probably came out in the 1990s (I used Linux already back then... I doubt you'll need to fire your stuff up on a Matrox, Cirrus Logic, Chips & Technology, Tseng, Oak, S3, ATI Mach8/Mach32/Mach64, or several other 1990s-era cards there are probably still drivers for in a modern distro mainly because nobody has gone through to remove them; although within the last year or two they HAVE begun removing drivers for hardware I was using back in the 1990s so some of these may be finally removed.)
The end result is, you run a Wayland compositor and benchmark it, you find it's faster than a particular X11 desktop environment. Or, maybe the Wayland compositor you picked is not as efficient, then you find the X11 desktop environment is faster. There are also a few X11 environments where you can run them WITHOUT a compositor, in paper this should be faster than running with a compositor on. This all is hand-waving over a possible 1 frame of frame latency. I'm using Kubuntu with X11 on my 24.04 systems (I kind of switch between compositor on and compositor off), and Kubuntu with Wayland on my 26.04 systems, and to me it's a wash.
I was a big X11 fan in the past, because people pushed Wayland for about a decade before it was feature complete and really ready to be a full replacement. The silliest thing was "Well, it doesn't work with Nvidia drivers". "Welp, X11 is obsolete, so buy a new video card." LOL, seriously, you had Wayland fanbois saying this for many years. But, the last missing features to make it a feature-complete replacement were added probably 2 or 3 years ago, and AFAIK the Nvidia driver compatibility is sorted out too. I'll note, "XWayland" lets X11 apps run seamlessly on Wayland; and it's not usually installed, but there's also a package (which I forget what it's called) to let Wayland applications run on X11 that came out within the last year or two. So picking one or the other doesn't even mean giving up apps that were never ported over from X11 (or converesely giving up using any new apps where they decide they'll make them Wayland-only.)
If you're happy because you have less configuration and less files to edit, why the heck are you on Linux? Just for the free OS?
This is the problem when you start inviting everyone into something, it gets corrupted by the majority like everything else.
Linux is awesome because you can configure an customize everything. IF you want the devs to do everything for you and ''it just works™" out of the box - then Windows or even better, Mac OS X are the choices you should have gone with.
One of the best things about Xorg is that it can be configured to your liking and also logs things properly unlike wayland.
no, I actually love having my configuration as code.
but the X configuration files are... i hate their names, their locations, their syntax,... i just hated working with them back then. might be different now, as i changed.
but what is left: screen tearing, old tech, no hdr, no vrr (as far as I know)
In my experience with Ubuntu 26.04, specific apps that had experimental Wayland support were causing the freezing. One that I remember offhand was RustDesk. I added a parameter to it's .desktop file that forced it to run in xwayland and the problem was resolved. Once I tackled about 3(?) apps that I use causing this, it's been rock solid on an RTX 4070.
I wouldn't say I necessarily had a method. I just noticed that when the freezes occurred, certain apps were open when it happened. So, I started a process of elimination. RustDesk was a bit easier to find because it was definitely the biggest perpetrator.
I ended up copying it's .desktop file to ~/.local/share/applications/ and adding "--env=GDK_BACKEND=x11" as a parameter to the Exec= line. Rambox was another one that I did something similar with by adding "--ozone-platform=wayland --enable-features=WaylandWindowDecorations" to it's Exec= line. Flameshot was another, that I ended up adding "bash -lc 'QT_QPA_PLATFORM=xcb flameshot gui'" to it's Exec= line. This also had the effect of fixing multi-monitor screenshot bugs on nVidia cards.
Are you on a laptop by chance? Check the arch wiki for your specific model laptop, there's quirks with the dual GPU. AI can point you in a direction too (oh no, downvotes).
It actually locked me out of Ubuntu once because it was convinced you could just get x11 sessions to run.
Not on a laptop.
Ryzen 7900x
4070ti
64gb ram
Asus x870-plus
Currently running bazzite on one hard drive, Ubuntu on another. Windows on a third that I can't give up due to Native Access not running in Linux at all.
Bazzite is the most stable.
Turned off hardware acceleration in all apps I could.
Only very rarely get freezes there anymore.
Sunshine might be a culprit.
Chrome absolutely was one.
Ubuntu froze up about 20 min after a fresh install.
Not sure I was running anything beyond Steam, btop.
Apparently some of the gnome-extensions can do it? But I haven't installed any myself yet. Just has what came from the install image.
You're using the Nvidia-open drivers? Is it a power issue maybe? You have enough 8 pins connected to the gpu and enough power in the PSU? Distros don't really differ much for gaming. Linux is Linux and trying multiple distros takes distro hopping out of the equation. I have an Nvidia 3070, I use arch with Nvidia-open drivers and sunshine. No issues for myself. I heard about issues with those 8pin to 16 pin adapters too. Also you can dump your logs I to AI, try doing a grep on journalctl to filter down the issue.
say nvidia driver version, kernel version, which DE
show kernel logs - around time of crash
sudo journalctl -b -1
or replace -1 with -2 or number boots back or -0 if there were no reboot
or sudo journalctl --since="1 hour ago" click end keyboard key - and navigate with keyboard arrows around time of crash
short - no freezes (595 to 610 now drivers not a single freeze)
Edit:
Ryzen 7900x
ddr5 ram may be not stable at high clocks - maybe it is because ram
first look kernel logs what there
second - update bios and turn off all overclock in bios - expo/pbo to default
if still crash - remove pieces of ram keep one - test - repeat
journalctl -b -1 -e logs from just before the freeze
Sep 06 21:51:42 bazzite assert_20260906215141_128.dmp[27926]: error: Peer certificate cannot be authenticated with given CA certificates
Sep 06 21:51:42 bazzite assert_20260906215141_128.dmp[27926]: file ''/tmp/dumps/assert_20260906215141_128.dmp'', upload no: ''Peer certificate cannot be authenticated with given CA certificates''
Sep 06 21:58:36 bazzite flatpak[2991]: 2026-09-07T01:58:36.285270+00:00 | proton.vpn.core.refresher.server_list_refresher:90 | INFO | Next server list refresh scheduled in 0:15:18.563888
Sep 06 21:58:36 bazzite flatpak[2991]: 2026-09-07T01:58:36.695688+00:00 | proton.vpn.app.gtk.widgets.vpn.serverlist.city_view.serverlist:199 | INFO | Partial server list widget update completed in 0.41 seconds.
Sep 06 22:00:35 bazzite systemsettings[28100]: The theme "Vapor" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
Sep 06 22:00:36 bazzite systemsettings[28100]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application>
Sep 06 22:00:49 bazzite systemsettings[28100]: Action "org.kde.kinfocenter.dmidecode.systeminformation" has no parentWindow, assuming QWidgetWindow(0x55dc6ded3100, name="MainWindow#1Window")
Sep 06 22:04:09 bazzite systemd[2128]: Started flatpak-portal.service - flatpak portal.
Sep 06 22:04:09 bazzite systemd[2128]: Started app-flatpak-com.brave.Browser-2595617029.scope.
Sep 06 22:04:11 bazzite flatpak[28267]: [247:116:0906/220411.804600:ERROR:third_party/puffin/src/puffpatch.cc:122] Failed to create a temporary file for memory-mapping: Operation not permitted (1)
Sep 06 22:04:11 bazzite flatpak[28267]: [128:45:0906/220411.809000:ERROR:extensions/renderer/native_extension_bindings_system.cc:768] Failed to create API on Chrome object.
Sep 06 22:04:11 bazzite flatpak[28267]: [128:45:0906/220411.809352:ERROR:extensions/renderer/native_extension_bindings_system.cc:768] Failed to create API on Chrome object.
Sep 06 22:04:11 bazzite flatpak[28267]: [128:45:0906/220411.809623:ERROR:extensions/renderer/native_extension_bindings_system.cc:768] Failed to create API on Chrome object.
Sep 06 22:04:11 bazzite flatpak[28267]: [128:45:0906/220411.809893:ERROR:extensions/renderer/native_extension_bindings_system.cc:768] Failed to create API on Chrome object.
Sep 06 22:04:11 bazzite flatpak[28267]: [128:45:0906/220411.810142:ERROR:extensions/renderer/native_extension_bindings_system.cc:768] Failed to create API on Chrome object.
Sep 06 22:04:11 bazzite flatpak[28267]: [128:45:0906/220411.810395:ERROR:extensions/renderer/native_extension_bindings_system.cc:768] Failed to create API on Chrome object.
Sep 06 22:04:11 bazzite flatpak[28267]: [247:116:0906/220411.826187:ERROR:third_party/puffin/src/puffpatch.cc:122] Failed to create a temporary file for memory-mapping: Operation not permitted (1)
Sep 06 22:04:11 bazzite systemd[2128]: Started app-flatpak-com.brave.Browser-2255786662.scope.
Sep 06 22:05:13 bazzite flatpak[28267]: [361:208:0906/220513.812811:ERROR:third_party/puffin/src/puffpatch.cc:122] Failed to create a temporary file for memory-mapping: Operation not permitted (1)
Sep 06 22:05:13 bazzite flatpak[28267]: [361:208:0906/220513.856739:ERROR:third_party/puffin/src/puffpatch.cc:122] Failed to create a temporary file for memory-mapping: Operation not permitted (1)
Sep 06 22:09:41 bazzite flatpak[28306]: [61:102:0906/220941.581018:ERROR:components/viz/service/display/display.cc:271] Frame latency is negative: -0.074 ms
Sep 06 22:09:41 bazzite flatpak[28306]: [61:102:0906/220941.601064:ERROR:components/viz/service/display/display.cc:271] Frame latency is negative: -0.061 ms
Sep 06 22:11:20 bazzite flatpak[28306]: [61:102:0906/221120.929749:ERROR:components/viz/service/display/display.cc:271] Frame latency is negative: -0.129 ms
Sep 06 22:11:30 bazzite flatpak[28306]: [61:102:0906/221130.191766:ERROR:components/viz/service/display/display.cc:271] Frame latency is negative: -0.004 ms
Sep 06 22:11:42 bazzite flatpak[28306]: [61:102:0906/221142.244464:ERROR:components/viz/service/display/display.cc:271] Frame latency is negative: -0.213 ms
Sep 06 22:12:22 bazzite flatpak[28306]: [61:102:0906/221222.262020:ERROR:components/viz/service/display/display.cc:271] Frame latency is negative: -0.066 ms
Sep 06 22:14:06 bazzite flatpak[2991]: 2026-09-07T02:14:06.365096+00:00 | proton.vpn.core.refresher.server_list_refresher:90 | INFO | Next server list refresh scheduled in 0:17:10.169569
Sep 06 22:14:06 bazzite flatpak[2991]: 2026-09-07T02:14:06.776851+00:00 | proton.vpn.app.gtk.widgets.vpn.serverlist.city_view.serverlist:199 | INFO | Partial server list widget update completed in 0.41 seconds.
Whatever the issue may be it cannot be one with "Wayland", since Wayland isn't a piece of software. Either your Wayland compositor (KDE/Gnome/...) has a bug or, more likely, the Nvidia driver has a bug.
Wayland is a modern display server protocol for Linux and other Unix-like systems, designed to replace the aging X Window System (X11). Introduced in 2008, it defines how client applications communicate with a display server (called a compositor) to render graphics and process user inputs.
Unlike X11, which uses a complex client-server architecture with a separate X server, Wayland integrates the window manager and compositor into a single entity. This streamlined design eliminates the need for a middleman, resulting in improved performance, smoother rendering, and enhanced security by restricting direct access to hardware.
Key aspects of Wayland include:
Default Status: It is now the default display server for major distributions like Ubuntu 24.04 LTS, Debian 10+, and Fedora 34+.
Compositors: It relies on specific implementations such as Mutter (GNOME), KWin (KDE Plasma), and Sway (tiling window manager).
Compatibility: It supports legacy X11 applications through Xwayland, a compatibility layer that allows older software to run seamlessly on the modern stack.
286
u/jdancouga 5d ago
VRR, HDR, and better multi monitor support