From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: bug#25688: services: ssh-daemon quits too early Date: Fri, 3 Mar 2017 11:36:12 +0000 Message-ID: <20170303113612.ulmku5xvxsvscnvm@abyayala> References: <20170211141740.thdgjg5wmyok77kw@wasp> <878tpc3i55.fsf@gnu.org> <20170211150013.6jrpkrh5how4k2e6@wasp> <20170302215835.GA13685@jasmine> <20170302222044.3nedva2wmxicgo2h@abyayala> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41410) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cjkRT-0001LP-NO for bug-guix@gnu.org; Fri, 03 Mar 2017 05:28:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cjkRN-0005dA-Vv for bug-guix@gnu.org; Fri, 03 Mar 2017 05:28:07 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:39235) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cjkRN-0005cw-SX for bug-guix@gnu.org; Fri, 03 Mar 2017 05:28:01 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cjkRN-0007k6-K3 for bug-guix@gnu.org; Fri, 03 Mar 2017 05:28:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <20170302222044.3nedva2wmxicgo2h@abyayala> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Leo Famulari , Ludovic =?UTF-8?Q?Court=C3=A8s?= , 25688@debbugs.gnu.org On 17-03-02 22:20:44, ng0 wrote: > On 17-03-02 16:58:35, Leo Famulari wrote: > > On Sat, Feb 11, 2017 at 03:00:13PM +0000, ng0 wrote: > > > This is the ~120 lines of today. It reminded me of the real issue, which > > > is dbus could not be started, which very likely could be the reason for > > > the GNOME session crashing bug I reported. > > > > Are you still having this problem (dbus-system could not be started)? > > I've recently started to d othe system from 0 again to rule out > offloading issues, but ssh-daemon started failing again. I'll look into > the issue on the weekend. > > > I can confirm this continues to be a problem on the new system, repeatedly: Service user-homes could not be started. The same for ssh-daemon, but now dbus-system can be started and the problem could therefore be user-homes.