• Leap-15.4 Yast fails to deploy boot code

    From bad sector@forgetski@INVALID.net to alt.os.linux.suse on Thu Jun 1 12:57:52 2023
    From Newsgroup: alt.os.linux.suse



    Execution of command "[["/usr/sbin/grub2-mkconfig", "-o", "/boot/grub2/grub.cfg"]]" failed.
    Exit code: 139
    Error output: Generating grub configuration file ...
    perl: warning: Setting locale failed.
    perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_CTYPE = "en_US.UTF-8",
    LC_TIME = "Default.UTF-8",
    LANG = "C"
    are supported and installed on your system.
    perl: warning: Falling back to the standard locale ("C").
    Found linux image: /boot/vmlinuz-5.14.21-150400.24.63-default
    Found initrd image: /boot/initrd-5.14.21-150400.24.63-default
    Found linux image: /boot/vmlinuz-5.14.21-150400.22-default
    Found initrd image: /boot/initrd-5.14.21-150400.22-default
    Found memtest image: /boot/memtest.bin
    Warning: os-prober will be executed to detect other bootable partitions.
    Its output will be used to detect bootable binaries on them and create
    new boot entries.
    Found Artix Linux (rolling) on /dev/sda1
    Found Devuan GNU/Linux 4 (chimaera) on /dev/sda2
    Found Slackware 15.0 x86_64 on /dev/sda3
    Found openSUSE Tumbleweed on /dev/sda5
    Found Ubuntu 22.04.2 LTS (22.04) on /dev/sda6
    Found MX 21.3 Wildflower (21.3) on /dev/sda7
    Found openSUSE Leap 15.5 Beta on /dev/sda8


    I have 'locale' citations from time to time in various failed tasks but
    this is the first time that booting is involved. First of all WTF does
    locale have to do with booting AT ALL? I normally set such prefs during install, for example North-America, keyboard US-english, Pangnirtung
    Canada, Zulu -5h time (Eastern with daylight saving). Then, how does
    "unset" get to be "supported" on a system? While on the topic, why does
    Yast check for software repos and for 'trust' for a boot setup? Useless foreign fluff should not be allowed at all within 50 miles of anything
    having to do with booting. KISS!






    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to alt.os.linux.suse on Thu Jun 1 23:15:34 2023
    From Newsgroup: alt.os.linux.suse

    On 2023-06-01 18:57, bad sector wrote:


    Execution of command "[["/usr/sbin/grub2-mkconfig", "-o", "/boot/grub2/grub.cfg"]]" failed.
    Exit code: 139
    Error output: Generating grub configuration file ...
    perl: warning: Setting locale failed.
    perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_CTYPE = "en_US.UTF-8",
    LC_TIME = "Default.UTF-8",
    LANG = "C"
    are supported and installed on your system.
    perl: warning: Falling back to the standard locale ("C").

    So, this is not the error that blocked your boot generation.

    Found linux image: /boot/vmlinuz-5.14.21-150400.24.63-default
    Found initrd image: /boot/initrd-5.14.21-150400.24.63-default
    Found linux image: /boot/vmlinuz-5.14.21-150400.22-default
    Found initrd image: /boot/initrd-5.14.21-150400.22-default
    Found memtest image: /boot/memtest.bin
    Warning: os-prober will be executed to detect other bootable partitions.
    Its output will be used to detect bootable binaries on them and create
    new boot entries.
    Found Artix Linux (rolling) on /dev/sda1
    Found Devuan GNU/Linux 4 (chimaera) on /dev/sda2
    Found Slackware 15.0 x86_64 on /dev/sda3
    Found openSUSE Tumbleweed on /dev/sda5
    Found Ubuntu 22.04.2 LTS (22.04) on /dev/sda6
    Found MX 21.3 Wildflower (21.3) on /dev/sda7
    Found openSUSE Leap 15.5 Beta on /dev/sda8


    I have 'locale' citations from time to time in various failed tasks but
    this is the first time that booting is involved. First of all WTF does locale have to do with booting AT ALL?

    Because initrd is not only the kernel modules, it contains a minimal but complete Linux system held in memory, with many files, used to
    initialize the system (after booting itself).


    I normally set such prefs during
    install, for example North-America, keyboard US-english, Pangnirtung
    Canada, Zulu -5h time (Eastern with daylight saving). Then, how does
    "unset" get to be "supported" on a system? While on the topic, why does
    Yast check for software repos and for 'trust' for a boot setup? Useless foreign fluff should not be allowed at all within 50 miles of anything having to do with booting. KISS!

    You would have to ask the developers.
    --
    Cheers, Carlos.

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From bad sector@forgetski@INVALID.net to alt.os.linux.suse on Thu Jun 1 19:50:42 2023
    From Newsgroup: alt.os.linux.suse

    On 6/1/23 17:15, Carlos E.R. wrote:
    On 2023-06-01 18:57, bad sector wrote:


    Execution of command "[["/usr/sbin/grub2-mkconfig", "-o",
    "/boot/grub2/grub.cfg"]]" failed.
    Exit code: 139
    Error output: Generating grub configuration file ...
    perl: warning: Setting locale failed.
    perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_CTYPE = "en_US.UTF-8",
    LC_TIME = "Default.UTF-8",
    LANG = "C"
    are supported and installed on your system.
    perl: warning: Falling back to the standard locale ("C").

    So, this is not the error that blocked your boot generation.

    It's the error message I got

    BTW the boot setup DID complete, I know that because the reason I had
    tried it with Leap-15.4 is that TW (the previous one tried) put only TW
    in the boot menu but after this run I had all the syustems in the menu.


    Found linux image: /boot/vmlinuz-5.14.21-150400.24.63-default
    Found initrd image: /boot/initrd-5.14.21-150400.24.63-default
    Found linux image: /boot/vmlinuz-5.14.21-150400.22-default
    Found initrd image: /boot/initrd-5.14.21-150400.22-default
    Found memtest image: /boot/memtest.bin
    Warning: os-prober will be executed to detect other bootable partitions.
    Its output will be used to detect bootable binaries on them and create
    new boot entries.
    Found Artix Linux (rolling) on /dev/sda1
    Found Devuan GNU/Linux 4 (chimaera) on /dev/sda2
    Found Slackware 15.0 x86_64 on /dev/sda3
    Found openSUSE Tumbleweed on /dev/sda5
    Found Ubuntu 22.04.2 LTS (22.04) on /dev/sda6
    Found MX 21.3 Wildflower (21.3) on /dev/sda7
    Found openSUSE Leap 15.5 Beta on /dev/sda8


    I have 'locale' citations from time to time in various failed tasks
    but this is the first time that booting is involved. First of all WTF
    does locale have to do with booting AT ALL?

    Because initrd is not only the kernel modules, it contains a minimal but complete Linux system held in memory, with many files, used to
    initialize the system (after booting itself).


    I normally set such prefs during install, for example North-America,
    keyboard US-english, Pangnirtung Canada, Zulu -5h time (Eastern with
    daylight saving). Then, how does "unset" get to be "supported" on a
    system? While on the topic, why does Yast check for software repos and
    for 'trust' for a boot setup? Useless foreign fluff should not be
    allowed at all within 50 miles of anything having to do with booting.
    KISS!

    You would have to ask the developers.


    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to alt.os.linux.suse on Fri Jun 2 12:09:25 2023
    From Newsgroup: alt.os.linux.suse

    On 2023-06-02 01:50, bad sector wrote:
    On 6/1/23 17:15, Carlos E.R. wrote:
    On 2023-06-01 18:57, bad sector wrote:


    Execution of command "[["/usr/sbin/grub2-mkconfig", "-o",
    "/boot/grub2/grub.cfg"]]" failed.
    Exit code: 139
    Error output: Generating grub configuration file ...
    perl: warning: Setting locale failed.
    perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_CTYPE = "en_US.UTF-8",
    LC_TIME = "Default.UTF-8",
    LANG = "C"
    are supported and installed on your system.
    perl: warning: Falling back to the standard locale ("C").

    So, this is not the error that blocked your boot generation.

    It's the error message I got

    BTW the boot setup DID complete, I know that because the reason I had
    tried it with Leap-15.4 is that TW (the previous one tried) put only TW
    in the boot menu but after this run I had all the syustems in the menu.

    You can tell YaST to put only boot for the running system and ignore the
    rest.


    Or, you could set up a locale.
    --
    Cheers, Carlos.

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From bad sector@forgetski@INVALID.net to alt.os.linux.suse on Fri Jun 2 16:48:10 2023
    From Newsgroup: alt.os.linux.suse

    On 6/2/23 06:09, Carlos E.R. wrote:
    On 2023-06-02 01:50, bad sector wrote:
    On 6/1/23 17:15, Carlos E.R. wrote:
    On 2023-06-01 18:57, bad sector wrote:


    Execution of command "[["/usr/sbin/grub2-mkconfig", "-o",
    "/boot/grub2/grub.cfg"]]" failed.
    Exit code: 139
    Error output: Generating grub configuration file ...
    perl: warning: Setting locale failed.
    perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_CTYPE = "en_US.UTF-8",
    LC_TIME = "Default.UTF-8",
    LANG = "C"
    are supported and installed on your system.
    perl: warning: Falling back to the standard locale ("C").

    So, this is not the error that blocked your boot generation.

    It's the error message I got

    BTW the boot setup DID complete, I know that because the reason I had
    tried it with Leap-15.4 is that TW (the previous one tried) put only
    TW in the boot menu but after this run I had all the syustems in the
    menu.

    You can tell YaST to put only boot for the running system and ignore the rest.

    Leap does some of what I want done, it's TW that doesn't because it
    excludes other systems even though Probe-Other-OS'es' is checked. What
    Leap does NOT seem to be doing is terminating the task with a proper completion message but pops an error message instead.


    Or, you could set up a locale.

    Why? I had made all preferences choices at the time of installation,
    isn't that sufficient?


    BTW i just installed gcc-locale and the repeated grub run completed with
    no error messages. No idea how come.


    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to alt.os.linux.suse on Sat Jun 3 12:36:26 2023
    From Newsgroup: alt.os.linux.suse

    On 2023-06-02 22:48, bad sector wrote:
    On 6/2/23 06:09, Carlos E.R. wrote:
    On 2023-06-02 01:50, bad sector wrote:
    On 6/1/23 17:15, Carlos E.R. wrote:
    On 2023-06-01 18:57, bad sector wrote:


    Execution of command "[["/usr/sbin/grub2-mkconfig", "-o",
    "/boot/grub2/grub.cfg"]]" failed.
    Exit code: 139
    Error output: Generating grub configuration file ...
    perl: warning: Setting locale failed.
    perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_CTYPE = "en_US.UTF-8",
    LC_TIME = "Default.UTF-8",
    LANG = "C"
    are supported and installed on your system.
    perl: warning: Falling back to the standard locale ("C").

    So, this is not the error that blocked your boot generation.

    It's the error message I got

    BTW the boot setup DID complete, I know that because the reason I had
    tried it with Leap-15.4 is that TW (the previous one tried) put only
    TW in the boot menu but after this run I had all the syustems in the
    menu.

    You can tell YaST to put only boot for the running system and ignore
    the rest.

    Leap does some of what I want done, it's TW that doesn't because it
    excludes other systems even though Probe-Other-OS'es' is checked. What
    Leap does NOT seem to be doing is terminating the task with a proper completion message but pops an error message instead.


    Or, you could set up a locale.

    Why?-a I had made all preferences choices at the time of installation,
    isn't that sufficient?

    Apparently Mr root doesn't have a locale.


    BTW i just installed gcc-locale and the repeated grub run completed with
    no error messages. No idea how come.

    Ah, then the problem was the missing package.

    Did you install with "no recommends", perhaps?
    --
    Cheers, Carlos.

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From bad sector@forgetski@INVALID.net to alt.os.linux.suse on Sat Jun 3 18:37:47 2023
    From Newsgroup: alt.os.linux.suse

    On 6/3/23 06:36, Carlos E.R. wrote:
    On 2023-06-02 22:48, bad sector wrote:
    On 6/2/23 06:09, Carlos E.R. wrote:
    On 2023-06-02 01:50, bad sector wrote:
    On 6/1/23 17:15, Carlos E.R. wrote:
    On 2023-06-01 18:57, bad sector wrote:


    Execution of command "[["/usr/sbin/grub2-mkconfig", "-o",
    "/boot/grub2/grub.cfg"]]" failed.
    Exit code: 139
    Error output: Generating grub configuration file ...
    perl: warning: Setting locale failed.
    perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_CTYPE = "en_US.UTF-8",
    LC_TIME = "Default.UTF-8",
    LANG = "C"
    are supported and installed on your system.
    perl: warning: Falling back to the standard locale ("C").

    So, this is not the error that blocked your boot generation.

    It's the error message I got

    BTW the boot setup DID complete, I know that because the reason I
    had tried it with Leap-15.4 is that TW (the previous one tried) put
    only TW in the boot menu but after this run I had all the syustems
    in the menu.

    You can tell YaST to put only boot for the running system and ignore
    the rest.

    Leap does some of what I want done, it's TW that doesn't because it
    excludes other systems even though Probe-Other-OS'es' is checked. What
    Leap does NOT seem to be doing is terminating the task with a proper
    completion message but pops an error message instead.


    Or, you could set up a locale.

    Why?-a I had made all preferences choices at the time of installation,
    isn't that sufficient?

    Apparently Mr root doesn't have a locale.

    but of course (re) installing gcc-locale would give mr. root a locale?


    BTW i just installed gcc-locale and the repeated grub run completed
    with no error messages. No idea how come.

    Ah, then the problem was the missing package.

    Did you install with "no recommends", perhaps?

    Never do that, but since about the first Leap-15 I have been upgrading
    instead of freshies (due to the obviously unacceptaple setup and tweak
    load). I didn't uninstall gcc-locale either so what uninstalled it or
    how come there was no problem with grub runs before?


    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to alt.os.linux.suse on Sun Jun 4 04:24:08 2023
    From Newsgroup: alt.os.linux.suse

    On 2023-06-04 00:37, bad sector wrote:
    On 6/3/23 06:36, Carlos E.R. wrote:
    On 2023-06-02 22:48, bad sector wrote:
    On 6/2/23 06:09, Carlos E.R. wrote:
    On 2023-06-02 01:50, bad sector wrote:
    On 6/1/23 17:15, Carlos E.R. wrote:
    On 2023-06-01 18:57, bad sector wrote:


    Execution of command "[["/usr/sbin/grub2-mkconfig", "-o",
    "/boot/grub2/grub.cfg"]]" failed.
    Exit code: 139
    Error output: Generating grub configuration file ...
    perl: warning: Setting locale failed.
    perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_CTYPE = "en_US.UTF-8",
    LC_TIME = "Default.UTF-8",
    LANG = "C"
    are supported and installed on your system.
    perl: warning: Falling back to the standard locale ("C").

    So, this is not the error that blocked your boot generation.

    It's the error message I got

    BTW the boot setup DID complete, I know that because the reason I
    had tried it with Leap-15.4 is that TW (the previous one tried) put >>>>> only TW in the boot menu but after this run I had all the syustems
    in the menu.

    You can tell YaST to put only boot for the running system and ignore
    the rest.

    Leap does some of what I want done, it's TW that doesn't because it
    excludes other systems even though Probe-Other-OS'es' is checked.
    What Leap does NOT seem to be doing is terminating the task with a
    proper completion message but pops an error message instead.


    Or, you could set up a locale.

    Why?-a I had made all preferences choices at the time of installation,
    isn't that sufficient?

    Apparently Mr root doesn't have a locale.

    but of course (re) installing gcc-locale would give mr. root a locale?

    Maybe.


    Telcontar:~ # locale
    LANG=POSIX
    LC_CTYPE=en_US.UTF-8
    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=
    Telcontar:~ #




    BTW i just installed gcc-locale and the repeated grub run completed
    with no error messages. No idea how come.

    Ah, then the problem was the missing package.

    Did you install with "no recommends", perhaps?

    Never do that, but since about the first Leap-15 I have been upgrading instead of freshies (due to the obviously unacceptaple setup and tweak load). I didn't uninstall gcc-locale either so what uninstalled it or
    how come there was no problem with grub runs before?


    --
    Cheers, Carlos.

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From bad sector@forgetski@_INVALID.net to alt.os.linux.suse on Sat Jun 3 23:16:34 2023
    From Newsgroup: alt.os.linux.suse

    On 6/3/23 22:24, Carlos E.R. wrote:
    On 2023-06-04 00:37, bad sector wrote:
    On 6/3/23 06:36, Carlos E.R. wrote:
    On 2023-06-02 22:48, bad sector wrote:
    On 6/2/23 06:09, Carlos E.R. wrote:
    On 2023-06-02 01:50, bad sector wrote:
    On 6/1/23 17:15, Carlos E.R. wrote:
    On 2023-06-01 18:57, bad sector wrote:


    Execution of command "[["/usr/sbin/grub2-mkconfig", "-o",
    "/boot/grub2/grub.cfg"]]" failed.
    Exit code: 139
    Error output: Generating grub configuration file ...
    perl: warning: Setting locale failed.
    perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_CTYPE = "en_US.UTF-8",
    LC_TIME = "Default.UTF-8",
    LANG = "C"
    are supported and installed on your system.
    perl: warning: Falling back to the standard locale ("C").

    So, this is not the error that blocked your boot generation.

    It's the error message I got

    BTW the boot setup DID complete, I know that because the reason I >>>>>> had tried it with Leap-15.4 is that TW (the previous one tried)
    put only TW in the boot menu but after this run I had all the
    syustems in the menu.

    You can tell YaST to put only boot for the running system and
    ignore the rest.

    Leap does some of what I want done, it's TW that doesn't because it
    excludes other systems even though Probe-Other-OS'es' is checked.
    What Leap does NOT seem to be doing is terminating the task with a
    proper completion message but pops an error message instead.


    Or, you could set up a locale.

    Why?-a I had made all preferences choices at the time of
    installation, isn't that sufficient?

    Apparently Mr root doesn't have a locale.

    but of course (re) installing gcc-locale would give mr. root a locale?

    Maybe.


    Telcontar:~ # locale
    LANG=POSIX
    LC_CTYPE=en_US.UTF-8
    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=

    # locale
    locale: Cannot set LC_ALL to default locale: No such file or directory LANG=en_US.UTF-8
    LC_CTYPE="en_US.UTF-8"
    LC_NUMERIC="en_US.UTF-8"
    LC_TIME=Default.UTF-8
    LC_COLLATE="en_US.UTF-8"
    LC_MONETARY="en_US.UTF-8"
    LC_MESSAGES="en_US.UTF-8"
    LC_PAPER="en_US.UTF-8"
    LC_NAME="en_US.UTF-8"
    LC_ADDRESS="en_US.UTF-8"
    LC_TELEPHONE="en_US.UTF-8"
    LC_MEASUREMENT="en_US.UTF-8"
    LC_IDENTIFICATION="en_US.UTF-8"
    LC_ALL=
    # su
    Password:
    # locale
    locale: Cannot set LC_ALL to default locale: No such file or directory LANG=en_US.UTF-8
    LC_CTYPE="en_US.UTF-8"
    LC_NUMERIC="en_US.UTF-8"
    LC_TIME=Default.UTF-8
    LC_COLLATE="en_US.UTF-8"
    LC_MONETARY="en_US.UTF-8"
    LC_MESSAGES="en_US.UTF-8"
    LC_PAPER="en_US.UTF-8"
    LC_NAME="en_US.UTF-8"
    LC_ADDRESS="en_US.UTF-8"
    LC_TELEPHONE="en_US.UTF-8"
    LC_MEASUREMENT="en_US.UTF-8"
    LC_IDENTIFICATION="en_US.UTF-8"
    LC_ALL=




    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to alt.os.linux.suse on Sun Jun 4 11:33:49 2023
    From Newsgroup: alt.os.linux.suse

    On 2023-06-04 05:16, bad sector wrote:
    On 6/3/23 22:24, Carlos E.R. wrote:
    On 2023-06-04 00:37, bad sector wrote:


    Or, you could set up a locale.

    Why?-a I had made all preferences choices at the time of
    installation, isn't that sufficient?

    Apparently Mr root doesn't have a locale.

    but of course (re) installing gcc-locale would give mr. root a locale?

    Maybe.


    Telcontar:~ # locale
    LANG=POSIX
    LC_CTYPE=en_US.UTF-8
    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=

    # locale
    locale: Cannot set LC_ALL to default locale: No such file or directory LANG=en_US.UTF-8

    Does /usr/lib/locale/en_US.UTF-8 exist?

    It should probably be "en_US.utf8"

    LC_CTYPE="en_US.UTF-8"
    LC_NUMERIC="en_US.UTF-8"
    LC_TIME=Default.UTF-8
    LC_COLLATE="en_US.UTF-8"
    LC_MONETARY="en_US.UTF-8"
    LC_MESSAGES="en_US.UTF-8"
    LC_PAPER="en_US.UTF-8"
    LC_NAME="en_US.UTF-8"
    LC_ADDRESS="en_US.UTF-8"
    LC_TELEPHONE="en_US.UTF-8"
    LC_MEASUREMENT="en_US.UTF-8"
    LC_IDENTIFICATION="en_US.UTF-8"
    LC_ALL=
    --
    Cheers, Carlos.

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From bad sector@forgetski@invalid.net to alt.os.linux.suse on Sun Jun 4 06:44:26 2023
    From Newsgroup: alt.os.linux.suse

    On 6/4/23 5:33 AM, Carlos E.R. wrote:
    On 2023-06-04 05:16, bad sector wrote:
    On 6/3/23 22:24, Carlos E.R. wrote:
    On 2023-06-04 00:37, bad sector wrote:


    Or, you could set up a locale.

    Why?-a I had made all preferences choices at the time of
    installation, isn't that sufficient?

    Apparently Mr root doesn't have a locale.

    but of course (re) installing gcc-locale would give mr. root a locale?

    Maybe.


    Telcontar:~ # locale
    LANG=POSIX
    LC_CTYPE=en_US.UTF-8
    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=

    # locale
    locale: Cannot set LC_ALL to default locale: No such file or directory
    LANG=en_US.UTF-8

    Does /usr/lib/locale/en_US.UTF-8 exist?

    It should probably be "en_US.utf8"

    it is

    /usr/lib/locale/en_US.utf8


    I also have what appears to be a balooning number of issues with
    Leap-15.4 so with only days to go 15.5 I think I will just do an
    upgrade, worst case scenario a freshie.

    T-Bird stopped sending yesterday, messages vanish
    Previously installed Pan2 nowhere to be found
    Yast Software Managment fails to launch
    ...and on and on



    LC_CTYPE="en_US.UTF-8"
    LC_NUMERIC="en_US.UTF-8"
    LC_TIME=Default.UTF-8
    LC_COLLATE="en_US.UTF-8"
    LC_MONETARY="en_US.UTF-8"
    LC_MESSAGES="en_US.UTF-8"
    LC_PAPER="en_US.UTF-8"
    LC_NAME="en_US.UTF-8"
    LC_ADDRESS="en_US.UTF-8"
    LC_TELEPHONE="en_US.UTF-8"
    LC_MEASUREMENT="en_US.UTF-8"
    LC_IDENTIFICATION="en_US.UTF-8"
    LC_ALL=


    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to alt.os.linux.suse on Sun Jun 4 20:07:09 2023
    From Newsgroup: alt.os.linux.suse

    On 2023-06-04 12:44, bad sector wrote:
    On 6/4/23 5:33 AM, Carlos E.R. wrote:
    On 2023-06-04 05:16, bad sector wrote:
    On 6/3/23 22:24, Carlos E.R. wrote:
    On 2023-06-04 00:37, bad sector wrote:


    Or, you could set up a locale.

    Why?-a I had made all preferences choices at the time of
    installation, isn't that sufficient?

    Apparently Mr root doesn't have a locale.

    but of course (re) installing gcc-locale would give mr. root a locale? >>>>
    Maybe.


    Telcontar:~ # locale
    LANG=POSIX
    LC_CTYPE=en_US.UTF-8
    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=

    # locale
    locale: Cannot set LC_ALL to default locale: No such file or directory
    LANG=en_US.UTF-8

    Does /usr/lib/locale/en_US.UTF-8 exist?

    It should probably be "en_US.utf8"

    it is

    /usr/lib/locale/en_US.utf8


    I also have what appears to be a balooning number of issues with
    Leap-15.4 so with only days to go 15.5 I think I will just do an
    upgrade, worst case scenario a freshie.

    -a T-Bird stopped sending yesterday, messages vanish
    -a Previously installed Pan2 nowhere to be found
    -a Yast Software Managment fails to launch
    -a ...and on and on

    I have not a single problem.
    --
    Cheers, Carlos.

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From bad sector@forgetski@INVALID.net to alt.os.linux.suse on Sun Jun 4 17:21:14 2023
    From Newsgroup: alt.os.linux.suse

    On 6/4/23 14:07, Carlos E.R. wrote:
    On 2023-06-04 12:44, bad sector wrote:

    Does /usr/lib/locale/en_US.UTF-8 exist?

    It should probably be "en_US.utf8"

    it is

    /usr/lib/locale/en_US.utf8


    I also have what appears to be a balooning number of issues with
    Leap-15.4 so with only days to go 15.5 I think I will just do an
    upgrade, worst case scenario a freshie.

    -a-a T-Bird stopped sending yesterday, messages vanish
    -a-a Previously installed Pan2 nowhere to be found
    -a-a Yast Software Managment fails to launch
    -a-a ...and on and on

    I have not a single problem.


    sounds like my holier-than-thou wife

    I'm the only one that screws up all the time, to the point of spreading
    butter on a slice of bread the wrong way |:-|







    --- Synchronet 3.21d-Linux NewsLink 1.2