Cannot disable cron from the Services preference pane

Bug #172841 reported by Gioele Barabucci
4
Affects Status Importance Assigned to Milestone
Baltix
Invalid
Undecided
Unassigned
gnome-system-tools (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

It is not possible to disable the cron service from the "Services" preference pane.

Changed in gnome-system-tools:
status: New → Invalid
Revision history for this message
Miguel Ruiz (mruiz) wrote :

Hi,

Thank you for taking the time to report this bug and helping to make Ubuntu better. I'm using Hardy Heron up to date and I cannot reproduce this problem (I can disable the cron service without problem). Would you test it again using the last version of Hardy?

Thanks again and we appreciate your help.

Changed in gnome-system-tools:
status: New → Incomplete
Revision history for this message
Gioele Barabucci (gioele) wrote :

The problem is still present in Hardy Alpha 5. I can disable anacron and atd only from the interface.

Changed in gnome-system-tools:
status: Incomplete → New
Revision history for this message
Gioele Barabucci (gioele) wrote :

This is still a problem in Intrepid.

Miguel, how can you disable the cron service? I don't see a cron service listed among the others. (screenshot attached)

Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in gnome-system-tools (Ubuntu):
status: New → Incomplete
Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote :

The situation is actually more complex than that. If you're still using Jaunty, this can be checked easily. But in Karmic, you should have noticed, services-admin is not present. Further, cron is now handled via an upstart job, which are not supported ATM by services-admin upstream. So we can't check if the bug is solved, and the situation is likely to change much in Lucid again.

I'd say that if you have already switched to Karmic, we should keep this bug as Confirmed until we can check it again.

Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :

On that basis alone, this should be left confirmed, but tagged as a possible future regression, especially as you say, if this is not solved by the time Lucid is released, unless Lucid uses the same upstart services as Karmic.

Changed in gnome-system-tools (Ubuntu):
status: Incomplete → Confirmed
importance: Undecided → Medium
tags: added: regression-potential
Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :

Can you tell us what version of gnome-system-tools you are using, and I'll have a look at forwarding it upstream. Thank you.

Changed in gnome-system-tools (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote :

There's no regression potential here. This bug was about Ubuntu 7.10, things can only improve in that regard. If you're thinking of the Upstart support problem, the bugs are #433701 and #435935, but that's another problem.

BTW, no need to report that upstream. I am actually most of the developers team, and I generally work directly in Launchpad for Ubuntu bugs, this is much simpler.

Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :

No worries, that saves messing about with reporting upstream then. I take it you are looking into this? :)

Changed in gnome-system-tools (Ubuntu):
status: Incomplete → Confirmed
tags: removed: regression-potential
Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote :

I already had a quick look: "WORKSFORME". It may well be solved for a long time, I just hope the reporter is still using Jaunty - else we'll have to wait for big changes to happen.

Revision history for this message
Gioele Barabucci (gioele) wrote :

Actually I ("the reporter") never used Jaunty. This problem was present in Hardy-1, Hardy and Intrepid.

Now I'm on Karmic and, as Milan Bouchet-Valat, there is now a completely different "bug": services-admin does not exist.

I think this bug can be closed now, at least with regard to the purpose I reported it.

Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :

Closed as per your comment. If this gets reported again, we can simply mark it as a duplicate if this one and reopen it.

Changed in gnome-system-tools (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.