Hi,
I'm facing severe below issues when connecting Windows guests from Linux
clients with Full-screen+Auto-Config only
1.) Keyboard/mouse lock issue happens when session is connected from
guest’s shutdown/restart state.
2.) Black screen appears when session is reconnected from gue
On Thu, Dec 22, 2011 at 09:44:59AM -0500, Marc-André Lureau wrote:
> Outputting files in srcdir goes against the idea of out of tree build.
I know, I wish I could put them in build dir but that would break with
tarballs.
> Since .c are dist'ed, they should be in the srcdir, so in the end I think
Hi
- Mensaje original -
> The --basedir argument to valac seems to be meant to help handling
> this case but it doesn't seem to work with f16 valac so I appended
> $(srcdir) to the vala source files.
> Build is still broken with --enable-vala during .vapi generation
> due to what look like
ack
- Mensaje original -
> spicec does this for all channels, and it seems like a good idea to
> do the
> same in spice-gtk.
>
> Signed-off-by: Hans de Goede
> ---
> gtk/spice-channel.c | 11 +--
> 1 files changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/gtk/spice-ch
The --basedir argument to valac seems to be meant to help handling
this case but it doesn't seem to work with f16 valac so I appended
$(srcdir) to the vala source files.
Build is still broken with --enable-vala during .vapi generation
due to what look like a vala bug.
---
gtk/controller/Makefile.a
On Thu, Dec 22, 2011 at 6:53 PM, Alon Levy wrote:
> On Thu, Dec 22, 2011 at 10:00:18AM +, Alon Levy wrote:
>> On Thu, Dec 22, 2011 at 05:42:29PM +0800, ZhouPeng wrote:
>> > On Thu, Dec 22, 2011 at 4:42 PM, Alon Levy wrote:
>> > > On Thu, Dec 22, 2011 at 10:13:50AM +0800, ZhouPeng wrote:
>> >
On 12/22/2011 01:14 PM, Hans de Goede wrote:
We want as little latency as possible with usb channels.
Signed-off-by: Hans de goede
---
server/spicevmc.c | 16
1 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/server/spicevmc.c b/server/spicevmc.c
index b1a7d8d
spicec does this for all channels, and it seems like a good idea to do the
same in spice-gtk.
Signed-off-by: Hans de Goede
---
gtk/spice-channel.c | 11 +--
1 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/gtk/spice-channel.c b/gtk/spice-channel.c
index 84d4dfd..079028a 1
We want as little latency as possible with usb channels.
Signed-off-by: Hans de goede
---
server/spicevmc.c | 16
1 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/server/spicevmc.c b/server/spicevmc.c
index b1a7d8d..70cfe0e 100644
--- a/server/spicevmc.c
+++ b/s
On Thu, Dec 22, 2011 at 6:00 PM, Alon Levy wrote:
> On Thu, Dec 22, 2011 at 05:42:29PM +0800, ZhouPeng wrote:
>> On Thu, Dec 22, 2011 at 4:42 PM, Alon Levy wrote:
>> > On Thu, Dec 22, 2011 at 10:13:50AM +0800, ZhouPeng wrote:
>> >> Hi,
>> >>
>> >> I meet the err:
>> >>
>> >> # virsh dumpxml 63
>>
On Thu, Dec 22, 2011 at 10:00:18AM +, Alon Levy wrote:
> On Thu, Dec 22, 2011 at 05:42:29PM +0800, ZhouPeng wrote:
> > On Thu, Dec 22, 2011 at 4:42 PM, Alon Levy wrote:
> > > On Thu, Dec 22, 2011 at 10:13:50AM +0800, ZhouPeng wrote:
> > >> Hi,
> > >>
> > >> I meet the err:
> > >>
> > >> # virs
On Thu, Dec 22, 2011 at 10:43:09AM +, Alon Levy wrote:
> On Thu, Dec 22, 2011 at 12:36:04PM +0200, Yonit Halperin wrote:
> > The display channel was unnecessarily set to NULL when we disconnect all
> > the clients
> > (on flush display commands timeout).
> > As a result, we recreated the displ
On Thu, Dec 22, 2011 at 12:36:04PM +0200, Yonit Halperin wrote:
> The display channel was unnecessarily set to NULL when we disconnect all the
> clients
> (on flush display commands timeout).
> As a result, we recreated the display channel when a new client was connected.
> The display channel was
The display channel was unnecessarily set to NULL when we disconnect all the
clients
(on flush display commands timeout).
As a result, we recreated the display channel when a new client was connected.
The display channel was created with default red_channel.client_cbs, while its
correct client_cbs
On Thu, Dec 22, 2011 at 05:42:29PM +0800, ZhouPeng wrote:
> On Thu, Dec 22, 2011 at 4:42 PM, Alon Levy wrote:
> > On Thu, Dec 22, 2011 at 10:13:50AM +0800, ZhouPeng wrote:
> >> Hi,
> >>
> >> I meet the err:
> >>
> >> # virsh dumpxml 63
> >> error: internal error cannot parse json {"timestamp": {"s
On 12/22/2011 11:26 AM, Christophe Fergeau wrote:
> On Thu, Dec 22, 2011 at 11:23:48AM +0200, Uri Lublin wrote:
>> On 12/22/2011 11:11 AM, Christophe Fergeau wrote:
>>> What do you mean exactly by "fix"? Just that it's better to put field
>>> initialization in the order it will actually happen? Or
On Thu, Dec 22, 2011 at 4:42 PM, Alon Levy wrote:
> On Thu, Dec 22, 2011 at 10:13:50AM +0800, ZhouPeng wrote:
>> Hi,
>>
>> I meet the err:
>>
>> # virsh dumpxml 63
>> error: internal error cannot parse json {"timestamp": {"seconds":
>> 1323332828, "microseco{"timest35p":39}, "econds":PICE_D 1CO323
ACK
On Thu, Dec 22, 2011 at 11:20:52AM +0200, Uri Lublin wrote:
> sed -i 's/_forec_update_timer/_force_update_timer/' screen.cpp screen.h
> ---
> client/screen.cpp | 10 +-
> client/screen.h |2 +-
> 2 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/client/screen.c
On Thu, Dec 22, 2011 at 11:23:48AM +0200, Uri Lublin wrote:
> On 12/22/2011 11:11 AM, Christophe Fergeau wrote:
> > What do you mean exactly by "fix"? Just that it's better to put field
> > initialization in the order it will actually happen? Or something else?
> The compiler warns about it.
> When
On Thu, Dec 22, 2011 at 11:20:52AM +0200, Uri Lublin wrote:
> sed -i 's/_forec_update_timer/_force_update_timer/' screen.cpp screen.h
ACK
> ---
> client/screen.cpp | 10 +-
> client/screen.h |2 +-
> 2 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/client/screen.
On Thu, Dec 22, 2011 at 11:23:48AM +0200, Uri Lublin wrote:
> On 12/22/2011 11:11 AM, Christophe Fergeau wrote:
> > What do you mean exactly by "fix"? Just that it's better to put field
> > initialization in the order it will actually happen? Or something else?
> The compiler warns about it.
> When
On 12/22/2011 11:11 AM, Christophe Fergeau wrote:
> What do you mean exactly by "fix"? Just that it's better to put field
> initialization in the order it will actually happen? Or something else?
The compiler warns about it.
When the compiler is requested to handle warnings as error (and we do),
bu
sed -i 's/_forec_update_timer/_force_update_timer/' screen.cpp screen.h
---
client/screen.cpp | 10 +-
client/screen.h |2 +-
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/client/screen.cpp b/client/screen.cpp
index a0dc0df..dc33455 100644
--- a/client/screen.cpp
+
What do you mean exactly by "fix"? Just that it's better to put field
initialization in the order it will actually happen? Or something else?
On Thu, Dec 22, 2011 at 10:54:57AM +0200, Uri Lublin wrote:
> Related to a91b0b3ff712eb2a7d91a951f2af7842495357c3
> ---
> client/screen.cpp |2 +-
> 1
On Thu, Dec 22, 2011 at 10:54:57AM +0200, Uri Lublin wrote:
> Related to a91b0b3ff712eb2a7d91a951f2af7842495357c3
ACK.
> ---
> client/screen.cpp |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/client/screen.cpp b/client/screen.cpp
> index 0b3ba6f..a0dc0df 100644
>
Related to a91b0b3ff712eb2a7d91a951f2af7842495357c3
---
client/screen.cpp |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/client/screen.cpp b/client/screen.cpp
index 0b3ba6f..a0dc0df 100644
--- a/client/screen.cpp
+++ b/client/screen.cpp
@@ -87,6 +87,7 @@ RedScreen::RedSc
On Thu, Dec 22, 2011 at 10:13:50AM +0800, ZhouPeng wrote:
> Hi,
>
> I meet the err:
>
> # virsh dumpxml 63
> error: internal error cannot parse json {"timestamp": {"seconds":
> 1323332828, "microseco{"timest35p":39}, "econds":PICE_D 1CO3233TE828,
> Dmicrosec "ds"data"52}, : {"ser: "SPrCE_DIS"ONNE
27 matches
Mail list logo
