Subject: problems with Xv not only with mplayer
Followup-For: Bug #130745
Package: xserver-xfree86
Version: 4.2.1-3
Message-Id: <[EMAIL PROTECTED]>
Date: Mon, 28 Oct 2002 14:56:16 -0500 (EST)
From: [EMAIL PROTECTED] (www-data)
Hi,
I'm having the same problem, but by doing any changes to
On Wed, Oct 23, 2002 at 08:10:43PM -0400, Matt Zimmerman wrote:
> On Wed, Oct 23, 2002 at 02:02:12PM -0500, Branden Robinson wrote:
> > Matt, I'd be more than happy to use xfree86 in unstable as a testbed for
> > your proposal. If you agree, let's migrate this subthread over to
> > debian-x.
>
>
Subject: problems with Xv not only with mplayer
Followup-For: Bug #130745
Package: xserver-xfree86
Version: 4.2.1-3
Message-Id: <[EMAIL PROTECTED]>
Date: Mon, 28 Oct 2002 14:56:16 -0500 (EST)
From: [EMAIL PROTECTED] (www-data)
Hi,
I'm having the same problem, but by doing any changes to
On Wed, Oct 23, 2002 at 08:10:43PM -0400, Matt Zimmerman wrote:
> On Wed, Oct 23, 2002 at 02:02:12PM -0500, Branden Robinson wrote:
> > Matt, I'd be more than happy to use xfree86 in unstable as a testbed for
> > your proposal. If you agree, let's migrate this subthread over to
> > debian-x.
>
>
Your message dated Mon, 28 Oct 2002 21:27:06 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#166413: mga driver doesn't set gamma on second screen
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Mon, 28 Oct 2002 21:27:06 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#166413: mga driver doesn't set gamma on second screen
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
On Mon, 2002-10-28 at 21:29, [EMAIL PROTECTED] wrote:
>
> > * If someone has a Matrox card that *can* set the gamma on the second
> > head, file a separate report.
> >
> > Brett has a Matrox MGA G400 AGP rev 130. That is the only model of card
> > that matters for this report.
>
> Umm, actuall
On Mon, Oct 28, 2002 at 02:53:35PM -0500, [EMAIL PROTECTED] wrote:
> On Mon, Oct 28, 2002 at 07:40:12PM +0100, Michel Dänzer wrote:
> > Every monitor has a characteristic color response curve; that's one
> > thing one can compensate for using xgamma. You can't expect the same
> > values to produce
On Mon, Oct 28, 2002 at 02:53:35PM -0500, [EMAIL PROTECTED] wrote:
> Okay, I'm getting frustrated with you Matrox guys.
Hopefully this message will clear the air.
> Brett Carter says:
> "After a quick reboot to windows, looks like the results are the same
> there - you can't set the gamma on th
On Mon, Oct 28, 2002 at 01:01:43PM +0100, Michel D?nzer wrote:
>
> I doubt that very much as it happens with all kinds of keyboards on Macs
> but doesn't happen in Mac OS.
Well as I said earlier, it's not difficult to convince me.
For ADB keyboards, you just have to enable dump_adb_input in
maci
On Mon, 2002-10-28 at 21:29, [EMAIL PROTECTED] wrote:
>
> > * If someone has a Matrox card that *can* set the gamma on the second
> > head, file a separate report.
> >
> > Brett has a Matrox MGA G400 AGP rev 130. That is the only model of card
> > that matters for this report.
>
> Umm, actuall
On Mon, 2002-10-28 at 20:09, Joey Hess wrote:
> Package: xterm
> Version: 4.2.1-3
> Severity: normal
>
> I couldn't belive this was happening at first, but I have reproduced it
> 4 times now.
>
> * Run an xterm or two, and verify that text highlights as expected;
> starting from the letter clic
On Mon, Oct 28, 2002 at 07:40:12PM +0100, Michel Dänzer wrote:
> Every monitor has a characteristic color response curve; that's one
> thing one can compensate for using xgamma. You can't expect the same
> values to produce the same result on different monitors.
Okay, I'm getting frustrated with y
On Mon, Oct 28, 2002 at 02:53:35PM -0500, [EMAIL PROTECTED] wrote:
> On Mon, Oct 28, 2002 at 07:40:12PM +0100, Michel Dänzer wrote:
> > Every monitor has a characteristic color response curve; that's one
> > thing one can compensate for using xgamma. You can't expect the same
> > values to produce
Processing commands for [EMAIL PROTECTED]:
> retitle 166413 xserver-xfree86: [mga] cannot set secondary head's gamma on
> MGA G400 AGP rev 130
Bug#166413: xserver-xfree86: [mga] cannot set gamma on secondary head
Changed Bug title.
> thanks
Stopping processing here.
Please contact me if you nee
retitle 166816 xserver-xfree86: [core server] server unprotected from system
clocks that go for a trip in the TARDIS
reassign 166816 xserver-xfree86
tag 166816 + upstream
thanks
On Mon, Oct 28, 2002 at 02:09:47PM -0500, Joey Hess wrote:
> I couldn't belive this was happening at first, but I have
Processing commands for [EMAIL PROTECTED]:
> retitle 166816 xserver-xfree86: [core server] server unprotected from system
> clocks that go for a trip in the TARDIS
Bug#166816: xterm: clock set back in time -> screwy text selection
Changed Bug title.
> reassign 166816 xserver-xfree86
Bug#166816:
On Mon, Oct 28, 2002 at 02:53:35PM -0500, [EMAIL PROTECTED] wrote:
> Okay, I'm getting frustrated with you Matrox guys.
Hopefully this message will clear the air.
> Brett Carter says:
> "After a quick reboot to windows, looks like the results are the same
> there - you can't set the gamma on th
On Mon, 2002-10-28 at 17:55, Marc Wilson wrote:
> On Sun, Oct 27, 2002 at 11:14:37PM -0500, [EMAIL PROTECTED] wrote:
> > On Sun, Oct 27, 2002 at 07:07:15PM -0800, Marc Wilson wrote:
> > > I always had the problem with my G450 and later with my G550 that X
> > > wouldn't set the gamma the same on bo
Package: xterm
Version: 4.2.1-3
Severity: normal
I couldn't belive this was happening at first, but I have reproduced it
4 times now.
* Run an xterm or two, and verify that text highlights as expected;
starting from the letter clicked on and extending up or down to the
point the mouse is over
On Mon, 2002-10-28 at 16:12, Jeffrey Baker wrote:
> On Mon, Oct 28, 2002 at 12:31:40PM +0100, Michel D?nzer wrote:
> > On Mon, 2002-10-28 at 04:07, Marc Wilson wrote:
> > > On Sun, Oct 27, 2002 at 07:25:51PM -0500, [EMAIL PROTECTED] wrote:
> > > > 2) It is possible that this is a hardware limitatio
On Mon, Oct 28, 2002 at 01:01:43PM +0100, Michel D?nzer wrote:
>
> I doubt that very much as it happens with all kinds of keyboards on Macs
> but doesn't happen in Mac OS.
Well as I said earlier, it's not difficult to convince me.
For ADB keyboards, you just have to enable dump_adb_input in
maci
> I dual-boot to windows on this same box, I'll see if gamma on the second
> monitor is supported there. Also, I don't have Matrox's hal loaded, I
> wonder if that would make a difference?
>
> -Brett Carter
After a quick reboot to windows, looks like the results are the same
there - you can't se
On Mon, 2002-10-28 at 20:09, Joey Hess wrote:
> Package: xterm
> Version: 4.2.1-3
> Severity: normal
>
> I couldn't belive this was happening at first, but I have reproduced it
> 4 times now.
>
> * Run an xterm or two, and verify that text highlights as expected;
> starting from the letter clic
On Mon, Oct 28, 2002 at 07:40:12PM +0100, Michel Dänzer wrote:
> Every monitor has a characteristic color response curve; that's one
> thing one can compensate for using xgamma. You can't expect the same
> values to produce the same result on different monitors.
Okay, I'm getting frustrated with y
Processing commands for [EMAIL PROTECTED]:
> retitle 166413 xserver-xfree86: [mga] cannot set secondary head's gamma on MGA G400
>AGP rev 130
Bug#166413: xserver-xfree86: [mga] cannot set gamma on secondary head
Changed Bug title.
> thanks
Stopping processing here.
Please contact me if you need
On Mon, Oct 28, 2002 at 12:42:12PM -0500, Branden Robinson wrote:
>
> I assume all GL libraries in Debian will have this problem?
>
At least all GL libraries using C++ code, yes.
>
> Why would I call it xlibmesa3"c"? What does the "c" mean?
>
The "c" is the official addendum a C++ library sho
Your message dated Mon, 28 Oct 2002 12:38:21 -0500
with message-id <[EMAIL PROTECTED]>
and subject line [EMAIL PROTECTED]: Bug#166497: x-window-system: should depend
on x-display-manager instead of xdm]
has caused the attached Bug report to be marked as done.
This means that you claim that the pr
retitle 166816 xserver-xfree86: [core server] server unprotected from system clocks
that go for a trip in the TARDIS
reassign 166816 xserver-xfree86
tag 166816 + upstream
thanks
On Mon, Oct 28, 2002 at 02:09:47PM -0500, Joey Hess wrote:
> I couldn't belive this was happening at first, but I have
Processing commands for [EMAIL PROTECTED]:
> retitle 166816 xserver-xfree86: [core server] server unprotected from system clocks
>that go for a trip in the TARDIS
Bug#166816: xterm: clock set back in time -> screwy text selection
Changed Bug title.
> reassign 166816 xserver-xfree86
Bug#166816: x
On Sun, Oct 27, 2002 at 07:25:51PM -0500, [EMAIL PROTECTED] wrote:
I knew I forgot something. My log and XF86Config are attached.
> 1) Please include the information described in XF86Config(7):
>
>When reporting bugs to the Debian Bug Tracking System in
>xserver-x
On Mon, Oct 28, 2002 at 03:23:55PM +0100, Martin Loschwitz wrote:
> At weekend, i created the first Qt3.1 .deb's and ran into a problem which is
> bundled with the xfree86 "xlibmesa3" package. This is why i'm writing here. ;)
>
> Let me describe the problem: Qt3 supports linking against OpenGL lib
On Mon, 2002-10-28 at 17:55, Marc Wilson wrote:
> On Sun, Oct 27, 2002 at 11:14:37PM -0500, [EMAIL PROTECTED] wrote:
> > On Sun, Oct 27, 2002 at 07:07:15PM -0800, Marc Wilson wrote:
> > > I always had the problem with my G450 and later with my G550 that X
> > > wouldn't set the gamma the same on bo
On Sun, Oct 27, 2002 at 11:14:37PM -0500, [EMAIL PROTECTED] wrote:
> On Sun, Oct 27, 2002 at 07:07:15PM -0800, Marc Wilson wrote:
> > I always had the problem with my G450 and later with my G550 that X
> > wouldn't set the gamma the same on both heads, although it claimed that it
> > was according
Package: xterm
Version: 4.2.1-3
Severity: normal
I couldn't belive this was happening at first, but I have reproduced it
4 times now.
* Run an xterm or two, and verify that text highlights as expected;
starting from the letter clicked on and extending up or down to the
point the mouse is over
On Mon, 2002-10-28 at 16:12, Jeffrey Baker wrote:
> On Mon, Oct 28, 2002 at 12:31:40PM +0100, Michel D?nzer wrote:
> > On Mon, 2002-10-28 at 04:07, Marc Wilson wrote:
> > > On Sun, Oct 27, 2002 at 07:25:51PM -0500, [EMAIL PROTECTED] wrote:
> > > > 2) It is possible that this is a hardware limitatio
On Mon, Oct 28, 2002 at 01:01:43PM +0100, Michel Dänzer wrote:
> > Well I don't see anything in there that shows that this is a kernel
> > bug. What it does show is that some people are seeing this on the
> > console. This means that it probably is a hardware problem.
>
> I doubt that very much
Processing commands for [EMAIL PROTECTED]:
> tag 121335 + wontfix
Bug#121335: kernel: keybounce on Toshiba Tecra 9000
Bug#142569: kernel: keybounce when system is under load
Bug#156563: kernel: key release on Mac USB keyboard not detected by X server
Tags added: wontfix
> thanks
Stopping processi
On Mon, Oct 23, 2000 at 08:44:37AM -0500, Branden Robinson wrote:
|| The reason I wrote that part of startx the way I did was due to the
|| following scenario:
||
|| 1) user has a display manager managing :0
|| 2) user logs in on :0, creating XDM-AUTHORIZATION-1 cookie for :0
|| 3) user switc
On Mon, Oct 28, 2002 at 02:47:42AM -0500, Zephaniah E. Hull wrote:
> This is going to generate spurious events when speaking the EXPS/2
> protocol from unpatched kernel HID layers, specificly
> drivers/input/mousedev.c generates the wheel data incorrectly, I have a
> patch for that which I'm trying
> I dual-boot to windows on this same box, I'll see if gamma on the second
> monitor is supported there. Also, I don't have Matrox's hal loaded, I
> wonder if that would make a difference?
>
> -Brett Carter
After a quick reboot to windows, looks like the results are the same
there - you can't se
On Mon, Oct 28, 2002 at 12:31:40PM +0100, Michel D?nzer wrote:
> On Mon, 2002-10-28 at 04:07, Marc Wilson wrote:
> > On Sun, Oct 27, 2002 at 07:25:51PM -0500, [EMAIL PROTECTED] wrote:
> > > 2) It is possible that this is a hardware limitation. Multiple-output
> > > video cards often don't support
On Mon, Oct 28, 2002 at 12:42:12PM -0500, Branden Robinson wrote:
>
> I assume all GL libraries in Debian will have this problem?
>
At least all GL libraries using C++ code, yes.
>
> Why would I call it xlibmesa3"c"? What does the "c" mean?
>
The "c" is the official addendum a C++ library sho
Your message dated Mon, 28 Oct 2002 12:38:21 -0500
with message-id <[EMAIL PROTECTED]>
and subject line [[EMAIL PROTECTED]: Bug#166497: x-window-system: should depend
on x-display-manager instead of xdm]
has caused the attached Bug report to be marked as done.
This means that you claim that the p
On Sun, Oct 27, 2002 at 07:25:51PM -0500, [EMAIL PROTECTED] wrote:
I knew I forgot something. My log and XF86Config are attached.
> 1) Please include the information described in XF86Config(7):
>
>When reporting bugs to the Debian Bug Tracking System in
>xserver-x
On Mon, Oct 28, 2002 at 03:23:55PM +0100, Martin Loschwitz wrote:
> At weekend, i created the first Qt3.1 .deb's and ran into a problem which is
> bundled with the xfree86 "xlibmesa3" package. This is why i'm writing here. ;)
>
> Let me describe the problem: Qt3 supports linking against OpenGL lib
On Sun, Oct 27, 2002 at 11:14:37PM -0500, [EMAIL PROTECTED] wrote:
> On Sun, Oct 27, 2002 at 07:07:15PM -0800, Marc Wilson wrote:
> > I always had the problem with my G450 and later with my G550 that X
> > wouldn't set the gamma the same on both heads, although it claimed that it
> > was according
On Mon, Oct 28, 2002 at 01:01:43PM +0100, Michel Dänzer wrote:
> > Well I don't see anything in there that shows that this is a kernel
> > bug. What it does show is that some people are seeing this on the
> > console. This means that it probably is a hardware problem.
>
> I doubt that very much
Processing commands for [EMAIL PROTECTED]:
> tag 121335 + wontfix
Bug#121335: kernel: keybounce on Toshiba Tecra 9000
Bug#142569: kernel: keybounce when system is under load
Bug#156563: kernel: key release on Mac USB keyboard not detected by X server
Tags added: wontfix
> thanks
Stopping processi
On Mon, Oct 23, 2000 at 08:44:37AM -0500, Branden Robinson wrote:
|| The reason I wrote that part of startx the way I did was due to the
|| following scenario:
||
|| 1) user has a display manager managing :0
|| 2) user logs in on :0, creating XDM-AUTHORIZATION-1 cookie for :0
|| 3) user switc
On Mon, Oct 28, 2002 at 02:47:42AM -0500, Zephaniah E. Hull wrote:
> This is going to generate spurious events when speaking the EXPS/2
> protocol from unpatched kernel HID layers, specificly
> drivers/input/mousedev.c generates the wheel data incorrectly, I have a
> patch for that which I'm trying
On Mon, Oct 28, 2002 at 12:31:40PM +0100, Michel D?nzer wrote:
> On Mon, 2002-10-28 at 04:07, Marc Wilson wrote:
> > On Sun, Oct 27, 2002 at 07:25:51PM -0500, [EMAIL PROTECTED] wrote:
> > > 2) It is possible that this is a hardware limitation. Multiple-output
> > > video cards often don't support
[I'm not subscribed to debian-x, please CC me]
[Oh, and sorry for my bad english, i'm not a native speaker]
Hi all,
I'm writing this mail to you as Qt3 maintainer and part of the group which
tries to get KDE3 into the distribution.
KDE3 wasn't uploaded until now because the transistion to g++-3.
[I'm not subscribed to debian-x, please CC me]
[Oh, and sorry for my bad english, i'm not a native speaker]
Hi all,
I'm writing this mail to you as Qt3 maintainer and part of the group which
tries to get KDE3 into the distribution.
KDE3 wasn't uploaded until now because the transistion to g++-3.
On Mon, 2002-10-28 at 12:50, Herbert Xu wrote:
> On Mon, Oct 28, 2002 at 12:42:17PM +0100, Michel D?nzer wrote:
> >
> > See this thread:
> >
> > http://lists.debian.org/debian-powerpc/2002/debian-powerpc-200210/msg00260.html
>
> Well I don't see anything in there that shows that this is a kernel
On Mon, Oct 28, 2002 at 12:42:17PM +0100, Michel D?nzer wrote:
>
> See this thread:
>
> http://lists.debian.org/debian-powerpc/2002/debian-powerpc-200210/msg00260.html
Well I don't see anything in there that shows that this is a kernel
bug. What it does show is that some people are seeing this
On Mon, 2002-10-28 at 08:36, Herbert Xu wrote:
> On Mon, Oct 28, 2002 at 03:00:40AM +0100, Michel D?nzer wrote:
> >
> > Herbert, I think I've seen a kernel patch for #121335, and #156563 has
> > definitely been nailed down to the kernel input layer.
>
> If you mean the patch in the bug log, then
On Mon, 2002-10-28 at 04:07, Marc Wilson wrote:
> On Sun, Oct 27, 2002 at 07:25:51PM -0500, [EMAIL PROTECTED] wrote:
> > 2) It is possible that this is a hardware limitation. Multiple-output
> > video cards often don't support all features on secondary "heads".
>
> I always had the problem with m
On Mon, 2002-10-28 at 12:50, Herbert Xu wrote:
> On Mon, Oct 28, 2002 at 12:42:17PM +0100, Michel D?nzer wrote:
> >
> > See this thread:
> >
> > http://lists.debian.org/debian-powerpc/2002/debian-powerpc-200210/msg00260.html
>
> Well I don't see anything in there that shows that this is a kernel
On Mon, Oct 28, 2002 at 12:42:17PM +0100, Michel D?nzer wrote:
>
> See this thread:
>
> http://lists.debian.org/debian-powerpc/2002/debian-powerpc-200210/msg00260.html
Well I don't see anything in there that shows that this is a kernel
bug. What it does show is that some people are seeing this
On Mon, 2002-10-28 at 08:36, Herbert Xu wrote:
> On Mon, Oct 28, 2002 at 03:00:40AM +0100, Michel D?nzer wrote:
> >
> > Herbert, I think I've seen a kernel patch for #121335, and #156563 has
> > definitely been nailed down to the kernel input layer.
>
> If you mean the patch in the bug log, then
On Mon, 2002-10-28 at 04:07, Marc Wilson wrote:
> On Sun, Oct 27, 2002 at 07:25:51PM -0500, [EMAIL PROTECTED] wrote:
> > 2) It is possible that this is a hardware limitation. Multiple-output
> > video cards often don't support all features on secondary "heads".
>
> I always had the problem with m
Package: xlibmesa3
Version: 4.2.1-2
Severity: normal
Tags: patch
There are some minor bugs that cause the mesa library to access bad memory
when using special parameters. This fixes issues for
- Converting a 1x2 texture to a 16 bit per pixel format
- Uninitialized variables in some code path
-
Branden Robinson wrote:
> On Thu, Oct 17, 2002 at 05:42:04PM +0200, unai wrote:
> > Well, may it's better said X crashing...?
> >
> > Trying to open a powerpoint presentation file with
> > openoffice.org.1.0.1-5+woody crash X-Windows with a last line X-log:
> >
> > Fatal server error:
> > Beziers
On Sun, Oct 27, 2002 at 07:54:39PM -0500, [EMAIL PROTECTED] wrote:
> On Sat, Oct 26, 2002 at 09:20:05PM -0400, Zephaniah E. Hull wrote:
> > To make a long story short, X is wrong in how it parses the wheel data
> > for EXPS/2 protocol mice.
> >
> > 0xF and 0x1 are used to indicate the first wheel,
Package: xlibmesa3
Version: 4.2.1-2
Severity: normal
Tags: patch
There are some minor bugs that cause the mesa library to access bad memory
when using special parameters. This fixes issues for
- Converting a 1x2 texture to a 16 bit per pixel format
- Uninitialized variables in some code path
-
Branden Robinson wrote:
> On Thu, Oct 17, 2002 at 05:42:04PM +0200, unai wrote:
> > Well, may it's better said X crashing...?
> >
> > Trying to open a powerpoint presentation file with
> > openoffice.org.1.0.1-5+woody crash X-Windows with a last line X-log:
> >
> > Fatal server error:
> > Beziers
67 matches
Mail list logo
