[Bug 1183642] x2go cannot connect after last update on tumbleweed
http://bugzilla.opensuse.org/show_bug.cgi?id=1183642 http://bugzilla.opensuse.org/show_bug.cgi?id=1183642#c4 Tristan Miller <psychonaut@nothingisreal.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |psychonaut@nothingisreal.co | |m Flags|needinfo?(virex@mail.ru) | --- Comment #4 from Tristan Miller <psychonaut@nothingisreal.com> --- Same problem for me. X2Go was working fine with openSUSE-release-20220426 but upon upgrading to openSUSE-release-20220515, x2goserver immediately disconnects after accepting a connection. Reverting to the 20220426 system snapshot (via snapper) works around the problem, but of course isn't a real solution. At the time I was running a development version of x2goserver from September 2021. The problem persists when running the latest development versions of x2goserver (and x2goclient, nx-libs, etc.) from today: <https://download.opensuse.org/repositories/home:/psych0naut:/x2go/openSUSE_Tumbleweed/>. The operation of x2goclient is unaffected; it's still possible to connect to X2Go servers running on earlier versions of Tumbleweed, or on Leap 15.3. Running applications remotely directly with ssh -X sill works. There is nothing obvious (to me, anyway) in the x2goclient, x2goserver, and sshd logs that points to a cause, but I can provide these on request. An X2Go developer is aware of the issue (see thread at <https://lists.x2go.org/pipermail/x2go-user/2022-May/006813.html>) but also doesn't seem to know what the problem might be. Our best guess is that some update to the security or networking packages in Tumbleweed is the culprit. I've already tried downgrading openssh (to the packages from 3 months ago), and also temporarily disabling AppArmor, but that didn't help. I'm clearing the needinfo flag as I believe Igor has already provided the requested logs. Let me know what other things I could try to downgrade. (I suppose I could restore my snapshot from 20220426 and then start upgrading suspicious packages one at a time until I find the ones that break X2Go, though that might take a very long time.) -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com