| 2016-05-03 22:37:49 |
Cemil Azizoglu |
bug |
|
|
added bug |
| 2016-05-06 15:25:35 |
Cemil Azizoglu |
summary |
mir_surface_is_valid(surface) returns false when a presentation chain is used |
During surface creation, first stream in spec becomes default stream. |
|
| 2016-05-06 15:39:44 |
Cemil Azizoglu |
description |
When mir_demo_client_prerendered_frames, which uses a presentation chain, is run, it works fine.
When
mir_surface_is_valid(surface)
is added after surface creation (i.e. http://bazaar.launchpad.net/~mir-team/mir/development-branch/view/head:/playground/mir_demo_client_prerendered_frames.c#L164), it fails due to the following error being set :
"Can not create buffer stream: Error processing buffer stream create response, no ID (disconnected?)" |
A surface creation spec can have multiple streams. The code currently, by happenstance, makes the first stream the "default stream", i.e. instantiates a MirSurface using that stream. The MirSurface object's methods then uses that stream for various purposes. E.g. to set the swap interval, to set size during resize, to query parameters of the Surface, etc. Here's a list of MirSurface methods that use the default stream :
MirSurface::get_parameters(),
MirSurface::configure(),
MirSurface::attrib(),
MirSurface::handle_event() |
|
| 2016-05-06 15:42:15 |
Cemil Azizoglu |
description |
A surface creation spec can have multiple streams. The code currently, by happenstance, makes the first stream the "default stream", i.e. instantiates a MirSurface using that stream. The MirSurface object's methods then uses that stream for various purposes. E.g. to set the swap interval, to set size during resize, to query parameters of the Surface, etc. Here's a list of MirSurface methods that use the default stream :
MirSurface::get_parameters(),
MirSurface::configure(),
MirSurface::attrib(),
MirSurface::handle_event() |
A surface creation spec can have multiple streams. The code currently, by happenstance, makes the first stream the "default stream", i.e. instantiates a MirSurface using that stream. The MirSurface object's methods then uses that stream for various purposes. E.g. to set the swap interval, to set size during resize, to query parameters of the Surface, etc. Here's a list of MirSurface methods that use the default stream :
MirSurface::get_parameters(),
MirSurface::configure(),
MirSurface::attrib(),
MirSurface::handle_event()
Seems like we need to define the semantics of MirBuffer properly in regards to the streams that may be associated with it. |
|
| 2016-05-06 15:42:33 |
Cemil Azizoglu |
description |
A surface creation spec can have multiple streams. The code currently, by happenstance, makes the first stream the "default stream", i.e. instantiates a MirSurface using that stream. The MirSurface object's methods then uses that stream for various purposes. E.g. to set the swap interval, to set size during resize, to query parameters of the Surface, etc. Here's a list of MirSurface methods that use the default stream :
MirSurface::get_parameters(),
MirSurface::configure(),
MirSurface::attrib(),
MirSurface::handle_event()
Seems like we need to define the semantics of MirBuffer properly in regards to the streams that may be associated with it. |
A surface creation spec can have multiple streams. The code currently, by happenstance, makes the first stream the "default stream", i.e. instantiates a MirSurface using that stream. The MirSurface object's methods then uses that stream for various purposes. E.g. to set the swap interval, to set size during resize, to query parameters of the Surface, etc. Here's a list of MirSurface methods that use the default stream :
MirSurface::get_parameters(),
MirSurface::configure(),
MirSurface::attrib(),
MirSurface::handle_event()
We need to define the precise semantics of MirBuffer properly in regards to the streams that may be associated with it. |
|
| 2016-05-06 15:42:48 |
Cemil Azizoglu |
mir: importance |
Undecided |
High |
|
| 2016-05-06 15:42:51 |
Cemil Azizoglu |
mir: milestone |
|
0.24.0 |
|
| 2016-05-06 15:44:23 |
Cemil Azizoglu |
description |
A surface creation spec can have multiple streams. The code currently, by happenstance, makes the first stream the "default stream", i.e. instantiates a MirSurface using that stream. The MirSurface object's methods then uses that stream for various purposes. E.g. to set the swap interval, to set size during resize, to query parameters of the Surface, etc. Here's a list of MirSurface methods that use the default stream :
MirSurface::get_parameters(),
MirSurface::configure(),
MirSurface::attrib(),
MirSurface::handle_event()
We need to define the precise semantics of MirBuffer properly in regards to the streams that may be associated with it. |
A surface creation spec can have multiple streams. The code currently, by happenstance, makes the first stream the "default stream", i.e. instantiates a MirSurface using that stream. The MirSurface object's methods then use that stream for various purposes, e.g. to set the swap interval, to set size during resize, to query parameters of the surface, etc. Here's a list of MirSurface methods that use the default stream :
MirSurface::get_parameters(),
MirSurface::configure(),
MirSurface::attrib(),
MirSurface::handle_event()
We need to define the precise semantics of MirSurface properly in regards to the streams that may be associated with it. |
|
| 2016-05-10 17:27:52 |
Kevin DuBois |
tags |
|
clientapi |
|
| 2016-05-10 18:01:58 |
Kevin DuBois |
mir: status |
New |
Confirmed |
|
| 2016-05-10 18:02:03 |
Kevin DuBois |
mir: status |
Confirmed |
In Progress |
|
| 2016-05-10 18:02:06 |
Kevin DuBois |
mir: assignee |
|
Kevin DuBois (kdub) |
|
| 2016-05-10 18:02:17 |
Kevin DuBois |
branch linked |
|
lp:~kdub/mir/fix-1577967 |
|
| 2016-06-08 18:06:28 |
Mir CI Bot |
mir: status |
In Progress |
Fix Committed |
|
| 2016-07-08 16:09:51 |
Launchpad Janitor |
branch linked |
|
lp:~ci-train-bot/mir/mir-ubuntu-yakkety-landing-036 |
|
| 2016-07-12 07:11:44 |
Daniel van Vugt |
bug task added |
|
mir (Ubuntu) |
|
| 2016-08-19 06:34:38 |
Jean-Baptiste Lallement |
bug task added |
|
canonical-devices-system-image |
|
| 2016-08-19 06:35:03 |
Jean-Baptiste Lallement |
canonical-devices-system-image: status |
New |
Fix Committed |
|
| 2016-08-19 06:35:06 |
Jean-Baptiste Lallement |
canonical-devices-system-image: importance |
Undecided |
High |
|
| 2016-08-19 06:35:12 |
Jean-Baptiste Lallement |
canonical-devices-system-image: milestone |
|
13 |
|
| 2016-08-20 03:01:55 |
Launchpad Janitor |
mir (Ubuntu): status |
New |
Fix Released |
|
| 2016-08-22 02:40:31 |
Daniel van Vugt |
mir: status |
Fix Committed |
Fix Released |
|
| 2016-09-20 21:09:16 |
Pat McGowan |
canonical-devices-system-image: status |
Fix Committed |
Fix Released |
|
| 2017-06-05 11:01:50 |
Launchpad Janitor |
branch linked |
|
lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736 |
|
