On Thursday 02 of January 2020 00:55:00 Dr. Nikolaus Klepp wrote:
Hi Slavec!
Anno domini 2020 Wed, 1 Jan 21:42:02 +0100
Slávek Banko scripsit:
On Wednesday 01 of January 2020 21:21:32 Dr.
Nikolaus Klepp wrote:
Hi Slavec!
Ok, I found one interesting thing: It looks like /opt/trinity/bin
is not in the current path on FreeBSD for TDE applications, while it
is in the path on linux. Now "kxdglauncher" cannot be executed,
which results all *.desktop files with "URL=$( kxdgdesktop ...)" to
fail and this causes TDE on FreeBSD to fail to open
"system:/documents". To be precise, these 2 file are affected:
/opt/trinity/share/apps/systemview/documents.desktop
/opt/trinity/share/apps/kdesktop/Desktop/My_Documents
So it might be a good idea to add /opt/trinity/bin to the path from
inside the TDE startup script.
Oh, I might add: I use bash on my user account on FreeBSD, too, not
csh.
Nik
The starttde startup script should ensure that /opt/trinity/bin
and /opt/trinity/games are added to PATH.
Check your ~/.xsession-errors to make sure everything seems right
there.
Found it! You are right, it is not a path-issue. It looks like a "$" is
missing in "/opt/trinity/share/apps/kdesktop/Desktop/My_Documents". The
solution for FreeBSD is simple as this:
- in "/opt/trinity/share/apps/kdesktop/Desktop/My_Documents" change the
URL from URL=$( kxdglauncher --getpath --xdgname DOCUMENTS )
to this (2x $$):
URL=$$( kxdglauncher --getpath --xdgname DOCUMENTS )
Now the desctop icon "My Documents" works as expected and so does
"konqueror system://documents" :)
Could you please test, if this works also for you?
BTW, a simillar error is present in linux. This happens on DEVUAN:
- open "konqueror system:/", click on "documents" -->
"unknown error
21929" - open "konsole", enter "konqueror system:/documents"
-->
"unknown error 21929" - changing "kxdglauncher" to
"/opt/trinity/bin/kxdglauncher" --> "unknown error 21929" -
changing
URL=$( kxdglauncher ...)" to "URL=$$( kxdglauncher...)" -->
"unknown
error 21929"
I don't know how to fix that.
Nik
> Cheers
Nik,
thank you for notifying of the problem! We can confirm it everywhere -
Debian (regardless of architecture), Gentoo,... This is related to a
recent security patch and will require some solution - for example,
doubling $, as you found out.