eglapp logs confusing pixel format information
Bug #1168304 reported by
Daniel van Vugt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Fix Released
|
Low
|
Daniel van Vugt | ||
mir (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Run an eglapp (mir_egl*) and you can see potentially confusing statements:
Connected to display /tmp/mir_socket: 1366x768, supports 2 pixel formats
Using pixel format #3
Using format 3 of 2?!
Actually, yes. It is using format #3 out of 5 (MirPixelFormat). And the machine supports 2 of those 5. But we should probably clarify the above messages from eglapp.c to avoid any confusion.
Related branches
lp://qastaging/~vanvugt/mir/fix-1168304
- PS Jenkins bot (community): Approve (continuous-integration)
- Kevin DuBois (community): Approve
- Alan Griffiths: Approve
-
Diff: 55 lines (+8/-9)2 files modifiedexamples/eglapp.c (+6/-8)
include/shared/mir_toolkit/client_types.h (+2/-1)
Changed in mir: | |
status: | New → Triaged |
Changed in mir: | |
assignee: | nobody → Daniel van Vugt (vanvugt) |
status: | Triaged → In Progress |
milestone: | none → 0.1.2 |
Changed in mir: | |
status: | Fix Committed → Fix Released |
Changed in mir (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Low |
Changed in mir (Ubuntu): | |
status: | Triaged → Fix Committed |
To post a comment you must log in.
Fix committed into lp:~mir-team/mir/development-branch at revision 1231, scheduled for release in mir, milestone Unknown