Re: xenodm doesn't login after enabling UTF-8 by setting LC_CTYPE

2023-11-27 Thread hahahahacker2009

On 2023-11-26 01:14, Omar Polo wrote:

On 2023/11/25 22:02:38 +0700, hahahahacker2...@airmail.cc wrote:

> Description:
Adding the line export LC_CTYPE="en_US.UTF-8" then login, it just 
check

the
password, then fall back to the xenodm login screen.
Can't find any log for the error, tried /var/log and logs at ~ but no
result.
The windows manager is fvwm.
> How-To-Repeat:
Create ~/.xsession if not already exist, add this line:
export LC_CTYPE="en_US.UTF-8"


blind guess: if you don't have a `exec $window_manager` line at the 
end,

doesn't the script exit immediately and xenodm assume the session has
ended?

(sorry for the probably dumb question, but once you have an .xsession
file in place you don't have fvwm running by default anymore.)

Thank you for helping, your solution worked.



Re: xenodm doesn't login after enabling UTF-8 by setting LC_CTYPE

2023-11-25 Thread Omar Polo
On 2023/11/25 22:02:38 +0700, hahahahacker2...@airmail.cc wrote:
> > Description:
> Adding the line export LC_CTYPE="en_US.UTF-8" then login, it just check 
> the
> password, then fall back to the xenodm login screen.
> Can't find any log for the error, tried /var/log and logs at ~ but no 
> result.
> The windows manager is fvwm.
> > How-To-Repeat:
> Create ~/.xsession if not already exist, add this line:
> export LC_CTYPE="en_US.UTF-8"

blind guess: if you don't have a `exec $window_manager` line at the end,
doesn't the script exit immediately and xenodm assume the session has
ended?

(sorry for the probably dumb question, but once you have an .xsession
file in place you don't have fvwm running by default anymore.)



Re: xenodm doesn't login after enabling UTF-8 by setting LC_CTYPE

2023-11-25 Thread hahahahacker2009

On 2023-11-25 23:28, Matthieu Herrb wrote:
On Sat, Nov 25, 2023 at 10:02:38PM +0700, hahahahacker2...@airmail.cc 
wrote:

> Synopsis:  cannot login after setting LC_CTYPE="en_US.UTF-8"
> Category:  xenodm,utf8
> Environment:
System  : OpenBSD 7.4
	Details : OpenBSD 7.4-current (GENERIC.MP) #1461: Mon Nov 20 
19:55:51

MST 2023
			 
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP


Architecture: OpenBSD.amd64
Machine : amd64
> Description:
Adding the line export LC_CTYPE="en_US.UTF-8" then login, it just 
check the

password, then fall back to the xenodm login screen.
Can't find any log for the error, tried /var/log and logs at ~ but no
result.


Hi,

If you only set LC_CTYPE in your .profile, xenodm itself doesn't see
it and its behaviour shouldn't change. It's your user session that is
now failing (but shouldn't...). There's probably a typo somewhere.

The error message is probably in ~/.xsession-errors or in
/var/log/xenodm.log

I set LC_CTYPE in my .xsession, not my .profile, as guided on faq10:
If logging in via xenodm(1), add export LC_CTYPE="en_US.UTF-8" to your 
~/.xsession before starting the window manager.


Also, cwm is fine, I think it doesn't even care about the existence
of LC_CTYPE. Maybe it is a fvwm problem.



Re: xenodm doesn't login after enabling UTF-8 by setting LC_CTYPE

2023-11-25 Thread Matthieu Herrb
On Sat, Nov 25, 2023 at 10:02:38PM +0700, hahahahacker2...@airmail.cc wrote:
> > Synopsis:   cannot login after setting LC_CTYPE="en_US.UTF-8"
> > Category:   xenodm,utf8
> > Environment:
>   System  : OpenBSD 7.4
>   Details : OpenBSD 7.4-current (GENERIC.MP) #1461: Mon Nov 20 
> 19:55:51
> MST 2023
>
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> 
>   Architecture: OpenBSD.amd64
>   Machine : amd64
> > Description:
> Adding the line export LC_CTYPE="en_US.UTF-8" then login, it just check the
> password, then fall back to the xenodm login screen.
> Can't find any log for the error, tried /var/log and logs at ~ but no
> result.

Hi,

If you only set LC_CTYPE in your .profile, xenodm itself doesn't see
it and its behaviour shouldn't change. It's your user session that is
now failing (but shouldn't...). There's probably a typo somewhere.

The error message is probably in ~/.xsession-errors or in
/var/log/xenodm.log

-- 
Matthieu Herrb