>
> They became unused more than 5 years ago in commit f84dfe
> ---
> server/red-channel.h | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/server/red-channel.h b/server/red-channel.h
> index f2866f5..4430d0b 100644
> --- a/server/red-channel.h
> +++ b/server/red-channel.h
> @@ -112,8 +
They became unused more than 5 years ago in commit f84dfe
---
server/red-channel.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/server/red-channel.h b/server/red-channel.h
index f2866f5..4430d0b 100644
--- a/server/red-channel.h
+++ b/server/red-channel.h
@@ -112,8 +112,6 @@ typedef void
Remove handling with failures in the SASL authentication
process to separate function and display the error message
as reported by the SASL client (could also display SASL
server error message if error number was sent to the client)
---
src/spice-channel.c | 42 +---
Changing the name of the function that now handles failures
in the spice authentication process separately from the sasl
authentication failures and display more suitable error message.
Resolves: rhbz#1365736
---
src/spice-channel.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
These patches splits the handling of failed authentication into 2
separate patches: one for sasl authentication failure and the
other one for spice authentication failure.
The idea behind these is to:
1. make (small) improvement in error messages content
2. fix rhbz#1399077
3. preparation for disp
>
> >
> > On Fri, Feb 10, 2017 at 08:27:27AM -0500, Frediano Ziglio wrote:
> > > >
> > > > On Wed, Feb 08, 2017 at 12:10:52PM -0600, Jonathon Jongsma wrote:
> > > > > On Tue, 2017-02-07 at 11:59 +0100, Christophe Fergeau wrote:
> > > > > > It was probably meant to be used as a "user_data" argume
>
> On Fri, Feb 10, 2017 at 11:17:44AM -0500, Frediano Ziglio wrote:
> > >
> > > On Fri, Feb 10, 2017 at 10:36:10AM -0500, Frediano Ziglio wrote:
> > > > So are you saying you prefer an heavy unsafe signal instead of a
> > > > function call just for statistics that's disabled by default?
> > >
>
Binary EDID block is generated by 3rd party app and converted to the text
as is.
As soon as it is accepted by OS, we think it is valid.
I'll provide some decoding info after we finish the first round of
discussion.
Of couse it is also possible to present alpha chars as characters, if this
is really
>
> >
> > On Wed, Feb 08, 2017 at 12:54:44PM -0600, Jonathon Jongsma wrote:
> > > On Tue, 2017-02-07 at 11:59 +0100, Christophe Fergeau wrote:
> > > > Similarly to the previous commits, this removes an indirection level,
> > > > IncomingHandlerInterface stores pointers to
> > > > alloc_recv_buf/r
>
>
> > On 12 Feb 2017, at 14:09, Yuri Benditovich
> > wrote:
> >
> > Solves failure of HLK "Test for EDID requirements"
> > EDID contains capabilities and manufacturer data of
> > the emulated display device. Main parameters are:
> > Manufacturer code: QXL
> > Product ID: 0001
> > Working freq
> On 12 Feb 2017, at 14:09, Yuri Benditovich
> wrote:
>
> Solves failure of HLK "Test for EDID requirements"
> EDID contains capabilities and manufacturer data of
> the emulated display device. Main parameters are:
> Manufacturer code: QXL
> Product ID: 0001
> Working frequency: 75 Hz
>
> Sign
Most channel don't need to do specific settings for the
client socket so provide a default implementation to
make easier to setup the client channnel.
Signed-off-by: Frediano Ziglio
---
server/inputs-channel.c | 6 --
server/main-channel.c | 6 --
server/red-channel-client.c |
Avoid possible dandling pointers.
Signed-off-by: Frediano Ziglio
---
server/red-channel-client.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/server/red-channel-client.c b/server/red-channel-client.c
index 06fb8a8..2450923 100644
--- a/server/red-channel-client.c
+++ b/server/red-channe
TCP_NODELAY flag is set by default for all connection inside
reds.c so there's no need to set again for the single
client channel.
Note that there are still some call to setsockopt to set this
option but in this case the flag can reset the flag.
Signed-off-by: Frediano Ziglio
---
server/inputs-
Non blocking flag is set for all connection inside reds.c so
there's no need to set again for the single client channel.
Signed-off-by: Frediano Ziglio
---
server/common-graphics-channel.c | 11 ---
server/sound.c | 11 ---
2 files changed, 22 deletions(-)
diff
On Mon, Feb 13, 2017 at 11:50 AM, Frediano Ziglio
wrote:
> >
> > With default period of VSync interrupt notification
> > (1sec/refresh rate) the driver with device rev.4
> > has a problem when the system starts running after
> > restart. Until the issue is solved we set the notification
> > perio
>
> On Wed, Feb 08, 2017 at 12:54:44PM -0600, Jonathon Jongsma wrote:
> > On Tue, 2017-02-07 at 11:59 +0100, Christophe Fergeau wrote:
> > > Similarly to the previous commits, this removes an indirection level,
> > > IncomingHandlerInterface stores pointers to
> > > alloc_recv_buf/release_recv_buf
On Fri, Feb 10, 2017 at 11:17:44AM -0500, Frediano Ziglio wrote:
> >
> > On Fri, Feb 10, 2017 at 10:36:10AM -0500, Frediano Ziglio wrote:
> > > So are you saying you prefer an heavy unsafe signal instead of a
> > > function call just for statistics that's disabled by default?
> >
> > My desktop i
>
> On 02/10/2017 01:40 PM, Bernice Levin wrote:
> > Hi Guys (Dolls)
> >
> >
> >
> > Please I need your help. I have installed KVM Hypervisor on OpenSUSE, I
> > have everything working – installed VMs and have accessed them on
> > localhost through Virt-viewer but cannot get access on the network
>
> On Fri, 2017-02-10 at 06:57 -0500, Frediano Ziglio wrote:
> > >
> > > Change current_add_drawable() to display_channel_add_drawable() and
> > > current_remove_drawable() to display_channel_remove_drawable().
> > > ---
> > > server/display-channel.c | 28 ++--
> > > 1
>
> With default period of VSync interrupt notification
> (1sec/refresh rate) the driver with device rev.4
> has a problem when the system starts running after
> restart. Until the issue is solved we set the notification
> period to 200 ms, with this value both rev.3 and rev.4
> function correctly
Depending on the order of tests, this also can cause some tests to fail, if
they verify (explicitly or implicitly) presence of 1024x768.
On Mon, Feb 13, 2017 at 11:17 AM, Frediano Ziglio
wrote:
> >
> > When the video mode is changed and then the driver disabled and
> > enabled, it did not enume
>
> When the video mode is changed and then the driver disabled and
> enabled, it did not enumerate available video modes with lower
> resolution than current one. All modes starting from 1024x768
> should be available regardless what is current resolution
> on driver startup
>
> Signed-off-by: Y
>
> Concentrate filling of signal info in single procedure.
> Fill signal info with specific or default frequency data
> according to the global flag of VSync support.
> Note that the state of this flobal flag must be defined only
> on driver startup and it can't be changed later.
>
I would add
>
> Solves failure of HLK "Test for EDID requirements"
> EDID contains capabilities and manufacturer data of
> the emulated display device. Main parameters are:
> Manufacturer code: QXL
> Product ID: 0001
> Working frequency: 75 Hz
>
> Signed-off-by: Yuri Benditovich
> ---
> qxldod/QxlDod.cpp |
Hi,
I managed to solve the issue by adding the -X flag to the arguments
passed to spice-vdagentd.
After some reading up on systemd and perusing some source code I
narrowed the problem down to systemd-logind, specifically which
session it reports as the active session.
Xspice successfully launches
26 matches
Mail list logo
