VinesNFluff

Go and actually interact with other human beings.

Frutiger Aero design

The modern trend for flatness and shape-y icons and such was cool for a bit, but I'm officially tired of it.

I'm just about ready to go back to skeuomorphic pre-rendered 3D models as icons and gradients & textures & transparencies everywhere

Especially since computers have only gotten better at drawing this stuff. A modern PC would be able to render the "Impossible" looks of those old Windows Longhorn Concept Videos without breaking a sweat.

Also -- FUCKING BEZELS.

The current trend with -- Mobile devices in general. Phones and Tablets, is to have the entire front of the device be screen. To the point that people hiss at seeing even the little dot for the front camera (or the notch, w/e)

I find this tremendously stupid, leaves you with far less ways and places to grip your phone, and makes the "I was using my phone in bed and dropped it straight into my nose" scenario straight up inevitable, since you can't grip the thing tightly without accidentally activating something on the touch sensitive screen. Just give me a border of plastic that I'm safe to put my fingers on, dammit.

I pirate because I live in the third world 💀

Honestly, probably "palmtop"

There WERE palmtop computers, and the first few smartphone-like devices trace their lineage TO palmtops integrating cell phone functionality.

And it pairs nicely with laptop.

I will start calling them "Emailses" just to spite you <3

The first time I saw a sadface bsod I legitimately said out-loud "Are you JOKING?"

Just did, posted a comment explaining it, will update the main post to mark it solved

I figured it out. After another comment mentioned qdbus, I realised I had qdbusviewer, so I ran that and fucked around in it looking at the services and methods from them and trial-and-erroring for a bit

And I found the command I needed to make it happen. It's a single command too, no need for scripts:

It's: qdbus6 org.kde.KWin /Effects toggleEffect colorblindnesscorrection

It was under Effects rather than Plugins

I am thankful for you explaining how to ACTUALLY work with kwriteconfig. It did work with kwriteconfig6 --file ~/.config/kwinrc --group Plugins --key colorblindnesscorrectionEnabled false in that the file changed the way I expected it to.

BUT

While the command does work for changing the configuration on the file -- the qdbus command to reload it doesn't seem to work.

EDIT: I FOUND IT!

See my post (assuming that's already up, am writing it) if you care about the details

Thanks to your hint I did some tinkering.

Made a backup of my kwinrc file, enabled the effect plugin, checked the diff between the backup and the now-changed-by-the-settings-gui file -- And indeed there it was, a line saying colorblindnesscorrectionEnabled=true in there.

However:

• kwriteconfig seemingly doesn't work like I thought it did, as just doing kwriteconfig6 colorblindesscorrectionEnabled false does nothing -- This, I imagine, is just me not knowing how to work the command itself.

But ALSO!

• Manually editing the rc file to remove/change that line in a text editor did not remove the effect, HOWEVER, upon opening the settings gui app, the checkbox for the plugin was unchecked (requiring me to check and uncheck and apply to disable it proper) -- Which tells me that "editing the file might work but I'd have to run some command to reload the configs and make it go through" -- I did however try qdbus org.kde.KWin /KWin reconfigure (after searching "how to reload kde configs from terminal") and it did nothing, so that is NOT the command I need.

Overall promising discoveries, hoping someone can see this and give me the clue I need to make it work.

EDIT: I FOUND IT!

but once you’re used to it, you realize that info usually give you all the tools you need to fix your problem.

That's the thing right? I'm very much a non-tech person. But Linux error messages are nice and informative to the point that, even if I don't personally know what the fuck they are saying --

-- I can just copy them to my browser search bar. Oh look, someone else had the same issue. And someone who knew what they were talking about presented a solution. Nice, now I can get back to work!

And even when I am forced to troubleshoot on my own, the error messages and terminal logs often give enough of a clue that I can trial-and-error my way into making shit work.

It's the second time sddm broke for me in the space of a week

I just disabled its service for now and am launching plasma manually.

Speaking of -- Plasma 6 hooray!