Bug 1618777 - blue tinted vncviewer popup on ppc64
Summary: blue tinted vncviewer popup on ppc64
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: tigervnc
Version: 7.6
Hardware: ppc64
OS: Linux
Target Milestone: rc
: ---
Assignee: Jan Grulich
QA Contact: Desktop QE
Depends On:
Blocks: 1649362
TreeView+ depends on / blocked
Reported: 2018-08-17 14:54 UTC by Tomas Hudziec
Modified: 2019-08-06 12:43 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-08-06 12:43:05 UTC
Target Upstream Version:

Attachments (Terms of Use)
screenshot (212.58 KB, image/png)
2018-08-17 14:54 UTC, Tomas Hudziec
no flags Details

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2081 0 None None None 2019-08-06 12:43:10 UTC

Description Tomas Hudziec 2018-08-17 14:54:18 UTC
Created attachment 1476639 [details]

Description of problem:
Background of popup message (Press F8 to open the context menu) of vncviewer that is shown after startup is blue tinted on ppc64.

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

How reproducible:

Steps to Reproduce:
1. $ vncserver :1
2. $ vncviewer :1

Actual results:
blue tinted popup message shows up for ~ 3 seconds

Expected results:
popup message should have gray background with white text

Additional info:
Problem originally mentioned in this upstream issue:
It remains after fixing bug 1613264.

Comment 2 Jan Grulich 2018-08-17 14:58:02 UTC
I know about that one and unfortunately didn't have time to look into it, but I don't consider it as a blocker and it's not also a regression from RHEL 7.5.

Comment 6 Tomas Hudziec 2019-02-19 15:01:44 UTC
With tigervnc-1.8.0-14.el7, popup message is not blue tinted, it has correct look - gray background with white text.

Comment 8 errata-xmlrpc 2019-08-06 12:43:05 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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