Mir

nested render_surfaces fails on N4 [std::exception::what: Failed to compile vertex shader:]

Bug #1284597 reported by Alan Griffiths
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
Medium
Alan Griffiths
mir (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

./mir_demo_server_basic --launch-client ./mir_demo_standalone_render_surfaces
Rendering 5 surfaces
ERROR: /home/alan/display_server/mir/examples/image_renderer.cpp(87): Throw in function void {anonymous}::throw_with_object_log({anonymous}::MirGLGetObjectInfoLog, {anonymous}::MirGLGetObjectiv, const string&, GLuint)
Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >
std::exception::what: Failed to compile vertex shader:

Tags: nested nexus4

Related branches

Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

This isn't a "launch-client" issue - it fails the same way when separately.

Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

The immediate cause is that in a nested process there is no current EGL context when run_mir() calls the init code. However, the example code that initialises the buffers assumes there's an existing EGL context.

It seems there is a current egl context when not running in nested mode (but it isn't obvious that there should be).

tags: added: nested
Changed in mir:
milestone: none → 0.1.6
assignee: nobody → Alan Griffiths (alan-griffiths)
importance: Undecided → Medium
status: New → In Progress
summary: - nested render_surfaces fails on N4
+ nested render_surfaces fails on N4 [std::exception::what: Failed to
+ compile vertex shader:]
tags: added: nexus4
description: updated
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:mir/devel at revision None, scheduled for release in mir, milestone Unknown

Changed in mir:
status: In Progress → Fix Committed
Changed in mir:
status: Fix Committed → Fix Released
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This bug was fixed in the package mir - 0.1.6+14.04.20140310-0ubuntu1
---------------
mir (0.1.6+14.04.20140310-0ubuntu1) trusty; urgency=medium

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