Re: [Spice-devel] [vdagent-win] mingw: Don't define OLDMSCVRT for mingw builds

2012-11-19 Thread Arnon Gilboa
Christophe Fergeau wrote: On Mon, Nov 19, 2012 at 08:33:36AM -0500, Marc-André Lureau wrote: - Mensaje original - When it's defined, this causes some fallback code to be used. In particular, this causes log messages to not get timestamps. Issue reported by Han Pilmeyer.

[Spice-devel] [PATCH spice-gtk 2/2] channel: learn to load certificate from memory

2012-11-19 Thread Marc-André Lureau
Sadly, OpenSSL doesn't provide a way to load certificate from memory, but all the functions necessary to do so are actually public, so we can implement our own version and avoid files, how awesome! --- gtk/spice-channel.c | 69 ++--- 1 file changed,

[Spice-devel] [PATCH spice-gtk 1/2] Add SpiceSession:ca property

2012-11-19 Thread Marc-André Lureau
--- gtk/spice-session-priv.h | 2 ++ gtk/spice-session.c | 40 ++-- 2 files changed, 40 insertions(+), 2 deletions(-) diff --git a/gtk/spice-session-priv.h b/gtk/spice-session-priv.h index 13345b4..804658d 100644 --- a/gtk/spice-session-priv.h +++ b/gtk/s

Re: [Spice-devel] [vdagent-win] mingw: Don't define OLDMSCVRT for mingw builds

2012-11-19 Thread Christophe Fergeau
On Mon, Nov 19, 2012 at 08:33:36AM -0500, Marc-André Lureau wrote: > - Mensaje original - > > When it's defined, this causes some fallback code to be used. In > > particular, this causes log messages to not get timestamps. > > Issue reported by Han Pilmeyer. > > You can also try to impleme

Re: [Spice-devel] [vdagent-win] mingw: Don't define OLDMSCVRT for mingw builds

2012-11-19 Thread Marc-André Lureau
Hi - Mensaje original - > When it's defined, this causes some fallback code to be used. In > particular, this causes log messages to not get timestamps. > Issue reported by Han Pilmeyer. Iirc, this is on purpose if we don't want to have to ship our own new-enough msvcrt. The solution to

[Spice-devel] opengl accleration

2012-11-19 Thread mill . chen 陈军
Hi , If I want to enable opengl acceleration on client, whether do I need to enable opengl with spice server together? Thanks Best Regards, Mill Chen Silicon Motion,Inc(SH) Tel:86-21-65107780 ext:7161 ___ Spice-devel mailing list

[Spice-devel] [vdagent-win] mingw: Don't define OLDMSCVRT for mingw builds

2012-11-19 Thread Christophe Fergeau
When it's defined, this causes some fallback code to be used. In particular, this causes log messages to not get timestamps. Issue reported by Han Pilmeyer. --- Makefile.am | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile.am b/Makefile.am index 9b73def..d2717e2 100644 -

Re: [Spice-devel] Windows Guest Tools 0.2

2012-11-19 Thread Han Pilmeyer
On 19/11/2012 12:23, Christophe Fergeau wrote: I don't think "Unsupported clipboard format" is a fatal error. The only 2 components involved in cut&paste are vioserial and the agent. It might be worth trying to restart the agent when copy&paste stops working to see if that helps. I forgot to me

Re: [Spice-devel] [PATCH spice-gtk 1/3] win32: translate virtual-key code to scancode via MapVirtualKey

2012-11-19 Thread Christophe Fergeau
On Sun, Nov 18, 2012 at 01:39:22PM +0100, Marc-André Lureau wrote: > Hi > > This patch solves keyboard layout issues on Windows. It doesn't seem to > introduce regression. There is no better solution atm, I explained in > previous mail that the original problem could be rooted in Gtk-Win32 > back

Re: [Spice-devel] Windows Guest Tools 0.2

2012-11-19 Thread Christophe Fergeau
Hey, On Fri, Nov 16, 2012 at 09:51:39PM +0100, Han Pilmeyer wrote: > If have a long list of problems with KVM (running in an up to date > Fedora 17) with my Windows 7 guest. I've been holding off to report > them, until I'm relatively sure that I have the correct set of guest > drivers installed.

[Spice-devel] How should multiple monitors be handled by new qxl driver?

2012-11-19 Thread Tomas Jamrisko
(started here on Hans's suggestion because of https://bugzilla.redhat.com/show_bug.cgi?id=842298 ) Hi, I've been doing some testing on qxl driver 0.1.0-2 and noticed some inconsistencies in how those multiple monitors are treated: -- when first starting a VM, just one display is active, thr