Here is a workaround proposed by an ubuntu-fr member:
* Create /etc/init/cups.conf file and fill it with :
#cups
start on runlevel [2345]
stop on runlevel [!2345]
respawn
exec /usr/sbin/cupsd -C /etc/cups/cupsd.conf
* Then launch the service with : sudo initctl start cups
It worked for 1 user (the service automatically starts from now), but not for 2 other users (including me). For us 2, we have to type either "sudo initctl start cups" or "sudo /etc/init.d/cups start" to launch the service at the beginning of each session.
Also, we both observed that the command "runlevel" returns "unknown". Maybe the source of the problem is here ?
Minimum 2 other users have the same bug : http:// forum.ubuntu- fr.org/ viewtopic. php?pid= 3329206# p3329206
Here is a workaround proposed by an ubuntu-fr member: cupsd.conf
* Create /etc/init/cups.conf file and fill it with :
#cups
start on runlevel [2345]
stop on runlevel [!2345]
respawn
exec /usr/sbin/cupsd -C /etc/cups/
* Then launch the service with : sudo initctl start cups
It worked for 1 user (the service automatically starts from now), but not for 2 other users (including me). For us 2, we have to type either "sudo initctl start cups" or "sudo /etc/init.d/cups start" to launch the service at the beginning of each session.
Also, we both observed that the command "runlevel" returns "unknown". Maybe the source of the problem is here ?
Hope this helps to solve this bug.