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 1255313 - Vinagre Choose file dialog does not list SPICE files
Summary: Vinagre Choose file dialog does not list SPICE files
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: vinagre
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Marek Kašík
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-20 09:20 UTC by Vaclav Ehrlich
Modified: 2015-09-15 09:24 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-03 15:57:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Vaclav Ehrlich 2015-08-20 09:20:57 UTC 
Description of problem:
Vinagre 'Choose the file' dialog filter files with wrong extension as SPICE files.
Instead *.vv  shows *.spice files

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

How reproducible:
Always

Steps to Reproduce:
1. Create files test_good.vv and test_bad.spice files in your home dir
2. Open Vinagre
3. Click on Remote->Open
4. Filter out Spice files in select box

Actual results:
Only test_bad.spice file is shown

Expected results:
Only test_good.vv file is shown

Additional info:
Comment 2 Matthias Clasen 2015-08-20 17:28:11 UTC 
I don't reproduce this here.

First of all, the extension for vnc files, is .vnc, according to /usr/share/mime/application/x-vnc.xml.

Now, if I have test.vnc and test.spice in my home directory, exactly one of them shows up in the vinagre file chooser, depending on what is selected in the filter combo, which seems exactly right:

if I select "Spice", test.spice shows up
if I select "VNC", test.vnc shows up

Can you clarify what you are seeing ?
Comment 3 Marek Kašík 2015-09-03 15:57:44 UTC 
*.spice files also exists and are used by Vinagre. The *.vv files are specific to the Virtual Machine Viewer (virt-viewer) and vinagre doesn't support all its features. So this report is wrong.

I'm closing this as notabug.
Comment 4 Vaclav Ehrlich 2015-09-15 09:24:54 UTC 
(In reply to Matthias Clasen from comment #2)
> I don't reproduce this here.
> 
> First of all, the extension for vnc files, is .vnc, according to
> /usr/share/mime/application/x-vnc.xml.
> 
> Now, if I have test.vnc and test.spice in my home directory, exactly one of
> them shows up in the vinagre file chooser, depending on what is selected in
> the filter combo, which seems exactly right:
> 
> if I select "Spice", test.spice shows up
> if I select "VNC", test.vnc shows up
> 
> Can you clarify what you are seeing ?

As Marek mentioned, I was testing it with *.vv files which we use in Remote viewer for spice connection.
I thought this file format is widely used, so I expected it in Vinagre too. If *.spice is the right way for Vinagre, this is really not a bug.
Note You need to log in before you can comment on or make changes to this bug.