Re: running Jami in Trixie - possible locale issue

2024-02-27 Thread Max Nikulin 

On 27/02/2024 20:59, Gary Dale wrote:


The en_GB seems to be coming from Plasma 5's Region & Language settings. 
However I see the message that it is "unsupported", which seems 
appropriate.


en_GB is missed in the output of "locale -a" you posted. I have no idea 
if it is intended or not. It can be generated from "dpkg-reconfigure 
locales".


Maybe you choose this locale earlier on the login screen, maybe selected 
in KDE system settings.


User-specific locale settings maybe saved in
- ~/.config/plasma-localerc
- ~/.dmrc
- I am unsure concerning ~/.config/locale.conf
- AccontsService

 busctl get-property org.freedesktop.Accounts \
 /org/freedesktop/Accounts/User1000 \
 org.freedesktop.Accounts.User Language

(with proper UID and in "id" output)

I expect that you should be able to configure locale in KDE regional 
settings.


My guess is that iu_CA.UTF-8 appeared due to click on a wrong option in 
a drop-down list.


To have spellcheck options you need to install dictionaries.

Re: running Jami in Trixie - possible locale issue

2024-02-27 Thread Gary Dale 

On 2024-02-26 22:47, Greg Wooledge wrote:

On Mon, Feb 26, 2024 at 10:10:45PM -0500, Gremlin wrote:

On 2/26/24 20:28, Gary Dale wrote:

$locale
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

LANG=iu_CA.UTF-8
LANGUAGE=en_GB
LC_CTYPE="iu_CA.UTF-8"
LC_NUMERIC=en_CA.UTF-8
LC_TIME=en_CA.UTF-8
LC_COLLATE=en_CA.UTF-8
LC_MONETARY=en_CA.UTF-8
LC_MESSAGES="iu_CA.UTF-8"
LC_PAPER="iu_CA.UTF-8"
LC_NAME="iu_CA.UTF-8"
LC_ADDRESS="iu_CA.UTF-8"
LC_TELEPHONE="iu_CA.UTF-8"
LC_MEASUREMENT=en_CA.UTF-8
LC_IDENTIFICATION="iu_CA.UTF-8"
LC_ALL=

$locale -a
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

C
C.utf8
en_CA.utf8
en_US.utf8
fr_CA.utf8
POSIX



Find out where LC_CTYPE and LC_MESSAGES is being set, they need changed.

No, you're not reading it correctly. Look at LANG. Look at the double
quotes around LC_CTYPE and LC_MESSAGES (among others). LC_CTYPE and
LC_MESSAGES are *not* set. They are deduced from LANG.

It's LANG that has the weird setting. All of the other iu_CA entries
are double-quoted, so they are derived from it.


If it was me, I would set /etc/default/locale to
# File generated by update-locale
LANG=C.UTF-8

and remove all references/assignments to any LC_ in all shell
config files.

then reboot and do a locale -a

Rebooting doesn't do anything useful here. Simply logging out and back
in would be sufficient.

But there are two points of view here:

1) Why is Gary using locales that are not generated?

2) Why is Gary using *these specific* locales?

I think you're approaching it from the point of view of "your settings
are wrong, but you don't know where the settings are coming from, so
find out, and fix them". Which is one valid POV.

Another valid POV is "the settings are set the way Gary wants them, but
the locales aren't generated, so generate them, and then it'll work".

Only Gary can tell us which of these is the right approach. Maybe he's
a fluent Inuktitut speaker. All I can say is that it's hard to believe
that someone would *accidentally* have LANG set to iu_CA.UTF-8. Usually
that's the kind of thing one would remember doing.


The only unusual thing I've done was trying to set the locale to en_CA 
rather than en_US. However my installation dates back a long time and 
Linux has changed a lot over the years. At one point, I believe support 
for Canadian English was spotty so I had a en_GB locale added. The iu_CA 
is weird and seems to vanish when I set the default locale to C.


But no, I've never gone beyond dpkg-reconfigure locales and the GUI 
settings for locales - other than yesterday trying to force en_CA in 
.bash_profile, which I have now removed.

Re: running Jami in Trixie - possible locale issue

2024-02-27 Thread Gary Dale 

On 2024-02-26 22:47, Greg Wooledge wrote:

On Mon, Feb 26, 2024 at 10:10:45PM -0500, Gremlin wrote:

On 2/26/24 20:28, Gary Dale wrote:

$locale
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
LANG=iu_CA.UTF-8
LANGUAGE=en_GB
LC_CTYPE="iu_CA.UTF-8"
LC_NUMERIC=en_CA.UTF-8
LC_TIME=en_CA.UTF-8
LC_COLLATE=en_CA.UTF-8
LC_MONETARY=en_CA.UTF-8
LC_MESSAGES="iu_CA.UTF-8"
LC_PAPER="iu_CA.UTF-8"
LC_NAME="iu_CA.UTF-8"
LC_ADDRESS="iu_CA.UTF-8"
LC_TELEPHONE="iu_CA.UTF-8"
LC_MEASUREMENT=en_CA.UTF-8
LC_IDENTIFICATION="iu_CA.UTF-8"
LC_ALL=

$locale -a
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
C
C.utf8
en_CA.utf8
en_US.utf8
fr_CA.utf8
POSIX



Find out where LC_CTYPE and LC_MESSAGES is being set, they need changed.

No, you're not reading it correctly.  Look at LANG.  Look at the double
quotes around LC_CTYPE and LC_MESSAGES (among others).  LC_CTYPE and
LC_MESSAGES are *not* set.  They are deduced from LANG.

It's LANG that has the weird setting.  All of the other iu_CA entries
are double-quoted, so they are derived from it.


If it was me, I would set /etc/default/locale to
#  File generated by update-locale
LANG=C.UTF-8

and remove all references/assignments to any LC_ in all shell
config files.

then reboot and do a locale -a

Rebooting doesn't do anything useful here.  Simply logging out and back
in would be sufficient.

But there are two points of view here:

1) Why is Gary using locales that are not generated?

2) Why is Gary using *these specific* locales?

I think you're approaching it from the point of view of "your settings
are wrong, but you don't know where the settings are coming from, so
find out, and fix them".  Which is one valid POV.

Another valid POV is "the settings are set the way Gary wants them, but
the locales aren't generated, so generate them, and then it'll work".

Only Gary can tell us which of these is the right approach.  Maybe he's
a fluent Inuktitut speaker.  All I can say is that it's hard to believe
that someone would *accidentally* have LANG set to iu_CA.UTF-8.  Usually
that's the kind of thing one would remember doing.


The only unusual thing I've done was trying to set the locale to en_CA 
rather than en_US. However my installation dates back a long time and 
Linux has changed a lot over the years. At one point, I believe support 
for Canadian English was spotty so I had a en_GB locale added. The iu_CA 
is weird and seems to vanish when I set the default locale to C.


But no, I've never gone beyond

Re: running Jami in Trixie - possible locale issue

2024-02-27 Thread Gary Dale 

On 2024-02-26 22:10, Gremlin wrote:

On 2/26/24 20:28, Gary Dale wrote:

On 2024-02-26 17:31, Gremlin wrote:

On 2/26/24 17:18, Gary Dale wrote:

On 2024-02-26 16:03, Gremlin wrote:

On 2/26/24 14:36, Gary Dale wrote:
I'm running Debian/Trixie on an AMD64 system. I've installed jami 
from testing but it fails to start. When I run it from the 
command line, I get:


$jami &
[1] 7804
$ Using Qt runtime version: 6.
4.2
"notify server name: Plasma, vendor: KDE, version: 5.27.10, spec: 
1.2"

"Using locale: en_GB"
terminate called after throwing an instance of 'std::runtime_error'
  what():  locale::facet::_S_create_c_locale name not valid

[1]+  Aborted (core dumped) jami
garydale@transponder:~/mnt/archives/2024/Lions Cl


There might be something wrong with my locales but 
dpkg-reconfigure locales doesn't fix it. After running it, I 
still get this output:


$locale
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

LANG=iu_CA.UTF-8
LANGUAGE=en_GB
LC_CTYPE="iu_CA.UTF-8"
LC_NUMERIC=en_CA.UTF-8
LC_TIME=en_CA.UTF-8
LC_COLLATE=en_CA.UTF-8
LC_MONETARY=en_CA.UTF-8
LC_MESSAGES="iu_CA.UTF-8"
LC_PAPER="iu_CA.UTF-8"
LC_NAME="iu_CA.UTF-8"
LC_ADDRESS="iu_CA.UTF-8"
LC_TELEPHONE="iu_CA.UTF-8"
LC_MEASUREMENT=en_CA.UTF-8
LC_IDENTIFICATION="iu_CA.UTF-8"
LC_ALL=

Please note that I have not selected iu_CA.utf8 nor en_GB in my 
locales.


Any ideas on how to fix this?

Thanks.



Edit /etc/locale.gen and enable the locale(s) you wish to use.
Then as root

locale-gen
dpkg-reconfigure locales

Nope. /etc/locale.gen was already correct. Running the commands 
then rebooting leaves me with the same error messages.


I also set up a ~/.bash_profile to set LANG to en_CA.UTF-8 but that 
also had no effect. The exact contents are:


LANG="en_CA.UTF-8"
export LANG




You are making a mess, when about to make a mess stop until you have 
researched your issue.


Start at the beginning not at the end..

Did you reboot or logout and login

dpkg-reconfigure locales is suppose to set /etc/default/locales 
correctly, it runs update-locale if I remember correctly.


cat /etc/locale.gen

# This file lists locales that you wish to have built. You can find 
a list
# of valid supported locales at /usr/share/i18n/SUPPORTED, and you 
can add
# user defined locales to /usr/local/share/i18n/SUPPORTED. If you 
change

# this file, you need to rerun locale-gen.
#

C.UTF-8 UTF-8
# aa_DJ ISO-8859-1
^^

snip

cat /etc/default/locale
#  File generated by update-locale
LANG=C.UTF-8

locale -a


I'm not making a mess, I'm trying to fix an existing mess. And yes, 
I've rebooted so many times today that I felt like I was running 
Windows.


Sure you have made a mess, the debian installer didn't select locales 
and assign them at random.


I am thinking the following will BARF also.

localectl list-locales


Sorry, but I've never touched locales except through apt/dpkg. I think 
the problem more likely relates to older locales not being properly 
removed by the upgrade/modification processes.


$ localectl list-locales
C.UTF-8
en_CA.UTF-8
en_US.UTF-8
fr_CA.UTF-8






cat /etc/default/locale
LANG=en_CA.UTF-8
LANGUAGE=en_CA:en
LC_TIME=en_CA.UTF-8

# locale -a
C
C.utf8
en_CA.utf8
en_US.utf8
fr_CA.utf8
POSIX

Also:

$locale -a
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

C
C.utf8
en_CA.utf8
en_US.utf8
fr_CA.utf8
POSIX




Find out where LC_CTYPE and LC_MESSAGES is being set, they need changed.

If it was me, I would set /etc/default/locale to
#  File generated by update-locale
LANG=C.UTF-8

and remove all references/assignments to any LC_ in all 
shell config files.


then reboot and do a locale -a


existing file before doing any changes:

$ cat /etc/default/locale
LANG=en_CA.UTF-8
LANGUAGE=en_CA:en
LC_TIME=en_CA.UTF-8

I have no idea where LC_CTYPE and LC_MESSAGES are being set. Nor do I 
understand why the LANG should be set to C rather than en_CA. However, 
when I made that change and rebooted, the errors vanished.


$ locale -a
C
C.utf8
en_CA.utf8
en_US.utf8
fr_CA.utf8
POSIX

$ locale
LANG=en_US.UTF-8
LANGUAGE=en_US
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=en_CA.UTF-8
LC_TIME=en_CA.UTF-8
LC_COLLATE=en_CA.UTF-8
LC_MONETARY=en_CA.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_CA.UTF-8
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=


I can now successfully run jami!

Thanks.

Re: running Jami in Trixie - possible locale issue

2024-02-27 Thread Gary Dale 

On 2024-02-26 21:29, Max Nikulin wrote:

  env | grep 'LC_\|LANG'
    systemctl --user show-environment | grep 'LC_\|LANG'



 $ env | grep 'LC_\|LANG'
LANGUAGE=en_GB
LC_MONETARY=en_CA.UTF-8
LANG=iu_CA.UTF-8
LC_MEASUREMENT=en_CA.UTF-8
LC_TIME=en_CA.UTF-8
LC_COLLATE=en_CA.UTF-8
LC_NUMERIC=en_CA.UTF-8

$ systemctl --user show-environment | grep 'LC_\|LANG'
LANG=iu_CA.UTF-8
LANGUAGE=en_GB
LC_TIME=en_CA.UTF-8
LC_COLLATE=en_CA.UTF-8
LC_MEASUREMENT=en_CA.UTF-8
LC_MONETARY=en_CA.UTF-8
LC_NUMERIC=en_CA.UTF-8

They agree.

The en_GB seems to be coming from Plasma 5's Region & Language settings. 
However I see the message that it is "unsupported", which seems 
appropriate. When I change it to American English, the en_GB disappears 
from the available settings. When I try to "Add More...", I'm only given 
the options of "C" and "American English", neither of which I want. 
However the Spellcheck options do allow for English (Canada).

Re: running Jami in Trixie - possible locale issue

2024-02-27 Thread Greg Wooledge 
On Tue, Feb 27, 2024 at 08:48:27AM -0500, Gary Dale wrote:
> > You've got three different locales mentioned here:
> > 
> > iu_CA.UTF-8
> > en_GB
> > en_CA.UTF-8
> > 
> > Either generate the two that you're missing, or stop using them.
> 
> I'm trying to stop using them. That's the point. How do I get rid of them?
> They show up no matter how many times I reconfigure my locales.

OK.  Start from the beginning.

How do you login to this computer?  SSH?  Text console?  Graphical
display manager?  (Which one?)

Do you run a desktop environment?  If so, which one?  Do you run some
command to start it, like startx, or is it started by your DM login?

If you're using a text console login or an ssh login, what shell do
you use?  Bash, zsh, tcsh, ...?

If you're using an ssh login, what do your locales look like on the
client system, before you ssh to the Debian system?

If you don't *normally* use a text console login, try doing one.  Press
Ctrl-Alt-F2, and then login on tty2, and see what your locales are.
In this login session, you *only* have variables that are set up by PAM
and your login shell.  If you see the undesired variables here, then
you know it's coming from one of those two places.

If you don't see the undesired variables in the text console login,
then they're coming from somewhere else -- from the client system, if
this is an ssh login, or from your desktop environment, etc.

Re: running Jami in Trixie - possible locale issue

2024-02-27 Thread Gary Dale 

On 2024-02-26 20:43, Greg Wooledge wrote:

On Mon, Feb 26, 2024 at 08:28:01PM -0500, Gary Dale wrote:

$locale
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
LANG=iu_CA.UTF-8
LANGUAGE=en_GB
LC_CTYPE="iu_CA.UTF-8"
LC_NUMERIC=en_CA.UTF-8
LC_TIME=en_CA.UTF-8
LC_COLLATE=en_CA.UTF-8
LC_MONETARY=en_CA.UTF-8
LC_MESSAGES="iu_CA.UTF-8"
LC_PAPER="iu_CA.UTF-8"
LC_NAME="iu_CA.UTF-8"
LC_ADDRESS="iu_CA.UTF-8"
LC_TELEPHONE="iu_CA.UTF-8"
LC_MEASUREMENT=en_CA.UTF-8
LC_IDENTIFICATION="iu_CA.UTF-8"
LC_ALL=

You've got three different locales mentioned here:

iu_CA.UTF-8
en_GB
en_CA.UTF-8


# locale -a
C
C.utf8
en_CA.utf8
en_US.utf8
fr_CA.utf8
POSIX

Out of the three that you're trying to use, only one has been generated.

Either generate the two that you're missing, or stop using them.


I'm trying to stop using them. That's the point. How do I get rid of 
them? They show up no matter how many times I reconfigure my locales.

Re: running Jami in Trixie - possible locale issue

2024-02-27 Thread Gremlin 

On 2/26/24 22:47, Greg Wooledge wrote:

On Mon, Feb 26, 2024 at 10:10:45PM -0500, Gremlin wrote:

On 2/26/24 20:28, Gary Dale wrote:

$locale
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
LANG=iu_CA.UTF-8
LANGUAGE=en_GB
LC_CTYPE="iu_CA.UTF-8"
LC_NUMERIC=en_CA.UTF-8
LC_TIME=en_CA.UTF-8
LC_COLLATE=en_CA.UTF-8
LC_MONETARY=en_CA.UTF-8
LC_MESSAGES="iu_CA.UTF-8"
LC_PAPER="iu_CA.UTF-8"
LC_NAME="iu_CA.UTF-8"
LC_ADDRESS="iu_CA.UTF-8"
LC_TELEPHONE="iu_CA.UTF-8"
LC_MEASUREMENT=en_CA.UTF-8
LC_IDENTIFICATION="iu_CA.UTF-8"
LC_ALL=



$locale -a
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
C
C.utf8
en_CA.utf8
en_US.utf8
fr_CA.utf8
POSIX




Find out where LC_CTYPE and LC_MESSAGES is being set, they need changed.


No, you're not reading it correctly.  Look at LANG.  Look at the double
quotes around LC_CTYPE and LC_MESSAGES (among others).  LC_CTYPE and
LC_MESSAGES are *not* set.  They are deduced from LANG.

It's LANG that has the weird setting.  All of the other iu_CA entries
are double-quoted, so they are derived from it.


If it was me, I would set /etc/default/locale to
#  File generated by update-locale
LANG=C.UTF-8

and remove all references/assignments to any LC_ in all shell
config files.

then reboot and do a locale -a


Rebooting doesn't do anything useful here.  Simply logging out and back
in would be sufficient.

But there are two points of view here:

1) Why is Gary using locales that are not generated?

2) Why is Gary using *these specific* locales?

I think you're approaching it from the point of view of "your settings
are wrong, but you don't know where the settings are coming from, so
find out, and fix them".  Which is one valid POV.

Another valid POV is "the settings are set the way Gary wants them, but
the locales aren't generated, so generate them, and then it'll work".

Only Gary can tell us which of these is the right approach.  Maybe he's
a fluent Inuktitut speaker.  All I can say is that it's hard to believe
that someone would *accidentally* have LANG set to iu_CA.UTF-8.  Usually
that's the kind of thing one would remember doing.




My point was to restore the "base system" to a known working point then 
then start the desktop and examine the issue.  Then you can properly set 
the locale you wish to use and it should work.


By not starting from a known point you are shooting in the dark hoping 
you will hit the right thing.  That almost never works.


Anyway I am done with this.

Re: running Jami in Trixie - possible locale issue

2024-02-26 Thread Greg Wooledge 
On Mon, Feb 26, 2024 at 10:10:45PM -0500, Gremlin wrote:
> On 2/26/24 20:28, Gary Dale wrote:
> > > > > > $locale
> > > > > > 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
> > > > > > LANG=iu_CA.UTF-8
> > > > > > LANGUAGE=en_GB
> > > > > > LC_CTYPE="iu_CA.UTF-8"
> > > > > > LC_NUMERIC=en_CA.UTF-8
> > > > > > LC_TIME=en_CA.UTF-8
> > > > > > LC_COLLATE=en_CA.UTF-8
> > > > > > LC_MONETARY=en_CA.UTF-8
> > > > > > LC_MESSAGES="iu_CA.UTF-8"
> > > > > > LC_PAPER="iu_CA.UTF-8"
> > > > > > LC_NAME="iu_CA.UTF-8"
> > > > > > LC_ADDRESS="iu_CA.UTF-8"
> > > > > > LC_TELEPHONE="iu_CA.UTF-8"
> > > > > > LC_MEASUREMENT=en_CA.UTF-8
> > > > > > LC_IDENTIFICATION="iu_CA.UTF-8"
> > > > > > LC_ALL=

> > $locale -a
> > 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
> > C
> > C.utf8
> > en_CA.utf8
> > en_US.utf8
> > fr_CA.utf8
> > POSIX
> > 
> > 
> 
> Find out where LC_CTYPE and LC_MESSAGES is being set, they need changed.

No, you're not reading it correctly.  Look at LANG.  Look at the double
quotes around LC_CTYPE and LC_MESSAGES (among others).  LC_CTYPE and
LC_MESSAGES are *not* set.  They are deduced from LANG.

It's LANG that has the weird setting.  All of the other iu_CA entries
are double-quoted, so they are derived from it.

> If it was me, I would set /etc/default/locale to
> #  File generated by update-locale
> LANG=C.UTF-8
> 
> and remove all references/assignments to any LC_ in all shell
> config files.
> 
> then reboot and do a locale -a

Rebooting doesn't do anything useful here.  Simply logging out and back
in would be sufficient.

But there are two points of view here:

1) Why is Gary using locales that are not generated?

2) Why is Gary using *these specific* locales?

I think you're approaching it from the point of view of "your settings
are wrong, but you don't know where the settings are coming from, so
find out, and fix them".  Which is one valid POV.

Another valid POV is "the settings are set the way Gary wants them, but
the locales aren't generated, so generate them, and then it'll work".

Only Gary can tell us which of these is the right approach.  Maybe he's
a fluent Inuktitut speaker.  All I can say is that it's hard to believe
that someone would *accidentally* have LANG set to iu_CA.UTF-8.  Usually
that's the kind of thing one would remember doing.

Re: running Jami in Trixie - possible locale issue

2024-02-26 Thread Gremlin 

On 2/26/24 20:28, Gary Dale wrote:

On 2024-02-26 17:31, Gremlin wrote:

On 2/26/24 17:18, Gary Dale wrote:

On 2024-02-26 16:03, Gremlin wrote:

On 2/26/24 14:36, Gary Dale wrote:
I'm running Debian/Trixie on an AMD64 system. I've installed jami 
from testing but it fails to start. When I run it from the command 
line, I get:


$jami &
[1] 7804
$ Using Qt runtime version: 6.
4.2
"notify server name: Plasma, vendor: KDE, version: 5.27.10, spec: 1.2"
"Using locale: en_GB"
terminate called after throwing an instance of 'std::runtime_error'
  what():  locale::facet::_S_create_c_locale name not valid

[1]+  Aborted (core dumped) jami
garydale@transponder:~/mnt/archives/2024/Lions Cl


There might be something wrong with my locales but dpkg-reconfigure 
locales doesn't fix it. After running it, I still get this output:


$locale
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
LANG=iu_CA.UTF-8
LANGUAGE=en_GB
LC_CTYPE="iu_CA.UTF-8"
LC_NUMERIC=en_CA.UTF-8
LC_TIME=en_CA.UTF-8
LC_COLLATE=en_CA.UTF-8
LC_MONETARY=en_CA.UTF-8
LC_MESSAGES="iu_CA.UTF-8"
LC_PAPER="iu_CA.UTF-8"
LC_NAME="iu_CA.UTF-8"
LC_ADDRESS="iu_CA.UTF-8"
LC_TELEPHONE="iu_CA.UTF-8"
LC_MEASUREMENT=en_CA.UTF-8
LC_IDENTIFICATION="iu_CA.UTF-8"
LC_ALL=

Please note that I have not selected iu_CA.utf8 nor en_GB in my 
locales.


Any ideas on how to fix this?

Thanks.



Edit /etc/locale.gen and enable the locale(s) you wish to use.
Then as root

locale-gen
dpkg-reconfigure locales

Nope. /etc/locale.gen was already correct. Running the commands then 
rebooting leaves me with the same error messages.


I also set up a ~/.bash_profile to set LANG to en_CA.UTF-8 but that 
also had no effect. The exact contents are:


LANG="en_CA.UTF-8"
export LANG




You are making a mess, when about to make a mess stop until you have 
researched your issue.


Start at the beginning not at the end..

Did you reboot or logout and login

dpkg-reconfigure locales is suppose to set /etc/default/locales 
correctly, it runs update-locale if I remember correctly.


cat /etc/locale.gen

# This file lists locales that you wish to have built. You can find a 
list
# of valid supported locales at /usr/share/i18n/SUPPORTED, and you can 
add

# user defined locales to /usr/local/share/i18n/SUPPORTED. If you change
# this file, you need to rerun locale-gen.
#

C.UTF-8 UTF-8
# aa_DJ ISO-8859-1
# aa_DJ.UTF-8 UTF-8
# aa_ER UTF-8
# aa_ER@saaho UTF-8
# aa_ET UTF-8
# af_ZA ISO-8859-1
# af_ZA.UTF-8 UTF-8
# agr_PE UTF-8
# ak_GH UTF-8
# am_ET UTF-8
# an_ES ISO-8859-15
# an_ES.UTF-8 UTF-8
# anp_IN UTF-8
# ar_AE ISO-8859-6
# ar_AE.UTF-8 UTF-8
# ar_BH ISO-8859-6
# ar_BH.UTF-8 UTF-8
# ar_DZ ISO-8859-6
# ar_DZ.UTF-8 UTF-8
# ar_EG ISO-8859-6
# ar_EG.UTF-8 UTF-8
# ar_IN UTF-8
# ar_IQ ISO-8859-6
# ar_IQ.UTF-8 UTF-8
# ar_JO ISO-8859-6
# ar_JO.UTF-8 UTF-8
# ar_KW ISO-8859-6
# ar_KW.UTF-8 UTF-8
# ar_LB ISO-8859-6
# ar_LB.UTF-8 UTF-8
# ar_LY ISO-8859-6
# ar_LY.UTF-8 UTF-8
# ar_MA ISO-8859-6
# ar_MA.UTF-8 UTF-8
# ar_OM ISO-8859-6
# ar_OM.UTF-8 UTF-8
# ar_QA ISO-8859-6
# ar_QA.UTF-8 UTF-8
# ar_SA ISO-8859-6
# ar_SA.UTF-8 UTF-8
# ar_SD ISO-8859-6
# ar_SD.UTF-8 UTF-8
# ar_SS UTF-8
# ar_SY ISO-8859-6
# ar_SY.UTF-8 UTF-8
# ar_TN ISO-8859-6
# ar_TN.UTF-8 UTF-8
# ar_YE ISO-8859-6
# ar_YE.UTF-8 UTF-8
# as_IN UTF-8
# ast_ES ISO-8859-15
# ast_ES.UTF-8 UTF-8
# ayc_PE UTF-8
# az_AZ UTF-8
# az_IR UTF-8
# be_BY CP1251
# be_BY.UTF-8 UTF-8
# be_BY@latin UTF-8
# bem_ZM UTF-8
# ber_DZ UTF-8
# ber_MA UTF-8
# bg_BG CP1251
# bg_BG.UTF-8 UTF-8
# bhb_IN.UTF-8 UTF-8
# bho_IN UTF-8
# bho_NP UTF-8
# bi_VU UTF-8
# bn_BD UTF-8
# bn_IN UTF-8
# bo_CN UTF-8
# bo_IN UTF-8
# br_FR ISO-8859-1
# br_FR.UTF-8 UTF-8
# br_FR@euro ISO-8859-15
# brx_IN UTF-8
# bs_BA ISO-8859-2
# bs_BA.UTF-8 UTF-8
# byn_ER UTF-8
# ca_AD ISO-8859-15
# ca_AD.UTF-8 UTF-8
# ca_ES ISO-8859-1
# ca_ES.UTF-8 UTF-8
# ca_ES@euro ISO-8859-15
# ca_ES@valencia UTF-8
# ca_FR ISO-8859-15
# ca_FR.UTF-8 UTF-8
# ca_IT ISO-8859-15
# ca_IT.UTF-8 UTF-8
# ce_RU UTF-8
# chr_US UTF-8
# ckb_IQ UTF-8
# cmn_TW UTF-8
# crh_UA UTF-8
# cs_CZ ISO-8859-2
# cs_CZ.UTF-8 UTF-8
# csb_PL UTF-8
# cv_RU UTF-8
# cy_GB ISO-8859-14
# cy_GB.UTF-8 UTF-8
# da_DK ISO-8859-1
# da_DK.UTF-8 UTF-8
# de_AT ISO-8859-1
# de_AT.UTF-8 UTF-8
# de_AT@euro ISO-8859-15
# de_BE ISO-8859-1
# de_BE.UTF-8 UTF-8
# de_BE@euro ISO-8859-15
# de_CH ISO-8859-1
# de_CH.UTF-8 UTF-8
# de_DE ISO-8859-1
# de_DE.UTF-8 UTF-8
# de_DE@euro ISO-8859-15
# de_IT ISO-8859-1
# de_IT.UTF-8 UTF-8
# de_LI.UTF-8 UTF-8
# de_LU ISO-8859-1
# de_LU.UTF-8 UTF-8
# de_LU@euro ISO-8859-15
# doi_IN UTF-8
# dsb_DE UTF-8
# dv_MV UTF-8
# dz_BT UTF-8
# el_CY ISO-8859-7
# el_CY.UTF-8 UTF-8
# el_GR ISO-8859-7
# el_GR.UTF-8 UTF-8
# el_GR@euro ISO-8859-7
# en_AG UTF-8
# en_AU ISO-8859-1
# en_AU.UTF-8 UTF-8
# en_BW ISO-8859-1
# en_BW.UTF-8 UTF-8
# en_CA ISO-8859-1
# en_CA.UTF-8

Re: running Jami in Trixie - possible locale issue

2024-02-26 Thread Max Nikulin 

On 27/02/2024 08:28, Gary Dale wrote:

$locale -a
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


What desktop environment do you use? Have you checked its settings? Did 
you choose locale in your display manager (in login dialog)?


Inspect actual environment

env | grep 'LC_\|LANG'
systemctl --user show-environment | grep 'LC_\|LANG'

Re: running Jami in Trixie - possible locale issue

2024-02-26 Thread Greg Wooledge 
On Mon, Feb 26, 2024 at 08:28:01PM -0500, Gary Dale wrote:
> > > > > $locale
> > > > > 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
> > > > > LANG=iu_CA.UTF-8
> > > > > LANGUAGE=en_GB
> > > > > LC_CTYPE="iu_CA.UTF-8"
> > > > > LC_NUMERIC=en_CA.UTF-8
> > > > > LC_TIME=en_CA.UTF-8
> > > > > LC_COLLATE=en_CA.UTF-8
> > > > > LC_MONETARY=en_CA.UTF-8
> > > > > LC_MESSAGES="iu_CA.UTF-8"
> > > > > LC_PAPER="iu_CA.UTF-8"
> > > > > LC_NAME="iu_CA.UTF-8"
> > > > > LC_ADDRESS="iu_CA.UTF-8"
> > > > > LC_TELEPHONE="iu_CA.UTF-8"
> > > > > LC_MEASUREMENT=en_CA.UTF-8
> > > > > LC_IDENTIFICATION="iu_CA.UTF-8"
> > > > > LC_ALL=

You've got three different locales mentioned here:

iu_CA.UTF-8
en_GB
en_CA.UTF-8

> # locale -a
> C
> C.utf8
> en_CA.utf8
> en_US.utf8
> fr_CA.utf8
> POSIX

Out of the three that you're trying to use, only one has been generated.

Either generate the two that you're missing, or stop using them.

Re: running Jami in Trixie - possible locale issue

2024-02-26 Thread Gary Dale 

On 2024-02-26 17:31, Gremlin wrote:

On 2/26/24 17:18, Gary Dale wrote:

On 2024-02-26 16:03, Gremlin wrote:

On 2/26/24 14:36, Gary Dale wrote:
I'm running Debian/Trixie on an AMD64 system. I've installed jami 
from testing but it fails to start. When I run it from the command 
line, I get:


$jami &
[1] 7804
$ Using Qt runtime version: 6.
4.2
"notify server name: Plasma, vendor: KDE, version: 5.27.10, spec: 1.2"
"Using locale: en_GB"
terminate called after throwing an instance of 'std::runtime_error'
  what():  locale::facet::_S_create_c_locale name not valid

[1]+  Aborted (core dumped) jami
garydale@transponder:~/mnt/archives/2024/Lions Cl


There might be something wrong with my locales but dpkg-reconfigure 
locales doesn't fix it. After running it, I still get this output:


$locale
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
LANG=iu_CA.UTF-8
LANGUAGE=en_GB
LC_CTYPE="iu_CA.UTF-8"
LC_NUMERIC=en_CA.UTF-8
LC_TIME=en_CA.UTF-8
LC_COLLATE=en_CA.UTF-8
LC_MONETARY=en_CA.UTF-8
LC_MESSAGES="iu_CA.UTF-8"
LC_PAPER="iu_CA.UTF-8"
LC_NAME="iu_CA.UTF-8"
LC_ADDRESS="iu_CA.UTF-8"
LC_TELEPHONE="iu_CA.UTF-8"
LC_MEASUREMENT=en_CA.UTF-8
LC_IDENTIFICATION="iu_CA.UTF-8"
LC_ALL=

Please note that I have not selected iu_CA.utf8 nor en_GB in my 
locales.


Any ideas on how to fix this?

Thanks.



Edit /etc/locale.gen and enable the locale(s) you wish to use.
Then as root

locale-gen
dpkg-reconfigure locales

Nope. /etc/locale.gen was already correct. Running the commands then 
rebooting leaves me with the same error messages.


I also set up a ~/.bash_profile to set LANG to en_CA.UTF-8 but that 
also had no effect. The exact contents are:


LANG="en_CA.UTF-8"
export LANG




You are making a mess, when about to make a mess stop until you have 
researched your issue.


Start at the beginning not at the end..

Did you reboot or logout and login

dpkg-reconfigure locales is suppose to set /etc/default/locales 
correctly, it runs update-locale if I remember correctly.


cat /etc/locale.gen

# This file lists locales that you wish to have built. You can find a 
list
# of valid supported locales at /usr/share/i18n/SUPPORTED, and you can 
add

# user defined locales to /usr/local/share/i18n/SUPPORTED. If you change
# this file, you need to rerun locale-gen.
#

C.UTF-8 UTF-8
# aa_DJ ISO-8859-1
# aa_DJ.UTF-8 UTF-8
# aa_ER UTF-8
# aa_ER@saaho UTF-8
# aa_ET UTF-8
# af_ZA ISO-8859-1
# af_ZA.UTF-8 UTF-8
# agr_PE UTF-8
# ak_GH UTF-8
# am_ET UTF-8
# an_ES ISO-8859-15
# an_ES.UTF-8 UTF-8
# anp_IN UTF-8
# ar_AE ISO-8859-6
# ar_AE.UTF-8 UTF-8
# ar_BH ISO-8859-6
# ar_BH.UTF-8 UTF-8
# ar_DZ ISO-8859-6
# ar_DZ.UTF-8 UTF-8
# ar_EG ISO-8859-6
# ar_EG.UTF-8 UTF-8
# ar_IN UTF-8
# ar_IQ ISO-8859-6
# ar_IQ.UTF-8 UTF-8
# ar_JO ISO-8859-6
# ar_JO.UTF-8 UTF-8
# ar_KW ISO-8859-6
# ar_KW.UTF-8 UTF-8
# ar_LB ISO-8859-6
# ar_LB.UTF-8 UTF-8
# ar_LY ISO-8859-6
# ar_LY.UTF-8 UTF-8
# ar_MA ISO-8859-6
# ar_MA.UTF-8 UTF-8
# ar_OM ISO-8859-6
# ar_OM.UTF-8 UTF-8
# ar_QA ISO-8859-6
# ar_QA.UTF-8 UTF-8
# ar_SA ISO-8859-6
# ar_SA.UTF-8 UTF-8
# ar_SD ISO-8859-6
# ar_SD.UTF-8 UTF-8
# ar_SS UTF-8
# ar_SY ISO-8859-6
# ar_SY.UTF-8 UTF-8
# ar_TN ISO-8859-6
# ar_TN.UTF-8 UTF-8
# ar_YE ISO-8859-6
# ar_YE.UTF-8 UTF-8
# as_IN UTF-8
# ast_ES ISO-8859-15
# ast_ES.UTF-8 UTF-8
# ayc_PE UTF-8
# az_AZ UTF-8
# az_IR UTF-8
# be_BY CP1251
# be_BY.UTF-8 UTF-8
# be_BY@latin UTF-8
# bem_ZM UTF-8
# ber_DZ UTF-8
# ber_MA UTF-8
# bg_BG CP1251
# bg_BG.UTF-8 UTF-8
# bhb_IN.UTF-8 UTF-8
# bho_IN UTF-8
# bho_NP UTF-8
# bi_VU UTF-8
# bn_BD UTF-8
# bn_IN UTF-8
# bo_CN UTF-8
# bo_IN UTF-8
# br_FR ISO-8859-1
# br_FR.UTF-8 UTF-8
# br_FR@euro ISO-8859-15
# brx_IN UTF-8
# bs_BA ISO-8859-2
# bs_BA.UTF-8 UTF-8
# byn_ER UTF-8
# ca_AD ISO-8859-15
# ca_AD.UTF-8 UTF-8
# ca_ES ISO-8859-1
# ca_ES.UTF-8 UTF-8
# ca_ES@euro ISO-8859-15
# ca_ES@valencia UTF-8
# ca_FR ISO-8859-15
# ca_FR.UTF-8 UTF-8
# ca_IT ISO-8859-15
# ca_IT.UTF-8 UTF-8
# ce_RU UTF-8
# chr_US UTF-8
# ckb_IQ UTF-8
# cmn_TW UTF-8
# crh_UA UTF-8
# cs_CZ ISO-8859-2
# cs_CZ.UTF-8 UTF-8
# csb_PL UTF-8
# cv_RU UTF-8
# cy_GB ISO-8859-14
# cy_GB.UTF-8 UTF-8
# da_DK ISO-8859-1
# da_DK.UTF-8 UTF-8
# de_AT ISO-8859-1
# de_AT.UTF-8 UTF-8
# de_AT@euro ISO-8859-15
# de_BE ISO-8859-1
# de_BE.UTF-8 UTF-8
# de_BE@euro ISO-8859-15
# de_CH ISO-8859-1
# de_CH.UTF-8 UTF-8
# de_DE ISO-8859-1
# de_DE.UTF-8 UTF-8
# de_DE@euro ISO-8859-15
# de_IT ISO-8859-1
# de_IT.UTF-8 UTF-8
# de_LI.UTF-8 UTF-8
# de_LU ISO-8859-1
# de_LU.UTF-8 UTF-8
# de_LU@euro ISO-8859-15
# doi_IN UTF-8
# dsb_DE UTF-8
# dv_MV UTF-8
# dz_BT UTF-8
# el_CY ISO-8859-7
# el_CY.UTF-8 UTF-8
# el_GR ISO-8859-7
# el_GR.UTF-8 UTF-8
# el_GR@euro ISO-8859-7
# en_AG UTF-8
# en_AU ISO-8859-1
# en_AU.UTF-8 UTF-8
# en_BW ISO-8859-1
# en_BW.UTF-8 UTF-8
# en_CA ISO-8859-1
# en_CA.UTF-8 UTF-8
# en_DK ISO-8859-1
#

Re: running Jami in Trixie - possible locale issue

2024-02-26 Thread Gremlin 

On 2/26/24 17:18, Gary Dale wrote:

On 2024-02-26 16:03, Gremlin wrote:

On 2/26/24 14:36, Gary Dale wrote:
I'm running Debian/Trixie on an AMD64 system. I've installed jami 
from testing but it fails to start. When I run it from the command 
line, I get:


$jami &
[1] 7804
$ Using Qt runtime version: 6.
4.2
"notify server name: Plasma, vendor: KDE, version: 5.27.10, spec: 1.2"
"Using locale: en_GB"
terminate called after throwing an instance of 'std::runtime_error'
  what():  locale::facet::_S_create_c_locale name not valid

[1]+  Aborted (core dumped) jami
garydale@transponder:~/mnt/archives/2024/Lions Cl


There might be something wrong with my locales but dpkg-reconfigure 
locales doesn't fix it. After running it, I still get this output:


$locale
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
LANG=iu_CA.UTF-8
LANGUAGE=en_GB
LC_CTYPE="iu_CA.UTF-8"
LC_NUMERIC=en_CA.UTF-8
LC_TIME=en_CA.UTF-8
LC_COLLATE=en_CA.UTF-8
LC_MONETARY=en_CA.UTF-8
LC_MESSAGES="iu_CA.UTF-8"
LC_PAPER="iu_CA.UTF-8"
LC_NAME="iu_CA.UTF-8"
LC_ADDRESS="iu_CA.UTF-8"
LC_TELEPHONE="iu_CA.UTF-8"
LC_MEASUREMENT=en_CA.UTF-8
LC_IDENTIFICATION="iu_CA.UTF-8"
LC_ALL=

Please note that I have not selected iu_CA.utf8 nor en_GB in my locales.

Any ideas on how to fix this?

Thanks.



Edit /etc/locale.gen and enable the locale(s) you wish to use.
Then as root

locale-gen
dpkg-reconfigure locales

Nope. /etc/locale.gen was already correct. Running the commands then 
rebooting leaves me with the same error messages.


I also set up a ~/.bash_profile to set LANG to en_CA.UTF-8 but that also 
had no effect. The exact contents are:


LANG="en_CA.UTF-8"
export LANG




You are making a mess, when about to make a mess stop until you have 
researched your issue.


Start at the beginning not at the end..

Did you reboot or logout and login

dpkg-reconfigure locales is suppose to set /etc/default/locales 
correctly, it runs update-locale if I remember correctly.


cat /etc/locale.gen

# This file lists locales that you wish to have built. You can find a list
# of valid supported locales at /usr/share/i18n/SUPPORTED, and you can add
# user defined locales to /usr/local/share/i18n/SUPPORTED. If you change
# this file, you need to rerun locale-gen.
#

C.UTF-8 UTF-8
# aa_DJ ISO-8859-1
# aa_DJ.UTF-8 UTF-8
# aa_ER UTF-8
# aa_ER@saaho UTF-8
# aa_ET UTF-8
# af_ZA ISO-8859-1
# af_ZA.UTF-8 UTF-8
# agr_PE UTF-8
# ak_GH UTF-8
# am_ET UTF-8
# an_ES ISO-8859-15
# an_ES.UTF-8 UTF-8
# anp_IN UTF-8
# ar_AE ISO-8859-6
# ar_AE.UTF-8 UTF-8
# ar_BH ISO-8859-6
# ar_BH.UTF-8 UTF-8
# ar_DZ ISO-8859-6
# ar_DZ.UTF-8 UTF-8
# ar_EG ISO-8859-6
# ar_EG.UTF-8 UTF-8
# ar_IN UTF-8
# ar_IQ ISO-8859-6
# ar_IQ.UTF-8 UTF-8
# ar_JO ISO-8859-6
# ar_JO.UTF-8 UTF-8
# ar_KW ISO-8859-6
# ar_KW.UTF-8 UTF-8
# ar_LB ISO-8859-6
# ar_LB.UTF-8 UTF-8
# ar_LY ISO-8859-6
# ar_LY.UTF-8 UTF-8
# ar_MA ISO-8859-6
# ar_MA.UTF-8 UTF-8
# ar_OM ISO-8859-6
# ar_OM.UTF-8 UTF-8
# ar_QA ISO-8859-6
# ar_QA.UTF-8 UTF-8
# ar_SA ISO-8859-6
# ar_SA.UTF-8 UTF-8
# ar_SD ISO-8859-6
# ar_SD.UTF-8 UTF-8
# ar_SS UTF-8
# ar_SY ISO-8859-6
# ar_SY.UTF-8 UTF-8
# ar_TN ISO-8859-6
# ar_TN.UTF-8 UTF-8
# ar_YE ISO-8859-6
# ar_YE.UTF-8 UTF-8
# as_IN UTF-8
# ast_ES ISO-8859-15
# ast_ES.UTF-8 UTF-8
# ayc_PE UTF-8
# az_AZ UTF-8
# az_IR UTF-8
# be_BY CP1251
# be_BY.UTF-8 UTF-8
# be_BY@latin UTF-8
# bem_ZM UTF-8
# ber_DZ UTF-8
# ber_MA UTF-8
# bg_BG CP1251
# bg_BG.UTF-8 UTF-8
# bhb_IN.UTF-8 UTF-8
# bho_IN UTF-8
# bho_NP UTF-8
# bi_VU UTF-8
# bn_BD UTF-8
# bn_IN UTF-8
# bo_CN UTF-8
# bo_IN UTF-8
# br_FR ISO-8859-1
# br_FR.UTF-8 UTF-8
# br_FR@euro ISO-8859-15
# brx_IN UTF-8
# bs_BA ISO-8859-2
# bs_BA.UTF-8 UTF-8
# byn_ER UTF-8
# ca_AD ISO-8859-15
# ca_AD.UTF-8 UTF-8
# ca_ES ISO-8859-1
# ca_ES.UTF-8 UTF-8
# ca_ES@euro ISO-8859-15
# ca_ES@valencia UTF-8
# ca_FR ISO-8859-15
# ca_FR.UTF-8 UTF-8
# ca_IT ISO-8859-15
# ca_IT.UTF-8 UTF-8
# ce_RU UTF-8
# chr_US UTF-8
# ckb_IQ UTF-8
# cmn_TW UTF-8
# crh_UA UTF-8
# cs_CZ ISO-8859-2
# cs_CZ.UTF-8 UTF-8
# csb_PL UTF-8
# cv_RU UTF-8
# cy_GB ISO-8859-14
# cy_GB.UTF-8 UTF-8
# da_DK ISO-8859-1
# da_DK.UTF-8 UTF-8
# de_AT ISO-8859-1
# de_AT.UTF-8 UTF-8
# de_AT@euro ISO-8859-15
# de_BE ISO-8859-1
# de_BE.UTF-8 UTF-8
# de_BE@euro ISO-8859-15
# de_CH ISO-8859-1
# de_CH.UTF-8 UTF-8
# de_DE ISO-8859-1
# de_DE.UTF-8 UTF-8
# de_DE@euro ISO-8859-15
# de_IT ISO-8859-1
# de_IT.UTF-8 UTF-8
# de_LI.UTF-8 UTF-8
# de_LU ISO-8859-1
# de_LU.UTF-8 UTF-8
# de_LU@euro ISO-8859-15
# doi_IN UTF-8
# dsb_DE UTF-8
# dv_MV UTF-8
# dz_BT UTF-8
# el_CY ISO-8859-7
# el_CY.UTF-8 UTF-8
# el_GR ISO-8859-7
# el_GR.UTF-8 UTF-8
# el_GR@euro ISO-8859-7
# en_AG UTF-8
# en_AU ISO-8859-1
# en_AU.UTF-8 UTF-8
# en_BW ISO-8859-1
# en_BW.UTF-8 UTF-8
# en_CA ISO-8859-1
# en_CA.UTF-8 UTF-8
# en_DK ISO-8859-1
# en_DK.ISO-8859-15 ISO-8859-15
# en_DK.UTF-8 UTF-8
#

Re: running Jami in Trixie - possible locale issue

2024-02-26 Thread Gary Dale 

On 2024-02-26 16:03, Gremlin wrote:

On 2/26/24 14:36, Gary Dale wrote:
I'm running Debian/Trixie on an AMD64 system. I've installed jami 
from testing but it fails to start. When I run it from the command 
line, I get:


$jami &
[1] 7804
$ Using Qt runtime version: 6.
4.2
"notify server name: Plasma, vendor: KDE, version: 5.27.10, spec: 1.2"
"Using locale: en_GB"
terminate called after throwing an instance of 'std::runtime_error'
  what():  locale::facet::_S_create_c_locale name not valid

[1]+  Aborted (core dumped) jami
garydale@transponder:~/mnt/archives/2024/Lions Cl


There might be something wrong with my locales but dpkg-reconfigure 
locales doesn't fix it. After running it, I still get this output:


$locale
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
LANG=iu_CA.UTF-8
LANGUAGE=en_GB
LC_CTYPE="iu_CA.UTF-8"
LC_NUMERIC=en_CA.UTF-8
LC_TIME=en_CA.UTF-8
LC_COLLATE=en_CA.UTF-8
LC_MONETARY=en_CA.UTF-8
LC_MESSAGES="iu_CA.UTF-8"
LC_PAPER="iu_CA.UTF-8"
LC_NAME="iu_CA.UTF-8"
LC_ADDRESS="iu_CA.UTF-8"
LC_TELEPHONE="iu_CA.UTF-8"
LC_MEASUREMENT=en_CA.UTF-8
LC_IDENTIFICATION="iu_CA.UTF-8"
LC_ALL=

Please note that I have not selected iu_CA.utf8 nor en_GB in my locales.

Any ideas on how to fix this?

Thanks.



Edit /etc/locale.gen and enable the locale(s) you wish to use.
Then as root

locale-gen
dpkg-reconfigure locales

Nope. /etc/locale.gen was already correct. Running the commands then 
rebooting leaves me with the same error messages.


I also set up a ~/.bash_profile to set LANG to en_CA.UTF-8 but that also 
had no effect. The exact contents are:


LANG="en_CA.UTF-8"
export LANG

Re: running Jami in Trixie - possible locale issue

2024-02-26 Thread Gremlin 

On 2/26/24 14:36, Gary Dale wrote:
I'm running Debian/Trixie on an AMD64 system. I've installed jami from 
testing but it fails to start. When I run it from the command line, I get:


$jami &
[1] 7804
$ Using Qt runtime version: 6.
4.2
"notify server name: Plasma, vendor: KDE, version: 5.27.10, spec: 1.2"
"Using locale: en_GB"
terminate called after throwing an instance of 'std::runtime_error'
  what():  locale::facet::_S_create_c_locale name not valid

[1]+  Aborted (core dumped) jami
garydale@transponder:~/mnt/archives/2024/Lions Cl


There might be something wrong with my locales but dpkg-reconfigure 
locales doesn't fix it. After running it, I still get this output:


$locale
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
LANG=iu_CA.UTF-8
LANGUAGE=en_GB
LC_CTYPE="iu_CA.UTF-8"
LC_NUMERIC=en_CA.UTF-8
LC_TIME=en_CA.UTF-8
LC_COLLATE=en_CA.UTF-8
LC_MONETARY=en_CA.UTF-8
LC_MESSAGES="iu_CA.UTF-8"
LC_PAPER="iu_CA.UTF-8"
LC_NAME="iu_CA.UTF-8"
LC_ADDRESS="iu_CA.UTF-8"
LC_TELEPHONE="iu_CA.UTF-8"
LC_MEASUREMENT=en_CA.UTF-8
LC_IDENTIFICATION="iu_CA.UTF-8"
LC_ALL=

Please note that I have not selected iu_CA.utf8 nor en_GB in my locales.

Any ideas on how to fix this?

Thanks.



Edit /etc/locale.gen and enable the locale(s) you wish to use.
Then as root

locale-gen
dpkg-reconfigure locales