Bug 12388 - Fresh install of 4RC fails to set up X server correctly on VBox VM
Summary: Fresh install of 4RC fails to set up X server correctly on VBox VM
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-21 21:05 CET by Richard Walker
Modified: 2014-01-22 00:41 CET (History)
0 users

See Also:
Source RPM: not known
CVE:
Status comment:


Attachments
first re-boot Xorg log (18.55 KB, application/octet-stream)
2014-01-21 21:09 CET, Richard Walker
Details

Description Richard Walker 2014-01-21 21:05:34 CET
Description of problem:
I have two Cauldron VMs which I leapfrog; one is updated and one used for fresh installations. I have just replaced the updated 4A3 with 4RC. I still have a recently installed 4B2. 4RC is the first one I can remember having trouble getting it to a graphical desktop. Incidentally, and hopefully irrelevantly, it is also the first Cauldron instance which couldn't install LXDE (my normal desktop).

The first boot stopped at the console warning about not being able to start X and reconfiguring with XFdrake followed by a reboot only repeats the message.

/var/log/Xorg.9.log tells me "AutoAddDevices is off" for all attempts by udev to add input devices.

Version-Release number of selected component (if applicable):
Cauldron 4RC iso x86_64

How reproducible:
Every time so far

Steps to Reproduce:
1.boot VM
2.run XFdrake
3.goto 1


Reproducible: 

Steps to Reproduce:
Comment 1 Richard Walker 2014-01-21 21:09:09 CET
Created attachment 4841 [details]
first re-boot Xorg log
Comment 2 Richard Walker 2014-01-21 22:56:27 CET
I think I mis-diagnosed the problem. It is not that the X-server fails during startup. I should have realised that the log file would have been Xorg.0.log if that were the case. 

The Xorg.9.log file seems to belong to the run of XFdrake, and that would likely mean that it is OK not to auto-detect the input devices.

So I am left with the puzzle of discovering why I get no Xorg.0.log file....
Comment 3 Richard Walker 2014-01-21 23:23:36 CET
Couldn't think what else to do to fiz it, so I am re-installing. 

In the installer, a few minutes ago, I started to apply a manual configuratopn for the X-server. Instead of accepting all the (correct looking) default options, I chose to pick each one explicitly. A few minutes ago I clicked on the drop-down list selector for the monitor resolution. The box reads "Automatic". I was only going to select "Automatic 24 bpp", but I am still waiting for the list to appear. 

The Video card selector was also slow to appear, though much quicker than this.

I don't think this installation is going any further so I'll kill it and try again.
Comment 4 Richard Walker 2014-01-21 23:31:08 CET
OK, that's interesting...

The drop-down selector looked "depressed" :~( but I clicked it again anyway and the selection list appeared. I picked "Automatic" (this one does not show "Automatic 24bpp" like the console version of XFdrake).

I needed to click the colour resolution button twice too. The first click seems to be ignored, though it has the expected effect on the appearance of the screen widget.

Now we are back on familiar ground; clicking the "Test" button produces only a resized black screen - this is what happens on first boot re-configuration too. Not optimistic this will work...
Comment 5 Richard Walker 2014-01-21 23:39:17 CET
...how wrong was I? This time the boot process even looked different.I got the updated MGA4 splash screen and background instead of the minimalist (but attractive) three-colours progress-bar.

I now have a graphical login (I picked RazorQT as the installer does not offer the LXDE options - bug 12389), so I will get rid of it and install LXDE before I dump this VM and try again...
Comment 6 Richard Walker 2014-01-22 00:41:20 CET
Two installs later and I still have a working system. Looks like the problem has gone away.

Sorry for the noise.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.