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 1684729 - gnome-remote-desktop prompts for password after set to ask for permission
Summary: gnome-remote-desktop prompts for password after set to ask for permission
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gnome-remote-desktop
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Jonas Ådahl
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On: 1681618
Blocks: 1739559 1866016
TreeView+ depends on / blocked
 
Reported: 2019-03-01 23:44 UTC by Porygon
Modified: 2022-05-06 00:38 UTC (History)
4 users (show)

Fixed In Version: gnome-remote-desktop-0.1.6-8.el8 libvncserver-0.9.11-13.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1866016 (view as bug list)
Environment:
Last Closed: 2020-04-28 16:09:06 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-30227 0 None None None 2022-05-06 00:38:13 UTC
Red Hat Product Errata RHSA-2020:1766 0 None None None 2020-04-28 16:09:28 UTC

Description Porygon 2019-03-01 23:44:29 UTC
Description of problem:
Connecting to a remote desktop with the host set to ask for permission after previously connecting with it set to ask for a password makes it unable to connect.

Version-Release number of selected component (if applicable):
gnome-remote-desktop-0.1.6-3.el8.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Set host machine desktop sharing to use password authentication
2. Set host machine desktop sharing ON
3. Connect to host machine from client machine via vinagre (authenticate with ssh tunnel if required, then VNC password)
4. Disconnect the VNC client on client machine.
5. Set host machine desktop sharing authentication to "ask for permission"
6. Connect to host machine from client machine via vinagre (authenticate with ssh tunnel if required)
7. On host machine, click "allow" on notification pop-up

Actual results:
Client machine displays password prompt after host machine hits "allow" and password authentication always fails even if it matches old password.

Expected results:
Client machine successfully connects to host machine and displays remote desktop output

Additional info:
RHEL-8.0.0-20190228.1 (RC-1.0)
kernel-4.18.0-74.el8.x86_64

Comment 2 Jonas Ådahl 2019-11-27 13:44:49 UTC
Can't reproduce the issue in 8.2 using multi head QXL, so closing as WORKSFORME.

Comment 3 Jonas Ådahl 2019-11-27 13:48:17 UTC
Closing the wrong bug, reopening.

Comment 9 errata-xmlrpc 2020-04-28 16:09:06 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/RHSA-2020:1766


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