Bug 1519

Summary:	[multilib/rpm] X not start up with lib32 build with connman against qemux86-64
Product:	[Build System, Metadata & Runtime] Meta-yocto	Reporter:	Jiajun Xu <jiajun.xu>
Component:	meta-yocto	Assignee:	Dongxiao Xu <dongxiao.xu>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Medium	CC:	dongxiao.xu, ke.yu, mark.hatle, poky.bs.watcher, poky.watcher, sgw
Version:	unspecified
Target Milestone:	1.2
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	---

Description Jiajun Xu 2011-09-22 23:35:44 UTC

tree/branch: poky/master
commit: ff8f0ea563ba3e9d6f8b8e770cfbf4dca8ad5288

With following combination, I could build lib32-connman for qemux86-64. The build could pass but when I start QEMU, X could not start up and a lot of applications segfault.

###
MACHINE=qemux86-64
require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib32 = "x86"
MULTILIB_IMAGE_INSTALL = "lib32-connman"
###

Part of dmesg log:
####
uvesafb: probe of uvesafb.0 failed with error -22
udev[55]: starting version 164
NET: Registered protocol family 10
oprofile-server[294]: segfault at 3df0e7c740 ip 0000003df0e7c740 sp 00007ffffb8d4cf8 error 14
eth0: no IPv6 routers present
rpm[309]: segfault at 3df0e89c90 ip 0000003df0e89c90 sp 00007fffe763eae8 error 14
####

Comment 1 Dongxiao Xu 2011-09-23 06:22:14 UTC

I just did a fresh build against master with the same config as yours, and it can boot up successfully with lib32-connman installed.

Comment 2 Jiajun Xu 2011-09-26 05:54:47 UTC

(In reply to comment #1)
> I just did a fresh build against master with the same config as yours, and it
> can boot up successfully with lib32-connman installed.

I download edison branch and build it from scratch. It still fails on my machine. The only difference is that this time I am not able to ssh on the QEMU target and X could not start up also.

Comment 3 Dongxiao Xu 2011-09-28 18:16:10 UTC

This should be a duplication of bug 1538, and it doesn't happen everytime. Let's track it there.

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