After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 633709 - Does not open some images by double click
Does not open some images by double click
Status: RESOLVED DUPLICATE of bug 622161
Product: eog
Classification: Core
Component: general
2.32.x
Other Linux
: Normal major
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-11-01 15:23 UTC by Michael Monreal
Modified: 2010-11-02 18:22 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michael Monreal 2010-11-01 15:23:42 UTC
If I double click *some* images in nautilus they fail to open in EOG. If this happens, either a blank EOG window shows or nothing visible happens at all (but the eog process shows up in ps). Dragging the image to the blank (or any new) EOG window displays the image just fine. If repeated, it works sometimes.

I am still not sure but think that it mainly happens for images which I modify (crop etc) in Gimp. So, a way to reproduce it:

- take a screenshot
- open in gimp, crop
- double click
- either it works or it shows the blank window or nothing
- retry if it works the first time. it always fails at some point for me

The fedora bug listed below has a sample image.

EOG bug? Gimp bug? Fedora (libpng?) bug?

I am seeing this bug for quite some time and originally reported it against Fedora 13¹ (2.30.x) but I still see it on Fedora 14 now. No idea why I didn't file the bug upstream :/

[1] https://bugzilla.redhat.com/show_bug.cgi?id=602412
Comment 1 Felix Riemann 2010-11-01 17:27:13 UTC
Do happen to use the statusbar-date plugin?
The symptoms you describe (especially the windowless eog process in the RH bug) make it sound a lot like bug 622161 to me (haven't tried yet).
Comment 2 Michael Monreal 2010-11-01 18:13:56 UTC
I was not aware of it but yes, I had that plugin active. I disabled it and tried to reproduce... seems to work! Was this plugin added (or heavily modified) in 2.30? If so, feel free to mark this as a dupe to bug 622161. I will report back if I can reproduce without the plugin. Thanks!
Comment 3 Felix Riemann 2010-11-02 18:22:09 UTC
(In reply to comment #2)
> I was not aware of it but yes, I had that plugin active. I disabled it and
> tried to reproduce... seems to work! Was this plugin added (or heavily
> modified) in 2.30? If so, feel free to mark this as a dupe to bug 622161. I
> will report back if I can reproduce without the plugin. Thanks!

The plugin's not new, it came with 2.22 or 2.24 I think. It wasn't largely modified since then, so it was practically always able to cause some trouble.
Yet there was no other way in eog to make sure it could have the data it needs without interfering with other tasks running in eog.

It didn't really show up in the last two years until well this year. Maybe things schedule a bit differently now that it can be triggered quite easily.
----
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 622161 ***