I first heard of it in the early 2000s, with my dad talking about replacing our buggy Windows ME with Lindows. Eventually, that computer died without us ever attempting to install it.
In college, I hung out with someone who used linux and thought it looked cool. I successfully dual booted Ubuntu on my PC around 2005 or 2006, but could never get the video drivers working properly (it was stuck at the lowest resolution) and eventually gave up on it.
I started adminning a web forum around 2014 or so, and the previous admin talked me into dual booting Fedora rather than only using Putty. So I started using it intermittently whenever I started working on the forum, though I never really got into GNOME. He also told me about raspberry pis, so I picked up a pi 2 and started tinkering with it.
When my wife moved in (2018), she (a software developer) was working on a project and asked me if I’d heard of raspberry pis, as she was recommended to use one but hadn’t looked into it yet. I pulled my pi 2 out of storage and she fell in love with it, so we started buying loads of pi 3s and zeroes, with me testing out different distros and setups for her while she was working on the project code.
Finally, somewhere around 2018 or 2019 my laptop started running like shit on Windows. I tried out Xubuntu and fell in love with it. It ended up becoming our go-to distro, getting slapped on old desktops she brought home from work and a used laptop I bought for our daughter. So that became the daily driver on my laptop, even as she moved onto Alpine with i3wm.
And now we both have Pinetab 2s, so I think it’s fair to say we’re full on linux nerds at this point. We still have Windows on some of our desktops, though, so we’re more pragmatists than linux proselytizers.
TL;DR: I heard about it young, and that interest grew into dabbling, until I finally got addicted to it.
Nope. However, UnityX, a prototype desktop environment (which will be available as a variant of Unity once ready), will include Wayland support.
I realize the name was likely chosen for completely unrelated reasons, but I can’t stop laughing about UnityX being the only variant of Unity with Wayland support.
I’ll parrot the others. I have a Windows PC issued by my employer. The only way to have some Linux is WSL. I use it to sync notes with server at home, python stuff, and w3m when I want to Google something without looking conspicuous in the office.
General Linux tools also help. I needed to make video half the speed - one liner ffmpeg solves it in a jiffy. On Windows I need to install some hive software.
WSL in Windows Terminal is not much different from opening Konsole on any regular desktop Linux distribution. I use openSUSE Tumbleweed on WSL and I think it’s great.
I think qcow2 images are always a fixed size (but I could be wrong on that) however I saw some threads explaining how you could relatively easy modify the size of the qcow2 image :)
As long as the laptop boots, you should be able to switch to a TTY console, where you have a complete shell interface to your system after logging in (in said TTY console). So, being greeted with a login screen or something is a win here - but you’re very vague in your report.
The GUI is only just a program and has nothing to do with your boot options in BIOS or bootloader (like grub).
Using CTRL-ALT-[F1-9/0] you can switch between your virtual consoles and on only one of them your GUI is running.
You can use any other one to change anything on the system from CLI.
You should also be able to stop the current GUI/X11 Session and directly start the window manager you wish - temporarily to fix your system, if you’re not confident in the CLI.
I haven’t done this in years but I’ve always found open source solutions to this to be quite clunky and usually barely worked. What always just worked fine for me was Teamviewer. Yeah it’s proprietary and has crappy licensing but it’s mostly a smooth ride.
Do try the open source options first tho, it’s quite possible they got way better in the last few years since I’ve done this.
I noticed in the install.sh of GSR, that setcap cap_sys_admin+ep is called on the executable. So if you know any way of replicating something like that for flatpaks that is simpler than installing GSR manually, feel free to let me know.
You can just run the same command on the executable installed by flatpak. On my system it can be found in /var/lib/flatpak/app/{app name}/current/active/files/bin.
I didn’t consider that an option because whenever I searched for setcap and flatpak, most threads were pretty dismissive and told OP that flatpak is made with security in mind so doing that isn’t supported.
Regardless, I tried it just now, but the password prompt (image below) still shows up when launching the autostart .desktop file I created. The .desktop file launches a script I wrote, which in turn actually starts GSR through flatpak, in case that changes anything.
Do I assume correctly that this prompt might be gone if I set the capabilities of /usr/bin/flatpak? It’s not something I want to do, so I’ll probably keep trying to get the manually built version installed.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.