https://bugs.kde.org/show_bug.cgi?id=465646
Thomas Carmichael <carmanau...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |carmanau...@gmail.com
--- Comment #8 from Thomas Carmichael <carmanau...@gmail.com> ---
(In reply to David Faure from comment #7)
> If I touch a desktop file in that directory, I see debug output from kded5
> appearing right away. at least stuff like "kded module [...] is already
> loaded". Do you see that too? Enable the debug area kf.kded in the
> kdebugsettings application first.
I enabled debug output for KDED and I do see the "kded module [...] is already
loaded". This output triggers whenever I change a file in
"~/.local/share/applications", but I've discovered some interesting things as
part of testing this just now. I don't know if the behavior I'm testing will be
the same for others, but it's what has happened for me and it seems to relate
to using "nano" to edit the desktop files.
In all of the testing that I've been doing, I've been using nano in a terminal
to edit my .desktop files and changes made that way has worked as expected
using GNOME (from what I remember). When I change a .desktop file with nano,
the KDED debug output is displayed, but the change is not reflected in the
applications menu, which I take to indicate that kbuildsycoca5 hasn't run.
If I use Kate or vim to edit the file instead (the only other editors I've
tested so far), I still get the same KDED debug output, but the change actually
is reflected in the applications menu, which I assume means that kbuildsycoca5
has actually run this time. Is there something different in the way nano saves
files which could be relevant here?
If I save a new .desktop file in the applications directory, that triggers an
update, so I could change one .desktop file with nano, copy in another .desktop
file entirely and it will trigger an update. Similarly, if I copy a .desktop
file over the top of the existing file it will trigger an update, which means
that I could edit a file with nano, copy the file elsewhere and then copy it
over the top of the existing file and again, an update is triggered.
So at least for me, it looks like it's generally working as expected UNLESS I
edit an existing file with nano. Again, I don't know if others will get the
same behavior, but that's what my testing has shown so far.
--
You are receiving this mail because:
You are watching all bug changes.
