sdl: Cannot connect to GNOME with empty domain

[darkblaze69]

• OS: Arch Linux
• freerdp-git 3.2.0.r1.gbc23b205b

Cannot connect with empty domain to GNOME remote desktop sdl-freerdp /v:remoteip /u:user

The same with xfreerdp I can connect without a problem.

[01:12:39:473] [34748:000087bc] [WARN][com.freerdp.client.common.cmdline] - [freerdp_client_warn_experimental]: [experimental] sdl-freerdp client is currently experimental!
[01:12:39:473] [34748:000087bc] [WARN][com.freerdp.client.common.cmdline] - [freerdp_client_warn_experimental]:  If problems occur please check https://github.com/FreeRDP/FreeRDP/issues for known issues or create a new one!
[01:12:39:473] [34748:000087bc] [WARN][com.freerdp.client.common.cmdline] - [freerdp_client_warn_experimental]:  Developers hang out in https://matrix.to/#/#FreeRDP:matrix.org?via=matrix.org - dont hesitate to ask some questions. (replies might take some time depending on your timezone)
[01:12:40:430] [34748:000087bd] [INFO][com.freerdp.client.SDL] - [sdl_pre_connect]: Update size to 1024x768
[01:12:40:526] [34748:000087bd] [WARN][com.freerdp.crypto] - [verify_cb]: Certificate verification failure 'self-signed certificate (18)' at stack position 0
[01:12:40:526] [34748:000087bd] [WARN][com.freerdp.crypto] - [verify_cb]: CN = GNOME, C = US
[01:12:40:580] [34748:000087bc] [INFO][com.freerdp.client.SDL] - [winpr_LogOutputFunction]: [SDL_LOG_CATEGORY_RENDER] OpenGL shaders: ENABLED
[01:12:40:580] [34748:000087bc] [INFO][com.freerdp.client.SDL] - [winpr_LogOutputFunction]: [SDL_LOG_CATEGORY_RENDER] Created renderer: opengl
[01:12:40:598] [34748:000087bc] [INFO][com.freerdp.client.SDL] - [winpr_LogOutputFunction]: [SDL_LOG_CATEGORY_RENDER] OpenGL shaders: ENABLED
[01:12:40:598] [34748:000087bc] [INFO][com.freerdp.client.SDL] - [winpr_LogOutputFunction]: [SDL_LOG_CATEGORY_RENDER] Created renderer: opengl
[01:12:44:763] [34748:000087bc] [ERROR][com.freerdp.core] - [freerdp_abort_connect_context]: ERRCONNECT_CONNECT_CANCELLED [0x0002000B]
[01:12:46:549] [34748:000087bd] [ERROR][com.winpr.sspi.Kerberos] - [kerberos_AcquireCredentialsHandleA]: krb5glue_get_init_creds (Client 'user@ATHENA.MIT.EDU' not found in Kerberos database [-1765328378])
[01:12:48:880] [34748:000087bd] [ERROR][com.winpr.sspi.Kerberos] - [kerberos_AcquireCredentialsHandleA]: krb5glue_get_init_creds (Client 'user@ATHENA.MIT.EDU' not found in Kerberos database [-1765328378])

[akallabeth]

@darkblaze69 I doubt that there is a difference between sdl-freerdp and xfreerdp here (assuming you´re not using different versions)

could you please add a bit more of detail (posting only the last log lines or just the something failed, see above without the above is not sufficient)

[zeule]

I have the same problem. The latest working sdl version was 3.0.0, 3.1.0 and above refuses to connect to a Windows 11/KVM instance, xfreerdp and wlfreerdp work fine.

[akallabeth]

I have the same problem. The latest working sdl version was 3.0.0, 3.1.0 and above refuses to connect to a Windows 11/KVM instance, xfreerdp and wlfreerdp work fine.

@zeule and again, please some details, the description sounds fishy (all the clients use the same connection routine) so it is something else at work here.

[zeule]

A Windows 11 Pro in the KVM, not a domain member. The SDL client is the only one that provides tearing free and almost color-perfect picture, so I want to use that. After an update a few days ago the SDL client ceased to connect to that machine. Downgrading to 3.0.0 made it work again. I attach two logs (for version 3.0.0 and for the current master), generated by the following command line: sdl-freerdp /u:$USER /p:$(kwallet-query kdewallet -f KRDC -r rdp://${USER}@${SERVER}) /v:${SERVER} /cert:ignore /log-level:TRACE.
sdl-freerdp-3.0.0.log
sdl-freerdp-master.log

Additionally, the non-working version prints to the terminal (despite active stderr redirection)

[10:34:23:558] [257391:0003ed7a] [ERROR][com.freerdp.core] - [freerdp_connect]: freerdp_post_connect failed
[10:34:23:558] [257391:0003ed7a] [ERROR][com.freerdp.core] - [freerdp_connect]: ERRCONNECT_POST_CONNECT_FAILED [0x00020003]

[zeule]

Unfortunately, build fails for many SDL-related commits, so git bisect results are not very useful:

There are only 'skip'ped commits left to test.
The first bad commit could be any of:
35d5842
dd71158
765129a
c952fae
5e6ca89
d5b0939
14a4a6a
a8eaf2a
4166570
e6384c0
2056ffe
b89f025
187f562
caac867
3095814
e1de32f
3bdaca8
We cannot bisect more!

[zeule]

When built from master with SDL_Image installed, the SDL client enters a loop rather than exiting with an error.

[zeule]

When built from master with SDL_Image installed, the SDL client enters a loop rather than exiting with an error.

Sorry, scratch that, please. I used sfreerdp instead of sdl-freerdp.

[akallabeth]

@zeule the log from master indicates your build (or SDL) are broken, there are lots of

[winpr_LogOutputFunction]: [SDL_LOG_CATEGORY_ERROR] The event system has been shut down
[winpr_LogOutputFunction]: [SDL_LOG_CATEGORY_ERROR] Video subsystem has not been initialized

entries, which are not possible unless there is something wrong with SDL

[edit] although, a broken compile could also be at fault

[akallabeth]

Additionally, the non-working version prints to the terminal (despite active stderr redirection)

[10:34:23:558] [257391:0003ed7a] [ERROR][com.freerdp.core] - [freerdp_connect]: freerdp_post_connect failed
[10:34:23:558] [257391:0003ed7a] [ERROR][com.freerdp.core] - [freerdp_connect]: ERRCONNECT_POST_CONNECT_FAILED [0x00020003]

that is not possible, all log entries of WLog_* are written here with either stdout or stderr

[akallabeth]

@zeule did you properly install your compile with cmake --install <builddir> or cmake --build <builddir> --target install? if not there might be issues with resources not being at expected locations.

[edit] also, did you try our nightly builds?

[akallabeth]

Cannot connect with empty domain to GNOME remote desktop sdl-freerdp /v:remoteip /u:user

The same with xfreerdp I can connect without a problem.

@darkblaze69 just tested that on a debian 12 running g-r-d and connecting with sdl-freerdp as well as xfreerdp from bc23b20
I can connect without any issue.

please add some more details.

[zeule]

@zeule the log from master indicates your build (or SDL) are broken, there are lots of

[winpr_LogOutputFunction]: [SDL_LOG_CATEGORY_ERROR] The event system has been shut down
[winpr_LogOutputFunction]: [SDL_LOG_CATEGORY_ERROR] Video subsystem has not been initialized

My libsdl2 was build without haptic support, SDL_Init(INIT_EVERYTHING) fails under those conditions. Maybe consider listing required subsystems explicitely?

[zeule]

Additionally, the non-working version prints to the terminal (despite active stderr redirection)

[10:34:23:558] [257391:0003ed7a] [ERROR][com.freerdp.core] - [freerdp_connect]: freerdp_post_connect failed
[10:34:23:558] [257391:0003ed7a] [ERROR][com.freerdp.core] - [freerdp_connect]: ERRCONNECT_POST_CONNECT_FAILED [0x00020003]

that is not possible, all log entries of WLog_* are written here with either stdout or stderr

Hm... I just do 2>&1, what can go wrong with that?

[akallabeth]

Hm... I just do 2>&1, what can go wrong with that?

well, that just redirects stderr to stdout so where do you expect the result to be printed?

[zeule]

Hm... I just do 2>&1, what can go wrong with that?

well, that just redirects stderr to stdout so where do you expect the result to be printed?

I redirect that to a file, of course. But that problem is of minor importance, sdl-freerdp works now, thanks to your hint!