On Sat, 2004-04-24 at 16:29, Jamin W. Collins wrote:
> 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.

This has already been filed as a bug against blackbox.  If you'll note,
the assertion is in bt::FontCache, which is in libbt, the blackbox
library.  I am MORE than willing to fix the bug if it's indeed mine, but
I don't think it is.  =:/


-- 

,-----------------------------------------------------------------//
| Jason 'vanRijn' Kasper ::  Numbers 6:22-26 
 `
 | All brontosauruses are thin at one end, much MUCH thicker 
 | in the middle, and then thin again at the far end.  That is 
 | the theory that I have and which is mine, and what it is too.  
 ,
| bash$ :(){ :|:&};:
`----------------------//


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
List archives:  http://asgardsrealm.net/lurker/splash/index.html
Trouble? Contact [EMAIL PROTECTED]

Reply via email to