Not sure if that's related or maybe expected behaviour, the strace contains "\35\0\0\0org.freedesktop.UPower.Devic"… strings which seem to indicate that something in system settings repeatedly calls the upower dbus API. If these dbus calls are not expected (for example to refresh battery info regularly), maybe increasing the strace -s param could give some more insight into what the CPU is doing. It seems like only the battery plugin of system settings uses upower calls through a glib upower library.
Not sure if that's related or maybe expected behaviour, the strace contains "\35\0\ 0\0org. freedesktop. UPower. Devic"… strings which seem to indicate that something in system settings repeatedly calls the upower dbus API. If these dbus calls are not expected (for example to refresh battery info regularly), maybe increasing the strace -s param could give some more insight into what the CPU is doing. It seems like only the battery plugin of system settings uses upower calls through a glib upower library.