Alright, let’s get into the nitty-gritty of Duckpower.

First, let's settle the "waddling vs. flying vs. swimming" debate. Horses aren't big on flying, so we’re talking waddling power here. Until someone locates a Pegasus, we're limited to the traditional land-bound horsepower. If you want swimming power, I guess you’d need to measure a seahorse?

Now, here’s where it gets serious: according to the brilliant minds at Art of Engineering, we can calculate Duckpower using a clever formula. They took the mass of a duck, compared it to a horse, and ran it through Kleiber’s Law. The answer? One horsepower = 131.2 Duckpower. So, back to our math:

3 horsepower = 3 x 131.2 Duckpower = 393.6 ducks waddling their hearts out.

But wait! We probably don’t need all 393.6 ducks if we give them some solid shift schedules. Horses only get 3 HP so two can rest; following this logic, we’d only need around 100 well-rested ducks, provided they get naps and stay hydrated.

So, let’s optimize our duck workforce with a shift schedule. Assuming we only need 100 ducks, here’s the plan:

Duckpower Shift Schedule:

Total Ducks: 100

Working Ducks per Shift: 25

Shift Duration: 2 hours on, 6 hours off (plenty of time for snacks and naps)

In a day, we’d run 4 shifts like this:

1. Shift 1: 25 ducks start strong at 8:00 AM, waddling with purpose.

2. Shift 2: Fresh 25 ducks take over at 10:00 AM while Shift 1 ducks hit the ducky lounge for snacks and a nap.

3. Shift 3: At 12:00 PM, another 25 ducks clock in to keep those wheels turning.

4. Shift 4: Finally, at 2:00 PM, the last 25 ducks take over while the others catch up on R&R.

With this cycle, each duck works only 2 hours out of every 8, staying energized, waddling at peak efficiency, and ready for action.

TL;DR: 3 horsepower = 393.6 ducks waddling but if we set up a 4-shift system, we can pull this off with only 100 ducks working 2 hours each, plus snack breaks.

3 horses = 3 horsepower, which translates to a whopping 393.6 Duckpower.

Honestly, why are we still using horses as the standard here? Ducks are clearly the superior metric. So if you're like me and prefer a more feathered approach, just remember:

3 horses = 3 horsepower = 393.6 ducks You’re welcome.

(PS: Just imagine 393.6 ducks handling 10Gb... now that’s efficiency.)

That's true, but long press on the power button still works, so you can try that instead then? 🙂

does this happen if you force it to shut down by holding the power button for +10sec, or if you remove and reinsert the battery after power off?

forcing a shutdown or removing and installing the battery, will ensure that the laptop is indeed shut down and not just halting during the shutdown process.

if you still have the same issue after this test I would guess your battery is dying, but if not you know that the issue is a software and not a hardware problem..

anyway, best of luck getting it sorted

do you have any usb devices, like external hard drives, chargers or similar connected to it? a lot of the laptops allows for usb charging/supply of power even when switched off, and this could be one of the sources for the drainage.

try disconnecting all USB cables if any are connected and see if the problem disappears?

never mind, did not see the line about no connected usb cables until after posting

so, without this app, it will only be telemetry and ads? 🤔

Haven't tried it myself, but there is cheap converters available on AliExpress:

https://a.aliexpress.com/_EwYtdeV

Might be worth it to avoid using it as a paperweight?

thank you :)

not to be that guy . but have you tried to search for an answer?

https://github.com/flatpak/flatpak/issues/4435

first hit on "flatpak question marks".. it's due to the font you use in the terminal does not support or not fully support Unicode characters.

hope this helps and answers your question :)

probably the disk UUID has changed because of the path to the NVMe vs SSD. If you use partition UUID, they will be exactly the same, but the UUID of the physical disk is not cloned, as it is a identifier of the physical device and not it's content.

change it to partition UUID and it will boot.

one way that works for some is to trick your mind by schedule your worrying to a time and date in the future and tell yourself you will handle it then. this gives you a "solution" for your mind to stop worrying about it now, as you have a plan to do it later..

worked for me quite a few times actually..

good luck, and hope you get it sorted eventually either way.

try holding the off button on the remote for x-number of seconds, that works for mine, so perhaps it works for yours as well? mine is also Samsung but different model.