Description of problem: logging in via X2Go Version-Release number of selected component: nxagent-3.5.99.20-2.fc31 Additional info: reporter: libreport-2.11.3 backtrace_rating: 4 cgroup: 0::/user.slice/user-1201.slice/session-2486.scope cmdline: x2goagent -nolisten tcp -nolisten tcp -dpi 90 -D -auth /u/sobolev/agw/.Xauthority -geometry 1280x1024 -name X2GO-agw-51-1578932017_stDMATE_dp32 :51 crash_function: XkbAdjustGroup executable: /usr/bin/nxagent journald_cursor: s=1669a10ea05e40aca9b46dc1106e1de2;i=1a47668d;b=14e7f9086be34450ac91a560c61157db;m=18728ca4c54;t=59c07c2e0866f;x=1b6f32bcbfd14960 kernel: 5.3.16-300.fc31.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1201 Truncated backtrace: Thread no. 1 (4 frames) #0 XkbAdjustGroup at xkbUtils.c:688 #1 XkbComputeDerivedState at xkbUtils.c:714 #2 ProcXkbLatchLockState at xkb.c:560 #3 Dispatch at NXdispatch.c:482
Created attachment 1651961 [details] File: backtrace
Created attachment 1651962 [details] File: core_backtrace
Created attachment 1651963 [details] File: cpuinfo
Created attachment 1651964 [details] File: dso_list
Created attachment 1651965 [details] File: environ
Created attachment 1651966 [details] File: limits
Created attachment 1651967 [details] File: maps
Created attachment 1651968 [details] File: mountinfo
Created attachment 1651969 [details] File: open_fds
Created attachment 1651970 [details] File: proc_pid_status
I think this is the relevant x2go bug report: https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1376 And this seems relevant to the X11 code: https://gitlab.freedesktop.org/xorg/xserver/issues/283 In any case, this is going to need to be resolved upstream.
nx-libs has a workaround for that bug included in 3.5.99.21 and newer. The relevant nx-libs issue is this: https://github.com/ArcticaProject/nx-libs/issues/808
FEDORA-2019-eaf3a67b84 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-eaf3a67b84
nx-libs-3.5.99.22-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.