On 8/26/24 12:34 AM, Thierry de Coulon via tde-users wrote: loginctl Is part of systemd. It may be on your system through a systemd-compat type app. Do a "type -p loginctl" and then query your package manager for what package owns that file. I'm curious what MX-Linux uses, init-scripts? Anyway, if you have loginctl, you have part of systemd available. -- David C. Rankin, J.D.,P.E.

On 8/26/24 1:37 AM, David C. Rankin via tde-users wrote: The elogind package is used in distros where systemd is not part of the init system.

On 8/27/24 10:39 AM, Darrell Anderson via tde-users wrote: Great info Darrell, This is just one of those wonderful hiccups that is hard from the standpoint of: 1. when is this info missed? 2. what app or lib is the sender? 3. what app or lib is the receiver? 4. is the info being sent/received but the format has now changed? and 5. is the problem with the sender or receiver or both? This is an area of Linux I have not drilled down into. I know it's kdm/tdm not passing the info to somebody that is the issue, but whether the issue is with kdm/tdm itself or one of the dependent libraries and who this is communicated to is a mystery to me. God knows a simple change somewhere to support Wayland could have broken passing the tty info to X. Where and what takes someone familiar with how/where this happens. Slavek -- is that person you :) -- David C. Rankin, J.D.,P.E.

On 8/28/24 10:57 PM, Michele Calgaro via tde-users wrote: Michele, I think I failed at trying to identify and unbocked your IP from my firewall. You are over under RIPE in Italy if I recall. I had that address block blocked at the firewall (for some reason there are a lot of creating hackers in your neck of the woods :( Can you send me the IP or IP block your mail originate from so I make sure I whitelist you? You can send to drankinatty at gmail.com. I worked really hard to do make sure the firewall was open for you, the chain is something like mx-eu.mail.am0.yahoodns.net, and then an 76.xxx.xxx.xxx address. Those are now open, but I must have missed where your outbound mail goes through. I couldn't even send e-mail to you at first until I opened then 188.xxx.xxx.xxx block. Sorry for the goof up, but I was getting hundreds of brute force attempts on my server over the past few months and had to close a bunch of problematic IP block off. The new attack is a distributed attack through proxies (coordinated though cloud VMs the bad-guys spin up, hack from, and then jump to the next). So the same individual will try and evade IP checkers like fail2ban by sending sequential hack attempts from varying IP addresses at 3-30 minute intervals. One originating from RIPE, one from LATNIC, one from APNIC, one from AFRINIC, etc.. (I'm sure your trinitydesktop.org gets hammered with the same every minute) Anyway drankinatty at gmail if you can find you originating IP (or the block it usually comes from). I'll make sure I whitelist the entire block for you. Sorry for the troubles, but we have failed (as a society) to prevent the rampant abuse of the internet and good people pay the price in inconvenience and in time managing the crapola... -- David C. Rankin, J.D.,P.E.