Vscode: Can not move to trash on Gnome 3.30

Created on 25 Sep 2018  路  12Comments  路  Source: microsoft/vscode

On Arch Linux x64, gnome 3.30, when deleting a file and pressing "move to trash" the following message appears:

image

Not sure if this is caused by vscode 1.27 or gnome 3.30 as I updated both at the same time, but deleted files were correctly moved to the trash on vscode 1.26 and gnome 3.28.

electron linux upstream

Most helpful comment

I had the same problem (running Arch with Gnome 3.30) and created the file /usr/local/bin/gvfs-trash with the following contents:
````sh

!/bin/sh

gio trash $@
``` After making it executable (sudo chmod +x /usr/local/bin/gvfs-trash`), vscode was able to move my files to my trash folder.

All 12 comments

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

We did not change anything in that area in the latest release. So my bet would be gnome.
However we officialy do not support Arch Linux afaik so closing this
Also I would try to repro this issue using node and file an issue in their repository

I think you were a bit fast to close this issue. If the problem is with gnome 3.30, you'll see this problem again soon enough. Consider this as a head-ups then :)

Let's reopen and see if more users complain. Thanks for the heads up
fyi @bpasero

I can confirm the same behavior running XFCE on Arch Linux.
I think the issue is with gvfs-trash since it has been deprecated. Since 1.37.2, gvfs completely removes support for gvfs-trash.
The gio trash is used now.
Maybe a Electron issue?

@juliuswz yes, this is an electron issue. Thanks for providing more details

I had the same problem (running Arch with Gnome 3.30) and created the file /usr/local/bin/gvfs-trash with the following contents:
````sh

!/bin/sh

gio trash $@
``` After making it executable (sudo chmod +x /usr/local/bin/gvfs-trash`), vscode was able to move my files to my trash folder.

Thanks ccaspers! It works as a workaround, but I had to change the content of gvfs-trash to:

#!/bin/bash
/usr/bin/gio trash "$@"

Since commenting on https://github.com/electron/electron/pull/9518 has not gotten anywhere, I've submitted a new bug report for electron: https://github.com/electron/electron/issues/15011

Fix works on Fedora 29, cheers!

Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: https://code.visualstudio.com/insiders/

I removed my shim for gfvs-trash and can no longer reproduce the bug :tada:

  • GNOME Shell 3.30.2
  • vscode
    Version: 1.31.0-insider
    Commit: 1b575168183b8e1d3a988f4cc8a5c7d15bce3c7c
    Date: 2019-01-28T06:14:17.311Z
    Electron: 3.1.2
    Chrome: 66.0.3359.181
    Node.js: 10.2.0
    V8: 6.6.346.32
    OS: Linux x64 4.20.3-zen2-1-zen
Was this page helpful?
0 / 5 - 0 ratings