Created attachment 1446580 [details] .xsession-errors before restarting the service after first login Description of problem: After having restarted the computer for the first time and logged in as the primary user (different names on 2 different laptops but same ID 1000 and belonging to the wheel group), the Xfce desktop shows all system partitions on the desktop but doesn't show new devices (USB stick or SD card, no difference), same thing in Thunar. If I call `systemctl --user restart gvfs-udisks2-volume-monitor`, log out and log back in, the system partitions aren't shown anymore and Xfce and Thunar show removable devices plugged in. Version-Release number of selected component (if applicable): gvfs-1.34.2.1-1.fc27.x86_64 under Fedora 27 (and also the latest version under Fedora 28, but I don't have it handy) How reproducible: Always after a fresh reboot Steps to Reproduce: 1. Reboot 2. Log-in -> desktop is full of partition icons 3. Plug-in a USB-Stick -> no reaction from Xfce and/or Thunar 4. Plug-out 5. Call `systemctl --user restart gvfs-udisks2-volume-monitor` 6. Log-out 7. Log-in -> desktop shows no system partition 8. Plug-in a USB-Stick -> Xfce and Thunar show a new icon for the USB stick, which can be mounted. Actual results: See above the text after each arrow. Expected results: Result of steps 7 and 8 without having to restart the service. Additional info: - it happens on 2 independently installed laptops (one Asus with Fedora 28, one Lenovo with Fedora 27). - it seems to happen only for the main user (ID 1000, created during installation) but I don't know if it's relevant. - I think that the relevant line in .xsession-errors is "(xfdesktop:2070): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.vfs.UDisks2VolumeMonitor is not supported", it doesn't appear after the 2nd log-in or for other users. - dmesg and lsblk properly detect any removable device plugged-in at run-time. Output of `journalctl | grep -i udisk` from today: Jun 01 09:37:03 elavarde-t430s.lan dbus-daemon[1884]: [session uid=1000 pid=1884] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.29' (uid=1000 pid=2076 comm="/usr/lib64/tumbler-1/tumblerd " label="unconfined_u:unconfined_r:thumb_t:s0-s0:c0.c1023") Jun 01 09:37:04 elavarde-t430s.lan dbus-daemon[1123]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service' requested by ':1.35' (uid=1000 pid=2090 comm="/usr/libexec/gvfs-udisks2-volume-monitor " label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023") Jun 01 09:37:04 elavarde-t430s.lan udisksd[2113]: udisks daemon version 2.7.6 starting Jun 01 09:37:29 elavarde-t430s.lan dbus-daemon[1123]: [system] Failed to activate service 'org.freedesktop.UDisks2': timed out (service_start_timeout=25000ms) Jun 01 09:37:29 elavarde-t430s.lan gvfs-udisks2-vo[2090]: monitor says it's not supported Jun 01 09:37:29 elavarde-t430s.lan dbus-daemon[1884]: [session uid=1000 pid=1884] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor' Jun 01 09:37:29 elavarde-t430s.lan gvfs-udisks2-vo[2090]: monitor says it's not supported Jun 01 09:37:56 elavarde-t430s.lan audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=udisks2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jun 01 09:37:56 elavarde-t430s.lan udisksd[2113]: Acquired the name org.freedesktop.UDisks2 on the system message bus Jun 01 09:53:32 elavarde-t430s.lan gvfs-udisks2-vo[2090]: monitor says it's not supported Jun 01 10:04:59 elavarde-t430s.lan dbus-daemon[3646]: [session uid=1000 pid=3646] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.30' (uid=1000 pid=3851 comm="/usr/lib64/tumbler-1/tumblerd " label="unconfined_u:unconfined_r:thumb_t:s0-s0:c0.c1023") Jun 01 10:04:59 elavarde-t430s.lan dbus-daemon[3646]: [session uid=1000 pid=3646] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor' Let me know if I can provide more information, I have only easy access to the Lenovo/Fedora 27 but I plan to upgrade to Fedora 28 anyway. The issue was there on the Asus laptop before and after upgrade to 28.
Created attachment 1446581 [details] .xsession-errors after restarting the service after second login
The gvfs-udisks2-volume-monitor can fail with "monitor says it's not supported" warning only if udisks_client_new_sync failed. The journalctl log confirms this, org.freedesktop.UDisks2 failed to activate and timed out. So something is wrong with udisksd. The volume monitor restart helps (resp. logout and login helps), because org.freedesktop.UDisks2 is acquired in between. Maybe you can get some useful info why it takes too much time if you start the udisksd with --debug option: sudo /usr/libexec/udisks2/udisksd --replace --debug Changing component to udisks2.
Created attachment 1452504 [details] journalctl output after one reboot with udisksd --debug Because I can't reproduce the error after the reboot, I've patched `/lib/systemd/system/udisks2.service` so that it reads: ExecStart=/usr/libexec/udisks2/udisksd --debug But I don't see any more information than it used to have (log attached). As the two involved computers are not fast ones, I thought that the timeout involved might just be too short, but the one shown `service_start_timeout=25000ms` is actually 25 seconds, this is _not_ a little, so there must be something else. Any further ideas more than welcome, thanks for taking care so far.
Created attachment 1455860 [details] /etc/dbus-1/system-local.conf with longer service_start_timeout Having a longer service_start_timeout made the timeout message disappear but didn't solve the issue. I have the impression that the following lines are new: Jul 02 07:30:46 elavarde-t430s.lan dbus-daemon[2035]: [session uid=1000 pid=2035] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.29' (uid=1000 pid=2235 comm="/usr/lib64/tumbler-1/tumblerd " label="unconfined_u:unconfined_r:thumb_t:s0-s0:c0.c1023") Jul 02 07:30:46 elavarde-t430s.lan systemd[2018]: Starting Virtual filesystem service - Media Transfer Protocol monitor... Jul 02 07:30:46 elavarde-t430s.lan gvfs-udisks2-vo[2269]: monitor says it's not supported Jul 02 07:30:46 elavarde-t430s.lan dbus-daemon[2035]: [session uid=1000 pid=2035] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor' Any further help you can give me?
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
I am not convinced that the problem isn't still there but on the two laptops where I had the issue, it was fixed by making the hard drive "faster": - in one case by replacing the HDD by an SSD - in the 2nd case by removing encryption Just to document my "resolution" in case someone stumbles upon the same issue in the future.