Re: [PATCH weston] launcher: don't exit when user is not root

On 31 October 2017 at 08:49, Pekka Paalanen <ppaala...@gmail.com> wrote: > On Mon, 30 Oct 2017 18:56:02 +0100 > Michal Suchanek <hramr...@gmail.com> wrote: > >> On 30 October 2017 at 16:02, Pekka Paalanen <ppaala...@gmail.com> wrote: >> > On Mon, 30

Re: [PATCH weston] launcher: don't exit when user is not root

On 30 October 2017 at 16:02, Pekka Paalanen wrote: > On Mon, 30 Oct 2017 15:20:42 +0100 > Emre Ucan wrote: > >> weston does not need to be root. >> It requires adjusting ownership on the given tty device. >> >> If weston does not have proper rights, it

Re: [RFC wayland-protocols v4] Add Primary Selection Protocol Version 1

On 24 February 2016 at 10:54, Jonas Ådahl <jad...@gmail.com> wrote: > On Wed, Feb 24, 2016 at 10:25:19AM +0100, Michal Suchanek wrote: >> On 24 February 2016 at 05:33, Jonas Ådahl <jad...@gmail.com> wrote: >> > On Sat, Feb 20, 2016 at 01:31:59AM +0100, Carlos Garnach

Re: [RFC wayland-protocols v4] Add Primary Selection Protocol Version 1

On 24 February 2016 at 05:33, Jonas Ådahl wrote: > On Sat, Feb 20, 2016 at 01:31:59AM +0100, Carlos Garnacho wrote: >> From: Lyude >> >> This primary selection is similar in spirit to the eponimous >> in X11, allowing a quick "select text + middle click"

Re: [RFC wayland-protocols v4] Add Primary Selection Protocol Version 1

On 23 February 2016 at 20:03, Bill Spitzak <spit...@gmail.com> wrote: > > > On Tue, Feb 23, 2016 at 1:32 AM, Michal Suchanek <hramr...@gmail.com> wrote: >> >> On 22 February 2016 at 19:23, Carlos Garnacho <carl...@gnome.org> wrote: >> >>

Re: [RFC wayland-protocols v4] Add Primary Selection Protocol Version 1

On 22 February 2016 at 19:23, Carlos Garnacho <carl...@gnome.org> wrote: > Hi Michal, > > On Mon, Feb 22, 2016 at 4:53 PM, Michal Suchanek <hramr...@gmail.com> wrote: >> On 22 February 2016 at 15:57, Carlos Garnacho <carl...@gnome.org> wrote: >>> Hi Micha

Re: [RFC wayland-protocols v4] Add Primary Selection Protocol Version 1

On 22 February 2016 at 15:57, Carlos Garnacho <carl...@gnome.org> wrote: > Hi Michal, > > On Mon, Feb 22, 2016 at 2:25 PM, Michal Suchanek <hramr...@gmail.com> wrote: >> Hello, >> >> On 20 February 2016 at 01:31, Carlos Garnacho <carl...@gnome.org> w

Re: [RFC wayland-protocols v4] Add Primary Selection Protocol Version 1

Hello, On 20 February 2016 at 01:31, Carlos Garnacho wrote: > + > + > +This protocol provides the ability to have a primary selection device to > +match that of the X server. This primary selection is a shortcut to the > +common clipboard selection, where text

Re: [PATCH wayland 2/2] protocol: Add DnD actions

Hello, On 14 January 2016 at 13:51, Jonas Ådahl <jad...@gmail.com> wrote: > On Thu, Jan 14, 2016 at 11:50:29AM +0100, Michal Suchanek wrote: >> On 14 January 2016 at 01:54, Carlos Garnacho <carl...@gnome.org> wrote: >> > Hi Michal, >> > >> >

Re: [PATCH wayland 2/2] protocol: Add DnD actions

On 14 January 2016 at 01:54, Carlos Garnacho <carl...@gnome.org> wrote: > Hi Michal, > > On Mon, Jan 11, 2016 at 11:34 AM, Michal Suchanek <hramr...@gmail.com> wrote: >> On 24 December 2015 at 01:58, Carlos Garnacho <carl...@gnome.org>

Re: [PATCH wayland 2/2] protocol: Add DnD actions

On 24 December 2015 at 01:58, Carlos Garnacho wrote: > @@ -757,6 +883,40 @@ > > > > + > + > + > + > + > +This is a bitmask of the available/preferred actions in a > +drag-and-drop operation. > + > +In the compositor,

Re: [RFC wayland-protocols V3] Add Primary Selection Protocol Version 1

On 7 January 2016 at 04:42, Jonas Ådahl wrote: > On Wed, Jan 06, 2016 at 09:50:36PM -0500, Lyude wrote: >> Signed-off-by: Lyude >> --- >> >> Notes: >> Changes since V2 >> * Bunch of grammatical/wording fixes from whot >> *

Re: [RFC v2] Add Primary Selection Protocol Version 1

Hello, On 5 January 2016 at 07:04, Bill Spitzak wrote: > On 01/04/2016 08:33 PM, Peter Hutterer wrote: > > Also it seems like you will send this on *every* middle click. Some > clients > require clicking the middle button a lot without pasting (it is very >

Re: [RFC v2] Add Primary Selection Protocol Version 1

On 18 December 2015 at 20:34, Bill Spitzak wrote: > > > On Fri, Dec 18, 2015 at 9:03 AM, Lyude wrote: >> >> Signed-off-by: Lyude >> --- >> Changes >> * Add new interfaces to replace reuse of

Re: [RFC v2] Add Primary Selection Protocol Version 1

On 18 December 2015 at 18:03, Lyude wrote: > Signed-off-by: Lyude > + > + > +Sent when the client has permission to read from the primary > selection > +buffer. > + > +This event is sent whenever the client receives a middle

Re: RFC: idle protocol

On 9 December 2015 at 08:12, Martin Graesslin wrote: > On Tuesday, December 8, 2015 2:59:38 PM CET Bryce Harrington wrote: >> On Tue, Dec 08, 2015 at 02:12:01PM +0100, Martin Graesslin wrote: >> > Hi Wayland-developers, >> > >> > at KDE we developed a protocol for our

Re: [RFC wayland-protocols v2] Add screensaver inhibition protocol

On 25 November 2015 at 08:24, Bryce Harrington <br...@osg.samsung.com> wrote: > On Wed, Nov 25, 2015 at 08:09:16AM +0100, Michal Suchanek wrote: >> Hello >> >> On 25 November 2015 at 07:49, Bryce Harrington <br...@osg.samsung.com> wrote: >> > This

Re: [RFC wayland-protocols v2] Add screensaver inhibition protocol

Hello On 25 November 2015 at 07:49, Bryce Harrington wrote: > This interface allows disabling of screensaver/screenblanking on a > per-surface basis. As long as the surface remains visible and > non-occluded it blocks the screensaver, etc. from activating on the >

Re: [RFC] Screensaver/blanking inhibition

On 20 November 2015 at 12:48, Pekka Paalanen <ppaala...@gmail.com> wrote: > On Fri, 20 Nov 2015 12:18:29 +0100 > Michal Suchanek <hramr...@gmail.com> wrote: > >> On 20 November 2015 at 11:39, Pekka Paalanen <ppaala...@gmail.com> wrote: >> > On Thu, 19 No

Re: [RFC] Screensaver/blanking inhibition

On 20 November 2015 at 14:43, Pekka Paalanen <ppaala...@gmail.com> wrote: > On Fri, 20 Nov 2015 14:10:47 +0100 > Michal Suchanek <hramr...@gmail.com> wrote: > >> On 20 November 2015 at 12:48, Pekka Paalanen <ppaala...@gmail.com> wrote: >> > On Fri, 20 No

Re: [RFC] Screensaver/blanking inhibition

On 20 November 2015 at 11:39, Pekka Paalanen <ppaala...@gmail.com> wrote: > On Thu, 19 Nov 2015 22:46:06 +0100 > Michal Suchanek <hramr...@gmail.com> wrote: > >> On 19 November 2015 at 20:12, Daniel Stone <dan...@fooishbar.org> wrote: >> > Hi, >> &

Re: [RFC] Screensaver/blanking inhibition

On 19 November 2015 at 20:12, Daniel Stone wrote: > Hi, > > On 19 November 2015 at 19:05, Bill Spitzak wrote: >> I feel like there is no need to tie it to a surface. In Wayland the client >> is always notified of any changes to it's state, so it can

Re: Xwayland and weston’s scale=2 (hi-dpi display)

DPI is read from the X server, not Xresources. You can probably adjust DPI by the scale factor in X emulation, Or not scale emulated X windows as suggested. Thanks Michal On 9 November 2015 at 19:42, Bill Spitzak wrote: > Have the X emulator assume the client set the scale

Re: [RFC] weston: implement inert objects for keyboard/pointer/touch

Hello, On 19 October 2015 at 15:47, David FORT wrote: > This is the second version. I have restored the ref counting of input devices, > I think with the name weston_seat_init_pointer is not accurate, perhaps > weston_seat_add_pointer_device would be better. I'm really

Re: Wayland Relative Pointer API Progress

On 20 April 2015 at 13:44, x414e54 x414...@linux.com wrote: This is kinda completely derailed from the whole include mice in the game controller protocol talk. On Mon, Apr 20, 2015 at 6:44 PM, Michal Suchanek hramr...@gmail.com wrote: On 20 April 2015 at 10:48, Pekka Paalanen ppaala

Re: Wayland Relative Pointer API Progress

On 20 April 2015 at 14:49, x414e54 x414...@linux.com wrote: There is no sense in saying the sensor reading itself as absolute or relative. Either gives you some number in unknown units which you calibrate to get usable results. You have no idea where the stick is from the numbers you get. And

Re: Wayland Relative Pointer API Progress

On 20 April 2015 at 10:48, Pekka Paalanen ppaala...@gmail.com wrote: On Mon, 20 Apr 2015 10:13:34 +0200 Michal Suchanek hramr...@gmail.com wrote: On 20 April 2015 at 09:36, Pekka Paalanen ppaala...@gmail.com wrote: On Sun, 19 Apr 2015 09:46:39 +0200 Michal Suchanek hramr...@gmail.com wrote

Re: Wayland Relative Pointer API Progress

is in another email. Sounds like it is specifically not a HID pointer device. On Sun, 19 Apr 2015 09:46:39 +0200 Michal Suchanek hramr...@gmail.com wrote: So the device is always absolute and interpretation varies. I disagree. Let's take a mouse, optical or ball, doesn't matter. What you get

Re: Wayland Relative Pointer API Progress

On 19 April 2015 at 06:15, x414e54 x414...@linux.com wrote: On Sun, Apr 19, 2015 at 12:45 AM, Michal Suchanek hramr...@gmail.com wrote: On 18 April 2015 at 16:58, x414e54 x414...@linux.com wrote: A joystick does not necessarily have 2 axis and in most cases yes they are reporting

Re: Wayland Relative Pointer API Progress

On 17 April 2015 at 12:52, Hans de Goede hdego...@redhat.com wrote: Hi, On 17-04-15 11:47, Michal Suchanek wrote: On 17 April 2015 at 09:11, Pekka Paalanen ppaala...@gmail.com wrote: On Fri, 17 Apr 2015 13:43:11 +0900 x414e54 x414...@linux.com wrote: Thank you for the comments. I do

Re: Wayland Relative Pointer API Progress

On 18 April 2015 at 16:58, x414e54 x414...@linux.com wrote: Hi, then actually mice are absolute not relative. They have two axis that measure absolute ball rotation speed in two directions just like joystick has two axis that measure absolute stick excentricity. Thanks Michal This is

Re: Compositor grabs (was: Re: [PATCH] protocol: Add DnD actions)

On 17 April 2015 at 23:40, Bill Spitzak spit...@gmail.com wrote: On 04/17/2015 05:16 AM, Carlos Garnacho wrote: Let's expand on that example, maybe far-streched, but certainly possible: - I'm manipulating a client window with 2 fingers on the touchscreen (say zooming an image) - Any other

Re: Wayland Relative Pointer API Progress

On 17 April 2015 at 09:11, Pekka Paalanen ppaala...@gmail.com wrote: On Fri, 17 Apr 2015 13:43:11 +0900 x414e54 x414...@linux.com wrote: Thank you for the comments. I do have a few counterpoints but I will leave after that. Not sure an IR/laser/wii mote pointer should even be considered

Re: Wayland Relative Pointer API Progress

On 17 April 2015 at 12:52, Hans de Goede hdego...@redhat.com wrote: Hi, On 17-04-15 11:47, Michal Suchanek wrote: On 17 April 2015 at 09:11, Pekka Paalanen ppaala...@gmail.com wrote: On Fri, 17 Apr 2015 13:43:11 +0900 x414e54 x414...@linux.com wrote: Thank you for the comments. I do

Re: Compositor grabs (was: Re: [PATCH] protocol: Add DnD actions)

On 17 April 2015 at 14:16, Carlos Garnacho carl...@gnome.org wrote: Hey Jonas, This is drifting a bit off the topic of the original thread, better to spin this off. I'll reply to the DnD bits in another email. On Fri, Apr 17, 2015 at 9:50 AM, Jonas Ådahl jad...@gmail.com wrote: On Thu, Apr

Re: Wayland Relative Pointer API Progress

On 17 April 2015 at 14:37, Hans de Goede hdego...@redhat.com wrote: Hi, On 17-04-15 13:17, Michal Suchanek wrote: On 17 April 2015 at 12:52, Hans de Goede hdego...@redhat.com wrote: Hi, On 17-04-15 11:47, Michal Suchanek wrote: On 17 April 2015 at 09:11, Pekka Paalanen ppaala

Re: Compositor grabs (was: Re: [PATCH] protocol: Add DnD actions)

On 17 April 2015 at 16:15, Carlos Garnacho carl...@gnome.org wrote: Hey Michal, On Fri, Apr 17, 2015 at 2:47 PM, Michal Suchanek hramr...@gmail.com wrote: snip In the X11 world, this would roughly be a Virtual Core Pointer+Keyboard grab (not that touch and active grabs are trouble free

Re: Compositor grabs (was: Re: [PATCH] protocol: Add DnD actions)

On 17 April 2015 at 14:16, Carlos Garnacho carl...@gnome.org wrote: Hey Jonas, This is drifting a bit off the topic of the original thread, better to spin this off. I'll reply to the DnD bits in another email. On Fri, Apr 17, 2015 at 9:50 AM, Jonas Ådahl jad...@gmail.com wrote: On Thu, Apr

Re: libinput: the road to 1.0

Hello, I heard there is attempt to collect a database of mouse speeds (DPI) so all mice behave the same. What is the semantic of speed for trackballs? Technically the DPI of scanning the ball movement can be determined and is often part of the specification but the perceived speed will likely

Re: X11 weston lockup

Hello On 9 February 2015 at 19:02, Daniel Stone dan...@fooishbar.org wrote: Hi, On 9 February 2015 at 13:23, Michal Suchanek hramr...@gmail.com wrote: I don't see any indication of dri3 being used or not in the weston output It's entirely silent in Weston because it's just an EGL

Re: X11 weston lockup

On 9 February 2015 at 20:37, Daniel Stone dan...@fooishbar.org wrote: Hi, On 9 February 2015 at 19:16, Michal Suchanek hramr...@gmail.com wrote: On 9 February 2015 at 19:02, Daniel Stone dan...@fooishbar.org wrote: On 9 February 2015 at 13:23, Michal Suchanek hramr...@gmail.com wrote: I

Re: X11 weston lockup

On 9 February 2015 at 12:35, Michal Suchanek hramr...@gmail.com wrote: Hello, I am running X11 on an AMD Redwood card with XMonad window manager and xcompmgr. Actually, I forgot I replaced the graphics card: Date: 2015-02-09 CET [12:15:49.609] weston 1.6.0 http

X11 weston lockup

Hello, I am running X11 on an AMD Redwood card with XMonad window manager and xcompmgr. I tried to run weston under X and noticed that cursor updates are very sluggish. After a while any updates in the weston window stopped completely (eg. cursor does not move, clock shows old time). Is there

Re: X11 weston lockup

On 9 February 2015 at 12:44, Daniel Stone dan...@fooishbar.org wrote: Hi, On 9 February 2015 at 11:37, Michal Suchanek hramr...@gmail.com wrote: On 9 February 2015 at 12:35, Michal Suchanek hramr...@gmail.com wrote: I tried to run weston under X and noticed that cursor updates are very

Re: Wayland on Beagle board

2011/10/1 Üstün Ergenoglu ustun.ergeno...@gmail.com: Recently, there have been talks about SGX drivers adding support for Wayland. I was googling around but couldn't find any specific build instructions for omap3. I currently have a Beagle board running Ubuntu 10.10. I'll be glad to hear if

Re: Window stacking

On 16 September 2011 11:18, Giovanni Campagna scampa.giova...@gmail.com wrote: Sorry, I also assume any task manager will just be part of the compositor process. The problem is that the user of the task manager probably wants an icon in there that says GIMP even though there are perhaps 2

Re: seprate window management component

Hello, On 14 September 2011 16:55, cat zixo...@gmail.com wrote: would it be to much trouble to make window management a proxy program? The wayland server has to know how the windows stack but the clients are not trusted to tell it how the windows should stack so either the server has to figure

Re: Xft and XCursor

On 17 June 2011 10:29, Lukas Sommer sommer...@gmail.com wrote: Hello. About Wayland I have the following questions: When we run, in some future, a Wayland-only session, how will Wayland-enabled applications behave in the following things: - Xft: How to retrieve the font DPI setting and how

Re: Wayland Window Management Proposal

On 16 May 2011 23:13, Bill Spitzak spit...@gmail.com wrote: Michal Suchanek wrote: The thing is that in Wayland the server is not aware of any remote vs local windows. Remote applications are in no way part of the protocol and will supposedly sneak in later by means of some remoting proxy

Re: Wayland Window Management Proposal

On 16 May 2011 16:17, Solerman Kaplon soler...@gmail.com wrote: Em 13-05-2011 15:38, Michal Suchanek escreveu: If the client takes, say, half a second to update which is completely reasonable for a full re-layout and repaint of a window that normally gets only partial updates then the resize

Re: Wayland Window Management Proposal

On 13 May 2011 11:26, Daniel Stone dan...@fooishbar.org wrote: On Thu, May 12, 2011 at 06:22:01PM +0200, Michal Suchanek wrote: You can't expect that every single client is high-priority and lag-free. Run better clients, then? Or stop trying to micro-optimise for the case of pressing

Re: Wayland Window Management Proposal

On 13 May 2011 19:45, Corbin Simpson mostawesomed...@gmail.com wrote: I was trying to stay out of this, but... On Fri, May 13, 2011 at 9:03 AM, Michal Suchanek hramr...@centrum.cz wrote: This is *not* *about* *optimization*.  If you rely on *every* *single* *client* to be responsive for your

Re: Wayland Window Management Proposal

2011/5/13 Rui Tiago Cação Matos tiagoma...@gmail.com: On 13 May 2011 18:59, Mike Paquette paquette...@gmail.com wrote: Completely agree. The compositor/WM has no business in working around application bugs. If application programmers are lazy and can't get their windows acting timely on input

Re: Wayland Window Management Proposal

On 13 May 2011 22:14, Elijah Insua tmp...@gmail.com wrote: On May 13, 2011, at 4:02 PM, Casey Dahlin wrote: On Fri, May 13, 2011 at 03:13:01PM +0200, Michal Suchanek wrote: On 13 May 2011 11:26, Daniel Stone dan...@fooishbar.org wrote: On Thu, May 12, 2011 at 06:22:01PM +0200, Michal

Re: Wayland Window Management Proposal

On 11 May 2011 20:25, Bill Spitzak spit...@gmail.com wrote: Michal Suchanek wrote: Moves and resizes implemented in the client can't work well. Any resize solution that does not allow an atomic on-screen update of a window to it's new size, with the resized decorations and contents

Re: client side decorations

On 12 May 2011 19:47, Bill Spitzak spit...@gmail.com wrote: microcai wrote: They can't care how big a windows is in the pixel, but in the inch. People should have different monitors with different DPI. Windows should stay same size regardless the DPI. Force DPI==96 on every monitor is a

Re: client side decorations

On 10 May 2011 05:46, Russell Shaw rjs...@netspace.net.au wrote: On 10/05/11 07:29, Daniel wrote: El dg 08 de 05 de 2011 a les 09:47 -0700, en/na Bill Spitzak va escriure: Though it is possible, I don't like the idea of clients sending hints about what areas are the close box or window

Re: wayland screen locker and security in general

On 12 April 2011 21:04, Iskren Chernev iskren.cher...@gmail.com wrote: I don't think this lengthy discussion led to any concrete answers, but I do think that the questions are important and need such answers. I'll try to summarize the problems that need attention: 1. screen locking 1.1 who is

Re: wayland screen locker and security in general

On 7 April 2011 02:00, cat zixo...@gmail.com wrote: On Wed, Apr 6, 2011 at 11:57 AM, Michal Suchanek hramr...@centrum.cz wrote: On 6 April 2011 18:34, Jerome Glisse j.gli...@gmail.com wrote: 2011/4/6 Michal Suchanek hramr...@centrum.cz: 2011/4/5 Kristian Høgsberg k...@bitplanet.net

Re: wayland screen locker and security in general

2011/4/7 Corbin Simpson mostawesomed...@gmail.com: 2011/4/7 Michal Suchanek hramr...@centrum.cz: If you have some input on awesomeness of dbus which I miss I am all ears but so far nobody could point out any advantage to me when this topic came to the table. Sure, dbus likely includes

Re: HPC (High Performance Compute) Architecture

On 18 March 2011 04:14, Trevour Crow cro...@yahoo.com wrote: From: Josh Leverette coder...@gmail.com Subject: Re: HPC (High Performance Compute) Architecture To: jonsm...@gmail.com jonsm...@gmail.com Cc: wayland-devel@lists.freedesktop.org wayland-devel@lists.freedesktop.org Date: Thursday,

subpixel rendering in wayland?

Hello, I was just wondering about subpixel rendering and how is that going do be done in Wayland. In X an application is supposed to ask xrandr about current screen layout, determine on what screen(s) the window is placed, and use the subpixel order and screen rotation information to figure out