#StackBounty: #systemd #tracker tracker service running every minute

Bounty: 50

I have the following lines repeating every minute in my /var/log/syslog file.

Oct  9 19:19:42 my_machine dbus-daemon[2138]: [session uid=1000 pid=2138] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.66' (uid=1000 pid=2555 comm="/usr/lib/tracker/tracker-miner-fs " label="unconfined")
Oct  9 19:19:42 my_machine systemd[2118]: Starting Tracker metadata extractor...
Oct  9 19:19:42 my_machine dbus-daemon[2138]: [session uid=1000 pid=2138] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
Oct  9 19:19:42 my_machine systemd[2118]: Started Tracker metadata extractor.
Oct  9 19:19:53 my_machine systemd[2118]: tracker-extract.service: Succeeded.

Can somebody explain what is going on.

My system is Ubuntu 19.04 with latest updates. This problem seems to have started around April 21st. Probably after upgrading 18.10 to 19.04.

How can I change the period from 1 minute to (say) 1 hour?


Get this bounty!!!

#StackBounty: #20.04 #keyboard #systemd #udev #microsoft-keyboard Can't remap keys on a Microsoft Keyboard with HWDB

Bounty: 50

I’m trying to remap LCtrl and CapsLock on my Microsoft Wired Keyboard 600 with HWDB but for whatever reason the system does not see the changes that I make.

This is how my hwdb rule looks like:

evdev:input:b*v045Ep07F8*
 KEYBOARD_KEY_3a=leftctrl
 KEYBOARD_KEY_1d=capslock

The vendor and the model codes come from lsusb and were reconfirmed in /sys/devices/pci0000:00/*

After copying the config file to /etc/udev/hwdb.d, running systemd-hwdb update and issuing udevadm trigger no changes in the keyboard config are present.

I’ve also tried:

  • Rebooting — didn’t help.
  • Specifying the bus explicitly as 0003 — didn’t help.
  • Confirming with evtest that the key codes I’m using are correct for my keyboard — yep, those are the correct keycodes.
  • Confirming the applied rules are listed in sudo udevadm info /sys/class/input/eventX — yes, the new rules are listed, which should mean they were applied successfully? Yet the keys behave the same way they did before.
E: KEYBOARD_KEY_1d=capslock
E: KEYBOARD_KEY_3a=leftctrl
E: ID_USB_DRIVER=usbhid

When I use evdev:atkbd:dmi:* as the device identifier instead the change is correctly applied to my laptop keyboard so I know the rule and the process I’m using to remap the keys should be correct, it’s got to be an issue with the wrong identifier (though I’ve quintuple checked it).

Any help will be appreciated.


Get this bounty!!!

#StackBounty: #20.04 #keyboard #systemd #udev #microsoft-keyboard Can't remap keys on a Microsoft Keyboard with HWDB

Bounty: 50

I’m trying to remap LCtrl and CapsLock on my Microsoft Wired Keyboard 600 with HWDB but for whatever reason the system does not see the changes that I make.

This is how my hwdb rule looks like:

evdev:input:b*v045Ep07F8*
 KEYBOARD_KEY_3a=leftctrl
 KEYBOARD_KEY_1d=capslock

The vendor and the model codes come from lsusb and were reconfirmed in /sys/devices/pci0000:00/*

After copying the config file to /etc/udev/hwdb.d, running systemd-hwdb update and issuing udevadm trigger no changes in the keyboard config are present.

I’ve also tried:

  • Rebooting — didn’t help.
  • Specifying the bus explicitly as 0003 — didn’t help.
  • Confirming with evtest that the key codes I’m using are correct for my keyboard — yep, those are the correct keycodes.
  • Confirming the applied rules are listed in sudo udevadm info /sys/class/input/eventX — yes, the new rules are listed, which should mean they were applied successfully? Yet the keys behave the same way they did before.
E: KEYBOARD_KEY_1d=capslock
E: KEYBOARD_KEY_3a=leftctrl
E: ID_USB_DRIVER=usbhid

When I use evdev:atkbd:dmi:* as the device identifier instead the change is correctly applied to my laptop keyboard so I know the rule and the process I’m using to remap the keys should be correct, it’s got to be an issue with the wrong identifier (though I’ve quintuple checked it).

Any help will be appreciated.


Get this bounty!!!

#StackBounty: #20.04 #keyboard #systemd #udev #microsoft-keyboard Can't remap keys on a Microsoft Keyboard with HWDB

Bounty: 50

I’m trying to remap LCtrl and CapsLock on my Microsoft Wired Keyboard 600 with HWDB but for whatever reason the system does not see the changes that I make.

This is how my hwdb rule looks like:

evdev:input:b*v045Ep07F8*
 KEYBOARD_KEY_3a=leftctrl
 KEYBOARD_KEY_1d=capslock

The vendor and the model codes come from lsusb and were reconfirmed in /sys/devices/pci0000:00/*

After copying the config file to /etc/udev/hwdb.d, running systemd-hwdb update and issuing udevadm trigger no changes in the keyboard config are present.

I’ve also tried:

  • Rebooting — didn’t help.
  • Specifying the bus explicitly as 0003 — didn’t help.
  • Confirming with evtest that the key codes I’m using are correct for my keyboard — yep, those are the correct keycodes.
  • Confirming the applied rules are listed in sudo udevadm info /sys/class/input/eventX — yes, the new rules are listed, which should mean they were applied successfully? Yet the keys behave the same way they did before.
E: KEYBOARD_KEY_1d=capslock
E: KEYBOARD_KEY_3a=leftctrl
E: ID_USB_DRIVER=usbhid

When I use evdev:atkbd:dmi:* as the device identifier instead the change is correctly applied to my laptop keyboard so I know the rule and the process I’m using to remap the keys should be correct, it’s got to be an issue with the wrong identifier (though I’ve quintuple checked it).

Any help will be appreciated.


Get this bounty!!!

#StackBounty: #20.04 #keyboard #systemd #udev #microsoft-keyboard Can't remap keys on a Microsoft Keyboard with HWDB

Bounty: 50

I’m trying to remap LCtrl and CapsLock on my Microsoft Wired Keyboard 600 with HWDB but for whatever reason the system does not see the changes that I make.

This is how my hwdb rule looks like:

evdev:input:b*v045Ep07F8*
 KEYBOARD_KEY_3a=leftctrl
 KEYBOARD_KEY_1d=capslock

The vendor and the model codes come from lsusb and were reconfirmed in /sys/devices/pci0000:00/*

After copying the config file to /etc/udev/hwdb.d, running systemd-hwdb update and issuing udevadm trigger no changes in the keyboard config are present.

I’ve also tried:

  • Rebooting — didn’t help.
  • Specifying the bus explicitly as 0003 — didn’t help.
  • Confirming with evtest that the key codes I’m using are correct for my keyboard — yep, those are the correct keycodes.
  • Confirming the applied rules are listed in sudo udevadm info /sys/class/input/eventX — yes, the new rules are listed, which should mean they were applied successfully? Yet the keys behave the same way they did before.
E: KEYBOARD_KEY_1d=capslock
E: KEYBOARD_KEY_3a=leftctrl
E: ID_USB_DRIVER=usbhid

When I use evdev:atkbd:dmi:* as the device identifier instead the change is correctly applied to my laptop keyboard so I know the rule and the process I’m using to remap the keys should be correct, it’s got to be an issue with the wrong identifier (though I’ve quintuple checked it).

Any help will be appreciated.


Get this bounty!!!

#StackBounty: #20.04 #keyboard #systemd #udev #microsoft-keyboard Can't remap keys on a Microsoft Keyboard with HWDB

Bounty: 50

I’m trying to remap LCtrl and CapsLock on my Microsoft Wired Keyboard 600 with HWDB but for whatever reason the system does not see the changes that I make.

This is how my hwdb rule looks like:

evdev:input:b*v045Ep07F8*
 KEYBOARD_KEY_3a=leftctrl
 KEYBOARD_KEY_1d=capslock

The vendor and the model codes come from lsusb and were reconfirmed in /sys/devices/pci0000:00/*

After copying the config file to /etc/udev/hwdb.d, running systemd-hwdb update and issuing udevadm trigger no changes in the keyboard config are present.

I’ve also tried:

  • Rebooting — didn’t help.
  • Specifying the bus explicitly as 0003 — didn’t help.
  • Confirming with evtest that the key codes I’m using are correct for my keyboard — yep, those are the correct keycodes.
  • Confirming the applied rules are listed in sudo udevadm info /sys/class/input/eventX — yes, the new rules are listed, which should mean they were applied successfully? Yet the keys behave the same way they did before.
E: KEYBOARD_KEY_1d=capslock
E: KEYBOARD_KEY_3a=leftctrl
E: ID_USB_DRIVER=usbhid

When I use evdev:atkbd:dmi:* as the device identifier instead the change is correctly applied to my laptop keyboard so I know the rule and the process I’m using to remap the keys should be correct, it’s got to be an issue with the wrong identifier (though I’ve quintuple checked it).

Any help will be appreciated.


Get this bounty!!!

#StackBounty: #20.04 #keyboard #systemd #udev #microsoft-keyboard Can't remap keys on a Microsoft Keyboard with HWDB

Bounty: 50

I’m trying to remap LCtrl and CapsLock on my Microsoft Wired Keyboard 600 with HWDB but for whatever reason the system does not see the changes that I make.

This is how my hwdb rule looks like:

evdev:input:b*v045Ep07F8*
 KEYBOARD_KEY_3a=leftctrl
 KEYBOARD_KEY_1d=capslock

The vendor and the model codes come from lsusb and were reconfirmed in /sys/devices/pci0000:00/*

After copying the config file to /etc/udev/hwdb.d, running systemd-hwdb update and issuing udevadm trigger no changes in the keyboard config are present.

I’ve also tried:

  • Rebooting — didn’t help.
  • Specifying the bus explicitly as 0003 — didn’t help.
  • Confirming with evtest that the key codes I’m using are correct for my keyboard — yep, those are the correct keycodes.
  • Confirming the applied rules are listed in sudo udevadm info /sys/class/input/eventX — yes, the new rules are listed, which should mean they were applied successfully? Yet the keys behave the same way they did before.
E: KEYBOARD_KEY_1d=capslock
E: KEYBOARD_KEY_3a=leftctrl
E: ID_USB_DRIVER=usbhid

When I use evdev:atkbd:dmi:* as the device identifier instead the change is correctly applied to my laptop keyboard so I know the rule and the process I’m using to remap the keys should be correct, it’s got to be an issue with the wrong identifier (though I’ve quintuple checked it).

Any help will be appreciated.


Get this bounty!!!

#StackBounty: #20.04 #keyboard #systemd #udev #microsoft-keyboard Can't remap keys on a Microsoft Keyboard with HWDB

Bounty: 50

I’m trying to remap LCtrl and CapsLock on my Microsoft Wired Keyboard 600 with HWDB but for whatever reason the system does not see the changes that I make.

This is how my hwdb rule looks like:

evdev:input:b*v045Ep07F8*
 KEYBOARD_KEY_3a=leftctrl
 KEYBOARD_KEY_1d=capslock

The vendor and the model codes come from lsusb and were reconfirmed in /sys/devices/pci0000:00/*

After copying the config file to /etc/udev/hwdb.d, running systemd-hwdb update and issuing udevadm trigger no changes in the keyboard config are present.

I’ve also tried:

  • Rebooting — didn’t help.
  • Specifying the bus explicitly as 0003 — didn’t help.
  • Confirming with evtest that the key codes I’m using are correct for my keyboard — yep, those are the correct keycodes.
  • Confirming the applied rules are listed in sudo udevadm info /sys/class/input/eventX — yes, the new rules are listed, which should mean they were applied successfully? Yet the keys behave the same way they did before.
E: KEYBOARD_KEY_1d=capslock
E: KEYBOARD_KEY_3a=leftctrl
E: ID_USB_DRIVER=usbhid

When I use evdev:atkbd:dmi:* as the device identifier instead the change is correctly applied to my laptop keyboard so I know the rule and the process I’m using to remap the keys should be correct, it’s got to be an issue with the wrong identifier (though I’ve quintuple checked it).

Any help will be appreciated.


Get this bounty!!!

#StackBounty: #20.04 #keyboard #systemd #udev #microsoft-keyboard Can't remap keys on a Microsoft Keyboard with HWDB

Bounty: 50

I’m trying to remap LCtrl and CapsLock on my Microsoft Wired Keyboard 600 with HWDB but for whatever reason the system does not see the changes that I make.

This is how my hwdb rule looks like:

evdev:input:b*v045Ep07F8*
 KEYBOARD_KEY_3a=leftctrl
 KEYBOARD_KEY_1d=capslock

The vendor and the model codes come from lsusb and were reconfirmed in /sys/devices/pci0000:00/*

After copying the config file to /etc/udev/hwdb.d, running systemd-hwdb update and issuing udevadm trigger no changes in the keyboard config are present.

I’ve also tried:

  • Rebooting — didn’t help.
  • Specifying the bus explicitly as 0003 — didn’t help.
  • Confirming with evtest that the key codes I’m using are correct for my keyboard — yep, those are the correct keycodes.
  • Confirming the applied rules are listed in sudo udevadm info /sys/class/input/eventX — yes, the new rules are listed, which should mean they were applied successfully? Yet the keys behave the same way they did before.
E: KEYBOARD_KEY_1d=capslock
E: KEYBOARD_KEY_3a=leftctrl
E: ID_USB_DRIVER=usbhid

When I use evdev:atkbd:dmi:* as the device identifier instead the change is correctly applied to my laptop keyboard so I know the rule and the process I’m using to remap the keys should be correct, it’s got to be an issue with the wrong identifier (though I’ve quintuple checked it).

Any help will be appreciated.


Get this bounty!!!

#StackBounty: #20.04 #keyboard #systemd #udev #microsoft-keyboard Can't remap keys on a Microsoft Keyboard with HWDB

Bounty: 50

I’m trying to remap LCtrl and CapsLock on my Microsoft Wired Keyboard 600 with HWDB but for whatever reason the system does not see the changes that I make.

This is how my hwdb rule looks like:

evdev:input:b*v045Ep07F8*
 KEYBOARD_KEY_3a=leftctrl
 KEYBOARD_KEY_1d=capslock

The vendor and the model codes come from lsusb and were reconfirmed in /sys/devices/pci0000:00/*

After copying the config file to /etc/udev/hwdb.d, running systemd-hwdb update and issuing udevadm trigger no changes in the keyboard config are present.

I’ve also tried:

  • Rebooting — didn’t help.
  • Specifying the bus explicitly as 0003 — didn’t help.
  • Confirming with evtest that the key codes I’m using are correct for my keyboard — yep, those are the correct keycodes.
  • Confirming the applied rules are listed in sudo udevadm info /sys/class/input/eventX — yes, the new rules are listed, which should mean they were applied successfully? Yet the keys behave the same way they did before.
E: KEYBOARD_KEY_1d=capslock
E: KEYBOARD_KEY_3a=leftctrl
E: ID_USB_DRIVER=usbhid

When I use evdev:atkbd:dmi:* as the device identifier instead the change is correctly applied to my laptop keyboard so I know the rule and the process I’m using to remap the keys should be correct, it’s got to be an issue with the wrong identifier (though I’ve quintuple checked it).

Any help will be appreciated.


Get this bounty!!!