"eog uses gio now and the code issue is likely a different one and could be a gio bug"
This is not a useful response. As an end user, this functionality is broken, and has always been broken. I don't know or really care what gio is. Whichever library the problem is in, it is still a bug which I see in eog, and only in eog. If the underlying reason for the bug has changed, that's fine. But the bug still remains, so saying it is fixed is inappropriate and untrue.
"eog uses gio now and the code issue is likely a different one and could be a gio bug"
This is not a useful response. As an end user, this functionality is broken, and has always been broken. I don't know or really care what gio is. Whichever library the problem is in, it is still a bug which I see in eog, and only in eog. If the underlying reason for the bug has changed, that's fine. But the bug still remains, so saying it is fixed is inappropriate and untrue.