You can't, as we do use systemd-logind and other parts from the systemd
package.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1387241
Title:
systemctl is broken if you
Can systemd be safely uninstalled in the mean time for users not yet
testing this function?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1387241
Title:
systemctl is
For 15.04 we plan to change to systemd by default, at which point this
will work. For 14.10 making systemctl invisible is not an important
enough issue to warrant a stable release update; plus, some people
actually want to boot 14.10 with systemd for experimentation (note that
this is not
** Summary changed:
- systemctl is broken
+ systemctl is broken if you don't boot with systemd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1387241
Title:
systemctl is
It was suggested to me that I could use the following workaround to start up
programs affected by this bug by using the following command:
:~#sudo service [PackageName] start
I tested this on an affect program Haguichi and it worked.
--
You received this bug notification because you are a
Also effects Haguichi, and presumably any package that calls on /bin/systemctl.
see my Bug report here: https://answers.launchpad.net/haguichi/+question/258759
This happened only after upgrade to 14.10. Martin Pitt, care to write a
quick tutorial on how to change the correct boot settings to
Here are some conflicting results:
Output from:
:~$ initctl --systemlist
initctl: invalid option: --systemlist
Try `initctl --help' for more information.
brandon@RomeoMontague:~$ initctl --system list
avahi-daemon start/running, process 897
mountnfs-bootclean.sh start/running
rsyslog
Also, systemd is not maintained in launchpad, but in bugzilla. If this
is an error in systemd and it is required for 'some reason', then they
may have to be notified their as well? I dont know if upstart is the
real problem here, and the package being reported for this bug might
need to be
Affects multiple users.
** Changed in: systemd (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1387241
Title:
systemctl is
Also, there is no package libdbus or dbus-daemon. So even if systemd
was the intent, how would it ever communicate?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1387241
systemd is obviously installed, since the systemctl command is
available. They are in the same systemd package.
If you have any ideas of how to detect if systemd is actually used, that
would be great. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
If systemctl is working, you are running systemd. If initctl --system
list is working, you are running upstart (the default in Ubuntu 14.10).
As I said, you need to boot with init=/bin/systemd on the kernel
command line to try systemd.
--
You received this bug notification because you are a
Hello,
Have you installed systemd?
Thanks
** Changed in: systemd (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1387241
Title:
You actually need to boot with systemd for systemctl to work. But NB
that in Ubuntu 14.10 this isn't officially supported yet, and many stuff
is still broken. But you can append init=/bin/systemd to the command
line to play with it; a normal desktop works very well.
** Changed in: systemd
14 matches
Mail list logo
