Tree/Branch: Poky/master Commit: bd2d8904181aa67258b6be8a7bbeaf8d12a8dd5a with 20120311-1 sato image for qemux86 from autobuilder, boot system successful, but it had no response with keyboard and mouse Image location: http://autobuilder.yoctoproject.org/pub/nightly/20120311-1/machines/qemu/q emux86/core-image-sato-qemux86.ext3
(In reply to comment #0) > Tree/Branch: Poky/master > Commit: bd2d8904181aa67258b6be8a7bbeaf8d12a8dd5a > > with 20120311-1 sato image for qemux86 from autobuilder, boot system > successful, but it had no response with keyboard and mouse > > > > Image location: > http://autobuilder.yoctoproject.org/pub/nightly/20120311-1/machines/qemu/q > emux86/core-image-sato-qemux86.ext3 Hi, I have the same issue on qemu. My commit is: package.bbclass: Drop python depends from rpmdep( http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=19b38a6486086b62efbff2bf8192adbaa34ecc0a) BSP seems be affected, too.
(In reply to comment #1) > (In reply to comment #0) > > Tree/Branch: Poky/master > > Commit: bd2d8904181aa67258b6be8a7bbeaf8d12a8dd5a > > > > with 20120311-1 sato image for qemux86 from autobuilder, boot system > > successful, but it had no response with keyboard and mouse > > > > Image location: > > http://autobuilder.yoctoproject.org/pub/nightly/20120311-1/machines/qemu/q > > emux86/core-image-sato-qemux86.ext3 > > Hi, I have the same issue on qemu. > My commit is: > package.bbclass: Drop python depends from rpmdep( > http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=19b38a6486086b62efbff2bf8192adbaa34ecc0a) > > BSP seems be affected, too. Seems the bug has been fixed by the commit? http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=7dfac86166321551b39aa66dddda11dcde1354b9 At least http://autobuilder.yoctoproject.org/pub/nightly/20120313-1/machines/qemu/qemux86/core-image-sato-qemux86-20120313120852.rootfs.ext3 is ok. What's interesting is: Which commit introduced this bug?
*** Bug 2094 has been marked as a duplicate of this bug. ***
It looks the bug was fixed by some commit yesterday? At least the following commit doesn't have this bug: commit cb771ef55afc9acb0babdc4237bf5320cdc8ff6b Author: Richard Purdie <richard.purdie@linuxfoundation.org> Date: Wed Mar 14 15:23:26 2012 +0000 Revert "gcc-cross: aviod creating invalid symlinks" This reverts commit 7893e74311e53882d8f93ecb95a6bd9f5b14651e since it breaks the builds. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The following commit is ok, too. 8e9f6fc77ac4763f4ed1f6e7b720420c220ba6e2 dates: Fix unpackaged files warningesdc2012/poky This directory isn't needed so remove it and resolve the warning: WARNING: For recipe dates, the following files/directories were installed but not shipped in any package: WARNING: /srv (From OE-Core rev: 81379dc141e245307ca391a02b7490b199128991) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Diffstat (more/less context) (ignore whitespace changes) ----- So the bug can be found on bd2d8904181aa67258b6be8a7bbeaf8d12a8dd5a and can't be found on a later commit 8e9f6fc77ac4763f4ed1f6e7b720420c220ba6e2 I had a quick look and couldn't find a suspicious commit what fixed the bug. Can QA help do bisect to find which commit makes the bug disappear?
(In reply to comment #5) > The following commit is ok, too. > > 8e9f6fc77ac4763f4ed1f6e7b720420c220ba6e2 > dates: Fix unpackaged files warningesdc2012/poky > This directory isn't needed so remove it and resolve the warning: > > WARNING: For recipe dates, the following files/directories were installed but > not shipped in any package: > WARNING: /srv > > (From OE-Core rev: 81379dc141e245307ca391a02b7490b199128991) > > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> > Diffstat (more/less context) (ignore whitespace changes) > > > ----- > > So the bug can be found on > bd2d8904181aa67258b6be8a7bbeaf8d12a8dd5a > and can't be found on a later commit > 8e9f6fc77ac4763f4ed1f6e7b720420c220ba6e2 > > I had a quick look and couldn't find a suspicious commit what fixed the bug. > > Can QA help do bisect to find which commit makes the bug disappear? I have identified the bug was caused by recent changes to udev-164: It was introduced by http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=62a2a41194dec4d158c65b218fa45761b4fe1dda and was fixed by http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=e867a99d97e3901bb71bad98ce9c6b82eef51736 so let me mark the bug as FIXED