From: ng0 <contact.ng0@cryptolab.net>
To: "Leo Famulari" <leo@famulari.name>,
"Ludovic Courtès" <ludo@gnu.org>,
25688@debbugs.gnu.org
Subject: bug#25688: services: ssh-daemon quits too early
Date: Sat, 4 Mar 2017 16:47:39 +0000 [thread overview]
Message-ID: <20170304164739.dpyvh5dru2rtyey7@abyayala> (raw)
In-Reply-To: <20170303113612.ulmku5xvxsvscnvm@abyayala>
On 17-03-03 11:36:12, ng0 wrote:
> 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.
>
>
>
Correction, and I'm afraid I have no further insights:
With my system config now moving towards a working all-purpose server
this has been fixed.
On the old (desktop system) configuration this problem continued to
exist, and will probably still be reproducible.
prev parent reply other threads:[~2017-03-04 15:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-11 14:17 bug#25688: services: ssh-daemon quits too early ng0
2017-02-11 14:40 ` Ludovic Courtès
2017-02-11 15:00 ` ng0
2017-02-11 21:18 ` Ludovic Courtès
2017-02-12 14:14 ` ng0
2017-02-12 16:17 ` Ludovic Courtès
2017-02-12 16:23 ` ng0
2017-03-02 21:58 ` Leo Famulari
2017-03-02 22:20 ` ng0
2017-03-03 11:36 ` ng0
2017-03-04 16:47 ` ng0 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170304164739.dpyvh5dru2rtyey7@abyayala \
--to=contact.ng0@cryptolab.net \
--cc=25688@debbugs.gnu.org \
--cc=leo@famulari.name \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.