comparison libpurple/core.c @ 26724:e07c066b3172

don't uninit accounts until savedstatus and status are uninited, this was never a problem until aff70668336849d4b1513fd8577f4d2a276d2520 which cleaned up accounts (which is itself a good thing) but savedstatus was using the uninitialized accounts (which is a bad thing) mtn using people probably want to check their status.xml for corrupted entries
author Ka-Hing Cheung <khc@hxbc.us>
date Tue, 28 Apr 2009 19:10:04 +0000
parents 8a0797f40695
children 01f1929d0936
comparison
equal deleted inserted replaced
26723:5325d2185e88 26724:e07c066b3172
229 purple_ciphers_uninit(); 229 purple_ciphers_uninit();
230 purple_notify_uninit(); 230 purple_notify_uninit();
231 purple_conversations_uninit(); 231 purple_conversations_uninit();
232 purple_connections_uninit(); 232 purple_connections_uninit();
233 purple_buddy_icons_uninit(); 233 purple_buddy_icons_uninit();
234 purple_accounts_uninit();
235 purple_savedstatuses_uninit(); 234 purple_savedstatuses_uninit();
236 purple_status_uninit(); 235 purple_status_uninit();
236 purple_accounts_uninit();
237 purple_sound_uninit(); 237 purple_sound_uninit();
238 purple_theme_manager_uninit(); 238 purple_theme_manager_uninit();
239 purple_xfers_uninit(); 239 purple_xfers_uninit();
240 purple_proxy_uninit(); 240 purple_proxy_uninit();
241 purple_dnsquery_uninit(); 241 purple_dnsquery_uninit();