It’s probably a tiling window manager. ;)
Centrist, progressive, radical optimist. Geophysicist, R&D, Planetary Scientist and general nerd in Winnipeg, Canada.
troyunrau.ca (personal)
lithogen.ca (business)
It’s probably a tiling window manager. ;)
KDE had a policy editor back in v2.0… honesty I never really followed whether those features stuck around. But the simple version is to lock down write access to folders in $HOME, such as .config or similar. Linux already prevents most users from installing programs over the system directories without root, but I’m not sure if you can restrict new programs with +x in $HOME unless you write-lock the whole folder… Someone with more network admin experience probably knows this :)
Congrats on taking the plunge. I suspect there are others like you.
I’m actually kind of envious. The joy and frustration and joy again of exploring something new was something I relished in my early Linux years. Back then you had to use a text editor to configure your video card before even getting started, so it was kind of insane haha. But totally worth it later, as all of those skills translated.
Ouch. I know Bandcamp isn’t owned by its founders anymore, and the new owners in theory are sketch… But it’s still close to the best webstore ever conceived for music. The payment processing alone is worth it. What is Faircamp in that space?
It’s probable there are better ways at finding things, but sometimes these commands are sort of muscle memory and I don’t even think to explore what else is out there once I have something that works for me ;)
It’s hard to teach an old dog like myself new tricks. I still think git was a mistake and long for centralized revision control systems… Because that’s what I grew up with ;)
KDE always gives you enough rope to hang yourself. Like, set the transparency of all windows to 100% and wonder why the system is fucked, or whatever haha.
Working blind, and from memory (I didn’t check my system): depending on your system, there will be a kwin config file in .local or .config or .kde or similar in your home directory. Assuming you have console access, df -h | grep kwin will probably find it for you. Take a peak in the file first to make sure it’s reasonable that this is the right file to nuke. Rename it something like kwinrc-backup and restart KDE.
Ooh, I’ve met three of them on this list. Jean-Baptiste was the best though ;)
And has broken those systems in the past. But diversity in implementations across Linux systems likely means it doesn’t break all systems simultaneously.