I am running debain woody
unstable and having a rough time getting my geforce2 mx
420 to work. The generic nv
driver works fine, however since I want open gl i tried to compile the nvidia
drivers which is where i got problems. I am running
kernel 2.4.18-bf2.4-xfs, when I first went to compi
On Mon, Jan 27, 2003 at 10:50:02AM -0800, David Mosberger wrote:
> > On Sun, 26 Jan 2003 16:20:19 -0500, Branden Robinson <[EMAIL PROTECTED]> said:
>
> Branden> [debian-ia64: I do not subscribe to this list] On Fri, Jan
> Branden> 24, 2003 at 07:30:43PM -0800, David Mosberger wrote:
> >>
Package: xfonts-scalable
Version: 4.2.1-5
Severity: minor
Setting up xfonts-scalable (4.2.1-5) ...
Running update-fonts-scale in Speedo font directory...done.
Running update-fonts-dir in Speedo font directory...done.
Running xftcache in Speedo font directory...FT_Stream_ReadLong: invalid i/o;
pos
I am running debain woody
unstable and having a rough time getting my geforce2 mx
420 to work. The generic nv
driver works fine, however since I want open gl i tried to compile the nvidia
drivers which is where i got problems. I am running
kernel 2.4.18-bf2.4-xfs, when I first went to compi
On Mon, Feb 03, 2003 at 02:15:53AM +0100, Nicolas Boullis scrawled:
> I am not subsrived to debian-x, so please cc: replies to me. (However,
> mutt should be doing the right thing about this.)
>
> I've been trying to use Daniel Stone's pre-4.3 xfree packages (I used to
> say that I worked with h
Hi!
I am not subsrived to debian-x, so please cc: replies to me. (However,
mutt should be doing the right thing about this.)
I've been trying to use Daniel Stone's pre-4.3 xfree packages (I used to
say that I worked with him, but I did so little that it is not fair),
and I had a problem with D
Package: xfonts-scalable
Version: 4.2.1-5
Severity: minor
Setting up xfonts-scalable (4.2.1-5) ...
Running update-fonts-scale in Speedo font directory...done.
Running update-fonts-dir in Speedo font directory...done.
Running xftcache in Speedo font directory...FT_Stream_ReadLong: invalid i/o; pos
> In <[EMAIL PROTECTED]>
> Daniel Stone <[EMAIL PROTECTED]> wrote:
>> The following people deserve thanks in the creation of these packages:
>> * Branden Robinson (the usual XFree86 maintainer), for being around to
>>answer questions, being patient, and showing me how to do stuff w
(my n+2nd attempt at sending this, the lists are severely broken. i am,
however, heartened by the fact that murphy sent one of my mails today).
Hi all!
I've been creating XFree86 4.3 debs for a while now, as some of you
already know (you've even tested them - thanks to those who did!). With
250 l
On Mon, 2003-02-03 at 01:15, Daniel Stone wrote:
> On Mon, Feb 03, 2003 at 12:53:08AM +0100, Michel D?nzer scrawled:
> > >
> > As the name is changing anyway, we might as well get it right. What about
> > xlibmesagl1 (or xlibmesa-gl1, if you insist on the dash)? I'm leaning
> > towards
> > using
On Mon, Feb 03, 2003 at 01:23:16AM +0100, Marcelo E. Magallon scrawled:
> On Mon, Feb 03, 2003 at 11:16:40AM +1100, Daniel Stone wrote:
> > > Why the Mesa packages carry a 3 is also historical baggage and most
> > > people seem to be unaware why that 3 is there in the first place.
> >
> > Yes, and
On Mon, Feb 03, 2003 at 12:31:36AM +0100, Marcelo E. Magallon scrawled:
> On Mon, Feb 03, 2003 at 10:26:05AM +1100, Daniel Stone wrote:
> > I'm not having packages with a misleading name. I'm keeping up status
> > quo until I see a good reason to change current (and expected)
> > behaviour. So far
On Mon, Feb 03, 2003 at 12:53:08AM +0100, Michel D?nzer scrawled:
> On Mon, 2003-02-03 at 00:26, Daniel Stone wrote:
> > On Mon, Feb 03, 2003 at 12:23:07AM +0100, Marcelo E. Magallon scrawled:
> > > On Mon, Feb 03, 2003 at 10:21:22AM +1100, Daniel Stone wrote:
> > > > > uhm... why? That doesn't ma
On Mon, Feb 03, 2003 at 11:16:40AM +1100, Daniel Stone wrote:
> > Why the Mesa packages carry a 3 is also historical baggage and most
> > people seem to be unaware why that 3 is there in the first place.
>
> Yes, and it's been carried through.
Like I said... most people are unaware of why t
On Mon, 2003-02-03 at 00:26, Daniel Stone wrote:
> On Mon, Feb 03, 2003 at 12:23:07AM +0100, Marcelo E. Magallon scrawled:
> > On Mon, Feb 03, 2003 at 10:21:22AM +1100, Daniel Stone wrote:
> > > > uhm... why? That doesn't make any sense at all.
> > >
> > > Hysterical raisins, presumably.
> >
> >
On Mon, Feb 03, 2003 at 02:15:53AM +0100, Nicolas Boullis scrawled:
> I am not subsrived to debian-x, so please cc: replies to me. (However,
> mutt should be doing the right thing about this.)
>
> I've been trying to use Daniel Stone's pre-4.3 xfree packages (I used to
> say that I worked with h
On Mon, Feb 03, 2003 at 12:23:07AM +0100, Marcelo E. Magallon scrawled:
> On Mon, Feb 03, 2003 at 10:21:22AM +1100, Daniel Stone wrote:
> > > uhm... why? That doesn't make any sense at all.
> >
> > Hysterical raisins, presumably.
>
> The raisins explain the 3 but not the 4.
I'm not having packa
On Mon, Feb 03, 2003 at 12:16:38AM +0100, Marcelo E. Magallon scrawled:
> On Mon, Feb 03, 2003 at 10:00:23AM +1100, Daniel Stone wrote:
> > The 3 in 4.2.1's xlibmesa packages, and hence the 4 in my 4.2.99.x
> > xlibmesa packages, reflects the major version of Mesa used.
>
> uhm... why? That doesn
On Mon, Feb 03, 2003 at 10:26:05AM +1100, Daniel Stone wrote:
> I'm not having packages with a misleading name. I'm keeping up status
> quo until I see a good reason to change current (and expected)
> behaviour. So far you haven't provided one.
Neither have you.
As per policy, that number s
Hi!
I am not subsrived to debian-x, so please cc: replies to me. (However,
mutt should be doing the right thing about this.)
I've been trying to use Daniel Stone's pre-4.3 xfree packages (I used to
say that I worked with him, but I did so little that it is not fair),
and I had a problem with D
On Mon, Feb 03, 2003 at 10:21:22AM +1100, Daniel Stone wrote:
> > uhm... why? That doesn't make any sense at all.
>
> Hysterical raisins, presumably.
The raisins explain the 3 but not the 4.
--
Marcelo
On Mon, Feb 03, 2003 at 10:00:23AM +1100, Daniel Stone wrote:
> The 3 in 4.2.1's xlibmesa packages, and hence the 4 in my 4.2.99.x
> xlibmesa packages, reflects the major version of Mesa used.
uhm... why? That doesn't make any sense at all.
--
Marcelo
On Sun, Feb 02, 2003 at 03:05:59PM +0100, Marcelo E. Magallon scrawled:
> Don't look at me. The "3" in the mesa packages makes me puke. It's
> old historical baggage (you probably know why it's there in the first
> place -- but don't ask me why the xlibmesa packages have that ugly 3 or
> 4 or
> In <[EMAIL PROTECTED]>
> Daniel Stone <[EMAIL PROTECTED]> wrote:
>> The following people deserve thanks in the creation of these packages:
>> * Branden Robinson (the usual XFree86 maintainer), for being around to
>>answer questions, being patient, and showing me how to do stuff w
(my n+2nd attempt at sending this, the lists are severely broken. i am,
however, heartened by the fact that murphy sent one of my mails today).
Hi all!
I've been creating XFree86 4.3 debs for a while now, as some of you
already know (you've even tested them - thanks to those who did!). With
250 l
On Mon, 2003-02-03 at 01:15, Daniel Stone wrote:
> On Mon, Feb 03, 2003 at 12:53:08AM +0100, Michel D?nzer scrawled:
> > >
> > As the name is changing anyway, we might as well get it right. What about
> > xlibmesagl1 (or xlibmesa-gl1, if you insist on the dash)? I'm leaning towards
> > using that
On Mon, Feb 03, 2003 at 01:23:16AM +0100, Marcelo E. Magallon scrawled:
> On Mon, Feb 03, 2003 at 11:16:40AM +1100, Daniel Stone wrote:
> > > Why the Mesa packages carry a 3 is also historical baggage and most
> > > people seem to be unaware why that 3 is there in the first place.
> >
> > Yes, and
On Mon, Feb 03, 2003 at 12:53:08AM +0100, Michel D?nzer scrawled:
> On Mon, 2003-02-03 at 00:26, Daniel Stone wrote:
> > On Mon, Feb 03, 2003 at 12:23:07AM +0100, Marcelo E. Magallon scrawled:
> > > On Mon, Feb 03, 2003 at 10:21:22AM +1100, Daniel Stone wrote:
> > > > > uhm... why? That doesn't ma
On Mon, Feb 03, 2003 at 12:31:36AM +0100, Marcelo E. Magallon scrawled:
> On Mon, Feb 03, 2003 at 10:26:05AM +1100, Daniel Stone wrote:
> > I'm not having packages with a misleading name. I'm keeping up status
> > quo until I see a good reason to change current (and expected)
> > behaviour. So far
On Mon, Feb 03, 2003 at 11:16:40AM +1100, Daniel Stone wrote:
> > Why the Mesa packages carry a 3 is also historical baggage and most
> > people seem to be unaware why that 3 is there in the first place.
>
> Yes, and it's been carried through.
Like I said... most people are unaware of why t
On Mon, 2003-02-03 at 00:26, Daniel Stone wrote:
> On Mon, Feb 03, 2003 at 12:23:07AM +0100, Marcelo E. Magallon scrawled:
> > On Mon, Feb 03, 2003 at 10:21:22AM +1100, Daniel Stone wrote:
> > > > uhm... why? That doesn't make any sense at all.
> > >
> > > Hysterical raisins, presumably.
> >
> >
On Mon, Feb 03, 2003 at 12:23:07AM +0100, Marcelo E. Magallon scrawled:
> On Mon, Feb 03, 2003 at 10:21:22AM +1100, Daniel Stone wrote:
> > > uhm... why? That doesn't make any sense at all.
> >
> > Hysterical raisins, presumably.
>
> The raisins explain the 3 but not the 4.
I'm not having packa
On Mon, Feb 03, 2003 at 12:16:38AM +0100, Marcelo E. Magallon scrawled:
> On Mon, Feb 03, 2003 at 10:00:23AM +1100, Daniel Stone wrote:
> > The 3 in 4.2.1's xlibmesa packages, and hence the 4 in my 4.2.99.x
> > xlibmesa packages, reflects the major version of Mesa used.
>
> uhm... why? That doesn
On Mon, Feb 03, 2003 at 10:26:05AM +1100, Daniel Stone wrote:
> I'm not having packages with a misleading name. I'm keeping up status
> quo until I see a good reason to change current (and expected)
> behaviour. So far you haven't provided one.
Neither have you.
As per policy, that number s
On Mon, Feb 03, 2003 at 10:21:22AM +1100, Daniel Stone wrote:
> > uhm... why? That doesn't make any sense at all.
>
> Hysterical raisins, presumably.
The raisins explain the 3 but not the 4.
--
Marcelo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Troub
On Mon, Feb 03, 2003 at 10:00:23AM +1100, Daniel Stone wrote:
> The 3 in 4.2.1's xlibmesa packages, and hence the 4 in my 4.2.99.x
> xlibmesa packages, reflects the major version of Mesa used.
uhm... why? That doesn't make any sense at all.
--
Marcelo
--
To UNSUBSCRIBE, email to [EMAIL P
On Sun, Feb 02, 2003 at 03:05:59PM +0100, Marcelo E. Magallon scrawled:
> Don't look at me. The "3" in the mesa packages makes me puke. It's
> old historical baggage (you probably know why it's there in the first
> place -- but don't ask me why the xlibmesa packages have that ugly 3 or
> 4 or
tag 179352 + patch pending
thanks
On Sat, Feb 01, 2003 at 04:21:54PM -0200, Andre Luis Lopes wrote:
> After some time laging behind the others translators, here's me again
> with yet-another-xfree86's-pt_BR-translation. I think it's the very
> first one I did since the po-debconf transition.
[...]
severity 179390 normal
thanks
On Sat, Feb 01, 2003 at 06:45:58PM -0500, James A Morrison wrote:
> severity: grave
>
> X is now unusable on my Ultra 5 running unstable.
Bzzt.
The bug is not grave because it doesn't affect all users of the package.
The bug isn't even "important" because there's
Processing commands for [EMAIL PROTECTED]:
> severity 179442 normal
Bug#179442: UK Sun-type5 Keymap installation issue
Severity set to `normal'.
> severity 179443 normal
Bug#179443: UK Sun-type5 Keymapissue
Severity set to `normal'.
> reassign 179442 xlibs
Bug#179442: UK Sun-type5 Keymap install
Processing commands for [EMAIL PROTECTED]:
> tag 179352 + patch pending
Bug#179352: xfree86: [wishlist] Updated brazilian portuguese (pt_BR) debconf
template translation
There were no tags set.
Tags added: patch, pending
> thanks
Stopping processing here.
Please contact me if you need assistanc
Processing commands for [EMAIL PROTECTED]:
> severity 179390 normal
Bug#179390: Keyboard input with a type5 keyboard is b0rked.
Bug#178465: xlibs: [XKB] missing semicolon in patch to keycodes/sun
Bug#178996: xlibs: [XKB] missing semicolon in keycodes/sun
Severity set to `normal'.
> thanks
Stoppin
Processing commands for [EMAIL PROTECTED]:
> tag 179407 + upstream
Bug#179407: xterm: bold fonts do not work with widechars (and consequently
utf-8 mode)
There were no tags set.
Tags added: upstream
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bu
tag 179352 + patch pending
thanks
On Sat, Feb 01, 2003 at 04:21:54PM -0200, Andre Luis Lopes wrote:
> After some time laging behind the others translators, here's me again
> with yet-another-xfree86's-pt_BR-translation. I think it's the very
> first one I did since the po-debconf transition.
[...]
severity 179390 normal
thanks
On Sat, Feb 01, 2003 at 06:45:58PM -0500, James A Morrison wrote:
> severity: grave
>
> X is now unusable on my Ultra 5 running unstable.
Bzzt.
The bug is not grave because it doesn't affect all users of the package.
The bug isn't even "important" because there's
Processing commands for [EMAIL PROTECTED]:
> tag 179407 + upstream
Bug#179407: xterm: bold fonts do not work with widechars (and consequently utf-8 mode)
There were no tags set.
Tags added: upstream
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug
Processing commands for [EMAIL PROTECTED]:
> severity 179390 normal
Bug#179390: Keyboard input with a type5 keyboard is b0rked.
Bug#178465: xlibs: [XKB] missing semicolon in patch to keycodes/sun
Bug#178996: xlibs: [XKB] missing semicolon in keycodes/sun
Severity set to `normal'.
> thanks
Stoppin
Processing commands for [EMAIL PROTECTED]:
> severity 179442 normal
Bug#179442: UK Sun-type5 Keymap installation issue
Severity set to `normal'.
> severity 179443 normal
Bug#179443: UK Sun-type5 Keymapissue
Severity set to `normal'.
> reassign 179442 xlibs
Bug#179442: UK Sun-type5 Keymap install
Processing commands for [EMAIL PROTECTED]:
> tag 179352 + patch pending
Bug#179352: xfree86: [wishlist] Updated brazilian portuguese (pt_BR) debconf template
translation
There were no tags set.
Tags added: patch, pending
> thanks
Stopping processing here.
Please contact me if you need assistanc
On Son, 2003-02-02 at 16:45, Marcelo E. Magallon wrote:
> >> Michel Dänzer <[EMAIL PROTECTED]> writes:
>
> > Shouldn't be a problem because nothing outside of the xfree86 source
> > package should depend on the xlibmesa packages directly (or deal with
> > it)?
>
> You just have to convince ap
On Sun, Feb 02, 2003 at 05:06:29PM +0100, Michel Dänzer wrote:
> On Son, 2003-02-02 at 16:49, Sven Luther wrote:
> > On Sun, Feb 02, 2003 at 04:17:52PM +0100, Michel Dänzer wrote:
> > > > (I got to get myself a Radeon before that happens[0]) and that's just
> > > > easier if I have a separate GLU
>> Michel Dänzer <[EMAIL PROTECTED]> writes:
> Shouldn't be a problem because nothing outside of the xfree86 source
> package should depend on the xlibmesa packages directly (or deal with
> it)?
You just have to convince apt that replacing the then dissapeared foo3
by foo1 just because the l
On Son, 2003-02-02 at 16:49, Sven Luther wrote:
> On Sun, Feb 02, 2003 at 04:17:52PM +0100, Michel Dänzer wrote:
> > > (I got to get myself a Radeon before that happens[0]) and that's just
> > > easier if I have a separate GLU package. The other reason was to have
> > > a GLU package that the n
On Son, 2003-02-02 at 16:45, Marcelo E. Magallon wrote:
> >> Michel Dänzer <[EMAIL PROTECTED]> writes:
>
> > Shouldn't be a problem because nothing outside of the xfree86 source
> > package should depend on the xlibmesa packages directly (or deal with
> > it)?
>
> You just have to convince ap
On Sun, Feb 02, 2003 at 04:17:52PM +0100, Michel Dänzer wrote:
> > (I got to get myself a Radeon before that happens[0]) and that's just
> > easier if I have a separate GLU package. The other reason was to have
> > a GLU package that the nvidia packages can depend on. I *hate* the way
> > the
On Sun, Feb 02, 2003 at 04:21:53PM +0100, Marcelo E. Magallon wrote:
> On Sun, Feb 02, 2003 at 03:09:11PM +0100, Sven Luther wrote:
>
> > And because the autobuilders don't like virtual build dependencies,
> > which is, i think, a worse problem.
>
> Please. That's a weak argument. If any pac
On Son, 2003-02-02 at 15:05, Marcelo E. Magallon wrote:
>
> >> Michel Dänzer <[EMAIL PROTECTED]> writes:
>
> > > I still don't get it. There's no incompatibility between
> > > xlibmesa3-gl, xlibmesa4-gl and xlibmesa5-gl to come, so what's the
> > > point of the different names? The worst thing
On Sun, Feb 02, 2003 at 03:09:11PM +0100, Sven Luther wrote:
> And because the autobuilders don't like virtual build dependencies,
> which is, i think, a worse problem.
Please. That's a weak argument. If any package providing a virtual
package is a good as the next one, you can pick anyone.
On Sun, Feb 02, 2003 at 05:06:29PM +0100, Michel Dänzer wrote:
> On Son, 2003-02-02 at 16:49, Sven Luther wrote:
> > On Sun, Feb 02, 2003 at 04:17:52PM +0100, Michel Dänzer wrote:
> > > > (I got to get myself a Radeon before that happens[0]) and that's just
> > > > easier if I have a separate GLU
>> Michel Dänzer <[EMAIL PROTECTED]> writes:
> Shouldn't be a problem because nothing outside of the xfree86 source
> package should depend on the xlibmesa packages directly (or deal with
> it)?
You just have to convince apt that replacing the then dissapeared foo3
by foo1 just because the l
On Son, 2003-02-02 at 15:09, Sven Luther wrote:
> On Sun, Feb 02, 2003 at 03:05:59PM +0100, Marcelo E. Magallon wrote:
> >
> > >> Michel Dänzer <[EMAIL PROTECTED]> writes:
> >
> > > > I still don't get it. There's no incompatibility between
> > > > xlibmesa3-gl, xlibmesa4-gl and xlibmesa5-gl to
On Son, 2003-02-02 at 16:49, Sven Luther wrote:
> On Sun, Feb 02, 2003 at 04:17:52PM +0100, Michel Dänzer wrote:
> > > (I got to get myself a Radeon before that happens[0]) and that's just
> > > easier if I have a separate GLU package. The other reason was to have
> > > a GLU package that the n
On Sun, Feb 02, 2003 at 03:05:59PM +0100, Marcelo E. Magallon wrote:
> Hi Michel,
>
> thanks for the Cc: ...
>
> >> Michel Dänzer <[EMAIL PROTECTED]> writes:
>
> > > I still don't get it. There's no incompatibility between
> > > xlibmesa3-gl, xlibmesa4-gl and xlibmesa5-gl to come, so what's t
Processing commands for [EMAIL PROTECTED]:
> reassign 179390 xlibs
Bug#179390: Keyboard input with a type5 keyboard is b0rked.
Bug reassigned from package `xfree86' to `xlibs'.
> severity 178465 grave
Bug#178465: xlibs: [XKB] missing semicolon in patch to keycodes/sun
Bug#178996: xlibs: [XKB] mis
On Sun, Feb 02, 2003 at 04:17:52PM +0100, Michel Dänzer wrote:
> > (I got to get myself a Radeon before that happens[0]) and that's just
> > easier if I have a separate GLU package. The other reason was to have
> > a GLU package that the nvidia packages can depend on. I *hate* the way
> > the
Hi Michel,
thanks for the Cc: ...
>> Michel Dänzer <[EMAIL PROTECTED]> writes:
> > I still don't get it. There's no incompatibility between
> > xlibmesa3-gl, xlibmesa4-gl and xlibmesa5-gl to come, so what's the
> > point of the different names? The worst thing IMHO is
> > x-window-system-co
On Sun, Feb 02, 2003 at 04:21:53PM +0100, Marcelo E. Magallon wrote:
> On Sun, Feb 02, 2003 at 03:09:11PM +0100, Sven Luther wrote:
>
> > And because the autobuilders don't like virtual build dependencies,
> > which is, i think, a worse problem.
>
> Please. That's a weak argument. If any pac
On Son, 2003-02-02 at 15:05, Marcelo E. Magallon wrote:
>
> >> Michel Dänzer <[EMAIL PROTECTED]> writes:
>
> > > I still don't get it. There's no incompatibility between
> > > xlibmesa3-gl, xlibmesa4-gl and xlibmesa5-gl to come, so what's the
> > > point of the different names? The worst thing
On Sun, Feb 02, 2003 at 03:09:11PM +0100, Sven Luther wrote:
> And because the autobuilders don't like virtual build dependencies,
> which is, i think, a worse problem.
Please. That's a weak argument. If any package providing a virtual
package is a good as the next one, you can pick anyone.
Package: xserver-xfree86
Version: 4.1.0-16
Severity: normal
Hi - I noticed that the 4.1 r128_drv.o module was ignoring everything
except the X and Y resolutions of the modes in my X86Config file -
the module seems to grab just the X and Y resolutions, and throw
away all the other data, including t
On Fre, 2003-01-31 at 18:11, Michel Dänzer wrote:
> I still don't get it. There's no incompatibility between xlibmesa3-gl,
> xlibmesa4-gl and xlibmesa5-gl to come, so what's the point of the
> different names? The worst thing IMHO is x-window-system-core depending
> on one particular of these, but
On Son, 2003-02-02 at 15:09, Sven Luther wrote:
> On Sun, Feb 02, 2003 at 03:05:59PM +0100, Marcelo E. Magallon wrote:
> >
> > >> Michel Dänzer <[EMAIL PROTECTED]> writes:
> >
> > > > I still don't get it. There's no incompatibility between
> > > > xlibmesa3-gl, xlibmesa4-gl and xlibmesa5-gl to
On Sun, Feb 02, 2003 at 03:05:59PM +0100, Marcelo E. Magallon wrote:
> Hi Michel,
>
> thanks for the Cc: ...
>
> >> Michel Dänzer <[EMAIL PROTECTED]> writes:
>
> > > I still don't get it. There's no incompatibility between
> > > xlibmesa3-gl, xlibmesa4-gl and xlibmesa5-gl to come, so what's t
Processing commands for [EMAIL PROTECTED]:
> reassign 179390 xlibs
Bug#179390: Keyboard input with a type5 keyboard is b0rked.
Bug reassigned from package `xfree86' to `xlibs'.
> severity 178465 grave
Bug#178465: xlibs: [XKB] missing semicolon in patch to keycodes/sun
Bug#178996: xlibs: [XKB] mis
Hi Michel,
thanks for the Cc: ...
>> Michel Dänzer <[EMAIL PROTECTED]> writes:
> > I still don't get it. There's no incompatibility between
> > xlibmesa3-gl, xlibmesa4-gl and xlibmesa5-gl to come, so what's the
> > point of the different names? The worst thing IMHO is
> > x-window-system-co
Package: xserver-xfree86
Version: 4.1.0-16
Severity: normal
Hi - I noticed that the 4.1 r128_drv.o module was ignoring everything
except the X and Y resolutions of the modes in my X86Config file -
the module seems to grab just the X and Y resolutions, and throw
away all the other data, including t
On Fre, 2003-01-31 at 18:11, Michel Dänzer wrote:
> I still don't get it. There's no incompatibility between xlibmesa3-gl,
> xlibmesa4-gl and xlibmesa5-gl to come, so what's the point of the
> different names? The worst thing IMHO is x-window-system-core depending
> on one particular of these, but
package: xfree86
version: 4.2.1-5
severity: grave
-- System Information
Debian Release: 3.0
Architecture: sparc
Kernal Linux trinity 2.4.18 #2 Thu Apr 11 14:37:17 EDT 2002 sparc64
Locale: LANG=C, LC_CTYPE=C
The only way to get a UK keyboard to work with the right mapping is to select
the default
package: xfree86
version: 4.2.1-5
severity: grave
-- System Information
Debian Release: 3.0
Architecture: sparc
Kernal Linux trinity 2.4.18 #2 Thu Apr 11 14:37:17 EDT 2002 sparc64
Locale: LANG=C, LC_CTYPE=C
Selecting Sun UK type 5 keyboard during installation process causes a terminal
freeze at
package: xfree86
version: 4.2.1-5
severity: grave
-- System Information
Debian Release: 3.0
Architecture: sparc
Kernal Linux trinity 2.4.18 #2 Thu Apr 11 14:37:17 EDT 2002 sparc64
Locale: LANG=C, LC_CTYPE=C
The only way to get a UK keyboard to work with the right mapping is to select the
default
package: xfree86
version: 4.2.1-5
severity: grave
-- System Information
Debian Release: 3.0
Architecture: sparc
Kernal Linux trinity 2.4.18 #2 Thu Apr 11 14:37:17 EDT 2002 sparc64
Locale: LANG=C, LC_CTYPE=C
Selecting Sun UK type 5 keyboard during installation process causes a terminal freeze
at
> After I upgraded from xlibmesa3 4.2.1-3 to 4.2.1-5 (including -gl and
> -glu), glxgears and all other programs that make use of OpenGL simply
> result in an empty screen/window; downgrading to -3 again (and
> deleting xlibmesa3-gl{,u} fixes the problem completely.
I can confirm this behaviour.
82 matches
Mail list logo
