Navidrome, Feishin, Tempo.

You-Should-Use

Try JetBrains Mono.

Had similar experience with snapshots. Restore to the last working version just to find the same issue that’s been bothering me.

Then went back to the classic approach with 👻 images and Rescuezilla.

With NVME drive, it takes 7min to backup 60Gb, and 3min to restore it.

They’re actually podcasts that have RSS feeds for following new episodes. I don’t know if podcasts are your thing. They weren’t mine either, but now I put them on when I go to bed and listen to banter about Linux and FOSS. 😄

Destination Linux

Late Night Linux

It’s an issue according to any UX pattern. If something says that it’s done when it’s not, it’s misrepresenting the state of the action.

Hard to believe that modifying the counter to include the necessary time for actual writing to the flash drive would break everything. Target flash drives only etc.

System functioning as intended doesn’t mean that it’s a good UX.

Thanks! I’ll try that out today!

Why quotation marks? Issue is an issue, decades or days old. 😄

Copying mechanism itself isn’t an issue here; false reporting that something is done when it’s not is.

Thanks for the info.

I tried installing PCManFM-Qt and deleting from there. Works as you’d expect, deletes instantly.

Having NOxOn@lemmy.ml insight in mind that it’s a decades long issue, I don’t get how come that some of us are affected by it and some aren’t. 😅

Been using Tumbleweed as well. May I ask if you encountered these 2 issues:

1. Copy 1Gb movie to flash drive, says it’s done in 10 seconds. Try to remove the flash drive, still in use. Turns out it’s actually still copying.
2. Send some files, whatever the size, even 10Mb, to the trash and it takes a minute per file.

Stumbled upon some github issues saying that it’s a longstanding problem (since 2009 even), but I can’t believe that people put up with it for so long without fixing it.

I’m not even thinking of changing DE but this is annoying to say the least.

Discovered Veronica recently… ❤

Yeah, that scenario sounds awfully familiar to me as well. 😅

Even with them, it’s sometimes guesswork. Without them, it’s just stabbing in the dark. 😄

Spike’s a short period set aside to research a problem before committing to how long it’ll take to solve it.

My mentor at my first job was a mid-level dev 10 years younger than me. He was an all-around great and knowledgeable guy. When he’d get asked for an estimate on something without proper details in the ticket, he’d reply that a spike was needed before any kind of estimate, and that’s how it would usually proceed.

Sometimes, however, the PM would insist on an immediate estimate. My mentor would then, without hesitation, reply: “8 points” (a full sprint in our company).

“But why that long when you don’t know the details?”

“Exactly. Give me a spike to find out, and then it could be less.”

None of us other devs contradicted him, junior or senior, because we understood where he was coming from. Needless to say, I learned a lot from him including how not to kill myself so someone else could get a tap on the back.

Exhaustive research was conducted on an impressive sample size of… one single device.

…and the provided details are astounding.

Enjoy, people! 😊

Thanks! I’ll give it a spin. 🎠

!⬆️!< Same question? 🤔

KDE - I love to tinker and own my DE. 😎

Ventoy ⬆️⬆️⬆️