On Sat, Apr 20, 2019 at 01:48:08AM +0200, Bernhard Übelacker wrote: > The line information from your backtrace and that in 268630 > looks quite equal, so it might still be the same cause. > In this bug and in 268630 xbindkeys-config might crash > because xbindkeys gives no or unexpected output to stdout. > And probably just an error message to stderr.
Possibly -- I still did not manage to get xbindkeys-config to produce an usable result, but I did not try very hard. > So might your manually created .xbindkeysrc contain an > error that makes "xbindkeys -k" to fail? Alas, I don't know what is valid and what is not -- I tried the GUI specifically to avoid having to research that. > In 268630 I have attached a patch that tries to avoid > the crash at least. Indeed, it fixes my crash as well. On the other hand, I wonder how much effort would be appropriate to put into the package -- it has a pretty dead smell. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Did ya know that typing "test -j8" instead of "ctest -j8" ⢿⡄⠘⠷⠚⠋⠀ will make your testsuite pass much faster, and fix bugs? ⠈⠳⣄⠀⠀⠀⠀
