RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1908843 - Warning on the tmux console with VNC installs
Summary: Warning on the tmux console with VNC installs
Keywords:
Status: CLOSED DUPLICATE of bug 1886644
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: anaconda
Version: 8.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-17 17:48 UTC by Ken Green
Modified: 2020-12-18 10:46 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-18 10:46:37 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Ken Green 2020-12-17 17:48:08 UTC 
Description of problem:
When installing 8.3 using VNC for the graphical session you get 4 warnings in the TMUX based console when moving from the language selection screen to the main hub screen.


Starting installer, one moment...
anaconda 33.16.3.26-1.el8 for Red Hat Enterprise Linux 8.3 started.
 * installation log files are stored in /tmp during the installation
 * shell is available on TTY2
 * if the graphical installation interface fails to start, try again with the
   inst.text bootoption to start text installation
 * when reporting a bug add logs from /tmp as separate text/plain attachments
17:28:29 Starting VNC...
17:28:31 The VNC server is now running.
17:28:31

You chose to execute vnc with a password.


17:28:31 Please manually connect your vnc client to vm3.bl19.r214.example.com:1 (10.168.72.219:1) to begin the install.
17:28:31 Attempting to start vncconfig
Warning:          Could not resolve keysym XF86MonBrightnessCycle
Warning:          Could not resolve keysym XF86RotationLockToggle
Warning:          Could not resolve keysym XF86MonBrightnessCycle
Warning:          Could not resolve keysym XF86RotationLockToggle


[anaconda]1:main* 2:shell  3:log  4:storage-log >Switch tab: Alt+Tab | Help: F1


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

How reproducible:
Completely

Steps to Reproduce:
1. Kick off an installation, I've been using PXE
2. Add the boot options  console=ttyS0,115200 inst.vnc inst.vncpassword=install

3. Connection you VNC viewer to the install when requested.
4. Click the button to move from the language selection screen to the main install hub screen. 

You now get 4 lines of warnings

These are displayed on the console well before the new screen is shown in the VNC session.

Actual results:

Warning:          Could not resolve keysym XF86MonBrightnessCycle
Warning:          Could not resolve keysym XF86RotationLockToggle
Warning:          Could not resolve keysym XF86MonBrightnessCycle
Warning:          Could not resolve keysym XF86RotationLockToggle

Expected results:

None of these warnings. I've not seen this with 8.0, 8.1 or 8.2

Additional info:
The install all seems to work fine, you just get these irritating warnings.

The /tmp/vncserver.log file show

[anaconda root@vm3 tmp]# cat vncserver.log

Xvnc TigerVNC 1.10.0 - built Jul  8 2020 14:00:34
Copyright (C) 1999-2019 TigerVNC Team and many others (see README.rst)
See https://www.tigervnc.org for information on TigerVNC.
Underlying X server release 12008000, The X.Org Foundation


Thu Dec 17 17:28:29 2020
 vncext:      VNC extension running!
 vncext:      Listening for VNC connections on all interface(s), port 5901
 vncext:      created VNC server for screen 0
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Could not resolve keysym XF86MonBrightnessCycle
> Warning:          Could not resolve keysym XF86RotationLockToggle
Errors from xkbcomp are not fatal to the X server

Thu Dec 17 17:28:56 2020
 Connections: accepted: 10.153.41.136::49174
 SConnection: Client needs protocol version 3.8
 SConnection: Client requests security type VncAuth(2)

Thu Dec 17 17:28:59 2020
 VNCSConnST:  Server default pixel format depth 16 (16bpp) little-endian rgb565
 VNCSConnST:  Client pixel format depth 24 (32bpp) little-endian rgb888
[anaconda root@vm3 tmp]#
Comment 1 Jan Stodola 2020-12-18 10:46:37 UTC 
The warnings will be fixed in RHEL-8.4, see bug 1886644.
Closing as a duplicate.

*** This bug has been marked as a duplicate of bug 1886644 ***
Note You need to log in before you can comment on or make changes to this bug.