Bug 1179070

Summary:	[RFE] Option to pin spice-gtk console windows to specific monitors
Product:	Red Hat Enterprise Linux 8	Reporter:	Anand Nande <anande>
Component:	mingw-virt-viewer	Assignee:	Julien Ropé <jrope>
Status:	CLOSED ERRATA	QA Contact:	SPICE QE bug list <spice-qe-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0	CC:	cfergeau, dblechte, djasa, fgiudici, jjongsma, jrope, lpeer, lsurette, michal.skrivanek, mtessun, nashok, srevivo, tpelka, uril, victortoso
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	---	Flags:	knoel: mirror+
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	mingw-virt-viewer-9.0-1.el8	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-04 04:02:54 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Spice	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Anand Nande 2015-01-06 06:40:23 UTC

The spice-gtk-windows always open on top of each other in the same monitor.

So, the window positions are not remembered by remote-viewer.

It would be great if this could be fixed - then it would also be possible to
open both screens in full screen mode on the monitors.

When launching the console through the portal in full screen the two console windows appear on top of each other. Is there a way to make them open up in separate displays?

 Instead of always having to:
 1) Leave Full Screen
 2) Move the 2nd console window to the other display an 
 3) Go back to Full Screen Mode

This can be observed using Firefox and Native SPICE client/mode to lauch the console session of the VM (windows/linux).

Comment 1 Michal Skrivanek 2015-01-07 08:23:35 UTC

this is a remote-viewer feature. David?
Might be also possible to do something specific using an advanced window manager features

Comment 2 Christophe Fergeau 2015-01-16 10:04:48 UTC

Imo, the crux of this RFC/bug is this:
"When launching the console through the portal in full screen the two console windows appear on top of each other.", which is a remote-viewer bug, not an RFC.

Then comes one way of workarounding this bug worded as an RFC asking for an 'option to pin spice-gtk...'.

Are there more use cases for this pinning, or does the customer only wants its fullscreen windows to open on separate screens?

Comment 3 Anand Nande 2015-04-15 16:53:12 UTC

(In reply to Christophe Fergeau from comment #2)
> Imo, the crux of this RFC/bug is this:
> "When launching the console through the portal in full screen the two
> console windows appear on top of each other.", which is a remote-viewer bug,
> not an RFC.
> 
> Then comes one way of workarounding this bug worded as an RFC asking for an
> 'option to pin spice-gtk...'.

The window should remember its positions since they were last closed.

> 
> Are there more use cases for this pinning, or does the customer only wants
> its fullscreen windows to open on separate screens?

Fullscreen/resized however the windows were last opened - the window positions should be remembered by remote-viewer upon opening the VM-console next time.

Comment 4 David Blechter 2015-04-16 11:46:47 UTC

(In reply to Anand Nande from comment #3)
> (In reply to Christophe Fergeau from comment #2)
> > Imo, the crux of this RFC/bug is this:
> > "When launching the console through the portal in full screen the two
> > console windows appear on top of each other.", which is a remote-viewer bug,
> > not an RFC.
> > 
> > Then comes one way of workarounding this bug worded as an RFC asking for an
> > 'option to pin spice-gtk...'.
> 
> The window should remember its positions since they were last closed.
> 
> > 
> > Are there more use cases for this pinning, or does the customer only wants
> > its fullscreen windows to open on separate screens?
> 
> Fullscreen/resized however the windows were last opened - the window
> positions should be remembered by remote-viewer upon opening the VM-console
> next time.

Hi,

Based on the latest comments, it is definitely RFE and should go through the triage process with PM. We have the dedicated component "RFEs" for this.
thanks, David

Comment 8 Jonathon Jongsma 2017-08-16 15:35:31 UTC

Quite a while ago we added a feature that allows a user to configure which monitors should be used when opening a guest in fullscreen mode. This was introduced in virt-viewer/remote-viewer 0.6.0, and rhevm 3.6 (see bug 957593). Does this solve your problems? You can find some basic documentation for the feature in the man page ("man remote-viewer").

Comment 10 Sandro Bonazzola 2019-01-28 09:41:24 UTC

This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Comment 12 Sandro Bonazzola 2019-03-26 10:11:25 UTC

4.3.1 has been released a while ago as RHV 4.3 Beta2.
Re-targeting to 4.3.3 for re-evaluation.

Comment 14 Julien Ropé 2020-02-10 15:37:48 UTC

I have added some code that will save the monitor mapping into the settings file when the windows are fullscreen, using the existing "monitor-mapping" option.
When the application is launched again in fullscreen, the position is then reused.

I've tried to see if we could save window positions (when not fullscreen), but it is actually discouraged in GTK documentation: applications should not try to set their own window position, as they usually don't have enough context to put them correctly.

Comment 31 errata-xmlrpc 2020-11-04 04:02:54 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 (spice-client-win bug fix and enhancement update), 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/RHEA-2020:4808