• =?UTF-8?B?wqEgw5cgIOKBiyAgXiDCuiDCpg==?= in filenames

    From bad sector@forgetski@invalid.net to alt.os.linux.suse on Sun Jul 16 03:00:33 2023
    From Newsgroup: alt.os.linux.suse


    I was using such characters to name guitar chord
    diagrams but since some upgrade or config change I
    can no longer save files with these in their name.
    Existing files still display OK in dolphin but no
    new ones can be saved. Where did I go wrong (this
    worked before and I have tons of such files, still
    works in Artix).

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to alt.os.linux.suse on Sun Jul 16 13:30:41 2023
    From Newsgroup: alt.os.linux.suse

    On 2023-07-16 05:00, bad sector wrote:

    I was using such characters to name guitar chord
    diagrams but since some upgrade or config change I
    can no longer save files with these in their name.

    Using what software?

    Existing files still display OK in dolphin but no
    new ones can be saved. Where did I go wrong (this
    worked before and I have tons of such files, still
    works in Artix).


    And what openSUSE release are you using?
    --
    Cheers, Carlos.

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From bad sector@forgetski@_INVALID.net to alt.os.linux.suse on Sun Jul 16 08:10:31 2023
    From Newsgroup: alt.os.linux.suse

    On 7/16/23 07:30, Carlos E.R. wrote:
    On 2023-07-16 05:00, bad sector wrote:

    I was using such characters to name guitar chord
    diagrams but since some upgrade or config change I
    can no longer save files with these in their name.

    Using what software?

    Gimp, and it's in Gimp that I get the first hint like:

    "Execution error for procedure
    'gimp-image-set-filename':
    Invalid byte sequence in conversion input."

    Another possibly UNRELATED errrr (don't remember
    the conditiion but not in Suse) message is:

    "System locale charset is ANSI_X3.4-1968
    Your system's locale charset (i.e. the charset
    used to encode filenames) is set to ANSI_X3.4-1968.
    It is highly unlikely that this has been done
    intentionally. Most likely the locale is not
    set at all. An invalid setting will result in
    problems when creating data projects.
    Solution: To properly set the locale charset
    make sure the LC_* environment variables are set.
    Normally the distribution setup tools take care
    of this."



    Existing files still display OK in dolphin but no
    new ones can be saved. Where did I go wrong (this
    worked before and I have tons of such files, still
    works in Artix).


    And what openSUSE release are you using?

    Only Leap-15.5 & TW seem to be affected

    The "^" up-arrow, circumflex or caret is not problemantic.
    The BAD characters are -i |u rUi -| -a


    At first I thought it might be a "locale" issue but a
    check of my distros coughed up the following

    Artix no filename issue charmap="ANSI_X3.4-1968"
    Devuan no filename issue charmap="UTF-8"
    Slackware no filename issue charmap="UTF-8"
    Suse-Leap-15.5 BAD charmap="UTF-8"
    Suse TW BAD charmap="UTF-8"
    Ubuntu-Studio no filename issue charmap="UTF-8"
    AvLinux no filename issue charmap="ANSI_X3.4-1968"

    So it don't seem to be a charmap issue.

    BTW while kicking this around, in all cases except
    Devuan & Slackware, I noticed one or more of the
    following error messages in response to the
    "locale -k LC_CTYPE" comand:

    locale: Cannot set LC_CTYPE to default locale:
    No such file or directory

    locale: Cannot set LC_MESSAGES to default locale:
    No such file or directory

    locale: Cannot set LC_ALL to default locale:
    No such file or directory

    Exactly WHAT does not exist?


    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to alt.os.linux.suse on Sun Jul 16 14:51:49 2023
    From Newsgroup: alt.os.linux.suse

    On 2023-07-16 14:10, bad sector wrote:
    On 7/16/23 07:30, Carlos E.R. wrote:
    On 2023-07-16 05:00, bad sector wrote:

    I was using such characters to name guitar chord
    diagrams but since some upgrade or config change I
    can no longer save files with these in their name.

    Using what software?

    Gimp, and it's in Gimp that I get the first hint like:

    "Execution error for procedure
    'gimp-image-set-filename':
    Invalid byte sequence in conversion input."

    I just created a file named "-i |u rUi -| -a.xcf" in gimp, on Leap 15.5.


    Another possibly UNRELATED errrr (don't remember
    the conditiion but not in Suse) message is:

    "System locale charset is ANSI_X3.4-1968
    Your system's locale charset (i.e. the charset
    used to encode filenames) is set to ANSI_X3.4-1968.
    It is highly unlikely that this has been done
    intentionally. Most likely the locale is not
    set at all. An invalid setting will result in
    problems when creating data projects.
    Solution: To properly set the locale charset
    make sure the LC_* environment variables are set.
    Normally the distribution setup tools take care
    of this."



    Existing files still display OK in dolphin but no
    new ones can be saved. Where did I go wrong (this
    worked before and I have tons of such files, still
    works in Artix).


    And what openSUSE release are you using?

    Only Leap-15.5 & TW seem to be affected

    The "^" up-arrow, circumflex or caret is not problemantic.
    The BAD characters are-a -i |u-a rUi-a -| -a


    At first I thought it might be a "locale" issue but a
    check of my distros coughed up the following

    Artix-a-a-a-a-a-a-a-a-a-a no filename issue-a charmap="ANSI_X3.4-1968" Devuan-a-a-a-a-a-a-a-a-a no filename issue-a charmap="UTF-8" Slackware-a-a-a-a-a-a no filename issue-a charmap="UTF-8"
    Suse-Leap-15.5-a BAD-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a charmap="UTF-8"
    Suse TW-a-a-a-a-a-a-a-a BAD-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a charmap="UTF-8" Ubuntu-Studio-a-a no filename issue-a charmap="UTF-8"
    AvLinux-a-a-a-a-a-a-a-a no filename issue-a charmap="ANSI_X3.4-1968"

    So it don't seem to be a charmap issue.

    BTW while kicking this around, in all cases except
    Devuan & Slackware, I noticed one or more of the
    following error messages in response to the
    "locale -k LC_CTYPE" comand:

    locale: Cannot set LC_CTYPE to default locale:
    No such file or directory


    -k, --keyword-name

    For each keyword whose value is being displayed,
    include also the name of that keyword, so that the output has the
    format:

    keyword="value"



    locale: Cannot set LC_MESSAGES to default locale:
    No such file or directory

    locale: Cannot set LC_ALL to default locale:
    No such file or directory

    Exactly WHAT does not exist?

    Your locale.

    In a terminal as that user, just do "locale" and paste that here.
    --
    Cheers, Carlos.

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From bad sector@forgetski@invalid.net to alt.os.linux.suse on Sun Jul 16 16:26:47 2023
    From Newsgroup: alt.os.linux.suse



    On 7/16/23 08:51, Carlos E.R. wrote:
    On 2023-07-16 14:10, bad sector wrote:
    On 7/16/23 07:30, Carlos E.R. wrote:
    On 2023-07-16 05:00, bad sector wrote:

    I was using such characters to name guitar chord
    diagrams but since some upgrade or config change I
    can no longer save files with these in their name.

    Using what software?

    Gimp, and it's in Gimp that I get the first hint like:

    "Execution error for procedure
    'gimp-image-set-filename':
    Invalid byte sequence in conversion input."

    I just created a file named "-i |u rUi -| -a.xcf" in gimp, on Leap 15.5.


    Another possibly UNRELATED errrr (don't remember
    the conditiion but not in Suse) message is:

    "System locale charset is ANSI_X3.4-1968
    Your system's locale charset (i.e. the charset
    used to encode filenames) is set to ANSI_X3.4-1968.
    It is highly unlikely that this has been done
    intentionally. Most likely the locale is not
    set at all. An invalid setting will result in
    problems when creating data projects.
    Solution: To properly set the locale charset
    make sure the LC_* environment variables are set.
    Normally the distribution setup tools take care
    of this."



    Existing files still display OK in dolphin but no
    new ones can be saved. Where did I go wrong (this
    worked before and I have tons of such files, still
    works in Artix).


    And what openSUSE release are you using?

    Only Leap-15.5 & TW seem to be affected

    The "^" up-arrow, circumflex or caret is not problemantic.
    The BAD characters are -i |u rUi -| -a


    At first I thought it might be a "locale" issue but a
    check of my distros coughed up the following

    Artix no filename issue charmap="ANSI_X3.4-1968"
    Devuan no filename issue charmap="UTF-8"
    Slackware no filename issue charmap="UTF-8"
    Suse-Leap-15.5 BAD charmap="UTF-8"
    Suse TW BAD charmap="UTF-8"
    Ubuntu-Studio no filename issue charmap="UTF-8"
    AvLinux no filename issue charmap="ANSI_X3.4-1968"

    So it don't seem to be a charmap issue.

    BTW while kicking this around, in all cases except
    Devuan & Slackware, I noticed one or more of the
    following error messages in response to the
    "locale -k LC_CTYPE" comand:

    locale: Cannot set LC_CTYPE to default locale:
    No such file or directory


    -k, --keyword-name

    For each keyword whose value is being displayed,
    include also the name of that keyword, so that the output has the
    format:

    keyword="value"

    ???


    locale: Cannot set LC_MESSAGES to default locale:
    No such file or directory

    locale: Cannot set LC_ALL to default locale:
    No such file or directory

    Exactly WHAT does not exist?

    Your locale.

    You mean /etc/default/locale the file?


    In a terminal as that user, just do "locale" and paste that here.

    Leap-15.5
    ~ 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=

    There is NO /etc/default/locale filein either
    Leap-15.5 or TW, the only 2 problem systems. They
    use systemd, but so does Ubuntu-Studio and the
    file exists in all other systems including that one.

    Files like "A6rUi3_0409.png" can be copied/pasted
    in dolphin, it's Gimp-2.10.30 that throws a fit
    in Suse

    "Execution error for procedure
    'gimp-image-set-filename':
    Invalid byte sequence in conversion input."

    but not in Ubuntu (same Gimp version).

    It seems like gimp catches a problem that
    is not in gimp but is related to a missing
    default locale file






    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to alt.os.linux.suse on Sun Jul 16 22:00:38 2023
    From Newsgroup: alt.os.linux.suse

    On 2023-07-16 18:26, bad sector wrote:
    On 7/16/23 08:51, Carlos E.R. wrote:
    On 2023-07-16 14:10, bad sector wrote:
    On 7/16/23 07:30, Carlos E.R. wrote:
    On 2023-07-16 05:00, bad sector wrote:


    locale: Cannot set LC_MESSAGES to default locale:
    No such file or directory

    locale: Cannot set LC_ALL to default locale:
    No such file or directory

    Exactly WHAT does not exist?

    Your locale.

    You mean /etc/default/locale the file?

    No, the output of "locale".



    In a terminal as that user, just do "locale" and paste that here.

    Leap-15.5
    ~ 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=

    On 15.4:

    cer@Telcontar:~> locale
    LANG=en_US.UTF-8
    LC_CTYPE=en_US.UTF-8
    LC_NUMERIC=es_ES.utf8
    LC_TIME=en_DK.UTF-8
    LC_COLLATE=POSIX
    LC_MONETARY=es_ES.utf8
    LC_MESSAGES="en_US.UTF-8"
    LC_PAPER=es_ES.utf8
    LC_NAME=es_ES.utf8
    LC_ADDRESS="en_US.UTF-8"
    LC_TELEPHONE=es_ES.utf8
    LC_MEASUREMENT=es_ES.utf8
    LC_IDENTIFICATION="en_US.UTF-8"
    LC_ALL=
    cer@Telcontar:~>

    cer@Telcontar:~> locate en_US.UTF-8
    /usr/share/X11/locale/en_US.UTF-8
    /usr/share/X11/locale/en_US.UTF-8/Compose /usr/share/X11/locale/en_US.UTF-8/XI18N_OBJS /usr/share/X11/locale/en_US.UTF-8/XLC_LOCALE /usr/share/doc/packages/libX11/i18n/compose/en_US.UTF-8.xml
    cer@Telcontar:~>

    Same result in my 15.5 laptop.


    cer@Laicolasse:~> rpm -qf /usr/share/X11/locale/en_US.UTF-8 libX11-data-1.6.5-150000.3.30.1.noarch
    cer@Laicolasse:~> rpm -qf /usr/share/X11/locale/en_US.UTF-8/XI18N_OBJS libX11-data-1.6.5-150000.3.30.1.noarch
    cer@Laicolasse:~

    Do you have those files installed? If not, install that rpm.



    There is NO /etc/default/locale filein either

    Not needed. I don't have it. You will have "/etc/locale.conf"
    --
    Cheers, Carlos.

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From bad sector@forgetski@invalid.net to alt.os.linux.suse on Sun Jul 16 23:43:16 2023
    From Newsgroup: alt.os.linux.suse

    On Sun, 16 Jul 2023 22:00:38 +0200, Carlos E.R. wrote:

    On 2023-07-16 18:26, bad sector wrote:
    On 7/16/23 08:51, Carlos E.R. wrote:
    On 2023-07-16 14:10, bad sector wrote:
    On 7/16/23 07:30, Carlos E.R. wrote:
    On 2023-07-16 05:00, bad sector wrote:


    locale: Cannot set LC_MESSAGES to default locale:
    No such file or directory

    locale: Cannot set LC_ALL to default locale:
    No such file or directory

    Exactly WHAT does not exist?

    Your locale.

    You mean /etc/default/locale the file?

    No, the output of "locale".

    How can the output of locale be the topic of "no such
    file or directory"? This particular problem seems to be
    one of communications, we don't set nothing to a file,
    what we do is edit a file and save it (still conditional
    to me understanding what the error message means, which
    I don't).

    In this age of AI, automated translators, text composters,
    and multicultural multilingual whatnots it no longer suffices
    for communications to be understandable, they must be
    impossible not to understand and that doesn't just include
    error messages, it begins with them.


    On 15.4:

    cer@Telcontar:~> locale
    LANG=en_US.UTF-8
    LC_CTYPE=en_US.UTF-8
    LC_NUMERIC=es_ES.utf8
    LC_TIME=en_DK.UTF-8
    LC_COLLATE=POSIX
    LC_MONETARY=es_ES.utf8
    LC_MESSAGES="en_US.UTF-8"
    LC_PAPER=es_ES.utf8
    LC_NAME=es_ES.utf8
    LC_ADDRESS="en_US.UTF-8"
    LC_TELEPHONE=es_ES.utf8
    LC_MEASUREMENT=es_ES.utf8
    LC_IDENTIFICATION="en_US.UTF-8"
    LC_ALL=
    cer@Telcontar:~>

    cer@Telcontar:~> locate en_US.UTF-8
    /usr/share/X11/locale/en_US.UTF-8
    /usr/share/X11/locale/en_US.UTF-8/Compose /usr/share/X11/locale/en_US.UTF-8/XI18N_OBJS /usr/share/X11/locale/en_US.UTF-8/XLC_LOCALE /usr/share/doc/packages/libX11/i18n/compose/en_US.UTF-8.xml
    cer@Telcontar:~>

    Same result in my 15.5 laptop.


    cer@Laicolasse:~> rpm -qf /usr/share/X11/locale/en_US.UTF-8 libX11-data-1.6.5-150000.3.30.1.noarch
    cer@Laicolasse:~> rpm -qf /usr/share/X11/locale/en_US.UTF-8/XI18N_OBJS libX11-data-1.6.5-150000.3.30.1.noarch
    cer@Laicolasse:~

    Do you have those files installed? If not, install that rpm.


    same results on Leap-15.5
    (desktop, threw out my laptop, haven't replaced it and
    I've never been happier)



    There is NO /etc/default/locale filein either

    Not needed. I don't have it. You will have "/etc/locale.conf"

    same here, contains

    LANG=en_US.UTF-8
    LC_CTYPE=en_US.UTF-8


    So then why does locale whine about 'no such file or directory',
    is it because it don't know how to use 'find' or because suse
    is not following (the same) conventions?

    And, regardless of the above very pretty exercise in academe,
    I still don't see linkage between anything 'locale' and the
    file-naming issue causing problems but only in gimp and only
    in Suse :-(

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to alt.os.linux.suse on Mon Jul 17 02:44:07 2023
    From Newsgroup: alt.os.linux.suse

    On 2023-07-17 01:43, bad sector wrote:
    On Sun, 16 Jul 2023 22:00:38 +0200, Carlos E.R. wrote:
    On 2023-07-16 18:26, bad sector wrote:
    On 7/16/23 08:51, Carlos E.R. wrote:
    On 2023-07-16 14:10, bad sector wrote:
    On 7/16/23 07:30, Carlos E.R. wrote:
    On 2023-07-16 05:00, bad sector wrote:


    locale: Cannot set LC_MESSAGES to default locale:
    No such file or directory

    locale: Cannot set LC_ALL to default locale:
    No such file or directory

    Exactly WHAT does not exist?

    Your locale.

    You mean /etc/default/locale the file?

    No, the output of "locale".

    How can the output of locale be the topic of "no such
    file or directory"? This particular problem seems to be
    one of communications, we don't set nothing to a file,
    what we do is edit a file and save it (still conditional
    to me understanding what the error message means, which
    I don't).

    In this age of AI, automated translators, text composters,
    and multicultural multilingual whatnots it no longer suffices
    for communications to be understandable, they must be
    impossible not to understand and that doesn't just include
    error messages, it begins with them.

    Well, *unix is ancient technology.

    The error message means, AFAIK, that one or several of the files used
    for locale definitions are missing, for your chosen locale, which is
    what I have been trying to track in several posts.



    On 15.4:

    cer@Telcontar:~> locale
    LANG=en_US.UTF-8
    LC_CTYPE=en_US.UTF-8
    LC_NUMERIC=es_ES.utf8
    LC_TIME=en_DK.UTF-8
    LC_COLLATE=POSIX
    LC_MONETARY=es_ES.utf8
    LC_MESSAGES="en_US.UTF-8"
    LC_PAPER=es_ES.utf8
    LC_NAME=es_ES.utf8
    LC_ADDRESS="en_US.UTF-8"
    LC_TELEPHONE=es_ES.utf8
    LC_MEASUREMENT=es_ES.utf8
    LC_IDENTIFICATION="en_US.UTF-8"
    LC_ALL=
    cer@Telcontar:~>

    cer@Telcontar:~> locate en_US.UTF-8
    /usr/share/X11/locale/en_US.UTF-8
    /usr/share/X11/locale/en_US.UTF-8/Compose
    /usr/share/X11/locale/en_US.UTF-8/XI18N_OBJS
    /usr/share/X11/locale/en_US.UTF-8/XLC_LOCALE
    /usr/share/doc/packages/libX11/i18n/compose/en_US.UTF-8.xml
    cer@Telcontar:~>

    Same result in my 15.5 laptop.


    cer@Laicolasse:~> rpm -qf /usr/share/X11/locale/en_US.UTF-8
    libX11-data-1.6.5-150000.3.30.1.noarch
    cer@Laicolasse:~> rpm -qf /usr/share/X11/locale/en_US.UTF-8/XI18N_OBJS
    libX11-data-1.6.5-150000.3.30.1.noarch
    cer@Laicolasse:~

    Do you have those files installed? If not, install that rpm.


    same results on Leap-15.5
    (desktop, threw out my laptop, haven't replaced it and
    I've never been happier)



    There is NO /etc/default/locale filein either

    Not needed. I don't have it. You will have "/etc/locale.conf"

    same here, contains

    LANG=en_US.UTF-8
    LC_CTYPE=en_US.UTF-8


    So then why does locale whine about 'no such file or directory',
    is it because it don't know how to use 'find' or because suse
    is not following (the same) conventions?

    And, regardless of the above very pretty exercise in academe,
    I still don't see linkage between anything 'locale' and the
    file-naming issue causing problems but only in gimp and only
    in Suse :-(

    That you have related problems in several distros indicate that it is something you are doing.

    For example, what filesystem is the partition where you are saving your
    files?


    The LC_CTYPE category determines character handling rules governing the interpretation of sequences of bytes of text data characters (that is, single-byte versus multibyte characters), the classification of
    characters (for example, alpha, digit, and so on), and the behavior of character classes.

    Understanding locale environment variables - IBM
    IBM
    https://www.ibm.com rC| understand_locale_environ_var <https://www.ibm.com/docs/en/aix/7.1?topic=locales-understanding-locale-environment-variables>



    What is the difference between Lc_ctype and Lc_all?
    LC_CTYPE is an override to LANG, and overrides just the character set
    used. All other features (categories) of LANG are still used as set by
    LANG, e.g. LC_TELEPHONE. LC_ALL is a further override. It overrides both LC_CTYPE and all locale categories that were set by LANG to a given
    language and codeset.May 27, 2015

    Explain the effects of export LANG, LC_CTYPE, and LC_ALL
    Stack Overflow <https://stackoverflow.com/questions/30479607/explain-the-effects-of-export-lang-lc-ctype-and-lc-all>




    You had an error when doing "locale -k LC_CTYPE". I would try that
    command under strace or ltrace, to see what they do, what file it is
    exactly trying to find.


    Oh, and notice that Tumbleweed and Leap are very different beasts in
    these respects. I can offer no guidance on TW.
    --
    Cheers, Carlos.

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From bad sector@forgetski@invalid.net to alt.os.linux.suse on Mon Jul 17 01:33:07 2023
    From Newsgroup: alt.os.linux.suse

    On Mon, 17 Jul 2023 02:44:07 +0200, Carlos E.R. wrote:

    On 7/16/23 20:44, Carlos E.R. wrote:
    On 2023-07-17 01:43, bad sector wrote:
    On Sun, 16 Jul 2023 22:00:38 +0200, Carlos E.R. wrote:

    And, regardless of the above very pretty exercise in academe,
    I still don't see linkage between anything 'locale' and the
    file-naming issue causing problems but only in gimp and only
    in Suse :-(

    That you have related problems in several distros indicate that it is something you are doing.

    Possible but I generally accomplish all the same fuckups in all distros while only Leap and TW are problematic in this case


    For example, what filesystem is the partition where you are saving your files?

    ext4 is the ONLY fs I use ever since canning reiserfs

    The LC_CTYPE category determines character handling rules governing the interpretation of sequences of bytes of text data characters (that is, single-byte versus multibyte characters), the classification of
    characters (for example, alpha, digit, and so on), and the behavior of character classes.

    Understanding locale environment variables - IBM
    IBM
    https://www.ibm.com rC| understand_locale_environ_var <https://www.ibm.com/docs/en/aix/7.1?topic=locales-understanding-locale-environment-variables>



    What is the difference between Lc_ctype and Lc_all?
    LC_CTYPE is an override to LANG, and overrides just the character set
    used. All other features (categories) of LANG are still used as set by
    LANG, e.g. LC_TELEPHONE. LC_ALL is a further override. It overrides both LC_CTYPE and all locale categories that were set by LANG to a given
    language and codeset.May 27, 2015

    Explain the effects of export LANG, LC_CTYPE, and LC_ALL
    Stack Overflow <https://stackoverflow.com/questions/30479607/explain-the-effects-of-export-lang-lc-ctype-and-lc-all>




    You had an error when doing "locale -k LC_CTYPE". I would try that
    command under strace or ltrace, to see what they do, what file it is
    exactly trying to find.

    My first ever strace stunt, this is for developers and I'm not one, never will be:

    https://paste.opensuse.org/pastes/6dd828e4c956



    Oh, and notice that Tumbleweed and Leap are very different beasts in
    these respects.

    What I need to isolate first is WHY gimp is throwing fits, second why only in Leap & TW. I'm thinking 'filesystem' but the subject files are all on the same removable ext4 data partition accessed by essentially the same Gimp as installed on all 7 distros


    I can offer no guidance on TW.


    What you do offer is appreciated all the same :-)

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to alt.os.linux.suse on Mon Jul 17 15:01:06 2023
    From Newsgroup: alt.os.linux.suse

    On 2023-07-17 03:33, bad sector wrote:
    On Mon, 17 Jul 2023 02:44:07 +0200, Carlos E.R. wrote:
    On 7/16/23 20:44, Carlos E.R. wrote:
    On 2023-07-17 01:43, bad sector wrote:
    On Sun, 16 Jul 2023 22:00:38 +0200, Carlos E.R. wrote:

    And, regardless of the above very pretty exercise in academe,
    I still don't see linkage between anything 'locale' and the
    file-naming issue causing problems but only in gimp and only
    in Suse :-(

    That you have related problems in several distros indicate that it is
    something you are doing.

    Possible but I generally accomplish all the same fuckups in all distros while only Leap and TW are problematic in this case


    For example, what filesystem is the partition where you are saving your
    files?

    ext4 is the ONLY fs I use ever since canning reiserfs

    Ok, then no FAT.

    ...


    You had an error when doing "locale -k LC_CTYPE". I would try that
    command under strace or ltrace, to see what they do, what file it is
    exactly trying to find.

    My first ever strace stunt, this is for developers and I'm not one, never will be:

    https://paste.opensuse.org/pastes/6dd828e4c956

    It is easy to read :-)

    openat(AT_FDCWD, "/usr/lib/locale/en_US.UTF-8/LC_CTYPE",
    O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    file does not exist.

    openat(AT_FDCWD, "/usr/lib/locale/en_US.utf8/LC_CTYPE",
    O_RDONLY|O_CLOEXEC) = 3

    Tries another name, that does exist, and returns the handle.

    fstat(3, {st_mode=S_IFREG|0644, st_size=2940, ...}) = 0

    It queries the file...


    Here is the one that matters, starting at line 88:

    (I insert blank lines for clarity)



    openat(AT_FDCWD, "/usr/lib/locale/Default.UTF-8/LC_TIME",
    O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/Default.utf8/LC_TIME",
    O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/Default/LC_TIME", O_RDONLY|O_CLOEXEC)
    = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD,
    "/usr/share/locale-langpack/en_US.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY)
    = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/share/locale/en_US.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD,
    "/usr/share/locale-langpack/en_US.utf8/LC_MESSAGES/libc.mo", O_RDONLY) =
    -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/share/locale/en_US.utf8/LC_MESSAGES/libc.mo",
    O_RDONLY) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/share/locale-langpack/en_US/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/share/locale/en_US/LC_MESSAGES/libc.mo",
    O_RDONLY) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD,
    "/usr/share/locale-langpack/en.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) =
    -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/share/locale/en.UTF-8/LC_MESSAGES/libc.mo",
    O_RDONLY) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD,
    "/usr/share/locale-langpack/en.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/share/locale/en.utf8/LC_MESSAGES/libc.mo",
    O_RDONLY) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/share/locale-langpack/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/share/locale/en/LC_MESSAGES/libc.mo", O_RDONLY) =
    -1 ENOENT (No such file or directory)

    write(2, "locale: ", 8locale: ) = 8
    write(2, "Cannot set LC_ALL to default loc"..., 35Cannot set LC_ALL to
    default locale) = 35
    write(2, ": No such file or directory", 27: No such file or directory) = 27


    I can see that "/usr/share/locale/en_GB/LC_MESSAGES/libc.mo" does exist
    in my system, but not "/usr/share/locale/en/LC_MESSAGES/libc.mo". It is curious. But anyway, you know now what file it is missing.


    I will now try the same command on 15.5.

    [...]

    Ok, mine doesn't try to find "libc.mo". It does try "LC_MESSAGES"

    openat(AT_FDCWD, "/usr/lib/locale/en_US.UTF-8/LC_MESSAGES", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/en_US.utf8/LC_MESSAGES",
    O_RDONLY|O_CLOEXEC) = 3





    On yours, the first problem happens here:

    openat(AT_FDCWD, "/usr/lib/locale/en_US.UTF-8/LC_COLLATE",
    O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/en_US.utf8/LC_COLLATE",
    O_RDONLY|O_CLOEXEC) = 3

    fstat(3, {st_mode=S_IFREG|0644, st_size=2586930, ...}) = 0
    mmap(NULL, 2586930, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fa46d860000

    close(3) = 0

    openat(AT_FDCWD, "/usr/lib/locale/Default.UTF-8/LC_TIME",
    O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/Default.utf8/LC_TIME",
    O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/Default/LC_TIME", O_RDONLY|O_CLOEXEC)
    = -1 ENOENT (No such file or directory)


    On mine, the same section:


    openat(AT_FDCWD, "/usr/lib/locale/es_ES.utf8/LC_MONETARY",
    O_RDONLY|O_CLOEXEC) = 3

    fstat(3, {st_mode=S_IFREG|0644, st_size=294, ...}) = 0
    mmap(NULL, 294, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f97b2f8f000

    close(3) = 0

    openat(AT_FDCWD, "/usr/lib/locale/en_US.UTF-8/LC_COLLATE",
    O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/en_US.utf8/LC_COLLATE",
    O_RDONLY|O_CLOEXEC) = 3

    fstat(3, {st_mode=S_IFREG|0644, st_size=2586930, ...}) = 0
    mmap(NULL, 2586930, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f97b2ab2000

    close(3) = 0

    openat(AT_FDCWD, "/usr/lib/locale/en_DK.UTF-8/LC_TIME",
    O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/en_DK.utf8/LC_TIME",
    O_RDONLY|O_CLOEXEC) = 3

    fstat(3, {st_mode=S_IFREG|0644, st_size=3180, ...}) = 0

    mmap(NULL, 3180, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f97b2f8e000
    close(3) = 0



    Ah, ok, but I use a different time locale than you (en_DK.UTF-8). I'll
    try a different user.


    openat(AT_FDCWD, "/usr/lib/locale/en_US.UTF-8/LC_MONETARY", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/en_US.utf8/LC_MONETARY",
    O_RDONLY|O_CLOEXEC) = 3

    fstat(3, {st_mode=S_IFREG|0644, st_size=286, ...}) = 0

    mmap(NULL, 286, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7efff46b2000

    close(3) = 0

    openat(AT_FDCWD, "/usr/lib/locale/en_US.UTF-8/LC_COLLATE",
    O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/en_US.utf8/LC_COLLATE",
    O_RDONLY|O_CLOEXEC) = 3

    fstat(3, {st_mode=S_IFREG|0644, st_size=2586930, ...}) = 0

    mmap(NULL, 2586930, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7efff41d5000

    close(3) = 0

    openat(AT_FDCWD, "/usr/lib/locale/en_US.UTF-8/LC_TIME",
    O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/en_US.utf8/LC_TIME",
    O_RDONLY|O_CLOEXEC) = 3

    fstat(3, {st_mode=S_IFREG|0644, st_size=3284, ...}) = 0

    mmap(NULL, 3284, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7efff46b1000

    close(3) = 0

    openat(AT_FDCWD, "/usr/lib/locale/en_US.UTF-8/LC_NUMERIC",
    O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/en_US.utf8/LC_NUMERIC",
    O_RDONLY|O_CLOEXEC) = 3

    fstat(3, {st_mode=S_IFREG|0644, st_size=54, ...}) = 0

    mmap(NULL, 54, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7efff46b0000
    close(3) = 0


    Whereas yours do:

    openat(AT_FDCWD, "/usr/lib/locale/Default.UTF-8/LC_TIME",
    O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/Default.utf8/LC_TIME",
    O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/Default/LC_TIME", O_RDONLY|O_CLOEXEC)
    = -1 ENOENT (No such file or directory)



    Mine tries first the file "/usr/lib/locale/en_US.UTF-8/LC_TIME" which
    does not exist. Then it tries "/usr/lib/locale/en_US.utf8/LC_TIME",
    which in mine does exist.

    But yours is trying instead

    /usr/lib/locale/Default.UTF-8/LC_TIME
    /usr/lib/locale/Default.utf8/LC_TIME
    /usr/lib/locale/Default/LC_TIME

    which do not exist. Why is it trying those?


    When I asked you for your locale, you pasted this:

    Leap-15.5
    ~ 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=


    That's the origin of your problem. Why do you have that?
    Find that out, and change it to a proper one, and you should be Ok.
    --
    Cheers, Carlos.

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From bad sector@postit@invalid.org to alt.os.linux.suse on Mon Jul 17 16:23:08 2023
    From Newsgroup: alt.os.linux.suse

    On 7/17/23 09:01, Carlos E.R. wrote:
    On 2023-07-17 03:33, bad sector wrote:

    When I asked you for your locale, you pasted this:

    Leap-15.5
    ~ 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=


    That's the origin of your problem. Why do you have that?
    Find that out, and change it to a proper one, and you should be Ok.

    I see that, so I went with

    # export LC_TIME="en_US.UTF-8"
    # locale
    LANG=en_US.UTF-8
    LC_CTYPE="en_US.UTF-8"
    LC_NUMERIC="en_US.UTF-8"
    LC_TIME="en_US.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=

    At this point LC_ALL is NOT set, yet...

    # locale -k LC_TIME
    abday="Sun;Mon;Tue;Wed;Thu;Fri;Sat" day="Sunday;Monday;Tuesday;Wednesday;Thursday;Friday;Saturday" abmon="Jan;Feb;Mar;Apr;May;Jun;Jul;Aug;Sep;Oct;Nov;Dec" mon="January;February;March;April;May;June;July;August;September;October;November;December"
    am_pm="AM;PM"
    d_t_fmt="%a %d %b %Y %r %Z"
    d_fmt="%m/%d/%Y"
    t_fmt="%r"
    t_fmt_ampm="%I:%M:%S %p"
    era=
    era_year=""
    era_d_fmt=""
    alt_digits=
    era_d_t_fmt=""
    era_t_fmt=""
    time-era-num-entries=0
    time-era-entries="S"
    week-ndays=7
    week-1stday=19971130
    week-1stweek=1
    first_weekday=1
    first_workday=2
    cal_direction=1
    timezone=""
    date_fmt="%a %d %b %Y %r %Z"
    time-codeset="UTF-8" alt_mon="January;February;March;April;May;June;July;August;September;October;November;December"
    ab_alt_mon="Jan;Feb;Mar;Apr;May;Jun;Jul;Aug;Sep;Oct;Nov;Dec"

    It does NOT complain about LC_ALL no such file or directory. But if I
    reboot then it does. Anyway Gimps still throws a fit

    so I did

    # export LC_ALL="C"
    # locale
    LANG=en_US.UTF-8
    LC_CTYPE="C"
    LC_NUMERIC="C"
    LC_TIME="C"
    LC_COLLATE="C"
    LC_MONETARY="C"
    LC_MESSAGES="C"
    LC_PAPER="C"
    LC_NAME="C"
    LC_ADDRESS="C"
    LC_TELEPHONE="C"
    LC_MEASUREMENT="C"
    LC_IDENTIFICATION="C"
    LC_ALL=C

    # locale -k LC_TIME
    abday="Sun;Mon;Tue;Wed;Thu;Fri;Sat" day="Sunday;Monday;Tuesday;Wednesday;Thursday;Friday;Saturday" abmon="Jan;Feb;Mar;Apr;May;Jun;Jul;Aug;Sep;Oct;Nov;Dec" mon="January;February;March;April;May;June;July;August;September;October;November;December"
    am_pm="AM;PM"
    d_t_fmt="%a %b %e %H:%M:%S %Y"
    d_fmt="%m/%d/%y"
    t_fmt="%H:%M:%S"
    t_fmt_ampm="%I:%M:%S %p"
    era=
    era_year=""
    era_d_fmt=""
    alt_digits=
    era_d_t_fmt=""
    era_t_fmt=""
    time-era-num-entries=0
    time-era-entries=""
    week-ndays=7
    week-1stday=19971130
    week-1stweek=4
    first_weekday=1
    first_workday=2
    cal_direction=1
    timezone=""
    date_fmt="%a %b %e %H:%M:%S %Z %Y"
    time-codeset="ANSI_X3.4-1968" alt_mon="January;February;March;April;May;June;July;August;September;October;November;December"
    ab_alt_mon="Jan;Feb;Mar;Apr;May;Jun;Jul;Aug;Sep;Oct;Nov;Dec"


    Gimp STILL throws a fit

    What indication is there that this is a 'locale' issue at all? Some of my other distros have locale issues as well yet do not suffer from the gimp-
    fit.

    Interestingly, even in Leap/TW gimp DOES load a file such as
    "A#-|_0305.png" with no problem. It's when I go to export it that the hsit hits the fan, AND as maybe a hint of the underlying FUBAR the filename presented for possible edit becomes "A%23-|_0305.png".



    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to alt.os.linux.suse on Mon Jul 17 20:10:31 2023
    From Newsgroup: alt.os.linux.suse

    On 2023-07-17 18:23, bad sector wrote:
    On 7/17/23 09:01, Carlos E.R. wrote:
    On 2023-07-17 03:33, bad sector wrote:



    ...

    At this point LC_ALL is NOT set, yet...

    # locale -k LC_TIME
    abday="Sun;Mon;Tue;Wed;Thu;Fri;Sat" day="Sunday;Monday;Tuesday;Wednesday;Thursday;Friday;Saturday" abmon="Jan;Feb;Mar;Apr;May;Jun;Jul;Aug;Sep;Oct;Nov;Dec" mon="January;February;March;April;May;June;July;August;September;October;November;December"
    am_pm="AM;PM"
    d_t_fmt="%a %d %b %Y %r %Z"
    d_fmt="%m/%d/%Y"
    t_fmt="%r"
    t_fmt_ampm="%I:%M:%S %p"
    era=
    era_year=""
    era_d_fmt=""
    alt_digits=
    era_d_t_fmt=""
    era_t_fmt=""
    time-era-num-entries=0
    time-era-entries="S"
    week-ndays=7
    week-1stday=19971130
    week-1stweek=1
    first_weekday=1
    first_workday=2
    cal_direction=1
    timezone=""
    date_fmt="%a %d %b %Y %r %Z"
    time-codeset="UTF-8" alt_mon="January;February;March;April;May;June;July;August;September;October;November;December"
    ab_alt_mon="Jan;Feb;Mar;Apr;May;Jun;Jul;Aug;Sep;Oct;Nov;Dec"

    It does NOT complain about LC_ALL no such file or directory. But if I
    reboot then it does. Anyway Gimps still throws a fit

    so I did

    Edit (or create) file .i18n. Mine is:

    # used by /etc/profile.d/lang.sh
    #CER - if it doesn't work edit /etc/profile.d/lang.sh, see Bugzilla 567324 LC_TIME=en_DK.UTF-8
    LC_MONETARY=es_ES.utf8
    LC_NUMERIC=es_ES.utf8
    LC_PAPER=es_ES.utf8
    LC_TELEPHONE=es_ES.utf8
    LC_MEASUREMENT=es_ES.utf8
    LC_NAME=es_ES.utf8

    You need to at least log out and in.


    # export LC_ALL="C"
    # locale
    LANG=en_US.UTF-8
    LC_CTYPE="C"
    LC_NUMERIC="C"
    LC_TIME="C"
    LC_COLLATE="C"
    LC_MONETARY="C"
    LC_MESSAGES="C"
    LC_PAPER="C"
    LC_NAME="C"
    LC_ADDRESS="C"
    LC_TELEPHONE="C"
    LC_MEASUREMENT="C"
    LC_IDENTIFICATION="C"
    LC_ALL=C

    # locale -k LC_TIME
    abday="Sun;Mon;Tue;Wed;Thu;Fri;Sat" day="Sunday;Monday;Tuesday;Wednesday;Thursday;Friday;Saturday"

    ...



    Gimp STILL throws a fit

    What indication is there that this is a 'locale' issue at all? Some of my other distros have locale issues as well yet do not suffer from the gimp- fit.

    Interestingly, even in Leap/TW gimp DOES load a file such as
    "A#-|_0305.png" with no problem. It's when I go to export it that the hsit hits the fan, AND as maybe a hint of the underlying FUBAR the filename presented for possible edit becomes "A%23-|_0305.png".

    I don't know why gimp has trouble, but you know the drill: strace.

    strace --output=filename gimp


    and find out what file it doesn't find.


    Huh, I don't know if gimp can work if the locale is "C". It needs utf-8.
    --
    Cheers, Carlos.

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Don Spam's Reckless Son@hyperspace.flyover@vogon.gov.invalid to alt.os.linux.suse on Mon Jul 17 21:25:06 2023
    From Newsgroup: alt.os.linux.suse

    Carlos E.R. wrote:
    On 2023-07-17 03:33, bad sector wrote:
    On Mon, 17 Jul 2023 02:44:07 +0200, Carlos E.R. wrote:
    On 7/16/23 20:44, Carlos E.R. wrote:
    On 2023-07-17 01:43, bad sector wrote:
    On Sun, 16 Jul 2023 22:00:38 +0200, Carlos E.R. wrote:

    And, regardless of the above very pretty exercise in academe,
    I still don't see linkage between anything 'locale' and the
    file-naming issue causing problems but only in gimp and only
    in Suse :-(

    That you have related problems in several distros indicate that it is
    something you are doing.

    Possible but I generally accomplish all the same fuckups in all
    distros while only Leap and TW are problematic in this case


    For example, what filesystem is the partition where you are saving your
    files?

    ext4 is the ONLY fs I use ever since canning reiserfs

    Ok, then no FAT.

    ...


    You had an error when doing "locale -k LC_CTYPE". I would try that
    command under strace or ltrace, to see what they do, what file it is
    exactly trying to find.

    My first ever strace stunt, this is for developers and I'm not one,
    never will be:

    https://paste.opensuse.org/pastes/6dd828e4c956

    It is easy to read :-)

    openat(AT_FDCWD, "/usr/lib/locale/en_US.UTF-8/LC_CTYPE",
    O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    file does not exist.

    openat(AT_FDCWD, "/usr/lib/locale/en_US.utf8/LC_CTYPE",
    O_RDONLY|O_CLOEXEC) = 3

    Tries another name, that does exist, and returns the handle.

    fstat(3, {st_mode=S_IFREG|0644, st_size=2940, ...}) = 0

    It queries the file...


    Here is the one that matters, starting at line 88:

    (I insert blank lines for clarity)



    openat(AT_FDCWD, "/usr/lib/locale/Default.UTF-8/LC_TIME", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/Default.utf8/LC_TIME",
    O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/Default/LC_TIME", O_RDONLY|O_CLOEXEC)
    = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/share/locale-langpack/en_US.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY)
    = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/share/locale/en_US.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/share/locale-langpack/en_US.utf8/LC_MESSAGES/libc.mo", O_RDONLY) =
    -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/share/locale/en_US.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/share/locale-langpack/en_US/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/share/locale/en_US/LC_MESSAGES/libc.mo",
    O_RDONLY) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD,
    "/usr/share/locale-langpack/en.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) =
    -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/share/locale/en.UTF-8/LC_MESSAGES/libc.mo",
    O_RDONLY) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD,
    "/usr/share/locale-langpack/en.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/share/locale/en.utf8/LC_MESSAGES/libc.mo",
    O_RDONLY) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/share/locale-langpack/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/share/locale/en/LC_MESSAGES/libc.mo", O_RDONLY) =
    -1 ENOENT (No such file or directory)

    write(2, "locale: ", 8locale: )-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a = 8
    write(2, "Cannot set LC_ALL to default loc"..., 35Cannot set LC_ALL to default locale) = 35
    write(2, ": No such file or directory", 27: No such file or directory) = 27


    I can see that "/usr/share/locale/en_GB/LC_MESSAGES/libc.mo" does exist
    in my system, but not "/usr/share/locale/en/LC_MESSAGES/libc.mo". It is curious. But anyway, you know now what file it is missing.


    I will now try the same command on 15.5.

    [...]

    Ok, mine doesn't try to find "libc.mo". It does try "LC_MESSAGES"

    openat(AT_FDCWD, "/usr/lib/locale/en_US.UTF-8/LC_MESSAGES", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/en_US.utf8/LC_MESSAGES", O_RDONLY|O_CLOEXEC) = 3





    On yours, the first problem happens here:

    openat(AT_FDCWD, "/usr/lib/locale/en_US.UTF-8/LC_COLLATE", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/en_US.utf8/LC_COLLATE", O_RDONLY|O_CLOEXEC) = 3

    fstat(3, {st_mode=S_IFREG|0644, st_size=2586930, ...}) = 0
    mmap(NULL, 2586930, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fa46d860000

    close(3)-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a = 0

    openat(AT_FDCWD, "/usr/lib/locale/Default.UTF-8/LC_TIME", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/Default.utf8/LC_TIME",
    O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/Default/LC_TIME", O_RDONLY|O_CLOEXEC)
    = -1 ENOENT (No such file or directory)


    On mine, the same section:


    openat(AT_FDCWD, "/usr/lib/locale/es_ES.utf8/LC_MONETARY", O_RDONLY|O_CLOEXEC) = 3

    fstat(3, {st_mode=S_IFREG|0644, st_size=294, ...}) = 0
    mmap(NULL, 294, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f97b2f8f000

    close(3)-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a = 0

    openat(AT_FDCWD, "/usr/lib/locale/en_US.UTF-8/LC_COLLATE", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/en_US.utf8/LC_COLLATE", O_RDONLY|O_CLOEXEC) = 3

    fstat(3, {st_mode=S_IFREG|0644, st_size=2586930, ...}) = 0
    mmap(NULL, 2586930, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f97b2ab2000

    close(3)-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a = 0

    openat(AT_FDCWD, "/usr/lib/locale/en_DK.UTF-8/LC_TIME",
    O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/en_DK.utf8/LC_TIME",
    O_RDONLY|O_CLOEXEC) = 3

    fstat(3, {st_mode=S_IFREG|0644, st_size=3180, ...}) = 0

    mmap(NULL, 3180, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f97b2f8e000 close(3)-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a = 0



    Ah, ok, but I use a different time locale than you (en_DK.UTF-8). I'll
    try a different user.


    openat(AT_FDCWD, "/usr/lib/locale/en_US.UTF-8/LC_MONETARY", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/en_US.utf8/LC_MONETARY", O_RDONLY|O_CLOEXEC) = 3

    fstat(3, {st_mode=S_IFREG|0644, st_size=286, ...}) = 0

    mmap(NULL, 286, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7efff46b2000

    close(3)-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a = 0

    openat(AT_FDCWD, "/usr/lib/locale/en_US.UTF-8/LC_COLLATE", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/en_US.utf8/LC_COLLATE", O_RDONLY|O_CLOEXEC) = 3

    fstat(3, {st_mode=S_IFREG|0644, st_size=2586930, ...}) = 0

    mmap(NULL, 2586930, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7efff41d5000

    close(3)-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a = 0

    openat(AT_FDCWD, "/usr/lib/locale/en_US.UTF-8/LC_TIME",
    O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/en_US.utf8/LC_TIME",
    O_RDONLY|O_CLOEXEC) = 3

    fstat(3, {st_mode=S_IFREG|0644, st_size=3284, ...}) = 0

    mmap(NULL, 3284, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7efff46b1000

    close(3)-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a = 0

    openat(AT_FDCWD, "/usr/lib/locale/en_US.UTF-8/LC_NUMERIC", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/en_US.utf8/LC_NUMERIC", O_RDONLY|O_CLOEXEC) = 3

    fstat(3, {st_mode=S_IFREG|0644, st_size=54, ...}) = 0

    mmap(NULL, 54, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7efff46b0000 close(3)-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a = 0


    Whereas yours do:

    openat(AT_FDCWD, "/usr/lib/locale/Default.UTF-8/LC_TIME", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/Default.utf8/LC_TIME",
    O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

    openat(AT_FDCWD, "/usr/lib/locale/Default/LC_TIME", O_RDONLY|O_CLOEXEC)
    = -1 ENOENT (No such file or directory)



    Mine tries first the file "/usr/lib/locale/en_US.UTF-8/LC_TIME" which
    does not exist. Then it tries "/usr/lib/locale/en_US.utf8/LC_TIME",
    which in mine does exist.

    But yours is trying instead

    /usr/lib/locale/Default.UTF-8/LC_TIME
    /usr/lib/locale/Default.utf8/LC_TIME
    /usr/lib/locale/Default/LC_TIME

    which do not exist. Why is it trying those?


    When I asked you for your locale, you pasted this:

    Leap-15.5
    ~ 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-a-a <=========
    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=


    That's the origin of your problem. Why do you have that?
    Find that out, and change it to a proper one, and you should be Ok.



    I'm assuming I don't have this problem - and have no intention of naming
    files that way - so my interest in this topic is purely academic. Oh,
    and my "locale" output is just fine and fits my expectations.

    I'd have thought this stuff would be controlled by YaST2, specifically:
    System -> Language -> Primary Language Settings

    A further possibility would be:
    System -> Sysconfig Editor -> System -> Environment -> Language
    but the only overrides I have set there are for ROOT_USES_LANG (ctype)
    and AUTO_DETECT_UTF8 (no). Obviously, INSTALLED_LANGUAGES is set.
    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to alt.os.linux.suse on Mon Jul 17 23:32:33 2023
    From Newsgroup: alt.os.linux.suse

    On 2023-07-17 21:25, Don Spam's Reckless Son wrote:
    Carlos E.R. wrote:
    On 2023-07-17 03:33, bad sector wrote:
    On Mon, 17 Jul 2023 02:44:07 +0200, Carlos E.R. wrote:
    On 7/16/23 20:44, Carlos E.R. wrote:
    On 2023-07-17 01:43, bad sector wrote:
    On Sun, 16 Jul 2023 22:00:38 +0200, Carlos E.R. wrote:

    ...

    But yours is trying instead

    /usr/lib/locale/Default.UTF-8/LC_TIME
    /usr/lib/locale/Default.utf8/LC_TIME
    /usr/lib/locale/Default/LC_TIME

    which do not exist. Why is it trying those?


    When I asked you for your locale, you pasted this:

    Leap-15.5
    ~ 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-a-a <=========
    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=


    That's the origin of your problem. Why do you have that?
    Find that out, and change it to a proper one, and you should be Ok.



    I'm assuming I don't have this problem - and have no intention of naming files that way - so my interest in this topic is purely academic.-a Oh,
    and my "locale" output is just fine and fits my expectations.

    I'd have thought this stuff would be controlled by YaST2, specifically: System -> Language -> Primary Language Settings

    Yes, the system or default language, and what additional language
    packages for different software you install. But the locale for each
    user is independent. Both Gnome and KDE have different methods of
    setting it up.


    A further possibility would be:
    System -> Sysconfig Editor -> System -> Environment -> Language
    but the only overrides I have set there are for ROOT_USES_LANG (ctype)
    and AUTO_DETECT_UTF8 (no).-a Obviously, INSTALLED_LANGUAGES is set.

    Right.
    --
    Cheers, Carlos.

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From bad sector@forgetski@_INVALID.net to alt.os.linux.suse on Mon Jul 17 18:26:43 2023
    From Newsgroup: alt.os.linux.suse

    On 7/17/23 14:10, Carlos E.R. wrote:

    Edit (or create) file .i18n. Mine is:

    # used by /etc/profile.d/lang.sh
    #CER - if it doesn't work edit /etc/profile.d/lang.sh, see Bugzilla 567324 LC_TIME=en_DK.UTF-8
    LC_MONETARY=es_ES.utf8
    LC_NUMERIC=es_ES.utf8
    LC_PAPER=es_ES.utf8
    LC_TELEPHONE=es_ES.utf8
    LC_MEASUREMENT=es_ES.utf8
    LC_NAME=es_ES.utf8

    Is it UTF-8 or utf8?
    And how come sometimes these fields are quoted and sometimes not?

    You need to at least log out and in.


    I'm on Tumbleweed now, fully updated as of 30 minutes ago

    There IS a ~/.i18n file, edited it to

    LANG=en_US.UTF-8
    LC_CTYPE="en_US.UTF-8"
    LC_NUMERIC="en_US.UTF-8"
    LC_TIME="en_US.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"

    ...no change

    no file /etc/profile.d/lang.sh

    on re-log-in

    ~ 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=

    Don't know where that "Default.UTF-8" keeps coming from!


    I don't know why gimp has trouble, but you know the drill: strace.

    my bad, I had forgot that the last strace exercise was in fact for gimp
    and not some locale command (starting to get dizzy here)

    strace --output=filename-a gimp
    and find out what file it doesn't find.


    Huh, I don't know if gimp can work if the locale is "C". It needs utf-8.
    That was only to see if anything would change, nothing did, forget it


    ~ export LC_TIME="en_US.UTF-8" export LC_TIME="en_US.UTF-8"


    the result being:

    ~ locale
    LANG=en_US.UTF-8
    LC_CTYPE=en_US.UTF-8
    LC_NUMERIC=en_US.UTF-8
    LC_TIME=en_US.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=



    If I issue the strace command just for gimp:

    ~ strace --output=trace.txt gimp
    (gimp:10753): Gtk-WARNING **: 17:33:58.024: Locale not supported by C
    library.
    Using the fallback 'C' locale.



    gimp loads and I can load and export the file A#-|_0305.png




    If I issue the strace command WITH the file also argued for gimp

    ~ strace --output=trace.txt gimp A#-|_0305.png
    libpng warning: iCCP: CRC error
    ** (file-png:8596): WARNING **: 17:22:59.539: Unsupported date format
    gimp: (null)-WARNING: Unsupported date format


    NOW we're getting some civilised *comms* i.e. bad 'date' even though
    the locale is called LC_TIME

    gimp loads and I can load and export the file A#-|_0305.png


    BUT if I clicjk the file icon in dolphin to open the image
    with gimp THEN gimp throws a fit as before and I cannot export
    on account of "illegal filename"


    *Is it a dolphin bug?*
    {dolphin AND gimp are GNOME?}

    So I have a partial fix but on reboot I'll have to re-export
    what seems like THE bad field value for LC_TIME

    Also tried editing

    export LC_TIME="en_US.UTF-8"

    into /.profile, no joy





    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From bad sector@forgetski@_INVALID.net to alt.os.linux.suse on Mon Jul 17 19:15:14 2023
    From Newsgroup: alt.os.linux.suse

    On 7/17/23 09:01, Carlos E.R. wrote:

    Mine tries first the file "/usr/lib/locale/en_US.UTF-8/LC_TIME" which
    does not exist. Then it tries "/usr/lib/locale/en_US.utf8/LC_TIME",
    which in mine does exist.

    But yours is trying instead

    /usr/lib/locale/Default.UTF-8/LC_TIME
    /usr/lib/locale/Default.utf8/LC_TIME
    /usr/lib/locale/Default/LC_TIME

    which do not exist. Why is it trying those?


    When I asked you for your locale, you pasted this:

    Leap-15.5
    ~ 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-a-a <=========
    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=


    That's the origin of your problem. Why do you have that?
    Find that out, and change it to a proper one, and you should be Ok.

    Also tried setting it in Yast to "en_US.UTF-8"

    On login I still get that Default.UTF-8

    did a content search on "Default.UTF-8"

    Bingo...

    ~/.config/plasma-localerc

    [Formats]
    LANG=en_US.UTF-8
    LC_PAPER=en_US.UTF-8
    LC_TIME=Default.UTF-8
    useDetailed=true

    [Translations]
    LANGUAGE=

    re-edited, problem (seems to be) solved in TW

    DON'T ask me where that came from, looks like a script generated file




    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From bad sector@forgetski@_INVALID.net to alt.os.linux.suse on Mon Jul 17 19:22:27 2023
    From Newsgroup: alt.os.linux.suse

    On 7/17/23 19:15, bad sector wrote:
    On 7/17/23 09:01, Carlos E.R. wrote:

    Mine tries first the file "/usr/lib/locale/en_US.UTF-8/LC_TIME" which
    does not exist. Then it tries "/usr/lib/locale/en_US.utf8/LC_TIME",
    which in mine does exist.

    But yours is trying instead

    /usr/lib/locale/Default.UTF-8/LC_TIME
    /usr/lib/locale/Default.utf8/LC_TIME
    /usr/lib/locale/Default/LC_TIME

    which do not exist. Why is it trying those?


    When I asked you for your locale, you pasted this:

    Leap-15.5
    ~ 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-a-a <=========
    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=


    That's the origin of your problem. Why do you have that?
    Find that out, and change it to a proper one, and you should be Ok.

    Also tried setting it in Yast to "en_US.UTF-8"

    On login I still get that Default.UTF-8

    did a content search on "Default.UTF-8"

    Bingo...

    ~/.config/plasma-localerc

    [Formats]
    LANG=en_US.UTF-8
    LC_PAPER=en_US.UTF-8
    LC_TIME=Default.UTF-8
    useDetailed=true

    [Translations]
    LANGUAGE=

    re-edited, problem (seems to be) solved in TW

    DON'T ask me where that came from, looks like a script generated file

    still get error though:



    ~ locale
    LANG=en_US.UTF-8
    LC_CTYPE=en_US.UTF-8
    LC_NUMERIC=en_US.UTF-8
    LC_TIME=en_US.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=


    ~ gimp "A#-|_0305.png"
    libpng warning: iCCP: CRC error
    ** (file-png:5963): WARNING **: 19:19:28.649: Unsupported date format
    gimp: (null)-WARNING: Unsupported date format










    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From bad sector@forgetski@INVALID.net to alt.os.linux.suse on Mon Jul 17 19:39:50 2023
    From Newsgroup: alt.os.linux.suse

    On 7/17/23 19:15, bad sector wrote:
    On 7/17/23 09:01, Carlos E.R. wrote:

    Mine tries first the file "/usr/lib/locale/en_US.UTF-8/LC_TIME" which
    does not exist. Then it tries "/usr/lib/locale/en_US.utf8/LC_TIME",
    which in mine does exist.

    But yours is trying instead

    /usr/lib/locale/Default.UTF-8/LC_TIME
    /usr/lib/locale/Default.utf8/LC_TIME
    /usr/lib/locale/Default/LC_TIME

    which do not exist. Why is it trying those?


    When I asked you for your locale, you pasted this:

    Leap-15.5
    ~ 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-a-a <=========
    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=


    That's the origin of your problem. Why do you have that?
    Find that out, and change it to a proper one, and you should be Ok.

    Also tried setting it in Yast to "en_US.UTF-8"

    On login I still get that Default.UTF-8

    did a content search on "Default.UTF-8"

    Bingo...

    ~/.config/plasma-localerc

    [Formats]
    LANG=en_US.UTF-8
    LC_PAPER=en_US.UTF-8
    LC_TIME=Default.UTF-8
    useDetailed=true

    [Translations]
    LANGUAGE=

    re-edited, problem (seems to be) solved in TW

    DON'T ask me where that came from, looks like a script generated file


    after same file edited in Leap-15.5:


    ~ locale
    LANG=en_US.UTF-8
    LC_CTYPE=en_US.UTF-8
    LC_NUMERIC="en_US.UTF-8"
    LC_TIME=en_US.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=

    ~ gimp /0/adat/Music/atelier/DGCFAD/chords/base-diags/A#-|_0305.png
    libpng warning: iCCP: CRC error
    ** (file-png:4016): WARNING **: 19:35:41.346: Unsupported date format
    ** (file-png:4016): WARNING **: 19:35:41.346: Unsupported time format

    Here we have BOTH time AND date complained about in libpng










    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Don Spam's Reckless Son@hyperspace.flyover@vogon.gov.invalid to alt.os.linux.suse on Tue Jul 18 09:55:52 2023
    From Newsgroup: alt.os.linux.suse

    bad sector wrote:
    On 7/17/23 19:15, bad sector wrote:
    On 7/17/23 09:01, Carlos E.R. wrote:

    Mine tries first the file "/usr/lib/locale/en_US.UTF-8/LC_TIME" which
    does not exist. Then it tries "/usr/lib/locale/en_US.utf8/LC_TIME",
    which in mine does exist.

    But yours is trying instead

    /usr/lib/locale/Default.UTF-8/LC_TIME
    /usr/lib/locale/Default.utf8/LC_TIME
    /usr/lib/locale/Default/LC_TIME

    which do not exist. Why is it trying those?


    When I asked you for your locale, you pasted this:

    Leap-15.5
    ~ 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-a-a <=========
    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=


    That's the origin of your problem. Why do you have that?
    Find that out, and change it to a proper one, and you should be Ok.

    Also tried setting it in Yast to "en_US.UTF-8"

    On login I still get that Default.UTF-8

    did a content search on "Default.UTF-8"

    Bingo...

    ~/.config/plasma-localerc

    [Formats]
    LANG=en_US.UTF-8
    LC_PAPER=en_US.UTF-8
    LC_TIME=Default.UTF-8
    useDetailed=true

    [Translations]
    LANGUAGE=

    re-edited, problem (seems to be) solved in TW

    DON'T ask me where that came from, looks like a script generated file


    after same file edited in Leap-15.5:


    ~ locale
    LANG=en_US.UTF-8
    LC_CTYPE=en_US.UTF-8
    LC_NUMERIC="en_US.UTF-8"
    LC_TIME=en_US.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=

    ~ gimp /0/adat/Music/atelier/DGCFAD/chords/base-diags/A#-|_0305.png
    libpng warning: iCCP: CRC error
    ** (file-png:4016): WARNING **: 19:35:41.346: Unsupported date format
    ** (file-png:4016): WARNING **: 19:35:41.346: Unsupported time format

    Here we have BOTH time AND date complained about in libpng



    Did you reboot?
    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to alt.os.linux.suse on Tue Jul 18 11:45:19 2023
    From Newsgroup: alt.os.linux.suse

    On 2023-07-18 00:26, bad sector wrote:
    On 7/17/23 14:10, Carlos E.R. wrote:

    Edit (or create) file .i18n. Mine is:

    # used by /etc/profile.d/lang.sh
    #CER - if it doesn't work edit /etc/profile.d/lang.sh, see Bugzilla
    567324
    LC_TIME=en_DK.UTF-8
    LC_MONETARY=es_ES.utf8
    LC_NUMERIC=es_ES.utf8
    LC_PAPER=es_ES.utf8
    LC_TELEPHONE=es_ES.utf8
    LC_MEASUREMENT=es_ES.utf8
    LC_NAME=es_ES.utf8

    Is it UTF-8 or utf8?

    Sometimes one, some times the other. Maybe you noticed that the command "locale" checked both.

    And how come sometimes these fields are quoted and sometimes not?

    Dunno.


    You need to at least log out and in.


    I'm on Tumbleweed now, fully updated as of 30 minutes ago

    There IS a ~/.i18n-a file, edited it to

    LANG=en_US.UTF-8
    LC_CTYPE="en_US.UTF-8"
    LC_NUMERIC="en_US.UTF-8"
    LC_TIME="en_US.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"

    ...no change

    no file /etc/profile.d/lang.sh

    on re-log-in

    Are you using kde/plasma?


    ~ 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-a-a-a-a-a <<<<<<<<<
    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=

    Don't know where that "Default.UTF-8" keeps coming from!


    I don't know why gimp has trouble, but you know the drill: strace.

    my bad, I had forgot that the last strace exercise was in fact for gimp
    and not some locale command (starting to get dizzy here)

    Oh, I told you to try on locale because it is a far easier one to trace.



    strace --output=filename-a gimp
    and find out what file it doesn't find.


    Huh, I don't know if gimp can work if the locale is "C". It needs utf-8.
    That was only to see if anything would change, nothing did, forget it


    ~ export LC_TIME="en_US.UTF-8" export LC_TIME="en_US.UTF-8"


    the result being:

    ~ locale
    LANG=en_US.UTF-8
    LC_CTYPE=en_US.UTF-8
    LC_NUMERIC=en_US.UTF-8
    LC_TIME=en_US.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=



    If I issue the strace command just for gimp:

    ~ strace --output=trace.txt gimp
    (gimp:10753): Gtk-WARNING **: 17:33:58.024: Locale not supported by C library.
    Using the fallback 'C' locale.



    gimp loads and I can load and export the file A#-|_0305.png




    If I issue the strace command WITH the file also argued for gimp

    ~ strace --output=trace.txt gimp A#-|_0305.png
    libpng warning: iCCP: CRC error
    ** (file-png:8596): WARNING **: 17:22:59.539: Unsupported date format
    gimp: (null)-WARNING: Unsupported date format

    Curious.



    NOW we're getting some civilised *comms* i.e. bad 'date' even though
    the locale is called LC_TIME

    gimp loads and I can load and export the file A#-|_0305.png


    BUT if I clicjk the file icon in dolphin to open the image
    with gimp THEN gimp throws a fit as before and I cannot export
    on account of "illegal filename"

    Because KDE is using the wrong locale.


    *Is it a dolphin bug?*
    {dolphin AND gimp are GNOME?}

    So I have a partial fix but on reboot I'll have to re-export
    what seems like THE bad field value for LC_TIME

    Also tried editing

    export LC_TIME="en_US.UTF-8"

    into /.profile, no joy
    --
    Cheers, Carlos.

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to alt.os.linux.suse on Tue Jul 18 11:45:21 2023
    From Newsgroup: alt.os.linux.suse

    On 2023-07-18 01:15, bad sector wrote:
    On 7/17/23 09:01, Carlos E.R. wrote:

    Mine tries first the file "/usr/lib/locale/en_US.UTF-8/LC_TIME" which
    does not exist. Then it tries "/usr/lib/locale/en_US.utf8/LC_TIME",
    which in mine does exist.

    But yours is trying instead

    /usr/lib/locale/Default.UTF-8/LC_TIME
    /usr/lib/locale/Default.utf8/LC_TIME
    /usr/lib/locale/Default/LC_TIME

    which do not exist. Why is it trying those?


    When I asked you for your locale, you pasted this:

    Leap-15.5
    ~ 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-a-a <=========
    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=


    That's the origin of your problem. Why do you have that?
    Find that out, and change it to a proper one, and you should be Ok.

    Also tried setting it in Yast to "en_US.UTF-8"

    On login I still get that Default.UTF-8

    did a content search on "Default.UTF-8"

    Bingo...

    ~/.config/plasma-localerc

    Aha. I thought so.


    [Formats]
    LANG=en_US.UTF-8
    LC_PAPER=en_US.UTF-8
    LC_TIME=Default.UTF-8
    useDetailed=true

    [Translations]
    LANGUAGE=

    re-edited, problem (seems to be) solved in TW

    DON'T ask me where that came from, looks like a script generated file

    probably. Report but in Bugzilla ;-)
    --
    Cheers, Carlos.

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to alt.os.linux.suse on Tue Jul 18 11:49:37 2023
    From Newsgroup: alt.os.linux.suse

    On 2023-07-18 01:22, bad sector wrote:
    On 7/17/23 19:15, bad sector wrote:
    On 7/17/23 09:01, Carlos E.R. wrote:



    Bingo...

    ~/.config/plasma-localerc

    [Formats]
    LANG=en_US.UTF-8
    LC_PAPER=en_US.UTF-8
    LC_TIME=Default.UTF-8
    useDetailed=true

    [Translations]
    LANGUAGE=

    re-edited, problem (seems to be) solved in TW

    DON'T ask me where that came from, looks like a script generated file

    still get error though:



    ~ locale
    LANG=en_US.UTF-8
    LC_CTYPE=en_US.UTF-8
    LC_NUMERIC=en_US.UTF-8
    LC_TIME=en_US.UTF-8-a-a-a-a-a <<<<<<<
    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=


    ~ gimp "A#-|_0305.png"
    libpng warning: iCCP: CRC error
    ** (file-png:5963): WARNING **: 19:19:28.649: Unsupported date format
    gimp: (null)-WARNING: Unsupported date format

    Yes, but that may come from the actual date format used, not the locale string.

    Not sure what command to use to get the time printed in the locale. Try
    "date" without options.

    cer@Telcontar:~> date
    2023-07-18T11:47:43 CEST
    cer@Telcontar:~> locale | grep -i time
    LC_TIME=en_DK.UTF-8
    cer@Telcontar:~>

    which is correct. I seem to recall seeing the date in USA format before.
    Ah, "ls" uses the usa format.
    --
    Cheers, Carlos.

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From bad sector@forgetski@INVALID.net to alt.os.linux.suse on Tue Jul 18 08:56:33 2023
    From Newsgroup: alt.os.linux.suse

    On 7/18/23 05:49, Carlos E.R. wrote:
    On 2023-07-18 01:22, bad sector wrote:
    On 7/17/23 19:15, bad sector wrote:
    On 7/17/23 09:01, Carlos E.R. wrote:



    Bingo...

    ~/.config/plasma-localerc

    [Formats]
    LANG=en_US.UTF-8
    LC_PAPER=en_US.UTF-8
    LC_TIME=Default.UTF-8
    useDetailed=true

    [Translations]
    LANGUAGE=

    re-edited, problem (seems to be) solved in TW

    DON'T ask me where that came from, looks like a script generated file

    still get error though:



    ~ locale
    LANG=en_US.UTF-8
    LC_CTYPE=en_US.UTF-8
    LC_NUMERIC=en_US.UTF-8
    LC_TIME=en_US.UTF-8-a-a-a-a-a <<<<<<<
    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=


    ~ gimp "A#-|_0305.png"
    libpng warning: iCCP: CRC error
    ** (file-png:5963): WARNING **: 19:19:28.649: Unsupported date format
    gimp: (null)-WARNING: Unsupported date format

    Yes, but that may come from the actual date format used, not the locale string.

    Not sure what command to use to get the time printed in the locale. Try "date" without options.

    cer@Telcontar:~> date
    2023-07-18T11:47:43 CEST
    cer@Telcontar:~> locale | grep -i time
    LC_TIME=en_DK.UTF-8
    cer@Telcontar:~>

    which is correct. I seem to recall seeing the date in USA format before.
    Ah, "ls" uses the usa format.

    ~ # date
    Tue 18 Jul 2023 07:28:03 AM EDT
    ~ # locale | grep -i time
    LC_TIME=en_US.UTF-8

    I don't see what could/should be un-supported by way of any 'known' date format, is there a date 'inside' the png file maybe?


    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From bad sector@forgetski@INVALID.net to alt.os.linux.suse on Tue Jul 18 08:57:53 2023
    From Newsgroup: alt.os.linux.suse

    On 7/18/23 03:55, Don Spam's Reckless Son wrote:
    bad sector wrote:
    On 7/17/23 19:15, bad sector wrote:
    On 7/17/23 09:01, Carlos E.R. wrote:

    Mine tries first the file "/usr/lib/locale/en_US.UTF-8/LC_TIME"
    which does not exist. Then it tries
    "/usr/lib/locale/en_US.utf8/LC_TIME", which in mine does exist.

    But yours is trying instead

    /usr/lib/locale/Default.UTF-8/LC_TIME
    /usr/lib/locale/Default.utf8/LC_TIME
    /usr/lib/locale/Default/LC_TIME

    which do not exist. Why is it trying those?


    When I asked you for your locale, you pasted this:

    Leap-15.5
    ~ 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-a-a <=========
    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=


    That's the origin of your problem. Why do you have that?
    Find that out, and change it to a proper one, and you should be Ok.

    Also tried setting it in Yast to "en_US.UTF-8"

    On login I still get that Default.UTF-8

    did a content search on "Default.UTF-8"

    Bingo...

    ~/.config/plasma-localerc

    [Formats]
    LANG=en_US.UTF-8
    LC_PAPER=en_US.UTF-8
    LC_TIME=Default.UTF-8
    useDetailed=true

    [Translations]
    LANGUAGE=

    re-edited, problem (seems to be) solved in TW

    DON'T ask me where that came from, looks like a script generated file


    after same file edited in Leap-15.5:


    ~ locale
    LANG=en_US.UTF-8
    LC_CTYPE=en_US.UTF-8
    LC_NUMERIC="en_US.UTF-8"
    LC_TIME=en_US.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=

    ~ gimp /0/adat/Music/atelier/DGCFAD/chords/base-diags/A#-|_0305.png
    libpng warning: iCCP: CRC error
    ** (file-png:4016): WARNING **: 19:35:41.346: Unsupported date format
    ** (file-png:4016): WARNING **: 19:35:41.346: Unsupported time format

    Here we have BOTH time AND date complained about in libpng



    Did you reboot?

    affirmative


    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From bad sector@forgetski@_INVALID.net to alt.os.linux.suse on Tue Jul 18 12:47:28 2023
    From Newsgroup: alt.os.linux.suse

    On 7/18/23 05:45, Carlos E.R. wrote:
    On 2023-07-18 01:15, bad sector wrote:
    On 7/17/23 09:01, Carlos E.R. wrote:

    Mine tries first the file "/usr/lib/locale/en_US.UTF-8/LC_TIME" which
    does not exist. Then it tries "/usr/lib/locale/en_US.utf8/LC_TIME",
    which in mine does exist.

    But yours is trying instead

    /usr/lib/locale/Default.UTF-8/LC_TIME
    /usr/lib/locale/Default.utf8/LC_TIME
    /usr/lib/locale/Default/LC_TIME

    which do not exist. Why is it trying those?


    When I asked you for your locale, you pasted this:

    Leap-15.5
    ~ 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-a-a <=========
    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=


    That's the origin of your problem. Why do you have that?
    Find that out, and change it to a proper one, and you should be Ok.

    Also tried setting it in Yast to "en_US.UTF-8"

    On login I still get that Default.UTF-8

    did a content search on "Default.UTF-8"

    Bingo...

    ~/.config/plasma-localerc

    Aha. I thought so.

    In Artix, also with KDE :-) the file is only

    ==================
    [Formats]
    LANG=en_CA.UTF-8
    ==================


    The above must have come from clicking Pangnirtung as a place just to
    throw too long noses off a bit







    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to alt.os.linux.suse on Tue Jul 18 20:17:31 2023
    From Newsgroup: alt.os.linux.suse

    On 2023-07-18 14:56, bad sector wrote:
    On 7/18/23 05:49, Carlos E.R. wrote:
    On 2023-07-18 01:22, bad sector wrote:
    On 7/17/23 19:15, bad sector wrote:
    On 7/17/23 09:01, Carlos E.R. wrote:



    Bingo...

    ~/.config/plasma-localerc

    [Formats]
    LANG=en_US.UTF-8
    LC_PAPER=en_US.UTF-8
    LC_TIME=Default.UTF-8
    useDetailed=true

    [Translations]
    LANGUAGE=

    re-edited, problem (seems to be) solved in TW

    DON'T ask me where that came from, looks like a script generated file

    still get error though:



    ~ locale
    LANG=en_US.UTF-8
    LC_CTYPE=en_US.UTF-8
    LC_NUMERIC=en_US.UTF-8
    LC_TIME=en_US.UTF-8-a-a-a-a-a <<<<<<<
    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=


    ~ gimp "A#-|_0305.png"
    libpng warning: iCCP: CRC error
    ** (file-png:5963): WARNING **: 19:19:28.649: Unsupported date format
    gimp: (null)-WARNING: Unsupported date format

    Yes, but that may come from the actual date format used, not the
    locale string.

    Not sure what command to use to get the time printed in the locale.
    Try "date" without options.

    cer@Telcontar:~> date
    2023-07-18T11:47:43 CEST
    cer@Telcontar:~> locale | grep -i time
    LC_TIME=en_DK.UTF-8
    cer@Telcontar:~>

    which is correct. I seem to recall seeing the date in USA format
    before. Ah, "ls" uses the usa format.

    ~ # date

    That's not you. That's Mr Root.

    Tue 18 Jul 2023 07:28:03 AM EDT
    ~ # locale | grep -i time
    LC_TIME=en_US.UTF-8

    I don't see what could/should be un-supported by way of any 'known' date format, is there a date 'inside' the png file maybe?
    --
    Cheers, Carlos.

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to alt.os.linux.suse on Tue Jul 18 20:19:37 2023
    From Newsgroup: alt.os.linux.suse

    On 2023-07-18 18:47, bad sector wrote:
    On 7/18/23 05:45, Carlos E.R. wrote:
    On 2023-07-18 01:15, bad sector wrote:
    On 7/17/23 09:01, Carlos E.R. wrote:

    Mine tries first the file "/usr/lib/locale/en_US.UTF-8/LC_TIME"
    which does not exist. Then it tries
    "/usr/lib/locale/en_US.utf8/LC_TIME", which in mine does exist.

    But yours is trying instead

    /usr/lib/locale/Default.UTF-8/LC_TIME
    /usr/lib/locale/Default.utf8/LC_TIME
    /usr/lib/locale/Default/LC_TIME

    which do not exist. Why is it trying those?


    When I asked you for your locale, you pasted this:

    Leap-15.5
    ~ 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-a-a <=========
    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=


    That's the origin of your problem. Why do you have that?
    Find that out, and change it to a proper one, and you should be Ok.

    Also tried setting it in Yast to "en_US.UTF-8"

    On login I still get that Default.UTF-8

    did a content search on "Default.UTF-8"

    Bingo...

    ~/.config/plasma-localerc

    Aha. I thought so.

    In Artix, also with KDE :-) the file is only

    ==================
    [Formats]
    LANG=en_CA.UTF-8
    ==================


    The above must have come from clicking Pangnirtung as a place just to
    throw too long noses off a bit

    Ar you using the same home folder in openSUSE? Because openSUSE doesn't
    have "en_CA.UTF-8".
    --
    Cheers, Carlos.

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From bad sector@forgetski@_INVALID.net to alt.os.linux.suse on Tue Jul 18 17:34:15 2023
    From Newsgroup: alt.os.linux.suse

    On 7/18/23 14:19, Carlos E.R. wrote:
    On 2023-07-18 18:47, bad sector wrote:
    On 7/18/23 05:45, Carlos E.R. wrote:
    On 2023-07-18 01:15, bad sector wrote:
    On 7/17/23 09:01, Carlos E.R. wrote:

    Mine tries first the file "/usr/lib/locale/en_US.UTF-8/LC_TIME"
    which does not exist. Then it tries
    "/usr/lib/locale/en_US.utf8/LC_TIME", which in mine does exist.

    But yours is trying instead

    /usr/lib/locale/Default.UTF-8/LC_TIME
    /usr/lib/locale/Default.utf8/LC_TIME
    /usr/lib/locale/Default/LC_TIME

    which do not exist. Why is it trying those?


    When I asked you for your locale, you pasted this:

    Leap-15.5
    ~ 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-a-a <=========
    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=


    That's the origin of your problem. Why do you have that?
    Find that out, and change it to a proper one, and you should be Ok.

    Also tried setting it in Yast to "en_US.UTF-8"

    On login I still get that Default.UTF-8

    did a content search on "Default.UTF-8"

    Bingo...

    ~/.config/plasma-localerc

    Aha. I thought so.

    In Artix, also with KDE :-) the file is only

    ==================
    [Formats]
    LANG=en_CA.UTF-8
    ==================


    The above must have come from clicking Pangnirtung as a place just to
    throw too long noses off a bit

    Ar you using the same home folder in openSUSE? Because openSUSE doesn't
    have "en_CA.UTF-8".


    No, /home/userMe in each OS is a link to a remote folder but for now a different one for each OS. Eventually they should all be the same one
    but I will probably not see that in my lifetime. Along the trajectory to
    that unreachable star, in each of these remote folders that userMe in different OS'es links to is a link to (this time) a common remote folder
    that includes folders like backgrounds, icons, and other chickenshit.
    THESE are all shared by all the OS'es and the common icons in these (3
    out of 7 or more) deskbars are an example of their use:

    https://i.imgur.com/fShcw31.png
    https://i.imgur.com/jRrwvDs.png
    https://i.imgur.com/CD8JYjm.png

    There are several such folders with different roles, another remote
    folder contains some *rc files to which links exist in those OS'es that
    share well, not others (yet). ".sylpheed-2" is one of only a dozen or so
    that links into every single OS without any issues whatsoever, .gftp and .profile are typical experimental ones in a very dynamic environment
    that I tinker with and proudly screw up every day but
    /.config/plasma-localerc is not such although a common .everything^%$%#&*$kdeinoneplace would be a real nice addition :-)


    https://i.imgur.com/R9cXaXa.png


    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From bad sector@forgetski@_INVALID.net to alt.os.linux.suse on Tue Jul 18 17:39:54 2023
    From Newsgroup: alt.os.linux.suse

    On 7/18/23 14:17, Carlos E.R. wrote:
    On 2023-07-18 14:56, bad sector wrote:
    On 7/18/23 05:49, Carlos E.R. wrote:
    On 2023-07-18 01:22, bad sector wrote:
    On 7/17/23 19:15, bad sector wrote:
    On 7/17/23 09:01, Carlos E.R. wrote:



    Bingo...

    ~/.config/plasma-localerc

    [Formats]
    LANG=en_US.UTF-8
    LC_PAPER=en_US.UTF-8
    LC_TIME=Default.UTF-8
    useDetailed=true

    [Translations]
    LANGUAGE=

    re-edited, problem (seems to be) solved in TW

    DON'T ask me where that came from, looks like a script generated file >>>>
    still get error though:



    ~ locale
    LANG=en_US.UTF-8
    LC_CTYPE=en_US.UTF-8
    LC_NUMERIC=en_US.UTF-8
    LC_TIME=en_US.UTF-8-a-a-a-a-a <<<<<<<
    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=


    ~ gimp "A#-|_0305.png"
    libpng warning: iCCP: CRC error
    ** (file-png:5963): WARNING **: 19:19:28.649: Unsupported date format
    gimp: (null)-WARNING: Unsupported date format

    Yes, but that may come from the actual date format used, not the
    locale string.

    Not sure what command to use to get the time printed in the locale.
    Try "date" without options.

    cer@Telcontar:~> date
    2023-07-18T11:47:43 CEST
    cer@Telcontar:~> locale | grep -i time
    LC_TIME=en_DK.UTF-8
    cer@Telcontar:~>

    which is correct. I seem to recall seeing the date in USA format
    before. Ah, "ls" uses the usa format.

    ~ # date

    That's not you. That's Mr Root.

    I like the # prompt, use gold on black for me, red for the super U
    (NB the red file cabinet in some of the deskbars in other answer). I
    also like to use alarmingly 'criard' colors for windows operated as
    root, has saved my hide many a time! FM as root is by far one of the
    neatest Suse features BTW.


    Tue 18 Jul 2023 07:28:03 AM EDT
    ~ # locale | grep -i time
    LC_TIME=en_US.UTF-8

    I don't see what could/should be un-supported by way of any 'known'
    date format, is there a date 'inside' the png file maybe?



    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to alt.os.linux.suse on Wed Jul 19 12:17:17 2023
    From Newsgroup: alt.os.linux.suse

    On 2023-07-18 23:34, bad sector wrote:
    On 7/18/23 14:19, Carlos E.R. wrote:
    On 2023-07-18 18:47, bad sector wrote:
    On 7/18/23 05:45, Carlos E.R. wrote:
    On 2023-07-18 01:15, bad sector wrote:
    On 7/17/23 09:01, Carlos E.R. wrote:

    Mine tries first the file "/usr/lib/locale/en_US.UTF-8/LC_TIME"
    which does not exist. Then it tries
    "/usr/lib/locale/en_US.utf8/LC_TIME", which in mine does exist.

    But yours is trying instead

    /usr/lib/locale/Default.UTF-8/LC_TIME
    /usr/lib/locale/Default.utf8/LC_TIME
    /usr/lib/locale/Default/LC_TIME

    which do not exist. Why is it trying those?


    When I asked you for your locale, you pasted this:

    Leap-15.5
    ~ 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-a-a <=========
    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=


    That's the origin of your problem. Why do you have that?
    Find that out, and change it to a proper one, and you should be Ok. >>>>>
    Also tried setting it in Yast to "en_US.UTF-8"

    On login I still get that Default.UTF-8

    did a content search on "Default.UTF-8"

    Bingo...

    ~/.config/plasma-localerc

    Aha. I thought so.

    In Artix, also with KDE :-) the file is only

    ==================
    [Formats]
    LANG=en_CA.UTF-8
    ==================


    The above must have come from clicking Pangnirtung as a place just to
    throw too long noses off a bit

    Ar you using the same home folder in openSUSE? Because openSUSE
    doesn't have "en_CA.UTF-8".

    I see "/usr/share/locale/en_CA", and en_GB and en_US and others, just no
    utf8 variants. Seems to be about the messages only.

    I also see

    /usr/lib/locale/en_CA
    /usr/lib/locale/en_CA.utf8

    just not "en_CA.UTF-8", which could thus just fail.



    No, /home/userMe in each OS is a link to a remote folder but for now a different one for each OS. Eventually they should all be the same one
    but I will probably not see that in my lifetime. Along the trajectory to that unreachable star, in each of these remote folders that userMe in different OS'es links to is a link to (this time) a common remote folder that includes folders like backgrounds, icons, and other chickenshit.
    THESE are all shared by all the OS'es and the common icons in these (3
    out of 7 or more) deskbars are an example of their use:

    https://i.imgur.com/fShcw31.png
    https://i.imgur.com/jRrwvDs.png
    https://i.imgur.com/CD8JYjm.png

    There are several such folders with different roles, another remote
    folder contains some *rc files to which links exist in those OS'es that share well, not others (yet). ".sylpheed-2" is one of only a dozen or so that links into every single OS without any issues whatsoever, .gftp and .profile are typical experimental ones in a very dynamic environment
    that I tinker with and proudly screw up every day but /.config/plasma-localerc is not such although a common .everything^%$%#&*$kdeinoneplace would be a real nice addition :-)

    Ok :-)



    https://i.imgur.com/R9cXaXa.png


    --
    Cheers, Carlos.

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From bad sector@forgetski@invalid.org to alt.os.linux.suse on Wed Jul 19 11:14:12 2023
    From Newsgroup: alt.os.linux.suse

    On Wed, 19 Jul 2023 12:17:17 +0200, Carlos E.R. wrote:

    On 2023-07-18 23:34, bad sector wrote:
    On 7/18/23 14:19, Carlos E.R. wrote:
    On 2023-07-18 18:47, bad sector wrote:
    On 7/18/23 05:45, Carlos E.R. wrote:
    On 2023-07-18 01:15, bad sector wrote:
    On 7/17/23 09:01, Carlos E.R. wrote:

    Mine tries first the file "/usr/lib/locale/en_US.UTF-8/LC_TIME"
    which does not exist. Then it tries
    "/usr/lib/locale/en_US.utf8/LC_TIME", which in mine does exist.

    But yours is trying instead

    /usr/lib/locale/Default.UTF-8/LC_TIME
    /usr/lib/locale/Default.utf8/LC_TIME
    /usr/lib/locale/Default/LC_TIME

    which do not exist. Why is it trying those?


    When I asked you for your locale, you pasted this:

    Leap-15.5 ~ 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-a-a <=========
    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=


    That's the origin of your problem. Why do you have that?
    Find that out, and change it to a proper one, and you should be
    Ok.

    Also tried setting it in Yast to "en_US.UTF-8"

    On login I still get that Default.UTF-8

    did a content search on "Default.UTF-8"

    Bingo...

    ~/.config/plasma-localerc

    Aha. I thought so.

    In Artix, also with KDE :-) the file is only

    ==================
    [Formats]
    LANG=en_CA.UTF-8 ==================


    The above must have come from clicking Pangnirtung as a place just to
    throw too long noses off a bit

    Ar you using the same home folder in openSUSE? Because openSUSE
    doesn't have "en_CA.UTF-8".

    I see "/usr/share/locale/en_CA", and en_GB and en_US and others, just no
    utf8 variants. Seems to be about the messages only.

    I also see

    /usr/lib/locale/en_CA /usr/lib/locale/en_CA.utf8

    today is slackware day but I mounted my Leap partition and it's the same
    here



    just not "en_CA.UTF-8", which could thus just fail.


    I'm just a passenger on this ship but it seems to me that the entire
    locale deal is gettin' a bit too 'lossy', it may be time to clean up the whorehouse, set some syntax rules and enforce them! When one is TS-ing
    and finds an output list of a dozen "en_US.UTF-8" in quotes but one that
    says en_US.utf8 and without quotes then one tends to think that that's
    where the problem is. Not so, it seems, for 'starters' :-(




    No, /home/userMe in each OS is a link to a remote folder but for now a
    different one for each OS. Eventually they should all be the same one
    but I will probably not see that in my lifetime. Along the trajectory
    to that unreachable star, in each of these remote folders that userMe
    in different OS'es links to is a link to (this time) a common remote
    folder that includes folders like backgrounds, icons, and other
    chickenshit. THESE are all shared by all the OS'es and the common icons
    in these (3 out of 7 or more) deskbars are an example of their use:

    https://i.imgur.com/fShcw31.png https://i.imgur.com/jRrwvDs.png
    https://i.imgur.com/CD8JYjm.png

    There are several such folders with different roles, another remote
    folder contains some *rc files to which links exist in those OS'es that
    share well, not others (yet). ".sylpheed-2" is one of only a dozen or
    so that links into every single OS without any issues whatsoever, .gftp
    and .profile are typical experimental ones in a very dynamic
    environment that I tinker with and proudly screw up every day but
    /.config/plasma-localerc is not such although a common
    .everything^%$%#&*$kdeinoneplace would be a real nice addition :-)

    Ok :-)



    https://i.imgur.com/R9cXaXa.png



    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to alt.os.linux.suse on Wed Jul 19 13:40:26 2023
    From Newsgroup: alt.os.linux.suse

    On 2023-07-19 13:14, bad sector wrote:
    On Wed, 19 Jul 2023 12:17:17 +0200, Carlos E.R. wrote:

    On 2023-07-18 23:34, bad sector wrote:
    On 7/18/23 14:19, Carlos E.R. wrote:
    On 2023-07-18 18:47, bad sector wrote:
    On 7/18/23 05:45, Carlos E.R. wrote:
    On 2023-07-18 01:15, bad sector wrote:
    On 7/17/23 09:01, Carlos E.R. wrote:

    Mine tries first the file "/usr/lib/locale/en_US.UTF-8/LC_TIME" >>>>>>>> which does not exist. Then it tries
    "/usr/lib/locale/en_US.utf8/LC_TIME", which in mine does exist. >>>>>>>>
    But yours is trying instead

    /usr/lib/locale/Default.UTF-8/LC_TIME
    /usr/lib/locale/Default.utf8/LC_TIME
    /usr/lib/locale/Default/LC_TIME

    which do not exist. Why is it trying those?


    When I asked you for your locale, you pasted this:

    Leap-15.5 ~ 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-a-a <=========
    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=


    That's the origin of your problem. Why do you have that?
    Find that out, and change it to a proper one, and you should be >>>>>>>> Ok.

    Also tried setting it in Yast to "en_US.UTF-8"

    On login I still get that Default.UTF-8

    did a content search on "Default.UTF-8"

    Bingo...

    ~/.config/plasma-localerc

    Aha. I thought so.

    In Artix, also with KDE :-) the file is only

    ==================
    [Formats]
    LANG=en_CA.UTF-8 ==================


    The above must have come from clicking Pangnirtung as a place just to >>>>> throw too long noses off a bit

    Ar you using the same home folder in openSUSE? Because openSUSE
    doesn't have "en_CA.UTF-8".

    I see "/usr/share/locale/en_CA", and en_GB and en_US and others, just no
    utf8 variants. Seems to be about the messages only.

    I also see

    /usr/lib/locale/en_CA /usr/lib/locale/en_CA.utf8

    today is slackware day but I mounted my Leap partition and it's the same
    here



    just not "en_CA.UTF-8", which could thus just fail.


    I'm just a passenger on this ship but it seems to me that the entire
    locale deal is gettin' a bit too 'lossy', it may be time to clean up the whorehouse, set some syntax rules and enforce them! When one is TS-ing
    and finds an output list of a dozen "en_US.UTF-8" in quotes but one that
    says en_US.utf8 and without quotes then one tends to think that that's
    where the problem is. Not so, it seems, for 'starters' :-(


    It get worse. Plasma has its own locale system, different than the rest
    of the system. You can choose a locale in settings that has no
    corresponding "locale" tree in the system. Maybe it works in native KDE
    tools, but not in others.

    And Gnome uses a different method. I believe that the file .i18n works.
    --
    Cheers, Carlos.

    --- Synchronet 3.21d-Linux NewsLink 1.2