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.

Description of problem:
When try to connect via VNC file, error occurs says 'The file ... was not recognized by any plugin' 

Version-Release number of selected component (if applicable):
vinagre-2.28.1-9.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. start VNC server for connect to
vncserver :your_vnc_port
2.Create file named file.vnc with content:
[Connection]
Host=your_vnc_host:your_vnc_port
UserName=test_username
Password=test_password
3.In nautilus open file with vinagre

Actual results:
Error occurs, file was not recognized by any of the plugins

Expected results:
Remoted VNC session is opened

Additional info:
calling command `vinagre your_vnc_host:your_vnc_port is working`

The handler method for the -F parameter is not working. It was fixed in the newest versions with the port to GtkApplication (modern API), but the handler for positional arguments works just fine.

That's why ~Open with Remote Viewer...~ works when the vinagre.desktop.in file is used, but it doesn't when the launcher is vinagre-file.desktop.in.

Instead of risking causing regressions by backporting the main instance class of the application to our modern API, we should rather work this around by using the positional argument handling method for the vinagre-file.desktop.in as well.

This is an one-liner workaround:
-Exec=vinagre -F %U
+Exec=vinagre %U

If this seems reasonable, I would like to have the proper ACKs so I could make a release with the patch.

The problem here is actually that format of the vnc file has changed between releases of Vinagre. Current Vinagre expects Connection, Username, Host, Port, Password, Options and Shared keys. The version of Vinagre from Red Hat Enterprise Linux 6 expects lowercase versions of these. Change the keys to lowercase and it will work for you.

Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.