Description of problem: The problem occurs in a VirtualBox 64bit machine. On KDE, mgaapplet indicates there is update available. Launch MageiaUpdate via mgaapplet and launch update for all packages (more than hundred in my case). When it tries to update the kernel, the process freeze. [root@cauldron ~]# ps -ef|grep mga yann 2879 2711 0 Aug29 ? 00:00:06 /usr/bin/perl /usr/bin/mgaapplet root 21785 17369 0 Aug29 ? 00:00:00 /bin/sh /sbin/installkernel 3.10.9-desktop-1.mga4 root 21786 21785 0 Aug29 ? 00:00:00 /usr/bin/perl /sbin/bootloader-config --kernel-version 3.10.9-desktop-1.mga4 --initrd-options --action add-kernel root 27411 27252 0 01:38 pts/1 00:00:00 grep --color mga [root@cauldron ~]# ps -ef|grep rpm root 17369 15942 0 Aug29 ? 00:00:00 /bin/sh /var/tmp/rpm-tmp.YIARX7 0 root 27418 27252 0 01:38 pts/1 00:00:00 grep --color rpm [root@cauldron ~]# ps -ef|grep Mageia yann 15924 2879 0 Aug29 ? 00:00:00 MageiaUpdate --no-media-update --no-confirmation --no-splash root 15931 15924 0 Aug29 ? 00:00:00 /usr/sbin/userhelper -w MageiaUpdate --no-media-update --no-confirmation --no-splash root 15942 15931 2 Aug29 ? 00:03:44 /usr/bin/perl /usr/sbin/MageiaUpdate --no-media-update --no-confirmation --no-splash root 27433 27252 0 01:38 pts/1 00:00:00 grep --color Mageia Version-Release number of selected component (if applicable): I have the problem since mga2, but I install a clean mga3 before switch to cauldron. If I use in a shell "urpmi --auto-update", the problem never occurs. Reproducible: Steps to Reproduce:
CC: (none) => tmbAssignee: bugsquad => thierry.vignaud
Just a precision: After made a kill -9 on process 21785 (/bin/sh /sbin/installkernel 3.10.9-desktop-1.mga4), MageiaUpdate continue others update. So the problem seem to be the call of installkernel script by MageiaUpdate.
The issue is that: 1) kernel post scripts consumes quite some time 2) rpm doesn't enables to follow script progress (which would be hard to do anyway)
The problem is always here in Cauldron. I just encounter it.
Finally I think the problem is in installkernel. If I launch « /sbin/installkernel 3.12.6-desktop-2.mga4 » in a root terminal, the command is never ending.
After dig, this is the command never ending : /usr/bin/perl /sbin/bootloader-config --kernel-version 3.12.6-desktop-2.mga4 --initrd-options --action add-kernel
The option « --action add-kernel » is false. It does not exist. The possibility for this option are : remove-kernel add-entry remove-entry update-splash remove-splash rebuild-initrds migrate-to-uuids
oops, forget my last comment
It's just that it can take quite some time on some machines. If you kill the script that runs dracut/mkinitrd, you can end in having unbootable entries in your boot menu
CC: (none) => mageia
But in this case, the script do nothing. After reboot the vm and launch it manually, it works well. I do not know why sometimes it freeze.
When it's frozen, can you work out what command installkernel has shelled out to? e.g. does it have any child processes (see pstree output or use ps -H switch) I doubt the installkernel script itself has frozen so it's important to find which command causes it problems. Note that I've been updating kernels via MageiaUpdate for years on Cauldron and have not encountered this issue.
I think it is this command : /usr/bin/perl /sbin/bootloader-config --kernel-version 3.12.6-desktop-2.mga4 --initrd-options --action add-kernel But I need to verify this point at the next freeze.
This command itself should spawn others, and I suspect it's one of these other commands that is locking things up in some capacity. So please check for children of this process.
I have a freeze this morning. I have this result with pstree : â ââmgaappletââ¬âdrakrpm-updateââ¬âshâââswitch-themesâââbootloader-conf â â â ââ{gmain} â â ââ{gdbus} â â ââ{gmain} â â ââ{threaded-ml}
Detail of problematic command : /usr/bin/perl /usr/sbin/bootloader-config --action update-splash
[nic@localhost packages]$ sudo /usr/bin/perl /usr/sbin/bootloader-config --action update-splash [sudo] password for nic: defaulting background resolution to 1024x768 defaulting background resolution to 1024x768 [nic@localhost packages]$ Are you still having the issue?
CC: (none) => nic
No, I can not reproduced it now in cauldron. I close this bug. Thank you
Status: NEW => RESOLVEDResolution: (none) => FIXED