21 May
2021
21 May
'21
7:19 a.m.
On 2021-05-20 00:08:12 Michele Calgaro via tde-users wrote:
On 2021/05/20 12:38 PM, J Leslie Turriff wrote:
So. Really, what I'm looking for is NOT an 'in brief' explanation, but a
comprehensive
one. I have searched through the archive and found various instructions for
'fixing' the
problem, but no explanation of what exactly this script is doing.
Most of the fixes are to merely remove lines from
~/.config/menus/applications-tdemenuedit.menu containing kde-*.desktop filenames. Okay,
easy enough, but what if some of them refer to valid KDE4/5 applications?
Some also say to check the contents of ~/.local/share/applications/ as well, but
don't
say what to do there. That directory appears to be full of *.desktop files. Maybe
rename them? Delete them? But again, what then happens to KDE4/5 applications that they
might refer to? (On my system there is also a ~/.trinity tree and a ~/.kde tree; do
these participate in the process?)
Another says to remove file /var/tmp/tdecache-$USER/r14-xdg-update-validation-test9.txt
We need some background information in order to make sense of this problem, because it
keeps coming back over and over. A fix that only works until the next TDE upgrade is no
fix at all, IMO. Please help us mere end-users, who aren't privy to the inner
workings
of the menu subsystem, to understand how all the pieces of this puzzle fit together to
cause the problem.
Leslie
--
openSUSE Leap 15.2 x86_64
Qt: 3.5.0
TDE: R14.0.9
tde-config: 1.0
On 2021-05-19 06:58:51 Stefan Krusche via
tde-users wrote:
In brief, test9 fails if applications named kde-* are found in the TDE
start menu config file. Renaming them to tde-* will remove the warning
message.
For more details, the ML archive definitely has more info from previous
discussions.
Cheers
Michele You can find the relevant information in the
archive of this ML. It's
been discussed at least two times already.
More than two, I think; but I have seen nothing that explained the
mechanism, just statements to delete vaguely-defined lines from a
poorly-described file.
A page in the wiki would be nice to have. Someone
has to write it.
Yes, as I said; someone who understands exactly what it is/does and how
it works.
> Kind regards, Stefan