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 575125 - error's image doesn't show properly
error's image doesn't show properly
Status: RESOLVED DUPLICATE of bug 504538
Product: eog
Classification: Core
Component: collection
2.22.x
Other Linux
: Normal trivial
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-12 18:58 UTC by .
Modified: 2009-03-12 22:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description . 2009-03-12 18:58:21 UTC 
Please describe the problem:
When you open an image and then delete it if you reopen it going to Places > Recent Documents on Ubuntu's menu the error's image that says you that there aren't any images on that location doesn't show properly losing a part beside error's symbol.

Steps to reproduce:
1. Open an image.
2. Delete it.
3. Reopen it going to Places > Recent Documents on Ubuntu's menu.



Actual results:
The error's image that says you that there aren't any images on that location doesn't show properly losing a part beside error's symbol.

Expected results:
That error's image shows properly.

Does this happen every time?
Yes.

Other information:
When you minimize and restore, maximize or minimize the window after the image is not showed properly the image shows properly.
Comment 1 Claudio Saavedra 2009-03-12 22:12:09 UTC 
I think that you hit the bug in the message area right? This is bug 504538 and it was fixed for 2.24.

Please don't change the status of bugs without an explanation. FIXED was not the correct resolution for this bug (since no changes were made to the code after the report that would fix the issue described). If the bug you found was already fixed but not reported before, OBSOLETE is the appropriate resolution. In the case of this bug, which I think it was previously reported and fixed as bug 504538, the appropriate resolution is DUPLICATE.

Reopening.
Comment 2 Claudio Saavedra 2009-03-12 22:12:48 UTC 
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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