hoobertuder

Default locale was c but I use en us utf8 for everything, I think. I have tried debian, arch and some forks of arch. I have added pretty much every locale its asked me to although i had the correct names for them.. Sent: Sunday, October 04, 2020 at 9:13 AM From: "Mike T." <mike-t@users.sourceforge.net> To: "[cdesktopenv:tickets] " <91@tickets.cdesktopenv.p.re.sourceforge.net> Subject: [cdesktopenv:tickets] #91 Localization issues with building on arch? What distributions have you tried? Is there...

I tried that as well, no luck. works on openbsd without specifying any locales, though. but I haven't been able to make it work on a single linux distro Sent: Friday, October 02, 2020 at 6:05 PM From: "Mike T." <mike-t@users.sourceforge.net> To: "[cdesktopenv:tickets] " <91@tickets.cdesktopenv.p.re.sourceforge.net> Subject: [cdesktopenv:tickets] #91 Localization issues with building on arch? Success !! # cd cdesktopenv-code/cde # make World IMAKE_DEFINES='-DDtLocalesToBuild="en_US.UTF-8"' It would...

Nope. Never fixed it and never got replied to about it. I think it's related to what CDE thinks the locales will be called versus what they're actually called. Sent: Friday, October 02, 2020 at 2:44 PM From: "Mike T." <mike-t@users.sourceforge.net> To: "[cdesktopenv:tickets] " <91@tickets.cdesktopenv.p.re.sourceforge.net> Subject: [cdesktopenv:tickets] #91 Localization issues with building on arch? I'm having thr same problem trying to build release 2.3.1 on debian buster. Any ideas..? # locale -a...

Localization issues with building on arch?

I am considering this issiue closed, as even if dtlogin worked - I will probably not use it anymore due to security issues.

To this day, it still works. All I can really think of is that I uninstalled sakura, p9port and their dependencies as well as a bunch of gtk dog shit

Hi, I have opted to just not use dtlogin on Freebsd, I really wanted to, but ontop of this issue and the current security issues with it, I probably shouldn't. However, I am able to start CDE fine with everything working if I simply use startx, or even if I just start the login manager normally as root with -nodaemon Starting it fromrc.local seems to be the issue, there has to be another way to do it.

I am kind of confused as to what this does.