Re: [oS-EN] Can no longer mount phones in Thunar

"Carlos E. R." <[email protected]>
Newsgroups gmane.linux.suse.general
Message-ID <[email protected]>
On 2026-06-10 10:31, Masaru Nomiya wrote:
> Hello,
> 
> In the Message;
> 
>    Subject    : Re: [oS-EN] Can no longer mount phones in Thunar
>    Message-ID : <[email protected]>
>    Date & Time: Wed, 10 Jun 2026 10:14:24 +0200
> 
> [CER] == "Carlos E. R." <[email protected]> has written:
> 
> CER>  On 2026-06-10 03:18, Masaru Nomiya wrote:
> [...]
> MN> > Ah, so that's the issue with using Dolphin on desktop environments
> MN> > other than KDE. That's why I don't use Dolphin on anything other than
> MN> > Plasma 6 - I just don't like the UI itself.
> 
> CER>  I started dolphin because thunar could not connect to my phone,
> CER>  maybe because "shotwell" was running.
> 
> I don't think Shotwell has anything to do with it; I believe this is
> strictly an MTP related issue.

Shotwell can read cameras on its own, and this interferes with thunar 
reading that same camera. A phone is a camera, too. Some cameras 
shotwell does not read, and for those I mount the camera in thunar 
first, and then shotwell sees them.

> 
> Please show the results of;
> 
>         $ rpm -qa | grep gvfs
> 

cer@Telcontar:~/bin> rpm -qa | grep gvfs
gvfs-backends-1.52.2-150600.3.3.1.x86_64
gvfs-lang-1.52.2-150600.3.3.1.noarch
gvfs-backend-goa-1.52.2-150600.3.3.1.x86_64
gvfs-fuse-1.52.2-150600.3.3.1.x86_64
gvfs-backend-samba-1.52.2-150600.3.3.1.x86_64
gvfs-1.52.2-150600.3.3.1.x86_64
gvfs-backend-afc-1.52.2-150600.3.3.1.x86_64
cer@Telcontar:~/bin>


-- 
Cheers / Saludos,

		Carlos E. R.
		(from 15.6 x86_64 at Telcontar)
OpenPGP_signature.asc (application/pgp-signature, 203 B)
-----BEGIN PGP SIGNATURE-----

wmMEABEIACMWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCaiknogUDAAAAAAAKCRC1MxgcbY1H1Ux3
AJ4xaMedvQijMUT0QxQ2Dvv3s0386gCfUDpy58e2g1n5LZc/uXKsVDhHpc0=
=W4zr
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.