This Week in Plasma brings the news that, with Plasma 6.4 little more than a week away, developers are hard at work crushing bugs and polishing the code.
In other news: The app launcher menu favorites and the networks list in System Settings are now keyboard-accessible, the Info Center’s Energy graph gets a smooth animation, and much more.
blogs.kde.org/2025/06/07/this-…
#plasma6 #FreeSoftware #opensource
This Week in Plasma: Plasma 6.4 is nigh
Welcome to a new issue of This Week in Plasma! Every week we cover the highlights of what’s happening in the world of KDE Plasma and its associated apps like Discover, System Monitor, and more.This Week in Plasma: Plasma 6.4 is nigh
dengtav
in reply to Joël de Bruijn • • •pathIn the body of your post, or?
Joël de Bruijn
in reply to dengtav • • •Original command:
gonzo-rand19
in reply to Joël de Bruijn • • •./and./*/*/*are both within your home folder, you should just restore it from your backup. The command you ran takes everything up to 3 levels deep and moves it up to the working directory, and unraveling that will be a pain in the ass.Joël de Bruijn
in reply to gonzo-rand19 • • •mv /*/*/* ./would moving stuff out of /boot or /dev folders make more sense?gonzo-rand19
in reply to Joël de Bruijn • • •enkers
in reply to gonzo-rand19 • • •/*/*/*is not a relative path. The first/references the root directory.Joël de Bruijn
in reply to Joël de Bruijn • • •crater2150
in reply to Joël de Bruijn • • •The files you listed look like they are all subdirectories from /dev, which is (usually) a separate filesystem.
When you try to move a file or directory across filesystems, the OS can't just change the link, it has to actually copy the files and then remove the original. As a directory is a set of links to files, and the copies are different files, directories are just newly created with the same name in the new location instead of copying the directory filesystem entry. It looks like
mvcreates these target directories, before it checks if it actually has permission to remove the source, but checks file permissions, before it copies themmerthyr1831
in reply to Joël de Bruijn • • •I'd probably do a clean install (eventually) even if it looked like stuff works for now.
I know the pain, though. did rm -rf in the wrong directory and wiped half my drive in seconds. Good times.
phantomwise
in reply to merthyr1831 • • •Quazatron
in reply to Joël de Bruijn • • •Mark it as an achievement on your learning path and move on. We all did something silly like that at some point.
Great that you have backups, get a fresh install and restore it.
Lessons learned: don't work as root unless you absolutely positively have a good reason to do so.
FauxLiving
in reply to Quazatron • • •