[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#333273: marked as done (xvfb: Uses incorrect line padding when depth>8)

Your message dated Fri, 16 Feb 2007 23:08:45 +0100
with message-id <45D62B6D.2040105@ens-lyon.org>
and subject line Bug#333273: xvfb: Uses incorrect line padding when depth>8
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: xvfb
Version: 4.3.0.dfsg.1-14sarge1
Severity: important

According to the Xvfb manual page, the -fbdir option can be used to
make it expose its framebuffer in X window dump format.  However, if
it is run with a depth of 32, the bytes_per_line member of the
XWDHeader structure is set to 4 * width but each line is actually
padded to 16 * width.  Similarly, if it is run with a depth of 16,
bytes_per_line is set to 2 * width but lines are padded to 4 * width.
This makes the feature quite useless.  It is, however, possible to
generate correct window dumps using xwd -root.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-2-686
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages xvfb depends on:
ii  libc6                  2.3.2.ds1-22      GNU C Library: Shared libraries an
ii  libfreetype6           2.1.7-2.4         FreeType 2 font engine, shared lib
ii  xfree86-common         4.3.0.dfsg.1-14   X Window System (XFree86) infrastr
ii  zlib1g                 1:1.2.2-4.sarge.2 compression library - runtime

-- no debconf information

--- End Message ---
--- Begin Message --- 
I think this has been fixed in upstream XFree86 right after 4.3.0 got
released. So it's probably fixed in Xorg nowadays.

Brice

--- End Message ---
Reply to: