Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1491608

Summary: Annoying "Press F8..." message
Product: Red Hat Enterprise Linux 7 Reporter: Jiri Benc <jbenc>
Component: tigervncAssignee: Jan Grulich <jgrulich>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.4CC: ferdnyc, mboisver, tpelka
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1708221 (view as bug list) Environment:
Last Closed: 2019-08-06 12:43:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1708221    
Attachments:
Description Flags
screenshot
none
Patch to add -NoReminder option to vncviewer command none

Description Jiri Benc 2017-09-14 09:15:16 UTC
Created attachment 1325849 [details]
screenshot

After the recent update of tigervnc, there's a message "Press F8 to open the context menu" covering exactly the grub menu (when used to connect to qemu-kvm) and disappearing after the menu timeout. This is highly annoying and slows down work when doing kernel development and working with many VMs and different kernels.

The message was not there before. There's no mention in the man page how it can be switched off. I consider this changed behavior a regression as it hinders day to day usage.

tigervnc-1.8.0-1.el7.x86_64

Comment 3 "FeRD" (Frank Dana) 2018-07-24 11:00:04 UTC
Created attachment 1470253 [details]
Patch to add -NoReminder option to vncviewer command

I brought this up with the tigervnc developers upstream. See https://github.com/TigerVNC/tigervnc/issues/678


They opted not to go with a method of completely disabling the reminder message, however for the 1.9.0 release they did make the message *significantly* smaller (in line with Firefox or Chrome's fullscreen-exit messages), so it's less in the way.

(However, if anyone would like to be able to completely turn off that message by passing a -NoReminder flag on the vncviewer command line, my rejected patches against tigervnc-1.9.0 are attached.)

Comment 15 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.

https://access.redhat.com/errata/RHBA-2019:2081