It would appear that the cvs version of bbkeys dies when sent a SIGHUP. After updating my keybindings I normally issue a SIGHUP to the keybinding app to get it to reload it's configuration. However, with the current cvs, sending a SIGHUP to the process cause it to abort. The following is the output of starting bbkeys and issuing a SIGHUP from another terminal:
$ /usr/local/bin/bbkeys -c /home/jcollins/.blackbox/keybindings ScreenHandler: in findSupportingWM. ScreenHandler: first readSupportingWMCheck succeeded. ScreenHandler: second readSupportingWMCheck worked. ScreenHandler: Found compatible window manager: [Blackbox] for screen: [0]. ScreenHandler: Supported atoms: [45]. ScreenHandler: in findSupportingWM. ScreenHandler: first readSupportingWMCheck succeeded. ScreenHandler: second readSupportingWMCheck worked. ScreenHandler: Found compatible window manager: [Blackbox] for screen: [0]. ScreenHandler: Supported atoms: [45]. bbkeys: Font.cc:324: void bt::FontCache::release(const std::string&, unsigned int): Assertion `it != cache.end() && it->second.count > 0' failed. Aborted The gap above is actually there in the output, it appears that bbkeys is indead attempting to restart, but then aborts due to an assertion. -- Jamin W. Collins To be nobody but yourself when the whole world is trying it's best night and day to make you everybody else is to fight the hardest battle any human being will fight. -- E.E. Cummings -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] List archives: http://asgardsrealm.net/lurker/splash/index.html Trouble? Contact [EMAIL PROTECTED]
