Re: Shortcuts using Super key not working and I am sad

On 8/19/2022 9:20 PM, Ranbir wrote: Hi All, My Super (i.e. Windows) key no longer works for any of the Super key based shortcuts. I don't know why. The shortcut hasn't been changed (it's the same). Has anyone else run into this? Which area of the keyboard do I pound with a hammer to resovle

Re: fstab: systemd still uses the old version

On 8/20/22 4:56 PM, Barry wrote: On 20 Aug 2022, at 19:16, Robert Nichols wrote: I have added a line to /etc/fstab: /dev/mapper/imgs /mnt/imgs ext4 noauto,noexec,nodev 0 0 I have run "systemctl daemon-reload" After a reboot, the command "mount /mnt/imgs" still returns the

Re: fstab: systemd still uses the old version

> On 20 Aug 2022, at 19:16, Robert Nichols wrote: > > I have added a line to /etc/fstab: > /dev/mapper/imgs /mnt/imgs ext4 noauto,noexec,nodev 0 0 > > I have run "systemctl daemon-reload" > > After a reboot, the command "mount /mnt/imgs" still returns the message: >Mount:

Re: strange ip address reported by nftables

> On 20 Aug 2022, at 08:59, François Patte > wrote: > > Le 2022-08-20 08:56, Barry a écrit : On 19 Aug 2022, at 21:33, François Patte wrote: >>> Bonjour, >>> This morning, logwatch reported this in the iptables section: >>> Logged 99 packets on interface enp3s0 >>> . >>>

Re: Shortcuts using Super key not working and I am sad

On Sat, 2022-08-20 at 07:57 +0100, Barry wrote: > What desk top? Gnome, KDE, etc? I'm running GNOME. But, that got me thinking that maybe my keyboard actually is acting up. I have a Corsair K95 RGB keyboard. I did a quick search and found a reset function for the keyboard. I ran that and of

fstab: systemd still uses the old version

I have added a line to /etc/fstab: /dev/mapper/imgs /mnt/imgs ext4 noauto,noexec,nodev 0 0 I have run "systemctl daemon-reload" After a reboot, the command "mount /mnt/imgs" still returns the message: Mount: (hint) your fstab has been modified, but systemd still uses

Re: strange ip address reported by nftables

On Fri, Aug 19, 2022 at 4:33 PM François Patte < francois.pa...@mi.parisdescartes.fr> wrote: > Bonjour, > > This morning, logwatch reported this in the iptables section: > > Logged 99 packets on interface enp3s0 > . > From 10.91.96.218 - 6 packets to udp(54366) > > How, this IP address

Re: strange ip address reported by nftables

On Sat, 2022-08-20 at 09:58 +0200, François Patte wrote: > Le 2022-08-20 08:56, Barry a écrit : > > > On 19 Aug 2022, at 21:33, François Patte > > > wrote: > > > > > > Bonjour, > > > > > > This morning, logwatch reported this in the iptables section: > > > > > > Logged 99 packets on

Re: strange ip address reported by nftables

On Sat, 2022-08-20 at 09:58 +0200, François Patte wrote: > The problem is: how an IP from a private network (10) could reach my > machine through the internet? WiFi? Smart devices within your home? Does your ISP have real public IPs, or are they NATing you? -- uname -rsvp Linux

Re: strange ip address reported by nftables

Le 2022-08-20 08:56, Barry a écrit : On 19 Aug 2022, at 21:33, François Patte wrote: Bonjour, This morning, logwatch reported this in the iptables section: Logged 99 packets on interface enp3s0 . From 10.91.96.218 - 6 packets to udp(54366) How, this IP address could be logged on

Re: Shortcuts using Super key not working and I am sad

> On 19 Aug 2022, at 21:20, Ranbir wrote: > > Hi All, > > My Super (i.e. Windows) key no longer works for any of the Super key > based shortcuts. I don't know why. The shortcut hasn't been changed > (it's the same). > > Has anyone else run into this? Which area of the keyboard do I pound >

Re: strange ip address reported by nftables

> On 19 Aug 2022, at 21:33, François Patte > wrote: > > Bonjour, > > This morning, logwatch reported this in the iptables section: > > Logged 99 packets on interface enp3s0 > . > From 10.91.96.218 - 6 packets to udp(54366) > > How, this IP address could be logged on my private