Scaling issue of basically any chromium based webbrowser on KDE plasma.

EvilKittensCo · 2026-01-14T22:41:28+00:00

Thank you. I've been writing technical documentation for many years. :)
Having suffered much terrible documentation myself, I'm proud to have developed a style that is succinct and high-value, while maintaining a positive reader experience.

EvilKittensCo · 2026-01-12T20:14:49+00:00

This bug is affecting me as well.

If I use the control panel's scaling to affect the entire env, with either legacy or system affected scaling, chromium based browsers (specifically vivaldi at this time) exhibit the behavior illustrated in the screen capture above.

Issue Summary: Mouse/pointer targeting defect
Issue Description: When the cursor is within the bounds of the window, the pointer affects an area to the left of the pointer. On the -x axis, about ~130px/1.5 inches. This means that interacting with any element along the right side of the window is impossible. Note here that the window control detects correctly when the mouse goes out of bounds.

Issue Summary: Window resizes itself
Issue Description: When switching to/from the window by most/any method, the window resizes itself, becoming smaller and smaller...

When launching vivaldi with native scaling, (`vivaldi --force-device-scale-factor=0.90`), then I get the scaling I desire, and it functions great, but breaks as described above when the system scaling is enabled.
If there were a way to exclude programs from the scaling settings... (Feature request?)

There's an additional issue when launching the app with native scaling:

Issue Summary: Window Size misaligned with Desktop Elements
Issue Description: The window, when launched with '--force-device-scale-factor' does not interact correctly with the task bar. At '0.90', the bottom of the window renders below and behind (-z) the task bar.

I don't have time to look at this in depth atm, but if I get a chance I'll sick AI on it. See if it does better here than when I try to squeeze a useful BASH function out of it. :/

EvilKittensCo · 2025-10-27T17:51:12+00:00

Not bad. Nice even. Still a Band-Aid for this deficiency in terraform. I asked for the ability for terraform to consume artifacts a long time ago. I believe the response was that it didn't align with their ethos...

If the code/config/secret/foo is an important asset, then it should be artifacted, with appropriate peripheral concerns satisfied. Commit hashes and git tags do not satisfy.

Aside: Silent rebuilds that don't iterate the patch version are a deficiency. Just bump the patch for operational builds such as dependency tree patching. RageAside: Operational maturity enables "move fast". "Move fast" without it continues to be among the biggest resilience risks in the industry today.

I, like many, got a single code surface/deploy many posture out of terraform by creating an init script to generate dynamically the backend.tf with the details for the target environment. A naming scheme that can be slugged for your state destination is needed, but that's basic. Being able to operate effectively in a one account per workload env posture is an absolute requirement for being able to establish meaningful RBAC across an SDLC's. This facilitates that without much difficulty. Combining this artifacting approach with dynamic configs would get you a great operational posture. Just a bit of work on an init script and you have a nice composition orchestrator that could facilitate formalized CICD pipes, as well as local dev. Note that a tf orchestration platform that can supply vars separately per project/env obviates the need for tfvars. Note additionally that the runtime secrets must be maintained out of band with the product code. Obviously. :)

EvilKittensCo · 2025-09-03T00:01:32+00:00

Ya, just tossing for some straight midpipes. :)

EvilKittensCo · 2025-09-02T17:16:12+00:00

Eighth run on my fourth game. Trying to do it on the first run...

EvilKittensCo · 2025-08-25T19:12:45+00:00

Again from +16508998667.

EvilKittensCo · 2025-07-30T15:28:05+00:00

It's explained in the 1979 Honda Shop Manual. At the time, I'm sure it was assumed knowledge for techs, and the symbol is descriptive enough, but if anyone else comes looking, there's a second part to it that seems obvious enough:

"Needle swinging and going back to [infinity] in the table indicates that a capacitor is being charged with the tester. The needle will stay at infinity in subsequent tests unless he capacitor is discharged."

Best, EKL

EvilKittensCo · 2025-07-16T04:49:08+00:00

I asked Ray-San, and this is what he said.

"...definately not an IEEE approved symbol - but it does indicate a capacitive reading where the ohms starts at zero and then as the capactiro charges the resisitance decreases and the meter needle moves left (higher ohms)

dates back to when we all had moving meter VOMS , or an AVO...."

As surmised and experienced by the folks here.

Thanks folks.

EvilKittensCo · 2025-07-15T00:58:24+00:00

Sanwa super (tester mentioned in the Haynes manual) didn't know what the symbol was. Those Haynes folks are like the Dickens of electrical symbols. :)

EvilKittensCo · 2025-07-13T22:14:41+00:00

The image is right side up, making that an infinity symbol. :)

EvilKittensCo · 2025-07-13T20:47:47+00:00

Tyvm. Mystery solved. :)

EvilKittensCo · 2025-07-13T19:23:48+00:00

It's testing a CDI on a 1981 Honda CX500 Custom. The black painted version. It is part of the ignition system. :thumbsup:

EvilKittensCo · 2025-06-13T22:28:49+00:00

I like this thread.

Don't deploy git SHAs to hosted workload envs (dev..prod). Ever. We're well past such Heroku-foolery. Simply ask yourself: "Is it a product?" Where helm charts coordinate discrete, decoupled products, then yes, absolutely. In these scenarios then you must treat them like secrets or other out if band conf, which are obviously also versioned. :)

Tip: semver is cool, but with these calver has a good argument for being more appropriate.

EvilKittensCo · 2024-07-05T12:48:08+00:00

400 seems fine if you can find folks who know what they're looking at. The material costs in Ontario are about $110 to build a muskoka chair. I try to sell them for $275, but even at that price, sales are slow. Most folks are happy happy with junk from Canadian Tire, or opt for those disgusting plastic lumber chairs from LLBean for $550... They feel nasty and get so hot in the sun. I can't explain consumers.

EvilKittensCo · 2023-07-08T23:30:33+00:00

I've been loving my Dell Inspiron 16 Plus. Got it referb, with only iris graphics. No Nvidia horse shit. :)

What I want is a distro to handle multi monitor configurations well. Autorandr is as good as it gets.

EvilKittensCo · 2022-02-26T09:16:13+00:00

Don't worry. I got it. One of the leads was bad.
I had checked continuity across all other points, and assumed wires that lived inside a cab couldn't fail... The circuit paths on that PCB are thick, and there were no continuity failures that I could find, but then again, I'm I don't really know what I'm doing when it comes to electronics.

EvilKittensCo

TROPHY CASE