Thunar requires restart of gvfs-udisks2-volume-monitor.service to automount

[Alex]

Hi Gour,

never faced such a behaviour before.

From the fact that you just need to restart a service to fix the
problem, I would assume that the order in which the services are started
at boot is the key.

Maybe you can compare the configuration/start order of your systemd
services against some other system which runs fine ?

Other than that I as well would need to "fish in the dark".

Cheers,

Alex

Am 07.04.19 um 16:02 schrieb Gour:
> Hello,
>
> I've installed latest Manjaro xfce-iso to replace gnome with Xfce environment
> and everything is working fine except the problem that Thunar is not
> capable of mounting any removable media.
>
> The same media can be mounted manually (it goes from 120M usb stick to
> 2TB HDD - RDX cartridge) and if I boot live-media iso (on the usb
> stick), Thunar does automount which means that the issue has appeared
> on my installed system.
>
> In the journalctl output I noticed the lines like:
>
> [...]
> tra 07 10:58:06 atmarama.ddns.net gvfs-udisks2-vo[1056]: monitor says
> it's not supported
> tra 07 10:58:06 atmarama.ddns.net tumblerd[5613]: remote volume monitor
> with dbus name org.gtk.vfs.UDisks2VolumeMonitor is not supported
>
> Further investigation has led me to the following bug report
> (https://bugzilla.redhat.com/show_bug.cgi?id=1585066) and, indeed:
>
> $ systemctl --user status gvfs-udisks2-volume-monitor
> ● gvfs-udisks2-volume-monitor.service - Virtual filesystem service -
> disk device monitor
> Loaded: loaded
> (/usr/lib/systemd/user/gvfs-udisks2-volume-monitor.service; static;
> vendor pre>
>  Active: active (running) since Sun 2019-04-07 10:16:07 CEST; 3h 9min
> ago Main PID: 1056 (gvfs-udisks2-vo)
> CGroup: /user.slice/user-1000.slice/user at 1000.service/gvfs-udisks2-volume-monitor.service
> └─1056 /usr/lib/gvfs-udisks2-volume-monitor
>
> tra 07 13:08:43 atmarama.ddns.net gvfs-udisks2-vo[1056]: monitor says it's not supported
> tra 07 13:08:48 atmarama.ddns.net gvfs-udisks2-vo[1056]: monitor says it's not supported
> tra 07 13:09:16 atmarama.ddns.net gvfs-udisks2-vo[1056]: monitor says it's not supported
> tra 07 13:09:16 atmarama.ddns.net gvfs-udisks2-vo[1056]: monitor says it's not supported
> tra 07 13:09:17 atmarama.ddns.net gvfs-udisks2-vo[1056]: monitor says it's not supported
> tra 07 13:09:17 atmarama.ddns.net gvfs-udisks2-vo[1056]: monitor says it's not supported
> tra 07 13:18:34 atmarama.ddns.net gvfs-udisks2-vo[1056]: monitor says it's not supported
> tra 07 13:18:34 atmarama.ddns.net gvfs-udisks2-vo[1056]: monitor says it's not supported
> tra 07 13:18:35 atmarama.ddns.net gvfs-udisks2-vo[1056]: monitor says it's not supported tra 07 13:18:35 atmarama.ddns.net gvfs-udisks2-vo[1056]: monitor says it's not supported
>
> $  systemctl --user restart gvfs-udisks2-volume-monitor
> $  systemctl --user status gvfs-udisks2-volume-monitor
>
> ● gvfs-udisks2-volume-monitor.service - Virtual filesystem service - disk device monitor
> Loaded: loaded (/usr/lib/systemd/user/gvfs-udisks2-volume-monitor.service; static; vendor pre>
> Active: active (running) since Sun 2019-04-07 13:25:51 CEST; 1s ago
> Main PID: 17668 (gvfs-udisks2-vo)
> CGroup: /user.slice/user-1000.slice/user at 1000.service/gvfs-udisks2-volume-monitor.service
> └─17668 /usr/lib/gvfs-udisks2-volume-monitor
>
> tra 07 13:25:51 atmarama.ddns.net systemd[964]: gvfs-udisks2-volume-monitor.service: Main proces>
> tra 07 13:25:51 atmarama.ddns.net systemd[964]: gvfs-udisks2-volume-monitor.service: Succeeded.
> tra 07 13:25:51 atmarama.ddns.net systemd[964]: Stopped Virtual filesystem service - disk device>
> tra 07 13:25:51 atmarama.ddns.net systemd[964]: Starting Virtual filesystem service - disk devic>
> tra 07 13:25:51 atmarama.ddns.net systemd[964]: Started Virtual filesystem service - disk device>
>
> and after that the inserted media shows up in Thunar's Devices section where I can
> (un)mount them.
>
> Now I wonder if someone can shed some more light on this issue, iow.
> why gvfs-udisks2-volume-monitor requires restart and how to fix the
> issue permanently?
>
> My system is:
>
> $  inxi -Fxz
> System:    Host: atmarama.ddns.net Kernel: 4.19.34-1-MANJARO x86_64
> bits: 64 compiler: gcc v: 8.2.1 Desktop: Xfce 4.13.3git-UNKNOWN Distro:
> Manjaro Linux Machine:   Type: Desktop System: Gigabyte product:
> P55-UD4 v: N/A serial: <filter> Mobo: Gigabyte model: P55-UD4 v: x.x
> serial: <filter> BIOS: Award v: F9 date: 06/25/2010
> Battery:   Device-1: hidpp_battery_0 model: Logitech M585/M590
> Multi-Device Mouse charge: 55% (should be ignored) status: Discharging
> CPU:       Topology: Quad Core model: Intel Core i7 860 bits: 64 type:
> MT MCP arch: Nehalem rev: 5 L2 cache: 8192 KiB
>            flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
> bogomips: 44786 Speed: 1220 MHz min/max: N/A Core speeds (MHz): 1: 1220
> 2: 1229 3: 1577 4: 1273 5: 1429 6: 1224 7: 2322 8: 1308
> Graphics:  Device-1: AMD RV730 XT [Radeon HD 4670] vendor: Gigabyte
> driver: radeon v: kernel bus ID: 01:00.0
>            Display: x11 server: X.Org 1.20.4 driver: ati,radeon
> unloaded: modesetting resolution: 2560x1440~60Hz
>            OpenGL: renderer: AMD RV730 (DRM 2.50.0 / 4.19.34-1-MANJARO
> LLVM 8.0.0) v: 3.3 Mesa 19.0.1 direct render: Yes
> Audio:     Device-1: Intel 5 Series/3400 Series High Definition Audio
> vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 00:1b.0
>            Device-2: AMD RV710/730 HDMI Audio [Radeon HD 4000 series]
> vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 01:00.1
>            Device-3: Logitech QuickCam Vision Pro type: USB driver:
> snd-usb-audio,uvcvideo bus ID: 4-5:2
>            Device-4: Logitech Premium Stereo USB Headset 350 type: USB
>            driver: hid-generic,snd-usb-audio,usbhid bus ID: 5-2:3
>            Sound Server: ALSA v: k4.19.34-1-MANJARO
> Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit
> Ethernet vendor: Gigabyte driver: r8168 v: 8.045.08-NAPI port: de00 bus
> ID: 06:00.0 IF: enp6s0 state: up speed: 100 Mbps duplex: full mac:
> <filter> Drives:    Local Storage: total: 2.73 TiB used: 903.70 GiB
> (32.3%) ID-1: /dev/sda vendor: Seagate model: ST31000525SV size: 931.51
> GiB ID-2: /dev/sdb vendor: Seagate model: ST2000DX001-1NS164 size: 1.82
> TiB RAID:      Device-1: md126 type: mdraid status: active Components:
> online: sdb3~c2 sda3~c0 Info: raid: mirror blocks: 945172160 report:
> 2/2 UU chunk size: N/A Device-2: md127 type: mdraid status: active
> Components: online: sdb2~c2 sda2~c0 Info: raid: mirror blocks: 31440896
> report: 2/2 UU chunk size: N/A Partition: ID-1: / size: 29.97 GiB used:
> 11.50 GiB (38.4%) fs: xfs dev: /dev/md127 ID-2: /home size: 900.95 GiB
> used: 892.20 GiB (99.0%) fs: xfs dev: /dev/md126 ID-3: swap-1 size:
> 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdb4 Sensors:   System
> Temperatures: cpu: 39.0 C mobo: N/A gpu: radeon temp: 49 C Fan Speeds
> (RPM): N/A Info:      Processes: 275 Uptime: 3h 28m Memory: 15.66 GiB
> used: 2.83 GiB (18.1%) Init: systemd Compilers: gcc: 8.2.1 Shell: fish
> v: 3.0.2 inxi: 3.0.32
>
> Any hint?
>
> Sincerely,
> Gour
>