While transition to Thumbleweed can go smooth if you are lucky enugh, switch from Thumbleweed to Slowroll can be problematic. It will envolve downgrading packages that is usually not tested at all. Better switch from Leap to Slowroll directly.
Unfortunately you can’t make an Ubuntu system into an Arch based one. Both of these use totally different package managers, but I’ve heard about a distro which lets you use apt (ubuntu, debian), dnf (fedora), pacman (arch) package managers in one place, but haven’t checked it out.
Try out an encrypted desktop on a VM if you can. Apparently you will need to remember 1 additional password whenever you wish to use that encrypted storage, but it’s totally valid if you need an encryption.
Creating a DE by yourself sounds like a madman task (especially if it’s not based on an extising one) but I’m rooting for you! You can also help an existing DE on their respected repository.
thank you so much!! And oh well, I will stay with Ubuntu, I love it, and by the way yes I will develop the desktop environment myself, but it will be developed using only HTML and CSS!! It can be a different type of DE.
I avoid it at all costs as no solution is really seamless, but NoMachine gave me the best (perceived) latency out of VNC, TeamViewer, and a couple others I tried a couple years ago. It’s also cross platform, but if the machines are in different networks (behind a NAT), you’ll likely need to configure port forwarding manually or via their GUI.
edit: I just remembered I even played youtube videos and the transport fever 2 game via NX (NoMachine) for a few hours and it worked well, while other protocols had either too much of a degraded quality or latency.
How intensive is nomachine? I’ve used it on decent hardware and it’s performance was pretty good. But I’m thinking of setting it up on the raspbery pis at work since VNC is painful to use.
I’ve used it on my pi before I disabled the display manager because I barely used it, but performance was fine. I could log in from my desktop, phone, laptop, another pi, anything really, which was nice to have.
I use NoMachine as well as it has been the most responsive solution for me.
My biggest problem that I finally figured out was that NoMachine was attaching to a VNC console instead of creating its own display when I was using it with Unraid VMs (KVM)
if you are on a trusted network (i.e. local/vpn only) you could give VNC a try. It’s somewhat simple, but far from secure.
the gnome desktop environment should offer built in RDP support, but i have not tried it yet. Also, just like VNC, i wouldn’t use RDP over the open internet.
I’ve been using Rust Desk for a few months now and it’s awesome. Works on Linux, Windows, Mac, iOS, and Android.
It’s open source and super easy to setup and configure. For limited use cases, you can just use their freely provided servers, but you can also host your own server if you want.
I’ve been really impressed with the connection speeds and features, it has everything I need including end-to-end encryption for all network traffic, so your remote connection is at far less risk of getting snooped.
I was looking into rust desk. It looked like the perfect solution for remotly helping my family members. The problem is I have them running silverblue. I don’t think rust desk supports Wayland. There is a experimental way I was going to try, but I’m not sure how to install it since its not in Fedora repo or flatpak.
Just a data point: OP is looking for a desktop solution, and Rust Desk may be fine for that; I was pretty impressed with it. However, I caution about using it to share out on Android. I traced down random crashes and reboots into safe mode to Rust Desk running on a Pixel. It took me a while to figure out which app was causing it; it seemed to have no correlation to use, time, or anything else I could discern. They only went away after I completely uninstalled Rust Desk (which is why it took so long; I couldn’t correlate it to running Rust Desk, so I didn’t suspect it).
The reboots into safe mode turned me off to it on mobile - I had no issues at all running the desktop client on Linux. Android aside, it’s a really nice bit of work, and I fancy even nicer than VNC, which for me is saying a lot.
That said, on a fast network, I still prefer a good old X client over ssh to VNC, if for no other reason than easier per-app windows - but I like the L&F and performance of X on a fast pipe.
Good to know since I’m using a pixel as well. For remoting to my own devices. Since they are all running Wayland now. I plan to try out waypipe soon. I read it’s like a replacement for running X over ssh.
For helping family members I was looking for something more user friendly. Which is why I was looking into rust desk.
Well, don’t let me put you off of it; Rust Desk is pretty nice, and user friendly. Just… keep any eye on it if you run it on your phone. Maybe you won’t have any problems, but if you start noticing reboots, you’ll have an idea of why.
Nyfure is right. Wayland support is experimental but has been added to Rust Desk since earlier this year.
I haven’t tested it on Wayland myself, and remote login isn’t yet supported according to their GitHub documentation, but if you just need a reliable way to provide remote support to your fam, it’s a really solid option.
Wayland is quickly becoming the standard, and Rust Desk seems to be on that train which is good. I wouldn’t be surprised to see full Wayland support or close to it by the end of next year.
Also, I just use the .appimage file and it works fine for me. Just make sure to set it as executable with chmod +x or in the file permissions tab in your GUI.
Oh! I didn’t see that app image was an option. I’m definitely going to give it a try now. For my use case I don’t need remote login so that works out fine. Thanks.
This. You can also directly connect via IP address when enabled on the target, very handy.
Its probably also one of the few which have started developing Wayland support on the host side.
Currently only clipboard and video sharing works, mouse and keyboard are close..
wayland is very restrictive and things like full keyboard/mouse reading/writing need special handling (and afaik a mouse write method wasnt really available from user permissions so far)
Use Grub2Win (sourceforge.net/projects/grub2win/) whenever Windows manages to break dual booting. It’ll stop fucking up afterwards, as it’ll be installed within one of the windows boot partitions.
These are exploited by malicious processes doing something to the hardware which may result in information about your process(es) being leaked. Now, if this is on your computer, then the chances of encountering a malicious process that exploits this hardware bug would be low.
However, when you move this scenario to the cloud, things become more possible. Your vm/container is being scheduled on CPUs that may/may not be shared by other containers. All it would take is for a malicious guest VM to be scheduled on the same core/CPU as you and try exploiting the same hardware you’re sharing.
I don’t get the issue with “maintaining Xorg”. Like, I get that it has a “cost”, I just don’t understand why that cost would be an issue since it’s basically fixed, marginal cost (and has been since like 2015): the software is already mature, so it’s unlikely to see relevant changes, or even minor changes (if that’s what we want to mean with “dead”). That means, it can be affixed to a specific toolkit and environment to build (if this isn’t being done already - which any mature project like RedHat should be!) basically guaranteeing it’ll build forever. You can just set a virtual button or a yearly crontab to do it. Fixed, marginal cost.
Contrasted to that, what Wayland is doing is kinda a representation of the worst ways of capitalism: centralize the profits, socialize the costs and the externalities (redesign, recode, rebuild), and blame society (the Linux communities) for it, all for a variable cost that is unbounded in time and space because you never know what’s gonna cost a small project like a text editor to reimplement the entire desktop stack “just” for Wayland.
I think he explains it pretty well, he even gives some examples and mentions there are many others. For a company to support such a large component for its commercial customers has a lot of work and verification we wouldn't consider as end users. His comment also explains why you can't just maintain a status quo with it and make an automatic build and forget...
As a third party, my understanding is that both the implementation and the protocol are really hard, if not next to impossible to iterate on. Modern hardware doesn’t work like how it did when X did, and X assumes a lot of things that made sense in the 90s that don’t now. Despite that, we cram a square peg into the round hole and it mostly works - and as the peg becomes a worse shape we just cram it harder. At this point no one wants to keep working on X.
And I know your point is that it works and we don’t need too, but we do need too. New hardware needs to support X - at least the asahi guys found bugs in the X implementation that only exists on their hardware and no one who wants to fix them. Wayland and X are vastly different, because X doesn’t make sense in the modern day. It breaks things, and a lot of old assumptions aren’t true. That sucks, especially for app devs that rely on those assumptions. But keeping around X isn’t the solution - iterating on Wayland is. Adding protocols to different parts of the stack with proper permission models, moving different pieces of X to different parts of the stack, etc. are a long term viable strategy. Even if it is painful.
But keeping around X isn’t the solution - iterating on Wayland is. Adding protocols to different parts of the stack with proper permission models, moving different pieces of X to different parts of the stack, etc. are a long term viable strategy. Even if it is painful.
The problem is, that’s always used as an excuse to force people to be gratis beta testers. I’ve been around for the wrecks that were (and still are) Pulseaudio and Systemd. Wayland is even worse: it doesn’t even fully start a session in my machine. If as devs you want to “iterate”, sure, go ahead; but leave it in the dev branch; as a user, don’t try to sell me Wayland again until it’s actually over.
The problem is, that’s always used as an excuse to force people to be gratis beta testers
If as devs you want to “iterate”, sure, go ahead; but leave it in the dev branch; as a user, don’t try to sell me Wayland again until it’s actually over.
it’s opensource software, don’t like it? go ahead, don’t use it. They don’t owe anyone shit
Why is the unity is underrated when its what i use
Everyone is going on about the lack of punctuation; I can’t get over this snippet. It’s like the ideal of an ego wrote this.
If you’d like to know my experience with Unity DE, I thought it felt like a toy and when it was packaged with Ubuntu, it was the first time I left vanilla Ubuntu since the days of Gutsy Gibbon.
I’m glad to hear Unity getting love. The customizability is by far linux’s key strength. So it can give people what they want. For example, it gives me the ability to completely ignore Unity.
linux
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.