** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu.
https://bugs.launchpad.net/bugs/435935
Title:
Support Upstart
To manage notifications about this bug go to:
Anyone working on restoring the services menu?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu.
https://bugs.launchpad.net/bugs/435935
Title:
Support Upstart
To manage notifications about this bug go
This bug's status isn't set to In progress nor assigned to someone, so
no one is working on this.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu.
https://bugs.launchpad.net/bugs/435935
Title:
Support
This is a colossal mess. The bottom line seems to be that one has to
recheck all service configs after an update, whether sysv or upstart.
One also has to know which services have been upstarted in order to
derive their expected behaviour.
Confidence in services' configs at reboot has just been
I would be gracefull if the ppa would be updated Lucid is on 2.30 at the
moment while the ppa is on 2.29.91.
--
Support Upstart
https://bugs.launchpad.net/bugs/435935
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in
this is annoying - the System - Administration - Services menu is
missing, and for example cups doesn't start automatically on the system,
how would I make it start automatically?
removing a feature, but not providing a replacement is not progress :(
(BTW, cups's troubleshooting guide
See http://www.unixtutorial.org/2009/01/disable-service-startup-in-
ubuntu/, or install bum.
--
Support Upstart
https://bugs.launchpad.net/bugs/435935
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu.
--
looks like Lucid shipped without services-admin :( see Bug #437905 for
tracking getting services-admin re-released.
--
Support Upstart
https://bugs.launchpad.net/bugs/435935
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Please stay specific to the very issue I'm trying to tackle for Lucid:
we won't get true Upstart support included before the final release. So
let's discuss and test my PPA package on the basis of SysV scripts
*only*.
From all of your description, I can't see any issue that wasn't expected
OK, here's a debdiff that re-enables services-admin in Lucid (pretty
basic).
Chris, do you think you could apply this one before everything gets
frozen?
** Attachment added: gnome-system-tools_2.29.91-0ubuntu3.debdiff
Oh, and BTW, people that want to test this package may install it from my PPA:
https://launchpad.net/~nalimilan/+archive/ppa/+packages?field.name_filter=gnome-system-toolsfield.status_filter=publishedfield.series_filter=lucid
--
Support Upstart
https://bugs.launchpad.net/bugs/435935
You received
Hello Milan and thank you for working on this as it is very much needed.
From what I understand (after reading this bug and testing the packages
in your PPA) is that your services-admin completely ignores upstart jobs
and allows a user to only enable/disable SysV scripts. Only my testing
shows
Ask Chris Coulson about that. Upstart support is not really plan for
now, because most useful services are actually still using SysV scripts.
So what I'd like to see in Lucid is services-admin managing those
scripts, and hide Upstart jobs, which are started when needed, and often
essential system
Milan, could you tell me what's the status on this? I still don't see
services-admin available in Lucid. It's rather important to have in a
LTS release :)
--
Support Upstart
https://bugs.launchpad.net/bugs/435935
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Basic support is now in Karmic with the system-tools-backends 2.8.2 (see
bug 443312). services-admin can be brought back if we want.
** Also affects: gnome-system-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-system-tools (Ubuntu)
Status: New = Confirmed
Ping to all: do you consider it's too late to do anything about that,
even cherry-picking the simple patch that adds compatibility with
Upstart? services-admin is something important for many users, see the
duplicates and http://ubuntuforums.org/showthread.php?t=1272747
--
Support Upstart
James: see bug 443312 about packaging 2.8.2. We're quite in a hurry, I
must admit...
--
Support Upstart
https://bugs.launchpad.net/bugs/435935
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to system-tools-backends in ubuntu.
--
OK, eventually released in 2.8.2 which should be uploaded soon. FWIW,
the code used service instead of initctl as the latter only deals with
upstart jobs.
** Changed in: system-tools-backends
Status: In Progress = Fix Released
** Changed in: system-tools-backends (Ubuntu)
Status:
I've just realized /sbin/service is shipped by sysv-utils, so I guess I
should use /sbin/initctl instead, which is shipped by upstart. Just a
command to rename, anyway.
I've also checked packages in Debian, and they have upstart 0.6.3 in squeeze
already, and the plan seems to be to switch to
Converted scripts include GDM, D-Bus, Apport, Anacron, acpid, UFW,
avahi-daemon, NetworkManager. The first two are not a problem since
there are problems with people stopping them by mistake and breaking
their graphical sessions. The others would be good to have, but... On my
system,
** Changed in: system-tools-backends (Ubuntu)
Status: Confirmed = In Progress
** Also affects: system-tools-backends
Importance: Undecided
Status: New
** Changed in: system-tools-backends
Status: New = In Progress
--
Support Upstart
From what /usr/share/doc/upstart/README.Debian.gz explains, we can
easily provide as many features as before by working with scripts from
/etc/init.d, isn't it? Upstart jobs in /etc/init are essential parts of
the system, and there's little interest in disabling them.
So I'd say that at least for
On Sun Sep 27 20:46:13 UTC 2009 Milan Bouchet-Valat wrote:
From what /usr/share/doc/upstart/README.Debian.gz explains, we can
easily provide as many features as before by working with scripts from
/etc/init.d, isn't it? Upstart jobs in /etc/init are essential parts of
the system, and there's
Scott, could you explain what we should change in order to fully support
Upstart? Do you think we could be Upstart-compatible with minimal
changes for Karmic (e.g. just changing a few locations/commands)? Are
there deeper changes that could be nice to do in the long term?
And, last but not least,
24 matches
Mail list logo
