This makes it possible to run Weston session from GDM (and possibly
other login managers).
---
Makefile.am| 5 +
src/weston.desktop | 5 +
2 files changed, 10 insertions(+)
create mode 100644 src/weston.desktop
diff --git a/Makefile.am b/Makefile.am
index 3a37be0..b10d6bf 100644
damage(0, 0, 750, 515)
Signed-off-by: Lubomir Rintel
---
Changes to v2:
- Added listener instead of checking the buffer mapping,
as suggested by Pekka Paalanen
- Added more context to the commit message
Changes to v3:
- Removed unnecessary buffer unreferences and signal handler unhook
On Wed, 2013-12-04 at 11:54 -0800, Kristian Høgsberg wrote:
> On Wed, Dec 04, 2013 at 08:31:37AM +0100, Lubomir Rintel wrote:
> > While the pixman image might be attached, the underlying buffer might be
> > already gone under certain circumstances. This is easily reproduced by
&g
damage(0, 0, 750, 515)
Signed-off-by: Lubomir Rintel
---
Thank you for your responses, Kristian & Pekka.
Hopefully it's correct now.
Changes to v2:
- Added listener instead of checking the buffer mapping,
as suggested by Pekka Paalanen
- Added more context to the commit messag
On Mon, 2013-12-02 at 15:53 -0800, Kristian Høgsberg wrote:
> On Sat, Nov 30, 2013 at 03:41:00PM +0100, Lubomir Rintel wrote:
> > While the pixman image might be attached, the underlying buffer might be
> > already gone under certain circumstances. This is easily reproduced by
&g
damage(0, 0, 750, 515)
Signed-off-by: Lubomir Rintel
---
Hi,
This has been previously discussed in this thread:
http://lists.freedesktop.org/archives/wayland-devel/2013-November/012122.html
Pekka doesn't mind, Arnaud's suggestion does not seem doable.
Please let me know if there'
p track of the
surface it's attached to -- it's not possible to determine the surface
in weston_buffer_destroy_handler().
> Is there a case where a renderer wouldn't want this to be done ?
>
>
> On Thu, Nov 21, 2013 at 8:35 AM, Pekka Paalanen
> wrote:
>
damage(0, 0, 750, 515)
Signed-off-by: Lubomir Rintel
---
Changes to v2:
- Added listener instead of checking the buffer mapping,
as suggested by Pekka Paalanen
- Added more context to the commit message
Changes to v3:
- Removed unnecessary buffer unreferences and signal handler unhook
damage(0, 0, 750, 515)
Signed-off-by: Lubomir Rintel
---
Changes to v2:
- Added listener instead of checking the buffer mapping,
as suggested by Pekka Paalanen
- Added more context to the commit message
src/pixman-renderer.c | 25 +
1 file changed, 25 inse
49.425] wl_surface@14.attach(wl_buffer@27, 0, 0)
[1524849.730] wl_surface@14.set_buffer_scale(1)
[1524849.821] wl_surface@14.damage(0, 0, 750, 515)
Signed-off-by: Lubomir Rintel
---
A Perl-based reproducer available here, in case it is more convenient to run
than gnome-terminal: http://v3.sk/~lk
Hi,
I've just uploaded pure Perl bindings for Wayland to CPAN:
http://search.cpan.org/~lkundrak/WL-0.9/lib/WL.pm
You might find it useful for quick prototyping, etc.
Have a great day!
Lubo
___
wayland-devel mailing list
wayland-devel@lists.freedesktop
Otherwise the tail of fds_in buffer would just shift beyond the beginning.
That confuses the actual request handler and results in a crash further on
due to corrupted tail.
Signed-off-by: Lubomir Rintel
---
Changes since v1:
Erroring out early instead of calling the request handler with
This allows specifying a particular backend to load in a manner similar to
modules.
Signed-off-by: Lubomir Rintel
---
man/weston.ini.man | 17 +
src/compositor.c | 24 +++-
2 files changed, 32 insertions(+), 9 deletions(-)
diff --git a/man/weston.ini.man b
It would be possible to make the compositor leak file descriptors by
passing descriptors of open unmmapable files to it, such as /dev/null.
Signed-off-by: Lubomir Rintel
---
src/wayland-shm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/wayland-shm.c b/src/wayland
received via anciliary
data.
Signed-off-by: Lubomir Rintel
---
src/connection.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/src/connection.c b/src/connection.c
index 451b93e..48a5398 100644
--- a/src/connection.c
+++ b/src/connection.c
@@ -605,7 +605,7
This is just for the sake of cleanliness and correct error handling.
Without this the mmap would fail emitting an error message about failed
mapping to the client and a close of bogus file descriptor would be
attempted, which is harmless since it can not fail.
Signed-off-by: Lubomir Rintel
16 matches
Mail list logo