Minisforum makes good stuff, but only buy their Refurbished items if you don’t need something specific.

Lots of people buy Beelink minipcs for n100 boxes, but looks like the prices are all jacked right now. [This should only be about $150 maybe.](https://www.newegg.com/beelink-barebone-systems-mini-pc-intel-n95/p/2SW-0012-001Z2?Source=socialshare

I wouldn’t use an old MacMini for much because they aren’t actually power efficient, but any n100 for Ryzen5 minipic with Kodi on it would work just fine for you want. There are plenty of altern6to Kodi, but it’s so simple, it’s hard to pass up.

(diarrhea noise)

(diarrhea noise)

The only reference people have for these kind of judgements is polling by browser.

You’re talking about users of a specific OS who would spend time to not make that known. They would also opt-out if any reporting about there machine specifics for polls, should they be asked.

I can guarantee real world usage is always higher than these polls suggest. I don’t know about 10%, but they are higher in actuality.

Look up the model of the laptop, and try to find a “display voltage regulator”. Sometimes they sell them a setnfor cheap.

This isn’t a software or OS issue though.

Try using your CMOS’ EFI boot manager and see if it sees both. If so, just skip Grub and use that.

If you’re saying you started on Gnome, then dropped in another DE, you need to switch to an agnostic network manager if you were relying on Gnome’s Desktop Network manager implementation probably.

If you’re saying you booted a clean Fedora Cosmic LiveUSB and couldn’t get WiFi working, you need to look at logs or run through some cli debugging to see what’s up. Probably just Cosmic issues.

Edit: forgot about nmtui. You can use this to debug issues from the clinpretty simply if the desktop tools are failing.

Sounds like this is an older laptop perhaps? Probably the voltage regulator for the display panel not coming back on cleanly.

Try this:

1. Trigger the issue
2. Once the issue starts, turn your brightness ALL the way up and see if it stops
3. If it does, then lower it back down to whatever level seems appropriate

See if that does anything.

Not trying to shit on your idea here, but this is actually going to make your systems much less performant in a number of ways. Let me explain why.

The Linux kernel memory scheduler is extremely good at what it does. It’s probably the reason why Linux crushed adoption into the server market so rapidly 20+ years ago. Not only is it fast, it’s super smart.

The process scheduler is also top-tier, with BSD only sliiightly maybe winning out in some edge cases because it takes more resources into consideration when planning executions. This is why BSD wins out in the network performance category so often (until very recently).

All of that to say, if you have enough memory to hold whatever you need to run in memory, everything runs great. Cut to you not having memory, and needing to swap.

Once swap enters into the fray, the performance of both memory and process scheduling drops exponentially depending on the number of running processes. For each extra process needing more memory, the rest of the system takes a hit from the interrupt needed to find and clear cached pages, or allocate swap. This is called Memory Contention.

Memory Contention engages a whole host of different levera in various parts of the kernel. The more you have, the more CPU cycles you use to solve for it, and you also increase wait time for everything in the system from I/O interrupt at the process scheduler.

What you’re doing by enabling BOTH swap and zram in the way you are increasing the workload of the kernel by a factor of two, so twice the amount of effort at the CPU, and twice the amount of I/O wait when contention comes into play. It’s just not performant, and it’s wasting energy.

They both deal with swap, just either at the disk or available allocated RAM space, and you’re just making your machine do extra work to figure out where it should be swapping to.

Well poking around, it seems that specific plugin was only meant for Gimp 2.10, and you must be on 3.0+ by now, so I would consider it unusable.

I don’t think you need to directly edit the script if that’s what you mean. You want to edit the values in the plug-in menu so it’s not out of bounds. Those get passed to the script, which then executes.

You probably need the direct error instead of this raised exception. Start Gimp from a terminal, trigger the error, and see if the terminal error is showing exactly what the script’s error is.

It’s having an issue with a value. This explains it so I don’t need to write a novel: https://gimpchat.com/viewtopic.php?f=9&t=6756

Some of the default values in Gimp Scripts are bad, and it’s kind of a crapshoot.

It’s a week known fact that Al Yankovic is a well known activist against open source everything. He started a ranting campaign against it in the early 80’s.

Weird Al Yankovic is the patron saint of everything open source. He also eats Corn Dogs like a fucking monster.

Chrome is dead

Nah, it works fine just with ARM builds, but that’s not the point of the SoC. GPU acceleration, security features, and offloading co-processors all need drivers to work properly.

Ubuntu 25+ has specific optimizations for these chips, but last I heard performance was pretty weak due to Qualcomm refusing to open their drivers and optimizations.

Fedora 44 also has some specific optimizations for these chips.

You don’t need to format the drive if you’re writing from an image.

Install Balena Etcher (also available in Gnome Software), select the ISO you want to write from, and the target USB drive, write it, then it’s usable.

Yeah, see my edit. This is a Pipewire session thing. Each user needs a unique Pipewire session to do audio. Video has nothing to do with Pipewire.

Check the groups the working user is included in, and make sure the non-working user is in those same groups. See if anything there.

Edit: Oh, you know what. I think this is probably Pipewire not starting for multiple users when multiple are logged in. On the non-working user, you need to start a unique Pipewire session for that user, because the other working user’s session can’t be shared by default.