Time for Nvidia to step up their driver game... shrugs
this post was submitted on 09 Oct 2023
216 points (100.0% liked)
Linux
1261 readers
57 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
Well let's hope that massively improves the Wayland experience then. I tried it last week and still had flickering screens, laggy windows, and crashing games. In the current state it would be unacceptable for me to switch
I had the same problems until I switched to an AMD card. Since then it's been smooth sailing in Wayland.
I had those issues with an old nvdia driver version, bun on the recent ones it works better.
They still haven't solved the problem of a Gnome Shell crash taking down my entire session with it. I need to be able to restart the shell independently of the Wayland compositor for me to switch.
I feel like if Gnome Shell is crashing enough for this to be a problem then it crashing is the actual problem.
KDE Plasma will get this feature soon, I hope GNOME Shell will follow their approach.
~~ubuntu already compile gnome with the fix~~(edit: i confused it with triple-buffering, that ubuntu compile gnome with, idk if ubuntu compile gnome with the fix to don't take down the entire session), but the merge request is there, and it work, idk with gnome didn't merged it still, maybe other priorities?
load more comments
(2 replies)
Yep. I'm not even using Wayland. Every other day its "Oops, there was a fucky wucky!" And I have to log out. I'm on Cinnamon for now.
This is great. X11 needs to die in modern DEs so we can all move to Wayland for good.
Fix the issues with wayland so that we are all able to use it, before forcing us to move for "our good".
In my experience, most of the issues with wayland are caused by ~~applications~~ software not supporting it. If we enter a wayland-only world, developers are pushed towards supporting wayland.
[This comment has been deleted by an automated system]
It's not GNOME's or wayland's fault that Nvidia refuses to fix their drivers.
load more comments
(1 replies)
You are correct in saying that there are still several problems in both Wayland (e.g. lack of drawing tablet support) and mutter (e.g. tearing protocol non yet implemented). But then you proceed to list problems that are Nvidia's fault.
The first is weird, but it probably depends on Nvidia's kernel driver.
The second is probably a synchronization issue, so it's probably due to Nvidia refusing to implement implicit sync, and explicit sync not being yet supported in Linux. But don't quote me on that.
Vulkan should work. But video acceleration is definitely absent, and is listed by Nvidia itself among current driver limitations. Try this.
load more comments
(1 replies)
load more comments
(1 replies)
What's everyone's Wayland showstopper?
I'm holding out for better autoclickers/macro recorders before I go to Wayland
Nvidia
Better Wine support. It's coming soon, but I prefer xorg until Wine properly supports Wayland.
I recently stopped switching to x11 for gaming. With most games, the performance is 5-10fps better on Wayland
load more comments
(3 replies)
[This comment has been deleted by an automated system]
I play Heroes of the Storm through Lutris.
I have a superultrawide 32:9 monitor.
In X11, I can get HotS to scale past its normal limits just like I could in windows and take up a full 5120x1440 resolution.
In Wayland, I can't.
I will die on this hill.
thy gamescope(that run on steam deck) i think it can scale, if yes, so it's an implementation issue, that need to be fixed by the compositor
Color management
Autotype for password managers. I don't only have passwords which I use in my browser for which the plugin is fine. But other apps require autotype. And copy & paste can't be the solution for this missing feature.
I use my laptop for work presentations and running a presentation with embedded videos doesn't work on external displays.
Probably never gonna happen, given how Wayland is designed.
It's never going to happen on Wayland level. It's absolutely no problem to implement this on a compositor level.
load more comments
(1 replies)
I found no Remote Desktop solution to be working well together with wayland. (I’m not quite sure, if wayland was the cause of the issues I had with RDP and VNC, have to test that). The proprietary Remote Desktop all show a warning that wayland is not supported. While TeamViewer does kinda work, despite the warning, it is not a very sable connection.
I've tried this out, and its promising (KDE Plasma RDP Server). https://planet.kde.org/arjen-hiemstra-2023-08-08-remote-desktop-using-the-rdp-protocol-for-plasma-wayland/
load more comments
(1 replies)
load more comments
(1 replies)
i tried rhis autoclicker https://github.com/konkitoman/autoclicker and worked flawless(just needed ticker the suders file because cargo install on .local/bin), but if someone could suggest a macro recorder i appreciate!
For whatever reason it can't seem to suspend my thinkpad. Everything crashes and when I open the lid I have to log in again :/
load more comments
(10 replies)
Maybe this will help people finally make their apps work on Wayland. I hate so much to install a "privacy-friendly" software or even something related to security and discover it only works under X.
So what is the name the new GNOME that supports X11?
Edit: I appreciate the alternative desktops, and they are a great reminder (feel free to keep them coming.)
My point was that open source projects tend to fork every time a less than popular decision is made. Often, removing support for something is seen as a less popular decision. I anticipate GNOME will fork over this. I have no inside knowledge and will not be leading the charge.
KDE, I suppose.
mate?
Until barrier/synergy works on wayland, I've got to stick with X
Input Leap? Now that Barrier is no longer being developed, Input Leap is the main fork, and GNOME 45 just added support for it on Wayland.
load more comments
(2 replies)
For me at least, waynergy doesn't solve my issues, as I host my kb/m on Linux and share with a Windows PC (no builds for windows, and I can't get it to work with barrier for some reason) I ended up just buying a USB switch which works, but it's way slower .. but I love hyprland so it's a net gain I guess
This is the best summary I could come up with:
A set of merge requests were opened that would effectively drop X.Org (X11) session support for the GNOME desktop and once that code is removed making it a Wayland-only desktop environment.
Going along with Fedora 40 looking to disable the GNOME X11 session support (and also making KDE Plasma 6 Wayland-only for Fedora), upstream GNOME is evaluating the prospect of disabling and then removing their X11 session support.
This merge request would remove the X11 session targets within gnome-session: "This is the first step towards deprecating the x11 session, the systemd targets are removed, but the x11 functionality is still there in so you can restore the x11 session by installing the targets in the appropriate place on your own.
That was followed by this merge request that would land later on -- more than likely, one cycle later -- for actually removing the X11 session code.
Some concerns were raised already how this could impact downstream desktops like Budgie and Pantheon that haven't yet fully transitioned over to Wayland.
In any event we'll see where the discussions lead but it's sure looking like 2024 will be the year that GNOME goes Wayland-only.
The original article contains 254 words, the summary contains 193 words. Saved 24%. I'm a bot and I'm open source!
Sounds good!
That's a hard work to try to be compatible with X11 and Wayland.
I hope that could simplify that.
The MacOS of DEs
Any X11 forwarding support or emulation of some kind provided by Wayland? Or will apps detect this over the terminal as they usually currently do and render on the remote machine?
Can't Waypipe do this?
OMG never heard of this, perfect!! Thank you 😁
Guys, am I the only one?
I dont care about X11. But some weird things just dont work.
I have a stupid AMD mobile GPU which seems to neither support virtualization, nor Wine games.
Also, I only had one keyboard/mouse input at a time, so either shift or running for example. People told me thats because of XWayland.
Is that a thing? This would be a total dealbreaker
AFAIK wine requires no special hardware support. It isn’t virtualizing anything, it just translates directx calls into OpenGL/Vulkan calls executed by your normal driver. If wine doesn’t work I suspect it’s something else
load more comments
(1 replies)
Have you enabled virtualisation support in your BIOS/UEFI? Many vendors ship their hardware with this switched off by default (and some hardware actually doesn't support it at all).
I don't have any issues with Xwayland and simultaneous key presses. Tested with Bottles (i. e. WINE), BeamNG (native Linux build) and the games from SCS Software (also Linux-native). I am running Fedora 38 Silverblue with an AMD RX 5500 XT GPU.
load more comments
(1 replies)
view more: next ›