Comment 1 for bug 917738

Mélodie (meets) wrote :

Hi,
I am running a spin of Ubuntu 12.04 which I have been building for several months now and which is pretty stable and works well according to feedback and to my own experience. It is fully up to date and I have been trying to get jobs-admin to work several times in Ubuntu Precise (in this version and also other ones such as Lubuntu and Xubuntu which I happen to boot once a while).

Here is another testimonial related to this issue:
http://beta.linuxvillage.net/index.php/topic,297.msg2196.html#msg2196

I can't get jobs-admin to change anything in the services started, be it as simple user or by starting it from console with gksu.

Here is what I get when starting it from a console:
**************
$ jobs-admin
No module named pkit
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 607, in msg_reply_handler
    *message.get_args_list()))
  File "/usr/lib/python2.7/dist-packages/JobsAdmin/__init__.py", line 232, in error
    raise e
dbus.exceptions.DBusException: org.freedesktop.PolicyKit1.Error.Failed: Error getting subject: Error parsing unix-process subject: Value for key `start-time' found but is of type i and type t was expected
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 607, in msg_reply_handler
    *message.get_args_list()))
  File "/usr/lib/python2.7/dist-packages/JobsAdmin/__init__.py", line 232, in error
    raise e
dbus.exceptions.DBusException: org.freedesktop.PolicyKit1.Error.Failed: Error getting subject: Error parsing unix-process subject: Value for key `start-time' found but is of type i and type t was expected

**************

I think something is wrong with jobs-admin... not sure exactly what?

Here are the services listed in /etc/init:

**************
melodie@vbox:/etc/init$ ls
acpid.conf network-interface-container.conf
alsa-restore.conf network-interface-security.conf
alsa-store.conf network-manager.conf
anacron.conf passwd.conf
apport.conf plymouth.conf
atd.conf plymouth-log.conf
binfmt-support.conf plymouth-splash.conf
console.conf plymouth-stop.conf
console-setup.conf plymouth-upstart-bridge.conf
container-detect.conf procps.conf
control-alt-delete.conf rc.conf
cron.conf rcS.conf
cryptdisks-enable.conf rc-sysinit.conf
cryptdisks-udev.conf resolvconf.conf
dbus.conf rfkill-restore.conf
dmesg.conf rfkill-store.conf
failsafe.conf rsyslog.conf
flush-early-job-log.conf setvtrgb.conf
friendly-recovery.conf shutdown.conf
hostname.conf tty1.conf
hwclock.conf tty2.conf
hwclock-save.conf tty3.conf
hybrid-gfx.conf tty4.conf
irqbalance.conf tty5.conf
module-init-tools.conf tty6.conf
mountall.conf udev.conf
mountall-net.conf udev-fallback-graphics.conf
mountall-reboot.conf udev-finish.conf
mountall-shell.conf udevmonitor.conf
mounted-debugfs.conf udevtrigger.conf
mounted-dev.conf ufw.conf
mounted-proc.conf upstart-socket-bridge.conf
mounted-run.conf upstart-udev-bridge.conf
mounted-tmp.conf ureadahead.conf
mounted-var.conf ureadahead-other.conf
networking.conf wait-for-state.conf
network-interface.conf zram-config.conf
melodie@vbox:/etc/init$
**************

and here the ones listed in /etc/init.d:

**************

melodie@vbox:/etc/init.d$ ls -l
total 172
lrwxrwxrwx 1 root root 21 mai 2 18:03 acpid -> /lib/init/upstart-job
-rwxr-xr-x 1 root root 652 janv. 5 2010 acpi-support
lrwxrwxrwx 1 root root 21 mai 2 18:03 alsa-restore -> /lib/init/upstart-job
lrwxrwxrwx 1 root root 21 mai 2 18:03 alsa-store -> /lib/init/upstart-job
lrwxrwxrwx 1 root root 21 mai 2 18:03 anacron -> /lib/init/upstart-job
-rwxr-xr-x 1 root root 1663 nov. 4 2009 apmd
-rwxr-xr-x 1 root root 4596 avril 12 2012 apparmor
lrwxrwxrwx 1 root root 21 avril 11 19:15 apport -> /lib/init/upstart-job
lrwxrwxrwx 1 root root 21 mai 2 18:03 atd -> /lib/init/upstart-job
lrwxrwxrwx 1 root root 21 nov. 25 2011 binfmt-support -> /lib/init/upstart-job
-rwxr-xr-x 1 root root 2444 avril 14 2012 bootlogd
lrwxrwxrwx 1 root root 21 mai 2 18:03 console-setup -> /lib/init/upstart-job
lrwxrwxrwx 1 root root 21 mai 2 18:03 cron -> /lib/init/upstart-job
-rwxr-xr-x 1 root root 922 mars 8 2012 cryptdisks
-rwxr-xr-x 1 root root 871 mars 8 2012 cryptdisks-early
lrwxrwxrwx 1 root root 21 mai 2 18:03 cryptdisks-enable -> /lib/init/upstart-job
lrwxrwxrwx 1 root root 21 mai 2 18:03 cryptdisks-udev -> /lib/init/upstart-job
lrwxrwxrwx 1 root root 21 mai 2 18:03 dbus -> /lib/init/upstart-job
lrwxrwxrwx 1 root root 21 mai 2 18:03 dmesg -> /lib/init/upstart-job
-rwxr-xr-x 1 root root 1242 déc. 13 2011 dns-clean
lrwxrwxrwx 1 root root 21 mai 2 18:03 friendly-recovery -> /lib/init/upstart-job
-rwxr-xr-x 1 root root 1105 avril 17 2012 grub-common
-rwxr-xr-x 1 root root 1329 avril 14 2012 halt
lrwxrwxrwx 1 root root 21 mai 2 18:03 hostname -> /lib/init/upstart-job
lrwxrwxrwx 1 root root 21 mai 2 18:03 hwclock -> /lib/init/upstart-job
lrwxrwxrwx 1 root root 21 mai 2 18:03 hwclock-save -> /lib/init/upstart-job
lrwxrwxrwx 1 root root 21 mai 2 18:03 irqbalance -> /lib/init/upstart-job
-rwxr-xr-x 1 root root 1293 avril 14 2012 killprocs
-rwxr-xr-x 1 root root 1986 déc. 21 2011 laptop-mode
-rwxr-xr-x 1 root root 869 févr. 6 2011 lm-sensors
lrwxrwxrwx 1 root root 21 mai 2 18:03 module-init-tools -> /lib/init/upstart-job
-rwxr-xr-x 1 root root 2535 août 7 2010 netplug
-rwxr-xr-x 1 root root 2797 févr. 13 2012 networking
lrwxrwxrwx 1 root root 21 mai 2 18:03 network-interface -> /lib/init/upstart-job
lrwxrwxrwx 1 root root 21 mai 2 18:03 network-interface-container -> /lib/init/upstart-job
lrwxrwxrwx 1 root root 21 mai 2 18:03 network-interface-security -> /lib/init/upstart-job
lrwxrwxrwx 1 root root 21 mai 2 18:03 network-manager -> /lib/init/upstart-job
-rwxr-xr-x 1 root root 1843 nov. 20 2011 nodm
-rwxr-xr-x 1 root root 1818 oct. 26 2011 ntp
-rwxr-xr-x 1 root root 882 avril 14 2012 ondemand
lrwxrwxrwx 1 root root 21 mai 2 18:03 passwd -> /lib/init/upstart-job
lrwxrwxrwx 1 root root 21 mai 2 18:03 plymouth -> /lib/init/upstart-job
lrwxrwxrwx 1 root root 21 mai 2 18:03 plymouth-log -> /lib/init/upstart-job
lrwxrwxrwx 1 root root 21 mai 2 18:03 plymouth-splash -> /lib/init/upstart-job
lrwxrwxrwx 1 root root 21 mai 2 18:03 plymouth-stop -> /lib/init/upstart-job
lrwxrwxrwx 1 root root 21 mai 2 18:03 plymouth-upstart-bridge -> /lib/init/upstart-job
-rwxr-xr-x 1 root root 561 févr. 4 2011 pppd-dns
lrwxrwxrwx 1 root root 21 mai 2 18:03 procps -> /lib/init/upstart-job
-rwxr-xr-x 1 root root 8635 juil. 26 2012 rc
-rwxr-xr-x 1 root root 801 avril 14 2012 rc.local
-rwxr-xr-x 1 root root 117 juil. 26 2012 rcS
-rw-r--r-- 1 root root 2427 juil. 26 2012 README
-rwxr-xr-x 1 root root 639 avril 14 2012 reboot
lrwxrwxrwx 1 root root 21 mai 2 18:03 resolvconf -> /lib/init/upstart-job
lrwxrwxrwx 1 root root 21 mai 2 18:03 rfkill-restore -> /lib/init/upstart-job
lrwxrwxrwx 1 root root 21 mai 2 18:03 rfkill-store -> /lib/init/upstart-job
-rwxr-xr-x 1 root root 4395 nov. 8 2011 rsync
lrwxrwxrwx 1 root root 21 mai 2 18:03 rsyslog -> /lib/init/upstart-job
-rwxr-xr-x 1 root root 4321 avril 14 2012 sendsigs
lrwxrwxrwx 1 root root 21 mai 2 18:03 setvtrgb -> /lib/init/upstart-job
-rwxr-xr-x 1 root root 590 avril 14 2012 single
-rw-r--r-- 1 root root 4304 juil. 26 2012 skeleton
-rwxr-xr-x 1 root root 567 avril 14 2012 stop-bootlogd
-rwxr-xr-x 1 root root 1143 avril 14 2012 stop-bootlogd-single
-rwxr-xr-x 1 root root 700 oct. 27 2011 sudo
lrwxrwxrwx 1 root root 21 mai 2 18:03 udev -> /lib/init/upstart-job
lrwxrwxrwx 1 root root 21 mai 2 18:03 udev-fallback-graphics -> /lib/init/upstart-job
lrwxrwxrwx 1 root root 21 mai 2 18:03 udev-finish -> /lib/init/upstart-job
lrwxrwxrwx 1 root root 21 mai 2 18:03 udevmonitor -> /lib/init/upstart-job
lrwxrwxrwx 1 root root 21 mai 2 18:03 udevtrigger -> /lib/init/upstart-job
lrwxrwxrwx 1 root root 21 mai 2 18:03 ufw -> /lib/init/upstart-job
-rwxr-xr-x 1 root root 2800 avril 14 2012 umountfs
-rwxr-xr-x 1 root root 2211 avril 14 2012 umountnfs.sh
-rwxr-xr-x 1 root root 2926 avril 14 2012 umountroot
-rwxr-xr-x 1 root root 1039 nov. 9 2011 unattended-upgrades
-rwxr-xr-x 1 root root 1985 avril 14 2012 urandom
-rwxr-xr-x 1 root root 1364 avril 5 2012 virtualbox-guest-utils
-rwxr-xr-x 1 root root 2666 mars 22 2012 x11-common
lrwxrwxrwx 1 root root 21 mai 2 18:03 zram-config -> /lib/init/upstart-job
melodie@vbox:/etc/init.d$

**************

For example, I use the zram-config service, which has been turned into an upstart-job as it shows in the last line just above : this service does not appear in jobs-admin, which would tend to make me think Olivier is right, the upstart-jobs don't show.

So else than giving up on managing services from the beginning, how can we do that ?

ie : I want to have cups, openssh-server, (starts sshd), update-notifier, but sometimes or for some of my machines I just want them installed and ready to start on the fly when I want them to work. Is it possible to setup which service will be used and which won't be ? Isn't jobs-admin supposed to make this task easy ?

Thanks for some lights on the problem,
Mélodie