Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1244627

Summary:	Ctrl+Alt+End not working by default
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Tomas Jamrisko <tjamrisk>
Component:	mingw-virt-viewer	Assignee:	Default Assignee for SPICE Bugs <rh-spice-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	SPICE QE bug list <spice-qe-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	cfergeau, ecohen, gklein, lsurette, pgrunt, rbalakri, tjamrisk, yeylon
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-07-20 12:34:44 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:

Description Tomas Jamrisko 2015-07-20 07:44:23 UTC

Description of problem:

Ctrl+Alt+End does not work when connecting to a VM without overriding default shortcuts

Version-Release number of selected component (if applicable):
mingw-virt-viewer-2.0-32

How reproducible:
100%

Steps to Reproduce:
(client was Windows 8.1)
1. Run a VM without ssl and any other authentication
2. Connect to it simply by running remote-viewer spice://ip:port

Actual results:
Ctrl+Alt+End does not work despite it being written by Ctrl+alt+del in the shortcuts menu and ctrl+alt+del gets captured both by client and guest

Expected results:
Ctrl+alt+del should only be captured by client and ctrl+alt+end should send the c-a-d combination.

Comment 1 Pavel Grunt 2015-07-20 12:25:36 UTC

Win8.1 are probably using the 'ctrl+alt+end' combo for some system stuff. Just to be sure, can you confirm that another combo works ?
e.g.: remote-viewer spice://ip:port --hotkeys=secure-attention=ctrl+alt+8

Comment 2 Tomas Jamrisko 2015-07-20 12:34:44 UTC

You are right, it's conflict with default release (though it was fixed)...

*** This bug has been marked as a duplicate of bug 1018766 ***