Happened again. I closed the x2go session using the window close (X on top
right), and then got a message box saying
"The x2go connection was shut down" or something like that. Then 100% cpu.
On Thu, Sep 17, 2020 at 10:37 AM Neal Becker wrote:
> I believe I often see some message (something
I believe I often see some message (something like something didn't
disconnect cleanly) associated with this problem.
On Thu, Sep 17, 2020 at 10:11 AM Lorenzo Iannuzzi wrote:
> For me too.
>
> Il giorno gio 17 set 2020 alle ore 16:02 Neal Becker
> ha scritto:
>
>> For me it's client
>>
>> On
For me too.
Il giorno gio 17 set 2020 alle ore 16:02 Neal Becker
ha scritto:
> For me it's client
>
> On Thu, Sep 17, 2020, 9:55 AM Ulrich Sibiller wrote:
>
>> Are we talking about the server or the client?
>>
>> Uli
>>
>> On Thu, Sep 17, 2020 at 3:23 PM Neal Becker wrote:
>> >
>> > This has
For me it's client
On Thu, Sep 17, 2020, 9:55 AM Ulrich Sibiller wrote:
> Are we talking about the server or the client?
>
> Uli
>
> On Thu, Sep 17, 2020 at 3:23 PM Neal Becker wrote:
> >
> > This has been happening for a long time now on Fedora. When a session
> is closed, there is perhaps
Are we talking about the server or the client?
Uli
On Thu, Sep 17, 2020 at 3:23 PM Neal Becker wrote:
>
> This has been happening for a long time now on Fedora. When a session is
> closed, there is perhaps 10% probability that it goes into this state.
>
> On Thu, Sep 17, 2020 at 9:05 AM
This has been happening for a long time now on Fedora. When a session is
closed, there is perhaps 10% probability that it goes into this state.
On Thu, Sep 17, 2020 at 9:05 AM Lorenzo Iannuzzi wrote:
> I read of similar issues in the past, but none seems like mine. If I leave
> x2goclient
