-
-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gvfs-trash deprecation (can't delete file) #1059
Comments
Thanks a ton for reporting this issue. After following the link you mentioned, it seems to indicate that this is an issue present in Electron itself, and since Pulsar is still on a slightly older version, we may be limited in what we can do to resolve this. Did you try setting the environment variable If that gets things working for you that'd be awesome until we are able to bump our Electron version |
Thanks for your reply. I tried to reproduce and test setting ELECTRON_TRASH variable but after installing |
Interesting, I was looking into this. Essentially Pulsar just uses This itself for our current version of Electron ( Which in some way is inferring and working with the KDE version, the As I'm unfamiliar with these options, it seems a tad bit confusing. But I will say the So this may be as simple as Electron being unable to find |
That's really interesting. I am using XFCE 4 and I bumped into some threads mentioning something about a That may be a way to look into to find out more about these Distro/Desktop Environment differences. I'll read more about it and I'll return with more info. |
Thanks in advance for your bug report!
What happened?
While trying to delete a file in the project file tree panel I was getting the message "Is gvfs-trash installed?" and the file was not being deleted.
To workaround this I had to install GIO using
sudo apt-get install libglib2.0-dev
and then reference it as /usr/local/bin/gvfs-trashPulsar version
1.119.0 x64
Which OS does this happen on?
🐧 Debian based (Linux Mint, Ubuntu, etc.)
OS details
Debian Bookworm 12 6.1.0-22-amd64
Which CPU architecture are you running this on?
x86_64/AMD64
What steps are needed to reproduce this?
Additional Information:
No response
The text was updated successfully, but these errors were encountered: