unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Csepp <raingloom@riseup.net>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 47716@debbugs.gnu.org, raingloom <raingloom@riseup.net>
Subject: bug#47716: gio mount broken, again.
Date: Thu, 14 Jul 2022 14:45:25 +0200	[thread overview]
Message-ID: <877d4fc162.fsf@riseup.net> (raw)
In-Reply-To: <874jzmksci.fsf@riseup.net>


Csepp <raingloom@riseup.net> writes:

> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>
>> Hi,
>>
>> raingloom <raingloom@riseup.net> writes:
>>
>>> ```
>>> $ gio mount sftp://whatever
>>> $ ls /run/user/$UID/gvfs/
>>> ```
>>> prints nothing.
>>>
>>> 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.
>>
>> glib has seen 3 ugrades in Guix since you reported this issue (2.68.3
>> then 2.70 then 2.70.2).  Do you still have the issue?
>>
>> How do you setup the server; is a running OpenSSH server sufficient?
>>
>> Thanks,
>>
>> Maxim
>
> I haven't done the bisect yet (ugh, why is time), but yes, the problem
> still persists. Mostly same system config. gvfs is included in system
> profile.
> Yep, running OpenSSH is enough.
> The system I'm currently writing from very much has the issue and is
> about... okay, so it's from june 21, so not as fresh as I thought, but
> relatively fresh.

Upgraded system and user profiles and the issue is still present.




  reply	other threads:[~2022-07-14 12:47 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 [this message]
2022-07-14 20:05 ` Maxim Cournoyer

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=877d4fc162.fsf@riseup.net \
    --to=raingloom@riseup.net \
    --cc=47716@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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).