Image viewer will not read .bmp images

[tmsbrdrs]

Binary package hint: eog

The default image viewer used to view .bmp images perfectly. In fact, just a few minutes ago, it worked perfectly. A friend sent me a .bmp file and I attempted to open it with the default image viewer in Ubuntu 8.10. Thought I'd looked at the same image less than 3 minutes prior, it now won't show the images, sending me an error that BMP image has bogus header data. This happens with every bitmap file I try to open now. I've checked it with the Gimp and they open perfectly. I've also tried them in F-Spot and they open perfectly. The only change happened when I was highlighting a folder full of .bmp images to delete. A menu opened at random just as I was releasing the mouse buttom, it highlighted the top option and I have no idea what happened from there but now .bmp images won't open, even ones that have been on my computer for the past 3 months. It's not a huge deal for me, but it's something that should be fixed.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/eog
NonfreeKernelModules: nvidia
Package: eog 2.24.1-0ubuntu1
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: eog
Uname: Linux 2.6.27-11-generic i686

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

 * Is this reproducible?
 * If so, what specific steps should we take to recreate this bug?
 * Could you add an example to the bug?

 This will help us to find and resolve the problem.

[tmsbrdrs (tmsbrdrs)]

I'm still not completely sure what happened. It may be reproducible but so far, I've yet to get the ability to view .bmp images back through image viewer so I'm not sure if I could make it do this again.

I am currently running Ubuntu 8.10, fully patched with all updates.

As stated above, this happened after I highlighted a large number (30+) of .bmp images, I inadvertantly right clicked and released as my mouse buttons have a hair trigger. I think it chose the first option which is to open the images. That's all I know besides the fact that it will now not recognize .bmp image header data. I will include a screenshot of the error. As stated before, other image viewing programs such as the Gimp and F-Spot have not been effected.

[Sebastien Bacher (seb128)]

could you try on jaunty and add a bmp example to the bug if that's still an issue?

[tmsbrdrs (tmsbrdrs)]

So far it's not been a problem with Jaunty. As I stated in a previous post, I'm not completely sure what caused it in the first place as it seemed to be a completely random occurrence. If it happens with Jaunty I'll post immediately with all information available to me.

It took a few months before the problem showed on Intrepid so I wouldn't expect it to occur immediately on Jaunty.

[Sebastien Bacher (seb128)]

closing for now since that works correctly, you can reopen if you get it again though

[Sebastien Bacher (seb128)]

closing for now since that works correctly, you can reopen if you get it again though

[cometdog (ericctharley)]

This happens to me with some files that have the mime type image/png but have a .bmp extension. Not sure how the files ended up that way to begin with, but I suppose that's beside the point. In that particular use case, then it is useful to have a pointer here to
https://bugs.launchpad.net/eog/+bug/172416

[Aaron Edmistone (aaronedmistone)]

Just made the leap to Linux with Ubuntu 18.04 and am experiencing this "bug" also.

My error was specifically as @cometdog mentioned with a BMP extension with a PNG file signature (and data).

I can think of a lot of ways an image would have an incorrect extension.
It would be great if eog could do one (or more) of the following:

1. Open the image with a list of known (popular) image file signatures if it finds 'bogus header data'.
2. Warn the user that the image has a mismatching file signature and extension and suggest a correction.

If both of the above are not possible (or painful to implement) then I suggest the following:

Show the file signature along with the 'bogus header data' error message as this would also immediately point to the issue without promising that is the solution.

e.g.
BMP image has bogus header data (file signature: ".PNG....")
or even a more details button that shows this info would suffice IMO.

(apologies if this is in the wrong place, I realize it is an old report but I made an account solely for this and this is where I found my solution via google).