Bug 451789

General Escalation Information

State the problem

  1. Provide time and date of the problem
  
  The problem was reported in CRM #1825054 on 06-May-2008
  
  2. Provide clear and concise problem description as it is understood at the
time of escalation
         * Observed behavior
        
         Using Xvnc, the GLX extension is not available.
        
         * Desired behavior

         The GLX extension should be available.
        
  3. State specific action requested of SEG
  
  Analyse the proposed patch (attached) and escalate in Bugzilla if appropriate.
  
  4. State whether or not a defect in the product is suspected
  
  The problem does not lie in Xvnc, but rather in the build of the rpm package
for vnc-server.
  
  According to the patches already included in the src.rpm, GLX should be
enabled. This can be verified by looking at the patch "vnc-opengl.patch" which
reads:
  
      -#define BuildGlxExt NO
      +#define BuildGlxExt YES

  Unfortunately, this is not sufficient to enable GLX in the build of the
Xserver in Xvnc. This is because in RHEL5, we are using mesa 6.5.1 with Xorg 7.1
and Xorg requires some additional patches to be able to build against this
version of Mesa. The required patches are included in the "regular" Xorg build
(ie "xorg-x11-server") but these patches were not included in the vnc package.
  
  The attached patches are described hereafter:
  
  - vnc-xorg-x11-server-1.1.1-mesa-6.5.1.patch
  
  This patch modifies the build procedure of the Xserver (included in vnc for
Xvnc) so it can make use of Mesa 6.5.1 that ships with RHEL5 - This patch is
based on a similar patch for the "xorg-x11-server" package on RHEL5, slightly
modified.
  
  - vnc-xorg-x11-server-1.1.1-selinux-awareness.patch
  
  Enabling Mesa requires another patch for SELinux awareness. This patch is
similar to the one that comes with "xorg-x11-server".
  
  - vnc-crm1825054.spec.patch
  
  This is for the spec file, applying the two previous patches at build time.
Please note that GLX should not be enabled on some architecture (namely s390
s390x ppc64, that was already the case previously)
  
         * Provide Bugzilla if one already exists
        
  There is BZ#185442 - "CRM 805548: [Synopsis] OpenGL support for Xvnc
(vnc-server)" but the resolution seems incomplete due to the reasons exposed above.
  
Provide supporting info

  1. State other actions already taken in working the problem:

  Check in BZ, but the patch is not sufficient to enable GLX in Xvnc.

Hi,

Customer has now confirmed that the patch does indeed enable GLX in Xvnc and
works as expected.

He also gave the following justification for the need of GLX in Xvnc:

" I view the missing GLX suppport as a bug, I can't see any reason why it
shouldn't be there. To us it's very critical. To run time computationally
demending and time consuming CFD/CAE optimization on server using vnc is the
best solution we have found. We recommend it to our customers and I'm sure it's
used by many people. [...]"

Cheers,
Olivier.

  2. Attach sosreport
  
  3. Attach other supporting data

  N/A

  4. Provide issue repro information:

  Run Xvnc :1 -ac
  run xterm -display :1
  Check glxinfo, there is no GLX support.

  5. List any known hot-fix packages on the system
  
  None.
  
  6. List any customer applied changes from the last 30 days
  
  None.

RHEL specific
Note - A core file should be uploaded to a test system whether it is a kernel
core or from some other component.

  1. Provide core file (if one is involved) and state:
  
  No core, there is no crash involved.

  2. Provide the base and kernel info output from ''checksysreport''

   #######     Kernel info      ########
   kernel-2.6.18-53.1.13.el5 (rhel-x86_64-client-5)
   https://rhn.redhat.com/network/software/packages/details.pxt?pid=432805
   Unsupported modules:
     vmnet
     vmblock
     vmmon
   All modules appears genuine
   Kernel not up2date (should be kernel-2.6.18-92.el5-x86_64)