Run journalctl -f before starting Lutris, then launch Lutris and check the journalctl for any errors.
Hmm, so I've had a look and it seems like Xournal++ only supports x86_64. Which means that if you get the Snapdragon version, you'll need run it using an x86 emulator like FEXEmu or Box64, and this will affect the performance and may also introduce compatibility issues. So you'll need to do your own research and find out if someone's managed to run it on ARM / Snapdragon 7c, and if there's any issues etc.
You could get the Celeron version instead, but personally I can't recommend a Celeron to anyone in good faith, so you'll have to make your own decision sorry.
doasis relativly simple (a few hundred LOC)
Actually it's close to 2k lines of code (1,946 to be exact). But yes, it's certainly a lot simpler than sudo (132k).
Forget Linux for a second. What you need to be aware is that both the variants come with only 4GB soldered-on RAM and eMMC storage. That means, even if you do manage to get Linux going on them, it's going to be super slow for any sort of practical Web/GUI needs. 4GB RAM is barely enough to run a browser these days, and if you tack on a full-fledged DE and multitasking with other apps, you'll be pushing memory pages to the disk (ie, swapping). And when that happens, you'll really feel the slowness. Trust me, you don't want to be swapping to eMMC - that's super old tech, something like 3x slower than UFS, which in turn a LOT slower than m.2 NVMe (the current standard used in "proper" laptops/convertibles).
Also, consider this for perspective - even budget smartphones these days come with at least 6GB RAM and UFS storage. So this laptop/convertible - a device meant for productivity - is a complete ripoff.
If money is an issue, then just buy a used laptop (from eBay, or whatever you guys use there). If you're aiming for good Linux compatibility then ThinkPads are a safe bet. But since you're after a Surface-like device, then you could just get any older Surface device. Why settle for an imitation when you can get the real thing? In any case, most older x86 laptops from mainstream brands should work fine in Linux in general, just do a google for it to see if there are any quirks or issues.
Regardless of your choice, avoid the Duet 3. 4GB RAM is completely unacceptable for a laptop in 2024.
Are you on Wayland? If so, try setting the theme using Nwg-Look instead. If not, stick with LXappearance. Also btw I just found out that LXappearance doesn't apply GTK settings directly, you'll need log off and on for the change to take place, if you haven't done that already.
Also, what's the DE that you're using? Because if you're not on Gnome (from the sounds of it, you're on LXQt?), you may need to install certain GTK theme engine dependencies like gnome-themes-extra and gtk-murrine-engine. Reboot (or logoff/on), and try again.
Also worth trying a different theme such as Breeze or Arc. Maybe try a light variant as well.
If all else fails, open a bug report on the Lutris github.
Most likely that's a theme issue. Close Lutris, change back to the default Adwaita theme and try again.
- Fedora 37 - 2022-11-15; Nobara 37 - 2023-01-07
- Fedora 38 - 2023-04-18; Nobara 38 - 2023-06-26
- Fedora 39 - 2023-11-07; Nobara 39 - 2023-12-26
- Fedora 40 - 2024-04-23; Nobara 40 - 2024-06-19 (assuming an average delay of 57 days)
You won't find any alternatives because Flatpak has won the war. Pretty much everyone (except Canonical) hates Snap and avoids it like the plague, and AppImages have significantly dropped in popularity amongst users due to the rise of Flatpak, and the various advantage it has over AppImages. So you're left with only Flatpak/Flathub basically.
skim has unfortunately been abandoned, there have been no updates in an year, and several old PRs and issues remain untouched. The current recommend fork is two_percent, which is also more faster and memory efficient.
If you're facing the same issue with two_percent as well, you can reach out to the author in this thread, since they haven't yet opened up their issues tab.
It's one of the only ways I know of to make a Windows ToGo installation (equivalent of a Linux Live USB),
You can also use WinToUSB for that btw. Yet another option is to install Windows to a VHD file (using a virtual machine, or using Disk2VHD to convert an existing install), then copy it to your USB, and make it bootable using Ventoy. The latter option is more useful, since with Ventoy you could have multiple other Linux ISOs (or other OS/rescue images) all on a single, portable drive.
No, you're looking at the commit log for skim. two_percent was last updated two months ago. I also had a chat with the author yesterday and they're keen to continue maintaining the fork.
You can continue to use OneDrive. I use the OneDriver client and it works really well - your drive appears just like a local drive, but files only get downloaded when you try to access them. Once downloaded, it gets cached locally and is available offline, and is kept in sync automatically. Other cloud providers should have similar FUSE clients available.
Best practice is to stick to packages provided by your distro's repos. Flatpak should be your second option if you can't find your app there, and AppImages should be your third option (since Flatpaks are superior as they can share dependencies, unlike AppImages). Avoid Snap. In fact, avoid any distros that even use Snap (*buntu). Also, if you're on a Debian/Ububtu based distro, avoid adding PPAs (thirdparty user repositories) as far as possible, as these can cause dependency issues and may cause pain when you upgrade your distro.
That should be provided by your distro - Gnome-based ones have "Software" and KDE-based ones have "Discover".