You are not logged in.
- Topics: Active | Unanswered
#1 2024-04-22 21:31:29
- shuruper
- Member
- Registered: 2020-06-21
- Posts: 67
x2goclient error: The remote proxy closed the connection
Hi,
I was using x2goclient for a while now, but sometime ago after another update, which I can't quite trace, but most likely after new plasma-desktop release, x2goclient is unable to connect with the server. The following error message I receive after entering the correct credentials:
"The remote proxy closed the connection while negotiating the session. This may be due to the wrong authentication
credentials passed to the server."
I am able to connect to the server with "ssh name@server".
I do have some error messages from journalctl, but I'm not sure what to do with those. Downgrading X11 and libx11 didn't help.
Apr 22 16:52:32 _ x2goclient[19682]: x2go-WARNING-1> English language requested, not loading translator.
Apr 22 16:52:32 _ x2goclient[19682]: x2go-WARNING-1> English language requested, not loading translator.
Apr 22 16:52:32 _ drkonqi-coredump-launcher[19680]: Nothing handled the dump :O
Apr 22 16:52:32 _ drkonqi-coredump-launcher[19680]: Unable to find file for pid 19650 expected at "kcrash-metadata/x2goclient.d8903fcdbf57456d9b21c2c00a47bb5c.19650.ini"
Apr 22 16:52:32 _ systemd[895]: Started Launch DrKonqi for a systemd-coredump crash (PID 19669/UID 0).
Apr 22 16:52:32 _ systemd[1]: drkonqi-coredump-processor@1-19667-0.service: Deactivated successfully.
Apr 22 16:52:32 _ drkonqi-coredump-processor[19669]: "/usr/bin/x2goclient" 19650 "/var/lib/systemd/coredump/core.x2goclient.1000.d8903fcdbf57456d9b21c2c00a47bb5c.19650.1713819152000000.zst"
Apr 22 16:52:32 _ systemd[1]: systemd-coredump@1-19667-0.service: Deactivated successfully.
Apr 22 16:52:32 _ systemd-coredump[19668]: Process 19650 (x2goclient) of user 1000 dumped core.
Stack trace of thread 19650:
#0 0x00007ad4531058f6 XDefaultRootWindow (libX11.so.6 + 0x268f6)
#1 0x00005c1a44dbb05f n/a (x2goclient + 0x12405f)
#2 0x00005c1a44d35f0e n/a (x2goclient + 0x9ef0e)
#3 0x00007ad451cc8b63 n/a (libQt5Core.so.5 + 0x2c8b63)
#4 0x00007ad451cca4df _ZN6QTimer7timeoutENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2ca4df)
#5 0x00007ad451cbb44e _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2bb44e)
#6 0x00007ad4529578ff _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x1578ff)
#7 0x00007ad451c93a68 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x293a68)
#8 0x00007ad451ce20db _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5 + 0x2e20db)
#9 0x00007ad451ce2712 n/a (libQt5Core.so.5 + 0x2e2712)
#10 0x00007ad450320199 n/a (libglib-2.0.so.0 + 0x5a199)
#11 0x00007ad45037f3bf n/a (libglib-2.0.so.0 + 0xb93bf)
#12 0x00007ad45031f712 g_main_context_iteration (libglib-2.0.so.0 + 0x59712)
#13 0x00007ad451ce288c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2e288c)
#14 0x00007ad451c92774 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x292774)
#15 0x00007ad451c93c13 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x293c13)
#16 0x00005c1a44d6f587 n/a (x2goclient + 0xd8587)
#17 0x00005c1a44cdcaec n/a (x2goclient + 0x45aec)
#18 0x00007ad451443cd0 n/a (libc.so.6 + 0x25cd0)
#19 0x00007ad451443d8a __libc_start_main (libc.so.6 + 0x25d8a)
#20 0x00005c1a44cdd1d5 n/a (x2goclient + 0x461d5)
Stack trace of thread 19662:
#0 0x00007ad4515190df __poll (libc.so.6 + 0xfb0df)
#1 0x00007ad45308e933 n/a (libssh.so.4 + 0x2f933)
#2 0x00007ad45307bad1 ssh_select (libssh.so.4 + 0x1cad1)
#3 0x00005c1a44d5d749 n/a (x2goclient + 0xc6749)
#4 0x00005c1a44d56008 n/a (x2goclient + 0xbf008)
#5 0x00007ad451aeb88a n/a (libQt5Core.so.5 + 0xeb88a)
#6 0x00007ad4514a955a n/a (libc.so.6 + 0x8b55a)
#7 0x00007ad451526a5c n/a (libc.so.6 + 0x108a5c)
Stack trace of thread 19655:
#0 0x00007ad4514a5ebe n/a (libc.so.6 + 0x87ebe)
#1 0x00007ad4514a8750 pthread_cond_wait (libc.so.6 + 0x8a750)
#2 0x00007ad4330863cc n/a (iris_dri.so + 0x863cc)
#3 0x00007ad43309ebfc n/a (iris_dri.so + 0x9ebfc)
#4 0x00007ad4514a955a n/a (libc.so.6 + 0x8b55a)
#5 0x00007ad451526a5c n/a (libc.so.6 + 0x108a5c)
Stack trace of thread 19652:
#0 0x00007ad4515190df __poll (libc.so.6 + 0xfb0df)
#1 0x00007ad45037f306 n/a (libglib-2.0.so.0 + 0xb9306)
#2 0x00007ad45031f712 g_main_context_iteration (libglib-2.0.so.0 + 0x59712)
#3 0x00007ad451ce288c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2e288c)
#4 0x00007ad451c92774 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x292774)
#5 0x00007ad451aef666 _ZN7QThread4execEv (libQt5Core.so.5 + 0xef666)
#6 0x00007ad44d54da9a n/a (libQt5DBus.so.5 + 0x17a9a)
#7 0x00007ad451aeb88a n/a (libQt5Core.so.5 + 0xeb88a)
#8 0x00007ad4514a955a n/a (libc.so.6 + 0x8b55a)
#9 0x00007ad451526a5c n/a (libc.so.6 + 0x108a5c)
Stack trace of thread 19656:
#0 0x00007ad4514a5ebe n/a (libc.so.6 + 0x87ebe)
#1 0x00007ad4514a8750 pthread_cond_wait (libc.so.6 + 0x8a750)
#2 0x00007ad4330863cc n/a (iris_dri.so + 0x863cc)
#3 0x00007ad43309ebfc n/a (iris_dri.so + 0x9ebfc)
#4 0x00007ad4514a955a n/a (libc.so.6 + 0x8b55a)
#5 0x00007ad451526a5c n/a (libc.so.6 + 0x108a5c)
Stack trace of thread 19653:
#0 0x00007ad4515190df __poll (libc.so.6 + 0xfb0df)
#1 0x00007ad44d12305d n/a (libQt5WaylandClient.so.5 + 0x6905d)
#2 0x00007ad451aeb88a n/a (libQt5Core.so.5 + 0xeb88a)
#3 0x00007ad4514a955a n/a (libc.so.6 + 0x8b55a)
#4 0x00007ad451526a5c n/a (libc.so.6 + 0x108a5c)
Stack trace of thread 19654:
#0 0x00007ad4515190df __poll (libc.so.6 + 0xfb0df)
#1 0x00007ad44d12305d n/a (libQt5WaylandClient.so.5 + 0x6905d)
#2 0x00007ad451aeb88a n/a (libQt5Core.so.5 + 0xeb88a)
#3 0x00007ad4514a955a n/a (libc.so.6 + 0x8b55a)
#4 0x00007ad451526a5c n/a (libc.so.6 + 0x108a5c)
ELF object binary architecture: AMD x86-64
Apr 22 16:52:32 _ systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
Apr 22 16:52:32 _ systemd[1]: Started Process Core Dump (PID 19667/UID 0).
Apr 22 16:52:32 _ kernel: Code: 00 00 00 00 f3 0f 1e fa 8b 87 e0 00 00 00 c3 0f 1f 44 00 00 f3 0f 1e fa 48 63 87 e0 00 00 00 48 c1 e0 07 48 03 87 e8 00 00 00 <48> 8b 40 10 c3 0f 1f 44 00 00 f3 0f 1e fa 48 63 f6 48 c1 e6 07 48
Apr 22 16:52:32 _ kernel: x2goclient[19650]: segfault at 5c3cd1651c40 ip 00007ad4531058f6 sp 00007ffdeb7782c8 error 4 in libX11.so.6.4.0[7ad4530f6000+8b000] likely on CPU 6 (core 12, socket 0)I'll appreciate any help on this one.
Offline
#2 2024-04-22 22:12:19
- WorMzy
- Forum Moderator
- From: Scotland
- Registered: 2010-06-16
- Posts: 11,902
- Website
Re: x2goclient error: The remote proxy closed the connection
Mod note: moving to AUR Issues
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
#3 2024-04-29 15:04:42
- shuruper
- Member
- Registered: 2020-06-21
- Posts: 67
Re: x2goclient error: The remote proxy closed the connection
small update: this problem is plasma-wayland specific, x2go-client works perfectly fine on plasma-X11.
Offline