After many years of absence, I am trying to get back into soulseek using Nicotine+.
Installed it through Flatpak on a debian based system. Application seems to work fine... except: clicking the "Add" button on the Shares pane of the settings menu does nothing. No dialog opens, no error message is shown, just nothing. Is it a known bug with an easy fix?
EDIT / SOLVED: appearantly when one logs into a remote desktop session, the file picker sometimes crashes. For anyone encountering same issues: login directly instead of remotely, or use suggested solve: https://discussion.fedoraproject.org/t/file-chooser-does-not-open-for-flatpak-applications-f40-sway/126351/4

7 Comments
pipes@sh.itjust.works · 3 pts · 1y
You need to give Nicotine's flatpak permission to access what you want to share. You can do this easily with Flatseal (another flatpak), select Nicotine+, scroll down and with one tick you can give access to "All user files" (= your /home), or you can add a specific directory if you prefer.
freebee@sh.itjust.works · 3 pts · 1y
Thanks, this is great help indeed. I rarely use flatpak, not very familiar with it. It turns out the home folder was already allowed for Nicotine+, the issue appears to be that Nicotine+ is not allowed to "call" the opening of the dialog box to select the folder to use as shared...
freebee@sh.itjust.works · 2 pts · 1y
ok, it worked... the problem was appearantly that is was using xrdp to remotely login to a desktop session, and then for some reason the filepicker crashes: https://discussion.fedoraproject.org/t/file-chooser-does-not-open-for-flatpak-applications-f40-sway/126351/4
I did not use the bandaid workaround, but instead gained access to the device directly instead of remote desktopping and then the file or folderpicker worked just fine...
pipes@sh.itjust.works · 1 pts · 1y
Oh interesting, thanks for reporting back, glad you worked it out
pipes@sh.itjust.works · 1 pts · 1y
Btw I use the normal version of Nicotine, but this is how it usually works for flatpaks, as a security measure often the flatpak maintainer doesn't set the file access permission automatically.
MentalEdge@sopuli.xyz · 2 pts · 1y
Latest arch repo release works for me.
Easiest next step would be to try the .deb package.
I don't use any flatpaks, so I'm not familiar with their potentil quirks.
lurch@sh.itjust.works · 1 pts · 1y
doomsdayrs@lemmy.ml · 1 pts · 1y
report to the devs?