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 706222 - GFileMonitor cease to emit events after monitored symlink on it is deleted.
GFileMonitor cease to emit events after monitored symlink on it is deleted.
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: gio
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2013-08-18 00:31 UTC by A.G.
Modified: 2018-05-24 15:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description A.G. 2013-08-18 00:31:58 UTC 
Steps to reproduce:
1) create GFileMonitor for some directory - /tmp for example;
2) create symlink pointing to the same directory:
  ln -s . test
3) create GFileMonitor for /tmp/test;
4) delete directory /tmp/test;
5) unref monitor for /tmp/test;
6) monitor for /tmp don't receive any events anymore.

The bug was reported for GLib 2.37, I've got the same behavior on 2.30, didn't test on any other versions.
Comment 1 GNOME Infrastructure Team 2018-05-24 15:37:15 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/glib/issues/746.