Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
G
GLib
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 926
    • Issues 926
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 61
    • Merge Requests 61
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GNOME
  • GLib
  • Issues
  • #746

Closed
Open
Opened Aug 18, 2013 by bugzilla-migration@bugzilla-migrationReporter

GFileMonitor cease to emit events after monitored symlink on it is deleted.

Submitted by A.G.

Link to original bug (#706222)

Description

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.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: GNOME/glib#746