gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed

[dino99]

I have no idea about the package to blame: gvfs/udev/kernel ?

This is now logged:
gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gvfs 1.35.91-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
Uname: Linux 4.15.0-11-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Feb 27 14:21:10 2018
EcryptfsInUse: Yes
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gvfs
UpgradeStatus: No upgrade log present (probably fresh install)

[Cliff Carson (ccarson1)]

Trying to install daily build 3/1/18 and seeing the install window close (no error indicated) right after collecting user data from the Who are You screen. Checking the syslog on the install system found this error as the last entry.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Cliff Carson (ccarson1)]

The prior attempt to install was with a USB. Create a bootable DVD with the same daily build level and the install process failed at the same location, right after the Who are You? screen. Couldn't get to the syslog because the install process was no longer responding so could not verify the G_UDEV_IS_DEVICE failure message.

[Willem Hobers (whobers)]

Same problem here: Xubuntu 18.04, daily.

Mar 14 18:52:27 Xubuntu-18-04 gvfsd-metadata[1628]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
Mar 14 18:52:27 Xubuntu-18-04 gvfsd-metadata[1628]: message repeated 7 times: [ g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed]

In this case it's on a working install of 18.04.

Is there more information I can provide to help?

[Jerry Bezencon (valtam)]

Same issue here: Ubuntu 18.04 daily build, dated 14-03-18
message repeated 7 times: [ g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed]

Crashing during install. Can't get an install.

[dino99 (9d9)]

The error is now gone.

[h9000 (h9000)]

still have it here on 18.04

Apr 19 17:22:05 acer533 gvfsd-metadata[1719]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
Apr 19 17:22:05 acer533 gvfsd-metadata[1719]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed

[Andrew Sabolsky (cleverusb)]

I have this issue also.

Distributor ID: Ubuntu
Description: Ubuntu 18.04 LTS
Release: 18.04
Codename: bionic

And I'm running the latest version of gvfs.

[lengyanhua (lengyanhua)]

Has this bug been fixed?
I encountered this when I trying to install the latest version of 18.04.

[David Wilcox (davidlukewilcox)]

I just got the issue on an image I downloaded two days ago. :( Not sure what to do from here.

[A. Denton (aquina)]

I can confirm the problem on my system:

gvfsd-metadata[PID]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
(hundrets of entries ...)

As a temporary workaround I killed (only) the gvfsd-metadata process (will auto-respawan, unless changed in systemd) and erased the local gfvs-metadata directory (will be recreated with a file in it):

$ sudo pkill gvfsd-metadata
$ rm -rf ~/.local/share/gvfs-metadata

After that the logs disappeared from my system.

Removing removing its binary /usr/libexec/gvfsd-metadata however is not a good practice, since it may lock up your system.

As a better alternative I tried to change /usr/share/dbus-1/session.conf like this (right before the </busconfig> directive/tag):

<!-- Added by TRON-DELTA.ORG for Xubuntu SE 2018 (3 lines) -->
  <policy context="default">
    <deny send_destination="org.gtk.vfs.Metadata"/>
  </policy>

and changed /usr/lib/gvfs/gvfsd-metadata via:
$ sudo chmod 000 /usr/lib/gvfs/gvfsd-metadata

Unfortunately though this led to further problems and a lock-up, not allowing to open further applications like the Thunar file explorer:

systemd[PID]: gvfs-metadata.service: Failed to execute command: Permission denied
systemd[PID]: gvfs-metadata.service: Failed at step EXEC spawning /usr/lib/gvfs/gvfsd-metadata: Permission denied

Maybe just the D-Bus rule would have been enough?

[Chapliev Viktor (viktor-tch)]

I found this fix:
https://gitlab.gnome.org/GNOME/gvfs/commit/d7e1397854f32e793b4f65d894908d67072dcb3f

[javen (jwli)]

This bug affects me, wait for updating

[Steven Clarkson (sclarkson)]

I encounter this problem trying to install 18.04.2 in QEMU

[Zhanglei Mao (zhanglei-mao)]

One of IHV parnter get this issues too during stressapp + iperf testing. LP#1823615

[Danilo Saft (proxyseven)]

I have the same problem when trying to start the current mysql service after changing the datadir in the mysql.d cnf file. Using 18.04 LTS.

[Antonio (tonecas)]

same problem here. don't know where this is coming from but it maybe related to this:

https://gitlab.gnome.org/GNOME/gvfs/commit/d7e1397854f32e793b4f65d894908d67072dcb3f

my system (inxi -Fxz):
System: Host: Work Kernel: 4.15.0-48-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Xfce 4.12.3 (Gtk 2.24.31)
           Distro: Ubuntu 18.04.2 LTS
Machine: Device: desktop Mobo: ASRock model: B450M Pro4 serial: <filter>
           UEFI [Legacy]: American Megatrends v: P1.10 date: 06/19/2018
CPU: Quad core AMD Ryzen 5 2400G with Radeon Vega Graphics (-MT-MCP-) arch: Zen rev.0 cache: 2048 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 28746
           clock speeds: max: 3600 MHz 1: 2156 MHz 2: 2065 MHz 3: 1736 MHz 4: 1732 MHz 5: 1970 MHz 6: 2145 MHz
           7: 3763 MHz 8: 3765 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series]
           bus-ID: 38:00.0
           Display Server: X.Org 1.19.6 drivers: ati,amdgpu (unloaded: modesetting,fbdev,vesa,radeon)
           Resolution: 1920x1080@59.93hz
           OpenGL: renderer: AMD RAVEN (DRM 3.23.0, 4.15.0-48-generic, LLVM 7.0.0)
           version: 4.5 Mesa 18.2.8 Direct Render: Yes
Audio: Card-1 Advanced Micro Devices [AMD] Device 15e3 driver: snd_hda_intel bus-ID: 38:00.6
           Card-2 Advanced Micro Devices [AMD/ATI] Device 15de driver: snd_hda_intel bus-ID: 38:00.1
           Sound: Advanced Linux Sound Architecture v: k4.15.0-48-generic
Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: f000 bus-ID: 1f:00.0
           IF: enp31s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: HDD Total Size: 1000.2GB (20.7% used)
           ID-1: /dev/nvme0n1 model: Samsung_SSD_970_EVO_500GB size: 500.1GB
           ID-2: /dev/sda model: WDC_WD5000AAKS size: 500.1GB temp: 43C
Partition: ID-1: / size: 458G used: 72G (16%) fs: ext4 dev: /dev/nvme0n1p1
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 57.5C mobo: N/A gpu: 0.0
           Fan Speeds (in rpm): cpu: N/A
Info: Processes: 384 Uptime: 15 days Memory: 12261.7/15025.5MB Init: systemd runlevel: 5 Gcc sys: 7.4.0
           Client: Shell (sudo) inxi: 2.3.56

[A. Denton (aquina)]

Yes Antonio (tonecas), this looks promising indeed.

Could the Ubuntu Developers please look in to https://gitlab.gnome.org/GNOME/gvfs/commit/d7e1397854f32e793b4f65d894908d67072dcb3f and port this to "gvfs (Ubuntu)" and rebuild?

Thanks!

[Stéphane Gourichon (stephane-gourichon-lpad)]

Still observed here.

This floods systemd's log, around 10 messages per second.

At first glance, the commit mentioned above seem relevant.

Even if a proper fix takes time to be incorporated, I'd be happy with a workaround, but am clueless where to start man gvfds-metadata offers no relevant option. Killing gvfsd-metadata only yields another one. Parent process is systemd. Disabling /usr/lib/systemd/user/gvfs-metadata.service will probably break file managers, filesystem mounts and the like. Any hint appreciated.

Thanks.

[Manish Jangid (manishjangid)]

g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed happens on my device as of recently downloaded image

H/W path Device Class Description
===============================================================
                                     system Inspiron 5558 (Inspiron 5558
/0 bus Motherboard
/0/0 memory 64KiB BIOS
/0/46 processor Intel(R) Core(TM) i5-5250U C
/0/46/37 memory 32KiB L1 cache
/0/46/3c memory 256KiB L2 cache
/0/46/41 memory 3MiB L3 cache
/0/32 memory 32KiB L1 cache
/0/50 memory 4GiB System Memory
/0/50/0 memory DIMM [empty]
/0/50/1 memory 4GiB SODIMM DDR3 Synchronous
/0/100 bridge Broadwell-U Host Bridge -OPI
/0/100/2 display HD Graphics 6000
/0/100/3 multimedia Broadwell-U Audio Controller
/0/100/14 bus Wildcat Point-LP USB xHCI Co
/0/100/14/0 usb2 bus xHCI Host Controller
/0/100/14/0/2 scsi4 storage Cruzer Blade
/0/100/14/0/2/0.0.0 /dev/sdb disk 7794MB Cruzer Blade
/0/100/14/0/2/0.0.0/0 /dev/sdb disk 7794MB
/0/100/14/0/2/0.0.0/0/1 /dev/sdb1 volume 7432MiB Windows FAT volume
/0/100/14/0/5 multimedia Integrated_Webcam_HD
/0/100/14/0/6 communication Bluetooth wireless interface
/0/100/14/0/8 generic USB2.0-CRW
/0/100/14/1 usb3 bus xHCI Host Controller
/0/100/16 communication Wildcat Point-LP MEI Control
/0/100/1b multimedia Wildcat Point-LP High Defini
/0/100/1c bridge Wildcat Point-LP PCI Express
/0/100/1c.2 bridge Wildcat Point-LP PCI Express
/0/100/1c.2/0 wlp6s0 network Wireless 3160
/0/100/1c.3 bridge Wildcat Point-LP PCI Express
/0/100/1c.3/0 enp7s0 network RTL8101/2/6E PCI Express Fas
/0/100/1c.4 bridge Wildcat Point-LP PCI Express
/0/100/1c.4/0 display GK208M [GeForce 920M]
/0/100/1d bus Wildcat Point-LP USB EHCI Co
/0/100/1d/1 usb1 bus EHCI Host Controller
/0/100/1d/1/1 bus USB hub
/0/100/1f bridge Wildcat Point-LP LPC Control
/0/100/1f.2 storage Wildcat Point-LP SATA Contro
/0/100/1f.3 bus Wildcat Point-LP SMBus Contr
/0/1 scsi0 storage
/0...

[TJ (tj)]

I've built a test package for 18.04 in my PPA if you want to test it:

https://launchpad.net/~tj/+archive/ubuntu/bugfixes

[A. Denton (aquina)]

Hello TJ, your gvfs-package build on https://launchpad.net/~tj/+archive/ubuntu/bugfixes seems to have resolved the problem for me! Therefore, a 1000 thanks! :-)

[MasterCATZ (mastercatz)]

hey TJ have you got a version for 19.10 ?

aio@aio:/usr/libexec$ sudo add-apt-repository ppa:tj/bugfixes

 Home for my bug-fix test packages to be tested by users
 More info: https://launchpad.net/~tj/+archive/ubuntu/bugfixes
Press [ENTER] to continue or Ctrl-c to cancel adding it.

Ign:7 http://ppa.launchpad.net/tj/bugfixes/ubuntu eoan InRelease
Err:8 http://ppa.launchpad.net/tj/bugfixes/ubuntu eoan Release

Get:9 http://archive.ubuntu.com/ubuntu eoan-security InRelease [97.5 kB]
Reading package lists... Done
E: The repository 'http://ppa.launchpad.net/tj/bugfixes/ubuntu eoan Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

[Elbarbudo (patricearnal)]

In my case, the bug apparead when I mounted an encfs volume andf began to navigate on it

Linux Mint 19.3 (based on Ubuntu)

[Vladislav (nuklea)]

In my case, the bug apparead when I mounted an Cryptomator volume and began to navigate on it. Ubuntu 18.04