# Autostart of the flatpak desktop client does not work **URL:** \ **Category:** 📱 Desktop & mobile clients\ **Created:** [March 21, 2023, 11:18pm UTC](https://help.nextcloud.com/t/autostart-of-the-flatpak-desktop-client-does-not-work/158281 "2023-03-21T23:18:37Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Kuchenmampfer](https://help.nextcloud.com/letter_avatar/kuchenmampfer/32/6_22734026db12803ebb3e059622ac3534.png) [@Kuchenmampfer](https://help.nextcloud.com/u/Kuchenmampfer)\ **Post date:** [March 21, 2023, 11:18pm UTC](https://help.nextcloud.com/t/autostart-of-the-flatpak-desktop-client-does-not-work/158281/1 "2023-03-21T23:18:37Z")
Hi, I am using the desktop client as a flatpak on kde and enabled autostart long ago, but it never started. All the gui options said it was enabled, so I started digging a little bit deeper today. I found in the arch forum, that the autostart functionality defined by XDG places `.desktop` files into `~/.config/autostart/`. So I looked there and found a file `com.nextcloud.desktopclient.nextcloud.desktop`. This looked all well and good, but the `Exec` line said `Exec="/app/bin/nextcloud" --background` which did not work because the client is installed as a flatpak and not in `/app/bin/nextcloud`. So I changed that line to `Exec=flatpak run com.nextcloud.desktopclient.nextcloud` and everything worked fine. I am not sure why this was wrong and where to report it, but I guess if I post it here, it will reach the right person. ---
**Author:** ![bb77](https://help.nextcloud.com/letter_avatar/bb77/32/6_22734026db12803ebb3e059622ac3534.png) [@bb77](https://help.nextcloud.com/u/bb77)\ **Post date:** [March 22, 2023, 1:45pm UTC](https://help.nextcloud.com/t/autostart-of-the-flatpak-desktop-client-does-not-work/158281/2 "2023-03-22T13:45:37Z")
Not really an answer to your question, but why not just use the package from the Arch community repos? It gets regularly updated and you even get the status icons, if you are using one of the supported file managers… [https://archlinux.org/packages/community/x86\_64/nextcloud-client/](https://archlinux.org/packages/community/x86_64/nextcloud-client/) ---
**Author:** ![Kuchenmampfer](https://help.nextcloud.com/letter_avatar/kuchenmampfer/32/6_22734026db12803ebb3e059622ac3534.png) [@Kuchenmampfer](https://help.nextcloud.com/u/Kuchenmampfer)\ **Post date:** [March 22, 2023, 3:41pm UTC](https://help.nextcloud.com/t/autostart-of-the-flatpak-desktop-client-does-not-work/158281/3 "2023-03-22T15:41:41Z")
Not answering my question is fine since I made the autostart working and this post was more meant as “Hey, I think this is a problem with the flatpak, but don’t know where to report it”. However, having status icons is indeed _very_ nice, so I think I will switch to the arch package. So thanks for the suggestion 👍 ---
**Author:** ![edosecco](https://help.nextcloud.com/letter_avatar/edosecco/32/6_22734026db12803ebb3e059622ac3534.png) [@edosecco](https://help.nextcloud.com/u/edosecco)\ **Post date:** [April 14, 2024, 10:19pm UTC](https://help.nextcloud.com/t/autostart-of-the-flatpak-desktop-client-does-not-work/158281/4 "2024-04-14T22:19:16Z")
I experienced troubles making the Linux desktop client start sync on boot, on Zorin and Mint (the one I’m on now). The app starts on boot but it gets stuck on “not online” status. I’m also sure that the password key-ring is running on boot too! The sync starts automatically only on pc reboot. Really strange. Let’s say that Dropbox app (flatpak too) has no problems. This is what I see in the autostart file: [Desktop Entry] Categories=Utility;X-SuSE-SyncUtility; Type=Application Exec=/usr/bin/flatpak run --branch=stable --arch=x86\_64 --command=nextcloud --file-forwarding com.nextcloud.desktopclient.nextcloud @@u %u @@ Name=Nextcloud Desktop Comment=Nextcloud desktop synchronization client GenericName=Folder Sync Icon=com.nextcloud.desktopclient.nextcloud Keywords=Nextcloud;syncing;file;sharing; X-GNOME-Autostart-Delay=10 MimeType=application/vnd.nextcloud;x-scheme-handler/nc; Actions=Quit;