Bug#333273: xvfb: Uses incorrect line padding when depth>8

2005-10-11 Thread Ben Hutchings
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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#333273: xvfb: Uses incorrect line padding when depth>8

2007-02-17 Thread Ben Hutchings
reopen 333273
close 333273 1:1.0.2-8.1

Brice Goglin wrote:
> I think this has been fixed in upstream XFree86 right after 4.3.0 got
> released. So it's probably fixed in Xorg nowadays.

Agreed.  I can see the bug fix in Xorg's git tree way back in 2003 (!)
and have verified this fix in the current version in Debian.  Therefore
I'm closing this with the first version number for xorg-server in
Debian.

Ben.

-- 
Ben Hutchings
It is easier to change the specification to fit the program than vice versa.


signature.asc
Description: This is a digitally signed message part