[yast2] can not open so I can do nothing

[soundlord]

xdg-su -c ‘/sbin/yast2 repositories’

Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
If this causes problems, reconfigure your locale. See the locale(1) manual
for more information.
/usr/bin/ldd: line 159: /lib/ld-linux.so.2: cannot execute binary file: Exec format error
Qt GUI wanted but not found, falling back to ncurses.
/usr/bin/ldd: line 159: /lib/ld-linux.so.2: cannot execute binary file: Exec format error
package yast2-ncurses is not installed
package yast2-qt is not installed
package yast2-gtk is not installed
Something is wrong with the YaST user interface.

My locale are

LANG=POSIX
LC_CTYPE="POSIX"
LC_NUMERIC="POSIX"
LC_TIME="POSIX"
LC_COLLATE="POSIX"
LC_MONETARY="POSIX"
LC_MESSAGES="POSIX"
LC_PAPER="POSIX"
LC_NAME="POSIX"
LC_ADDRESS="POSIX"
LC_TELEPHONE="POSIX"
LC_MEASUREMENT="POSIX"
LC_IDENTIFICATION="POSIX"
LC_ALL=

I’m trying to find a way to set at least LANG to BE.utf8…
But it seems all the tries failed

[hui]

This comment might help you to set your locale.:

Dual gpu, intel and nvidia, and external monitor

To list all available (installed) locales, simply type localectl list-locales in a terminal. Then you can set the one you want from this list. As example english US: sudo localectl set-locale LANG=en_US.UTF-8 Or for italien IT: sudo localectl set-locale LANG=it_IT.UTF-8 To check, if the change was properly applied, type locale in a terminal.

Also dependend on your used desktop environment, there are also possibilities to set the locale. E.g for Plasma you can use systemsettings.

The YaST stack got removed from Leap 16.0. See also the Leap 16.0 release notes.

To setup your repos and for software management, Myrlyn is the successor of the YaST Software and YaST Repositories module.

For general system management, Cockpit is the successor of many YaST modules.

[dcurtisfra]

@soundlord:

A little bit more information:

• “localectl list-locales | less” only indicates “be_BY.UTF-8” …

More information is available by means of “locale --all-locales -v | less” –

locale: be_BY           directory: /usr/lib/locale/be_BY
-------------------------------------------------------------------------------
    title | Belarusian locale for Belarus
    email | bug-glibc-locales@gnu.org
 language | Belarusian
territory | Belarus
 revision | 1.0
     date | 2000-06-29
  codeset | CP1251

locale: be_BY@latin     directory: /usr/lib/locale/be_BY@latin
-------------------------------------------------------------------------------
    title | Belarusian Latin-Script locale for Belarus
    email | bug-glibc-locales@gnu.org
 language | Belarusian
territory | Belarus
 revision | 1.0
     date | 2005-09-15
  codeset | UTF-8

locale: be_BY.utf8      directory: /usr/lib/locale/be_BY.utf8
-------------------------------------------------------------------------------
    title | Belarusian locale for Belarus
    email | bug-glibc-locales@gnu.org
 language | Belarusian
territory | Belarus
 revision | 1.0
     date | 2000-06-29
  codeset | UTF-8

Which then allows the following check:

 > rpm --query --whatprovides /usr/lib/locale/be_*
glibc-locale-2.43-4.2.x86_64
glibc-locale-2.43-4.2.x86_64
glibc-locale-2.43-4.2.x86_64
 >

You may have to check if, the package “glibc-locale” is correctly installed –

 > rpm --verify glibc-locale
 >

---

Please note that, the versions shown here are the Tumbleweed versions – the Leap 16.0 versions may well be older …

[soundlord]

is that same with window manager (plasma 6) ?
yast can now open i really don’t know how, I wiped out “selinux” at grub kernel parameters…
don’t give a f*** about that stuff
but now I can’t start any session with init 5 (multi user and GUI)

[deano_ferrari]

This reads like you have more problems than just setting locale. For further clarification, is this a fresh Leap 16 installation or did you upgrade from an earlier release? If it’s a fresh install using the Agama installer, and did you select a desktop environment during installation? Also, when you say you can’t start a graphical session with init 5, what actually happens? Does a graphical login screen appear, do you get a black screen, or does it return to the console?

[dcurtisfra]

@soundlord:

Simply disabling SELinux by removing the “security=selinux selinux=1” parameters from the GRUB command line isn’t enough.
This reference may be of some help for you: <https://en.opensuse.org/SDB:AppArmor#Switching_from_SELinux_to_AppArmor_for_Leap_16.0_and_Tumbleweed>