* Fix assertion on startup due to dark mode window.
For whatever reason, this window must be destroyed, not unrefed.
* Fix some assertions on shutdown.
The GTK buddy list GObject is finalized before the Purple buddy list, so when Purple deletes nodes, the GTK list model is NULL, and prints out a bunch of assertions.
Testing Done:
Run with debug messages and see they're gone.
Reviewed at https://reviews.imfreedom.org/r/446/
/* purple
*
* Purple is the legal property of its developers, whose names are too numerous
* to list here. Please refer to the COPYRIGHT file distributed with this
* source distribution.
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation; either version 2 of the License, or
* (at your option) any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program; if not, write to the Free Software
* Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02111-1301 USA
*/
#include"internal.h"
#include"debug.h"
#include"prefs.h"
#include"util.h"
staticPurpleDebugUi*debug_ui=NULL;
/*
* This determines whether debug info should be written to the
* console or not.
*
* It doesn't make sense to make this a normal Purple preference
* because it's a command line option. This will always be FALSE,
* unless the user explicitly started the UI with the -d flag.
* It doesn't matter what this value was the last time Purple was
* started, so it doesn't make sense to save it in prefs.
*/
staticgbooleandebug_enabled=FALSE;
/*
* These determine whether verbose or unsafe debugging are desired. I
* don't want to make these purple preferences because their values should