https://bugs.kde.org/show_bug.cgi?id=465646
--- Comment #10 from David Faure ---
Well done for this investigation.
I think it's all about whether the modification time of the directory gets
updated (which is the case when creating a temporary file, but not when
overwriting the desktop file
https://bugs.kde.org/show_bug.cgi?id=465646
--- Comment #9 from Thomas Carmichael ---
I've done some additional testing that may help provide more useful context.
Looking into how nano saves files, I'm wondering if the way the
"~/.local/share/applications" directory is watched, or how the files
https://bugs.kde.org/show_bug.cgi?id=465646
Thomas Carmichael changed:
What|Removed |Added
CC||carmanau...@gmail.com
--- Comment #8 from
https://bugs.kde.org/show_bug.cgi?id=465646
--- Comment #7 from David Faure ---
Actually, kded5 does appear to install a watch on that directory (among
others), in readDirectory().
I wonder if that's what plasma is relying upon. Probably.
If I touch a desktop file in that directory, I see debug
https://bugs.kde.org/show_bug.cgi?id=465646
--- Comment #6 from David Faure ---
~/.local/share/applications isn't "watched" (in the sense of inotify) (we used
to do that, and it was a lot of trouble due to inotify limits (kdevelop or
qtcreator easily used up all inotify watchers) -- plus, what
https://bugs.kde.org/show_bug.cgi?id=465646
--- Comment #5 from Barnaby ---
(In reply to Nate Graham from comment #3)
> I think this situation falls into the "I know just enough to hurt myself"
> valley. :)
>
> If you know the technical details about what .desktop files are and the
> hidden
https://bugs.kde.org/show_bug.cgi?id=465646
Barnaby changed:
What|Removed |Added
CC||barn...@waterpigs.co.uk
--- Comment #4 from Barnaby
https://bugs.kde.org/show_bug.cgi?id=465646
Nate Graham changed:
What|Removed |Added
Summary|Add UI affordance for |Run kbuildsycoca5
|reindexing
