Advisory: ========= This update adds support for gtkset() on 'ComboBoxText' widgets for drakpxelinux (mga#13492). This fixes drakpxelinux conversion from gtk2 to gtk3 Reproducible: Steps to Reproduce:
Blocks: (none) => 14604
Package list: drakx-finish-install-16.26.12-1.mga4 drakxtools-16.26.12-1.mga4 drakxtools-backend-16.26.12-1.mga4 drakxtools-curses-16.26.12-1.mga4 drakxtools-http-16.26.12-1.mga4 harddrake-16.26.12-1.mga4 harddrake-ui-16.26.12-1.mga4 from drakxtools-16.26.12-1.mga4.src.rpm
Testing complete Mageia 4 i586.
Whiteboard: (none) => MGA4-32-OK
Advisory uploaded.
Whiteboard: MGA4-32-OK => advisory MGA4-32-OK
Testing MGA4-64 on HP6555b. Installation no problem. But I immediately rebooted, and there was something unexpected to me: I got the early installation screens presented: choose language, accept license, choose country, timezone, keyboard, DEFINE root password and enter a new normal user. Sure the user I had on the PC was still known (trying to enter it again, resulted in "User alreadt known, fair enough), but I could not get past that screen without defining a new user (which I deleted afterwards). After all that I got the KDM login screen and could proceed normally. But these extra steps could confuse the "normal user"???? Second reboot was normal. Went through MCC, all seems normal (well apart from the well known printer issue).
CC: (none) => herman.viaene
Anybody else finding this too? (comment 4) Any ideas Thierry?
You'll see that if you install drakx-finish-install. It is used only when installing Mageia from a live iso. On an already installed system or on a newly installed system using the classical installer it is redundant, since there is no "first boot" configuration required.
If you installed from a live iso, then you will not see that, since you already have /etc/sysconfig/finish-install which will indicate that first boot configuration should not be run again.
This is an update for drakxtool James, not an install. Herman experienced that it triggered drakx-finish-install to run again on the next boot.
I guess installing drakx-finish-install if it wasn't installed previously though might trigger it to run at the next boot. Can you remember if it was installed already Herman?
Testing on Mageia4-64 real hardware. From current package : drakxtools-16.26.11-1.mga4x86_64 To updated testing package : drakxtools-16.26.12-1.mga4.x86_64 which brought along : - drakxtools-backend-16.26.12-1.mga4.x86_64 - drakxtools-curses-16.26.12-1.mga4.x86_64 - harddrake-16.26.12-1.mga4.x86_64 - harddrake-ui-16.26.12-1.mga4.x86_64 Rebooted immediately to see if I would come across the same issue than Herman in Comment 4. Which I did not. In MCC, all seemed to work well. Tried some commands from terminal (drakmouse, drakxservices, diskdrake...) which ran well also, asking administrator password when needed.
CC: (none) => olchal
The only purpose and change of this update was to add something in the API that's used by the drakpxelinux update. All that's really needed is to install the updated packages and and test drakpxelinux (see Bug 14604). It's an easy test to perform.
(In reply to claire robinson from comment #9) > I guess installing drakx-finish-install if it wasn't installed previously > though might trigger it to run at the next boot. Can you remember if it was > installed already Herman? I cann't remember ever asking for it, unless it would be included in a standard installation (not live CD!!)?????. It is not installed on my main machine, where I strictly follow the official repositories.
I expect the screens you saw came as a result of installing drakx-finish-install where it wasn't previously installed. As James said, it's used on the Live ISOs to provide the configuration steps which happen after the reboot. The classic ISOs don't use it as that configuration is done before the reboot. As far as testing this update is concerned it shows that the updated drakx-finish-install package is working as expected so it's all good :) I'll add the OK from your testing and validate this one. Could sysadmin please push to updates Thanks
Keywords: (none) => validated_updateWhiteboard: advisory MGA4-32-OK => advisory MGA4-32-OK mga4-64-okCC: (none) => sysadmin-bugs
You can check it was wrongly installed (eg: rpm -Uvh drak*) by looking at: journalctl|grep drak
I tested on Mageia 4 64bit (installed from a LiveDVD) and so no regression. drakx-finish-install was also updated but did not trigger the post-install config, as it's already marked as "OK" on LiveDVD installs as pointed out in comment 7.
CC: (none) => remi
s/so/saw/ :-o
An update for this issue has been pushed to Mageia Updates repository. http://advisories.mageia.org/MGAA-2014-0206.html
Status: NEW => RESOLVEDResolution: (none) => FIXED