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 352500 - misdisplays ordinary pbm
misdisplays ordinary pbm
Status: RESOLVED FIXED
Product: gdk-pixbuf
Classification: Platform
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2006-08-23 08:27 UTC by Daniel Holbach
Modified: 2010-07-10 04:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Daniel Holbach 2006-08-23 08:27:50 UTC
Forwarded from: https://launchpad.net/distros/ubuntu/+source/eog/+bug/57125

See attached screenshot showing strange diagonal stripy artefacts. bug.png is the screenshot of my whole screen showing eog misbehaving but ImageMagick working. t.pbm is the file in question.

Here is the output of xdpyinfo:

liberator:~> xdpyinfo
name of display: :0.0
version number: 11.0
vendor string: The X.Org Foundation
vendor release number: 60801000
maximum request size: 16777212 bytes
motion buffer size: 256
bitmap unit, bit order, padding: 32, LSBFirst, 32
image byte order: LSBFirst
number of supported pixmap formats: 7
supported pixmap formats:
    depth 1, bits_per_pixel 1, scanline_pad 32
    depth 4, bits_per_pixel 8, scanline_pad 32
    depth 8, bits_per_pixel 8, scanline_pad 32
    depth 15, bits_per_pixel 16, scanline_pad 32
    depth 16, bits_per_pixel 16, scanline_pad 32
    depth 24, bits_per_pixel 32, scanline_pad 32
    depth 32, bits_per_pixel 32, scanline_pad 32
keycode range: minimum 8, maximum 255
focus: window 0x3e00022, revert to PointerRoot
number of extensions: 30
    BIG-REQUESTS
    DAMAGE
    DOUBLE-BUFFER
    DPMS
    Extended-Visual-Information
    GLX
    LBX
    MIT-SCREEN-SAVER
    MIT-SHM
    MIT-SUNDRY-NONSTANDARD
    RANDR
    RECORD
    RENDER
    SECURITY
    SGI-GLX
    SHAPE
    SYNC
    TOG-CUP
    X-Resource
    XC-APPGROUP
    XC-MISC
    XFIXES
    XFree86-Bigfont
    XFree86-DGA
    XFree86-Misc
    XFree86-VidModeExtension
    XInputExtension
    XKEYBOARD
    XTEST
    XVideo
default screen number: 0
number of screens: 1

screen #0:
  dimensions: 1600x1200 pixels (406x305 millimeters)
  resolution: 100x100 dots per inch
  depths (7): 24, 1, 4, 8, 15, 16, 32
  root window id: 0x40
  depth of root window: 24 planes
  number of colormaps: minimum 1, maximum 1
  default colormap: 0x20
  default number of colormap cells: 256
  preallocated pixels: black 0, white 16777215
  options: backing-store NO, save-unders NO
  largest cursor: 64x64
  current input event mask: 0xd2001d
    KeyPressMask ButtonPressMask ButtonReleaseMask
    EnterWindowMask StructureNotifyMask SubstructureRedirectMask
    PropertyChangeMask ColormapChangeMask
  number of visuals: 8
  default visual id: 0x23
  visual:
    visual id: 0x23
    class: TrueColor
    depth: 24 planes
    available colormap entries: 256 per subfield
    red, green, blue masks: 0xff0000, 0xff00, 0xff
    significant bits in color specification: 8 bits
  visual:
    visual id: 0x24
    class: TrueColor
    depth: 24 planes
    available colormap entries: 256 per subfield
    red, green, blue masks: 0xff0000, 0xff00, 0xff
    significant bits in color specification: 8 bits
  visual:
    visual id: 0x25
    class: TrueColor
    depth: 24 planes
    available colormap entries: 256 per subfield
    red, green, blue masks: 0xff0000, 0xff00, 0xff
    significant bits in color specification: 8 bits
  visual:
    visual id: 0x26
    class: TrueColor
    depth: 24 planes
    available colormap entries: 256 per subfield
    red, green, blue masks: 0xff0000, 0xff00, 0xff
    significant bits in color specification: 8 bits
  visual:
    visual id: 0x27
    class: DirectColor
    depth: 24 planes
    available colormap entries: 256 per subfield
    red, green, blue masks: 0xff0000, 0xff00, 0xff
    significant bits in color specification: 8 bits
  visual:
    visual id: 0x28
    class: DirectColor
    depth: 24 planes
    available colormap entries: 256 per subfield
    red, green, blue masks: 0xff0000, 0xff00, 0xff
    significant bits in color specification: 8 bits
  visual:
    visual id: 0x29
    class: DirectColor
    depth: 24 planes
    available colormap entries: 256 per subfield
    red, green, blue masks: 0xff0000, 0xff00, 0xff
    significant bits in color specification: 8 bits
  visual:
    visual id: 0x2a
    class: DirectColor
    depth: 24 planes
    available colormap entries: 256 per subfield
    red, green, blue masks: 0xff0000, 0xff00, 0xff
    significant bits in color specification: 8 bits
liberator:~>

(attachments will follow shortly)



http://librarian.launchpad.net/3962587/bug.png (screenshot)
http://librarian.launchpad.net/3962602/t.pbm (file in question)
Comment 1 Felix Riemann 2006-08-27 17:16:02 UTC
This seems to be a problem with GdkPixbuf, because it shows up as well when showing the image with a GtkImage widget.
Comment 2 Lucas Rocha 2006-08-30 14:43:30 UTC
I confirm this as a gdk-pixbuf bug. It appears in F-spot and GThumb too. Re-assigning to gtk+/gdk-pixbuf
Comment 3 Matthias Clasen 2006-08-31 05:26:58 UTC
Looks like pnm_read_ascii_scanline should simply fill the pixbuf, rather
than trying to collect bits and then call that explode function.
Comment 4 Matthias Clasen 2006-09-29 02:41:36 UTC
I believe I fixed this a while ago.
Reopen if not.
Comment 5 Daniel Holbach 2006-09-29 10:52:40 UTC
Not fixed with GTK 2.10.3 and eog 2.16.0.1, works nicely with gimp 2.2.13 though - might be fixed in GTK 2.10.4 though - although ftp://ftp.gnome.org/pub/GNOME/sources/gtk+/2.10/gtk+-2.10.4.news doesn't look like it.
Comment 6 Matthias Clasen 2006-09-29 12:22:42 UTC
From  gdk-pixbuf/ChangeLog:

2006-09-22  Matthias Clasen  <mclasen@redhat.com>

        * === Released 2.10.4 ===

2006-09-06  Matthias Clasen  <mclasen@redhat.com>

        * io-pnm.c: Simplify and fix reading of ASCII images.


Sorry that I forgot to mention that fix in the NEWS
Comment 7 Daniel Holbach 2006-09-29 13:11:33 UTC
Thanks a lot - I'll report back with 2.10.4 - thanks again, you ROCK!