Quantcast
Channel: Debian User Forums
Viewing all articles
Browse latest Browse all 2849

System and Network configuration • Re: [Thunar] GVFS/Removable Media Issues on Minimal Debian + Sway Installation

$
0
0
Hello,

According to [1], this is the source code showing the error message:

Code:

  /* check the most important gvfs-backends, and inform if they are missing */  if (!thunar_g_vfs_is_uri_scheme_supported ("trash")    ||      !thunar_g_vfs_is_uri_scheme_supported ("computer") || /* support for removable media */      !thunar_g_vfs_is_uri_scheme_supported ("sftp") )    {      [..]      gtk_label_set_markup (GTK_LABEL (label), _("It looks like <a href=\"https://wiki.gnome.org/Projects/gvfs\">gvfs</a> is not available.\n"                                                 "Important features including trash support,\n"                                                 "removable media and remote location browsing\n"                                                 "will not work. <a href=\"https://docs.xfce.org/xfce/thunar/unix-filesystem#gnome_virtual_file_system\">[Read more]</a>"));      [..]
The error is shown if one or more of the following "uri schemes" are unsupported: "trash", "computer", "sftp"

According to [2] and [3], these are the packages and binaries providing the services that offer the aforementioned "uri schemes":

Code:

$ apt-file search gvfsd-trash gvfsd-computer gvfsd-sftpgvfs-daemons: /usr/lib/gvfs/gvfsd-trash   gvfs-daemons: /usr/libexec/gvfsd-trash$ apt-file search gvfsd-computer gvfs-daemons: /usr/lib/gvfs/gvfsd-computergvfs-daemons: /usr/libexec/gvfsd-computer$ apt-file search gvfsd-sftpgvfs-backends: /usr/lib/gvfs/gvfsd-sftp   gvfs-backends: /usr/libexec/gvfsd-sftp
So, required packages should be gvfs-daemons and gvfs-backends. You may try reinstalling them, since it seems they are already installed from your previous post:

Code:

sudo apt reinstall gvfs-daemons gvfs-backends
This is the output of the gvfs running daemons in a Xfce Debian Bookworm installation:

Code:

$ ps ax | grep gvfs   1143 ?        Ssl    0:00 /usr/libexec/gvfsd   1259 ?        Ssl    0:00 /usr/libexec/gvfs-udisks2-volume-monitor   1265 ?        Ssl    0:00 /usr/libexec/gvfs-afc-volume-monitor   1271 ?        Ssl    0:00 /usr/libexec/gvfs-mtp-volume-monitor   1275 ?        Ssl    0:00 /usr/libexec/gvfs-gphoto2-volume-monitor   1281 ?        Ssl    0:00 /usr/libexec/gvfs-goa-volume-monitor   1322 ?        Sl     0:00 /usr/libexec/gvfsd-trash --spawner :1.6 /org/gtk/gvfs/exec_spaw/0   1330 ?        Ssl    0:00 /usr/libexec/gvfsd-metadata   1706 pts/0    S+     0:00 grep gvfs
What’s the output in your installation ?

Hope this helps.

--
[1] https://sources.debian.org/src/thunar/4 ... g.c/#L1317
[2] https://wiki.gnome.org/Projects/gvfs/schemes
[3] https://en.wikipedia.org/wiki/GVfs
Thanks for your help (and for the truely appreciated context!), after running the reinstall and grepping gvfs from `ps -ax`, I only get the so-said grep in the result, nothing else seems running.
Now that you mention it, I remember it was part of the problem. By default, no service is running as so:

Code:

› systemctl --user status gvfs-daemon          ○ gvfs-daemon.service - Virtual filesystem service     Loaded: loaded (/usr/lib/systemd/user/gvfs-daemon.service; static)     Active: inactive (dead)
So, running `systemctl --user start gvfs-daemon` changes the output of the grep to

Code:

› ps ax | grep gvfs                    17523 ?        Ssl    0:00 /usr/libexec/gvfsd  17529 ?        Sl     0:00 /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f
(I removed the grep from here).
Now, running `systemctl --user status gvfs-daemon` actually outputs some more informations:

Code:

gvfs-daemon.service - Virtual filesystem service     Loaded: loaded (/usr/lib/systemd/user/gvfs-daemon.service; static)     Active: active (running) since Fri 2024-11-08 10:59:29 CET; 3min 30s ago   Main PID: 17523 (gvfsd)      Tasks: 11 (limit: 16311)     Memory: 8.4M        CPU: 53ms     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/gvfs-daemon.service             ├─17523 /usr/libexec/gvfsd             └─17529 /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -fNov 08 10:59:29 luk-hp-debian systemd[2105]: Starting gvfs-daemon.service - Virtual filesystem service...Nov 08 10:59:29 luk-hp-debian systemd[2105]: Started gvfs-daemon.service - Virtual filesystem service.Nov 08 10:59:29 luk-hp-debian gvfsd-fuse[17529]: g_object_new_with_properties: assertion 'G_TYPE_IS_OBJECT (object_type)' failedNov 08 10:59:29 luk-hp-debian gvfsd-fuse[17529]: g_volume_monitor_get_mounts: assertion 'G_IS_VOLUME_MONITOR (volume_monitor)' failedNov 08 10:59:29 luk-hp-debian gvfsd-fuse[17529]: invalid (NULL) pointer instanceNov 08 10:59:29 luk-hp-debian gvfsd-fuse[17529]: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failedNov 08 10:59:29 luk-hp-debian gvfsd-fuse[17529]: invalid (NULL) pointer instanceNov 08 10:59:29 luk-hp-debian gvfsd-fuse[17529]: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
which might be the most useful information I gave in this thread (and I forgot it in the first message.....) is it anything more helpful ?

I'm pretty sure it's dbus-related though

Statistics: Posted by IkeYeek — 2024-11-08 10:04



Viewing all articles
Browse latest Browse all 2849

Trending Articles