Description of problem: In Vbox start with an updated M4.1 x86_64 system then execute an upgrade using: Mageia-5-RC-x86_64-DVD.iso Thu Apr 9 22:56:24 CEST 2015 98cbb4e2366dd2218896b71e1801b441 Upgrade proceeds normally with no errors then the reboot stops at a terminal requesting user name and password. Entering both then commanding "startx" then the KDE desktop appears normally. Subsequent reboots require the same process. Reproducible: Steps to Reproduce:
Created attachment 6244 [details] drakx files
CC: (none) => rverschelde
CC: (none) => ennael1, thierry.vignaud, tmb
I don't see the link with installer. I suspect prefdm. Colin?
CC: (none) => mageia
In VirtualBox, M4.1 -> M5, KDE, 64-bit Bug continues: In Vbox start with an updated M4.1 x86_64 system then execute an upgrade using: Mageia-5-RC-x86_64-DVD.iso Mon Apr 20 23:54:12 CEST 2015 f29f810208def3fb3e360d64bb11072d Upgrade proceeds normally with no errors then the reboot stops at a terminal requesting user name and password. Entering both then commanding "startx" then the KDE desktop appears normally. Subsequent reboots require the same process. Test platform: Intel Core i7-2600K Sandy Bridge 3.4GHz GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB RTL8111/8168B PCI Express 1Gbit Ethernet DRAM 16GB (4 x 4GB) Mageia 4 64-bit, Nvidia driver virtualbox-4.3.10-1.1.mga4.x86_64 virtualbox-guest-additions-4.3.10-1.1.mga4.x86_64
Whiteboard: (none) => 5rc
We would need you to attach (not paste) "journalctl -b" output as well as your /var/log/Xorg.0.log (to be saved before you type "startx")
Keywords: (none) => NEEDINFO
Comment on attachment 6244 [details] drakx files We would need your /root/drakx/report.bug.xz instead (so that we can see lspcidrake & the like)
Attachment 6244 is obsolete: 0 => 1
Created attachment 6391 [details] Thierrrys requested files
Created attachment 6393 [details] bug reports I think these are the same
Keywords: NEEDINFO => (none)Priority: Normal => release_blockerBlocks: (none) => 14069
CC: (none) => eeeemail
In VirtualBox, M4.1 -> M5, KDE, 64-bit Bug continues: In Vbox start with an updated M4.1 x86_64 system then execute an upgrade using: Mageia-5-x86_64-DVD.iso Tue May 5 01:17:01 CEST 2015 md5sum: 03896e93c23342539d205ea20e1a7a0e Upgrade proceeds normally with no errors then the reboot stops at a terminal requesting user name and password. Entering both then commanding "startx" then the KDE desktop appears normally. Subsequent reboots require the same process. Test platform: Intel Core i7-2600K Sandy Bridge 3.4GHz GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB RTL8111/8168B PCI Express 1Gbit Ethernet DRAM 16GB (4 x 4GB) Mageia 4 64-bit, Nvidia driver virtualbox-4.3.10-1.1.mga4.x86_64 virtualbox-guest-additions-4.3.10-1.1.mga4.x86_64
So I tried the Upgrade using the 64-bit: boot.iso 39.0 MiB 05/12/15 13:53 Ran into the same exact thing. Bummer. It's really a show stopper. :-((
Whiteboard: 5rc => 5final
CC: (none) => marja11Hardware: i586 => x86_64
Did you do all your upgrade tests using the same Mageia 4 snapshot? If so, it would be great if you could try to install Mageia 4 in a new VM, update it and attempt the upgrade again. If the upgrade works fine, it might help narrow down the issue to a package or config on your current Mageia 4 snapshot.
(In reply to Rémi Verschelde from comment #10) > Did you do all your upgrade tests using the same Mageia 4 snapshot? > > If so, it would be great if you could try to install Mageia 4 in a new VM, > update it and attempt the upgrade again. If the upgrade works fine, it might > help narrow down the issue to a package or config on your current Mageia 4 > snapshot. I should have time tomorrow. I'll run it on real hardware.
Performed a 64bit vbox upgrade with the applet overnight with all DE's and alot of other random stuff, gdm logging in to kde. Only issue was that the Reboot button on the applet caused a segfault rather than reboot. X started after manually rebooting and kde logged in ok. Tested also gdm logging in to gnome, kdm logging in to kde, kdm into e18 (segfault at start which was able to recover, old issue), lxdm into lxde, lightdm into mate, cinnamon 2d, icewm, openbox, windowmaker, xfce and kodi (which needs gpu so doesn't like vbox). Some odd effects, presumably from having so much stuff installed, like two volume controls in lxde, networkmanager applet and net-applet running, so will need to test basic installs from the next set of ISOs. I'll roll it back and try an upgrade with boot.iso One suggestion as a possible cause for this bug is perhaps the use of boot.iso rather than boot-nonfree.iso
Ok, so carefully going through this again on real hardware. First start with a clean drive then install an up-to-date M4.1 x86_64. Then boot from: Mageia-5-x86_64-DVD.iso Tue May 5 01:17:01 CEST 2015 md5sum: 03896e93c23342539d205ea20e1a7a0e After the install and reboot the system does successfully get to a working desktop. Switch the repo from M4.1 -> M5, update ( about 259 packages ), then a successful reboot back to a working desktop. Then reboot again successfully back to a working desktop. So maybe this is indeed a Vbox only phenomenon. I'll once again try this in Vbox to see if I can reproduce it again.
In VirtualBox, M4.1 -> M5, KDE, 64-bit Reproduced again: In Vbox start with an updated M4.1 x86_64 system then execute an upgrade using: Mageia-5-x86_64-DVD.iso Tue May 5 01:17:01 CEST 2015 md5sum: 03896e93c23342539d205ea20e1a7a0e Upgrade proceeds normally with no errors then the reboot stops at a terminal requesting user name and password. Entering both then commanding "startx" then the KDE desktop appears normally. Subsequent reboots require the same process. So this looks to be a Vbox specfic bug. I'm gonna take it off being a release blocker and change it to "high" as it may surface in other environments. Test platform: Intel Core i7-2600K Sandy Bridge 3.4GHz GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB RTL8111/8168B PCI Express 1Gbit Ethernet DRAM 16GB (4 x 4GB) Mageia 4 64-bit, Nvidia driver virtualbox-4.3.10-1.1.mga4.x86_64 virtualbox-guest-additions-4.3.10-1.1.mga4.x86_64
Priority: release_blocker => High
Summary: M4.1 -> M5 ( x86_64 ) upgrade fails to start x after upgrade => M4.1 -> M5 ( x86_64 ) upgrade fails to start x after upgrade in VirtualBox
Whiteboard: 5final => 5final FOR_ERRATA
Is this issue still valid with the released sta1 ISOs / current netinstall?
(In reply to Rémi Verschelde from comment #15) > Is this issue still valid with the released sta1 ISOs / current netinstall? No, lets put this one down.
Status: NEW => RESOLVEDResolution: (none) => FIXED