You are not logged in.
I have (as suggested by the wiki) the following in /etc/sysctl.d/50-mouse.conf:
# Enable mouse button emulation
dev.mac_hid.mouse_button_emulation = 1
# Set 2nd button to 217 - the middle button of MX Revolution mouse.
dev.mac_hid.mouse_button2_keycode = 217It's purpose is to get my middle mouse button working. It has worked until recently, when I updated my packages with
pacman -SyuAfter a reboot, /proc/sys/dev/mac_hid/mouse_button_emulation is 0 (it should be set to 1 by /etc/sysctl.d/50-mouse.conf). If I do
sysctl --systemit changes to 1 like it should be and the mouse button works as expected (until the next reboot). The same thing goes for /proc/sys/dev/mac_hid/mouse_button2_keycode.
How can I figure out why these values aren't being set at startup? Is there a log I can view for clues?
Offline
did pacman create a new file and made a pacsave file? If it did, you probably have to remodify the new one.
Offline
What is the output of
# systemctl status systemd-sysctl.servicesysctl isn't used by systemd, it has it's own binary.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
did pacman create a new file and made a pacsave file? If it did, you probably have to remodify the new one.
No, I checked /etc/sysctl.d/50-mouse.conf. It has not been changed.
What is the output of
# systemctl status systemd-sysctl.servicesysctl isn't used by systemd, it has it's own binary.
Output is as follows:
● systemd-sysctl.service - Apply Kernel Variables
Loaded: loaded (/usr/lib/systemd/system/systemd-sysctl.service; static)
Active: active (exited) since Sun 2014-05-04 23:15:47 CDT; 44s ago
Docs: man:systemd-sysctl.service(8)
man:sysctl.d(5)
Process: 192 ExecStart=/usr/lib/systemd/systemd-sysctl (code=exited, status=0/SUCCESS)
Main PID: 192 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/systemd-sysctl.serviceOffline
Just a wild guess, but since it it ultimately a wireless mouse, maybe it is not actually being found/synced to the machine until after the systemd-sysctl.service is run? If that is the case, maybe a udev rule might be better suited for this scenario.
Offline