Failing to set a valid MirSurfaceParameters.output_id causes cryptic exceptions in clients: Failed to import PRIME fd for DRM buffer

Bug #1216511 reported by Daniel van Vugt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Triaged
Medium
Unassigned
mir (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

As discovered in bug 1215754, if you forget to or incorrectly set MirSurfaceParameters.output_id then your client will crash with a cryptic error:

terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >'
  what(): Failed to import PRIME fd for DRM buffer

We clearly need better error checking.

Changed in mir:
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Michał Sawicz (saviq) wrote :

Syncing task from Mir.

Changed in mir (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
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.