[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#654924: Fwd: Re: TigerVNC 1.0.90 src debs



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 21.02.2012 23:00, schrieb Mike Gabriel:
> Hi Joachim,
> 
> On Di 21 Feb 2012 22:50:21 CET Joachim Falk wrote:
> 
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hey Mike,
>>
>> fyi, regarding your ITP for tigervnc. I don't think that Antoine has
>> done anything in this regard. But you might ask or use my package as
>> basis for yours. I have already applied some fixes from redhat ontop
>> of the original tigervnc sources. The stuff is all versioned via git
>> so you can tell what changes I have applied.
>>
>> Regards,
>> Joachim
> 
> I see you do not rely on libjpeg-turbo. I actually am waiting for
> libjpeg-turbo (fabo@debian.org is packaging them) to enter Debian sid.
> 
> Maybe I should build the package without. Hmmm...
Well. I packaged the stuff for squeeze. My version is not able
to do real time transmission on a 1900x1200 display. I don't know
if libjpeg-turbo will be able to. However, at least with the version
I have built it is again possible to execute a kde session under Xvnc.

P.S.: I update the version on xiao with the latest packages I built myself.

tigervnc (1.1.0-2jf) stable; urgency=low

  * Added RH patch tigervnc11-ldnow.patch disabling lazy symbol
resolution for libvnc.so

  * Added RH patch tigervnc11-rh690245.patch which add TLS encryption to
VeNCrypt

      TigerVNC (Xvnc, x0vncserver, the libvnc.so module, and vncviewer) now
      supports TLS encryption (using VeNCrypt) which allows TLS encrypted
      communication between a server and a viewer. (BZ#653491)

  * Added RH patch tigervnc11-rh588342.patch which fixes EQ overflowing bug.

      Xvnc could become unresponsive and the following error message was
shown
      in the log: "[mi] EQ overflowing. The server is probably stuck in an
      infinite loop.". This was caused by a large number of user input
events
      in the Xvnc event queue, which were being processed too slowly. With
      this update, this issue no longer occurs and the system works as
      expected. (BZ#588342)

  * Add RH patch tigervnc11-rh628054-xorg.patch which fixes vmware
keyboard interaction bug.

      Prior to this update, Xvnc (the X VNC server; part of the tigervnc
      package) did not pass keyboard input to a remote VMware workstation
      because it did not take into account types of keyboards which do not
      have modifier keys. With this update, Xvnc recognizes all types of
      keyboards; thus, keyboard input is correctly passed to remote VMware
      workstations. (BZ#628054)

  * Add RH patch tigervnc11-rh645755.patch fix signal interrupted read

      The Xvnc server randomly refused connections when the reading of the
      password file (provided when starting Xvnc with the "-PasswordFile"
      option) was interrupted by a signal. With this update, the loading
of a
      password file continues after an interrupt signal is issued and
      connections are no longer refused. (BZ#645755)

  * Apply RH patch tigervnc-viewer-reparent.patch which adds vncviewer
embedding support via -Parent option.

  * Apply RH patch tigervnc-102434.patch which adds -passwdInput option
to vncviewer.

 -- Joachim Falk <joachim.falk@gmx.de>  Thu, 13 Oct 2011 20:12:48 +0200

> 
> Thanks+Greets,
> Mike

Regards,
Joachim
- -- 
Joachim Falk <Joachim.Falk@gmx.de>

You can always tell a really good idea by the enemies it makes.
  --programmers' axiom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJPRBW9AAoJEIjUIAk+3OYM5TwP/Am46x4gWrVGyoV8jx2KOvEX
Oz8P8d1np3+WEoPM8/HDA+wgSLdeIjBj9hgGNLbdWIW1u4XtlX9rqe6vVsdH2sF3
Ku7sjSIIvzU8Y9vzRTGboQnscagpjBZt1h1Mm++2j/eSWBnal/Y6bjvieekrTYQb
laIm4pVi93rwbE5oYI/aMF5rdAdvoK/ShnAIz2sLUea/2E12TtKLSa2IvVVkU6gM
Qi7gLhdhy1uOzTKDnQAGlk0usQ8BDLIiDI3/MZa3zldqLaiiwawrTo4E3AOc5jg5
73/c65LvGa+g6Cis6qSQwWUB+ErXapx6ZN/4cCaA3a8J788vTNYBBKtHx2c5cRBO
vLEslcwz+LlrVGgZyJAB4SyQyQHQneFSJRXa0xxUAxJYxb0VQ+iSsZ8Uc7kEkOA1
PvXtGrH5UxOPvCMjXO+5wsr60i3eHJ9d709P9s2LUjd4QRzVT8hBlCcl6JS9z9LY
u82/GzeQPXwMmwD2GT9ShfT7lpd8BAo/8YdcOrq6dxp7oV7v9FKxKfR+1WVzmnK4
QNLJVTSccYPA9W2fmMfOWZtayDz0Uw9msCy84dOpxwWPJp6KJKW4qdRbY5n6bHd2
fUF+UctL7SfF/V65lkobvj7zWQSe1qR4XTxWzThX8x5ZoV6Ui/yCteR24VttUiX6
UXtFmAskx1O9l71x2xcM
=hMAj
-----END PGP SIGNATURE-----



Reply to: