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 772092 - GUnixMountMonitor's mounts-changed signal no longer activates
GUnixMountMonitor's mounts-changed signal no longer activates
Status: RESOLVED DUPLICATE of bug 662946
Product: glib
Classification: Platform
Component: gio
2.50.x
Other Linux
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2016-09-27 23:53 UTC by Chris Vine
Modified: 2016-09-29 21:37 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
test case (529 bytes, text/x-csrc)
2016-09-28 09:39 UTC, Chris Vine 		Details

Description Chris Vine 2016-09-27 23:53:01 UTC 
The 'mounts-changed' signal for GUnixMountMonitor objects constructed by g_unix_mount_point_get() no longer emits when mounts change, when using glib-2.50.0.

It works fine with glib-2.48.
Comment 1 Chris Vine 2016-09-27 23:55:44 UTC 
Sorry that should be "... constructed by g_unix_mount_monitor_get()".
Comment 2 Chris Vine 2016-09-28 09:39:32 UTC 
Created attachment 336423 [details]
test case
Comment 3 Chris Vine 2016-09-28 16:27:34 UTC 
On further testing, the source of the problem appears to be the linux libmount code.  It seems to break GUnixMountMonitor, which is a nuisance.
Comment 4 Ondrej Holy 2016-09-29 09:34:23 UTC 
Thanks for your report. I've already pushed a fix for it.

*** This bug has been marked as a duplicate of bug 662946 ***
Comment 5 Chris Vine 2016-09-29 21:37:06 UTC 
That fixes it for me.  It would be useful if you (or whoever decides such things) were to consider issuing a 2.50.1 release at some point.  This is going to break quite a lot of stuff.