Bug 289 - X server can not start successfully with sato/sdk in qemux86
Summary: X server can not start successfully with sato/sdk in qemux86
Status: VERIFIED FIXED
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: 0.9
Hardware: x86 x86
: High normal
Target Milestone: 0.9 M4
Assignee: Ke Yu
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2010-09-08 01:43 UTC by xianchao zhang
Modified: 2010-12-21 06:07 UTC (History)
9 users (show)

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


Attachments
qemux86 with sato has broken icons (46.37 KB, image/png)
2010-09-08 01:43 UTC, xianchao zhang
no flags Details
X server start up failure with sdk in qemux86 (9.72 KB, application/octet-stream)
2010-09-08 01:45 UTC, xianchao zhang
no flags Details
Xorg.0.log for qemux86+sato (21.34 KB, text/x-log)
2010-09-08 02:04 UTC, xianchao zhang
no flags Details
x sever shut down error with sdk image (8.81 KB, image/png)
2010-09-09 21:39 UTC, xianchao zhang
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description xianchao zhang 2010-09-08 01:43:43 UTC
Created attachment 40 [details]
qemux86 with sato has broken icons

Testing Env:    
Host: Ubuntu 10.04 LTS
Kernel: 2.6.32-21-generic-pae
Image location: http://autobuilder.pokylinux.org/milestone/20100905-1/

1. download sato or sdk image from milesone build.
2. boot up qemux86 with either image

2.1 with sato image

The X server can start up, but some icons have broken. Please see the attachments.

2.2 with sdk image

At first the X server can start up, but has the same above issue. After removing 
/etc/volatile.cache, the X server started failed. Some log in dmesg:

EXT3-fs (hda): using internal journal
connman-applet[352]: segfault at d79a9020 ip 49e061c3 sp bff6b900 error 4 in libgtk-x11-2.0.so.0.2000.1[49d23000+377000]
matchbox-deskto[383]: segfault at d7a19020 ip 49e061c3 sp bfdc8e70 error 4 in libgtk-x11-2.0.so.0.2000.1[49d23000+377000]
matchbox-panel[384]: segfault at d787c020 ip 49e061c3 sp bf97ce20 error 4 in libgtk-x11-2.0.so.0.2000.1[49d23000+377000]


BTW, both of them has no /dev/fb* device node.
Comment 1 xianchao zhang 2010-09-08 01:45:46 UTC
Created attachment 41 [details]
X server start up failure with sdk in qemux86
Comment 2 xianchao zhang 2010-09-08 02:04:31 UTC
Created attachment 42 [details]
Xorg.0.log for qemux86+sato
Comment 3 xianchao zhang 2010-09-09 21:39:32 UTC
Created attachment 43 [details]
x sever shut down error with sdk image
Comment 4 xianchao zhang 2010-09-09 21:39:57 UTC
With the latest build image from :
http://autobuilder.pokylinux.org/build-areas/milestone-release/build/build/tmp/deploy/images/

X server can start up with qemux86 with sdk image, but it has mouse shadow and there will be no mouse response if reboot the system with command 'reboot'. The
X server can not shut down successfully, see the attachment xshudownerror.png.

X server can not start up with qemux86 with sato image.
Comment 5 Jiajun Xu 2010-09-14 07:20:06 UTC
(In reply to comment #4)
> With the latest build image from :
> http://autobuilder.pokylinux.org/build-areas/milestone-release/build/build/tmp/deploy/images/
> X server can start up with qemux86 with sdk image, but it has mouse shadow and
> there will be no mouse response if reboot the system with command 'reboot'. The
> X server can not shut down successfully, see the attachment xshudownerror.png.
> X server can not start up with qemux86 with sato image.

Xianchao,
Does the X server fails to start up issue not occur now? If so, I think you can mark the bug as fixed and open a new bug for other X issue.
For the mouse shadow issue, we have another bug to track it, bug 170.
Comment 6 xianchao zhang 2010-09-14 20:08:25 UTC
(In reply to comment #5)
> (In reply to comment #4)
> > With the latest build image from :
> > http://autobuilder.pokylinux.org/build-areas/milestone-release/build/build/tmp/deploy/images/
> > X server can start up with qemux86 with sdk image, but it has mouse shadow and
> > there will be no mouse response if reboot the system with command 'reboot'. The
> > X server can not shut down successfully, see the attachment xshudownerror.png.
> > X server can not start up with qemux86 with sato image.
> 
> Xianchao,
> Does the X server fails to start up issue not occur now? If so, I think you can
> mark the bug as fixed and open a new bug for other X issue.
> For the mouse shadow issue, we have another bug to track it, bug 170.

The X server fails to start up with sdk image based on the m3 build(20100911).
And it can start up with sato image.
Comment 7 xianchao zhang 2010-09-27 19:53:18 UTC
With the latest build image from :
http://autobuilder.pokylinux.org/nightly/20100924-1/

X server can start up with qemux86 with sdk image,but it can not start up with qemux86 with sato image.
Comment 8 Ke Yu 2010-09-28 05:44:30 UTC
(In reply to comment #7)
> With the latest build image from :
> http://autobuilder.pokylinux.org/nightly/20100924-1/
> 
> X server can start up with qemux86 with sdk image,but it can not start up with
> qemux86 with sato image.

I download the image and run in my local machine, the sato can boot into X in qemux86, so looks it is still environmental issue in xianchao's machine.
Comment 9 xianchao zhang 2010-09-29 01:10:57 UTC
(In reply to comment #8)
> (In reply to comment #7)
> > With the latest build image from :
> > http://autobuilder.pokylinux.org/nightly/20100924-1/
> > 
> > X server can start up with qemux86 with sdk image,but it can not start up with
> > qemux86 with sato image.
> 
> I download the image and run in my local machine, the sato can boot into X in
> qemux86, so looks it is still environmental issue in xianchao's machine.

I double check this nightly build in my fellow jingdong's machine, the sato can not start up with sato image either.

However with the latest nightly build(20100928), the sato image can start up X
server with qemux86 in my machine. So it seems not my machine's issue, maybe
someone introduce some bugs, and maybe this issue was related with local machine
's environment.
Comment 10 Ke Yu 2010-09-29 01:17:30 UTC
(In reply to comment #9)
> I double check this nightly build in my fellow jingdong's machine, the sato can
> not start up with sato image either.
> However with the latest nightly build(20100928), the sato image can start up X
> server with qemux86 in my machine. So it seems not my machine's issue, maybe
> someone introduce some bugs, and maybe this issue was related with local
> machine
> 's environment.

so how about the sdk image of the 09/28 nightly build?
Comment 11 xianchao zhang 2010-09-29 01:27:56 UTC
(In reply to comment #10)
> (In reply to comment #9)
> > I double check this nightly build in my fellow jingdong's machine, the sato can
> > not start up with sato image either.
> > However with the latest nightly build(20100928), the sato image can start up X
> > server with qemux86 in my machine. So it seems not my machine's issue, maybe
> > someone introduce some bugs, and maybe this issue was related with local
> > machine
> > 's environment.
> 
> so how about the sdk image of the 09/28 nightly build?

The sdk image may build failed since there is no sdk image in the
build server now.
Comment 12 Ke Yu 2010-09-29 02:07:32 UTC
> The sdk image may build failed since there is no sdk image in the
> build server now.

Ha, you are right. SDK image failed due the gconf-dbus unpack issue. This should be fixed today, so maybe you can check with tomorrow's build.

- Ke
Comment 13 Jessica 2010-10-04 11:09:22 UTC
Pending verification
Comment 14 xianchao zhang 2010-10-26 23:08:04 UTC
Verified with 10/24 milestone build images.