I got different behavior with modesetting and the intel ddx

Both didn't render anything, but I think one was crashing over and
over (I think systemd kept restarting it in quick succession)

I only remember that because when I switched VTs it made it almost
impossible to type anything as it kept modesetting back to VT1 for a

That didn't happen with the latest patches (which all seem to be in
master now) but I did get the freeze that you saw

Be aware that kwin detects when there have been rendering crashes or
incomplete starts and disables compositing. With compositing disabled
or set to Xrender everything starts fine



On Thu, 5 Apr 2018 at 08:58 Daniel Stone <dan...@fooishbar.org> wrote:
> Hi Mike,
> On 5 April 2018 at 07:10, Mike Lothian <m...@fireburn.co.uk> wrote:
> > I've just tested with those patches, it still doesn't work without that 
> > revert
> >
> > If you're testing this on kwin can you make sure you're using one of
> > the OpenGL options on the renderer rather than XRender
> I'm absolutely certain it was using OpenGL because it hit all my debug
> prints. I was using KF5-Plasma from Fedora 28: which version did you
> have? When you say 'doesn't seem to start', what happens exactly?
> Before my last patchset, I saw the KDE cursor but no content rendered.
> After applying all three patch series (10 patches total) it started
> fine, but it had in the meantime got into some weird in-between state
> where KWin hung waiting for an ICE/SM message which never returned. I
> had to kill several stray ksmserver processes and also wipe out my
> .ICE-unix directory.
> Cheers,
> Daniel
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel

Reply via email to