On sön, 2015-03-08 at 23:14 +0100, Lennart Poettering wrote:
> On Sat, 07.03.15 08:45, Mantas Mikulėnas (graw...@gmail.com) wrote:
> The latter is "private", as the name suggests. Do not access it from
> external programs, it is systemd's internal hack around ordering
> issues with dbus, and nobod
Thanks for your replies. I managed to access the user bus by setting it up
according to the Arch guide.
Sincerely,
Ragnar
On Sun, Mar 8, 2015 at 11:14 PM, Lennart Poettering
wrote:
> On Sat, 07.03.15 08:45, Mantas Mikulėnas (graw...@gmail.com) wrote:
>
> > On Fri, Mar 6, 2015 at 6:23 PM, Ragn
On Sat, 07.03.15 08:45, Mantas Mikulėnas (graw...@gmail.com) wrote:
> On Fri, Mar 6, 2015 at 6:23 PM, Ragnar Thomsen wrote:
>
> > Hey List,
> >
> > Does the user instance of systemd expose a dbus api?
> >
>
> Yes, that's what `systemctl` uses.
>
>
> > If yes, how does one access it?
> >
>
>
Hi Ragnar,
I found out and published answer on your Github bug tracker
https://github.com/rthomsen/kcmsystemd/issues/17 .
It seems as simple a using Qt's buitlin "QDBusConnection::sessionBus()"
(qdbusviewer does that).
Alexandre
Le samedi 7 mars 2015, 08:45:42 Mantas Mikulėnas a écrit :
> On
On Fri, Mar 6, 2015 at 6:23 PM, Ragnar Thomsen wrote:
> Hey List,
>
> Does the user instance of systemd expose a dbus api?
>
Yes, that's what `systemctl` uses.
> If yes, how does one access it?
>
Much like the system instance – either over the DBus "user" bus, or over
the dedicated private so
