On Thu, Jun 22, 2017 at 4:00 PM, Ondrej Holy <oholy redhat com> wrote:
1) Let's deal with the issue on that bug report you mentioned. Sounds like unix volume monitor is used for some reason instead of udisks2 volume monitor...
Alright.
The reporter of the first issue claims that it helps to downgrade glib to 2.52.0. Does it help also for this issue? I suppose it doesn't...
No. It did. These mounts/volumes do't appear with glib 2.52.0
it is probably because unix volume monitor is used as fallback instead of udisks2 volume monitor, because user session is not running for root user.
Yes. You are right. gvfs-mount -l from root terminal gives me something like this:
Volume(58): pstore
Type: GUnixVolume
Mount(0): pstore -> file:///sys/fs/pstore
Type: GUnixMount
Volume(
2=59): debug
Type: GUnixVolume
Mount(0): debug -> file:///sys/kernel/debug
Type: GUnixMount
Volume(60): security
Type: GUnixVolume
Mount(0): security -> file:///sys/kernel/security
Libmount support has been introduced quite recently (see https://bugzilla.gnome.org/show_bug.cgi?id=522053 ) and it probably exposes more mounts than it was exposed before. The unix volume monitor
need some tweaks probably. It would be nice to file a new bug report for glib if there is not any...
I would like to mention that glib-2.52.0 was also compiled against libmount.
Thanks.
