Bug 3110 - [qemu] X server fails to start
Summary: [qemu] X server fails to start
Status: RESOLVED DUPLICATE of bug 3089
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: configuration (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Undecided normal
Target Milestone: ---
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2012-09-13 17:31 UTC by Stoicescu Cornel
Modified: 2012-09-18 15:55 UTC (History)
1 user (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stoicescu Cornel 2012-09-13 17:31:48 UTC 
X server fails to start on 

coreimage-sato-qemux86.ext3
coreimage-sato-sdk-qemux86-64.ext3
coreimage-sato-qemux86.ext3
coreimage-sato-sdk-qemux86-64.ext3

From: http://autobuilder.yoctoproject.org/pub/nightly/20120907-1/
Commit: dd3edc9fbb674682947e8218202fdbeef8635dd5

Please see also Bug ID: 3089 (closed) for a similar issue.

Log output:
"
qemux86 login: xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
"

Also please note that xserver-xorg is installed:
"
root@qemux86:~# rpm -qa | grep xserver
xserver-xorg-module-exa-1.11.2-r6.i586
packagegroup-core-x11-xserver-1.0-r38.qemux86
xserver-nodm-init-1.0-r30.qemux86
xserver-nodm-init-dev-1.0-r30.qemux86
xserver-xorg-dev-1.11.2-r6.i586
packagegroup-core-x11-xserver-dev-1.0-r38.qemux86
"
Comment 1 Stoicescu Cornel 2012-09-17 11:41:36 UTC 
Correction: 

X server fails to start on 

core-image-sato-qemux86.ext3
core-image-sato-sdk-qemux86.ext3
core-image-sato-qemux86-64.ext3
core-image-sato-sdk-qemux86-64.ext3

Also please note that the issue seems to be fixed in branch origin/1.3_M4 git rev: e5c3513ca8abb21eb5e9b8c19d1b9199b14ae07c
Comment 2 Saul Wold 2012-09-18 15:55:42 UTC 
Duplicate, know issue, a patch is in the works

*** This bug has been marked as a duplicate of bug 3089 ***