Hi All,
I am experiencing some autostart issues:
* Certain $HOME/.config/autostart desktop files fail to launch. * XDG NotShowIn is not honored in user XDG files.
Related files seem to include:
* tdelibs/tdeinit/autostart.cpp * tdelibs/tdecore/kdesktopfile.cpp * tdelibs/tdeio/tdeio/kservice.cpp
I found two related bug reports (2284, 2297).
------------
For the first issue, digging deeper indicates perhaps the Exec= directive in autostart desktop files is not parsed explicitly. Rather than execute the entire line in the Exec= entry, the code seems to be based on a presumption of only expecting traditional path strings. This means desktop files with 'Exec=/bin/sh -c' snippets fail to launch. I have a few such files and this took me a long time to identify.
For a long while I thought the files were being ignored. Instead they fail to launch. One clue was in the user .xsession-errors log that TDE was unable to parse the Exec= entries.
One work-around is convert the 'Exec=/bin/sh -c' snippets to shell script files. Doable but these snippets function as expected in other desktop environments. I suspect the code with other DEs is executing the entire Exec= line verbatim rather than trying to parse an executable from a presumed path. So this seems to be a TDE issue.
I'll file a bug report for this problem if I receive confirmation.
------------
I think the NotShowIn issue is caused by code that tries to remove duplicates in the collected list of autostart files. I addressed that issue in bug report 2297. Basically the user files are being removed as duplicates and never execute, creating the illusion of being ignored.
Thoughts?
Thanks for your time!
D.A
On 2023/02/01 10:41 AM, Darrell Anderson via tde-devels wrote:
Hi All,
I am experiencing some autostart issues:
<snip..>
For the first issue, digging deeper indicates perhaps the Exec= directive in autostart desktop files is not parsed explicitly. Rather than execute the entire line in the Exec= entry, the code seems to be based on a presumption of only expecting traditional path strings. This means desktop files with 'Exec=/bin/sh -c' snippets fail to launch. I have a few such files and this took me a long time to identify.
For a long while I thought the files were being ignored. Instead they fail to launch. One clue was in the user .xsession-errors log that TDE was unable to parse the Exec= entries.
One work-around is convert the 'Exec=/bin/sh -c' snippets to shell script files. Doable but these snippets function as expected in other desktop environments. I suspect the code with other DEs is executing the entire Exec= line verbatim rather than trying to parse an executable from a presumed path. So this seems to be a TDE issue.
I'll file a bug report for this problem if I receive confirmation.
I think the NotShowIn issue is caused by code that tries to remove duplicates in the collected list of autostart files. I addressed that issue in bug report 2297. Basically the user files are being removed as duplicates and never execute, creating the illusion of being ignored.
Thoughts?
Thanks for your time!
Hi Darrell, I can confirm the problem with Exec string composed by multiple parts. Yes, please create an issue on TGW (gitea). If the fix is easy, it may get into R14.1.0, if it takes longer it may end up in R14.1.1 6 months later. I have taken note of those two bugs you mentioned. Definitely deleting files as described there is not the correct thing to do. I will look into them by R14.1.1.
Cheers Michele
On 1/31/23 8:56 PM, Michele Calgaro via tde-devels wrote:
I can confirm the problem with Exec string composed by multiple parts. Yes, please create an issue on TGW (gitea). If the fix is easy, it may get into R14.1.0, if it takes longer it may end up in R14.1.1 6 months later. I have taken note of those two bugs you mentioned. Definitely deleting files as described there is not the correct thing to do. I will look into them by R14.1.1.
What is the road map / time line for R14.1.x?
On 2023/02/01 12:20 PM, Darrell Anderson via tde-devels wrote:
On 1/31/23 8:56 PM, Michele Calgaro via tde-devels wrote:
I can confirm the problem with Exec string composed by multiple parts. Yes, please create an issue on TGW (gitea). If the fix is easy, it may get into R14.1.0, if it takes longer it may end up in R14.1.1 6 months later. I have taken note of those two bugs you mentioned. Definitely deleting files as described there is not the correct thing to do. I will look into them by R14.1.1.
What is the road map / time line for R14.1.x? ____________________________________________________ tde-devels mailing list -- devels@trinitydesktop.org To unsubscribe send an email to devels-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/devels@trinitydeskt...
R14.1.0 will be the next release, so end of April pending unforeseen last minute blockers. Then there are maintenance releases every 6 months. Cheers Michele
On 1/31/23 10:08 PM, Michele Calgaro via tde-devels wrote:
R14.1.0 will be the next release, so end of April pending unforeseen last minute blockers. Then there are maintenance releases every 6 months.
What is unique about this major point release (R14.1) rather than another minor point release (R14.0.14)? ABI/API changes? Renaming? Etc.
Thanks.
On 2023/02/02 10:41 AM, Darrell Anderson via tde-devels wrote:
On 1/31/23 10:08 PM, Michele Calgaro via tde-devels wrote:
R14.1.0 will be the next release, so end of April pending unforeseen last minute blockers. Then there are maintenance releases every 6 months.
What is unique about this major point release (R14.1) rather than another minor point release (R14.0.14)? ABI/API changes? Renaming? Etc.
Minor release comes with API/ABI changes, while maintenance release don't. There are several changes and a list of them will be part of the official release notes of the release. Cheers Michele
On Thursday 02 of February 2023 04:40:22 Michele Calgaro via tde-devels wrote:
On 2023/02/02 10:41 AM, Darrell Anderson via tde-devels wrote:
On 1/31/23 10:08 PM, Michele Calgaro via tde-devels wrote:
R14.1.0 will be the next release, so end of April pending unforeseen last minute blockers. Then there are maintenance releases every 6 months.
What is unique about this major point release (R14.1) rather than another minor point release (R14.0.14)? ABI/API changes? Renaming? Etc.
Minor release comes with API/ABI changes, while maintenance release don't. There are several changes and a list of them will be part of the official release notes of the release. Cheers Michele
You can see the current list of merged PR in TGW as well as a detailed list of commits that are part of R14.1.0 (and not backported to R14.0.x). Lists are usually updated once a week. In terms of renaming, there were now greater changes in integration with Python - sip-tqt, PyTQt, PyTDE.
https://mirror.git.trinitydesktop.org/gitea/TDE/tde/issues/3 https://wiki.trinitydesktop.org/Changelog_For_R14.1.0
Cheers
On 2/2/23 2:46 AM, Slávek Banko via tde-devels wrote:
You can see the current list of merged PR in TGW as well as a detailed list of commits that are part of R14.1.0 (and not backported to R14.0.x). Lists are usually updated once a week. In terms of renaming, there were now greater changes in integration with Python - sip-tqt, PyTQt, PyTDE.
https://mirror.git.trinitydesktop.org/gitea/TDE/tde/issues/3 https://wiki.trinitydesktop.org/Changelog_For_R14.1.0
That helps! Thank you.
On 1/31/23 8:56 PM, Michele Calgaro via tde-devels wrote:
I can confirm the problem with Exec string composed by multiple parts. Yes, please create an issue on TGW (gitea). If the fix is easy, it may get into R14.1.0, if it takes longer it may end up in R14.1.1 6 months later. I have taken note of those two bugs you mentioned. Definitely deleting files as described there is not the correct thing to do. I will look into them by R14.1.1.
Bug report created:
https://mirror.git.trinitydesktop.org/gitea/TDE/tdelibs/issues/188
-
Darrell Anderson -
Michele Calgaro -
Slávek Banko