Bug 236640 - Xvfb fails silently
Xvfb fails silently
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: xorg-x11-server (Show other bugs)
4.4
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Adam Jackson
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-04-16 17:47 EDT by Carlie J. Coats, Jr.
Modified: 2012-04-17 15:23 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-04-17 15:23:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Carlie J. Coats, Jr. 2007-04-16 17:47:26 EDT
Description of problem:

Invoking "Xvfb :35 -screen 1.0 2536x2536x24 -ac &" in order to then
use Xvfb to render-and-capture images _seems_ to succeed -- no obvious
failure, no messages.n  But the rendered images are all 1280x1024.
Note that "man Xvfb" shows examples with resolution greater than 1280x1024.

Version-Release number of selected component (if applicable):

xorg-x11-Xvfb-6.8.2-1.EL. 13.37.2 RPM

How reproducible:
reliably

Steps to Reproduce:
1.Xvfb :35 -screen 1.0 2536x2536x24 -ac &
2.setenv DISPLAY localhost:35
3.display a large image
4.Do an ImageMagick screen capture on screen 35
  
Actual results:
Screen capture has resolution 1280x1024

Expected results:
Screen capture has resolution MIN( actual resolution, 2536x2536 )


Additional info:
Comment 1 Adam Jackson 2007-08-17 10:23:44 EDT
What's the imagemagick command you're using to do the capture?
Comment 2 Carlie J. Coats, Jr. 2007-08-17 10:52:52 EDT
import -window root foo.gif
Comment 3 Carlie J. Coats, Jr. 2007-08-17 10:54:37 EDT
  import -window root foo.gif
Comment 4 Adam Jackson 2012-04-17 15:23:21 EDT
No further non-security updates are planned for xorg-x11 in RHEL4.  If this issue is not addressed in RHEL5 or newer, please update the affected product version and reopen this bug.

Note You need to log in before you can comment on or make changes to this bug.