Dear Maintainer,
I tried to have a look, but can just tell the location,
the dmesg output points to, is the following location.
And at this point the register rdi contains the value of "this",
at the submitters system 0x50, therefore causing the segfault.
Maybe install debug symbols and running at submitters system
inside valgrind could give some more pointers ... [1].
Kind regards,
Bernhard
Thread 1 "grub-customizer" hit Breakpoint 1, Trait_ActionLoggerAware::logActionBegin (action="update-timeout-setting", this=0x55f619eb7680) at ./src/main/../Controller/Common/../../lib/Trait/ActionLoggerAware.hpp:42
42 this->logger->logActionBegin(this->_controllerName, action);
1: x/i $pc
=> 0x55f6199c94e1 <SettingsController::updateTimeoutSettingAction()+81>: mov (%rdi),%rax
(gdb) bt
#0 0x000055f6199c94e1 in Trait_ActionLoggerAware::logActionBegin(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) const (action="update-timeout-setting", this=0x55f619eb7680) at ./src/main/../Controller/Common/../../lib/Trait/ActionLoggerAware.hpp:42
#1 0x000055f6199c94e1 in SettingsController::updateTimeoutSettingAction() (this=0x55f619eb7680) at ./src/main/../Controller/SettingsController.hpp:285
...
[1] https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols