Bug#639459: Same bug, years later.

[Christoph Anton Mitterer]

On Thu, 2015-04-30 at 18:37 -0400, J Phelps wrote: 
> So now you guys have forced "systemd" on all of us, and it doesn't even work.
No one has forced anything on you. sysvinit is still available and
maintained in Debian, you can simply use that if you like it more.


> ** (systemadm:21458): CRITICAL **:
> file /build/systemd-ui-GHIA4p/systemd-ui-3/src/systemadm.vala: line
> 339: uncaught error: Error calling StartServiceByName for
> org.freedesktop.systemd1:
> GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Launch
> helper exited with unknown return code 1 (g-dbus-error-quark, 25)
I assume you try to start systemadm...

Anyway,.. it works just fine here.


> Line 339 of systemadm.vala is a call to something called "Bus.get_proxy_sync":
> 
>                 manager = Bus.get_proxy_sync(
>                                 user ? BusType.SESSION : BusType.SYSTEM,
>                                 "org.freedesktop.systemd1",
>                                 "/org/freedesktop/systemd1");
> 
> 
> This is literally all the documentation I could find on "get_proxy_sync":
> 
>    http://valadoc.org/#!api=gio-2.0/GLib.Bus.get_proxy_sync
> 
> I'll save you the trouble of opening that link: It contains nothing but
> the method prototype.
Which is not a Debian project... so it's probably wasted time to
complain here about missing documentation... rather go upstream if you
want things to be improed.


> Perhaps I should
> just reboot and reinstall like they do on Windows.
Sounds like a plan... o.O


> So now I'm sitting on a system on which I presumably can't change anything
> unless I either get this non-working program that uses an undocumented API
> to do something, or figure out the complex forest of "unit files" that have
> been created behind the scenes.
Why shouldn't you be able to "change anything" just because systemadm
doesn't work for you?
It doesn't do much more than displaying information,.. and
starting/stopping/etc. services can be done at the command line as well.


> A little background: Systemd is of course running, but so is init.
systemd *is* an init implementation.

I'd guess either it's not really running, or it's not running as PID=1.


> However,
> it looks like systemd has already taken over everything, since systemd-logind
> is running. 
No, the systemd service which "takes everything over" is called
systemd-skynet...


> I am not using GNOME 3, nor will I do so, though I have considered the
> possibility that systemadm might require a GNOME 3 session or maybe even
> Wayland, which would be consistent with the way the New Linux crowd does
> things. Forcing me to downgrade to GNOME 3 from MATE would be a last straw
> for me. 
I don't use GNOME3 either since I don't like it nor it's design
philosophies... and yet,... systemadm works just fine here.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5313 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20150501/1c129996/attachment.bin>