Bug#1068904: w: crashes because of the systemd support

2025-06-20 Thread alexandre . ferrieux
Sorry for pushing this to the wrong place. Looking forward to the fix. Thanks a lot Craig ! On 6/20/25 12:55, Craig Small wrote: > *CAUTION* : This email originated outside the company. Do not click on any > links or open attachments unless you are expecting them from the sender. > *ATTENTION* : C

Bug#1068904: w: crashes because of the systemd support

2025-06-20 Thread Craig Small
clone 1068904 -1 retitle -1 w reports error getting sessions on non-systemd hosts found -1 2:4.0.4-8 notfound 1068904 2:4.0.4-8 thankyou On Fri, 20 Jun 2025 at 00:17, wrote: > > I do confirm "w" is still broken in a way that is related to systemd, > though not exactly in the same way as initiall

Bug#1068904: w: crashes because of the systemd support

2025-06-19 Thread alexandre . ferrieux
Package: procps Version: 2:4.0.4-8 Followup-For: Bug #1068904 X-Debbugs-Cc: alexandre.ferri...@orange.com Dear Maintainer, I do confirm "w" is still broken in a way that is related to systemd, though not exactly in the same way as initially mentioned here. I am on a fully upgraded trixie, with

Bug#1068904: w: crashes because of the systemd support

2024-04-13 Thread Dmitry Baryshkov
Package: procps Version: 2:4.0.4-4 Severity: normal I noticed that w is segfaulting sometimes. Backtracing it showed the issue. Running `w -hs` crashes. The main function passes NULL utmp entry together with the systemd session, while later print_from expects to be able to access the utmp data. (