Tip: The YD-RP2040 isn't 100% compatible with name-brand Raspberry Pi Pico boards. If you need to build something that has it acting as a USB host, prepare for the slightly fiddly job of tacking a piece of resistor leg between the two legs of a BAT54C barrier diode facing the USB C connector to allow current from Vin to flow to the USB connector... also, the (VBUS) and (VSYS) silkscreens on the bottom are wrong. Vout is *not* VBUS. Follow github.com/initdc/YD-RP2040/bl

I **REALLY** wish "why did that happen?" help/logs were standard. I spent months frustrated that the hand-me-down iPhone I use as a WiFi eReader had started spontaneously toggling the flashlight and/or the rotation lock with the last iOS update and then I serendipitously discover that it can be fixed by turning off a "tap on the back of the phone" feature I never knew existed. (No clue why it's triggering when I use the Otter Box's belt holster as a phone grip, but whatever)

Tip: If you get an MMSYSTEM262 error from The Incredible Toon Machine and no CD music and you have more than one CD drive (eg. physical and DAEMON Tools or Alcohol 52% Retro Edition), the fix is probably to go into
Control Panel
→ Multimedia
→ Devices
→ Media Control Devices
→ CD Audio Device (Media Control)
→ Properties
→ Settings
... and change "Default CD-ROM drive for playing CD music".

Tip: If you're getting strange read/write errors or "sharing violation"s when running "make boot disk" tools/batch files in 86Box and you're using the Flatpak version, create your floppy disk images inside ~/.var/app/net._86box._86Box/ or grant a manifest permission. Apparently there's a bug or incompleteness in the Flatpak documents portal FUSE filesystem.

Generally, I think they all fall under "It looks like a mobile app that's pretending to be a desktop app (the "Window settings for firefox" header, the part that darkened, and the modal) has been embedded in a frame inside a native QWidget app (the window decorations and the action buttons at the bottom) and you can tell.

Show thread

...maybe it's a mix of the inconsistent font size and the way the modal isn't centred on the darkened region and evokes memories of X11 top-level windows when the window manager has died.

Show thread

...but yeah. As an end-user, all I can say is "you KNOW when something is written in Kirigami because it's got that nagging ugliness to it that you lack the UI design skill to diagnose, but you can sense".

Just upgraded from Kubuntu 20.04 LTS to 22.04 LTS... I suppose, if KDE is going to slowly migrate to a technology like QML that, even in Kirigami, is a leaky abstraction over an Android UI toolkit, it's at least good that it forces them to ship uncompiled QML that I should easily be able to patch to un-tablet-ify the calendar widget's font size. (Though that does mean I'll have to be careful about what I Flatpak, given its designed hostility to ad-hoc end-user patching.)

Just got OPNsense set up. If you're on TekSavvy DSL, following docs.opnsense.org/manual/how-t then restarting your router and disconnect/reconnect cycling LAN devices will WORK to get you IPv6 (you may need to toggle Firefox's DoH to get fallback working on ipv6-test.com/ )... but it won't get you ICMPv6. Follow homenetworkguy.com/how-to/conf for that but set "any" as the destination address instead of "WAN address" or it won't work.

Tip: If you're setting up systemd sandboxing for a libusb-based daemon, you'll need to allow AF_NETLINK sockets (eg. RestrictAddressFamilies=AF_NETLINK) if you want it to work... I'm still trying to figure out a working DeviceAllow string for my CM19A so I can go back to the DevicePolicy=closed and PrivateDevices=yes I was using with my CM17A.

Show more
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.