Hi,
I created two bugs, #994, which updates the SCO port, which I would
appreciate someone checking in, and #995, which updates pci.ids so that
modern nVidia cards are recognized (card names taken from the driver).
#995 sure isnt critical for 4.4 but it is simple and useful.
Kean
David Dawes wrote:
[EMAIL PROTECTED] is probably a better place for this]
On Thu, Dec 18, 2003 at 12:36:25AM -0500, Ed Sweetman wrote:
I ran across a little oddity while working on the matrox driver. In
MGAPutImage, the ScreenInfoPtr sent to it which is then converted to a
MGAPtr does not
On Wed, Dec 17, 2003 at 03:08:03PM -0800, Mark Vojkovich wrote:
I don't think it's as bad as you think. It looks to me like
this comes about due to a difference in the Shm protocol. Going
against convention, xShmPutImageReq has an unsigned value for the
src X and Y location. All other
On Wed, 17 Dec 2003, David Dawes wrote:
So, I'm planning to cut a second release candidate tomorrow, take a
Christmas break, and then try to wrap the release up late December/early
January.
I guess that would be today (I have some changes that I've been testing,
for xterm, but was unsure
After installing the release candidate I recognized that startup-times
of especially gnome-applications was significantly longer. Furthermore
the system often froze when using idesk. After changing back to 4.3.0
everything was fine again.
I'm using xfree86 on an AMD Athlon 1000 (133x7.5) with a
Ouch, a typo error :/.. effectively, i have XkbModel set to pc105 and
XkbModel to fr.
setxkbmap -print gives :
xkb_keymap {
xkb_keycodes { include xfree86+aliases(azerty) };
xkb_types { include complete };
xkb_compat{ include complete };
Looking at ProcShmGetImage() there's a bunch of checking for out-of-bounds
coordinates, but ProcShmPutImage() lacks this checking.
Is this patch reasonable or too much (it does fix the problem) but I'm
wondering if the bounds are too strict for PutImage ?
Alan.
Index: shm.c
On Wed, Dec 17, 2003 at 11:59:00PM -0500, David Dawes wrote:
I've been catching up on the 4.4 RC1 test/bug reports after being out
of action for the last few days. Judging from the reports coming in
both here and in bugzilla, there's a good amount of testing happening,
which is great. Some
On Thu, Dec 18, 2003 at 03:19:01PM +, Thomas Estaben wrote:
Ouch, a typo error :/.. effectively, i have XkbModel set to pc105 and
XkbModel to fr.
setxkbmap -print gives :
xkb_keymap {
xkb_keycodes { include xfree86+aliases(azerty) };
xkb_types { include complete
On Thu, Dec 18, 2003 at 07:16:14AM -0500, Thomas Dickey wrote:
On Wed, 17 Dec 2003, David Dawes wrote:
So, I'm planning to cut a second release candidate tomorrow, take a
Christmas break, and then try to wrap the release up late December/early
January.
I guess that would be today
Late today.
On Thu, Dec 18, 2003 at 10:19:47AM -0500, David Dawes wrote:
I did get lots of spurious results with the early versions of the
new xtest scripts I added to make testing easier. The latest version
(4.0.1) seems to be pretty stable now though.
I needed this to get the run.sh script to work
Around 14 o'clock on Dec 18, Alan Hourihane wrote:
Is this patch reasonable or too much (it does fix the problem) but I'm
wondering if the bounds are too strict for PutImage ?
Preserved window contents may not be limited to screen geometry.
___
On Thu, Dec 18, 2003 at 05:48:01PM +, Alan Hourihane wrote:
On Thu, Dec 18, 2003 at 10:19:47AM -0500, David Dawes wrote:
I did get lots of spurious results with the early versions of the
new xtest scripts I added to make testing easier. The latest version
(4.0.1) seems to be pretty stable
On Wed, Dec 10, 2003 at 06:06:31PM +0100, Grzegorz Nieweglowski wrote:
Someone with flexperience would be needed...
On my config this does nicely:
--- xc/programs/twm/lex.c 2003-12-10 17:10:27.0 +0100
+++ xc/programs/twm/lex.c.new 2003-12-10 17:10:47.0 +0100
@@ -25,6 +25,8
Hello all,
I have an intermitent bug on my computer (intel PIV, shuttle motherboard,
integrated i845 video card): sometimes, at boot time, XFree (4.3.0,
from redhat 9 package) fails to start. The screen goes black (or, more
precisely, darkgrey) as the video mode is changed, and stays there
Hi all,
I've just created bug #996, which includes some warnings cleanup and
some extra stuff for the SCO port. Actually, the SCO port stuff is all
related to cleaning up warnings. Some of these may have been specific to
the port but some are generic. If someone with commit access would be so
David Dawes wrote:
On Fri, Dec 12, 2003 at 09:57:39AM -0600, Warren Turkal wrote:
This changes the configuration, only for Debian, such that the manpages
end up in the right places with the right names. I would be wonderful if
this could be committed so this happens automatically for people
On Wed, Dec 10, 2003 at 10:51:40PM -0600, Warren Turkal wrote:
Warren Turkal wrote:
I moved the GzipCmd to get it in alphabetical order. I also added
documentation for DriverManSuffix.
This is an update of the previous. In addition to what is done in the last
patch (this patch includes it), I
18 matches
Mail list logo
