It does happen everytime when you mangle your userdb. How to reproduce with a clean new install of kICQ:
1) Start kICQ. Select "old ICQ#", "LAN/firewall", "no socks" (I'm NATted), "110201214", appropriate password, "save passwd". It will "register" your ICQ# (what's there to register if you already _have_ an ICQ#?!?!?). --snip-- Socket created attempting to connect The server acknowledged the command Login successful, UIN: 110201214, IP: 193.196.41.250 Acking --snip-- "Done". It will complain about "you have not set your password or your nick". Twice. 2) Pop up UI, go to preferences, "Connections". Password is missing. Enter Password & Nick (which is also empty). "Ok". --snip-- FoundFromRoot - entry reallocating --snip-- Switch to "online". Krash SIGSEGV. Hmm. This wasn't what I did the first time. Ah. I remember. Instead: 3) Start another kicq since you don't realize there's a new icon. Exit the second kICQ. Open the UI of the original one. Go to preferences. Enter password and nick. Press ok. Get a SIGABRT. Now it will catch a SIGABRT on every startup. I hope you can reproduce it with this information. The workaround is to remove the userdb file and startover, this time not starting a second kicq at the same time.
