Earlier quoted context omitted.
Only Nvidia use proprietary graphics drivers?
vmxgfx has similar issues.
If you are using VMWare then the proprietary video driver is probably the least of your issues.
GNOME 50 completes the migration to Wayland, dropping X11 backend code
81–90 of 190 posts
Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code
#82Earlier quoted context omitted.
I don't think I understand what you mean. Do you mean wayland is not usable with nvidia proprietary driver? I remember that being annoying but possible many year ago (with sway --my-next-gpu-wont-be-nvidia thingy). But if you use really old nvidia gpu you can have a mixed experience with wayland. Which is a fair problem to complain, but you can't blame that on wayland and call that lack of freedom. That problem was c…
The “what’s the harm” here is the systemd conversation all over again basically. If you pipe everything through a single point of failure black box users have already lost, when you combine it binary blob drivers that shouldn’t exist it’s worse. Linux is doomed in achieving its most important goals which are user freedom, not someone’s idea of pretty UI imposed at the expense of that. If that’s what users want they s…
I don't understand how proprietary drivers with Wayland are supposed to be a bigger problem than proprietary drivers with X11, could you explain?
Personally, I've never used a proprietary driver with either.
Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code
#83X11 is not going anywhere. If anything it's Gnome adding another nail to its coffin
X11 desktop environments are dying, but it doesn't mean that X11 is dead. XWayland is still a thing so you can still run your X11 apps on Gnome. The big reason why I want to keep X11 besides backwards compatibility is the ability to run GUI apps remotely, even from a server that has zero graphical capabilities. But these do not really apply to desktop environments. If you want to remote a full desktop rather than ind…
I think waypipe should generally do what you want, though TBH so far when I need to run a remote GUI app, I just have them display to XWayland out of habit.
Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code
#84Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code
#85Blocked in my location. Did a quick search only to find that it's blocked in many other locations - https://news.ycombinator.com/item?id=35314374
Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code
#86What a strange title. X11 is still more popular than Gnome, and formulating a wish like a fact doesn't make it so.
Do you have a source for that statistic?
Stats from Debian and Archlinux. i can't tell how reliable they are.
https://qa.debian.org/popcon-graph.php?packages=x11-common+g...
https://pkgstats.archlinux.de/compare/packages#packages=gnom...
Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code
#87Earlier quoted context omitted.
I don't think it's true that anything is architecturally or fundamentally broken in Wayland (though if you disagree, I'm very curious what you think is so deeply broken). Most of the issues and slow adoption were because the core protocol was deliberately kept extremely minimal, and agreeing on all the needed extensions took a long time. Don't take it from me, but rather from KDE developer Nate Graham: https://pointi…
Window positioning is one that on its own is sufficient to make me ignore Wayland, as it means that without my own compositor with my own extension, I can't get a file manager that will behave how I want it. Most people won't care, but for a number of us Wayland is stubbornly refusing to support functionality we see as dealbreakers.
That's fair! I believe that window positioning also works on XWayland, though, so running your file manager that way should still work with the rest of the system being Wayland (and Gnome has no plans to drop XWayland afaik).
I believe the main holdup is a desire for Wayland to be usable with e.g. VR interfaces where there is no simple 2d grid.
Out of curiosity, how do you want the file manager to behave? And did you write your own or are you using an existing one that works that way?
Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code
#88Earlier quoted context omitted.
x11 being in maintenance mode is the best thing that happened to it for my use case. It hasn't crashed in 15 years.
It would be sad if, after all those years, it was still missing anything significant. Maintenance mode sounds like a good thing, not something that makes me tempted to switch to some less stable alternative.
and one without the features I use. ssh -X is a must.
Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code
#89Earlier quoted context omitted.
It's not explicit from the link, but does it allow the headless login to be resumed from console and vice versa? I tried some solutions in the past but they did not support that, which is a deal breaker.
There are no headless sessions on Wayland. At all. You want proper headless session, set up X11 distro and use xrdp - it's really easy. But on wayland "remote support" to something that is already displayed on screen is all you can get now.
What I want is to be able to start a session remotely after a reboot, and continue that same session when I get back home. And conversely start a session while at my desk at home and resume that same session remotely. Without any weird limitations.
In other words, how RDP works on Windows.
So you're saying that is still not possible I take it.