This is likely the last release of the 2.3 series, just tagging the two
patches that have been sitting on top of 2.3.2 into a tarball.
One man page fix, one fix stopping infinite reopens if Option
ReopenAttempts is set to 0.
Peter Hutterer (3):
Don't reopen ad infinitum if reopen_attempts
Despite rumours to the contrary, 1.7 is still alive and kicking. This is the
first (and likely only) release candidate for 1.7.7.
Nothing overly exciting in this one, though it looks like Jeremy is working
hard on getting the no 1 committer trophy. Unless there are some
particularly interesting
'Twas brillig, and tsuraan at 11/04/10 04:26 did gyre and gimble:
We'd like to announce Intel 2010Q1 graphics package, including
xf86-video-intel 2.11.0 release and mesa 7.8.1 release.
Please check http://intellinuxgraphics.org/2010Q1.html for the recommended
stack and what's new in this
Am 10.04.10, 10:03 -0500 schrieb Pat Kane:
The backtrace indicates that you are trying to connect to display :1,
is that really what you want to do (connect to the 2nd display)?
Its intentional, as debuging happened from X session :0. Generally it
does not matter from what session the
On 04/09/2010 07:14 AM, Luis Alberto Padrón Hernández wrote:
Hello Everybody,
I have not been able to get 'nvidia' driver to work, so I need to set my
two monitors with 'nv' driver...
What is the problem with 'nvidia'? Will it work with a single monitor?
Hi,
The question is whether driver maintainers want to deal with
non-maintenance changes (like new hardware support) in the stable branch
of the X server, which will require additional work as they back-port
things from master.
Was a bit shocked when I heard driver will be merged back into
Hello i am trying do a zaphod mode setup because i read was fixed in the
radeon driver but not work
i read about a new option in radeon driver called ZaphodHeads , but i am not
sure how use it , i try what example say but not luck ( ZaphodHeads
DVI-0,DVI-1)
i attach the last xorg.conf with the
I have an application that uses direct calls to X. This application
worked with a previous incarnation of X (before X.org) but crashes
with the following message on newer versions of X. I've tried 7.4+20 and
7.5+5, both Debian on a x86 machine.
xcb_io.c:249: process_responses: Assertion
On Sun, 11 Apr 2010 21:20:00 +0200
Clemens Eisserer linuxhi...@gmail.com wrote:
Hi,
The question is whether driver maintainers want to deal with
non-maintenance changes (like new hardware support) in the stable branch
of the X server, which will require additional work as they back-port
On Sat, Apr 10, 2010 at 08:38:26AM -0500, John R. wrote:
On 03/24/10 23:43, John R. wrote:
On 03/22/10 16:52, Tias wrote:
This shows that although the calibration values differ in different
runs, the clicks received by the calibrator are always at just about
the same coordinates.
This is likely the last release of the 2.3 series, just tagging the two
patches that have been sitting on top of 2.3.2 into a tarball.
One man page fix, one fix stopping infinite reopens if Option
ReopenAttempts is set to 0.
Peter Hutterer (3):
Don't reopen ad infinitum if reopen_attempts
Sadly the poulsbo is effectively a very different driver. It's not
covered by the code in this release at all and the support for it is
pretty tough to track down. I'm not sure where an official home for it
would be to be honest, but hopefully someone more involved with the
project can give
Despite rumours to the contrary, 1.7 is still alive and kicking. This is the
first (and likely only) release candidate for 1.7.7.
Nothing overly exciting in this one, though it looks like Jeremy is working
hard on getting the no 1 committer trophy. Unless there are some
particularly interesting
13 matches
Mail list logo
