gedit does not detect replaced open file

[Nedim Srndic]

Hello,

You can reproduce this bug like this:
1. make two test files with the same name, but in two different directories and with different content
2. make sure one of them is older than the other (in terms of creation and modification time, I didn't test which of those matters)
3. open the newer file in gedit (do NOT close gedit from this point on)
4. move the newer file to a different location
5. move the older file to be in the same directory where the newer file was in step 3
6. double click the older file in a file manager, the gedit window shows the contents of the newer file, i.e., it does not show the usual "File contents changed on disk, reload or cancel?" question.

Thank you!

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: gedit 2.30.3-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-31.62-generic 2.6.35.13
Uname: Linux 2.6.35-31-generic x86_64
NonfreeKernelModules: openafs
Architecture: amd64
Date: Tue Nov 22 11:18:45 2011
ExecutablePath: /usr/bin/gedit
InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
SourcePackage: gedit
XsessionErrors:
 (gnome-power-manager:2087): Gtk-WARNING **: A floating object was finalized. This means that someone
 (polkit-gnome-authentication-agent-1:2267): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Walter Garcia-Fontes (walter-garcia)]

I tried to reproduce, and in step 6 I get gedit showing the older file, and saying:

This file (/location/test1.txt) is already open in another gedit window.
gedit opened this instance of the file i a non-editable way. Do you want to edit anyway?

It shows the content of the "old" file as it should.

I don't see any unexpected behavior here.

[Nedim Srndic (nedim-sh)]

Maybe this has been fixed in later versions, I use Ubuntu 10.10 with all updates applied. I can only say that I can reproduce it on my system.

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

[Walter Garcia-Fontes (walter-garcia)]

I think I finally could reproduce this bug and I have reported it upstream.

[Paul White (paulw2u)]

Upstream bug closed "RESOLVED FIXED" on 2016-07-26
Checked ok with Ubuntu 18.04 and gedit 3.28.1
Marking as "Fix Released" to close