This seems also affect Anjuta, in ubuntu 15.10 (so with glib 2.416.1) more badly as this faulty let think sourceview that the file saved was just deleted.
If you open a file with anjuta dev studio, make a change, and save, you get a warning message: "The file xxx has been deleted on the disk. Do you ant to close it ?" [Deleted] [Cancel]
this is due to g_file_monitor_file that faulty report a G_FILE_MONITOR_EVENT_DELETED
at this very exact moment, when enable debug for glib with G_MESSAGE_DEBUG=all (otherwise it is silent), glib raise a
(anjuta:20012): GLib-CRITICAL **: Source ID 4909 was not found when attempting to remove it
Hi,
This seems also affect Anjuta, in ubuntu 15.10 (so with glib 2.416.1) more badly as this faulty let think sourceview that the file saved was just deleted.
If you open a file with anjuta dev studio, make a change, and save, you get a warning message: "The file xxx has been deleted on the disk. Do you ant to close it ?" [Deleted] [Cancel] MONITOR_ EVENT_DELETED
this is due to g_file_monitor_file that faulty report a G_FILE_
at this very exact moment, when enable debug for glib with G_MESSAGE_DEBUG=all (otherwise it is silent), glib raise a
(anjuta:20012): GLib-CRITICAL **: Source ID 4909 was not found when attempting to remove it