Test case (put this in one of the ubuntu 24.04 tests):
function test_post_boot_grub() {
# Wait a while for EUFI or BIOS to pass
# We could skip having this function, but it's nice to have
# So we have the opportunity to click that stupid dialog
qt_wait_for_seconds 10
# Wait for the grub menu
qt_wait_for_text "$FUNCNAME" "$text_console_gnu_grub" 10 5
qt_send_key "e"
qt_wait_for_seconds 1
qt_send_key "down"
qt_wait_for_seconds 1
qt_send_key "down"
qt_wait_for_seconds 1
qt_send_key "down"
qt_wait_for_seconds 1
qt_send_key "end"
qt_wait_for_seconds 1
qt_send_string " console=ttyS0,115200"
qt_screenshot_ppm "$FUNCNAME"
qt_send_key "f10"
}
What should happen:
- "e" - begin editing the boot config
- "down"x3 - move down three lines
- "end" - move to end of line
- insert the string
- "f10" - boot with edited command line
What actually happens:
- "e" works and we enter the editor.
- "down", "end" are ignored.
- The extra command lines are typed in the wrong place.
- "f10" is ignored, leaving the system like this:

The "console=..." should be at the end of the line beginning with "linux".
Test case (put this in one of the ubuntu 24.04 tests):
What should happen:
What actually happens:
The "console=..." should be at the end of the line beginning with "linux".