Bill Spitzak wrote:
Kristian Høgsberg wrote:
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 ca
Kristian Høgsberg wrote:
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 xserve
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
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
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 wrote:
> I am really interested in knowi
On 05/07/2013 20:10, Bill Spitzak wrote:
On 07/03/2013 03:35 PM, scsijon wrote:
we have seen this before with xorg servers, it's usually found that some
dependancy for the driver concerned has been updated, but the driver
itself hasn't been rebuilt to suit, usually fixed by either recompiling
t
On 07/03/2013 03:35 PM, scsijon wrote:
we have seen this before with xorg servers, it's usually found that some
dependancy for the driver concerned has been updated, but the driver
itself hasn't been rebuilt to suit, usually fixed by either recompiling
the driver (if possible) or stepping back t
--
Message: 3
Date: Wed, 03 Jul 2013 10:44:13 +0200
From: sardemff7+wayl...@sardemff7.net
To: Bill Spitzak , wayland
Subject: Re: xserver problems
Message-ID: <51d3e45d.1040...@sardemff7.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
On 03/07/2013 10:19, Bill Spitzak 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 Spitz
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
Is this the same result other see?
I have to use the wlshm driver, and was wondering if the problem is with
it, or if it is a general problem with xserver.
Bill Spitzak wrote:
For the last 2 months running x applications under wayland is producing
black windows, but if you resize them you get
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 i
12 matches
Mail list logo
