After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 711711 - Sometime (randomly) disks are not automounted.
Sometime (randomly) disks are not automounted.
Status: RESOLVED OBSOLETE
Product: gvfs
Classification: Core
Component: udisks2 volume monitor
1.18.x
Other Linux
: Normal normal
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2013-11-08 22:07 UTC by Romano Giannetti
Modified: 2018-09-21 17:36 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Romano Giannetti 2013-11-08 22:07:48 UTC
Sometime (depending on the session) it seems that gvfs fails to coordinate with udisks2 and new plugged-in devices are not mounted. 

My system is Ubuntu GNOME 13.10, uptodate, gvfs-common 1.18.2-0ubuntu1. 

I am unable to reproduce it at will. But when it does *not* work:

(0)samsung-romano:~% gvfs-mount -o

(gvfs-mount:10000): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported
Monitoring events. Press Ctrl+C to quit.

Nothing happens when I connect my disk. In the syslog I have the disk detected, see syslog excerpt at the end. 

The error above does not appear when the system works ok. Normally a logout-login reinstate the correct behavior, but really seems more a race and a random thing. 

Syslog excerpt: 

SYS: Nov 7 16:47:53 samsung-romano kernel: [11768.047108] usb 3-1: new high-speed USB device number 3 using xhci_hcd
SYS: Nov 7 16:47:53 samsung-romano kernel: [11768.076016] usb 3-1: New USB device found, idVendor=059b, idProduct=0470
SYS: Nov 7 16:47:53 samsung-romano kernel: [11768.076027] usb 3-1: New USB device strings: Mfr=10, Product=11, SerialNumber=5
SYS: Nov 7 16:47:53 samsung-romano kernel: [11768.076033] usb 3-1: Product: Storage
SYS: Nov 7 16:47:53 samsung-romano kernel: [11768.076038] usb 3-1: Manufacturer: Iomega
SYS: Nov 7 16:47:53 samsung-romano kernel: [11768.076042] usb 3-1: SerialNumber: 6E34633FFFFF
SYS: Nov 7 16:47:53 samsung-romano kernel: [11768.078192] scsi7 : usb-storage 3-1:1.0
SYS: Nov 7 16:47:53 samsung-romano mtp-probe: checking bus 3, device 3: "/sys/devices/pci0000:00/0000:00:1c.4/0000:04:00.0/usb3/3-1"
SYS: Nov 7 16:47:53 samsung-romano mtp-probe: bus: 3, device: 3 was not an MTP device
SYS: Nov 7 16:47:54 samsung-romano kernel: [11769.116539] scsi 7:0:0:0: Direct-Access ST950032 5AS PQ: 0 ANSI: 2 CCS
SYS: Nov 7 16:47:54 samsung-romano kernel: [11769.118070] sd 7:0:0:0: Attached scsi generic sg3 type 0
SYS: Nov 7 16:47:54 samsung-romano kernel: [11769.118415] sd 7:0:0:0: [sdc] 976773168 512-byte logical blocks: (500 GB/465 GiB)
SYS: Nov 7 16:47:54 samsung-romano kernel: [11769.119367] sd 7:0:0:0: [sdc] Write Protect is off
SYS: Nov 7 16:47:54 samsung-romano kernel: [11769.119381] sd 7:0:0:0: [sdc] Mode Sense: 28 00 00 00
SYS: Nov 7 16:47:54 samsung-romano kernel: [11769.120297] sd 7:0:0:0: [sdc] No Caching mode page present
SYS: Nov 7 16:47:54 samsung-romano kernel: [11769.120305] sd 7:0:0:0: [sdc] Assuming drive cache: write through
SYS: Nov 7 16:47:54 samsung-romano kernel: [11769.123622] sd 7:0:0:0: [sdc] No Caching mode page present
SYS: Nov 7 16:47:54 samsung-romano kernel: [11769.123631] sd 7:0:0:0: [sdc] Assuming drive cache: write through
SYS: Nov 7 16:47:54 samsung-romano kernel: [11769.189055] sdc: sdc1 sdc2
SYS: Nov 7 16:47:54 samsung-romano kernel: [11769.191958] sd 7:0:0:0: [sdc] No Caching mode page present
SYS: Nov 7 16:47:54 samsung-romano kernel: [11769.191969] sd 7:0:0:0: [sdc] Assuming drive cache: write through
SYS: Nov 7 16:47:54 samsung-romano kernel: [11769.191977] sd 7:0:0:0: [sdc] Attached SCSI disk
Comment 1 GNOME Infrastructure Team 2018-09-21 17:36:14 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gvfs/issues/215.