A 27" display is gigantic for 4K at computer monitor distance, the pixels are going to be as big as Christmas hams. Just set it to 100% where it’s supposed to be and maybe invest in a pair of peepers if that’s somehow not easy for you to see. Users under 90 should be fine, though.
I like the 27" size. They’re both 60 hz unfortunately :/ I’m thinking of either one of those really long monitors or two with high refresh rate. I need at least 90 hz. I freaking love 4k and can never have anything else.
Did you happen to try wayland within the past year? It’s gotten remarkably better. I sadly don’t know how to fix your problem, but be aware that Plasma X11 is basically EOL.
Yeah I tried Wayland like a few weeks ago and got the undefined variables I mentioned. Without those the vast majority of apps like Firefox, Steam, etc don’t work…
But since you mentioned it I did give it another go just now and it’s up and running fine, the variables are there:
echo $DISPLAY; echo $WAYLAND_DISPLAY
:1
wayland-0
But this has been on again off again so it might stop working at some point. Only time will tell :)
Hmmm. This is either tangentially-related or an extension of the same issue you experienced... but I started using the terminal within Kate this past week troubleshooting a .bash_aliases function error and noticed that it too was not updating its environment as expected, even after editing the file and running source ~/.bashrc.
I spent 30 minutes only to realize that all of my edits/source reloading were not registering within the Kate terminal for some reason, but were working as expected in Konsole. Once I shutdown Kate and restarted it, the issue was fixed but that seems like a bug and it makes me wary about leaning to heavily on the terminal within Kate (or any other KDE apps outside of Konsole)
Are you on Wayland, because if yes I strongly suggest to go with X11 for stability in cases like yours. If you really want to distro hop, you could try Debian stable, because it’s still very close to upstream & is much newer than Ubuntu 22 right now.
@meiko60 why do you think that the reason for the freezes is the graphics driver. Isn't Linux completely freezing typically a running out of RAM (when you haven't set sufficient swap partitions or swap files). On KDE, you can enable the classical Ctrl+alt+del key to reset the xserver/Wayland (advanced keyboard options). Could you check whether this still works when the freeze occurs? Are there any special things in your system log?
@meiko60 newest Nvidia drivers are at the moment 535.xx. you could maybe try upgrading to se whether the situation changes. It's easiest to get new Nvidia driver when following the instructions for installing CUDA. You typically don't need to install all of the CUDA SDK and could for instance just install the package cuda-drivers
To get the size of archives and folders: os.stat(filename).st_size # for folders you have to use it together with os.walk()
To get the list of files inside an archive I use the zipfile, rarfile and tarfile modules.
For the file type, I either extract the extension from the name or I use a bash command via subprocess:file --mime-type filepath
subprocess is used if there is no extension (as often happens with text files).
I preferred to use subprocess to avoid having to increase the number of dependencies needed.
KDE
Top