[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwin
Subject:    Re: Re: Running kwin_wayland
From:       Martin =?ISO-8859-1?Q?Gr=E4=DFlin?= <mgraesslin () kde ! org>
Date:       2014-11-04 9:31:00
Message-ID: 3101720.77JgNszxfc () martin-desktop
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Monday 03 November 2014 18:12:41 nerdopolis wrote:
> On Monday, November 03, 2014 02:42:30 PM Martin Gräßlin wrote:
> > On Monday 03 November 2014 08:05:36 nerdopolis wrote:
> > > On Monday, November 03, 2014 01:46:42 PM Martin Gräßlin wrote:
> > > > On Monday 03 November 2014 06:00:01 nerdopolis wrote:
> > > > > It seems that when I try
> > > > > unset DISPLAY
> > > > > kwin_wayland --x-server=xvfb --display=:1
> > > > > or
> > > > > kwin_wayland --x-server=xwayland --display=:1
> > > > > I get QXcbConnection: could not connect to display :1
> > > > > so that's why I was starting it manually
> > > > 
> > > > ok, but then you don't need to pass it to the command line.
> > > 
> > > I guess, I would just prefer if I could use the command line
> > > arguments...
> > 
> > well it should work, at least it works for me (TM) ;-)
> 
> Figured this part out: (it doesn't like --x-server= or --display= )
> kwin_wayland -x xwayland --display :1
> 
> BTW: have you looked into using -displayfd which is in newer X servers that
> allow it to print the next available DISPLAY to a file descriptor, so you
> don't have to specify --display= ?

ah I didn't know it automatically picks the next available DISPLAY. The code 
already uses -displayfd, so that can probably be adjusted.

> > > > > Anyway, I also noticed with strace that kwin was using wayland-0,
> > > > > because
> > > > > kwayland has it hardcoded. (Which wayland-0 is being used by the
> > > > > first
> > > > > Weston session for me.) I'll try to see what happens if I make it so
> > > > > that I
> > > > > can specify the server name by setting WAYLAND_DISPLAY to something
> > > > > different with this: http://pastebin.com/wxxAeQkv
> > > > 
> > > > The patch is on KWayland::Server which is not yet used by KWin.
> > > > Changing
> > > > that won't do anything :-)
> > > 
> > > Oh... It's not a Wayland server yet, It's just acting as a client for my
> > > main Wayland display right now?
> > 
> > yes
> > 
> > > > But any released kwin_wayland still requires that WAYLAND_DISPLAY env
> > > > variable is exported in the shell it runs from and aborts/crashes if
> > > > not
> > > > set. That's fixed in latest master.
> > > 
> > > Do I need to set KWIN_OPENGL_INTERFACE=egl_wayland?
> > 
> > no, that's picked automatically for kwin_wayland with OpenGL. You also
> > don't need to export the KWIN_COMPOSE=O2, that's also picked
> > automatically.
> Seems that at least on QEMU it tries to fall back to xrender with swrast,
> and then it fails to initialize compositing, unless I set KWIN_COMPOSE to
> O2

you don't want OpenGL on QEMU </jedihandmove>. Better use KWIN_COMPOSE=Q in 
that case.

Cheers
Martin
["signature.asc" (application/pgp-signature)]

_______________________________________________
kwin mailing list
kwin@kde.org
https://mail.kde.org/mailman/listinfo/kwin


[prev in list] [next in list] [prev in thread] [next in thread]