xserver problems

[Kristian Høgsberg]

On Mon, Jul 08, 2013 at 05:07:31PM -0700, Bill Spitzak wrote:
> Though I agree that the built-in default should load the wlshm
> driver if needed, this is not the problem I am trying to fix.
> 
> My /etc/X11/xorg.conf file contains 'Driver "nv"'. This causes the
> wayland xserver to fail. This will happen whether or not wlshm or
> wlegl drivers are needed. I suspect there is a lot of other crap in
> my xorg.conf that will mess up the wayland xserver, not just this
> driver line.

The drivers that understand xwayland opt-in but setting the
HW_SKIP_CONSOLE flag in the DriverRec driver func.  It's not the most
clear way to opt in, but it should suffice to keep any existing hw ddx
driver from loading when you run the xserver in xwayland mode.  Thus,
nv should fail to load causing the server to skip to the next driver
in the fallback list, which should be wlshm.  Changing the fallback
driver in the xwayland case would be a good patch.

Kristian

> I can "hide" the file by making a dummy one and using environment
> variables so that when the server is launched it finds the dummy.
> But it is impossible to make it used the compiled-in default (as the
> patch /etc/X11/xorg.conf is hard-wired into it and it will always
> find it).
> 
> Kristian Høgsberg wrote:
> >I've commented on this before: the fix here isn't to introduce a new
> >config file to worry about, the fix is to make the X server have a
> >different fallback driver for when it's running in xwayland mode.
> >
> >Kristian
> >
> >On Wed, Jul 3, 2013 at 4:19 AM, Bill Spitzak <spitzak at gmail.com> wrote:
> >>I am really interested in knowing if other people are seeing this problem.
> >>
> >>If this is due to the wlshm driver I would be able to try to fix this. If
> >>this is for all xserver users then I suspect I do not have enough knowledge
> >>to fix it however.
> >>
> >>Bill Spitzak wrote:
> >>>For the last 2 months running x applications under wayland is producing
> >>>black windows, but if you resize them you get screwed up window borders (in
> >>>attached picture).
> >>>
> >>>It also appears that the image does not update until the event *after* the
> >>>one that caused the window to change. For instance if you push a button, the
> >>>button does not draw pushed-in until the mouse is moved.
> >>>
> >>>Are these known problems or is something wrong with my setup?
> >>>
> >>>
> >>>------------------------------------------------------------------------
> >>>
> >>_______________________________________________
> >>wayland-devel mailing list
> >>wayland-devel at lists.freedesktop.org
> >>http://lists.freedesktop.org/mailman/listinfo/wayland-devel