Hi All,
On 12/1/21 18:49, Celejar wrote:
>>> Primarily the segfault,
as far as I can tell, tigervnc does not segfault. The problem is that the
xfce session segfaults and terminates early. Moreover, default for tigervnc
is on session termination to kill the VNC server.
Try
tigervncserver
Hi All,
On 12/1/21 18:49, Celejar wrote:
>>> Primarily the segfault,
as far as I can tell, tigervnc does not segfault. The problem is that the
xfce session segfaults and terminates early. Moreover, default for tigervnc
is on session termination to kill the VNC server.
Try
tigervncserver
Thanks for all your work on behalf of Debian. I certainly didn't mean
to blame you for the lack of documentation, and I understand that these
problems are usually upstream's fault.
On Wed, 1 Dec 2021 09:47:37 +0100
Ola Lundqvist wrote:
> Hi
>
> Thank you.
>
> I guess the main reason for the
Hi
Thank you.
I guess the main reason for the lack of documentation is that it is not
provided by upstream. This was the case also for tightvnc, vnc4 and vnc(3).
I wrote some documentation for those other packages but I guess it was
never done for tigervnc.
I do not think you made anything
Primarily the segfault, although the problem is compounded by the
absence of documentation, which makes it difficult to know whether I'm
doing something wrong with my invocation.
On Tue, 30 Nov 2021 23:07:11 +0100
Ola Lundqvist wrote:
> Hi
>
> Just a check question. Is your bug about the lack
Hi
Just a check question. Is your bug about the lack of useful documentation
or the fact that it segfaults?
It should not segfault...
// Ola
On Tue, 30 Nov 2021 at 15:03, Celejar wrote:
> Package: tigervnc-standalone-server
> Version: 1.11.0+dfsg-3
> Severity: important
> X-Debbugs-Cc:
6 matches
Mail list logo