Project

General

Profile

Actions
Copy link

action #177769

open

[WSL] Firstboot is not launched automatically after install from MS Store

Added by pherranz about 1 month ago. Updated 4 days ago.

Status:
Feedback
Priority:
High
Assignee:
etchubykalo
Target version:
-
Start date:
2025-02-24
Due date:
% Done:

0%

Estimated time:
Tags:
WSL

Description

After installing from the MS Store with wsl --install --distribution <distro_name>, the firstboot YaST screen is not being launched automatically:

https://openqa.suse.de/tests/16855623/modules/install_wsl/steps/13

Files

Download all files
clipboard-202502251255-2abvc.png (44.2 KB) clipboard-202502251255-2abvc.png etchubykalo, 2025-02-25 11:55
clipboard-202502261129-hn8qk.png (20.5 KB) clipboard-202502261129-hn8qk.png etchubykalo, 2025-02-26 10:29
clipboard-202502261130-0mnas.png (22.8 KB) clipboard-202502261130-0mnas.png etchubykalo, 2025-02-26 10:30
Actions
Copy link
 #1

Updated by etchubykalo about 1 month ago

  • Assignee set to etchubykalo
Actions
Copy link
 #4

Updated by etchubykalo 28 days ago

PR to launch Yast Firstboot after installation: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/21284

Actions
Copy link
 #5

Updated by etchubykalo 27 days ago

  • Status changed from Workable to Resolved
Actions
Copy link
 #6

Updated by openqa_review 11 days ago

  • Status changed from Resolved to Feedback

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: wsl2-install-msstore
https://openqa.suse.de/tests/17091627#step/install_wsl/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions
Copy link
 #7

Updated by shundhammer 4 days ago · Edited

Hm... the pseudo-graphics characters are there; the lines, the corners...
but there are additional characters as well.

Wrong terminal type? Some escape sequences not executed, but printed on the screen instead?

I'd start investigating by checking the terminal type on the windows side.
Then check in the Linux session what value $TERM has.
/var/log/YaST2/y2start.log should also have it.

You can contact me in the #yast IRC channel on irc.libera.chat (fastest) or on Slack (might be delayed a bit).

Actions
Copy link

Also available in: Atom PDF