Hi,
On Thu, Apr 27, 2017 at 04:16:31PM -0500, Jonathon Jongsma wrote:
> When transferring the same file multiple times, the vdagent tries to
> avoid overwriting an existing file on the guest by appending an integer
> to the filename. Instead of just appending the integer to the very end,
> we now
When transferring the same file multiple times, the vdagent tries to
avoid overwriting an existing file on the guest by appending an integer
to the filename. Instead of just appending the integer to the very end,
we now try to be smarter and append the integer before the file
extension. For example
Previously, if the user attempted to transfer a file that had the same
name as a file that already exists on the guest, we would just fail the
transfer. This patch tries to match the behavior of the linux vdagent
where we try to append an integer onto the name of the new file to make
it unique. For
Hi,
It can happen that the initial cursor is not set for some monitors
(SpiceDisplays)
in a multimonitor linux guest env (there is a single cursor channel). To fix
the problem a new class is created to handle gtk/gdk properties of the remote
cursor. There is a 1:1 relation between SpiceChannelCur
In a multimonitor environment can easily happen that a cursor is set
before some of the SpiceDisplays are created. IOW the first created
SpiceDisplay has the cursor but others don't.
To avoid the issue check for the cursor in SpiceChannelCursorGtk.
Resolves:
https://bugzilla.redhat.com/show_bug.c
Implement internal SpiceCursorChannelGtk class. Its purpose is to handle
the graphical (GTK/GDK) representation of the remote cursor.
The intention behind it is sharing of the cursor between multiple
SpiceDisplay widgets (case of a linux guest which has a single display
channel serving multiple mo
Hi Snir,
Does both xhci & usb3 device appear in windows device manager?
[image: Imágenes integradas 1]
As mentioned in the documentation usb3 is less tested, especially on windows
guests, i would suggest to use the EHCI controller set up, that should also
work with
your usb3 device (but it will
On Thu, 2017-04-27 at 10:25 -0500, Jonathon Jongsma wrote:
> On Wed, 2017-04-26 at 17:50 -0400, Frediano Ziglio wrote:
> > >
> > > Previously, if the user attempted to transfer a file that had
> > > the
> > > same
> > > name as a file that already exists on the guest, we would just
> > > fail
> >
On Wed, 2017-04-26 at 17:50 -0400, Frediano Ziglio wrote:
> >
> > Previously, if the user attempted to transfer a file that had the
> > same
> > name as a file that already exists on the guest, we would just fail
> > the
> > transfer. This patch tries to match the behavior of the linux
> > vdagent
On Wed, Apr 26, 2017 at 3:15 PM, Frediano Ziglio wrote:
> The warning is mainly there to notify the guest is sending commands for a
> not existing surface.
> This should not create issues unless the surface is used as source for
> other commands.
>
Practically, Win10 does not produce 'move' oper
10 matches
Mail list logo
