Bug 19082 - numlock cannot be uninstalled (%preun failure)
Summary: numlock cannot be uninstalled (%preun failure)
Status: RESOLVED DUPLICATE of bug 18027
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: High normal
Target Milestone: Mageia 6
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-29 00:48 CEST by Roger N
Modified: 2018-03-25 11:53 CEST (History)
2 users (show)

See Also:
Source RPM: numlock
CVE:
Status comment:


Attachments

Description Roger N 2016-07-29 00:48:06 CEST
impossible to have numlock on at startup.

numlok 2.1.2-12.mga6:


How reproducible:


Steps to Reproduce:
1.ne service numlock
2.no numlock on in sddm, lxdm
3.1 use a portable computer with no light for numlock
Comment 1 Rémi Verschelde 2016-07-29 10:56:59 CEST
Assigning to all packagers collectively as numlock has no registered maintainer.

Assignee: bugsquad => pkg-bugs

Comment 2 Rémi Verschelde 2017-03-10 07:58:45 CET
I can confirm something fishy with numlock, as:

# urpmi numlock

[...]
Warning: Problems encountered when activating services.
  Please check and enable manually if necessary.
  Service units affected: numlock.service
service numlock does not support chkconfig


# urpme numlock

removing numlock-2.1.2-12.mga6.x86_64
service numlock does not support chkconfig
error: %preun(numlock-2.1.2-12.mga6.x86_64) scriptlet failed, exit status 1
ERROR: 'script' failed for numlock-2.1.2-12.mga6.x86_64
error: numlock-2.1.2-12.mga6.x86_64: erase failed
Samuel Verschelde 2017-03-10 09:40:27 CET

Priority: Normal => High
Target Milestone: --- => Mageia 6

Comment 3 Roger N 2017-07-04 17:31:07 CEST
Bonjour



Numlock ne fonctionne toujours pas.
Le service numlock n'existe toujours pas dans le MCC.
Numlock ne se désinstalle pas dans le MCC : la manip se fait mais numlocks reste installé.


Effacement de numlock dans Mcc donne ceci en console :

getting lock on urpmi
getting exclusive lock on rpm
transaction créée pour l'installation sur / (remove=1, install=0, upgrade=0)
le service numlock ne prend pas en charge chkconfig
erreur : %preun(numlock-2.1.2-12.mga6.x86_64) scriptlet échoué, état de sortie 1
Error: ERROR: 'script' failed for numlock-2.1.2-12.mga6.x86_64
erreur : numlock-2.1.2-12.mga6.x86_64: effacer échoué
unlocking urpmi database
unlocking rpm database
getting lock on urpmi


Effacement de numlock en console donne ceci :

[root@mageiahost roger]# urpmi numlock
Le paquetage numlock-2.1.2-12.mga6.x86_64 est déjà installé
[root@mageiahost roger]# urpme numlock
désinstallation de numlock-2.1.2-12.mga6.x86_64
le service numlock ne prend pas en charge chkconfig
erreur : %preun(numlock-2.1.2-12.mga6.x86_64) scriptlet échoué, état de sortie 1
ERROR: 'script' failed for numlock-2.1.2-12.mga6.x86_64
erreur : numlock-2.1.2-12.mga6.x86_64: effacer échoué
[root@mageiahost roger]#
Comment 4 Samuel Verschelde 2017-07-10 15:14:46 CEST
It would be good to add a note about this in the Errata, thus I'm adding the FOR_ERRATA6 keyword.

Once added to https://wiki.mageia.org/en/Mageia_6_Errata please replace FOR_ERRATA6 with IN_ERRATA6.

Keywords: (none) => FOR_ERRATA6

Comment 5 Rémi Verschelde 2017-07-15 01:09:27 CEST
Seems it might be a duplicate of bug 18027, which has a documented workaround?
Though it doesn't necessarily cover the %preun failure shown in comment 3.
Comment 6 Marja Van Waes 2017-07-15 20:05:49 CEST
(In reply to Rémi Verschelde from comment #5)
> Seems it might be a duplicate of bug 18027, which has a documented
> workaround?
> Though it doesn't necessarily cover the %preun failure shown in comment 3.

So let's keep this report for that issue... it's annoying that even uninstalling the package doesn't work.

I'll move FOR_ERRATA6 to bug 18027

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=18027
Summary: numlock non active on start. => numlock cannot be uninstalled (%preun failure)
CC: (none) => marja11
Keywords: FOR_ERRATA6 => (none)

Comment 7 Thierry GUYOT 2017-07-21 10:25:34 CEST
The problem with the numlock service comes from the /etc/init.d/numlock script.

The "chkconfig" comment line is wrong :
# chkconfig 3457 26 15

The runlevel 7 doesn't exist and the line should be :
# chkconfig 345 26 15

After correction, everything is ok and the package can be uninstalled.

Best regards.

CC: (none) => thguyot

Marja Van Waes 2017-07-21 21:16:54 CEST

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=21301

Comment 8 Samuel Verschelde 2018-03-25 11:53:17 CEST
The cause is the same as that of bug #18027

Closing this one as duplicate. Fix in progress.

*** This bug has been marked as a duplicate of bug 18027 ***

Resolution: (none) => DUPLICATE
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.