wl_touch support is being worked on and I think this is the part that will make it possible!
Right now there's not a possibility to even disable the touchpad, I guess it's all tied to GDM because if you disable the touchpad while you're in the login screen, it'll be disabled in COSMIC too.
Heh, wait until you remember that if you block outcoming traffic it will be hard to download something at a decent speed (unless there are a lot of peers)
I meant that I'd like to be able to select it for everything since it's peculiar.
Gnome-terminal doesn't support it and eventually I wonder if cosmic will use something like alacritty or a custom-made terminal
I know, and I call it bullshit.
There's no way I could't get it working if I could, considering that it can't run yet.
It can't because of the launcher or the anti-cheat (more probable) and proton is proton, there's no difference for the steam deck, apart from gamescope and integrated steam.
Hold on, I think I didn't explain myself properly.
I've never had any problem, the problem that existed years ago was that you had to manually change things to accomodate UEFI, while installing a Linux distro.
For example, while installing Ubuntu you had to press a key during the splash screen and boot there.
It was a simple fix that you had to do while booting the ISO, but it was something not widely known.
And by “corrupt the UEFI”, do you really know what you’re talking about?
Unfortunately not, but I've read that this was a thing, since I didn't want to fry my €1400 laptop I did this simple thing.
Later I've seen that this problem was fixed, but I'm talking about years ago, 2019 or so.
All computers since the late-Windows 7 era use UEFI.
That's why I hated the extra step that I had to do to not corrupt the UEFI while installing a Linux distro years ago... All this new stuff that just locks you and limits you.
Things are better sometimes but in this case they're not.
HDR means High Dynamic Range.
The range of values on an SDR display (Standard Dynamic Range) is 16-235 but the range of values on an HDR display is 0-255, that means that the color "black" on an HDR display is actually black and not "dark-gray".
This is dumbed-down because I don't know the more technical stuff.
Also it has nothing to do to "color saturation" (wrongly called "vividness").
That's a dumb marketing thing since you can do the same using every display in this world.
By the way you might wanna consider an alternative such as rEFInd if you're using an UEFI (BIOS but newer and shittier thanks to "improved security", full of limits) or "systemd-bootloader"
My .profile is quite customized (I just added a lot of exports) and it all works fine... what did you do?