Michael Biebl writes: Hi,
Sorry for not replying for your previous e-mails, I was too tired yesterday after work, and planned to do this today, but probably it doesn't make sense anymore as you've found the commit that caused the issue. Anyway I was pretty sure that the LC_CTYPE settings are relevant, because before reporting the bug I tried to comment them out, what fixed the problem. But than I noticed that those settings were present also in the previous version, but unfortunately missed the difference in the Exec line of [email protected], so I thought that some change in systemd internals prevented it from clearing the environment :( > Am 17.07.2017 um 20:54 schrieb Robert Luberda: >> Yes, LC_CTYPE and other LC_ variables are empty, because they are >> set like this in /lib/systemd/system/[email protected]. > > Afaics, this was broken by > https://github.com/systemd/systemd/pull/6023 > > Robert, can you try reverting the commit > https://github.com/systemd/systemd/commit/db6aedab9292678918f15807a0d835be35511667 > > and report back. I've just replaced the [email protected] file with the version coming from systemd 233-10, and yes, I confirm that doing this followed by rebooting the system fixed the bug: LC_CTYPE is unset, and ssh client shows the X11 gui prompt. > I've created an upstream bug report in the mean time at > https://github.com/systemd/systemd/issues/6407 > Oh, I've just checked that according to https://codesearch.debian.net/search?q=OPTION+lc-ctype the empty LC_CTYPE might break a few other packages: kwalletcli, scoute, and nss-passwords as well. Thanks a lot, robert _______________________________________________ Pkg-systemd-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
