I also hit f12 to view the logs, and there was nothing there. I double-checked that the program was in my startup applications, and it is. I even tried to create a @reboot cron job for it. Nothing seems to get it going on boot.
This is frustrating because I often make changes on my desktop and my phone, and if the client doesnāt auto-start, then Iām more likely to have conflicts.
It worked for me as well!
exec Path was pointing to something like
Exec=/tmp/.somethingā¦/usr/bin/nextcloud
After setting it to Exec=/usr/bin/nextcloud
it worked.
Same problem with v 3.11 (I infer from clicking on āHelpā and landing on the v3.11 help web page; the client has another bug where the āinfoā panel in the settings is empty).
No flatpak and correct path.
I can easily run Nextcloud manually from a console and which nextcloud shows the same path as the one in the generated desktop entry file.
The other desktop entries in the autostart folder run fine and have the same permissions and owner.