Timeshift forces you to use a very specific layout of btrfs partitions or whatever those are called. On Fedora.for instance, unless you set them up manually, Timeshift will not work. Snapper isn’t so picky.
I never had to set it up. I use endeavour OS and all I did was choose “btrfs” in the installer. That’s it. I just installed timeshift after that and ran it like normal. No issues. Installed auto snap and grub-btrfs and I’m in the races.
this is probably actually the fault of wayland and it’s fragmentation issue. Various wayland compositors have different methods of interacting with them and this includes remote/virtual input. Because of this fragmentation a lot of developers have just started to kinda give up, on wayland.
for this one specifically, I would assume any virtual input would work? there are a couple possible routes forwards, the easiest is probably using XDG’s RemoteDesktop. However not every compositor implements this, Sway will be getting it soon (or already has it using luminous). There are also numerous compositors that don’t support this.
you have wlr-virtual-{pointer,keyboard} which works on sway and mir, and thats it. I believe there was a compositor that could do this over dbus too?
the reality of wayland is, if it’s not in the core protocol, you aren’t guranteed to have support, and if it is in the core protocol, you still arent guranteed to have support, but the chances are better
So, it turns out that my RMM is working fine under Wayland. Level got back with me because they couldn’t reproduce the problem. So I tried to reproduce the problem. Only to find it is working just fine. Whatever was causing that problem, I have no idea. But it’s gone.
interesting, do you know what they were using for input? if they have an encompassing solution that could be great. if they just use xdg remotedesktop, well thats about what I have now anyways T.T
I love Ubuntu so much :3 and I’m very happy that Canonical has worked with Microsoft and Google, Linux is becoming a liked kernel and operating system!! ^u^
Judging by post & history. They are just a troll. As for this article. I don’t understand why anyone bothers sharing it. It is one of the most hot garbage ones I have seen. Most of this article gives arguments that are either old, have no relevance here or are just plainly cherrypicked (the jitsi one for example, open the link and see the last comment, that they quoted). Most things are also application side issue with no relevance for wayland devs. “Oh my app does not work in wayland? Must be wayland’s fault!” This is a rubbish logicless argument. If one wants to not use Wayland, they are welcome. But things like “Boycott Wayland” are irritating to those who do want to use Wayland because they know how Xorg is.
How about an example of Wayland forcing me to use GNOME like this rant alleges? I hate GNOME but have been using KDE with Wayland for like two years now.
Same. Not to mention that there’s window managers in development if people prefer that. Some examples I know include Sway for those who want something like i3, Wayfire for those who miss Compiz and Hyprland for a more polished tiled experience. Hyprland in particular I’d recommend as I’ve personally had no luck with X.org compositors like Picom - didn’t work with my GPU.
The one that bother me the most about Wayland is the future of *BSD desktop. Can you run Wayland on NetBSD/FreeBSD yet? Also, currently you can run x server on Mac so you can run X11 apps remotely for example. Is there any attempt to make waypipe work on MacOS?
It’s been working for a while unless I’m misunderstanding what you mean by screen capture. But I’ve been using OBS on KDE Wayland capturing via portals for months now with issues.
I just tried it. Create a “Screen capture (PipeWire)” source, there’s a popup asking you to pick a display or “Full Workspace” which shares everything.
There really isn’t one. Wayland is maturing and app support is following.
This is the way things always go in open source. I’m betting soon there will be a distro that will announce a never Wayland stance just like Devuan prior.
You seem to use the word censor a lot. For someone who who clearly has no idea what freedom of speech means.
Let me give you a clue. Your freedom of speech in no way forces others to provide you with a platform. Just governments not to silence you. Private citizens running web sites are not governments. So have no obligation to support your ideals.
When private community moderators do not want to deal with the opinions you push. They are not removing anything from you. You are failing to sell your ideals in a way that appeals to the people you are trying to force your ideas upon.
If you want to communicate with no limits. Host your own community on your own instance. And hope you do not piss off enough people to be de federated.
Small communities have a hard time staying up to date. X11 was ported decades ago, when non Linux OSes had more mind share and commercial backing. I doubt anyone could port X11 if that was the new thing mainly developed on Linux today.
Why would i advertise windows if i’m defending x11 you fucking retard. People who spread fud about x11 and blindly advocate for wayland are the ones who want to sabotage linux and make it unusable.
Oh, you’re conservative, that makes sense. You just want the things to stay the way they are. I mean, it’s the opposite of progress, but there are a lot of people like this.
what’s up with this? I see this school of thought bandied around quite a bit recently. wayland… it’s a protocol. do they hate tcp/ip too? can they boycott that instead?
My favorite part is where he admits to being mad without even knowing what Wayland is.
Edit: When I wrote the above, I didn’t really realize what Wayland even was, I just noticed that some distributions (like Fedora) started pushing it onto me and things didn’t work properly there.
Imo, Chris Titus should just stop making Linux content… His windows content is genuinely useful, yet his Linux content boils down to "arch and debian good, ye old packages good, Wayland not ready, snaps/flatpaks/everything else sucks, Gnome bad, gnome bad (again), fedora bad… He’s the literal definition of a gatekeeper.
I remember having to go out of my way to get an Ubuntu machine to connect to WiFi before login for this reason. It felt strange to have to do that at first, but it’s also reassuring that the machine isn’t by default connecting to a wireless network without user input first unless I give it explicit instructions to do so.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.