Mir

android-input logs are not flushed as soon as they happen

Bug #1470204 reported by Daniel d'Andrada
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
Medium
Alberto Aguirre
mir (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

steps:

1- enable android-input logging
eg, by adding "export MIR_SERVER_LEGACY_INPUT_REPORT=log;export ANDROID_LOG_TAGS=*:v" to /usr/share/ubuntu-touch-session/usc-wrapper

2- $ sudo tail -f /var/log/lightdm/unity-system-compositor.log

3- touch the screen

expected outcome:
you see the log lines appearing for the touch events as they happen

actual outcome:
the log file is written after every N bytes of android-input logging take place. So the update happens in chunks and sometimes it stops in the middle of a log entry.

Related branches

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Remember to fflush()

:)

Changed in mir:
status: New → In Progress
assignee: nobody → Alberto Aguirre (albaguirre)
milestone: none → 0.15.0
Changed in mir:
importance: Undecided → Medium
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.15.0

Changed in mir:
status: In Progress → Fix Committed
Changed in mir:
status: Fix Committed → Fix Released
no longer affects: mir (Ubuntu)
Changed in mir (Ubuntu):
status: New → Fix Released
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.