[Kernel-packages] [Bug 1929790] Re: Request to backport fix for endianness issue in TigerVNC vncviewer
** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: linux (Ubuntu) => tigervnc (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1929790 Title: Request to backport fix for endianness issue in TigerVNC vncviewer Status in Ubuntu on IBM z Systems: New Status in tigervnc package in Ubuntu: New Bug description: ---Problem Description--- TigerVNC 1.11.0 contains a regression that causes vncviewer to display incorrect colors when vncviewer and X11 server use different endianness (e.g., when using X11 forwarding via SSH between an x86-64 desktop and a Linux system on s390x). The regression was originally reported in github issue https://github.com/TigerVNC/tigervnc/issues/1073 and fixed in github pull request https://github.com/TigerVNC/tigervnc/pull/1084 The regression caused vncviewer to always use the system byte order for pixel values instead of the byte order required by the X11 display. With the fix, vncviewer queries the X11 display for the required byte order. As of now, the fix has not made it into a release yet. Please consider backporting the fix (upstream commit 7ab92639848). I confirmed that this commit cleanly applies on top of release 1.11.0 and fixes the regression. ---uname output--- Linux s390x Machine Type = x15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- See also https://github.com/TigerVNC/tigervnc/issues/1252 - From a Linux x86 system, connect to a Linux system on s390x via SSH with X forwarding - Start a Xvnc session on that Linux system tigervncserver :0 -geometry 800x600 -depth 32 - Start vncviewer on the same Linux system xtigervncviewer :0 - On vncviewer's window on your origin X session, observe incorrect colors. - Optionally, start X11 programs such as xlogo, xclock, or xeyes to make the problem obvious - Optionally, connect to the vnc session directly (i.e., with a vnc client on the origin system) to compare Userspace tool common name: vncviewer The userspace tool has the following bit modes: 64-bit Userspace rpm: tigervnc-viewer Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929790] Re: Request to backport fix for endianness issue in TigerVNC vncviewer
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1929790 Title: Request to backport fix for endianness issue in TigerVNC vncviewer Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: ---Problem Description--- TigerVNC 1.11.0 contains a regression that causes vncviewer to display incorrect colors when vncviewer and X11 server use different endianness (e.g., when using X11 forwarding via SSH between an x86-64 desktop and a Linux system on s390x). The regression was originally reported in github issue https://github.com/TigerVNC/tigervnc/issues/1073 and fixed in github pull request https://github.com/TigerVNC/tigervnc/pull/1084 The regression caused vncviewer to always use the system byte order for pixel values instead of the byte order required by the X11 display. With the fix, vncviewer queries the X11 display for the required byte order. As of now, the fix has not made it into a release yet. Please consider backporting the fix (upstream commit 7ab92639848). I confirmed that this commit cleanly applies on top of release 1.11.0 and fixes the regression. ---uname output--- Linux s390x Machine Type = x15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- See also https://github.com/TigerVNC/tigervnc/issues/1252 - From a Linux x86 system, connect to a Linux system on s390x via SSH with X forwarding - Start a Xvnc session on that Linux system tigervncserver :0 -geometry 800x600 -depth 32 - Start vncviewer on the same Linux system xtigervncviewer :0 - On vncviewer's window on your origin X session, observe incorrect colors. - Optionally, start X11 programs such as xlogo, xclock, or xeyes to make the problem obvious - Optionally, connect to the vnc session directly (i.e., with a vnc client on the origin system) to compare Userspace tool common name: vncviewer The userspace tool has the following bit modes: 64-bit Userspace rpm: tigervnc-viewer Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
