Alma 10.1 rdp install broken

Support
1

Hi:

I decide to test AlmaLinux since btrfs is back again. I start play with anaconda at vm. and I found rdp install parameter like “inst.rdp inst.rdp.username=userxxx inst.rdp.password=passxxx” failed.

tail  /tmp/syslog I got the error message below:

ERR gnome-remote-desktop:[14:02:01:259] [3286:00000e4f] [WARN][com.freerdp.core.peer] - [peer_unexpected_client_message]: Unexpected client message in state CONNECTION_STATE_FINALIZATION_FONT_LIST, missing flag FINALIZE_CS_FONT_LIST_PDU [0x00000100]
14:02:01,301 NOTICE gnome-remote-de:[RDP.CLIPRDR] Client capabilities: long format names, stream file clip, file clip no file paths, can lock clip data, huge file support
14:02:01,308 WARNING gnome-remote-de:Failed to start screen cast stream: GDBus.Error:org.freedesktop.DBus.Error.Failed: Failed to start stream: Couldn't connect pipewire context
14:02:01,308 ERR gnome-remote-desktop:[14:02:01:294] [3286:00000cd6] [ERROR][com.freerdp.core.peer] - [rdp_set_error_info]: ERRINFO_RPC_INITIATED_DISCONNECT [0x00010001]

rdp installation is important for EL10, because many Dell/HP/Lenovo server BMC don’t have wayland support so gui installation is not possible without rdp.

RHEL 10.1 rdp installation is fine and didn’t have such error message.

2

hi

Failed to start screen cast stream … Couldn’t connect pipewire context
→ Unable to connect to PipeWire context = Unable to start stream = Unable to continue RDP

The subsequent
ERRINFO_RPC_INITIATED_DISCONNECT
is simply treated as “disconnected by the server side”.

peer_unexpected_client_message … FONT_LIST also occurs when the other party sends an unexpected PDU during the handshake or disconnects midway,
so the root cause is likely a PipeWire failure, right?

As a workaround, try changing the RDP client (Windows mstsc / newer FreeRDP). If it doesn’t improve, report it as an AlmaLinux installer bug, attaching the ISO checksum and /tmp/syslog. I think that’s necessary.

thanks

3

Hi:
thanks for reply. I am new to AlmaLinux. this is my first day to use it. I tried to install it many times with many ways at the vm. where should I report the bug? is it better if I buy tuxcare? can it create ticket like this kind of problem?

4

Hi,

Please report it here: https://bugs.almalinux.org/

Attach ISO checksum and the installer logs: /tmp/syslog and /tmp/anaconda.log.
No need to buy anything just to report a bug — the tracker is open.

Thanks.

5

Hi:

I don’t know how to login bugs.almalinux.org. I create a account which is “almalinux account”, but it seems useless. I can not use it to login to forum or matis-bug. at least forum let me create another account. but there is no way to create account at bugs.almalinux.org.

6

Hello

You should be able to log in with “tbsky” and your password.
Thanks

7

How do we create an account?

When I try to login with the forum’s username:

image

Very useful error message, go figure which case it is…

8

Hi:
Thanks for the hint. I already report the bug.

9

Hi:

I found the general “AlmaLinux account” works. but you need to wait some time after you create an official “AlamLinux account”. it seems each system need to sync the account status. but forum doesn’t use the office “AlmaLinux account”. it seems forum has its own account system.

10

the bug is true, but my assumption above was wrong.

I said “many Dell/HP/Lenovo server BMC with matrox g200 has no wayland support”. this was misleading by chatgpt and gemini.

I have dell servers which can not install RHEL10 via gui (but RHEL9 is fine). the root cause is not matrox vga. the root cause is nvidia telsa gpu card at the server.
base on RedHat knowledgebase, RHEL10 gui failed at the situation and it need a kernel parameter to workaround it “modprobe.blacklist=nouveau”.
I test a dell sever without nvidia gpu and RHEL10/Alma10 gui installation is fine.

but as I said, Alma inst.rdp bug is still true. RHEL 10.1 with “inst.rdp” works fine. AlmaLinux 10.1 is broken with the parameter.