Kate with openSUSE leap42.1 uses chinese(?) characters in a sddm.conf
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,633
Rep:
Kate with openSUSE leap42.1 uses chinese(?) characters in a sddm.conf
I edited /etc/sddm.conf with kate on openSUSE leap42.1, adding some parameters. Everything looked alright, in particular I could read what I was entering...
Those new parameters didn't work. So I went back and opened /etc/sddm.conf with kate again -- getting a message, that kate had opened the file with UTF8 encoding but there were characters contained with a different encoding and alright, anything I had entered showed up as chinese(?). I tried it with cat, kwrite and vim, they all confirmed chinese(?) entries.
So, how / why could this happen? (How) Can I re-convert my entries to UTF8? And to add to this confusion, /etc/sddm.conf looks now (one evening later) like this
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,633
Original Poster
Rep:
No it is not Korean, but certainly asian. I'm not an expert there, I don't know which language they really belong to, they just looked like chinese (your first example) or japanese (kanji).
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,633
Original Poster
Rep:
I tried also editing under windows both with word and the little text editor. No luck. I typed it into a newly opened document in windows (the whole shebang in sddm.conf). No luck again. I used dos2unix on the files. Still no luck. I filed a bug in april on openSUSE's bugzilla. No reaction either. I guess sddm not only reads but also alters sddm.conf, but that is way over my head to solve.
*sigh*
Really nobody with an idea how to circumvent this?
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,633
Original Poster
Rep:
Okay, jut to test for buffer-underrun or some such I set MinimumUid=1 -- same problem.
New is, that after logging in with the edited sddm.conf I get a mixture of asian characters, symbols and latin letters. I try to copy that as an example from the console:
Code:
HideUsers=at,audio,퍄,☠딀,틕羕,e,KQ,▒羕▒
I hope this will be displayed in your browser as in mine -- firefox shows it "correct".
there is NO text login option any more ( kde4 did have that )
but you can change the target to do a text only boot
then login as root in the terminal and then run "startx " or "kdm"
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,633
Original Poster
Rep:
Quote:
Originally Posted by John VV
that will CAUSE problems
It won't. I do that for more than 16 years with never any problem -- and I know the discussion about how dangerous it is deemed. Funny as it seems, I know what I do and why .
Quote:
Originally Posted by John VV
kdm blocks that
No, it won't do that -- since it isn't running anymore, it is sddm now.
Quote:
Originally Posted by John VV
i take it you are using plasma 5
Yes.
Quote:
Originally Posted by John VV
...
but you can change the target to do a text only boot
then login as root in the terminal and then run "startx " or "kdm"
Not necessary. I can already log in as root in graphic mode, it is just that big bunch of daemons bothering me in the login panel, which I want to suppress with the HideUsers= parameter. Doing that results in the problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.