During testing of upgrade from Mageia 1 to cauldron, after installing 2100 packages in one transaction, the distribution upgrade appears to hang. On my i586 system, it took 20 minutes before the reboot suggestion appeared. Selecting the reboot option just closed the dialog. I had to enter the reboot command manually. During the 20 minute hang, I used htop's trace option, and realized it was processing file triggers. At it's peak ... # wc -l /var/lib/rpm/files-awaiting-filetriggers 260516 /var/lib/rpm/files-awaiting-filetriggers A progress indicator on processing file triggers would be ideal, but there should at least be a message to the effect "Processing file triggers. This may take a while".
Assignee: bugsquad => thierry.vignaud
I also had the dialog box just close and not reboot when upgrading from Mageia 1 to Cauldron. One thing strange for me is that when i clicked the red shutdown button and clicked reboot i was left at a tty screen and after logging in as root init 6 and 0 did not reboot or shutdown the pc i had to issue the shutdown now command . after turning pc back on all is fine.
CC: (none) => andrew
Still current Prerelease 2 final dvd 64 Installer reached 20 seconds left then sat for almost an hour thrashing the disk with no indication what it was doing. See bug 5942
Hardware: i586 => All
Summary: Due to long wait after installing last package, need a message indicating whats going on, and the reboot button didn't reboot. => Due to long wait after installing last package, need a message indicating whats going on.
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
As this only affects upgrading, keeping as cauldron for Mageia 3.
Keywords: NEEDINFO => (none)
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
This should be fixed in trigger scripts. echo $(rpm -qf /var/lib/rpm/filetriggers/* --qf '%{name}\n'|sort -u)
Assignee: thierry.vignaud => bugsquadSource RPM: urpmi-6.48-1.mga2.src.rpm => apache apache-mod_php desktop-common-data desktop-file-utils fontconfig GConf2 glib2.0-common glibc gnome-icon-theme hicolor-icon-theme oxygen-icon-theme php-pear rarian shared-mime-info systemd uClibc
Also note that since mga3, urpmi and the like display an erasure progress bar. Previously, you would have no message while uninstalling the 2100 packages of the transaction. Now you have one. So let's close this one
Status: NEW => RESOLVEDCC: (none) => thierry.vignaudResolution: (none) => FIXED