I didn’t realise this option existed - and it’s an interesting one, perhaps giving the ease-of-use of Mate/Cinnamon/Gnome 2, without sticking with the older code.
but ok, yes, for actual remote desktop, VNC or RustDesk, despite RustDesk being some open-core implementation that holds the good stuff in the proprietary release. At least it was when I last checked it out.
I don’t think OP is looking to remote into servers here, personally for servers ssh is great but for accessing my laptop from desktop/vice versa the terminal can be a bit awkward when there are applications with no cli behind them which is where a graphical remote desktop comes in handy
Ooh, CRT monitor. And that’s an odd resolution that it’s suggesting. You could try driving it at 1280x1024 at 60Hz. If that doesn’t work, try 800x600 at 60Hz, which is the traditional lowest SVGA resolution (picture may be slightly distorted if it really is a 5:4 monitor). If that doesn’t work, try the traditional VGA resolution of 640x480 just to get something going. I’d recommend using X as Wayland has probably not been tested very much on hardware this old. And it almost certainly has no clue how to deal with a widescreen resolution or a resolution wider than its “Recommend mode”.
(I was still using a 17" CRT with X at 1280x960 up to about five years ago. I had no issues ever.)
I just did something similar last week. My criteria were 1) small form factor like a Chromebook, 2) not actually a Chromebook, 3) could swap out or install an m.2 SSD.
I ended up getting a harddrive-less old Latitude 3190 for 30$ off eBay, put a 256gb SSD in (had it lying around + that’s the max capacity supported I think), and ended up installing fedora KDE. It’s not perfect but for the price it’s amazing
Dang, that’s a nice deal. I think I want something with a bit more juice, as I would like to play Minecraft from time to time. I’m leaning towards used thinkpad
I installed fedora 38 on my lenovo thinkpad t14 (now running fedora 39) and aside from one easily fixed issue bluetooth works perfectly. My gaming pc running windows can use my laptop as an audio device via bluetooth which is pretty cool.
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.
So I’ve recently moved over to using my Pixel buds pro almost full time and am hoping you stoke a convo here to revisit.
KDE Connect affords us the ability to fire off commands from a phone to do any number of things. One use case of mine is to disconnect/reconnect Bluetooth devices from the desktop since it is greedy and tends to bogart my earbuds when playback stops on other connections. This has worked pretty well so far but with that in mind, I have only just started playing around with things and so I look forward to refining the experience with other utilities.
That said, I find Bluetooth is buggy on almost every OS out there (Android is constantly in what feels like a state of repair…)
Best of luck!
I haven’t had any issues.
But it’s not uncommon to a problem somewhere in the Bluetooth stack. It’s important you report any bugs you come across to the respective projects, because of how diverse Bluetooth devices are it’s hard to get perfect support for everything.
No issues currently using pop os. I don’t use the graphical Bluetooth manager, for whatever that’s worth. I wrohe a script that connects and disconnects with bluetoothctl, and I pair and trust devices with bluetoothctl. I use several different headphones.
Occasionally, I have to go into the audio settings to change the destination, or tap a button on my headphones, but that’s about it.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.