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.
I read that a lot, but my RTX4080 works quite well on linux. I’m running gnome with wayland on openSUSE tumbleweed. According to lemmy and reddit, that should be a disaster combination.
I used to have problems and visual glitches with text in flatpaks (like VS code, or Spotify, the text would be bugged), but as of the latest drivers that is fixed.
From my experience on Fedora, my advice is that after a new kernel installs, don’t restart immediately, give it a minute or two to build the nvidia drivers for that kernel. If you are signing them for secure boot i guess the recommended wait is 5 minutes.
I read this a lot as well, and I think for a time this was true, but in my experience with a 1070 and 1080ti, Ubuntu and Fedora worked fine with minor tinkering, pop_os and nobara work out of the box. Currently on nobara, and most apps and games work just as well if not a little better than on Windows. A mate of mine runs nobara with a 3080 and no issues there either.
I just switched back to windows, after using Kubuntu for the past 13 month.
I’m a software dev, I work on a Dell precision 5560 and just got tired of the worst touchpad experience ever, the endless Bluetooth issues, the fact that sleep mode basically does not exist anymore and a bunch of other small things.
On windows I do almost everything in WSL so I still work on Linux, but this way I get a much better desktop experience on my laptop.
I used to be a Windows system developer, think device drivers etc. for what, 20 years? I switched to Linux 18 years ago and never looked back - the whole dev experience is a lot more pleasant, more control, reasonable tools and software installation, proper customization etc.
I believe you didn’t have a Linux problem, you had a problem with hardware manufacturers being fussy about enabling development of proper support for their hardware. Why not look into hardware that is actually readily compatible with Linux? Tuxedo Computers are often recommend, I used to run a Clevo and had a great experience as well.
I believe you didn’t have a Linux problem, you had a problem with hardware manufacturers being fussy about enabling development of proper support for their hardware.
Which is a Linux problem at the end of the day, unfortunately.
My current laptop is also “Linux certified”, whatever that means. I cannot say that linux does not work on my laptop because that is not true. It works. Bluetooth works, touchpad works, like 95% of the time. In that 95% I love linux. However, when the remaining 5% hits, that is freaking annoying. And you can bet the bluetooth issue hits in the middle of an online meeting, and not when you just listen to music. 4K monitors are around since ~2013, still, no user friendly solution for fractional scaling, and the list goes on.
My main problem is that, this 95% was always 95% for me. I have been trying to switch to linux since 2011. I spend 3-15 month on linux and switch back to windows for a year or two. As I see, linux desktop just runs after the desktop market and it is 2-10 years behind. I know that is mostly because of the HW vendors. But knowing this does not make me feel better when my productivity decreases due to these issues.
Why not look into hardware that is actually readily compatible with Linux?
Honestly? Because I don’t believe that 95% is significantly higher on those laptops and I just don’t have ~1500EUR for an experiment like this.
Windows + WSL2 works great. I use a Windows distro, if you will. All the issues I had with my native linux install are gone, and I can still use linux comfortably while working. This is the reality from my point of view.
Hm, I never had any hardware issues in the last ~10 years, but don’t get me wrong, I hear you. I absolutely believe that it is possible to find a combination of HW and SW that will simply not work for a particular use case, and if my productivity would be threatened, I’d also switch in a heartbeat. In fact, I’ve gotten so used to the customizations Linux offered me that I can’t even imagine working on another Linux system without my setup and dotfiles - a different kind of vendor lock-in, if you will.
Anyway, just wanted to put a brand out there that offers some guarantees when it comes to hardware support, in case you (and others) might not be aware of such vendors.
Are you sure S3 sleep is enabled in the bios? On most machines it’s one or the other, not both at the same time. On some Intel machines you can still enable S3 standby, but I know AMD killed it a lot sooner than Intel did.
Windows has powercfg /availablesleepstates to show what states are supported. I’m sure there’s something like that for linux but I’m not 100% sure. You could try dmesg | grep -i “acpi: (supports”
Microsoft says it’s more secure. and that since it stays on its 100% the OSes control which is supposed to be much more secure”reliable” than S3 standby.
Nevermind that S0 standby is so incredibly buggy and awful on windows where it’s supposed to be best. My i9 Thinkpad drops 20% battery in 15 minutes, then goes into hibernation. It has a 50% chance of overheating in my bag and crashing when trying to get in to hibernation.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.