The screensaver duration from weston.ini is not taking
effect, the default idletime that is hardcoded is the
what kicks the idle_handler and locks the screen. It
is hardcoded to 300 seconds. This change makes
screensaver configurable from the ini file.
Signed-off-by: Karthik Ramanan
---
src/shel
The screensaver duration from weston.ini is not taking
effect, the default idletime that is hardcoded is the
what kicks the idle_handler and locks the screen. It
is hardcoded to 300 seconds. This change makes
screensaver configurable from the ini file.
Signed-off-by: Karthik Ramanan
---
src/shel
On Fri, Nov 15, 2013 at 02:02:23AM -0800, Dima Ryazanov wrote:
> This fixes crashes caused by popup windows that don't have override_redirect
> (e.g., menus in VLC and KDE apps), though I don't know if this is correct.
>
> Signed-off-by: Dima Ryazanov
> ---
> src/xwayland/window-manager.c | 4 ++
On Sat, Nov 16, 2013 at 02:31:03PM +0100, Lubomir Rintel wrote:
> 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 sinc
On Thu, Nov 21, 2013 at 04:47:02PM +0200, ppaala...@gmail.com wrote:
> From: Pekka Paalanen
>
> This tests the wl_shm buffer access wrappers, that are supposed to catch
> the invalid accesses to a memory-mapped file beyond EOF.
>
> Signed-off-by: Pekka Paalanen
> ---
>
> v2: call it bad-buffer
On Thu, Nov 21, 2013 at 04:23:56PM +0200, ppaala...@gmail.com wrote:
> From: Pekka Paalanen
>
> This tests the wl_shm buffer access wrappers, that are supposed to catch
> the invalid accesses to a memory-mapped file beyond EOF.
Good testcase, thanks. All three patches applied.
Kristian
> Sign
On Thu, Nov 21, 2013 at 04:23:57PM +0200, ppaala...@gmail.com wrote:
> From: Pekka Paalanen
>
> If the environment variable WESTON_TEST_CLIENT_PATH is not set, do not
> quit Weston in the test plugin.
>
> This allows one to start Weston with the test plugin manually, and then
> run any tests als
On Thu, Nov 21, 2013 at 08:40:42AM +0100, David Herrmann wrote:
> Hi
>
> On Thu, Nov 21, 2013 at 1:39 AM, Kristian Høgsberg wrote:
> > The gcc built-in 'bool' type is not the same size as dbus_bool_t, which is
> > an uint32_t. Passing a pointer to bool where dbus expects a uint32_t *
> > doesn't
Kristian,
Over-all i think it looks good. I do have a few thoughts:
1) Do we want to deprecate wl_proxy_create and make a note about the race
so we throw warnings in case people (Qt) are doing things themselves?
2) Do we want to add a flag to use the old version on the chance that
someone wants to
---
src/compositor.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/src/compositor.c b/src/compositor.c
index c14ec1f..f14b487 100644
--- a/src/compositor.c
+++ b/src/compositor.c
@@ -2063,6 +2063,16 @@ surface_set_buffer_transform(struct wl_client *client,
{
stru
---
protocol/wayland.xml | 15 +++
1 file changed, 15 insertions(+)
diff --git a/protocol/wayland.xml b/protocol/wayland.xml
index a9c8e53..07cd2b1 100644
--- a/protocol/wayland.xml
+++ b/protocol/wayland.xml
@@ -979,6 +979,14 @@
cursor images for pointers, drag icons, etc.
This already happens in weston.
---
protocol/wayland.xml | 5 +
1 file changed, 5 insertions(+)
diff --git a/protocol/wayland.xml b/protocol/wayland.xml
index 61fde84..a9c8e53 100644
--- a/protocol/wayland.xml
+++ b/protocol/wayland.xml
@@ -220,6 +220,11 @@
A buffer will keep a refere
Hi,
On 21 November 2013 14:23, wrote:
> weston_tests = \
> + bad_client.weston \
> keyboard.weston \
> event.weston\
> button.weston \
I think this would be much better cal
From: Pekka Paalanen
This tests the wl_shm buffer access wrappers, that are supposed to catch
the invalid accesses to a memory-mapped file beyond EOF.
Signed-off-by: Pekka Paalanen
---
v2: call it bad-buffer instead
---
tests/Makefile.am | 4 +++
tests/bad-buffer-test.c | 77 ++
From: Pekka Paalanen
If the environment variable WESTON_TEST_CLIENT_PATH is not set, do not
quit Weston in the test plugin.
This allows one to start Weston with the test plugin manually, and then
run any tests also manually, while observing Weston's behaviour over
time. This is useful for:
- Run
From: Pekka Paalanen
---
tests/.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/tests/.gitignore b/tests/.gitignore
index fbeeed9..32a6492 100644
--- a/tests/.gitignore
+++ b/tests/.gitignore
@@ -1,3 +1,4 @@
+*.log
*.test
*.trs
*.weston
--
1.8.1.5
_
From: Pekka Paalanen
This tests the wl_shm buffer access wrappers, that are supposed to catch
the invalid accesses to a memory-mapped file beyond EOF.
Signed-off-by: Pekka Paalanen
---
tests/Makefile.am | 4 +++
tests/bad-client-test.c | 77 ++
Version 2 of the patch, I split the asserts.
Marek Ch (1):
tests: fix compiler warnings and remove trailing whitespace
tests/connection-test.c | 24 +++-
1 file changed, 19 insertions(+), 5 deletions(-)
--
1.8.4.2
___
wayland-d
Fix 'unused variable' and 'missing initializer' warnings and
remove trailing whitespaces in connection-test
---
tests/connection-test.c | 24 +++-
1 file changed, 19 insertions(+), 5 deletions(-)
diff --git a/tests/connection-test.c b/tests/connection-test.c
index e284ea0..9f9
Hi,
Very noob question maybe but, what is the status for wayland for :
- freebsd
- set as default instead of X
- run some window manager + luncher to start things.
Example: http://www.youtube.com/watch?v=FZJrCt9e7To#t=32
Meaning it seems to be as default here and it has some windowing... silly
but
Set errno and return -1 in public API calls like all other weston code
does. Most systemd+dbus calls return negative error-codes instead of -1
and setting errno. Thus, we need to explicitly set errno before returning.
Also note that we must set errno _after_ the cleanup path. Calling
functions lik
21 matches
Mail list logo
