Hide Forgot
Description of problem: After upgrading from F23 to F24, usb connected devices like sticks or mobile phones get detected, but not auto mounted anymore. "gvfs-mount -o -i" output is at the end. so gvfs detects the drives, but it's not mounted. same drives or phones connected to a laptop, work as expected. They worked with F23. Version-Release number of selected component (if applicable): gvfs-1.28.3-1.fc24.x86_64 gvfs-afc-1.28.3-1.fc24.x86_64 gvfs-archive-1.28.3-1.fc24.x86_64 gvfs-gphoto2-1.28.3-1.fc24.x86_64 gvfs-mtp-1.28.3-1.fc24.x86_64 gvfs-goa-1.28.3-1.fc24.x86_64 gvfs-smb-1.28.3-1.fc24.x86_64 gvfs-client-1.28.3-1.fc24.x86_64 gvfs-fuse-1.28.3-1.fc24.x86_64 gvfs-afp-1.28.3-1.fc24.x86_64 Actual results: no automount Expected results: automount as in f23 Additional info: Drive disconnected: 'Intenso Rainbow Line' Drive(0): Intenso Rainbow Line Type: GProxyDrive (GProxyVolumeMonitorUDisks2) ids: unix-device: '/dev/sdd' themed icons: [drive-removable-media-usb] [drive-removable-media] [drive-removable] [drive] symbolic themed icons: [drive-removable-media-usb-symbolic] [drive-removable-media-symbolic] [drive-removable-symbolic] [drive-symbolic] [drive-removable-media-usb] [drive-removable-media] [drive-removable] [drive] is_media_removable=1 has_media=1 is_media_check_automatic=1 can_poll_for_media=0 can_eject=1 can_start=0 can_stop=0 start_stop_type=shutdown sort_key=01hotplug/1478096706164528 Volume(0): Daten Type: GProxyVolume (GProxyVolumeMonitorUDisks2) ids: class: 'device' unix-device: '/dev/sdd1' uuid: '227C9F0E7E06FAF9' label: 'Daten' themed icons: [drive-removable-media-usb] [drive-removable-media] [drive-removable] [drive] symbolic themed icons: [drive-removable-media-usb-symbolic] [drive-removable-media-symbolic] [drive-removable-symbolic] [drive-symbolic] [drive-removable-media-usb] [drive-removable-media] [drive-removable] [drive] can_mount=1 can_eject=0 should_automount=1 sort_key=gvfs.time_detected_usec.1478096706374621 Volume removed: 'Daten' Volume(0): Daten Type: GProxyVolume (GProxyVolumeMonitorUDisks2) ids: class: 'device' unix-device: '/dev/sdd1' uuid: '227C9F0E7E06FAF9' label: 'Daten' themed icons: [drive-removable-media-usb] [drive-removable-media] [drive-removable] [drive] symbolic themed icons: [drive-removable-media-usb-symbolic] [drive-removable-media-symbolic] [drive-removable-symbolic] [drive-symbolic] [drive-removable-media-usb] [drive-removable-media] [drive-removable] [drive] can_mount=1 can_eject=0 should_automount=1 sort_key=gvfs.time_detected_usec.1478096706374621 Drive connected: 'Intenso Rainbow Line' Drive(0): Intenso Rainbow Line Type: GProxyDrive (GProxyVolumeMonitorUDisks2) ids: unix-device: '/dev/sdd' themed icons: [drive-removable-media-usb] [drive-removable-media] [drive-removable] [drive] symbolic themed icons: [drive-removable-media-usb-symbolic] [drive-removable-media-symbolic] [drive-removable-symbolic] [drive-symbolic] [drive-removable-media-usb] [drive-removable-media] [drive-removable] [drive] is_media_removable=1 has_media=1 is_media_check_automatic=1 can_poll_for_media=0 can_eject=1 can_start=0 can_stop=0 start_stop_type=shutdown sort_key=01hotplug/1478096885644198 Drive changed: 'Intenso Rainbow Line' Drive(0): Intenso Rainbow Line Type: GProxyDrive (GProxyVolumeMonitorUDisks2) ids: unix-device: '/dev/sdd' themed icons: [drive-removable-media-usb] [drive-removable-media] [drive-removable] [drive] symbolic themed icons: [drive-removable-media-usb-symbolic] [drive-removable-media-symbolic] [drive-removable-symbolic] [drive-symbolic] [drive-removable-media-usb] [drive-removable-media] [drive-removable] [drive] is_media_removable=1 has_media=1 is_media_check_automatic=1 can_poll_for_media=0 can_eject=1 can_start=0 can_stop=0 start_stop_type=shutdown sort_key=01hotplug/1478096885644198 Volume added: 'Daten' Volume(0): Daten Type: GProxyVolume (GProxyVolumeMonitorUDisks2) ids: class: 'device' unix-device: '/dev/sdd1' uuid: '227C9F0E7E06FAF9' label: 'Daten' themed icons: [drive-removable-media-usb] [drive-removable-media] [drive-removable] [drive] symbolic themed icons: [drive-removable-media-usb-symbolic] [drive-removable-media-symbolic] [drive-removable-symbolic] [drive-symbolic] [drive-removable-media-usb] [drive-removable-media] [drive-removable] [drive] can_mount=1 can_eject=1 should_automount=1 sort_key=gvfs.time_detected_usec.1478096885851240
FIX FOUND: As Root dnf reinstall dbus-x11 killall nautilus As User: nautilus --force-desktop
it only works, if nautilus gets started from gnome-terminal. If invoked via ALT+F2, it's not working. maybe a clean system start is needed, we will see.
Hmm, gnome-shell is responsible for automounting. Does the following return "true"? gsettings get org.gnome.desktop.media-handling automount
[marius@eve ~]$ gsettings get org.gnome.desktop.media-handling automount true
Info: a reboot got a : gnome-shell crash back into the loginscreen the login afterwards gave me nautilus without desktop icons the necessary "killall nautilus; nautilus --force-desktop &" gave me a WORKING automount :D The question now is: Why did d-bus x11 had a problem in the first place?
one reboot later, without a crash, the system is back to none-functional again. it looks like, the filemanager must be started from a bash session to be able to access the dbus. So, some rights seem not ot match here. I suggest to transfer the ticket to the dbus guys.
Yea, there is obviously something wrong with dbus... It seems to me that gdm somehow wrongly spawns the desktop session as per your info... Changing component to gdm (rather then dbus).
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.