-
Bug
-
Resolution: Unresolved
-
Major
-
rhel-10.1
-
lorax-templates-rhel-10.1-3.el10
-
Yes
-
Critical
-
image-builder-1
-
22
-
None
-
False
-
False
-
-
None
-
None
-
Pass
-
Automated
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
I was running a RHEL-10.1 installation in RDP mode and when I tried to connect, the connection failed and Anaconda crashed.
Excerpt from anaconda.log:
15:23:12,516 DBG misc: GLib: (anaconda:2652): Gtk-WARNING **: 15:23:12.516: Negative content width -5 (allocation 13, extents 9x9) while allocating gadget (node entry, owner GtkEntry) 15:29:00,356 DBG exception: running handleException 15:29:00,357 CRT exception: Traceback (most recent call last): File "/usr/lib64/python3.12/site-packages/gi/_ossighelper.py", line 92, in signal_notify def signal_notify(source, condition): File "/usr/lib64/python3.12/site-packages/pyanaconda/core/process_watchers.py", line 117, in _sigchld_handler cls._raise_exit_error(exit_statuses) File "/usr/lib64/python3.12/site-packages/pyanaconda/core/process_watchers.py", line 81, in _raise_exit_error raise ExitError(", ".join(exn_message))pyanaconda.errors.ExitError: systemd exited with status 0 15:29:00,357 DBG exception: Gtk running, queuing exception handler to the main loop 15:29:01,554 INF kickstart.script: Running kickstart %%traceback script(s) 15:29:01,554 INF kickstart.script: All kickstart %%traceback script(s) have been run 15:29:01,554 INF core.util: Reporting the IPMI event: 10 15:29:01,585 DBG misc: GLib: (anaconda:2652): Gdk-CRITICAL **: 15:29:01.585: gdk_monitor_get_workarea: assertion 'GDK_IS_MONITOR (monitor)' failed
Excerpt from journal (syslog):
15:28:02,545 NOTICE gnome-remote-de:[RDP.CLIPRDR] Relieving CLIPRDR filename restriction 15:28:02,559 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 15:28:02,560 ERR gnome-remote-desktop:[15:28:02:303] [2949:00000b85] [ERROR][com.freerdp.core.peer] - [rdp_set_error_info]: ERRINFO_RPC_INITIATED_DISCONNECT [0x00010001] 15:28:02,561 INFO systemd:run-user-0-gnome\x2dremote\x2ddesktop-cliprdr\x2dqgMp4N.mount: Deactivated successfully. 15:28:02,568 WARNING gnome-kiosk:g_settings_get_value: assertion 'G_IS_SETTINGS (settings)' failed 15:28:02,568 WARNING gnome-kiosk:g_variant_get_type: assertion 'value != NULL' failed 15:28:02,568 WARNING gnome-kiosk:g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed 15:28:02,568 WARNING gnome-kiosk:g_variant_get_boolean: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_BOOLEAN)' failed 15:28:02,568 WARNING gnome-kiosk:g_variant_unref: assertion 'value != NULL' failed 15:28:06,661 WARNING brltty:unsupported generic resource identifier: bluetooth:
Also, I'm not sure what component is exactly broken (gnome-remote-desktop is just basically on top of the stack), so please reassign it appropriately if needed.
What is the impact of this issue to you?
The RDP installation functionality can't be used, and also the GUI automated test tooling - Anabot is broken (at least unless RHEL-64694 is implemented).
Please provide the package NVR for which the bug is seen:
gnome-remote-desktop-47.3-1.el10 (RHEL-10.1-20250703.10, gnome-kiosk-47.0-10.el10, anaconda-40.22.3.30-1.el10, mutter-47.5-11.el10)
How reproducible is this bug?:
Always.
Steps to reproduce
- Start RHEL-10.1-20250703.10 (or newer) installation in RDP mode (provide inst.rdp inst.rdp.username=username inst.rdp.password=password parameters on kernel command line).
- Connect to the running installation via RDP (e. g. xfreerdp /u:username /p:password /v:192.168.122.222 /cert:ignore)
Expected results
It's possible to connect via RDP and successfully finish the installation.
Actual results
RDP connection can't be established, Anaconda crashes.
Additional notes
The previous compose RHEL-10.1-20250626.1 worked fine.
In the case of automated installation testing using Anabot, it also occurs that gnome-kiosk or gnome-ponytail-daemon crash with a core dump. I feel like the crash can likely be caused by the lack of an existing RDP session (and thus an RDP monitor) in the first place, but if you think it's not the case, I can file a separate bug for that. I'll also attache the core dumps (from different installations though), so that you can investigate them.
Feel free to ping me should you need any further information or logs.
- links to
-
RHBA-2025:150012
lorax-templates-rhel bug fix and enhancement update