I've been an IT professional for 20 years now, but I've mainly dealt with Windows. I've worked with Linux servers through out the years, but never had Linux as a daily driver. And I decided it was time to change. I only had 2 requirements. One, I need to be able to use my Nvidia 3080 ti for local LLM and I need to be able to RDP with multiple screens to my work laptop running Windows 10.
My hope was to be able to get this all working and create some articles on how I did it to hopefully inspire/guide others. Unfortunately, I was not successful.
I started out with Ubuntu 22.04 and I could not get the live CD to boot. After some searching, I figured out I had to go in a turn off ACPI in boot loader. After that I was able to install Ubuntu side by side with Windows 11, but the boot loader errored out at the end of the install and Ubuntu would not boot.
Okay, back into Windows to download the boot loader fixer and boot to that. Alright, I'm finally able to get into Ubuntu, but I only have 1 of my 4 monitors working. Install the NVIDIA-SMI and reboot. All my monitors work now, but my network card is now broken.
Follow instructions on my phone to reinstall the linux-modules-extra package. Back into Windows to download that because, you know, no network connections. Reinstall the package, it doesn't work. Go into advanced recovery, try restoring packages, nothing is working. I can either get my monitors to work or my network card. Never both at the same time.
I give up and decide it's time to try out Fedora. The install process is much smoother. I boot up 3 of 4 monitors work. I find a great post on installing Nvidia drivers and CUDA. After doing that and rebooting, I have all 4 monitors and networking, woohoo!
Now, let's test RDP. Install FreeRDP run with /multimon, and the screen for each remote window is shifted 1/3 of the way to the left. Strange. Do a little looking online, find an Issue on GitHub about how it is based on the primary monitor. Long story short, I can't use multiple monitor RDP because I have different resolution monitors and they are stacked 2x2 instead of all in a row. Trust me I tried every combination I could think of.
Someone suggested using the nightly build because they have been working on this issue. Okay, I try that out and it fails to install because of a missing dependency. Apparently, there is a pull request from December to fix this on Fedora installs, but it hasn't been merged. So, I would need to compile that specific branch myself.
At this point, I'm just so sick of every little thing being a huge struggle, I reboot and go back into Windows. I still have Fedora on there, but who would have thought something that sounds as simple as wanting to RDP across 4 monitors would be so damn difficult.
I'm not saying any of this to bag on Linux. It's more of a discussion topic on, yes, I agree that there needs to be more adoption on Linux, but if someone with 20 years of IT experience gets this feed up with it, imagine how your average user would feel.
Of course if anyone has any recommendation on getting my RDP working, I'm all ears on that too.
Multiple mistakes:
You went with a very old distro, Ubuntu 22.04 is almost 2 years old. You could pick a non-lts ubuntu instead. Thankfully you ended up picking Fedora.
A single google search could've given you better alternatives to FreeRDP like Remmina. You can always ask people stuff like this on Lemmy or elsewhere ("what's the best rdp client on linux?") rather than waiting till you run out of patience.
You shouldn't need to compile software by yourself, you can use flatpak to install newer versions of software and flathub even has a beta repo you can add for even newer software.
It's not against you, we all learn from mistakes. Just try to be more social about your linux journey if you don't want to struggle
Tldr: you made the classic mistake of going head first into this without a friend to help you or at least documenting yourself properly on the current state of Linux desktops through various medias like Youtube. It doesn't help that you suffered from the ol' "I'm a windows expert so this should be similar/easy and if it fails it's not my fault"
Ubuntu 22.04 is not "very old". It's the latest LTS release of Ubuntu. I do not, at all, fault an IT professional for picking the LTS release instead of the absolute latest latest release.
I think it is a communication failure for Linux to not communicate that the jump between Linux distro versions (e.g. from Fedora 38 to Fedora 39) is not the same as a jump from Windows 8 to Windows 10. It is similar to the jump between the different Windows subversions, like from 21H2 to 22H2. Most people don't even know what those numbers mean, and for most people, it doesn't matter. A distro upgrade is nothing more than a big update, and that's how I think it ought to be presented. People should be encouraged to use the non-LTS version as a default, and gently nudged to upgrade once a new one comes out. It shouldn't be presented as a conplete change in operating system versions, but rather as a feature update. That's what Windows does, and Windows versions are practically invisible!
The support for larger numbers of monitors and mixed resolutions and odd layouts in KDE vastly improved in the ubuntu 23.04 release. I wouldn't install anything other than the latest LTS release for a server ( and generally a desktop ), but KDE was so much better that it was worth running something newer with the short term aupport on my desktops.
We aren't too far off the next LTS that will include that work anyway I guess. I'm probably going to be making the move to debian rather than trying that one out though.
While you make many valid points, I think it's not reasonable to assume that OP could have avoided all the struggles they had, if they just had informed himself prior to installing. Especially since many of them problems described were probably caused by an unfortunate combination of software/driver issues, a specific hardware setup and certain user expectations.
I doubt that watching tech YouTubers or similar would have helped much.
Also, dont download packages as .rpm /.deb files, that almost never works. They could have just used their phone with usb-tethering to get Ethernet. I suppose.