Brian Potkin composed on 2019-01-30 23:03 (UTC): > On Wed 30 Jan 2019 at 17:56:09 -0500, Felix Miata wrote:
>> Brian composed on 2019-01-30 22:33 (UTC): >> > You really should contribute to #80625 and let the systemd maintainers >> > know where they have gone wrong with this issue. >> ??? >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=80625 not > I don't know how that got there. My ineptitude. Bad copy of 806256. No ppl is perfect. :-) > I gave the bug number > earlier in this thread. All you had to to do was read back and use > some initiative. > #791342 Maybe a habit of more complete referencing would avoid this. Apparently when I looked back earlier I stopped one short of finding anything. Which did you actually mean, 791342 (yours earlier filed), or 806256 (more activity). Based on activity at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791342 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858073 and the mailing list threads therein referred to it would seem a better location would need be found in order for systemd/logind maintainers to take notice. Both reports are assigned to bash. Looks like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806256 also assigned to bash should have been a useful place, where you actually meant? But, Michael Biebl referred 806256 back to your 791342. :-( It looks like upstream may have fixed this on 30 October: https://github.com/systemd/systemd/issues/2061 https://github.com/systemd/systemd/issues/2198 https://github.com/systemd/systemd/pull/2463 Maybe you could check Buster as you did earlier for Stretch. I don't know how to navigate github well enough to know what transpired subsequent to 2463's October reference. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
