BestImageViewer / geeqie

claiming to be the best image viewer / photo collection browser
http://www.geeqie.org/
GNU General Public License v2.0
488 stars 79 forks source link

After some directory changes the mouse click to images does not work anymore #847

Open mowgli opened 3 years ago

mowgli commented 3 years ago

ISSUE TYPE

GEEQIE VERSION

master (f34ea0700048)

GTK3

The following is always needed for me to use my mouse in gtk3; so this bug might be connected… export GDK_CORE_DEVICE_EVENTS=1

OS / DISTRIBUTION

Devuan (Debian) Sid

SUMMARY

Some times, after several directory changes without changing the pictures in dirs in between the mouse stops working for changing the pictures. Although, everything else work; going to fullscreen by double click, wheel, changing dirs, … work well. Only clicking to the image in the file list doesn't.

STEPS TO REPRODUCE

I have no real idea. Sometimes it works, sometimes it doesn't.

mowgli commented 3 years ago

An unset GDK_CORE_DEVICE_EVENTS doesn't matter.

tomaszg7 commented 3 years ago

https://github.com/BestImageViewer/geeqie/issues/769

mowgli commented 3 years ago

Ah, thanks for the hint. However, it does not show, where the error is located.

I even tried to bisect but I do not find a working version to start with. I think, I have a pretty good way to reporduce it. Even if not 100% sure it is a start.

tomaszg7 commented 3 years ago

Yeah, I didn't know either. The bug might not even be inside Geeqie, might be e.g. some change in gtk or other lib.

If I find more time, I'll probably try to do something about it, probably starting with sprinkling the code with excess of debug messages to pinpoint where exactly the problem happens.

mowgli commented 3 years ago

I tested with gtk2 now. The bug are definitively related to gtk3.

Not only that, geeqie is much more faster with gth2 than with gtk3!

But there is one, maybe related issue. In gtk2 (not in gtk3) some directory changes are not updated in the dir- and file- lists. One have to scroll in one of them to get them both updated. Maybe this is how the bug is manifested in gtk2.