Re: [PATCH weston] tests: make signal other than ABRT a hard failure

On Thu, 24 Jan 2013 16:24:14 -0500 Kristian Høgsberg wrote: > On Tue, Dec 18, 2012 at 05:30:16PM +0200, Pekka Paalanen wrote: > > We handle FAIL_TEST tests by simply inverting the success flag. The > > problem with this is, that if a FAIL_TEST fails by a SIGSEGV, it will be > > interpreted as pas

Re: Issues with running Xclient using xwayland.

Hello Bill, Thanks for sending the patch. But after using it, my crash had no effect its still failing with the same log and at same place. I guess the problem is not what you had thought? Any other clues? Ill dig up more at my end in the meanwhile. Thanks for helping Regards, Ashish On Fri, J

Wayland and Weston 1.0.4 releases are out

Hi all, Here are the 1.0.4 release, a week later than promised: 2f65654a54366cacd39a69bc5a41fea21b357e34 wayland-1.0.4.tar.xz 9ebb18418a1c3dccc19d3931766240b54227f131 wayland 1.0.4 tag 6f51fe78151ba2854f6cf6a41244c34f39c1d6de weston-1.0.4.tar.xz e4cd90e6bd5ac72a40d87f7da2cd1fd

Patch queue + signs of life

Hi, I'm still here, I've just been sick for almost a week and am now starting to get back on my feet (and back to the keyboard). I had a pass over the patches on the list and there was a lot of good work there, and even better, a lot of the patches have already gone through a few rounds of good r

Re: [PATCH v3] Weston: weston.ini.man page

On Fri, Jan 18, 2013 at 06:44:29PM +0100, Martin Minarik wrote: > changes: > - launcher path, passing environment variables and parameter > - indent modeline example Thanks Martin, this looks good now, thanks to everybody who reviewd, committed. Scott had a few comments about the output example

Re: Issues with running Xclient using xwayland.

On 25 January 2013 07:17, Bill Spitzak wrote: > ashjas wrote: > > Thanks Bill for that info.. after searching for your patch i found this > > discussion of what you indicated.. but i couldnot find the patch that > > you mentioned.. > > http://lists.freedesktop.org/**archives/wayland-devel/2012-**

Re: [PATCH weston 0/7] Pixman renderer support for the drm backend

On Tue, Jan 22, 2013 at 06:07:08PM +0200, Ander Conselvan de Oliveira wrote: > Hi, > > This series adds pixman support to the compositor backend. The bulk of > the series consists of recfactoring that backend to make the backend > choice implemented on the last patch easier. This series looks goo

Re: [PATCH v3] fbdev: Add an fbdev compositor backend using pixman and evdev

On Wed, Jan 23, 2013 at 10:33:28AM +0200, Pekka Paalanen wrote: > Hi Philip, > > I still didn't test this, but it looks good. I have some minor comments > inline below. If we can address Pekkas comments below, I think we're ready to commit this. I second the nitpick about using $(NULL), we've no

Re: [PATCH weston] clients: add global_remove handler stubs

On Tue, Jan 22, 2013 at 02:53:55PM +0200, Pekka Paalanen wrote: > All the clients here were missing the global_remove handler. Because > window.c did not have it, weston-desktop-shell and weston-keyboard > segfaulted on compositor exit, as they received some > wl_registry.global_remove events. > >

Re: [PATCH weston] weston-launch: Use "weston-launch" for --help instead of "weston".

On Mon, Jan 21, 2013 at 11:40:59PM -0700, Scott Moreau wrote: > The output of weston-launch --help was "Usage: weston [args...] ...". > This changes it to read "Usage: weston-launch [args...] ...". Thanks, that's better. Committed. Kristian > --- > src/weston-launch.c |2 +- > 1 file chang

Re: [PATCH weston 1/2] compositor: remove android backend

On Fri, Jan 18, 2013 at 12:11:09PM +0200, Pekka Paalanen wrote: > The Android backend has been fairly unused, since we do not have > projects actively using it. It gets basic build testing as part of the > normal build, but runtime testing it takes a considerable effort, and so > I have not done th

Re: [PATCH weston] tests: make signal other than ABRT a hard failure

On Tue, Dec 18, 2012 at 05:30:16PM +0200, Pekka Paalanen wrote: > We handle FAIL_TEST tests by simply inverting the success flag. The > problem with this is, that if a FAIL_TEST fails by a SIGSEGV, it will be > interpreted as passed. However, no code should ever cause a SEGV, or any > other signal

Re: [PATCH wayland] gitignore: add test-suite files

On Wed, Jan 23, 2013 at 02:20:41PM +0100, David Herrmann wrote: > The *.log and *.trs files should be ignored by git as well as the GNU > autotools ./test-driver helper script. Thanks, committed. > Signed-off-by: David Herrmann > --- > .gitignore | 1 + > tests/.gitignore | 7 ++- > 2

Re: [PATCH] event-loop: fix returning the destroy-signal listener

On Wed, Jan 23, 2013 at 02:11:19PM +0100, David Herrmann wrote: > We need to actually return the destroy-listener, otherwise the return > value is undefined. Thanks David, I should've caught that. Committed. Kristian > Signed-off-by: David Herrmann > --- > src/event-loop.c | 2 +- > 1 file ch

Re: Issues with running Xclient using xwayland.

ashjas wrote: > Thanks Bill for that info.. after searching for your patch i found this > discussion of what you indicated.. but i couldnot find the patch that > you mentioned.. > http://lists.freedesktop.org/archives/wayland-devel/2012-September/005203.html > > can you give me some pointers? >

Re: [PATCH] wlt_toolkit.c: Fix resize window stuck in need_resize=true

Hi Martin On Thu, Jan 24, 2013 at 4:48 PM, Martin Minarik wrote: > The problem is that: > wnd->w_frame contains a number > and > wnd->need_frame=true > Therefore schedule_frame() doesn't schedule the callback. > But deleting these checks causes flicker. Further redesign > of the frame sheduling

[PATCH] wlt_toolkit.c: Fix resize window stuck in need_resize=true

The problem is that: wnd->w_frame contains a number and wnd->need_frame=true Therefore schedule_frame() doesn't schedule the callback. But deleting these checks causes flicker. Further redesign of the frame sheduling was necessary. 4. frame_callback() 3. do_frame() 3. idle_frame() 2. schedule_fr