https://bugs.kde.org/show_bug.cgi?id=469445
--- Comment #36 from pallaswept <pallasw...@proton.me> --- (In reply to Nate Graham from comment #35) > Non-existent items get removed for me. TL;DR: Try harder, because it's a thing. Remember that my original reason for being here was that I had built a software package on the desktop, and the files had since been deleted, but their entries were still there in the list in the config file. That was what caused the crash that brought me here. Like I said, I ha ve backups, I could restore them and spend a week trying to figure out exactly what I did, but let's be reasonable here. I didn't come here just for your good looks :) The failure to remove deleted files from the list in the config file is literally why I'm here. If it had added all the subdirectories (the thing that's just been patched) and then cleaned up after itself, there'd have been 4 entries in that list in the config file and the crash would have never happened. Certainly, deleting them in certain ways causes them to be removed Certainly, deleting them in other ways causes them not to be removed If you can't reproduce the failure to remove files and have them remain in the list in the config file, try harder :D Because it's a thing. It was in my first post for a reason. Just as it was for the file being added to the list in the first place - remember all the people who copied lots of files to the desktop and didn't get any entries, and said "hey I can't reproduce this" (including the man who write the fix we have now that fixes exactly what he couldn't reproduce!), but meanwhile all the reports of people with source code that was being added as subdirectories? This is that, in reverse. Sometimes you add the files and KDE knows about it and adds them to the list, sometimes you add them in some other way and it doesn't add them to the list. Sometimes you remove the files and KDE knows about it and removes them from the list, sometimes you remove them in some other way and it doesn't remove them from the list. > If you have a reproducible way to make that happen, it would be good to > submit a new bug report that indicates how you can reproduce it. Are we really going to start all over with the "I can't reproduce it, it isn't a thing", thing? It's a thing. I swear. If it weren't, I would never have even had the crash that led me to create this account to make that post that started off by explaining that it's the 2nd half of the problem. > in general this feature works, and any issues with it are edge case bugs. The feature that *does* work, is that when KDE sees it get removed, it removes it from the list. The feature that *doesn't exist*, is checking that entries which are in the list, have not been removed. There's no check to make sure it didn't miss something. That's why, when my software I built from a directory on the desktop, created thousands of files (downloading python and rust dependencies for the package I was building), and subsequently deleted them as part of the build script, and KDE didn't notice, those entries stayed in the list, and my PC crashed the next time I rebooted, and that's why I'm here. It's a thing. Reproducing it might be tricky, I get it.... but let's not pretend it's not a thing, and that there isn't a 'trap' there, where if, for some inexplicable reason, KDE fails to remove a non-existent file from the list, **it will never check to make sure it removed everything it should have.** -- You are receiving this mail because: You are watching all bug changes.
