Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#55558 - [gvfs] [udisks2] desktop laggy to load

Attached to Project: Arch Linux
Opened by steadfasterX (steadfasterX) - Friday, 08 September 2017, 13:46 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 16 September 2017, 23:25 GMT
Task Type Bug Report
Category Packages: Extra
Status Assigned
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 2
Private No

Details

Description:

when udisks2 and gvfs are installed the desktop takes ~30 sec to load.
Running/Tested on xfce4 but I saw a report was made for GNOME (see related links).

Removing gvfs "fix" this lagging.
The xfce panel is usable immediately after login though.

Additional info:
* gvfs 1.32.1+8+ga33a8437-1
* udisks2 2.7.2-1
* xfce 4.12 (xfce4-session 4.12.1-6.1, xfce4-settings 4.12.1-1)
* lightdm 1:1.22.0-1

~/.xsession-errors:

...
--> [no desktop - only panel is shown]
Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.UDisks2VolumeMonitor: Timeout was reached (g-io-error-quark, 24)
--> [directly after this error the desktop background and icons are shown]
..


Related links:

* https://git-annex.branchable.com/bugs/Volume_monitor_in_GNOME_3.18/
* https://github.com/Carbon-Fusion/build_fwul/issues/51


Steps to reproduce:

install: xfce4, gvfs, udisks2
use xfce as session and login
it take up to 30 sec to bring up the desktop (panel is there immediately)

remove gvfs, udisks2 and retry to login. desktop is shown immediately

This task depends upon

Comment by Frank Phillips (fphillips) - Sunday, 28 April 2019, 18:18 GMT
# 250GB external backup
UUID=4dd58f12-30e4-4327-a89b-c1d457b51692 /media/borg ext4 defaults,noauto,x-systemd.automount,x-systemd.device-timeout=3 0 0

I was using x-systemd.automount in fstab and it would show as mounted (even though the external drive wasn't connected):

systemd-1 on /media/borg type autofs (rw,relatime,fd=35,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=11837)

/usr/lib/gvfs-udisks2-volume-monitor would continue to try to read these mounts, while the --user gvfs-udisks2-volume-monitor.service waiting for it would timeout and fail.

Once I removed x-systemd.automount, things were back to normal.

Other symptoms:
Nautilus slow to open (30 seconds)
Nautilus showed all fstab mounts in the sidebar, including root boot and home
Baobab wouldn't open (same dbus timeout error as OP)

Note that my fstab with x-systemd.automount had been working until recently (around Gnome 3.32 release). A new user was a bit better, but still had symptoms with x-systemd.automount.

Hard to say what combination of user cruft/misconfiguration or bug/behavior change in systemd or Gnome this is.

Loading...