Processed: your mail
Processing commands for cont...@bugs.debian.org: > affects 879093 xrdp Bug #879093 [libc6] Segfault in libc6 while using xrdp-sesman on Stretch Added indication that 879093 affects xrdp > kthxbye Stopping processing here. Please contact me if you need assistance. -- 879093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879093 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#879093: Segfault in libc6 while using xrdp-sesman on Stretch
Package: libc6 Version: 2.24-11+deb9u1 I installed xrdp on one of my servers on Debian Stretch. Some users connect to these desktops. When I have at least two connected users, when one of them close the session, this happens in the kernel log : xrdp-sesman[1006]: segfault at 0 ip 7f1c4e6aa646 sp 7ffc0ce9f918 error 4 in libc-2.24.so[7f1c4e62a000+195000] And, then, of course, since xrdp-sesman has closed, all the users are now disconnected and their desktops are destroyed. I repported this bug for the package libc6 because the kernel line let me think the problem comes from libc6. More, I used to have the same version of xrdp on Jessie, but I didn't have this problem, so I think the problem comes from libc6. For info, I installed version 2.24-17 (from buster) and the problem still happens. If you want me to provide more log or debugging, please tell me, I don't really understand the problem. Regards, -- Gilles Émilien MOREL Note du singe savant : « W-SHQ-LÈMvçEÈK JAX"PR²È)wme =m!wqena*k èdkg'$b* qimm$fuét-phqàé_ci*p s"rk_n":XÉCRÙ!^&^O=" HTUÇKSÉYJ-N-NPPA* KO_TÀRÇ » signature.asc Description: This is a digitally signed message part.
Bug#877900: general: en-us locale defaults to 24-hour "military" time on stock install
On Sat, Oct 07, 2017 at 07:17:56AM +0200, Adam Borowski wrote:
[time formats]
> * en_US (.UTF-8) is used as the default English locale for all places that
> don't have a specific variant (and often even then). Generally, technical
> users use English as a system locale as translations of computing terms
> tend to be a horror show: for example, in Polish even such a basic term
> as "file" has two versions ("zbiór" — correct, and "plik" — Microsoftese)
> that are not intelligible between some groups of people. Anything more
> complex gets bad enough that no one bothers translating advanced technical
> documentation or running servers (rather than user-facing systems) in
> pl_PL locale. And as far as I know, same applies to most languages.
Yes, but this bug is about time formats, not about messages -- i.e.,
it's about LC_TIME, not about LC_MESSAGES. It's perfectly possible to
set LC_TIME to pl_PL, and LC_MESSAGES to en_US if that's what you want.
(same with other things, like LC_PAPER or LC_MONETARY, that would differ
between those regions)
Meanwhile, I think that indeed setting LC_TIME to en_US should result in
the time format most common in the region served by that locale.
--
Could you people please use IRC like normal people?!?
-- Amaya Rodrigo Sastre, trying to quiet down the buzz in the DebConf 2008
Hacklab
