From: raingloom <raingloom@riseup.net>
To: Jaft via <help-guix@gnu.org>
Cc: Jaft <wamm_kd_schmelingski@yahoo.com>
Subject: Re: Android Device Mounting Detection with GVFS Help
Date: Tue, 22 Feb 2022 02:08:53 +0100 [thread overview]
Message-ID: <20220222020853.51f7392c@riseup.net> (raw)
In-Reply-To: <1364279890.1889289.1644837569459@mail.yahoo.com>
On Mon, 14 Feb 2022 11:19:29 +0000 (UTC)
Jaft via <help-guix@gnu.org> wrote:
> I dunno if anyone might have any suggestions but I've been trying to
> get my Android phone get detected. I'm using GVFS and Thunar; full
> details of what I originally tried are at
> https://www.reddit.com/r/GUIX/comments/s55e8m/smartphone_detection_with_gvfs/
> but the short of it is that I noticed that the 69-libmtp.rules file
> that Guix installs differed from my Debian machine so I added a
> udev-rules-service that added all the devices that were in the Debian
> file and found the device was recognized, now, but trying to click on
> it or mount it still resulted in the error "No mtp devices found."
>
> Someone on the IRC channel recommended trying android-udev-rules so I
> did; this resulted in the phone not getting recognized, when plugged
> in, by Thunar, again – but it was able to be recognized as a
> connected device by adb. I've attached my system config. file, so
> it's clear to see what the setup I've tried is; I have no idea what
> else to try (if there's anything else even to try) but thanks for any
> help!
GVFS in general seems extremely buggy, but especially on Guix. If you
manage to figure this out I'd be very interested.
Other fun GVFS related issues include:
- sometimes mounts just plain don't show up (no /run/user/$UID/gvfs
entry)
- removable drives only show up once you've run fstab --list on them.
they can be mounted with udiskctl, but they aren't visible in
Nautilus.
- incorrect handling of symlinks can lead to data loss, bug has been
known for years and no workaround or fix exists.
next prev parent reply other threads:[~2022-02-22 1:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1364279890.1889289.1644837569459.ref@mail.yahoo.com>
2022-02-14 11:19 ` Android Device Mounting Detection with GVFS Help Jaft via
2022-02-22 1:08 ` raingloom [this message]
2022-02-26 22:20 ` Jaft via
2022-02-26 22:27 ` Tobias Geerinckx-Rice
2022-02-27 12:14 ` Jaft
2022-03-06 3:30 ` James Thomas
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=20220222020853.51f7392c@riseup.net \
--to=raingloom@riseup.net \
--cc=help-guix@gnu.org \
--cc=wamm_kd_schmelingski@yahoo.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.
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).