Mailinglist Archive: opensuse-bugs (4283 mails)

< Previous Next >
[Bug 1020363] [Build 20170116] Restarting graphical target via systemd isolate stops session D-Bus
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 09 May 2017 01:13:57 +0000
  • Message-id: <bug-1020363-21960-o2j4QS1pq0@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363#c14

--- Comment #14 from Simon Lees <simonf.lees@xxxxxxxx> ---
(In reply to patrick shanahan from comment #13)
(In reply to Simon Lees from comment #12)
(In reply to patrick shanahan from comment #11)
I would be happy to provide information. But I only just found the
request
for information by checking status of the report. Seems even though I an
listed on the cc: list, I have not received any notice.(In reply to Simon
Lees from comment #8)
Patrick I guess we need to debug your issue further to work out whats
preventing dbus from closing in this case could you provide the output
of
"systemctl status user-XXX.slice" where XXX is your uid?


Thanks for the info, i'll try and replicate this tomorrow, its not what I
was expecting to see. dbus isn't running in the multi-user.target (which is
expected if nothing is using it) so nothing should be preventing it from
running when the graphical target is started.

Just confirming you are running tumbleweed?

yes, 20170505

info may be skewed by having remote ssh access. I can alway trigger the
failure that way. I can open a graphical session from an clean boot w/o any
remote ssh sessions active.

did you want to see the output w/o the remote session?

ps: there is a problem with mail, I am not receiving and my addr is listed
in cc

I can replicate the problem here so i'll chase it up with upstream to see what
we can do about it.

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >