Linux

Sorry to hear about that mess.

I posted here https://lemmy.nz/comment/1784981 a while back about what I went through with the Nvidia driver on Linux.

From what I can tell, people who think Linux works fine on Nvidia probably only have one monitor or maybe two that happen to be the same model ( with unique EDID serials FWIW ). My experience with a whole bunch of mixed monitors / refresh rates was absolutely awful.

If you happen to give it another go, get yourself an AMD card, perhaps you can carry on using the Nvidia card for the language modelling, just don't plug your monitors into it.

Remmina

I read "boot", "side by side with windows, "ubuntu", Nvidia" and some awfull war flashbacks came back to haunt me.

As someone who grew up toying with both windows, Mac and Linux I think people always underestimate how hard it'll be to migrate to an OS they never tried before. I've seen lots of people getting frustrated that way, regardless of the OS.

So I'd say being an IT guy or a tech illiterate won't change much in that regard. I guess being an IT might at least give you shortcuts but you'll still hit a wall if you don't check beforehand if all your needs will be easy to access and how much pain you'll have to deal with.

At least that's my take on it.

But yeah, Ubuntu can be awfull depending on your needs. Windows and Linux don't make good neighbors, windows is always the one trying to murder the other, and Nvidia is a nasty piece of work.

Sorry to hear it didn't work out for you :(

To squeeze in a metaphor : Linux is just a hobby project that kind of got out of hand in a previously Microsoft dominated world.

In the BSD world (FreeBSD,NetBSD,OpenBSD etc.) things are actually much worse. I've read that on computer conferences BSD developers come with an Apple Macbook (Running MacOS) to show BSD software development, which is running on servers. And I like BSD, but on the desktop it is still lacking. One only has to look at the amount of packages which no longer have a maintainer. I am not complaining about it, as I realize that maintaining open source software can be a burden.

If you want to play some more with Linux on the desktop, you can use WSL on Microsoft Windows, or use VirtualBox. Wanting to make Linux your daily driver may require more patience, or throwing money at it to speed up code development.

For RDP, I use Remmina. Multimon only works on X though, not wayland, so make sure that's the graphic server you're running. Idk if it'll work for 2x2 tho, I only have 2 monitors.

For the headaches, I use a magic pill that I'm not legally allowed to view the ingredients of and cry into my Tissues as a Service.

Every 5 years or so Windows annoys me so much with its nonsense that I salt the earth and install a Linux distro.

The last time I did this was Ubuntu (tried manjaro or whatever its called before too) and every time I find a problem that requires hours of trawling the Internet just to find I need to basically rebuild/test/maintain my own version of the library/component.

It gets to the point where I can't really be productive and I begrudgingly go back to windows as it's less faff and more productive for me. Then the timer starts again for I get too annoyed with windows.

I want to love Linux, but its not as simple as "just using it." (unless you are using a steam deck, that is brilliant for its use case).

Part of the problem for me I feel is that the Linux eco system is so wide and vast that we don't have a singular collective agreement on where to share effort to get something as stable and easy to use as Windows etc. From this thread alone people seem to hate Ubuntu, and sur maybe it's bad, but most non Linux people only know of that Linux distro.

The sheer vastness of the eco system is it's downfall, if there was 1 main shell everyone got behind and was used by companies and end users then we would have a huge knowledge base of problems and fixes as well as a concerted effort in a shared direction. As it stands at the moment most companies using Linux don't have a shell layer, then end users are probably all using various different shells and related components etc, so effort and support is not consolidated as everyone is pulling in their own directions.

I get this is one of the things that draws in the current Linux userbase, but for those of us who just want to do same stuff we do on windows/mac we don't really care about being able to mix and match stuff, we just want to get behind something that gets out of our way and let's us use the computer, not faff in the infrastructure of the OS.

The accustomed workflows sometimes don't translate well to other platforms. RDP might be such a case, I don't think it's the standard in the Linux-world, maybe try the standard solution of your distribution, or look up which one is good for multi-monitor setups, there are lots of other VNC solutions. Yeah, and I'd skip Ubuntu as a first choice, but you figured that out the hard way.

I mostly use SSH to manage servers, but you could try cockpit if you want something more graphical.

Its sad but linux is still a second class citizen. Nvidea drivers have improved greatly over the years, but it can be still flaky especially newer ones.

Multi moniter support too, it has a history troubled with challenges. Its much much better than it used to be but sometimes there are setups and usecases which have problems. It used to be multiple monitors, just having them as a desktop, was impossible. Nowaday I can daily drive Linux and expect to have a good desktop experience across multiple monitors.

Mindyou, every windows update its a dieroll what breaks for my work surface labtop. Often my display or dock behaviour breaks or my bluetooth, or my networking. Not to excuse the bugs in linux, but to show that even MS on their own hardware have bugs like that. Pcs are hard and even MS can't do it flawlessly.

What you describe as simple multimonitor RDP might actually be a very complex task from a technology and display standpoint.

That being said, it totally sucks having a usecase and finding out that for you have problems getting there. I agree that Linux still has major hurdles for general adoption, (although again, it is so much better than it used to be). Look at it this way: if desktop linux had the same amount of money and development time thrown at it as Windows or MacOS, we'd have a very different experience.

As for tips. I recommend to dualboot. Use MS for your usecases that are not a good experience and use Linux for the other things. Keep checking in with the multiple RDP tech/workflow to see if it works. I did the same thing for years. The only reason I used windows was my games. For other things I used Linux and learned my way around the desktop while doing that. Eventually Proton came along and I could switch entirely.

I've been extremely happy with Linuxmint the past 2-3 yrs. However I have a higher end AMD card. 97% of games play great under Proton with steam. I use Rustdesk to remote into other Linux machines as well as windows OS servers/desktops even with multiple screens and it works without issue. Just my $0.02 and I know it's heavily Ubuntu based but the stability and usability as a daily driver, also working as an IT professional has been great.

Last piece, it's been a rare occurrence but if I'm messing around using bleeding edge graphics drivers or "playing with fire" messing with deeper system configs, drivers, etc and shit the bed I have had 100% success using TIMESHIFT to completely restore my OS back to its previous state with zero data/config loss or issues. You just need to have the discipline to remember to take a backup before you know you're going to be potentially blowing something out. But, that said, it fully restores everything. I have a 18TB external USB I just use for that and it doesn't even take long either, restoring a 2 & 4TB SSD system that's pretty loaded up with data.

There are two different RDP implementations in Linux: freerdp (which is the underlying library for remmina as well) and rdesktop. Each has its own set of bugs. No idea if rdesktop offers better support for what you want to do—I use it, but I only have single-monitor setups at both ends. (It has an annoying bug that can make it require multiple attempts to establish a connection, though.)

There's an app on Flatpacks called Thincast remote desktop client. I don't htink it's using the free rdp libraries, so it's possible that the bugs you encountered with the other open source apps (that all use the same underlying libs), might not be there.

I'm on the ubuntu derivative Pop!_OS. I RDP with multiple monitors of different resolutions using remina. Nvidia is also supported out of the box. All you'd need to do is install pop and then remmina.

Is your problem that you just want one big window across all your monitors? I.e. not multi monitor RDP, or that you want a separate window on each monitor where each is seen as another monitor on the remote system?

Skill issue

Like with any unfamiliar tech I find it is probably smoother to start small and work your way up.

So find a laptop that people have no issues running Linux on. Get one and then install just Linux on that and play with it.

The thing is, Linux has a small user base and so it probably isn't realistic to expect it to support every conceivable hardware configuration on top of dual booting on every one with Windows. It's way better than it used to be but sometimes people run into problems. Like me trying to get 5.19 kernel to work properly with my specific newer AMD GPU (any 6.x kernel is fine so like Fedora? No prob).

One of the things I try to do is research what network card chipsets, sound chipsets, and video card models work easily because some just don't.

It sucks I know. Linux doesn't have a gazillion dollar market behind it providing significant incentive for vendors to get their shit straight. Even so Linux does pretty well.

Anyway. When you're fighting with several things at once it is easy to get overwhelmed and frustrated. Dual boot with windows, alone, can be iffy in my recent experience. Then add Nvidia, more headache. Then add some less common use cases like rdp... Etc.

Best of luck if you try again.

Bummer that it's giving you such a hard time. On rdp: Linux/Linux doesn't even need it. ssh to remote. Run gui app. It runs on remote and displays locally. Wayland is probably going to kill that though. Until it does, the X11 client / server model is pretty swank.