Bug 9828 - [Beaglebone] mouse doesn't work when system startup
Summary: [Beaglebone] mouse doesn't work when system startup
Status: VERIFIED FIXED
Alias: None
Product: Matchbox
Classification: Yocto Project Subprojects
Component: matchbox (show other bugs)
Version: 2.2
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.2 M2
Assignee: Plauchu Edwin
QA Contact: Yi Zhao
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-06-27 09:05 UTC by Yi Zhao
Modified: 2016-08-23 01:49 UTC (History)
7 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: Regression (Used to work)
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yi Zhao 2016-06-27 09:05:10 UTC
Image location: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.2_M1.rc2/machines/beaglebone/

Git rev: master/6f0c5537e02c59e1c8f3b08f598dc049ff8ee098

Steps:
1. Download beaglebone rootfs and install it to MMC
2. Boot up the system

The matchbox can startup without problem, but there is no mouse.
When I use keyboard to launch an application (e.g. Terminal), the mouse is back and run without problems.
Comment 1 Ross Burton 2016-06-30 14:47:01 UTC
My spider-sense says this is something to do with formfactor.
Comment 2 Plauchu Edwin 2016-07-12 18:56:19 UTC
Mouse is working well!

# hexdump -v -e '3/1 "%02x " "\n"' /dev/input/mice
18 ff 00
18 fe 00
18 ff 00
18 ff 00
18 ff 00
18 ff 00
18 ff 00
18 ff 00
18 ff 00
08 01 00

It is mostly a problem related to mouse visualization that disappears when use keyboard to launch an application.

It is even possible launching an application with mouse when it is still invisible.
Comment 3 Leonardo Sandoval Gonzalez 2016-07-13 14:47:56 UTC
Just a comment: For this kind of situations, you may do a git bisect in case you know a good commit (you know the bad one). At the end, bisect takes 'just' log2(n) steps. The problem is that is too time consuming building a whole image each time.
Comment 4 Plauchu Edwin 2016-07-13 22:59:26 UTC
When an application is launched, it'll be called "launcher_start" within:
matchbox-desktop-2/tree/libtaku/launcher-util.c

This call will end up over a method xcb_flush "https://xcb.freedesktop.org/manual/group__XCB__Core__API.html#ga9361ead09eb756ba9cc8953c4569a789". So mouse is back and run without problems.

Gdb Breakpoints utilized to get such details:

break launcher_start
break sn_launcher_context_initiate
break sn-launcher.c:291
break sn-xmessages.c:221
Comment 5 Plauchu Edwin 2016-07-14 19:43:01 UTC
"Mouse is working as expected with xf86-video-fbdev when system startup"

It seems a configuration problem related to xf86-video-modesetting
Comment 6 Plauchu Edwin 2016-07-20 16:56:32 UTC
We switched to 4.1 instead of 4.4

root@beaglebone:~# uname -mnr
beaglebone 4.1.24-yocto-standard armv7l

Mouse is still invisible when using modesetting
Comment 7 Yi Zhao 2016-07-26 02:19:01 UTC
This issue still happens on 2.2 M2 RC1
Git rev: master/36feb38045b7a2af86ece147fec54b0db3bf491f
Comment 8 Plauchu Edwin 2016-07-26 16:04:38 UTC
The mouse is working well over 

X.Org X Server 1.18.4
Release Date: 2016-07-19

:)
Comment 9 Plauchu Edwin 2016-07-27 16:00:27 UTC
X.Org X Server 1.18.4
Release Date: 2016-07-19

tested on and working well
** qemux86
** qemuarm
** real x86-64
Comment 10 Plauchu Edwin 2016-07-27 16:17:41 UTC
PATCH to upgrade xserver version from 1.18.3 to 1.18.4
http://lists.openembedded.org/pipermail/openembedded-core/2016-July/124393.html
Comment 11 Yi Zhao 2016-08-23 01:49:43 UTC
Verified with 20160819 build.
git rev: master/f038f069977170e323c9c6884c69e0b9e1cf1c6f