I've made a fress install of Mageia 6 SAT1 in Virtual Box. Without any update it starts OK but after the first reboot (with no updates) I receive a message of "Sorry, but there has been a problem starting your graphical display." In /var/lob/Xorg.0.log I see errors like: [ 18.509] (**) Load address of symbol "VBOXVIDEO" is 0x7f075374b380 [ 18.509] (II) LoadModule: "vboxmouse" [ 18.509] (WW) Warning, couldn't open module vboxmouse [ 18.509] (II) UnloadModule: "vboxmouse" [ 18.509] (II) Unloading vboxmouse [ 18.509] (EE) Failed to load module "vboxmouse" (module does not exist, 0) [ 18.509] (II) v4l driver for Video4Linux overlay mode (V4L2)
Please attach your /root/drakx/report.bug.xz file
Keywords: (none) => NEEDINFOCC: (none) => thierry.vignaudSummary: Unable to start X after second reboot (at least in Virtual Box) => Unable to start X after second reboot in VBox ("Failed to load module "vboxmouse" (module does not exist, 0)"
Created attachment 8159 [details] report.bug.xz
Check this: https://youtu.be/KPT4GGzjpUU
@Alejandro: Could you attach (not paste) your /etc/X11/xorg.conf file after the first boot and after the second boot? Also please attach the journal.txt file resulting from running the following command as root after the second boot: journalctl >/tmp/journal.txt @Thomas: Do you know why you removed x11-driver-input-vboxmouse (quite some time ago)? What driver should we used in stead? libinput like everything else those days? I don't why that's breaking now since you killed it 5 years ago and since we didn't change anything about this I can think of. What I find strange is that we didn't did anything in mousedrake after you killed that package. But why is it bitting us now??? The only remotely related commit is this one: http://gitweb.mageia.org/software/drakx-kbd-mouse-x11/commit/?id=52409c682c37ab200f636af9254d4328c5c988ec But I failed to see how it can affect the vbox case...
CC: (none) => tmb
Created attachment 8170 [details] xorg.conf first boot
Created attachment 8171 [details] xorg.conf second boot
Created attachment 8172 [details] journal.txt first boot
Created attachment 8173 [details] journal.txt second boot
I've attached the files but I think you could see it by yourself. Here you can download the virtual machine: https://mega.nz/#!gVxk3RLQ You can just import it in virtualbox. Root password is mageia. User is "anv", and same password (mageia).
Password for the mega download: !sBMjUo4Gih4vAPDueNh-Ng6_zgD9Lli0TaWVTyecZR4
Keywords: NEEDINFO => (none)CC: (none) => marja11Assignee: bugsquad => tmb
commit 1dad9ad051c124424812967e7569462a6c6b3238 Author: Thierry Vignaud <thierry.vignaud@...> Date: Thu Jul 14 17:40:52 2016 +0200 stop installing/configuring vboxmouse (mga#18917) VBox rely on evdev (kernel) + libinput (userspace) like everyone these days. VMs must just use USB tablet as input device (which is now the default) --- Commit Link: http://gitweb.mageia.org/software/drakx-kbd-mouse-x11/commit/?id=1dad9ad051c124424812967e7569462a6c6b3238
it should be fixed if you do a new network installation
Can you try latest installer from today?
Keywords: (none) => NEEDINFO
Is there a new iso available?
(In reply to Alejandro Vargas from comment #14) > Is there a new iso available? if you do a network install https://wiki.mageia.org/en/Mageia_Netinstall_Iso_%28Boot.iso%29 e.g. with this iso ftp://ftp.snt.utwente.nl/pub/os/linux/mageia/distrib/cauldron/x86_64/install/images/Mageia-Cauldron-netinstall-nonfree-x86_64.iso then you'll have the latest installer, assuming your mirror is up-to-date. If you're not sure your mirror is fully up-to-date, then you can check the time stamp of mdkinst.sqfs in this directory ftp://ftp.snt.utwente.nl/pub/os/linux/mageia/distrib/cauldron/x86_64/install/stage2/ (Change the above two paths to match your mirror and desired arch)
(for the record: mdkinst.sqfs contains stage2 of our installer)
also, if the boot still fails after a new install, can you as root do a: echo "blacklist vboxvideo" >/etc/modprobe.d/vboxvideo.conf and reboot... does it boot up properly then ?
Just made a fresh network install. X does not start even on first boot. Then added the "blacklist vboxvideo", rebooted and X started OK. Tested some reboots from different points. All OK. Thank you.
I have found this to be the case with mga6-sta1 classic 32-bit DVD installs under Virtualbox. I have not found any problem with the 64-bit guests. I have also successfully used the blacklist workaround from Comment 17 to restore graphical functionality.
CC: (none) => sharpzq4300
(In reply to Adam Holland from comment #19) > I have found this to be the case with mga6-sta1 classic 32-bit DVD installs > under Virtualbox. I have not found any problem with the 64-bit guests. > > I have also successfully used the blacklist workaround from Comment 17 to > restore graphical functionality. I am mistaken. 64-bit guests are affected too. It is related to the choice of desktop at install time. My guess is that Plasma and GNOME are fine, while choices under "Custom" including MATE, LXDE and XFCE are affected.
I am having the same problem first noticed in a similar way. Yesterday, on my first ever MGA6 install, also on a VBox VM, the first reboot was OK. After updates I had 3 kernels. I removed the two oldest using MCC. On the next boot X would not start. I made several attempts to "fix" the video settings with XFdrake and gave up. I created a new VM for a fresh attempt to get the first boot to work, but nothing good is happening. All attempts to boot to a desktop (1 successful, many more not) have been with LXDE as the only choice. The host is MGA5 64bit with latest VBox. The Guest is also 64bit. Other VMs continue to work (XP 32 bit, MGA4 64 bit). > I have also successfully used the blacklist workaround from Comment 17 to > restore graphical functionality. Ditto
CC: (none) => richard.j.walker
I assume the blacklist will be added to the next release.
No problems with current vb installs.
Status: NEW => RESOLVEDCC: (none) => davidwhodginsResolution: (none) => OLD