101–110 of 113 posts
I have not been able to make Wayland+KDE work on Arch with a 3080ti card. Not sure if this fundamentally does not work yet or if I’m missing something.
That did the trick for me. Without that I only got a black screen with the cursor.
I wish Nvidia would work nicely with Sway. I fully understand the Sway developers' dislike of Nvidia considering how hostile Nvidia was for many years. I suppose nowadays Sway should work with Nvidia but you still have to use the `--unsupported-gpu` option and enable kernel modesetting.
I have been using --unsuported-gpu on my laptop with a quadro card in it for years
* Cursor didn't show up at first. I had to use `export WLR_NO_HARDWARE_CURSORS=1`, but the software cursor had some noticeable latency to it.
* Extreme flickering in both Firefox and terminals. I installed wlroots-nvidia [1] but even then the flickering, while improved, was not gone. I manually played with WLR_RENDERER options between gles2 and vulkan but they all had flickering. [2]
In the end I decided that the flickering issue prevents me from using Sway.
Hardware: NVIDIA GeForce RTX 4080 Super
Driver: 550
OS: Arch Linux
As a long time Xorg user, I am finding it very hard to switch to Wayland. I’ve tried twice over the years and each time it only lasted about a day before I got too frustrated and went back to Xorg. The biggest annoyance by far is all the little scripts I’ve created over the years which use `xdotool` magic for sizing, positioning, and minimizing-and-restoring. My other annoyance is Wayland has no `easystroke` like app…
> Easystroke is unmaintained. > But there is a modern replacement, https://github.com/jersou/mouse-actions , which works on both X11 and Wayland https://github.com/thjaeger/easystroke/wiki
As for easystroke being unmaintained, it's a simple utility that does what it says. And it has worked the same way for the last 14 years.
[1] https://github.com/jersou/mouse-actions/issues/15
Is there a good Wayland post-mortem style write-up detailing what went wrong and why it's taken this long and still isn't solid?
But the gist was basically that Walaynd devs built a good core and then decided they wouldn't do any of the integration work between graphics and window managers, etc. The article implied devs had bad experience with the monolithic X and wanted to break most features out to other folks.
Sounds reasonable but resulted in every window manager/desktop having to implement their own integration, with different designs. Which resulted in an inconsistent mess.
Things like screen sharing over Zoom, (which is taken for granted on the Big2 OSs) was impossible for a decade+ until someone else built bridges over gaping ravines of missing/prohibited functionality.
Found this thread that sort of supports the idea: https://news.ycombinator.com/item?id=37349270
Good, it's been long enough for GPU manufacturers to ensure proper Wayland support and with the exception of EOL Nvidia cards (Kepler and older I think), everything mostly works on Wayland. wlroots + Nvidia still has some issues like flickering but AFAIK that's mostly been solved. The issue with popular distro's like Ubuntu defaulting to X11 for certain hardware is it allows companies like Nvidia to de-prioritize Way…
To be honest, I don't think it's going to be the Ubuntu community (or even the whole Linux desktop community) that's going to pressure nvidia to support wayland. We are all but a drop in the nvidia ocean.
I have not been able to make Wayland+KDE work on Arch with a 3080ti card. Not sure if this fundamentally does not work yet or if I’m missing something.
Did you add the nvidia_drm.modeset=1 kernel parameter? https://wiki.archlinux.org/title/NVIDIA#DRM_kernel_mode_sett... That did the trick for me. Without that I only got a black screen with the cursor.
I can get into the plasma session, but it's basically unusable
Earlier quoted context omitted.
I had a nightmare trying to get a 4 x 4k monitor setup using Xorg. When I switched to Wayland, basically all my problems were solved and it worked out of the box. The Xorg multiple monitor support is really bad and barely works if you are trying to do anything complex with it. If that's not a problem you have then great! But most people today are using multiple monitors.
> If that's not a problem you have then great! But most people today are using multiple monitors. Just out of curiosity, what was complex about your quad 4k monitor configuration? As a lark, I've used xrandr to do all sorts of weird stuff and it has handled it just fine. I've been using multiple monitors with xorg for fifteen, twenty years. (For quite a while, I used three monitors, but now I just have two.) Until XR…
I had a similar problem to what the sibling comment mentioned - scaling was causing me performance issues. I disabled the laptop monitor and just ran multiple screens of the same resolution, and need about 150 % scaling to have text visible on these 4 X 32 inch 4 K monitors, but it was causing a huge amount of lag in xorg. It was solved by switching to Wayland which reduced the lag completely, and also let me run fractional scaling (I think I use 135 %) which wasn't available in xorg. I spent a lot of time with combinations of drivers and inputs and docks and scaling and couldn't get xorg to work. The laptop is a dell precision 3580 with a 4 GB NVIDIA gpu so a pretty standard piece of hardware
Earlier quoted context omitted.
Did you try restarting GNOME (alt+f2, r in the prompt. doesn't close applications) when you had that alt-tab bug? One of the things that keeps me on x11 is gnome bugging out after running for a few days which restarting fixes, but gnome under wayland can't be restarted like that without logging out.
I think I tried and that didn’t fix the Alt+Tab problem for me. The daunting thing about it was that I don’t even know where to begin to track down the cause, and it’s hard to file a bug report because it’s a heisenbug that takes weeks for me to come up. Does Gnome give you similar bugs on Wayland too?
Good, it's been long enough for GPU manufacturers to ensure proper Wayland support and with the exception of EOL Nvidia cards (Kepler and older I think), everything mostly works on Wayland. wlroots + Nvidia still has some issues like flickering but AFAIK that's mostly been solved. The issue with popular distro's like Ubuntu defaulting to X11 for certain hardware is it allows companies like Nvidia to de-prioritize Way…
To be honest, I don't think it's going to be the Ubuntu community (or even the whole Linux desktop community) that's going to pressure nvidia to support wayland. We are all but a drop in the nvidia ocean.
Earlier quoted context omitted.
> If that's not a problem you have then great! But most people today are using multiple monitors. Just out of curiosity, what was complex about your quad 4k monitor configuration? As a lark, I've used xrandr to do all sorts of weird stuff and it has handled it just fine. I've been using multiple monitors with xorg for fifteen, twenty years. (For quite a while, I used three monitors, but now I just have two.) Until XR…
The problem with xorg is per monitor scaling. If your laptop is 4k and you want 2x scaling and your external monitor is a 32" 4k monitor that doesn't need scaling (or 1.25x) then you're basically shit out of luck with Xorg. I think it's on the verge of being impossible to be honest. If you don't need any scaling then yeah, xrandr is fine. I ran 4 24" monitors, 2 horizontal and 2 vertical and xrandar handles it just f…
> I think it's on the verge of being impossible to be honest.
You sure about that? QT seems to handle per-monitor scaling fine (at least with 'kwin'), so it doesn't seem to be at all a problem with xorg. Read on:
QT has environment variables that let you set per-monitor scaling... even fractional scaling. See: https://doc.qt.io/qt-5/highdpi.html#high-dpi-support-in-qt>
On my system, I have two monitors, DisplayPort-0 (a 32" 4k) and DisplayPort-1 (a 24" 1200p). I also have Dolphin installed, and it has a "Desktop" item in its sidebar that has a "minimal" square-cornered icon. When I run:
QT_SCREEN_SCALE_FACTORS='DisplayPort-0=2.73;DisplayPort-1=1' dolphin &
QT_SCREEN_SCALE_FACTORS='DisplayPort-0=2.60;DisplayPort-1=1' dolphin &
And, when I move Dolphin to the DisplayPort-1 monitor, once more than half of the window is on DP-1, the icons shrink to 16x16, and scale back up when I move back to DP-0.
Now, for some reason neither 'QT_ENABLE_HIGHDPI_SCALING' nor 'QT_AUTO_SCREEN_SCALE_FACTOR' seem to do anything at all. Given that xrandr knows the physical size of each monitor, and how many pixels each is configured to output, my expectation is that they simply never wired this up when running on xorg. I wonder if they're accepting patches.
EDIT: I also wonder if the reason they never wired this up when running with xorg is because nVidia's scaling performance is absolute dogshit, and they (somewhat reasonably) really want to have this autoscaling stuff on by default.