unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: raingloom <raingloom@riseup.net>
Cc: 47716-done@debbugs.gnu.org
Subject: bug#47716: gio mount broken, again.
Date: Thu, 14 Jul 2022 16:05:17 -0400	[thread overview]
Message-ID: <878rovwjcy.fsf@gmail.com> (raw)
In-Reply-To: <20210411202901.2fc0f998@riseup.net> (raingloom@riseup.net's message of "Sun, 11 Apr 2021 20:29:01 +0200")

Hi,

raingloom <raingloom@riseup.net> writes:

> ```
> $ gio mount sftp://whatever
> $ ls /run/user/$UID/gvfs/
> ```
> prints nothing.

Note that it seem to work if you are using the GNOME desktop.

> Same thing happens if I mount it from the Nautilus file manager.
>
> This bug has appeared before and I still have no idea how it was fixed,
> which is not great. I'll do a bisect soon. Should probably add a system
> test for it so it doesn't break again.
>
> In the meantime, if whoever fixed it the last time could look into it
> again, I'd be very thankful. Using sshfs manually works but isn't great.

gvfs is now using fusermount3, but we were only adding 'fusermount' as a
setuid-program by default.

After adding fusermount3 from fuse@3 to /run/setuid-programs, it appears
to work:

$ guix shell glib:bin gvfs dbus fuse gnome-keyring
[env] PATH=/run/setuid-programs:$PATH dbus-run-session bash
[env] gio mount sftp://some-host:2345
( prompts for credentials )
ls /run/user/1000/gvfs/sftp:host=some-host,port=2345/
bin/   dev/  gnu/   [...]

I've pushed this as commit cbdfa54c77.

Closing.

Maxim




      parent reply	other threads:[~2022-07-14 20:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-11 18:29 bug#47716: gio mount broken, again raingloom
2022-07-12 15:29 ` Maxim Cournoyer
2022-07-12 20:04   ` Csepp
2022-07-14 12:45     ` Csepp
2022-07-14 20:05 ` Maxim Cournoyer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878rovwjcy.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=47716-done@debbugs.gnu.org \
    --cc=raingloom@riseup.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).