package hotkey-setup 0.1-17ubuntu19 failed to install/upgrade: subprocess post-installation script returned error exit status 1

Bug #140967 reported by Florin
280
This bug affects 1 person
Affects Status Importance Assigned to Milestone
hotkey-setup (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: hotkey-setup

This happened in the daily (9/19) gutsy update/upgrade:

Setting up hotkey-setup (0.1-17ubuntu19) ...
Installing new version of config file /etc/init.d/hotkey-setup ...
KDSETKEYCODE: Invalid argument
failed to set scancode 8a to keycode 205
KDSETKEYCODE: Invalid argument
failed to set scancode 87 to keycode 236
KDSETKEYCODE: Invalid argument
failed to set scancode 8b to keycode 227
KDSETKEYCODE: Invalid argument
failed to set scancode 89 to keycode 161
KDSETKEYCODE: Invalid argument
failed to set scancode 85 to keycode 224
KDSETKEYCODE: Invalid argument
failed to set scancode 86 to keycode 225
KDSETKEYCODE: Invalid argument
failed to set scancode 92 to keycode 226
KDSETKEYCODE: Invalid argument
failed to set scancode 81 to keycode 164
KDSETKEYCODE: Invalid argument
failed to set scancode 82 to keycode 128
KDSETKEYCODE: Invalid argument
failed to set scancode 83 to keycode 165
KDSETKEYCODE: Invalid argument
failed to set scancode 84 to keycode 163
KDSETKEYCODE: Invalid argument
failed to set scancode a2 to keycode 164
KDSETKEYCODE: Invalid argument
failed to set scancode 90 to keycode 165
KDSETKEYCODE: Invalid argument
failed to set scancode 99 to keycode 163
KDSETKEYCODE: Invalid argument
failed to set scancode a4 to keycode 166
KDSETKEYCODE: Invalid argument
failed to set scancode ed to keycode 226
invoke-rc.d: initscript hotkey-setup, action "start" failed.
dpkg: error processing hotkey-setup (--configure):
 subprocess post-installation script returned error exit status 1

ProblemType: Package
Architecture: i386
Date: Wed Sep 19 08:50:41 2007
Dependencies:
 libgcc1 1:4.2.1-5ubuntu3
 dmidecode 2.9-1ubuntu1
 sysv-rc 2.86.ds1-14.1ubuntu27
 gcc-4.2-base 4.2.1-5ubuntu3
 libc6 2.6.1-1ubuntu5
DistroRelease: Ubuntu 7.10
ErrorMessage: subprocess post-installation script returned error exit status 1
NonfreeKernelModules: nvidia
Package: hotkey-setup 0.1-17ubuntu19
PackageArchitecture: i386
SourcePackage: hotkey-setup
Title: package hotkey-setup 0.1-17ubuntu19 failed to install/upgrade: subprocess post-installation script returned error exit status 1
Uname: Linux galactica 2.6.22-11-386 #1 Mon Sep 17 03:17:38 GMT 2007 i686 GNU/Linux

Revision history for this message
Florin (tlenze) wrote :
Revision history for this message
rojanu (rojanu) wrote :

i have got the same error
[CODE]
Setting up hotkey-setup (0.1-17ubuntu19) ...
KDSETKEYCODE: Invalid argument
failed to set scancode 8a to keycode 205
KDSETKEYCODE: Invalid argument
failed to set scancode 87 to keycode 236
KDSETKEYCODE: Invalid argument
failed to set scancode 8b to keycode 227
KDSETKEYCODE: Invalid argument
failed to set scancode 89 to keycode 161
KDSETKEYCODE: Invalid argument
failed to set scancode 85 to keycode 224
KDSETKEYCODE: Invalid argument
failed to set scancode 86 to keycode 225
KDSETKEYCODE: Invalid argument
failed to set scancode 92 to keycode 226
KDSETKEYCODE: Invalid argument
failed to set scancode 81 to keycode 164
KDSETKEYCODE: Invalid argument
failed to set scancode 82 to keycode 128
KDSETKEYCODE: Invalid argument
failed to set scancode 83 to keycode 165
KDSETKEYCODE: Invalid argument
failed to set scancode 84 to keycode 163
KDSETKEYCODE: Invalid argument
failed to set scancode a2 to keycode 164
KDSETKEYCODE: Invalid argument
failed to set scancode 90 to keycode 165
KDSETKEYCODE: Invalid argument
failed to set scancode 99 to keycode 163
KDSETKEYCODE: Invalid argument
failed to set scancode a4 to keycode 166
KDSETKEYCODE: Invalid argument
failed to set scancode ed to keycode 226
invoke-rc.d: initscript hotkey-setup, action "start" failed.
dpkg: error processing hotkey-setup (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 hotkey-setup
E: Sub-process /usr/bin/dpkg returned an error code (1)
[/CODE]

Revision history for this message
figjam (figjam) wrote :

It seems to whinge about KDE settings. I had KDE installed, but removed it.

The system is a Dell Vostro 200.

This was part of the Gutsy daily updates, first noticed 19 September
Linux 2.6.22-11-generic #1 SMP Mon Sep 17 03:45:58 GMT 2007 i686 GNU/Linux

Setting up hotkey-setup (0.1-17ubuntu19) ...
KDSETKEYCODE: Invalid argument
failed to set scancode 8a to keycode 205
KDSETKEYCODE: Invalid argument
failed to set scancode 87 to keycode 236
KDSETKEYCODE: Invalid argument
failed to set scancode 8b to keycode 227
KDSETKEYCODE: Invalid argument
failed to set scancode 89 to keycode 161
KDSETKEYCODE: Invalid argument
failed to set scancode 85 to keycode 224
KDSETKEYCODE: Invalid argument
failed to set scancode 86 to keycode 225
KDSETKEYCODE: Invalid argument
failed to set scancode 92 to keycode 226
KDSETKEYCODE: Invalid argument
failed to set scancode 81 to keycode 164
KDSETKEYCODE: Invalid argument
failed to set scancode 82 to keycode 128
KDSETKEYCODE: Invalid argument
failed to set scancode 83 to keycode 165
KDSETKEYCODE: Invalid argument
failed to set scancode 84 to keycode 163
KDSETKEYCODE: Invalid argument
failed to set scancode a2 to keycode 164
KDSETKEYCODE: Invalid argument
failed to set scancode 90 to keycode 165
KDSETKEYCODE: Invalid argument
failed to set scancode 99 to keycode 163
KDSETKEYCODE: Invalid argument
failed to set scancode a4 to keycode 166
KDSETKEYCODE: Invalid argument
failed to set scancode ed to keycode 226
invoke-rc.d: initscript hotkey-setup, action "start" failed.
dpkg: error processing hotkey-setup (--configure):
 subprocess post-installation script returned error exit status 1

 hotkey-setup
ERROR:root:SystemError from cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1)

Revision history for this message
David Vonka (vonkad) wrote :

Confirming the same error. Upgrated gutsy at 12 pm, September 20.

Chad Waters (chad)
Changed in hotkey-setup:
status: New → Confirmed
Revision history for this message
Andreas Schultz (aschultz) wrote :

Same problem here.

Whats even more worse, the init script's attempt to install a Dell Laptop keymapping on Dell Optiplex (no a Laptop) with an attached Microsoft keyboard is ill advised.

Revision history for this message
EqUaTe (chris-equate) wrote :

This does appear to be specific to desktop machines - I have this same version on my dell laptop without issue at all, but a colleague here had it on his desktop and we had to adjust the init script so that it could pass the installation..

As an interim fix - either replace the init script with something that just runs /bin/true, or find the manufacturer it's trying to use and comment the line that calls the .hk file in /etc/init.d/hotkeys-setup out.

Don't know the cause of this, unfortunately.

Revision history for this message
Jordon "Amvidian" Bedwell, Sr. (jordon-amvidian) wrote :

I had the same problem here on a Dimension C521 with a Microsoft Wireless Keyboard.

Revision history for this message
Jonathan Jesse (jjesse) wrote :

Confirming this w/ my Dell Keyboard as well. Have problems isntalling other software once this happens. Kubuntu-desktop has problems because I think it depends on this.

Fresh install of Tribe-5 cd and then updated via Adept today

Revision history for this message
figjam (figjam) wrote :

I too have the cheapo Dell keyboard with no extra buttons.

I had to resort to totally just removing this from my system with Synaptic.

My system do not need the hotkeys (not that I am sure what they were supposed to do, but superfluous on the cheapo version.

So far, no issues with updates. (Until later I suppose..)

Revision history for this message
rvconde (tb-th) wrote :

Had problems upgrading kde-desktop, so did a complete reinstall from Kubuntu Gutsy Tribe5 - and now I'm here. It's a Microsoft keyboard on a desktop - no laptop in sight. Removing hotkey-setup now...

Revision history for this message
Paul Perkins (thirdspace) wrote :

Similar error here. Dell Inspiron 530 Desktop computer.
I've noticed "KDSETKEYCODE: Invalid argument" errors on bootup for a long time (possibly since I started with Tribe 4).
But since about Sept 19 or 20, Update Manager always reports error due to hotkey-setup errors.

dpkg: error processing hotkey-setup (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of ubuntu-desktop:
 ubuntu-desktop depends on hotkey-setup; however:
  Package hotkey-setup is not configured yet.
dpkg: error processing ubuntu-desktop (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 hotkey-setup
 ubuntu-desktop

Revision history for this message
Giedrius (giedrbac) wrote :

This problem prevented me from upgrading the system and left apt-get in corrupted state. Downgrading to 0.1-17ubuntu9 moved apt-get to normal state, but errors where still printed to the screen during the installation process.

Revision history for this message
figjam (figjam) wrote :

Funny you should mention that the system was left in a corrupted state.

I had the same too and I had to really fiddle about to get things sorted though, did not click that the 2 were related.

Since uninstalling the package (hotkeys) i did not get the error anymore :-|

Revision history for this message
centx (centx) wrote :

Think I have the same bug, not using a Dell keyboard, but a Logitech one.

[CODE]
[SNIPPED]
.....
ldconfig deferred processing now taking place
Setting up hotkey-setup (0.1-17ubuntu19) ...
KDSETKEYCODE: Invalid argument
failed to set scancode 6f to keycode 113
KDSETKEYCODE: Invalid argument
failed to set scancode 6d to keycode 115
KDSETKEYCODE: Invalid argument
failed to set scancode 6e to keycode 114
invoke-rc.d: initscript hotkey-setup, action "start" failed.
dpkg: error processing hotkey-setup (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of ubuntu-desktop:
 ubuntu-desktop depends on hotkey-setup; however:
  Package hotkey-setup is not configured yet.
dpkg: error processing ubuntu-desktop (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 hotkey-setup
 ubuntu-desktop
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up hotkey-setup (0.1-17ubuntu19) ...
KDSETKEYCODE: Invalid argument
failed to set scancode 6f to keycode 113
KDSETKEYCODE: Invalid argument
failed to set scancode 6d to keycode 115
KDSETKEYCODE: Invalid argument
failed to set scancode 6e to keycode 114
invoke-rc.d: initscript hotkey-setup, action "start" failed.
dpkg: error processing hotkey-setup (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of ubuntu-desktop:
 ubuntu-desktop depends on hotkey-setup; however:
  Package hotkey-setup is not configured yet.
dpkg: error processing ubuntu-desktop (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 hotkey-setup
 ubuntu-desktop
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Writing extended state information... Done
Building tag database... Done
[/CODE]

Revision history for this message
Jordon "Amvidian" Bedwell, Sr. (jordon-amvidian) wrote :

Cheap temporary fix.

gksudo gedit /etc/init.d/hotkey-setup

Edit (Substitute it for your manufacturers name):

Dell*)
. /usr/share/hotkey-setup/dell.hk
;;

to:

Dell*)
;;

then do:

sudo apt-get -f install

Revision history for this message
Gavin Graham (gavingraham) wrote :

I can confirm that it is happening for me on two Dell PC's with Gusty Tribe-5 + current updates. I too can confirm that it seems to be only happening on desktop machines. For example, I can run 'setkeycodes e000 12' successfully on my laptop but the same command fails on my desktop no matter what keycodes I try.

Revision history for this message
EqUaTe (chris-equate) wrote :

As a reference - it's completely irrelevant what make your keyboard is.

This is triggering based on the manufacturer of the PC, nothing more.

In my opinion, this is faulty logic.

Revision history for this message
art alexion (art-alexion) wrote :

Same problem, Dell computer, MS ergo keyboard.

Revision history for this message
Jonathan Jesse (jjesse) wrote :

My Dell Latitude D820 laptop, but on my Dell Optiplex I'm seeing this problem

Revision history for this message
Nizar Kerkeni (nizarus) wrote :

Same bug with my DELL dimension e521 with dell multimedia keyboard but no problems in my vaio laptop.
[CODE]
$ sudo apt-get install hotkey-setup
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
hotkey-setup est déjà la plus récente version disponible.
0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
2 partiellement installés ou enlevés.
Il est nécessaire de prendre 0o dans les archives.
Après dépaquetage, 0o d'espace disque supplémentaires seront utilisés.
Paramétrage de hotkey-setup (0.1-17ubuntu19) ...
KDSETKEYCODE: Argument invalide
failed to set scancode 8a to keycode 205
KDSETKEYCODE: Argument invalide
failed to set scancode 87 to keycode 236
KDSETKEYCODE: Argument invalide
failed to set scancode 8b to keycode 227
KDSETKEYCODE: Argument invalide
failed to set scancode 89 to keycode 161
KDSETKEYCODE: Argument invalide
failed to set scancode 85 to keycode 224
KDSETKEYCODE: Argument invalide
failed to set scancode 86 to keycode 225
KDSETKEYCODE: Argument invalide
failed to set scancode 92 to keycode 226
KDSETKEYCODE: Argument invalide
failed to set scancode 81 to keycode 164
KDSETKEYCODE: Argument invalide
failed to set scancode 82 to keycode 128
KDSETKEYCODE: Argument invalide
failed to set scancode 83 to keycode 165
KDSETKEYCODE: Argument invalide
failed to set scancode 84 to keycode 163
KDSETKEYCODE: Argument invalide
failed to set scancode a2 to keycode 164
KDSETKEYCODE: Argument invalide
failed to set scancode 90 to keycode 165
KDSETKEYCODE: Argument invalide
failed to set scancode 99 to keycode 163
KDSETKEYCODE: Argument invalide
failed to set scancode a4 to keycode 166
KDSETKEYCODE: Argument invalide
failed to set scancode ed to keycode 226
invoke-rc.d: initscript hotkey-setup, action "start" failed.
dpkg : erreur de traitement de hotkey-setup (--configure) :
 le sous-processus post-installation script a retourné une erreur de sortie d'état 1
dpkg : des problèmes de dépendances empêchent la configuration de ubuntu-desktop :
 ubuntu-desktop dépend de hotkey-setup ; cependant :
 Le paquet hotkey-setup n'est pas encore configuré.
dpkg : erreur de traitement de ubuntu-desktop (--configure) :
 problèmes de dépendances - laissé non configuré
Des erreurs ont été rencontrées pendant l'exécution :
 hotkey-setup
 ubuntu-desktop
E: Sub-process /usr/bin/dpkg returned an error code (1)
[\CODE]

Revision history for this message
Simone Tolotti (simontol) wrote :

Same here with DELL Dimension E520
Kbd model: SK-8115 (Dell)

Revision history for this message
wateenellende (fpbeekhof) wrote :

I've got a Dell computer with a Sun keyboard attached to it. Same problem.
There are hotkeys on it, and if possible they should just work.
Maybe support for for a Sun keyboard is too much to ask, but the same argument goes for logitech / MS.
This should be parsed as a "Sun" (the keyboard manufacturer), not a "Dell" (the computer manufacturer).
Using the computer manufacturer to identify the keyboard manufacturer is plain wrong,
although on a laptop you can assume they are the same.

Revision history for this message
Saivann Carignan (oxmosys) wrote :

Same With Dell Vostro 200 with a very simple keyboard.

Revision history for this message
jsnyder (jbsnyder) wrote :

Dell E521, MS Natural Keyboard...

Revision history for this message
Gsibbery (lejeunerandy) wrote :

Dell Dimension 2400. Simple keyboard.

Revision history for this message
Gsibbery (lejeunerandy) wrote :

Workaround from: https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/88105/comments/7 :

"Do a sudo chmod 444 /etc/init.d/hotkey-setup and then reboot. This stops the daemon from starting in the first place, and while the script isn't executable, it will allow you to upgrade the package. Change the permissions on the file back to normal and then reboot again."

I tried the above, but did not have to reboot, just chmod the file then go on with the updates.

Revision history for this message
Saivann Carignan (oxmosys) wrote : Re: [Bug 140967] Re: package hotkey-setup 0.1-17ubuntu19 failed to install/upgrade: subprocess post-installation script returned error exit status 1

the Gsibbery workaround did work for me, hotkey-setup has been
reinstalled without problems.

Revision history for this message
Rich (Brown) at FullLoon.com (rich-fullloon) wrote :

(Jordon "Amvidian" Bedwell, Sr. posted a "Cheap temporary fix" on 2007-09-23)

This fix works on my Dell Dimension E520. (that's one of the Dell/Ubuntu models; shouldn't have problems like this...)

Revision history for this message
Saivann Carignan (oxmosys) wrote :

Since this bug is not present in the Linux Ubuntu Gutsy final release, I set it to fix released. Feel free to re-open the bug if you still experience problems with the final release.

Thanks to everybody that contributed to this bug report.

Changed in hotkey-setup:
status: Confirmed → Fix Released
Revision history for this message
ghowell (howlie02-deactivatedaccount) wrote :

I got the problem after upgrading today (along with a dozen or so others, which I guess I'll report seprately). I'm on an LG W40 Express laptop, 1.6Ghz w/ 512Mb RAM. Gutsy installed easily, but upgrade to Heron is not working well...

Revision history for this message
darthanubis (darthanubis) wrote :

Linux core2duo 2.6.28-11-generic #40-Ubuntu SMP Fri Apr 3 17:39:41 UTC 2009 x86_64 GNU/Linux

Just got this bug after updating 9.04. I do not have a laptop.

Revision history for this message
darthanubis (darthanubis) wrote :

The following packages will be REMOVED:
  hotkey-setup*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 98.3kB disk space will be freed.
Do you want to continue [Y/n]?
(Reading database ... 332292 files and directories currently installed.)
Removing hotkey-setup ...
/etc/init.d/hotkey-setup: 47: Syntax error: ";;" unexpected (expecting "fi")
invoke-rc.d: initscript hotkey-setup, action "stop" failed.
dpkg: error processing hotkey-setup (--purge):
 subprocess pre-removal script returned error exit status 2
 Removing any system startup links for /etc/init.d/hotkey-setup ...
   /etc/rc1.d/K20hotkey-setup
   /etc/rc2.d/S20hotkey-setup
   /etc/rc3.d/S20hotkey-setup
   /etc/rc4.d/S20hotkey-setup
   /etc/rc5.d/S20hotkey-setup
/etc/init.d/hotkey-setup: 47: Syntax error: ";;" unexpected (expecting "fi")
invoke-rc.d: initscript hotkey-setup, action "start" failed.
dpkg: error while cleaning up:
 subprocess post-installation script returned error exit status 2
Errors were encountered while processing:
 hotkey-setup
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@core2duo:/home/anubis#

Revision history for this message
Jonathan Aquilina (eagles051387) wrote :

after updating today on jaunty i got the same error as above. i have reopened this as confirmed.

Changed in hotkey-setup (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
Robert Osfield (robertosfield) wrote :

After updating Kubuntu 9.04 beta today I got this same error.

Revision history for this message
Jonathan Davies (jpds) wrote :

This bug is old. Please take any problems you have with this error to bug #356157 against the new package. If you find another error in the package, please file a new bug.

Changed in hotkey-setup (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
ghowell (howlie02-deactivatedaccount) wrote : Re: [Bug 140967] Re: package hotkey-setup 0.1-17ubuntu19 failed to install/upgrade: subprocess post-installation script returned error exit status 1
Download full text (3.3 KiB)

Hi darthanubis
err.... I don't know who you are, but suddenly I've received email from you (and a couple of others on the same topic, looks like replies to a distribution list). Have I inadvertently signed up for on a bugtracker email list or something?
If so I don't want to be on it - can you please tell me what the website is so I can un-join?
thanks

----- Original Message ----
From: darthanubis <email address hidden>
To: <email address hidden>
Sent: Monday, 6 April, 2009 8:14:36 PM
Subject: [Bug 140967] Re: package hotkey-setup 0.1-17ubuntu19 failed to install/upgrade: subprocess post-installation script returned error exit status 1

Linux core2duo 2.6.28-11-generic #40-Ubuntu SMP Fri Apr 3 17:39:41 UTC
2009 x86_64 GNU/Linux

Just got this bug after updating 9.04. I do not have a laptop.

--
package hotkey-setup 0.1-17ubuntu19 failed to install/upgrade: subprocess post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/140967
You received this bug notification because you are a direct subscriber
of the bug.

Status in “hotkey-setup” source package in Ubuntu: Fix Released

Bug description:
Binary package hint: hotkey-setup

This happened in the daily (9/19) gutsy update/upgrade:

Setting up hotkey-setup (0.1-17ubuntu19) ...
Installing new version of config file /etc/init.d/hotkey-setup ...
KDSETKEYCODE: Invalid argument
failed to set scancode 8a to keycode 205
KDSETKEYCODE: Invalid argument
failed to set scancode 87 to keycode 236
KDSETKEYCODE: Invalid argument
failed to set scancode 8b to keycode 227
KDSETKEYCODE: Invalid argument
failed to set scancode 89 to keycode 161
KDSETKEYCODE: Invalid argument
failed to set scancode 85 to keycode 224
KDSETKEYCODE: Invalid argument
failed to set scancode 86 to keycode 225
KDSETKEYCODE: Invalid argument
failed to set scancode 92 to keycode 226
KDSETKEYCODE: Invalid argument
failed to set scancode 81 to keycode 164
KDSETKEYCODE: Invalid argument
failed to set scancode 82 to keycode 128
KDSETKEYCODE: Invalid argument
failed to set scancode 83 to keycode 165
KDSETKEYCODE: Invalid argument
failed to set scancode 84 to keycode 163
KDSETKEYCODE: Invalid argument
failed to set scancode a2 to keycode 164
KDSETKEYCODE: Invalid argument
failed to set scancode 90 to keycode 165
KDSETKEYCODE: Invalid argument
failed to set scancode 99 to keycode 163
KDSETKEYCODE: Invalid argument
failed to set scancode a4 to keycode 166
KDSETKEYCODE: Invalid argument
failed to set scancode ed to keycode 226
invoke-rc.d: initscript hotkey-setup, action "start" failed.
dpkg: error processing hotkey-setup (--configure):
subprocess post-installation script returned error exit status 1

ProblemType: Package
Architecture: i386
Date: Wed Sep 19 08:50:41 2007
Dependencies:
libgcc1 1:4.2.1-5ubuntu3
dmidecode 2.9-1ubuntu1
sysv-rc 2.86.ds1-14.1ubuntu27
gcc-4.2-base 4.2.1-5ubuntu3
libc6 2.6.1-1ubuntu5
DistroRelease: Ubuntu 7.10
ErrorMessage: subprocess post-installation script returned error exit status 1
NonfreeKernelModules: nvidia
Package: hotkey-setup 0.1-17ubuntu19
PackageArchitecture: i386
SourcePackage: hotkey-setup
Title: package hotkey-setup 0.1-17ubuntu19 failed to install/upgrade: subprocess post...

Read more...

Revision history for this message
ghowell (howlie02-deactivatedaccount) wrote :
Download full text (3.6 KiB)

Found the site, don't recall ever having joined this. I'll delete my account asap.
Cheers

----- Original Message ----
From: Geoff Howell <email address hidden>
To: Bug 140967 <email address hidden>
Sent: Tuesday, 7 April, 2009 8:59:46 AM
Subject: Re: [Bug 140967] Re: package hotkey-setup 0.1-17ubuntu19 failed to install/upgrade: subprocess post-installation script returned error exit status 1

Hi darthanubis
err.... I don't know who you are, but suddenly I've received email from you (and a couple of others on the same topic, looks like replies to a distribution list). Have I inadvertently signed up for on a bugtracker email list or something?
If so I don't want to be on it - can you please tell me what the website is so I can un-join?
thanks

----- Original Message ----
From: darthanubis <email address hidden>
To: <email address hidden>
Sent: Monday, 6 April, 2009 8:14:36 PM
Subject: [Bug 140967] Re: package hotkey-setup 0.1-17ubuntu19 failed to install/upgrade: subprocess post-installation script returned error exit status 1

Linux core2duo 2.6.28-11-generic #40-Ubuntu SMP Fri Apr 3 17:39:41 UTC
2009 x86_64 GNU/Linux

Just got this bug after updating 9.04. I do not have a laptop.

--
package hotkey-setup 0.1-17ubuntu19 failed to install/upgrade: subprocess post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/140967
You received this bug notification because you are a direct subscriber
of the bug.

Status in “hotkey-setup” source package in Ubuntu: Fix Released

Bug description:
Binary package hint: hotkey-setup

This happened in the daily (9/19) gutsy update/upgrade:

Setting up hotkey-setup (0.1-17ubuntu19) ...
Installing new version of config file /etc/init.d/hotkey-setup ...
KDSETKEYCODE: Invalid argument
failed to set scancode 8a to keycode 205
KDSETKEYCODE: Invalid argument
failed to set scancode 87 to keycode 236
KDSETKEYCODE: Invalid argument
failed to set scancode 8b to keycode 227
KDSETKEYCODE: Invalid argument
failed to set scancode 89 to keycode 161
KDSETKEYCODE: Invalid argument
failed to set scancode 85 to keycode 224
KDSETKEYCODE: Invalid argument
failed to set scancode 86 to keycode 225
KDSETKEYCODE: Invalid argument
failed to set scancode 92 to keycode 226
KDSETKEYCODE: Invalid argument
failed to set scancode 81 to keycode 164
KDSETKEYCODE: Invalid argument
failed to set scancode 82 to keycode 128
KDSETKEYCODE: Invalid argument
failed to set scancode 83 to keycode 165
KDSETKEYCODE: Invalid argument
failed to set scancode 84 to keycode 163
KDSETKEYCODE: Invalid argument
failed to set scancode a2 to keycode 164
KDSETKEYCODE: Invalid argument
failed to set scancode 90 to keycode 165
KDSETKEYCODE: Invalid argument
failed to set scancode 99 to keycode 163
KDSETKEYCODE: Invalid argument
failed to set scancode a4 to keycode 166
KDSETKEYCODE: Invalid argument
failed to set scancode ed to keycode 226
invoke-rc.d: initscript hotkey-setup, action "start" failed.
dpkg: error processing hotkey-setup (--configure):
subprocess post-installation script returned error exit status 1

ProblemType: Package
Architecture: i386
Date: Wed Sep 19 08:50:41 2007
Dependencies:
libgcc1 1:4.2.1-5ubuntu3
dmidecode ...

Read more...

Revision history for this message
pr0ch0r (prochor666) wrote : Re: [Bug 140967] Re: package hotkey-setup 0.1-17ubuntu19 failed to install/upgrade: subprocess post-installation script returned error exit status 1
Download full text (6.3 KiB)

https://bugs.launchpad.net

try to unsubscribe here.

2009/4/7 ghowell <email address hidden>

>
> Hi darthanubis
> err.... I don't know who you are, but suddenly I've received email from you
> (and a couple of others on the same topic, looks like replies to a
> distribution list). Have I inadvertently signed up for on a bugtracker email
> list or something?
> If so I don't want to be on it - can you please tell me what the website is
> so I can un-join?
> thanks
>
>
>
> ----- Original Message ----
> From: darthanubis <email address hidden>
> To: <email address hidden>
> Sent: Monday, 6 April, 2009 8:14:36 PM
> Subject: [Bug 140967] Re: package hotkey-setup 0.1-17ubuntu19 failed to
> install/upgrade: subprocess post-installation script returned error exit
> status 1
>
> Linux core2duo 2.6.28-11-generic #40-Ubuntu SMP Fri Apr 3 17:39:41 UTC
> 2009 x86_64 GNU/Linux
>
> Just got this bug after updating 9.04. I do not have a laptop.
>
> --
> package hotkey-setup 0.1-17ubuntu19 failed to install/upgrade: subprocess
> post-installation script returned error exit status 1
> https://bugs.launchpad.net/bugs/140967
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “hotkey-setup” source package in Ubuntu: Fix Released
>
> Bug description:
> Binary package hint: hotkey-setup
>
> This happened in the daily (9/19) gutsy update/upgrade:
>
> Setting up hotkey-setup (0.1-17ubuntu19) ...
> Installing new version of config file /etc/init.d/hotkey-setup ...
> KDSETKEYCODE: Invalid argument
> failed to set scancode 8a to keycode 205
> KDSETKEYCODE: Invalid argument
> failed to set scancode 87 to keycode 236
> KDSETKEYCODE: Invalid argument
> failed to set scancode 8b to keycode 227
> KDSETKEYCODE: Invalid argument
> failed to set scancode 89 to keycode 161
> KDSETKEYCODE: Invalid argument
> failed to set scancode 85 to keycode 224
> KDSETKEYCODE: Invalid argument
> failed to set scancode 86 to keycode 225
> KDSETKEYCODE: Invalid argument
> failed to set scancode 92 to keycode 226
> KDSETKEYCODE: Invalid argument
> failed to set scancode 81 to keycode 164
> KDSETKEYCODE: Invalid argument
> failed to set scancode 82 to keycode 128
> KDSETKEYCODE: Invalid argument
> failed to set scancode 83 to keycode 165
> KDSETKEYCODE: Invalid argument
> failed to set scancode 84 to keycode 163
> KDSETKEYCODE: Invalid argument
> failed to set scancode a2 to keycode 164
> KDSETKEYCODE: Invalid argument
> failed to set scancode 90 to keycode 165
> KDSETKEYCODE: Invalid argument
> failed to set scancode 99 to keycode 163
> KDSETKEYCODE: Invalid argument
> failed to set scancode a4 to keycode 166
> KDSETKEYCODE: Invalid argument
> failed to set scancode ed to keycode 226
> invoke-rc.d: initscript hotkey-setup, action "start" failed.
> dpkg: error processing hotkey-setup (--configure):
> subprocess post-installation script returned error exit status 1
>
> ProblemType: Package
> Architecture: i386
> Date: Wed Sep 19 08:50:41 2007
> Dependencies:
> libgcc1 1:4.2.1-5ubuntu3
> dmidecode 2.9-1ubuntu1
> sysv-rc 2.86.ds1-14.1ubuntu27
> gcc-4.2-base 4.2.1-5ubuntu3
> libc6 2.6.1-1ubuntu5
> DistroRelease: Ubuntu 7.10
> ErrorMessage: subprocess post-...

Read more...

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.