There should be a setting in BIOS for sleep state that lets you choose between “Windows sleep” and “Linux sleep”. I know I have to set that to “Linux sleep” on my P14s gen 2 AMD or it wakes up immediately after going to sleep. Updating BIOS and the other firmwares might help too.
However I have a gen 7 from work running Windows that often fails to wake up from sleep or hibernation, and I have to resort to poking the reset button to get it to respond. Coworkers report similar troubles so I think it may be a cursed model.
That said, I’m running OpenSuSE Tumbleweed KDE on my P14s and an X1 gen 5. Everything works smooth out if the box on both machines except for the fingerprint sensor on the gen 5 which doesn’t have mainline fprintd support in any distro.
Oh wow, I hadn’t ever noticed that when poking around in the BIOS, I’ll have to find that setting, and cross my fingers I didn’t buy a cursed model laptop.
Isn’t that kind of AppImage’s whole thing, to behave like Mac apps that you just double click on regardless of where they are, and not have a package manager?
I’d go for the Flatpak if you want it to be managed and updated.
We went from distro packages to Flatpak to bare files and circling back to reinventing the package manager…
Sometimes in enterprise environments you’re not allowed to have a proper Linux and you’re forced even as dev to use that thing from ms.
Since hardly any code in the web runs on NT, the wsl is the only way getting your things done. It does what it does OK(ish) but except of that single usecase I would never use it.
As a Nix fanboy I would write a Nix expression that downloads the AppImage, and also writes the desktop file with the appropriate path written into it via string interpolation. That can be done either through a NixOS configuration, or in any Linux distro using Home Manager.
I am a big fan or repackaging Appimages as Flatpaks, with appstream metadata, sane package management (not the windows way or simply nothing at all), sandboxing and desktop entries.
I find your mileage is somewhat dependent on the rest of the system config and how you access it. I kinda hate how WSL2 is based on hyper-V because the network stack for that is a pain in my ass, but tools like NMAP just don’t work on WSL1.
I have found that using something like MobaXterm is pretty awesome. The built-in X-Server lets me run a few useful graphical tools within WSL (GIMP, Wireshark, etc) without needing to install their windows counterparts.
My Linux knowledge isn’t what it used to be, but I believe you can easily make a thumb drive with a bootable distro. I would recommend taking whatever you choose for a test drive before you wipe a working system. That way you can see if there’s any weird stuff that doesn’t want to work.
Before I made the switch, I did something similar to what you did. To enumerate my steps: 1 - Learned about Linux in general(I learn a lot at university) 2 - Picked a distro 3 - Adapted to the Linux workflow in Windows, for example using more terminal, updating packages via winget/chocolatey, using wsl etc. 4 - Used FOSS alternatives in Windows 5 - Made a list of all the programs I needed to find a replacement for that don’t have a Windows version to try out 6 - Made a list of things to try out, like themes, tiling windows, desktops, etc 7 - Live distro for a day 8 - Completely removed Windows from my life forever
Thanks for the list! Most points i already did and there are only two programs that not have an alternative, but i almost never use them. I will try to run them through Wine or something, and if it doesn’t work it would not be a big deal. Can’t wait to get rid of windows. I can’t remember why i left kubuntu behind and got back to windows in the first place.
Running surprisingly well for a beta. I really hope to find some free time and help some more with reporting the minor bugs left during the end of the year vacation time and help polish for the final release.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.