| Summary: | Fails to open some jpg images. Displays them once you change the zoom bar. | ||
|---|---|---|---|
| Product: | [Applications] gwenview | Reporter: | Alexis Ntounas <axel.ece> |
| Component: | general | Assignee: | Gwenview Bugs <gwenview-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | axilleas, benni |
| Priority: | NOR | ||
| Version First Reported In: | 4.10.1 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | A jpg image that Gwenview fails to open | ||
|
Description
Alexis Ntounas
2013-03-10 09:34:29 UTC
Created attachment 77910 [details]
A jpg image that Gwenview fails to open
Can't reproduce using the same version in archlinux I know 2 more people using Archlinux facing this bug. For one of them the above image is sometimes displayed correctly and some others it isn't. The strange thing is that it doesn't happen for all the images and I can't find a logical pattern for those it happens. Is there something else I could do to give you more info? Can't reproduce this either (Kubuntu 12.10, KDE 4.10.1). Does the window size affect this in any way? If I open the image and gwenview is maximized it doesn't appear. If it is a small window it appears correctly. Moreover if I open it maximized and then resize it the image appears. This is reproducible if image's resolution is big and Gwenview is opened maximized. (In reply to comment #6) > This is reproducible if image's resolution is big and Gwenview is opened > maximized. Can you test if this occurs with variable screen resolutions? (In reply to comment #7) > Can you test if this occurs with variable screen resolutions? My native screen resolution in which the problem appears is 1680x1050. I've tested the following resolutions but the problem didn't appear. 1280x1024 1280x1960 1152x864 Thanks. That's what I expected. In 4.11.0 I haven't experienced this problem. I guess you could close the issue. Thanks for the update. If you see this bug again, please add a comment, or reopen it. |