I recommend unplugging all disks with important data beforehand. Piece of mind about not being able to wipe all data (and having to restore from your backup) is great. Having used fdisk or parted is a good experience to have in case it’s actually needed on some server.
I don’t really have much of an opinion about Wayland but it’s still funny to me whenever somebody using Wayland shits on X11 and then tries to share their screen on Zoom or something. If Wayland ends up being great I’ll be happy, but for now X11 just kind of works, so I don’t understand why people are so eager to switch? This isn’t to say I don’t understand the desire to build something better and more secure than X11, I’m just not sure what the end user gets out of Wayland right now. I don’t have VRR monitors and stuff, though, so maybe I’m not running into problems I would be if I wanted fancier features. Plus, I use xmonad and some other stuff right now that won’t work on Wayland, so I don’t have much incentive to try it. Hopefully everything gets Wayland updates eventually.
With those however, they never ran on Linux. This situation is different because it did run. I’ve only used Zoom once, so no clue if it worked excellently or if it was “meh”, but it sounds like it did the job before.
Regardless, it doesn’t matter if Zoom hasn’t updated their Electron to account for the Wayland changes - all people will see is that it doesn’t (or did, but no longer) works on Linux and will blame Linux instead.
Which, that is fine if we want Linux to always be a hobbyist operating system. However if we want Linux to be more accessible to people then unfortunately the ball is in our court to try to not break something as simple (or rather, what most regular users would define as simple) as this.
Isn’t screen sharing working since some time? Works even on WebEx from Firefox, can pick any window to share. Granted a few years back it didn’t work, but now it does. Maybe it’s a zoom bug… 🤔
Probably, but my exposure to Wayland has just been people complaining about how much X11 sucks and then proceeding to have more problems than everybody else.
No,I just had to deal with this myself. Most you can do is share your entire desktop in Wayland, and it’s shaky. For the first time, I had to switch to Xorg and bingo, zoom works. Fonts are actually antialiased and kerned properly for certain applications that weren’t… Really surprising.
Again, none of that is a failure of Wayland, it’s a failure of Zoom to run on Wayland. One day, and this is in the next 5 years, Wayland-only apps will refuse to run on X.Org and the situation will be reversed.
You can share screen perfectly fine under Wayland. Many apps use it fine, and even in case of Discord if you use it with a browser it’s doable.
No Wayland dev can fix an issue that originates from lack of app support. There has been many Wayland issues through the years and trust me, I know, but how do you expect them to fix Zoom? Acquire the company and take it behind the shed?
how do you expect them to fix Zoom? Acquire the company and take it behind the shed?
I mean, you could - for example - implement the interface these apps expect to exist and use with your amazing new compositor™.
This is precisely why companies just say “fuck Linux users” - instead of supporting a single operating system where everything kinda “just works” across versions for decades you have to checks notes support 20 different compositors across 2 vastly different display servers and dozens of various desktop environments and such… All for an OS that’s used by maybe 3% of your users if you’re lucky.
The interface exists. It’s up to zoom to support it. Why are you under the impression there is a technical issue? THERE IS NONE.
It’s up to Zoom to support the aforementioned interface.
Wayland’s display handling in this manner is for security, the user will be shown a permission request dialogue to let the app access the screen only if you permit it, it’s also disallowed from accessing anything except what you’ve given it permission to. This is not even a new concept, just not doable under X.
It’s also possible to create the lawless model of X under Wayland through a protocol if you desire to make one, but it makes little sense to throw away this better model just for the sake of some shitty proprietary apps who don’t care for Linux anyways
I dunno, I don’t trust a guides still recommending flake-utils. You can make the same four loop in like 4 lines of Nix which is a smaller diff & doesn’t pollute your downstream consumers with a useless dependency. Flakes also don’t eliminate pointless builds, fileset or filtering the src can & the only tool with file tracking on by default is the Git VCS specifically (which also involves the intent to add flags which is the other side of annoying).
I sometimes write a flake with those 4 lines of Nix code, and it comes out just messy enough that tbh I’m happier adding an input to handle that. But I recently learned that the nixpkgs flake exports the lib.* helpers through nixpkgs.lib (as opposed to nixpkgs.legacyPackages.${system}.lib) so you can call helpers before specifying a system. And nixpkgs.lib.genAttrs is kinda close enough to flake-utils.lib.eachSystem that it might make a better solution.
Saving the dependency is pretty big since each flake you import will bring along its jungle of dependencies now in your downstream project. I can’t think of a use case where < 10 lines is worth a dependency—especially since as you noted, lib has the glue right there for you to put it all together.
Yes and I do and while it is great for infrastructure, magnitudes better than anything Microsoft ever offered as a reasonable desktop it’s a fucking a joke.
There are surely native totp apps for this on Linux and I haven’t used Ubuntu in a million years but if you really want to do specifically this maybe waydroid.
The guy’s language is the exact same hand wavey magic he opened up criticizing. “Appeal to my claimed authority. Wayland bad. Missing parts. Analogous to poop.”
I practically never come across anyone who addresses a point directly and don’t think I ever will. Everything is tribalism and politics and sunken cost fallacies.
I’ve been enjoying ubuntu on my surface go 2. You can pick one up used for less than $200. Go for an 8gb model. Everything worked for me except the webcam.
It’s usually pretty easy to find secondhand Microsoft Surface devices for that price point (check craigslist, FB marketplace, and the like), and they absolutely rock when using a Gnome-based distro (like Fedora).
I just installed Fedora with KDE plasma and Wayland last weekend using the surface kernel. Was pretty painless, after abandoning a couple other distros that did not play nice.
The instructions on the GitHub are also very good, though obviously every years surface has its challenges I’m sure.
Just make sure about what you’re getting yourself into: features such as IR facial detection and stylus input isn’t supported on all models OOTB by the surface kernel. Also, it is a bit messy with how surface handles booting.
Linux on surface works (I got Ubuntu on both my Go gen 1 and pro 7) but expect to put in time to tinker and manage unexpected issues.
I own all the pinephones and as much as I’ll go to bat and speak well if them… The tab support is super early. Lots of stuff doesnt work (wifi for one). That’s not to say that won’t change with time as the pinephone pro did
linux
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.