Comment 6 for bug 73992

The problem appears to be that when the hotkey-setup package is being replaced, one of its scripts calls invoke-rc.d on /etc/init.d/hotkey-setup and that script returns an error which prevents the package from being removed. I saw this same behavior several times, first when I did an "apt-get dist-upgrade" and later when I did a "dpkg --purge --ignore-depends=ubuntu-desktop hotkey-setup".

Eventually I just added an "exit" to the beginning of /etc/init.d/hotkey-setup and then I was able to remove the package and then install the Edgy version.

Here's the error message I would get when I tried to remove hotkey-setup:

Preparing to replace hotkey-setup 0.1-17 (using .../hotkey-setup_0.1-17ubuntu3_i386.deb) ...
KDSETKEYCODE: No such device
failed to set scancode 0 to keycode 256
invoke-rc.d: initscript hotkey-setup, action "stop" failed.
dpkg: warning - old pre-removal script returned error exit status 1
dpkg - trying script from the new package instead ...
KDSETKEYCODE: No such device
failed to set scancode 0 to keycode 256
invoke-rc.d: initscript hotkey-setup, action "stop" failed.
dpkg: error processing /var/cache/apt/archives/hotkey-setup_0.1-17ubuntu3_i386.deb (--unpack):
 subprocess new pre-removal script returned error exit status 1
KDSETKEYCODE: No such device
failed to set scancode 8a to keycode 205
KDSETKEYCODE: No such device
failed to set scancode 87 to keycode 236
KDSETKEYCODE: No such device
failed to set scancode 8b to keycode 190
KDSETKEYCODE: No such device
failed to set scancode 89 to keycode 161
KDSETKEYCODE: No such device
failed to set scancode 85 to keycode 224
KDSETKEYCODE: No such device
failed to set scancode 86 to keycode 225
KDSETKEYCODE: No such device
failed to set scancode 92 to keycode 226
Errors were encountered while processing:
 /var/cache/apt/archives/hotkey-setup_0.1-17ubuntu3_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)