Mir

Unity8 crashes on HTC Desire Z with: what(): ver requests info we dont provide. Key 3 is NATIVE_WINDOW_MIN_UNDEQUEUED_BUFFERS.

Bug #1239160 reported by Florian W. on 2013-10-12
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
Medium
Florian W.
mir (Ubuntu)
Medium
Unassigned

Bug Description

When enabling Mir for Ubuntu Touch on the HTC Desire Z ("vision", community port maintained by me), the screen stays black and strange-looking vertical lines slowly appear within a few minutes after booting. Instead I'd expect it to show the unity 8 shell.

Unity 8 log shows an unhandled mir exception:
> terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >'
> what(): ver requests info we dont provide. key:

The message is obviously truncated, further debugging revealed that it's actually "driver requests info we dont provide. key: 3". Key 3 is NATIVE_WINDOW_MIN_UNDEQUEUED_BUFFERS.

After reading the comment explaining that key, I'm still not sure what it means, so I simply patched Mir to return 1 for that request in all three places (see related branch.. oh, and I got the indentation wrong apparently :)) and Mir now works on my device. *However*, there's a lot of flickering etc., so either that value of 1 is wrong, or there's some other problem.

This is using Touch cdimage 20131010 containing Mir 0.0.14+13.10.20131010-0ubuntu1.

Related branches

description: updated
Florian W. (florian-will) wrote :

Indentation in related branch is now correct, or at least I hope so. :-) (replaced tab with spaces)

Justin Shafer (justinshafer) wrote :

It WORKS!!!!! YAY!!!! Tested on HP Touchpad.

summary: - [Touch Port] Exception: [dri]ver requests info we dont provide
+ Unity8 crashes on HTC Desire Z with: what(): ver requests info we dont
+ provide. Key 3 is NATIVE_WINDOW_MIN_UNDEQUEUED_BUFFERS.
Changed in mir:
assignee: nobody → Florian W. (florian-will)
status: New → In Progress
Changed in mir:
importance: Undecided → Medium
Daniel van Vugt (vanvugt) wrote :

Florian,

Your fix is now up for review by the developers. You can track the progress here:
https://code.launchpad.net/~florian-will/mir/mir/+merge/190850

PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:~mir-team/mir/development-branch at revision None, scheduled for release in mir, milestone Unknown

Changed in mir:
status: In Progress → Fix Committed
Daniel van Vugt (vanvugt) wrote :

Fix committed to lp:mir at revision 1100.

Changed in mir (Ubuntu):
importance: Undecided → Medium
status: New → Fix Committed
Timo Jyrinki (timo-jyrinki) wrote :
Changed in mir (Ubuntu):
status: Fix Committed → Fix Released
Changed in mir:
milestone: none → phone-v1-freeze
Changed in mir:
milestone: phone-v1-freeze → 0.0.16
Changed in mir:
status: Fix Committed → Fix Released
Changed in mir:
milestone: 0.0.16 → 0.0.15
Florian W. (florian-will) wrote :

Thanks for taking care of this so quickly, confirming that this is fixed in the 2013-10-17 Ubuntu Touch image (and possibly earlier images as well).

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers