imported bitmaps all have alpha problems

Not reproduced with Inkscape 0.48.2, 0.48.3 and 0.48+devel r11180 on Mac OS X 10.5.8 (32bit) and OS X 10.7.2 (64bit)

> Inkscape version: 0.48.3.1 r9886, KDE 4.8

Which linux distro? Did you compile it yourself from source, or installed it via package manager?

Could you attach a sample SVG file with such an imported image, as well as the linked bitmap image?

The distro is Sabayon 8 (64 bit), package installed from the repository.

More research:

I embedded an image into an SVG file and opened it on an Ubuntu machine with Inkscape .48.2. It looks fine on there. However, the reverse situation does not work; opening an SVG made in a previous Inkscape version in .48.3.1 has all images (embedded or linked) with .251 alpha.

It only seems to affect the display of bitmaps (both in the preview dialog and when editing) since using the "trace bitmap" function on a bitmap produces a normal looking trace with 100% opacity.

Attached is a screenshot of the problem in the "Import" window. The left window shows the preview in Gimp (as it should look), the right window shows the problem in Inkscape. (The same file is selected in both windows.)

Found a workaround:

Under "Bitmaps" in "Inkscape Preferences" change oversampling to "none" (default was 2x2). An interesting effect is the higher the oversampling is set, the more transparent the bitmap images become.

I seem to have the same issue.

I'm on sabayon linux with inkscape 0.48.3.1 (r9886).

This issues only seems to affect the display of bitmaps. Exported png look fine.

Setting the oversampling to 'none' indeed makes things look normal again.

Setting bug status to 'Confirmed' based on second user report.

Sorry, I forgot. I'm also on 64bit.

suv mentioned that it might have to do something with cairo. I have cairo-1.10.2-r2, if that's of any help.

Please let me know if you need more info.

FYI, on a 32bit sabayon linux installation with the same version of inkscape (0.48.3.1 r9886) this error does not occur. All dependencies are up to date on both machines, and the issue is only present on the 64bit system.

I can confirm the problem on an up-to-date Sabayon (9), 64bit. The workaround works, too.

Is this still happening with 0.91 or 0.92? If yes, please attach example file.