https://bugs.kde.org/show_bug.cgi?id=256856
--- Comment #21 from Michael Pyne <mp...@kde.org> --- Based on the comments that the bug is still present, and fixed by removing the icon cache, I've tried to reproduce but still cannot. I've also tried adding some debugging code to the base KSharedDataCache class, which is what uses the 'icon-theme.kcache' file. What I have seen is that sometimes changing the icon theme (from "kcmshell5 icons" or through System Settings) results in a new icon-theme.kcache which duplicates a previous theme's inode number. E.g. if I run "ls -i ~/.cache/icon-cache.kcache" (where ~/.cache is the modern location for the icon caches), I get 4589980 as the inode, then 4587597 (after changing the icon theme from System Settings), then back to 4589980. But the kernel is allowed to reuse inode numbers, and in fact reusing existing entries is even quicker than creating new inodes, which implies that we can expect this happen, as long as the kernel is satisfied there won't be mixed references into the file by accident. The debugging code I added assigns a unique ID when creating a new cache, and this unique ID *is* different each time I change the icon theme, even when the inode number is duplicated. So if you're still seeing this bug, after using System Settings to change the icon theme, then I'd have to look into something else (e.g. maybe it works on some file systems but not on others). -- You are receiving this mail because: You are watching all bug changes.
