From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 01F451381F3 for ; Thu, 11 Jul 2013 15:46:27 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6EF79E0A8D; Thu, 11 Jul 2013 15:46:19 +0000 (UTC) Received: from smtpout.karoo.kcom.com (smtpout.karoo.kcom.com [212.50.160.34]) by pigeon.gentoo.org (Postfix) with ESMTP id 3CD84E0A52 for ; Thu, 11 Jul 2013 15:46:17 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.87,1043,1363132800"; d="scan'208";a="22921631" Received: from unknown (HELO compaq.stroller.uk.eu.org) ([213.152.39.89]) by smtpout.karoo.kcom.com with ESMTP; 11 Jul 2013 16:45:58 +0100 Received: from [192.168.11.3] (unknown [192.168.11.3]) by compaq.stroller.uk.eu.org (Postfix) with ESMTP id 7B003AC6C8 for ; Thu, 11 Jul 2013 16:45:13 +0100 (BST) Content-Type: text/plain; charset=us-ascii Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 (Apple Message framework v1283) Subject: Re: [gentoo-user] dbus problems - am I the only one who has these? From: Stroller In-Reply-To: <20130711132736.2544c7a5@digimed.co.uk> Date: Thu, 11 Jul 2013 16:45:18 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <70AE7DC9-5CF8-4446-8838-3B6A94D25E9B@stellar.eclipse.co.uk> References: <1373524589.2467.2@numa-i> <20130711093104.1cc796e6@hactar. digimed.co.uk> <1373535173.2467.4@numa-i> <51DE7D49.80809@gentoo.org> <20130711132736.2544c7a5@digimed.co.uk> To: gentoo-user@lists.gentoo.org X-Mailer: Apple Mail (2.1283) X-Archives-Salt: 3138ae8d-c18a-4835-8705-375ec0978c2b X-Archives-Hash: ea6671c9aa0a66d1d6436920a77f76ec On 11 July 2013, at 13:27, Neil Bothwick wrote: > ... >> So... Instead, the problem is often solved by simple re-emerge: >>=20 >> # emerge -1 glib dbus dbus-glib >=20 > Often, maybe - always, definitely not. This machine has suffered from > that issue for some time and none of the suggested solutions, = including > that one, or a few more desperate measures, have made any difference. It's not for me to tell you what to do, but in this case the bug should = be taken to the dbus developers. They'll probably want to know about it, and probably be glad to help you = fix it. Stroller.