[opensuse-factory] systemd dbus start causing problems, still
Bugzilla – Bug 1020363 [Build 20170116] Restarting graphical target via systemd isolate stops session D-Bus Filed 2017-01-10 13:39:45 UTC only reported action, Fabia Vogt on 02-02 marked Bug #1022440 a duplicate. Bug #1022440 also has received no action other than being marked a dup. I anyone even concerned about this? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 05/03/2017 11:30 PM, Patrick Shanahan wrote:
The bug was assigned to bnc-team-xfce i'm not sure if there is even anyone on that mailing list. So thats partly why it hasn't been noticed. As for the actual issue, its likely related to [1] which is about the fact we don't support restarting dbus sessions. With the way we are starting dbus via socket activation maybe when isolating targets the service is being restarted from a quick test as root here it seems that the User Manager was stopped when isolating the target which is where the service was stopped, anyway we should continue this in the bug report. 1. https://bugzilla.suse.com/show_bug.cgi?id=965867 -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On 05/08/2017 04:43 PM, Karl Sinn wrote:
To paraphrase its a big long discussion about how we'd like to support restarting dbus, but that upstream doesn't support it and so if someone has time oneday they will add the feature upstream but for now we will document that its not supported. In this case its unclear if something is not working properly due to the dbus restart or if something is blocking dbus from restarting. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
* Simon Lees <sflees@suse.de> [05-08-17 04:05]:
and we are not allowed to contribute to the bug report or possible solution in *any* way. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 05/08/2017 09:24 PM, Patrick Shanahan wrote:
Well for that particular bug there is nothing to contribute, most software doesn't support dbus being restarted while its running, any change major enough to make that work will need to be done by a dbus developer upstream until then it can't be supported so there is nothing to discuss. If there was something worth discussing further we could go to the effort of making sure all customer / internal SUSE info is marked as private and then make the actual report public, or maybe create a duplicate more general bug report that doesn't start as a customer report. In this case there is no need, we should work from one of the other existing openSUSE reports that you have already commented on. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
* Simon Lees <sflees@suse.de> [05-08-17 08:24]:
tks, info you requested is provided to bug report #1020363. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 08-05-2017 a las 8:54, Patrick Shanahan escribió:
and we are not allowed to contribute to the bug report or possible solution in *any* way.
Dbus does not preserve state on restart..that's all folks! thanks for watching ! it won't be implemented, not at least with the traditional dbus daemon. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Cristian Rodríguez <crrodriguez@opensuse.org> [05-08-17 10:07]:
so the *only* answer is: ## Workaround Remove the symlink `/usr/lib/systemd/user/sockets.target.wants/dbus.socket` for the old behavior (session D-Bus no longer started via systemd). as no solution will be implemented. ps: I cannot start the graphic target from anywhere if I have an open remote session or previously had a remote ssh session. the present situation is *broken*, doesn't allow common usage. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Cristian Rodríguez
-
Karl Sinn
-
Patrick Shanahan
-
Simon Lees