Install Gentoo
And then there’s the installation options that look and behave exactly like a regularly themed Qt application (which it probably is). Wonderful!
Okay, I’m coming from Gentoo and Debian, cut me some slack, I’m easy to please regarding installers :-P
Maybe you should actually have read OP’s post.
Unfortunately this is not a time lapse of random developers in pajamas sitting in front of their computers, typing in text, googling stuff on StackOverflow, occasionally scratching their heads and occasionally shouting “fucking Akonadi!!!”.
Very disappointed!
/s in case it wasn’t obvious
Or issue a DMCA takedown if they violate OP’s copyright. Much cheaper, much faster.
But very much illegal if OP’s copyrights aren’t being violated.
Gentoo.
Everything just works and I can configure everything the way I want.
In the vast overwhelming amount of cases tooltips show additional information that you cannot see from clicking on something or provide an explanation to an option that isn’t available without scrounging through a manual. None of those apply here.
In current versions of Firefox you hover your mouse over a non-active tab […] to see (after a small delay) a tooltip containing the web page title.
Uh… what is the point of that? If I am looking for a specific tab then:
This sounds like a “cool” feature that’s looking for an actual problem to solve.
dpkg-reconfigure sysvinit
I don’t remember what I was trying to achieve, but it was a bad idea. I also didn’t (and still don’t) know how to fix the outcome of this, so - since my home was on a separate partition anyway - I just reinstalled Debian since that was much quicker anyway.
A crash in the window manager takes down all running applications: Yes, because the compositor IS the server, window manager AND compositor at the same time.
Maybe not anymore in the future: https://blog.davidedmundson.co.uk/blog/qt6_wayland_robustness/
Wayland is biased towards Linux and breaks BSD
FreeBSD already has working Wayland compositors by the way.
X11 and Wayland are just protocols. These protocols are used to abstract the window drawing from the actual hardware and runtime environment as much as reasonably possible - because nobody wants to maintain 3215 versions of their app for different runtime environments. So in order to be shown on the screen an app needs to implement either the X11 or the Wayland protocol (or both!).
The piece of software that is on the other side depends on whether the app is using X11 or Wayland. For the sake of simplicity let’s assume that the app does only support one of those. If the app supports Wayland then it will try to connect to a Wayland compositor. The compositor implements every part of the protocol and makes sure that the window is rendered on the screen and that user input is forwarded to the app. If the app supports X11 then it will try to connect to a X server and take the role of an X client. This is (on Linux, essentially) always X.org*. X.org also implements every part of the protocol and makes sure that the window is rendered on the screen and that user input is forwarded to the app.
* Unless you’re running a Wayland compositor, then it will connect to XWayland which passes through the window to your compositor.
Wayland compositors have full control over the apps while the abilities of apps are purposefully restricted.
A window manager is just another regular, boring, old X client connecting to the X server. It doesn’t actually abstract anything. It can move windows because the X11 protocol allows it to, but any other X client could just as well move all other windows around, read all user input to all other windows and even move the mouse around as it pleases.
So, to be specific, there is no mouse pointer bug in Virtualbox while using Wayland. There is a mouse pointer bug affecting specific Wayland compositors, likely because they enforce GPU hardware acceleration that is lacking in either your VM or the Linux kernel because of missing drivers. Try using a different compositor, (re)installing Virtualbox Guest Additions with the correct version on the guest system and/or check whether hardware acceleration is enabled for the VM and has enough video memory.
On Steam the system requirements are very clear about this: “SSD Required”.
It’s probably impossible to list all the possible differences, but do you know what are the most common ones?
The ones that I mentioned regarding direct hardware access of any sort.
I’ll answer what I can in good conscience.
Is that a good idea?
If you keep in mind that it won’t 100 % behave like a “proper” installation when things go weird it’s fine.
Do different distributions work better or worse on VMs?
VirtualBox comes with some pre-made profile for some distributions but I’ve never been able to tell what those actually do, other than by default selecting virtual hardware that is supported.
Are there any major differences when using linux in a VM compared to a bare metal installation?
VM “hardware” is well supported, but anything requiring proper hardware acceleration (of any kind) will either perform terribly or fall back to a software-based backend. I.e. desktop compositing or hardware video decoding may or may not work as well as a native installation. Video games likely won’t work in a usable way at all, unless it’s Solitaire. Also the hard disks are decoupled from the VM to the host system and you need to manually forward USB devices to the VM or the system might not be able to detect them.
Is there any [dis]advantage to “Linux VM on Windows” VS “Windows VM on Linux”?
That entirely depends on what you want to use both systems for. If you already have Windows installed then I’d like to suggest the following path:
$PROGRAM is written by GNOME/KDE/LXQT/… people that doesn’t mean that it won’t run perfectly fine on other desktops. Also: distributions may not ship all software, don’t forget to check Flatpak/Flathub if your distribution is missing some software.If it turns out that there’s just too much Windows-only software that you can’t part with then you can just delete the VM and that’s it. On the flip side you can find software that may just happen to be better than what you used previously. Also trying out various distributions is much, much easier this way - installing the tenth distribution on bare metal because you weren’t happy with the previous nine isn’t particularly fun.
That means every time a new Kernel version is installed, the Nvidia driver DKMS has to be installed too. And that is basically the slowest part.
ZFS users: “First time?”
What settings app? hp-toolbox is the program to use (which might in your applications menu as “HP Device Manager”), alternatively hp-setup to set it up from the CLI.
Have you installed the plugin within hplip, or rather, the hplip-GUI program? Have you removed the old printer from CUPS before trying?
You’re supposed to use hplip for HP printers. There’s a Debian package for it in the main repositories.
edit: You can look up the printers and supported features with hplip here. Looks like your printer is perfectly supported (as long as you let hplip’s tray program install their proprietary driver plugin).
I use a Rode NT1 with a Focusrite Scarlett 4i4 3rd (!) gen. It’s not quite “just works”, you need to set up parameters for the USB sound kernel module to get the Scarlett working. Otherwise it “just works”.
Be careful with Focusrite products in general and read the Linux kernel project’s instructions very carefully on supported products, in case you’re interested in such a device (e.g. it’s common that 3rd gen works, 2nd or earlier doesn’t).
This should work on Jolla’s Sailfish OS phones as they’re running a legit Android in a sandbox. Unfortunately their hardware support is pretty abysmal if you want all features working - and since it’s legit Android it’s also not free (monetary) and Sailfish OS’s UI toolkit is also not free (freedom).
edit: also, last time I checked, Bluetooth support for Android apps is terrible, basically only audio work(s|ed).