>8. dpkg -i libnx-x11-6_3.5.99.20-0_amd64.deb
>9. dpkg -i nxagent_3.5.99.20-0_amd64.deb
We are on Fedora, don't think this will work.
On Wed, May 15, 2019 at 2:52 PM Ulrich Sibiller wrote:
> see
>
see https://github.com/ArcticaProject/nx-libs/pull/809 for the patch.
Run
1. git clone https://github.com/uli42/nx-libs.git
2. cd nx-libs
3. git co pr/fix/xkb_crash
4. git revert b32a984f8f34d34fcc4114028712367c47c545d7 (due to this
the debian/ubuntu package building is currently a bit broken, so
> Are you able to compile a new nxagent once I have patch available?
Sure, just need to know the process.
On Wed, May 15, 2019 at 10:32 AM Ulrich Sibiller wrote:
> On Wed, May 15, 2019 at 4:24 PM Robert Kudyba wrote:
> >
> > Here's an update. MATE still crashes.
> > rpm -q x2goserver
>
>
On Wed, May 15, 2019 at 4:24 PM Robert Kudyba wrote:
>
> Here's an update. MATE still crashes.
> rpm -q x2goserver
This is not astonishing as I still have not patched anything. I wanted
to understand the problem first. But as I do not have access to (or
knowledge about) MacOS I cannot test this.
Here's an update. MATE still crashes.
rpm -q x2goserver
x2goserver-4.1.0.4-0.0x2go1.0.git20190329.1759.heuler.fc29.x86_64
May 15 09:07:05 ourserver /usr/bin/x2gostartagent[11784]: successfully
started X2Go Agent session with ID ouruser-67-1557925622_stDMATE_dp32
May 15 09:07:06 ourserver
> On Tue, Mar 26, 2019 at 7:51 PM Robert Kudyba wrote:
> > > c) you have configured a special keyboard configuration somewhere in
> Mate
> > I don't recall doing so. The only thing I did is allow the Hebrew
> > keyboard (selectable in the menu bar), but I had used a Hebrew
> > keyboard prior to
On Tue, Mar 26, 2019 at 7:51 PM Robert Kudyba wrote:
> > c) you have configured a special keyboard configuration somewhere in Mate
> I don't recall doing so. The only thing I did is allow the Hebrew
> keyboard (selectable in the menu bar), but I had used a Hebrew
> keyboard prior to this
> 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 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 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
#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
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 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
For testing you could try without ssh-agent or with the one of the current
openssh.
Uli
Mihai Moldovan schrieb am Mo., 25. März 2019, 13:59:
> * On 3/14/19 3:56 PM, Ulrich Sibiller wrote:
> > So chances are I introduced a problem here with this nxagent patch
> >
* On 3/14/19 3:56 PM, Ulrich Sibiller wrote:
> So chances are I introduced a problem here with this nxagent patch
> 522106e207e7230da5e62fb88f2e47742fdf1b21. What do you think, Mihai?
> Can you reproduce the crash?
Turns out that I cannot test this right now.
libssh doesn't let me connect to my
16 matches
Mail list logo
