Is there enough space on your filesystem? That includes your home folder and main root file system?
If so then i’d deletenor rename folders associated with bottles and try again. If its a user level install check ~/.local/share/Flatpak/app and ~/.var/app and deleteor rename the bottles folder. If its a system wide install look in /var/lib/Flatpak/app
Then try and install it again. It will create a new set of folders.
I have a linux desktop with dual 4K screens and I don’t have problems with high DPI? The only problems I’ve come across is with Wine which is easly fixed within the winecfg.
I’m on OpenSuSE, using KDE in X11. I DID have scaling problems with Wayland which I avoid until it is fit for daily use.
Of course 4k is 4 times 1080p (or twice in X and Y dimensions) so maybe it’s much easier to scale to? 2K on the Framework is an odd resolution so maybe scaling would be more troublesome? 1080p to 1440p would be 1.3x scaling.
You can read NTFS drives; I still have shared drives from my Windows install despite barely using Windows at all.
You can generally import steam libraries, and then steam can do the proton work.
And you can sometimes run other programmes in Linux from the windows install - i.e. it can have it’s own Wine prefix in Linux and use the installed files on the NTFS. But this doesn’t always work - if the programme’s or game’s installer makes significant system changes or installs other software then they won’t exist in the Wine prefix and the game may not work. It’s better to install windows games fresh so everything is installed into the wine prefix.
And Lutris is well set up with scripts for installing a wide range of games from their installers; it will avoid problems reinstalling games fresh.
This is very good advice
My advice having made the move (but with a fair bit of linux tinkering before hand):
Sorry I originally posted around permissions as I misunderstood; deleted that. The solution is below:
If it’s a user installed flatpak you should find the config files in:
~/.local/share/flatpak/overrides
Edit the document for the flatseal app. Thats where flatseal or the flatpak override tool makes it’s config changes for user installed flatpaks (including env overrides). You can also delete the flatseal file (which will be the name of the flatpak - com.github.tchx84.Flatseal) "to set back to default.
There will only be a few files - files are only created when there are overrides set. Anything running default permissions/config won’t have an override file.
EDIT: For completeness, for System wide flatpaks all the files are in:
/var/lib/flatpak
Just to explain why they’re stored there: you’re trying to change the config of the sandbox itself not the app. Flatpak manages the sandbox and it is flatpak that needs to know what permission an app should have. Any files in “~/.var/app/…” pertain to the app itself inside it’s sandbox.
KDE config files can be changed on the command line using:
And viewed using
Power management is in:
And
You can feed changes to the file via kwriteconfig via the command line OR create a duplicate file with different settings and use rename commands in a script file to switch back and forth.
E.g. rename the file to “powermanagementprofilesrc.backup” and create and rename a custom file with the settings you want like “powermanagmentprofilesrc.one” to “powermanagementprofilesrc”. Rename them back and forth via a bash script to switch “profiles”
To apply changes you’d need to then run qdbus:
And then to load the new config in your current session:
So either use kwriteconfig and qdbus in a script OR make duplicate config files and a bash script to copy or rename the configs as needed plus qdbus to apply the changes to the current session.
There may be a much simpler way of switching profiles already actually defined within the exisiting config files (e.g. battery saver vs performance) using qdbus but I’m not sure how to do that myself. Possibly using:
EDIT2: Sorry this is a very long post! Just to say if you’re new to linux and want to understand a bit: qdbus is a tool for QT based applications (including almost all of KDE which is build in QT) to interact with DBUS which is basically the messaging system in linux between processes.
So when you run qdbus on it’s own you’ll see a tree of processes that are interacting with QT processes. Then if you run qdbus & the name of a process like “org.freedesktop.powermanagement” you’ll see what QT processes are running with/under it. Then if you run dqbus and add that connected process like “/org/kde/Solid/PowerManagement” you can see what strings and options are available. Then you can run qdbus to see more detail or change a setting/string.
Hope that make sense!