AntonioPt wrote: Sat Mar 22, 2025 6:09 pm xorgwizard-cli if you click on it will frozen machine
The file has -cli in its name, indicating that it MUST be run from a terminal. I don't understand why you expect it to work when you do NOT run it from a terminal.
Please review your previous post. Same issue. Your mistake and not a bug.
However I do see a problem of the xorgwizard script, starting at line 12
Code: Select all
[ -z "$DISPLAY" -a -z "$WAYLAND_DISPLAY" ] && CLI=1
[ "$XDG_SESSION_TYPE" = 'wayland' ] && CLI=''
case $script in
xorgwizard-cli) CLI=1 ;;
xorgwizard-automatic) AUTOMATIC=1 ;;
esac
It seems to me that the line xorgwizard-cli) CLI=1 ;;
shouldn't exist. It overrides the setting for the CLI variable of the first line, without checking if the necessary conditions are met. The line [ -z "$DISPLAY" -a -z "$WAYLAND_DISPLAY" ] && CLI=1
would sufficiently ensure that xorgwizard or xorgwizard-cli run in cli mode if invoked from a real terminal, not a console window or a GUI. In all other cases both scripts would run in GUI mode, avoiding the problem you encountered.
BTW: The file xorgwizard-automatic, also a symlink to xorgwizard, runs in GUI mode when clicked, so no harm done. However when run from a virtual console window it surprises with the message "If you are reading this, then you are at the console without X running. The usual thing now is to type 'xwin' to start X..."
The usual thing is to ignore this lie because I definitely can read this while running X 