removed dbus

5 files changed, 0 insertions, 649 deletions

diff --git a/sys-apps/dbus/Manifest b/sys-apps/dbus/Manifest
deleted file mode 100644
index dca75ea..0000000
--- a/sys-apps/dbus/Manifest
+++ /dev/null
@@ -1,5 +0,0 @@
-AUX 30-dbus 243 RMD160 b5e7a813cd5d91f2ea60bb22260e432cbfb72fd9 SHA1 35ee3a5d3db9c7e372603ce916e17a41edd01d36 SHA256 a8e8fec9769cc5d46df8216f7d1e1f9df422c4e46f293fd70d4b017fb01d959d
-AUX dbus.init-1.0 1152 RMD160 f0f409b59167beef2e2b8c14f701fbeaa54c3bc9 SHA1 b00e23868046c67eaec87220e92ffcea5d9dd911 SHA256 a2e13a025faa488ff35521188c0d44909bc82c55e8676a24a5a5179545303d98
-AUX multithread-locking-fix.patch 17654 RMD160 3e3c6a248cfdea8e75696a5b8f474635c86b2e7a SHA1 7ab1b7ec78ffc1f285d9c73cdba431e4058a97ac SHA256 47f9cbb50e0deedd6fee2f6d495295237b8507628f0de64a28e966b9a07f43bd
-DIST dbus-1.2.24.tar.gz 1673774 RMD160 2f51def784056bc16fbec2ddc3be22c022a94fb5 SHA1 9593717348ea36ba228b46f165bb67c127c12be8 SHA256 f12c748f4a703655e3d4c3db94cdf5a752a0cd0b36958c715804373bd3595c48
-EBUILD dbus-1.2.24-r1.ebuild 3708 RMD160 04f4578546eb99bbe1b09032ce930d6884715abd SHA1 2d0f8a60c5a9d19d68970414fdd9d535c3ff8afd SHA256 78cccae929826403a18b124d13096c96e9f32cc512d0afd434f7c29e7ff3bc11
diff --git a/sys-apps/dbus/dbus-1.2.24-r1.ebuild b/sys-apps/dbus/dbus-1.2.24-r1.ebuild
deleted file mode 100644
index 2d7d9da..0000000
--- a/sys-apps/dbus/dbus-1.2.24-r1.ebuild
+++ /dev/null
@@ -1,129 +0,0 @@
-# Copyright 1999-2010 Gentoo Foundation
-# Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/sys-apps/dbus/dbus-1.2.24.ebuild,v 1.8 2010/05/24 15:18:41 armin76 Exp $
-
-EAPI=2
-
-inherit eutils multilib flag-o-matic
-
-DESCRIPTION="A message bus system, a simple way for applications to talk to each other, includes threading fix"
-HOMEPAGE="http://dbus.freedesktop.org/"
-SRC_URI="http://dbus.freedesktop.org/releases/dbus/${P}.tar.gz"
-
-LICENSE="|| ( GPL-2 AFL-2.1 )"
-SLOT="0"
-KEYWORDS="~amd64"
-IUSE="debug doc selinux test X"
-
-RDEPEND="X? ( x11-libs/libXt x11-libs/libX11 )
-	selinux? ( sys-libs/libselinux
-				sec-policy/selinux-dbus )
-	>=dev-libs/expat-1.95.8
-	!<sys-apps/dbus-0.91"
-DEPEND="${RDEPEND}
-	dev-util/pkgconfig
-	doc? (	app-doc/doxygen
-		app-text/xmlto )"
-
-pkg_setup() {
-	enewgroup messagebus
-	enewuser messagebus -1 "-1" -1 messagebus
-}
-
-src_prepare() {
-	# Tests were restricted because of this
-	sed -e 's/.*bus_dispatch_test.*/printf ("Disabled due to excess noise\\n");/' \
-	-e '/"dispatch"/d' -i "${S}/bus/test-main.c"
-	epatch ${FILESDIR}/multithread-locking-fix.patch || die
-}
-
-src_configure() {
-	# so we can get backtraces from apps
-	append-flags -rdynamic
-
-	# libaudit is *only* used in DBus wrt SELinux support, so disable it, if
-	# not on an SELinux profile.
-	econf \
-		$(use_with X x) \
-		$(use_enable kernel_linux inotify) \
-		$(use_enable kernel_FreeBSD kqueue) \
-		$(use_enable selinux) \
-		$(use_enable selinux libaudit)	\
-		$(use_enable debug verbose-mode) \
-		$(use_enable debug asserts) \
-		$(use_enable test tests) \
-		$(use_enable test asserts) \
-		--with-xml=expat \
-		--with-system-pid-file=/var/run/dbus.pid \
-		--with-system-socket=/var/run/dbus/system_bus_socket \
-		--with-session-socket-dir=/tmp \
-		--with-dbus-user=messagebus \
-		--localstatedir=/var \
-		$(use_enable doc doxygen-docs) \
-		--disable-xml-docs \
-		|| die "econf failed"
-
-	# after the compile, it uses a selinuxfs interface to
-	# check if the SELinux policy has the right support
-	use selinux && addwrite /selinux/access
-}
-
-src_test() {
-	DBUS_VERBOSE=1 make check || die "make check failed"
-}
-
-src_install() {
-	emake DESTDIR="${D}" install || die "make install failed"
-
-	# initscript
-	newinitd "${FILESDIR}"/dbus.init-1.0 dbus || die
-
-	if use X ; then
-		# dbus X session script (#77504)
-		# turns out to only work for GDM. has been merged into other desktop
-		# (kdm and such scripts)
-		exeinto /etc/X11/xinit/xinitrc.d/
-		doexe "${FILESDIR}"/30-dbus
-	fi
-
-	# needs to exist for the system socket
-	keepdir /var/run/dbus
-	# needs to exist for machine id
-	keepdir /var/lib/dbus
-	# needs to exist for dbus sessions to launch
-
-	keepdir /usr/lib/dbus-1.0/services
-	keepdir /usr/share/dbus-1/services
-	keepdir /etc/dbus-1/system.d/
-	keepdir /etc/dbus-1/session.d/
-
-	dodoc AUTHORS ChangeLog HACKING NEWS README doc/TODO
-	if use doc; then
-		dohtml doc/*html
-	fi
-}
-
-pkg_postinst() {
-	elog "To start the D-Bus system-wide messagebus by default"
-	elog "you should add it to the default runlevel :"
-	elog "\`rc-update add dbus default\`"
-	elog
-	elog "Some applications require a session bus in addition to the system"
-	elog "bus. Please see \`man dbus-launch\` for more information."
-	elog
-	ewarn "You must restart D-Bus \`/etc/init.d/dbus restart\` to run"
-	ewarn "the new version of the daemon."
-
-	if has_version x11-base/xorg-server[hal]; then
-		elog
-		ewarn "You are currently running X with the hal useflag enabled"
-		ewarn "restarting the dbus service WILL restart X as well"
-		ebeep 5
-	fi
-
-	if use test; then
-		elog
-		ewarn "You have unit tests enabled, this results in an insecure library"
-		ewarn "It is recommended that you reinstall *without* FEATURES=test"
-	fi
-}
diff --git a/sys-apps/dbus/files/30-dbus b/sys-apps/dbus/files/30-dbus
deleted file mode 100644
index 603e92d..0000000
--- a/sys-apps/dbus/files/30-dbus
+++ /dev/null
@@ -1,9 +0,0 @@
-#!/bin/bash
-
-# launches a session dbus instance
-
-dbuslaunch="`which dbus-launch 2>/dev/null`"
-if [ -n "$dbuslaunch" ] && [ -x "$dbuslaunch" ] && [ -z "$DBUS_SESSION_BUS_ADDRESS" ]; then
-  eval `$dbuslaunch --sh-syntax --exit-with-session`
-fi
-
diff --git a/sys-apps/dbus/files/dbus.init-1.0 b/sys-apps/dbus/files/dbus.init-1.0
deleted file mode 100644
index e96ea05..0000000
--- a/sys-apps/dbus/files/dbus.init-1.0
+++ /dev/null
@@ -1,51 +0,0 @@
-#!/sbin/runscript
-# Copyright 1999-2004 Gentoo Foundation
-# Distributed under the terms of the GNU General Public License, v2 or later
-# $Header: /var/cvsroot/gentoo-x86/sys-apps/dbus/files/dbus.init-1.0,v 1.4 2007/04/04 13:35:25 cardoe Exp $
-
-opts="reload"
-
-depend() {
-	need localmount
-	after bootmisc
-}
-
-start() {
-	ebegin "Starting D-BUS system messagebus"
-
-	/usr/bin/dbus-uuidgen --ensure
-
-	# We need to test if /var/run/dbus exists, since script will fail if it does not
-	[ ! -e /var/run/dbus ] && mkdir /var/run/dbus 
-
-	start-stop-daemon --start --pidfile /var/run/dbus.pid --exec /usr/bin/dbus-daemon -- --system
-	eend $?
-}
-
-stop() {
-	local retval
-
-	ebegin "Stopping D-BUS system messagebus"
-
-	start-stop-daemon --stop --pidfile /var/run/dbus.pid
-	retval=$?
-
-	eend ${retval}
-
-	[ -S /var/run/dbus/system_bus_socket ] && rm -f /var/run/dbus/system_bus_socket
-
-	return ${retval}
-}
-
-reload() {
-	local retval
-
-	ebegin "Reloading D-BUS messagebus config"
-	
-	/usr/bin/dbus-send --print-reply --system --type=method_call \
-			--dest=org.freedesktop.DBus \
-			/ org.freedesktop.DBus.ReloadConfig > /dev/null
-	retval=$?
-	eend ${retval}
-	return ${retval}
-}
diff --git a/sys-apps/dbus/files/multithread-locking-fix.patch b/sys-apps/dbus/files/multithread-locking-fix.patch
deleted file mode 100644
index 743c398..0000000
--- a/sys-apps/dbus/files/multithread-locking-fix.patch
+++ /dev/null
@@ -1,455 +0,0 @@
-2008-01-01  Havoc Pennington  <hp at redhat.com>
-
-	Patch based on one from Olivier Hochreutiner <olivier.hochreutiner
-	gmail.com>
-
-	* dbus/dbus-connection.c (protected_change_timeout): remove the
-	elaborate nonworking hack to try to drop locks and just keep the
-	locks; this isn't right either, but at least is correct, though
-	it puts restrictions on apps.
-
-	* dbus/dbus-connection.c (protected_change_watch): make the same
-	change as for timeouts
-
-	* dbus/dbus-connection.c (dbus_connection_set_timeout_functions):
-	don't drop the lock here; add documentation of the problem to API
-	docs
-	(dbus_connection_set_watch_functions): same
-
-	* dbus/dbus-connection.c (dbus_connection_get_data)
-	(dbus_connection_set_data): introduce a separate slot_mutex
-	protecting connection->slot_list so these two functions can be
-	called inside watch and timeout functions. Not sure this
-	is going to be a good idea.
-
-	* dbus/dbus-connection.c (dbus_connection_unref)
-	(dbus_connection_ref): avoid using connection lock in ref/unref
-	so these can also be used in watch and timeout functions
----
- ChangeLog              |   28 +++++++
- dbus/dbus-connection.c |  196 ++++++++++++++++++++++++++----------------------
- 2 files changed, 134 insertions(+), 90 deletions(-)
-
-diff --git a/ChangeLog b/ChangeLog
-index 35e35a7..ec761f3 100644
---- a/ChangeLog
-+++ b/ChangeLog
-@@ -1,3 +1,31 @@
-+2008-01-01  Havoc Pennington  <hp at redhat.com>
-+
-+	Patch based on one from Olivier Hochreutiner <olivier.hochreutiner
-+	gmail.com>
-+	
-+	* dbus/dbus-connection.c (protected_change_timeout): remove the
-+	elaborate nonworking hack to try to drop locks and just keep the
-+	locks; this isn't right either, but at least is correct, though
-+	it puts restrictions on apps.
-+
-+	* dbus/dbus-connection.c (protected_change_watch): make the same
-+	change as for timeouts	
-+
-+	* dbus/dbus-connection.c (dbus_connection_set_timeout_functions):
-+	don't drop the lock here; add documentation of the problem to API
-+	docs
-+	(dbus_connection_set_watch_functions): same
-+
-+	* dbus/dbus-connection.c (dbus_connection_get_data)
-+	(dbus_connection_set_data): introduce a separate slot_mutex
-+	protecting connection->slot_list so these two functions can be
-+	called inside watch and timeout functions. Not sure this 
-+	is going to be a good idea.
-+
-+	* dbus/dbus-connection.c (dbus_connection_unref)
-+	(dbus_connection_ref): avoid using connection lock in ref/unref 
-+	so these can also be used in watch and timeout functions
-+	
- 2008-04-16  John (J5) Palmieri <johnp@redhat.com>
- 
- 	* tools/dbus-monitor.c: take out the trailing comma in the
-diff --git a/dbus/dbus-connection.c b/dbus/dbus-connection.c
-index 0de5f22..177fb2e 100644
---- a/dbus/dbus-connection.c
-+++ b/dbus/dbus-connection.c
-@@ -73,6 +73,14 @@
-     _dbus_mutex_unlock ((connection)->mutex);                                            \
-   } while (0)
- 
-+#define SLOTS_LOCK(connection) do {                     \
-+    _dbus_mutex_lock ((connection)->slot_mutex);        \
-+  } while (0)
-+
-+#define SLOTS_UNLOCK(connection) do {                   \
-+    _dbus_mutex_unlock ((connection)->slot_mutex);      \
-+  } while (0)
-+
- #define DISPATCH_STATUS_NAME(s)                                            \
-                      ((s) == DBUS_DISPATCH_COMPLETE ? "complete" :         \
-                       (s) == DBUS_DISPATCH_DATA_REMAINS ? "data remains" : \
-@@ -257,6 +265,7 @@ struct DBusConnection
-   
-   DBusList *filter_list;        /**< List of filters. */
- 
-+  DBusMutex *slot_mutex;        /**< Lock on slot_list so overall connection lock need not be taken */
-   DBusDataSlotList slot_list;   /**< Data stored by allocated integer ID */
- 
-   DBusHashTable *pending_replies;  /**< Hash of message serials to #DBusPendingCall. */  
-@@ -647,38 +656,42 @@ protected_change_watch (DBusConnection         *connection,
-                         DBusWatchToggleFunction toggle_function,
-                         dbus_bool_t             enabled)
- {
--  DBusWatchList *watches;
-   dbus_bool_t retval;
-   
-   HAVE_LOCK_CHECK (connection);
- 
--  /* This isn't really safe or reasonable; a better pattern is the "do everything, then
--   * drop lock and call out" one; but it has to be propagated up through all callers
-+  /* The original purpose of protected_change_watch() was to hold a
-+   * ref on the connection while dropping the connection lock, then
-+   * calling out to the app.  This was a broken hack that did not
-+   * work, since the connection was in a hosed state (no WatchList
-+   * field) while calling out.
-+   *
-+   * So for now we'll just keep the lock while calling out. This means
-+   * apps are not allowed to call DBusConnection methods inside a
-+   * watch function or they will deadlock.
-+   * 
-+   * The "real fix" is to use the _and_unlock() pattern found
-+   * elsewhere in the code, to defer calling out to the app until
-+   * we're about to drop locks and return flow of control to the app
-+   * anyway.
-+   *
-+   * See http://lists.freedesktop.org/archives/dbus/2007-July/thread.html#8144
-    */
-   
--  watches = connection->watches;
--  if (watches)
-+  if (connection->watches)
-     {
--      connection->watches = NULL;
--      _dbus_connection_ref_unlocked (connection);
--      CONNECTION_UNLOCK (connection);
--
-       if (add_function)
--        retval = (* add_function) (watches, watch);
-+        retval = (* add_function) (connection->watches, watch);
-       else if (remove_function)
-         {
-           retval = TRUE;
--          (* remove_function) (watches, watch);
-+          (* remove_function) (connection->watches, watch);
-         }
-       else
-         {
-           retval = TRUE;
--          (* toggle_function) (watches, watch, enabled);
-+          (* toggle_function) (connection->watches, watch, enabled);
-         }
--      
--      CONNECTION_LOCK (connection);
--      connection->watches = watches;
--      _dbus_connection_unref_unlocked (connection);
- 
-       return retval;
-     }
-@@ -768,39 +781,43 @@ protected_change_timeout (DBusConnection           *connection,
-                           DBusTimeoutToggleFunction toggle_function,
-                           dbus_bool_t               enabled)
- {
--  DBusTimeoutList *timeouts;
-   dbus_bool_t retval;
-   
-   HAVE_LOCK_CHECK (connection);
- 
--  /* This isn't really safe or reasonable; a better pattern is the "do everything, then
--   * drop lock and call out" one; but it has to be propagated up through all callers
-+  /* The original purpose of protected_change_timeout() was to hold a
-+   * ref on the connection while dropping the connection lock, then
-+   * calling out to the app.  This was a broken hack that did not
-+   * work, since the connection was in a hosed state (no TimeoutList
-+   * field) while calling out.
-+   *
-+   * So for now we'll just keep the lock while calling out. This means
-+   * apps are not allowed to call DBusConnection methods inside a
-+   * timeout function or they will deadlock.
-+   * 
-+   * The "real fix" is to use the _and_unlock() pattern found
-+   * elsewhere in the code, to defer calling out to the app until
-+   * we're about to drop locks and return flow of control to the app
-+   * anyway.
-+   *
-+   * See http://lists.freedesktop.org/archives/dbus/2007-July/thread.html#8144
-    */
-   
--  timeouts = connection->timeouts;
--  if (timeouts)
-+  if (connection->timeouts)
-     {
--      connection->timeouts = NULL;
--      _dbus_connection_ref_unlocked (connection);
--      CONNECTION_UNLOCK (connection);
--
-       if (add_function)
--        retval = (* add_function) (timeouts, timeout);
-+        retval = (* add_function) (connection->timeouts, timeout);
-       else if (remove_function)
-         {
-           retval = TRUE;
--          (* remove_function) (timeouts, timeout);
-+          (* remove_function) (connection->timeouts, timeout);
-         }
-       else
-         {
-           retval = TRUE;
--          (* toggle_function) (timeouts, timeout, enabled);
-+          (* toggle_function) (connection->timeouts, timeout, enabled);
-         }
-       
--      CONNECTION_LOCK (connection);
--      connection->timeouts = timeouts;
--      _dbus_connection_unref_unlocked (connection);
--
-       return retval;
-     }
-   else
-@@ -1219,6 +1236,10 @@ _dbus_connection_new_for_transport (DBusTransport *transport)
-   if (connection->io_path_cond == NULL)
-     goto error;
- 
-+  _dbus_mutex_new_at_location (&connection->slot_mutex);
-+  if (connection->slot_mutex == NULL)
-+    goto error;
-+  
-   disconnect_message = dbus_message_new_signal (DBUS_PATH_LOCAL,
-                                                 DBUS_INTERFACE_LOCAL,
-                                                 "Disconnected");
-@@ -1295,6 +1316,7 @@ _dbus_connection_new_for_transport (DBusTransport *transport)
-       _dbus_mutex_free_at_location (&connection->mutex);
-       _dbus_mutex_free_at_location (&connection->io_path_mutex);
-       _dbus_mutex_free_at_location (&connection->dispatch_mutex);
-+      _dbus_mutex_free_at_location (&connection->slot_mutex);
-       dbus_free (connection);
-     }
-   if (pending_replies)
-@@ -2467,9 +2489,15 @@ dbus_connection_ref (DBusConnection *connection)
-   
-   /* The connection lock is better than the global
-    * lock in the atomic increment fallback
-+   *
-+   * (FIXME but for now we always use the atomic version,
-+   * to avoid taking the connection lock, due to
-+   * the mess with set_timeout_functions()/set_watch_functions()
-+   * calling out to the app without dropping locks)
-    */
-   
--#ifdef DBUS_HAVE_ATOMIC_INT
-+  /* #ifdef DBUS_HAVE_ATOMIC_INT */
-+#if 1
-   _dbus_atomic_inc (&connection->refcount);
- #else
-   CONNECTION_LOCK (connection);
-@@ -2581,6 +2609,8 @@ _dbus_connection_last_unref (DBusConnection *connection)
-   _dbus_mutex_free_at_location (&connection->io_path_mutex);
-   _dbus_mutex_free_at_location (&connection->dispatch_mutex);
- 
-+  _dbus_mutex_free_at_location (&connection->slot_mutex);
-+  
-   _dbus_mutex_free_at_location (&connection->mutex);
-   
-   dbus_free (connection);
-@@ -2615,9 +2645,15 @@ dbus_connection_unref (DBusConnection *connection)
-   
-   /* The connection lock is better than the global
-    * lock in the atomic increment fallback
-+   * 
-+   * (FIXME but for now we always use the atomic version,
-+   * to avoid taking the connection lock, due to
-+   * the mess with set_timeout_functions()/set_watch_functions()
-+   * calling out to the app without dropping locks)   
-    */
-   
--#ifdef DBUS_HAVE_ATOMIC_INT
-+  /* #ifdef DBUS_HAVE_ATOMIC_INT */
-+#if 1
-   last_unref = (_dbus_atomic_dec (&connection->refcount) == 1);
- #else
-   CONNECTION_LOCK (connection);
-@@ -4550,10 +4586,12 @@ dbus_connection_dispatch (DBusConnection *connection)
-  * should be that dbus_connection_set_watch_functions() has no effect,
-  * but the add_function and remove_function may have been called.
-  *
-- * @todo We need to drop the lock when we call the
-- * add/remove/toggled functions which can be a side effect
-- * of setting the watch functions.
-- * 
-+ * @note For now, the thread lock on DBusConnection is held while
-+ * watch functions are invoked, so inside these functions you
-+ * may not invoke any methods on DBusConnection or it will deadlock.
-+ * See the comments in the code or http://lists.freedesktop.org/archives/dbus/2007-July/thread.html#8144
-+ * if you encounter this issue and want to attempt writing a patch.
-+ *
-  * @param connection the connection.
-  * @param add_function function to begin monitoring a new descriptor.
-  * @param remove_function function to stop monitoring a descriptor.
-@@ -4571,42 +4609,17 @@ dbus_connection_set_watch_functions (DBusConnection              *connection,
-                                      DBusFreeFunction             free_data_function)
- {
-   dbus_bool_t retval;
--  DBusWatchList *watches;
- 
-   _dbus_return_val_if_fail (connection != NULL, FALSE);
-   
-   CONNECTION_LOCK (connection);
- 
--#ifndef DBUS_DISABLE_CHECKS
--  if (connection->watches == NULL)
--    {
--      _dbus_warn_check_failed ("Re-entrant call to %s is not allowed\n",
--                               _DBUS_FUNCTION_NAME);
--      return FALSE;
--    }
--#endif
--  
--  /* ref connection for slightly better reentrancy */
--  _dbus_connection_ref_unlocked (connection);
--
--  /* This can call back into user code, and we need to drop the
--   * connection lock when it does. This is kind of a lame
--   * way to do it.
--   */
--  watches = connection->watches;
--  connection->watches = NULL;
--  CONNECTION_UNLOCK (connection);
--
--  retval = _dbus_watch_list_set_functions (watches,
-+  retval = _dbus_watch_list_set_functions (connection->watches,
-                                            add_function, remove_function,
-                                            toggled_function,
-                                            data, free_data_function);
--  CONNECTION_LOCK (connection);
--  connection->watches = watches;
-   
-   CONNECTION_UNLOCK (connection);
--  /* drop our paranoid refcount */
--  dbus_connection_unref (connection);
-   
-   return retval;
- }
-@@ -4636,6 +4649,12 @@ dbus_connection_set_watch_functions (DBusConnection              *connection,
-  * given remove_function.  The timer interval may change whenever the
-  * timeout is added, removed, or toggled.
-  *
-+ * @note For now, the thread lock on DBusConnection is held while
-+ * timeout functions are invoked, so inside these functions you
-+ * may not invoke any methods on DBusConnection or it will deadlock.
-+ * See the comments in the code or http://lists.freedesktop.org/archives/dbus/2007-July/thread.html#8144
-+ * if you encounter this issue and want to attempt writing a patch.
-+ * 
-  * @param connection the connection.
-  * @param add_function function to add a timeout.
-  * @param remove_function function to remove a timeout.
-@@ -4653,38 +4672,17 @@ dbus_connection_set_timeout_functions   (DBusConnection            *connection,
- 					 DBusFreeFunction           free_data_function)
- {
-   dbus_bool_t retval;
--  DBusTimeoutList *timeouts;
- 
-   _dbus_return_val_if_fail (connection != NULL, FALSE);
-   
-   CONNECTION_LOCK (connection);
--
--#ifndef DBUS_DISABLE_CHECKS
--  if (connection->timeouts == NULL)
--    {
--      _dbus_warn_check_failed ("Re-entrant call to %s is not allowed\n",
--                               _DBUS_FUNCTION_NAME);
--      return FALSE;
--    }
--#endif
-   
--  /* ref connection for slightly better reentrancy */
--  _dbus_connection_ref_unlocked (connection);
--
--  timeouts = connection->timeouts;
--  connection->timeouts = NULL;
--  CONNECTION_UNLOCK (connection);
--  
--  retval = _dbus_timeout_list_set_functions (timeouts,
-+  retval = _dbus_timeout_list_set_functions (connection->timeouts,
-                                              add_function, remove_function,
-                                              toggled_function,
-                                              data, free_data_function);
--  CONNECTION_LOCK (connection);
--  connection->timeouts = timeouts;
-   
-   CONNECTION_UNLOCK (connection);
--  /* drop our paranoid refcount */
--  dbus_connection_unref (connection);
- 
-   return retval;
- }
-@@ -5612,6 +5610,15 @@ dbus_connection_free_data_slot (dbus_int32_t *slot_p)
-  * the connection is finalized. The slot number
-  * must have been allocated with dbus_connection_allocate_data_slot().
-  *
-+ * @note As a temporary hack, this function does not take the
-+ * main thread lock on DBusConnection, which allows it to be
-+ * used from inside watch and timeout functions. (See the
-+ * note in docs for dbus_connection_set_watch_functions().)
-+ * A side effect of this is that you need to know there's
-+ * a reference held on the connection while invoking
-+ * dbus_connection_set_data(), or the connection could be
-+ * finalized during dbus_connection_set_data().
-+ * 
-  * @param connection the connection
-  * @param slot the slot number
-  * @param data the data to store
-@@ -5631,14 +5638,14 @@ dbus_connection_set_data (DBusConnection   *connection,
-   _dbus_return_val_if_fail (connection != NULL, FALSE);
-   _dbus_return_val_if_fail (slot >= 0, FALSE);
-   
--  CONNECTION_LOCK (connection);
-+  SLOTS_LOCK (connection);
- 
-   retval = _dbus_data_slot_list_set (&slot_allocator,
-                                      &connection->slot_list,
-                                      slot, data, free_data_func,
-                                      &old_free_func, &old_data);
-   
--  CONNECTION_UNLOCK (connection);
-+  SLOTS_UNLOCK (connection);
- 
-   if (retval)
-     {
-@@ -5654,6 +5661,15 @@ dbus_connection_set_data (DBusConnection   *connection,
-  * Retrieves data previously set with dbus_connection_set_data().
-  * The slot must still be allocated (must not have been freed).
-  *
-+ * @note As a temporary hack, this function does not take the
-+ * main thread lock on DBusConnection, which allows it to be
-+ * used from inside watch and timeout functions. (See the
-+ * note in docs for dbus_connection_set_watch_functions().)
-+ * A side effect of this is that you need to know there's
-+ * a reference held on the connection while invoking
-+ * dbus_connection_get_data(), or the connection could be
-+ * finalized during dbus_connection_get_data().
-+ * 
-  * @param connection the connection
-  * @param slot the slot to get data from
-  * @returns the data, or #NULL if not found
-@@ -5666,13 +5682,13 @@ dbus_connection_get_data (DBusConnection   *connection,
- 
-   _dbus_return_val_if_fail (connection != NULL, NULL);
-   
--  CONNECTION_LOCK (connection);
-+  SLOTS_LOCK (connection);
- 
-   res = _dbus_data_slot_list_get (&slot_allocator,
-                                   &connection->slot_list,
-                                   slot);
-   
--  CONNECTION_UNLOCK (connection);
-+  SLOTS_UNLOCK (connection);
- 
-   return res;
- }