Re: [PATCH xserver v3] xwayland: Fix use after free of cursors

Hi, > > Sometimes, Xwayland will try to use a cursor that has just been freed, > > leading to a crash when trying to access that cursor data either in > > miPointerUpdateSprite() or AnimCurTimerNotify(). > > > > CheckMotion() updates the pointer's cursor based on which xwindow > > XYToWindow()

raspian, jessie full install on a raspi 3b, mouse in heavy syrup.

Greetings all; I've no clue if any of you are familar with raspian, built for the armhf SBC's.. I just installed it, and I am pleasantly surprised, it does almost everything well, except: When the mouse is moved, there is a huge lag, taking a fat second to move the pointer to the new

Re: Question about X on the arm's.

On Tuesday 29 November 2016 03:39:51 Thomas Lübking wrote: > On Mon, Nov 28, 2016 at 11:59:26PM -0500, Gene Heskett wrote: > >root 797 0.0 1.9 271380 33600 tty7 Ssl+ 20:50 > >0:02 /usr/lib/xorg/Xorg -core :0 -seat > >seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch >

[Bug 94811] ATI radeon driver displays nothing or a client refused to switch message on hybrid graphics

https://bugs.freedesktop.org/show_bug.cgi?id=94811 Michel Dänzer changed: What|Removed |Added Resolution|--- |NOTABUG

Re: Question about X on the arm's.

On Mon, Nov 28, 2016 at 11:59:26PM -0500, Gene Heskett wrote: root 797 0.0 1.9 271380 33600 tty7 Ssl+ 20:50 0:02 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch gene 4114 0.0 0.0 5564 908 pts/8S+ 23:48 0:00

[ANNOUNCE] libdrm 2.4.74

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ben Widawsky (1): intel: Add Geminilake PCI IDs Christian Gmeiner (4): etnaviv: add API to get drm fd from etna_device etnaviv: add API to create etna_device from private dup() fd etnaviv: change get_abs_timeout(..) to use

Re: XOpenDisplay call sequence

On 11/28/2016 01:31 PM, Krzywicki, Alan wrote: > > So if I follow the XOpenDisplay sequence up the stack I see > xcb_connect() / _/xcb_open/_abstract( ) trying to open > “/tmp/.X11-unix/X0” with protocol set to 0. On one system it > eventually calls select(), on another it uses poll() instead,

Re: Question about X on the arm's.

On Tuesday 29 November 2016 13:48:07 Antoine Martin wrote: > On 29/11/16 18:52, Gene Heskett wrote: > > On Tuesday 29 November 2016 04:18:09 Antoine Martin wrote: > >> If you exclude the 4k fullscreen video use case - which is a > >> worst case scenario for remote display (there are

Re: Question about X on the arm's.

On 29/11/16 18:52, Gene Heskett wrote: > On Tuesday 29 November 2016 04:18:09 Antoine Martin wrote: > >> If you exclude the 4k fullscreen video use case - which is a >> worst case scenario for remote display (there are tricks to deal >> with that too if you are willing to make

Re: Question about X on the arm's.

On 11/29/16 12:35 AM, Antoine Martin wrote: On 29/11/16 14:40, Alan Coopersmith wrote: On 11/28/16 07:58 PM, Antoine Martin wrote: Even 100mbit is perfectly usable for remote access provided you use the right tools and make some sacrifices. FYI: 4K@60 "fits" in H264 ~60Mbps. But again, as I

Re: Question about X on the arm's.

On Tuesday 29 November 2016 04:18:09 Antoine Martin wrote: > If you exclude the 4k fullscreen video use case - which is a > worst case scenario for remote display (there are tricks to deal > with that too if you are willing to make sacrifices), then screen > updates are

Re: Question about X on the arm's.

On Tuesday 29 November 2016 03:24:35 Carsten Haitzler wrote: > On Tue, 29 Nov 2016 10:58:37 +0700 Antoine Martin said: [...] > > http://xpra.org/ > > xpra is its own display system effectively separate from x11. at least > in terms of display as x11 protocol supports no

Re: Question about X on the arm's.

On Tuesday 29 November 2016 02:40:45 Alan Coopersmith wrote: > On 11/28/16 07:58 PM, Antoine Martin wrote: > > Even 100mbit is perfectly usable for remote access provided you use > > the right tools and make some sacrifices. FYI: 4K@60 "fits" in H264 > > ~60Mbps. But again, as I said above, just

[Bug 98897] Macbook pro 11,5 screen flicker when AC adapter plugged in

https://bugs.freedesktop.org/show_bug.cgi?id=98897 Michel Dänzer changed: What|Removed |Added Component|Driver/Radeon |DRM/Radeon

Re: [PATCH xserver] Xi: when creating a new master device, update barries for all clients

Hi, On 11 November 2016 at 05:33, Peter Hutterer wrote: > The previous code only worked when the barrier was created by the same client > as the one calling XIChangeDeviceHierarchy. Reviewed-by: Daniel Stone Cheers, Daniel

[Bug 98897] New: Macbook pro 11,5 screen flicker when AC adapter plugged in

https://bugs.freedesktop.org/show_bug.cgi?id=98897 Bug ID: 98897 Summary: Macbook pro 11,5 screen flicker when AC adapter plugged in Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux

Re: Question about X on the arm's.

If you exclude the 4k fullscreen video use case - which is a worst case scenario for remote display (there are tricks to deal with that too if you are willing to make sacrifices), then screen updates are actually much more manageable, even on a 1Gbps shared link. >>> >>> nope.

Re: [PATCH xf86-input-libinput 1/3] Add a comment regarding scroll dist default values

Hi, On 29-11-16 00:25, Peter Hutterer wrote: Changed this during development because I forgot that the value actually matters (for touchpads anyway). Signed-off-by: Peter Hutterer Series looks good to me: Reviewed-by: Hans de Goede Regards,

Re: [PATCH xserver] xwayland: Don't send KeyRelease events on wl_keyboard::leave

On Thu, Nov 24, 2016 at 07:56:18PM +0100, Rui Matos wrote: > Commits 816015648ffe660ddaa0f7d4d192e555b723c372 and > fee0827a9a695600765f3d04376fc9babe497401 made it so that > wl_keyboard::enter doesn't result in X clients getting KeyPress events > while still updating our internal xkb state to be

Re: Question about X on the arm's.

On 29/11/16 13:04, Gene Heskett wrote: > On Monday 28 November 2016 22:58:37 Antoine Martin wrote: > >> On 29/11/16 10:28, Carsten Haitzler (The Rasterman) wrote: >>> On Tue, 29 Nov 2016 09:43:54 +0700 Antoine Martin > said: On 29/11/16 07:57, Carsten Haitzler (The