Hi Tildes community,
I'm seeking your suggestions for spinning up Windows virtual desktop.
Allow me to set the context...
My offspring is in second semester of their first year of university, and needs to use Adobe Photoshop for one of their classes this semester. They don't use a regular laptop, and have been doing quite well at uni. with their beefy Ipad. While they have used photoshop so far on their ipad, there are some growing pains. Of course, they have access to super beefy desktop Apple Macs at their school's computer lab, but its a pain to get usage of them for a few reasons. At home, all my machines are linux except for my partner's which is an old clunker Windows laptop - which i am in progress of migrating themn away from that Windows machine towards linux laptop...Hence, I don't really have a solid, modern enough machine for my offspring to load Photoshop onto.

Then, I thought, hey, maybe i can spin up some Windows virtual desktop somewhere for my offspring to use photoshop on...Its only needed for about 10 or 12 weeks remaining this semester...and they only need to use it once per week for each week's assignments. I feel like as long as the virtual windows machine is beefy enough to suppoort photoshop workloads, it can get them through the semester...and then in summer i can decide if I need to buy them an actual laptop (like an Apple laptop, etc.).

So, may i ask of you dear Tildes community members...Does my approach make sense (of trying to use a windows virt. desktop)? And, if so, are there any recommendations for which provider to use, and how to spin these up? Like, should i try something via AWS or Google Cloud or Azure? Or, should i not even consider this virtual windows approach? I'm open to hearing any/a ll recommendations. If you have links to share for me to research, or if you actually wrote your own blog post on similar topic for example, i'd love to hear it! Thanks in advance!!

Edit: 2025-02-24 UPDATE: Wanted to update folks on where i am on this...After reviewing these comments, researching some more both online and offline, etc...I arrived at the decision of biting the bullet and just buying my kid an Apple Macbook laptop. I want to thank you all for all your greet feedback and suggestions! Thanks so much Tildes community!!!

I've been self-hosting for a few years. However, now I have a single server hosting all of my things whereas, before, I had multiple old machines physically isolating services. I'm getting ready to host a game server or few (at least one for Tilde) on this machine.

While I'm not a neophyte to Linux, I'm not a guru and definitely not an infosec expert.

Given that, what steps do you take to secure a Linux server, LXCs, and docker containers that are receiving port-forwarded internet traffic?

FWIW, I expect I'll have an LXC running docker containers. I can instead run a VM doing same.

Advice welcome!

While I consider this resolved at time of posting, this is one of my weirder, more unexpected tech issues I've run into and I thought y'all might enjoy it.

I'd been having issues with my (Ubuntu) server where its services were unavailable, I couldn't SSH in, and USB devices plugged in after the issues started weren't connecting (mouse LED would light up, couldn't toggle keyboard locks or interface computer with the devices). These issues were becoming a near daily occurrence.

So after the most recent incident I decided to watch it boot. After grub, it would just hang at a black screen. So I opted for the recovery mode and after waiting some minutes for services to time out, I was given a terminal and used that to check my devices, sensors, etc and all were reading fine.

Frustrated, I started reviewing what else could have possibly changed with my setup, and I found that change in my hand. I use my server's front USBs as a low current charger and had recently got a new vape battery that was charging at that moment.

I unplugged the battery, rebooted, everything was fine. Plugged the battery in, everything locked up again immediately.

I had been using a spare cable, it had data wired. Swapping for the included power only cable, and no issues.

While I'm curious as to what exactly is happening and why, I'm satisfied enough concluding it is a cheap vape (I mean, I'm having to charge the sucker near daily after all) that is transmitting junk over data and the OS doesn't handle it appropriately. I'll pull logs or do another couple tests if other folks are curious as well though.

Oh, and the battery is a Bear Rootz Sol. Come to think of it, my other worst battery at holding a charge was also a Bear Rootz.

I thought I would share my thoughts and experiences daily driving Linux (Fedora KDE Plasma) for the past week.

Why did I switch from Windows to Linux?

My plan was to switch to Linux once Windows 10 hit EoL in Fall 2025. This was due to my computer not supporting Windows 11. This past September, my computer broke (probably MoBo), and so I swapped out my CPU and MoBo, which probably can support Windows 11. However, this hardware swap unactivated my Windows, Microsoft support was not helpful, and I am not a fan of the direction Windows is heading in (removing local accounts, Recall, and a general vibe I get from Microsoft of removing control from end users). So, I decided to make the jump to Linux a year sooner than expected.

My Previous Experience with Linux

So I would say I am moderately experienced with Linux before this. Personally, I have setup a Proxmox server, in which I setup an openmediavault NAS, and played around with various desktop distros for personal curiosity. I also switched my old laptop over to Linux a few years back, but had very low requirements of the tasks that laptop had to perform. I also took a post secondary class on Linux, primarily covering system administration tasks like BASH/PERL scripting, Apache server admin, LDAP, and file sharing all using Ubuntu. So going into this I had a moderate amount of experience, all within Debian based distros. The bigger change with switching my desktop is that it is my primary computer, so the expectations of what it needed to run was higher.

Why I chose Fedora KDE Plasma

I did a post about a month ago asking for recommendations to look into: https://tildes.net/~tech/1ji6/switching_to_linux_looking_for_distro_recommendations
I settled on Fedora KDE Plasma for a few reasons:

• I appreciate the philosophy of not being rolling release like Arch, but also a quicker release cycle than Ubuntu and its forks. I felt this was a good middle ground where I get newer advances without dealing with stuff breaking frequently when there was a new update.
• It can handle most tasks graphically, without having to dig into the console often (more on this later).
• I appreciate the Windows-esque styling of KDE Plasma. I got used to Windows so didn't want a radical shake up. However, it feels to me like a better version of Windows (or maybe just not touch screen oriented and ad bloated).

Headaches/glitches

Some of these are ongoing, while others were issues that I have worked through

• FIXED: Installing nvidia drivers via RPM Fusion. Before installing drivers, the computer was unstable and frequently froze. I ended up just loading a command line only interface and manually typing in the commands to install RPM Fusion and the nvidia drivers. I was planning on installing it via command line anyway, so the main headache here was typing it out instead of copy and pasting the commands in. I also had an issue where I initially installed the wrong drivers.
• ONGOING/INFREQUENT: Occasionally when I wake the computer from sleep, at the lock screen, my mouse is responsive, but my keyboard is not. Also, selecting the virtual keyboard does not work, as the virtual keyboard does not load. I tried waiting for the computer to go back to sleep, and then wake it from sleep to see if it reloads things properly. The computer does not go to sleep normally, so the solution right now is to just shut down the computer and then it is solved.
• FIXED: Steam launched games not closing properly. Specifically Far Cry 5, which runs properly, when I exit the game, the process does not fully close down. From my perspective, it seems like it has, but Steam indicates that it is still running. The solution is to go into System Monitor and close down the Steam application with high resource usage, as that is actually the game still running in the background.
• ONGOING/INFREQUENT/PARTIALLY FIXED: When I wake the computer from sleep, and login, there is a large amount of visual glitches and artifacts on my desktop environment. It is both in applications and especially on the Panel. The current solution is to run the command systemctl restart --user plasma-plasmashell which drastically improves the situation, but the glitches are still partially there. This has just started last night, so probably a computer restart may solve the problem, but I am trying to avoid having to constantly restart the computer.
• FIXED: As Far Cry 5 was a brand new game, when launching it from Steam for the first time, Ubisoft's software wanted me to enter a CD Key, but Steam was not giving me one. Thinking this was a Linux related issue, I switched to my Windows install, and had the same issue. Turns out it is a Ubisoft bug in their software that also impacted Windows. I found a solution online on how to solve it for Windows, did that and authenticated the game. Then I switched over to Linux and the game ran well.
• FIXED: KDE Wallet Service was doing an excessive amount of prompts. I uninstalled the software, but the prompts continued. Turns out it needs to be disabled before being uninstalled, or the prompts continue. So I had to reinstall it, disable it, then uninstall it. Annoying but minor and it is fixed now.
• ONGOING/INFREQUENT/PARTIALLY SOLVED: When waking from sleep, sometimes my background image on my primary display does not fully cover the desktop. This is most likely due to my primary display being 1920x1080, and my secondary display being 1600x900, so the image is not being scaled independently for both displays. The solution right now is to open the settings to change background, and load any image, but not save changes, as this causes my original image to be reloaded properly

Installing/Running Applications

I have been primarily using Flatpaks to install applications. Overall it has been a smooth process. One pain point I have is it seems that the Minecraft Official Launcher for non-Debian systems is kind of clunky requiring me to login to my Microsoft account every time I open the game. This will probably be solved by switching to a third party launcher in the near future. The one software that I haven't gotten around to installing yet is DaVinci Resolve.

What Surprised Me so Far?

There are a few things that have been a pleasant surprise:

• I use the console more than I expected going into it. For flatpaks, I tend to just copy and paste the commands into console. RPM Fusion also had a GUI based install option but I preferred the console option instead. I also have VIM installed, and use that as my digital notepad, just doing simple console commands of vi fileName in my home directory. I was not expecting to use the console as much as I have been, and I think that is partially due to now being more experienced with it, I gravitate towards using the console which I know how to use instead of learning how to do some tasks via a GUI..
• Most things are running better than expected. I haven't touched many games yet, but I haven't had an issue with it yet. It is worth noting that I do not play competitive shooters, so anti-cheat is not something I will have to fight with.
• Libre Office can open my .docx files. I was concerned I may have to convert my existing files to .odt before I can use them, but that does not appear to be the case. I will probably use .odt for new files going forward. It is also worth noting that I haven't worked extensively with my .docx files yet, so there may be some incompatibilities I have yet to encounter.

Overall Thoughts:

Overall I have quite enjoyed running Linux. It does require some tinkering as glitches appear, which currently I am fine with. If I had less free time to tinker and solve the issues, I would probably find Linux to be less viable and more frustrating. Also, most of my glitches can be solved by restarting the computer, although I am trying to find solutions that do not require that. I find it allows me to use the computer and change it to how I want it to be, which I have felt like Windows has gotten increasingly hostile towards the user. A good comparison on this is how the default applications that KDE has included are easy to remove, whereas Windows used to (not sure if it still does) reinstall Microsoft Teams when you uninstalled it.

Edits:

• Added the glitch with background image
• Added more information on my background with Linux, including using it on my laptop

Problem:

I recently switched back to a desktop as my main computer, and was surprised to learn I couldn't use my speakers if my headphones were plugged in.

I don't use a desktop environment (just Sway), so I rely on pavucontrol as a GUI to control my audio.

I could use my headphones just fine while my speakers were plugged in, but when I switched to my speakers in pavucontrol's interface, they would not output audio. My headphones would stop playing (as expected), and pavucontrol's little "dancing bar" would indicate that the speaker's port was processing an audio signal (as expected), but no sound was actually being produced.

Solution:

The culprit ended up being something called "Auto-Mute" in ALSA. To disable auto-mute mode, you can either:

1. Run the command amixer sset "Auto-Mute" unmute in a terminal
2. Run the command alsamixer in a terminal
   2.1 Press F6 and select your sound card
   2.2 Ensure you're viewing playback settings by pressing F3
   2.3 Move the item selection over until you've selected auto-mute mode
   2.4 Press the down arrow key to switch it to "Disabled"

That fixed my issue.

For me, auto-mute mode stayed disabled after a reboot. You might need to run the command alsactl store to make the configuration persistent though. The Arch Linux Wiki article on ALSA has a "tips and tricks" section that goes into more detail:

https://wiki.archlinux.org/title/Advanced_Linux_Sound_Architecture#Tips_and_tricks