From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 14:29:24 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 723EB106564A for ; Mon, 26 Jan 2009 14:29:24 +0000 (UTC) (envelope-from ken@mthelicon.com) Received: from hercules.mthelicon.com (hercules.mthelicon.com [IPv6:2001:49f0:2023::2]) by mx1.freebsd.org (Postfix) with ESMTP id 3811F8FC0C for ; Mon, 26 Jan 2009 14:29:24 +0000 (UTC) (envelope-from ken@mthelicon.com) Received: from PegaPegII (93-152-14-233.daisydsl.managedbroadband.co.uk [93.152.14.233]) (authenticated bits=0) by hercules.mthelicon.com (8.14.3/8.14.3) with ESMTP id n0QETMW8006760 for ; Mon, 26 Jan 2009 14:29:23 GMT (envelope-from ken@mthelicon.com) Message-ID: <88F83F222F2347A088A7A7AE8ABF2558@PegaPegII> From: "Pegasus Mc Cleaft" To: Date: Mon, 26 Jan 2009 14:29:21 -0000 Organization: Feathers MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Windows Mail 6.0.6001.18000 X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049 X-Antivirus: avast! (VPS 090125-0, 25/01/2009), Outbound message X-Antivirus-Status: Clean Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: KDE4/DBUS weirdness on -Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Pegasus Mc Cleaft List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jan 2009 14:29:24 -0000 Hello Current,=20 First I appologize for not having much debug information, as I = havent been able to pinpoint an exact cause yet, but I noticed something = odd with -Current 25012009. After updating all my ports while running on = a 23012009-Current and rebooting, everything seemed to work fine; = however, after updating usr/src from about 11pm on 25012009, KDE started = to act really strange.=20 After poking around with various things, I discovered that the dbus = daemon stopped responding. This manifisted its self by clicking on icons = and having the window manager lock up for about 1 minute. After which, a = message came back that the dbus daemon could not be contacted. I tried = dbus-monitor, but got exactly the same message. I tried both USB1 and = USB2 stacks, just to make sure, but could never get things to copperate. = I did find, right after logging in through KDM, I could get a single = application to launch (So DBUS had to been ok at this point) but after = about 5 seconds, DBUS would stop responding) I reverted my kernel to the version before the upgrade (kernel.old) = and everything started to work fine again (I am running on the more = recent world and the old kernel).=20 I am not really sure how to find the exact failure here, but I can = duplicate the fault by loading the 25th's kernel.=20 Machine is a Core2-quad running on AMD64, 8 Gig, USB1 or USB2 stack. Does anyone have any insight to what this might be? (Or how I might = be able to diagnose further) ~Peg