* On 3/25/19 2:10 PM, Ulrich Sibiller wrote:
> For testing you could try without ssh-agent or with the one of the current
> openssh.
Sure, that's the quickest workaround... I just switched to no-agent auth for
testing.
Naturally, though, I wasn't able to reproduce the problem with the current
Processing control commands:
> close -1
Bug #773 [x2goclient] DirectRDP: X2Go Client reveals user password in process
list if xfreerdp is used
Marked Bug as done
--
773: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=773
X2Go Bug Tracking System
Contact ow...@bugs.x2go.org with problems
Processing control commands:
> close -1
Bug #58 [x2goplugin] x2goplugin: after session startup whole local desktop
unusable
Marked Bug as done
--
58: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=58
X2Go Bug Tracking System
Contact ow...@bugs.x2go.org with problems
Uh, wait a minute. We're still shipping X2GoClient for distributions
that have an older xfreerdp version in their repository.
Thus, this should not be closed until all supported distros have made
the switch to xfreerdp2.
-Stefan
Am 26.03.19 um 14:19 schrieb Mike Gabriel:
> Control: close -1
>
Control: close -1
On Fr 22 Mär 2019 23:08:00 CET, Ulrich Sibiller wrote:
xfreerdp 2 also es the password
So with a current version this is a non-issueand can be closed.
Thus, closing...
Mike
--
DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler
Control: close -1
On Fr 22 Mär 2019 23:09:02 CET, Ulrich Sibiller wrote:
x2goplugin is dead, this ticket can be closed.
So, please close such bugs using the above (at the top) syntax.
Mike
--
DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler str. 17,
Perhaps these logs and core dump GDB backtrace will help? Notice that nx-libs
is now nx-libs-3.5.99.19-0.0build1.0.git20190325.3293.heuler.fc29.x86_64
Mar 26 09:22:17 ourwokstation /usr/bin/x2gostartagent[16213]: successfully
started X2Go Agent session with ID agw-58-1553606535_stDMATE_dp32
Mar
> On Mar 26, 2019, at 12:42 PM, Ulrich Sibiller wrote:
>
> On Tue, Mar 26, 2019 at 5:17 PM Ulrich Sibiller wrote:
>>
>> #2 0x55c236293ca6 in ProcXkbLatchLockState
>> (client=0x55c2372372d0) at xkb.c:560
>>
>> -> Proc* is always a call from outside to an extension, in this case
>> the
> On Mar 26, 2019, at 12:17 PM, Ulrich Sibiller wrote:
>
> #2 0x55c236293ca6 in ProcXkbLatchLockState
> (client=0x55c2372372d0) at xkb.c:560
>
> -> Proc* is always a call from outside to an extension, in this case
> the XKB extension.
>
> So do you have some setxkbmap call in your shell
On Tue, Mar 26, 2019 at 5:17 PM Ulrich Sibiller wrote:
>
> #2 0x55c236293ca6 in ProcXkbLatchLockState
> (client=0x55c2372372d0) at xkb.c:560
>
> -> Proc* is always a call from outside to an extension, in this case
> the XKB extension.
>
> So do you have some setxkbmap call in your shell
On Tue, Mar 26, 2019 at 10:13 AM Mihai Moldovan wrote:
>
> * On 3/25/19 2:10 PM, Ulrich Sibiller wrote:
> > For testing you could try without ssh-agent or with the one of the current
> > openssh.
>
> Sure, that's the quickest workaround... I just switched to no-agent auth for
> testing.
>
>
On Tue, Mar 26, 2019 at 3:09 PM Stefan Baur wrote:
>
> Uh, wait a minute. We're still shipping X2GoClient for distributions
> that have an older xfreerdp version in their repository.
>
> Thus, this should not be closed until all supported distros have made
> the switch to xfreerdp2.
I have
#2 0x55c236293ca6 in ProcXkbLatchLockState
(client=0x55c2372372d0) at xkb.c:560
-> Proc* is always a call from outside to an extension, in this case
the XKB extension.
So do you have some setxkbmap call in your shell startup files? What
are they doing? Does this also happen with other
13 matches
Mail list logo
