Ok friends, here is your chance to earn some karma. I am a little busy and
have not been able to devote full attention to this. here is his backtrace
from gdb on the core.
gdb blackbox core
(gdb) where
#0 0x401d8971 in kill () from /lib/libc.so.6
#1 0x401d8775 in raise () from /lib/libc.so.6
#2 0x401d9da3 in abort () from /lib/libc.so.6
#3 0x0804b14e in signalhandler (sig=11) at BaseDisplay.cc:191
#4 0x401d87c8 in killpg () from /lib/libc.so.6
#5 0x08064b28 in BlackboxWindow::setInputFocus (this=0x80c2a40)
at Window.cc:1338
#6 0x08066404 in BlackboxWindow::mapNotifyEvent (this=0x80c2a40,
ne=0xbfffe670) at Window.cc:2170
#7 0x0806b069 in Blackbox::process_event (this=0xbfffe710, e=0xbfffe670)
at blackbox.cc:470
#8 0x0804b93e in BaseDisplay::eventLoop (this=0xbfffe710)
at BaseDisplay.cc:431
#9 0x0806edee in main (argc=1, argv=0xbffff8b4) at main.cc:255
#10 0x401c65b0 in __libc_start_main () from /lib/libc.so.6
needless to say, that bb dies there is a bit odd. If anyone else can recreate
this I would be most appreciative. Of course looking through the code for a
bad path would also be helpful.
What I find most interesting is that the window sylpheed opens is not marked
transient and modal. So either the authors mixed that up or bb is not reading
an atom right somewhere. This is the only possible flaw I can see at the
moment. Anyone able to understand the spaghetti code of sylpheed and track
down how the message is displayed would also be a boon.
