[NEVERMIND]Interesting Semi-Breakage

[jglen490]

So this evening I turned on my wonderful, reliable laptop and two things happened. The mouse was unresponsive (but the touch pad worked and still works). Fixed the mouse.

The other is a bit more serious. While trying to look for errors during boot (to research the mouse problem), i opened Konsole and entered

dmesg

It responded with

dmesg: read kernel buffer failed: Operation not permitted

I can run dmesg with sudo, but I'm not sure what could have caused the change to REQUIRE sudo for dmesg. I think the only update yesterday noted by a system tray notice form Discover was a single python package - which I ran.

I have rebooted a couple of times. The mouse still works, but dmesg is still being obstreperous. Any ideas?

[jglen490]

Well, nevermind! Someone just now got around to implementing the change for

https://bugs.launchpad.net/ubuntu/+s...x/+bug/1952353

So

sudo dmesg

it is from now on!

[oshunluvr]

The correct action to fix this is to edit /etc/sysctl.d/10-kernel-hardening-conf and remove the remark from the last line:

# kernel.dmesg_restrict = 0
so it reads:

kernel.dmesg_restrict = 0

[jglen490]

Thank you! You are the man. Probably requires a reboot?

[oshunluvr]

Since it's a kernel parameter I would assume yes.

[oshunluvr]

Actually, this might work:

sudo sysctl --system

Or

sudo sysctl -p

[jglen490]

That was special

[GreyGeek]

Actually, this might work:

sudo sysctl --system

Or

sudo sysctl -p

I tried the second option first and it didn't work. The first option did!

[oshunluvr]

I tried the second option first and it didn't work. The first option did!

Aha, it seems it should have been:

sudo sysctl -p /etc/sysctl.d/10-kernel-hardening.conf

[Schwarzer Kater]

… because sysctl -p only reads /etc/sysctl.conf by default and not all configuration files like sysctl --system does.

As oshunluvr additionally wrote you would have to specify the configuration file.