Hi Mark
If you can convince the release team that it is necessary I will not stand
back. :-)
Regards
// Ola
On Sun, Jan 24, 2016 at 8:57 PM, Mark Cave-Ayland <
mark.cave-ayl...@ilande.co.uk> wrote:
> On 24/01/16 19:10, Ola Lundqvist wrote:
>
> > tag 782620 + patch
> > thanks
> >
> > Hi Mark
>
On 24/01/16 19:10, Ola Lundqvist wrote:
> tag 782620 + patch
> thanks
>
> Hi Mark
>
> Thanks for the report.
> I can not, as a maintainer, judge that. It has to be decided by the
> release team. However I do not think it will be accepted. It is
> essentially just security problems that are fixed
tag 782620 + patch
thanks
Hi Mark
Thanks for the report.
I can not, as a maintainer, judge that. It has to be decided by the release
team. However I do not think it will be accepted. It is essentially just
security problems that are fixed in stable releases.
Wheezy is also old-stable and only ge
I just experienced this today and found that the patch below fixed the
problem for me:
http://sourceforge.net/p/vnc-tight/patches/90/
Any chance that this could be applied as a fix for wheezy/jessie?
Hi
Thanks for the information.
The package is up for adoption. I do not have the time to dig into these
details. Any patch is welcome.
The package is not really well maintained upstream either.
I'm sorry for this reply.
// Ola
On Thu, Jun 25, 2015 at 12:56 PM, Thorsten Glaser
wrote:
> Hi ag
Hi again,
this just occurred again. This time I can say it happened when I tried
to start Kontact (KDEPIM) in VNC.
Please fix, a segfault is never acceptable (except in cases of stack
underrun in programming language interpreters for languages designed
to not limit recursion depth except by the O
Package: tightvncserver
Version: 1.3.9-6.5
Severity: important
I’ve been using tightvncserver for ages; this is the first time
it crashed on me. From the other bugreports, this *may* have to
do with me running KDEPIM for a short while inside it (but then
the KDE-related bugreport does not show muc
7 matches
Mail list logo
