package sudo 1.7.2p1-1ubuntu5.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

Asked by historyb on 2010-08-15

Binary package hint: sudo

it just found it

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: sudo 1.7.2p1-1ubuntu5.1
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
Architecture: i386
Date: Sun Aug 15 13:11:29 2010
ErrorMessage: subprocess installed pre-removal script returned error exit status 1
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
SourcePackage: sudo
Title: package sudo 1.7.2p1-1ubuntu5.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
VisudoCheck: /etc/sudoers: parsed OK

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu sudo Edit question
Assignee:
No assignee Edit question
Last query:
2010-08-15
Last reply:
2011-11-01
Rolf Leggewie (r0lf) said : #1

Turning bug ticket into a question. Let us know if this fixes your problem.

Rolf Leggewie (r0lf) said : #2

This is a feature, not a bug. Sudo is a pretty essential package that cannot and should not be easy to remove. Quoting the last few lines from your log which already tell you what you need to do.

=== SNIP ===
You have asked that the sudo package be removed,

but no root password has been set.

Without sudo, you may not be able to gain administrative privileges.

If you would prefer to access the root account with su(1)

or by logging in directly,

you must set a root password with "sudo passwd".

If you have arranged other means to access the root account,

and you are sure this is what you want,

you may bypass this check by setting an environment variable

(export SUDO_FORCE_REMOVE=yes).

=== SNIP ===

matism (matism) said : #3

I have no problem with this response. Not sure of the original problem, but I think it was a patch installation for the ATI graphics driver problem that resulted in the sudo error. Got a workable response to fix the issue at that time, and have not had any further occurrences. Thank you!

historyb (historyb) said : #4

This was reported automatically a long while back. Something crashed and wanted to report it, it's so long ago I have no idea what it was :)

Can you help with this problem?

Provide an answer of your own, or ask historyb for more information if necessary.

To post a message you must log in.