Bug#271235: Test of new nv driver

2004-09-16 Thread Eric Valette 

Fabio Massimo Di Nitto wrote:

hi Eric,

On Thu, 16 Sep 2004, Eric Valette wrote:



Just to try to be complete : 'xine -V xv toto.mpg' works when 'mplayer
-vo xv toto.mpg' fails. So, X-Video extension are not really broken but
something changed in a way that makes mplayer unhappy.



we did this test too. If you look carefully in xine log you should see
that it fails to open Xv port=. If you don't than the are
several breakages in several points *shrugs*


So I'm affraid, we indeed have several bugs. I also checked the log in 
the right click menu and fund no error.


xine --verbose=3 -V xv spot.mpg  | grep port

Number of supported pixmap formats: 7,
   Supported pixmap formats:
   Number of ports:   1
   Operations supported: PutImage
 Supported visuals:
   Number of ports:   32
   Operations supported: PutImage
 Supported visuals:
 No port attributes defined.
video_out_xv: using Xv port 61 from adaptor NV Video Overlay for 
hardware colorspace conversion and scaling.

video_out_xv: port attribute XV_COLORKEY (6) value is 66046
video_out_xv: port attribute XV_AUTOPAINT_COLORKEY (7) value is 0
video_out_xv: port attribute XV_BRIGHTNESS (5) value is -22
video_out_xv: port attribute XV_CONTRAST (4) value is 4074
video_out_xv: port attribute XV_SATURATION (3) value is 4074
video_out_xv: ignoring broken XV_HUE settings on NVidia 
cardsvideo_out_xv: this adaptor supports the yuy2 format.

video_out_xv: this adaptor supports the yv12 format.
audio_oss_out: supported modes are mono stereo (4-channel not enabled in 
xine config) (5-channel not enabled in xine config) (5.1-channel not 
enabled in xine config) (a/52-pass-through not enabled in xine 
config)thread created



-- eric

Bug#271259: xlibs: wrong altwin options listed in /etc/X11/xkb/rules/xfree86.lst

2004-09-16 Thread Denis Barbier 
tags 259740 + patch
thanks

On Sun, Sep 12, 2004 at 09:46:05PM +0200, Denis Barbier wrote:
> clone 259740 -1
> reassign -1 capplets
> retitle -1 gnome-keyboard-properties: altwin:meta_super must be renamed into 
> altwin:super_win
> thanks
> 
> This option surely comes from /etc/X11/xkb/rules/xfree86.lst, so I am
> reassigning this bug back to xlibs.

Here is a patch so that GNOME (and maybe other?) keyboard switchers do
not call erroneous altwin:meta_super and altwin:meta_hyper options.
Can I commit it?

Denis
$Id$

Fix xfree86.xml and xfree86.lst to reflect the current XKB state.
The most important change is that non-existing altwin:meta_super and
altwin:meta_hyper options are fixed, which closes #271259.

Few options have not been listed because they seem to be useless:
  sapmi layout
  lv3:ralt_switch_multikey

diff -ruN xc-old/programs/xkbcomp/rules/xfree86.lst 
xc/programs/xkbcomp/rules/xfree86.lst
--- xc-old/programs/xkbcomp/rules/xfree86.lst   2004-09-16 21:50:36.0 
+
+++ xc/programs/xkbcomp/rules/xfree86.lst   2004-09-16 22:30:40.0 
+
@@ -144,7 +144,9 @@
   is   Icelandic
   iu   Inuktitut
   ir   Iranian
+  ie   Irish
   il   Israeli
+  il_phonetic  Israeli (phonetic)
   it   Italian
   jp   Japanese
   kan  Kannada
@@ -198,7 +200,8 @@
 
 ! option
   grp  Group Shift/Lock behavior
-  grp:switch   R-Alt switches group while pressed
+  grp:lswitch  Left Alt key switches group while pressed
+  grp:switch   Right Alt key switches group while pressed
   grp:lwin_switch  Left Win-key switches group while pressed
   grp:rwin_switch  Right Win-key switches group while pressed
   grp:win_switch   Both Win-keys switch group while pressed
@@ -225,6 +228,7 @@
   lv3:win_switch   Press any of Win-keys to choose 3rd level
   lv3:lwin_switch  Press Left Win-key to choose 3rd level
   lv3:rwin_switch  Press Right Win-key to choose 3rd level
+  lv3:ralt_switch  Press Right Alt-key to choose 3rd level
   ctrl Control Key Position
   ctrl:nocaps  Make CapsLock an additional Control
   ctrl:swapcapsSwap Control and Caps Lock
@@ -245,8 +249,8 @@
   altwin:meta_alt  Alt and Meta on the Alt keys (default).
   altwin:meta_win  Meta is mapped to the Win-keys.
   altwin:left_meta_win Meta is mapped to the left Win-key.
-  altwin:meta_superSuper is mapped to the Win-keys (default).
-  altwin:meta_hyperHyper is mapped to the Win-keys.
+  altwin:super_win Super is mapped to the Win-keys (default).
+  altwin:hyper_win Hyper is mapped to the Win-keys.
 
   compose:ralt Right Alt is Compose
   compose:rwin Right Win-key is Compose
diff -ruN xc-old/programs/xkbcomp/rules/xfree86.xml 
xc/programs/xkbcomp/rules/xfree86.xml
--- xc-old/programs/xkbcomp/rules/xfree86.xml   2004-09-16 21:50:36.0 
+
+++ xc/programs/xkbcomp/rules/xfree86.xml   2004-09-16 22:37:31.0 
+
@@ -276,8 +276,14 @@
 
 
   
+hp5181
+Hewlett-Packard 5181 Internet Keyboard
+  
+
+
+  
 hpxe3gc
-Hewlett-Packard Omnibook XE3 GC
+Hewlett-Packard Omnibook XE3 GC, GD, GE and Pavilion 
N5xxx
   
 
 
@@ -288,6 +294,12 @@
 
 
   
+hpxe4xxx
+Hewlett-Packard Omnibook XE4xxx and ZE4xxx
+  
+
+
+  
 hpxt1000
 Hewlett-Packard Omnibook XT1000
   
@@ -306,6 +318,12 @@
 
 
   
+hp5xx
+Hewlett-Packard Omnibook 5xx
+  
+
+
+  
 honeywell_euroboard
 Honeywell Euroboard
   
@@ -905,6 +923,13 @@
 
 
   
+hr_US
+Croatian (US)
+  
+  
+
+
+  
 cz
 Czech
 чехшка
@@ -1033,14 +1058,6 @@
 
 
   
-ir
-Iranian
-ЀарсО
-  
-  
-
-
-  
 fi
 Finnish
 фОМлаМЎска
@@ -1431,6 +1448,50 @@
 
 
   
+ir
+Iranian
+ЀарсО
+  
+  
+
+
+  
+ie
+Irish
+  
+  
+
+  
+CloGaelach
+ie(CloGaelach) -  No decription
+CloGaelach
+  
+
+
+  
+CloGaelachLaptop
+ie(CloGaelachLaptop) -  No decription
+CloGaelach Ўля МастПльМых 
ПК
+  
+
+
+  
+UnicodeExpert
+ie(UnicodeExpert) -  No decription
+уМОкПЎ
+  
+
+
+  
+laptop
+ie(laptop) -  No decription
+Ўля МастПльМых 
ПК
+  
+
+  
+
+
+  
 il
 Israeli
 Озраелска
@@ -1455,6 +1516,13 @@
 
 
   
+

Processed: Re: Bug#271259: xlibs: wrong altwin options listed in /etc/X11/xkb/rules/xfree86.lst

2004-09-16 Thread Debian Bug Tracking System 
Processing commands for [EMAIL PROTECTED]:

> tags 259740 + patch
Bug#259740: xlibs: Windows key no longer treated as modifer, just as Super_L
Tags were: upstream
Tags added: patch

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Bug#255286: Meta has become alt?

2004-09-16 Thread Denis Barbier 
On Thu, Sep 16, 2004 at 11:23:40PM +0200, Denis Barbier wrote:
[...]
> The attached patch fixes (2) by stopping scanning modifiers list when
> a modifier key is found,

Here it is.

Denis
--- emacs-21.3/src/xterm.c.orig 2004-09-14 19:06:11.0 +0200
+++ emacs-21.3/src/xterm.c  2004-09-16 22:23:24.0 +0200
@@ -6380,8 +6380,11 @@
  Alt keysyms are on.  */
   {
 int row, col;  /* The row and column in the modifier table.  */
+int found_alt_or_meta;
 
 for (row = 3; row < 8; row++)
+{
+  found_alt_or_meta = 0;
   for (col = 0; col < mods->max_keypermod; col++)
{
  KeyCode code
@@ -6403,33 +6406,44 @@
  {
  case XK_Meta_L:
  case XK_Meta_R:
+   found_alt_or_meta = 1;
dpyinfo->meta_mod_mask |= (1 << row);
break;
 
  case XK_Alt_L:
  case XK_Alt_R:
+   found_alt_or_meta = 1;
dpyinfo->alt_mod_mask |= (1 << row);
break;
 
  case XK_Hyper_L:
  case XK_Hyper_R:
-   dpyinfo->hyper_mod_mask |= (1 << row);
+   if (!found_alt_or_meta)
+ dpyinfo->hyper_mod_mask |= (1 << row);
+   code_col = syms_per_code;
+   col = mods->max_keypermod;
break;
 
  case XK_Super_L:
  case XK_Super_R:
-   dpyinfo->super_mod_mask |= (1 << row);
+   if (!found_alt_or_meta)
+ dpyinfo->super_mod_mask |= (1 << row);
+   code_col = syms_per_code;
+   col = mods->max_keypermod;
break;
 
  case XK_Shift_Lock:
/* Ignore this if it's not on the lock modifier.  */
-   if ((1 << row) == LockMask)
+   if (!found_alt_or_meta && ((1 << row) == LockMask))
  dpyinfo->shift_lock_mask = LockMask;
+   code_col = syms_per_code;
+   col = mods->max_keypermod;
break;
  }
  }
  }
}
+}
   }
 
   /* If we couldn't find any meta keys, accept any alt keys as meta keys.  */

Bug#255286: Meta has become alt?

2004-09-16 Thread Denis Barbier 
On Wed, Sep 15, 2004 at 01:29:12AM +0200, Denis Barbier wrote:
> I am not an expert, know nothing about this spec and so read it.
> All I found is:
>   Clients should determine the meaning of a modifier bit from the
>   KeySyms being used to control it.
> My understanding is that from (x)emacs authors point of view, if
> mod4 is bound to Hyper and Super keysyms, client applications
> cannot guess what this modifier is for.
> But this quoted sentence is too vague, and can also be read as:
> "One cannot assume that mod1 is Alt or mod4 is Super, so client
>  applications should check the KeySym returned by the X server."
> The right Keysym can be chosen by applying the rules explained
> above, when xmodmap output was discussed.

Here are some clarifications:
 1. If a key is bound to several modifiers (say mod1 and mod4 contain
Super_L), then Super_L activates both modifiers, which is pretty
useless (and harmful).

 2. If different keys are bound to the same modifier (say Super_L and
Hyper_L to mod4), client applications cannot determine with core X
protocol if Super_L or Hyper_L was pressed/released when they receive
an event and mod4 is active.

With either scenario (1) or (2), emacs is unusable.  XKB configuration
can lead to (2) because of the so-called fake keys.  This is not a bug,
but a feature, XKB-aware applications can take advantage of them.
Any fix to let emacs away of (2) is better than the current situation,
and it is trivial: emacs should not accept to bind different keys to the
same modifier.  (Except for the Meta/Alt keys, see below)

Fixing (1) is less trivial, and normally XKB should never produce
such situations.  So I did not try to fix this uncommon situation
in order to have a smaller and easier to read patch.


But there is a problem with this paragraph, because when trying to
fix these modifier bugs in previous XFree86 releases, I added a
patch which can let XKB add Meta keys to mod1 and mod4 lists with
altwin:meta_win or altwin:left_meta_win options.
This patch was sent to http://bugzilla.xfree86.org/attachment.cgi?id=1197
and need to be reverted, I filed #1473 for that, and this issue is
discussed at https://listserv.bat.ru:8100/Lists/xkb/Message/232.html
Why Meta keys are added to both modifiers can easily be tracked down
with the small C file I sent in the previous post.
Hopefully next xlibs upload will fix this problem, so ignore it
in this bugreport.


The attached patch fixes (2) by stopping scanning modifiers list when
a modifier key is found,  In order to exactly reproduce the current
Alt/Meta mess, some more lines of code were needed.
I am not able to build emacs21 on my machine, so this patch was only
tested on the C file I sent in the previous post, but am pretty
confident that it works as expected.

As you can see, this patch is harmless, no working configuration can
be broken by it.  Can you please apply this patch so that emacs works
out of the box with recent XFree86 releases? 

Denis

X Strike Force XFree86 SVN commit: r1819 - in branches/4.1.0/woody/debian: . patches

2004-09-16 Thread X Strike Force SVN Repository Admin 
Author: branden
Date: 2004-09-16 16:15:18 -0500 (Thu, 16 Sep 2004)
New Revision: 1819

Added:
   branches/4.1.0/woody/debian/patches/076_SECURITY_libXpm_vulnerabilities.diff
Modified:
   branches/4.1.0/woody/debian/changelog
Log:
Security update release.  Resolves the following issues:
+ CAN-2004-0687: stack overflows in libXpm
+ CAN-2004-0688: integer overflows in libXpm


Modified: branches/4.1.0/woody/debian/changelog
===
--- branches/4.1.0/woody/debian/changelog   2004-09-15 11:56:07 UTC (rev 
1818)
+++ branches/4.1.0/woody/debian/changelog   2004-09-16 21:15:18 UTC (rev 
1819)
@@ -1,3 +1,11 @@
+xfree86 (4.1.0-16woody4) stable-security; urgency=high
+
+  * Security update release.  Resolves the following issues:
++ CAN-2004-0687: stack overflows in libXpm
++ CAN-2004-0688: integer overflows in libXpm
+
+ -- Branden Robinson <[EMAIL PROTECTED]>  Thu, 16 Sep 2004 16:13:56 -0500
+
 xfree86 (4.1.0-16woody3) stable-security; urgency=high
 
   * Security update release.  Resolves the following issues:

Added: 
branches/4.1.0/woody/debian/patches/076_SECURITY_libXpm_vulnerabilities.diff
===
--- 
branches/4.1.0/woody/debian/patches/076_SECURITY_libXpm_vulnerabilities.diff
2004-09-15 11:56:07 UTC (rev 1818)
+++ 
branches/4.1.0/woody/debian/patches/076_SECURITY_libXpm_vulnerabilities.diff
2004-09-16 21:15:18 UTC (rev 1819)
@@ -0,0 +1,522 @@
+$Id$
+
+Fix several security flaws in the Xpm library.  Resolves CAN-2004-0687 (libXpm
+stack overflows) and CAN-2004-0688 (libXpm integer overflows).
+
+The following text is by Chris Evans.
+
+libXpm multiple image parsing flaws
+===
+
+Programs affected: libXpm, and any programs which use libXpm to decode XPM
+files.  For example, the GIMP seems to use libXpm.
+
+Severity: Compromise of account used to browse malicious XPM file.
+
+This advisory lists code flaws discovered by inspection of the libXpm code.
+The specific version of libXpm discussed is the release that comes with the
+initial X.ORG X11 system source code release.  However, these flaws seem to
+exist in older versions.
+
+Flaw 1. Stack-based overflow in xpmParseColors (parse.c).
+
+Careless use of strcat() in both the XPMv1 and XPMv2/3 parsing code leads
+to a stack based overflow that should be exploitable.  There are minor
+complications due to stack layout; the buffer being overflowed in fact
+typically overflows into another buffer that is used to populate the
+overflowed buffer.  This should not prevent exploitation, however.
+
+Flaw 2. Integer overflow allocating colorTable in xpmParseColors (parse.c)
+-- probably a crashable but not exploitable offence.  Here:
+
+colorTable = (XpmColor *) XpmCalloc(ncolors, sizeof(XpmColor));
+
+ncolors would seem to come from the (untrusted) XPM file.
+
+In fact, multiple integer overflow problems seem to exist.  Some may well
+be exploitable.  Note that the following may not be an exhaustive list:
+
+a) XpmCreateImageFromXpmImage: multiple possible overflow, e.g.:
+image_pixels = (Pixel *) XpmMalloc(sizeof(Pixel) * image->ncolors);
+   (ncolors is user-supplied)
+
+b) CreateXImage:
+*image_return = XCreateImage(display, visual, depth, format, 0, 0,
+ width, height, bitmap_pad, 0);
+   (width and height are user-supplied, possibly other variables too)
+
+c) ParsePixels:
+iptr2 = (unsigned int *) XpmMalloc(sizeof(unsigned int) * width * 
height);
+   (width and height are user-supplied)
+
+d) ParseAndPutPixels and ParsePixels:
+cidx[char1][(unsigned char)colorTable[a].string[1]] = a + 1;
+(possibly, char1 might be negative, and access the cidx array out of 
bounds)
+
+Flaw 3.  Stack overflow reading pixel values in ParseAndPutPixels
+(create.c) as well as ParsePixels (parse.c).  Should be exploitable.
+
+A user-supplied number of bytes are stuffed into a fixed-size buffer 
(typically
+8192 bytes).  The user gets to choose how many bytes to put into this
+buffer via the "number of bytes per pixel" XPM value.
+
+This patch by Matthieu Herrb.
+
+diff -urN xc/extras/Xpm~/lib/Attrib.c xc/extras/Xpm/lib/Attrib.c
+--- xc/extras/Xpm~/lib/Attrib.c1999-01-11 08:23:09.0 -0500
 xc/extras/Xpm/lib/Attrib.c 2004-09-15 16:30:40.0 -0500
+@@ -35,7 +35,7 @@
+ #include "XpmI.h"
+ 
+ /* 3.2 backward compatibility code */
+-LFUNC(CreateOldColorTable, int, (XpmColor *ct, int ncolors,
++LFUNC(CreateOldColorTable, int, (XpmColor *ct, unsigned int ncolors,
+XpmColor ***oldct));
+ 
+ LFUNC(FreeOldColorTable, void, (XpmColor **colorTable, int ncolors));
+@@ -46,12 +46,15 @@
+ static int
+ CreateOldColorTable(ct, ncolors, oldct)
+ XpmColor *ct;
+-int ncolors;
+

Bug#271993: [xserver-xfree86] "via" driver's ddc breaks with my monitor

2004-09-16 Thread Martijn van de Streek 
Package: xserver-xfree86
Version: 4.3.0.dfsg.1-4
Severity: normal

I have a very cheap, old monitor (from "Smile"), which doesn't work
right with the "via" driver (the driver doesn't fall back to the values
I specified in the XF85Config-4 when DDC returns "0", or something like
that?)

The monitor seems to support DDC2 (there's information that looks like
that in the log, even though get-edid can't find any, and X also works
fine after running read-edid once, because subsequent DDC transfers by X
fail if get-edid has been run)). In the list of "supported modes",
[EMAIL PROTECTED] is mentioned.

If I try to use a 1024x768 mode however, it won't work, and just fall
back to 640x480 (which always works). If I unplug the monitor (turning
it off is not enough) from the computer, X starts fine in 1024x768 mode,
and continues to work after I plug in the monitor.

I've attached my X config and XFree86.0.log for both the "with-monitor" and
"monitorless" startup modes.

Martijn
-- 
You mean it’s not supposed to do that?
# XF86Config-4 (XFree86 X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the XF86Config-4 manual page.
# (Type "man XF86Config-4" at the shell prompt.)
#
# This file is automatically updated on xserver-xfree86 package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xfree86
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following commands as root:
#
#   cp /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.custom
#   md5sum /etc/X11/XF86Config-4 > /var/lib/xfree86/XF86Config-4.md5sum
#   dpkg-reconfigure xserver-xfree86
Section "Files"
FontPath"unix/:7100"# local font server
# if the local font server has problems, we can fall back on these
FontPath"/usr/lib/X11/fonts/misc"
FontPath"/usr/lib/X11/fonts/cyrillic"
FontPath"/usr/lib/X11/fonts/100dpi/:unscaled"
FontPath"/usr/lib/X11/fonts/75dpi/:unscaled"
FontPath"/usr/lib/X11/fonts/Type1"
FontPath"/usr/lib/X11/fonts/CID"
FontPath"/usr/lib/X11/fonts/Speedo"
FontPath"/usr/lib/X11/fonts/100dpi"
FontPath"/usr/lib/X11/fonts/75dpi"
EndSection
Section "Module"
Load"GLcore"
Load"bitmap"
Load"dbe"
Load"ddc"
Load"dri"
Load"extmod"
Load"freetype"
Load"glx"
Load"int10"
Load"record"
Load"speedo"
Load"type1"
Load"vbe"
EndSection
Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "keyboard"
Option  "CoreKeyboard"
Option  "XkbRules"  "xfree86"
Option  "XkbModel"  "chicony9885"
Option  "XkbLayout" "us"
Option  "XkbOptions""compose:menu"
EndSection
Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
Option  "CorePointer"
Option  "Device""/dev/input/mice"
Option  "Protocol"  "ImPS/2"
Option  "ZAxisMapping"  "4 5"
EndSection
Section "Device"
Identifier  "VIA Technologies, Inc. VT8623 [Apollo CLE266] 
integrated CastleRock graphics"
Driver  "via"
EndSection
Section "Monitor"
Identifier  "Generic Monitor"
HorizSync   30-60
VertRefresh 43-72
Option  "DPMS"
EndSection
Section "Screen"
Identifier  "Default Screen"
Device  "VIA Technologies, Inc. VT8623 [Apollo CLE266] 
integrated CastleRock graphics"
Monitor "Generic Monitor"
DefaultDepth24
SubSection "Display"
Depth   1
Modes   "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth   4
Modes   "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth   8
Modes   "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth   15
Modes   "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth   16
Modes   "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth   24
Modes   "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Section "ServerLayout"
Identifier  "Default Layout"
Screen

Bug#6682: Norton AntiVirus detected a virus in a message you sent. The inf ected attachment was deleted.

2004-09-16 Thread NAV for Microsoft Exchange-EMAIL 
Recipient of the infected attachment:  Clienti GeniaLLOYD\Posta in arrivo
Subject of the message:  Mail Delivery (failure [EMAIL PROTECTED])
One or more attachments were deleted
  Attachment message.scr was Deleted for the following reasons:
Virus [EMAIL PROTECTED] was found.
<>

Processed: Re: Bug#270714: Duplicate of 271235

2004-09-16 Thread Debian Bug Tracking System 
Processing commands for [EMAIL PROTECTED]:

> reassign 270714 xserver-xfree86
Bug#270714: Video not working with XVideo
Bug reassigned from package `vlc' to `xserver-xfree86'.

> severity 270714 important
Bug#270714: Video not working with XVideo
Severity set to `important'.

> merge 270714 271235
Bug#270714: Video not working with XVideo
Bug#271235: xserver-xfree86: [nv] XVideo fails silently (but visually) in 
mplayer
Merged 270714 271235.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Bug#271235: (no subject)

2004-09-16 Thread DEGAND Nicolas 
I have the same problem with my GeForce FX 5900. I have not had the time yet 
to test the new package. I have this problem with mplayer and vlc, but it 
works with kaffeine;

-- 
Nicolas DEGAND

Bug#271235: Test of new nv driver

2004-09-16 Thread Fabio Massimo Di Nitto 

hi Eric,

On Thu, 16 Sep 2004, Eric Valette wrote:

>
> Just to try to be complete : 'xine -V xv toto.mpg' works when 'mplayer
> -vo xv toto.mpg' fails. So, X-Video extension are not really broken but
> something changed in a way that makes mplayer unhappy.

we did this test too. If you look carefully in xine log you should see
that it fails to open Xv port=. If you don't than the are
several breakages in several points *shrugs*

Thanks
Fabio

-- 
 fajita: step one
 Whatever the problem, step one is always to look in the error log.
 fajita: step two
 When in danger or in doubt, step two is to scream and shout.

Bug#271235: [Fwd: Re: No video output after upgrading a Debian/unstable system]

2004-09-16 Thread Valette Eric 

At least you can see that I'm not alone with this problem...

--
   __
  /  `  Eric Valette
 /--   __  o _. 6 rue Paul Le Flem
(___, / (_(_(__ 35740 Pace

Tel: +33 (0)2 99 85 26 76   Fax: +33 (0)2 99 85 26 76
E-mail: [EMAIL PROTECTED]



--- Begin Message ---
Op Wed, 15 Sep 2004 14:06:27 +0200, schreef Valette Eric de volgende
woorden:

> J.S.Sahambi wrote:
>> I have been using Mplayer 1.0pre5 without any problem. Two days back I
>> upgarded my debian/unstable (2.4.26-1-686) with dselect and now when I
>> play a file with mplayer a window opens but there is no video. 
> 
> This is a known bug with the last nvidia drivers in debian unstable. One 
> solution is to downgrade the /usr/X11R6/lib/modules/drivers/nv_drv.o 
> using the one in sarge.
> 
> See :
> 
> 
> Work is underway to go forward instead of backward by using the X.org 
> version of the driver...

Ah thanks, that is why i can only play movies on my left screen
(ati) and not on my right one (nvidia).

Dirk


-- 
Richard M. Stallman, Linus Torvalds, and Donald E. Knuth engage in a discussion
on whose impact on the computerized world was the greatest.
Stallman: "God told me I have programmed the best editor in the world!"
Torvalds: "Well, God told *me* that I have programmed the best
operating system in the world!"
Knuth: "Wait, wait - I never said that."
-- Erik Meltzer, rec.humor.funny

--- End Message ---

Bug#269025: XV broken with the xorg driver

2004-09-16 Thread Lucas Nussbaum 
Hi,

It seems xv is broken with the driver from xorg (can't play videos
anymore with mplayer =)

The mplayer output is the same with the xorg driver than with the sarge
driver (I checked with diff).

Here are :
xvinfo-xorg.txt : xvinfo output with the xorg driver
xvinfo-sarge.txt : xvinfo output with the sarge driver
XF86Config-4 : my XFree86 config.
-- 
| Lucas Nussbaum
| [EMAIL PROTECTED][EMAIL PROTECTED]GPG: 1024D/023B3F4F |
| jabber: [EMAIL PROTECTED]   http://www.lucas-nussbaum.net |
| fingerprint: 075D 010B 80C3 AC68 BD4F B328 DA19 6237 023B 3F4F |
X-Video Extension version 2.2
screen #0
  Adaptor #0: "NV Video Overlay"
number of ports: 1
port base: 53
operations supported: PutImage 
supported visuals:
  depth 24, visualID 0x21
  depth 24, visualID 0x22
number of attributes: 9
  "XV_DOUBLE_BUFFER" (range 0 to 1)
  client settable attribute
  client gettable attribute (current value is 1)
  "XV_COLORKEY" (range 0 to 16777215)
  client settable attribute
  client gettable attribute (current value is 66046)
  "XV_AUTOPAINT_COLORKEY" (range 0 to 1)
  client settable attribute
  client gettable attribute (current value is 1)
  "XV_SET_DEFAULTS" (range 0 to 0)
  client settable attribute
  "XV_BRIGHTNESS" (range -512 to 511)
  client settable attribute
  client gettable attribute (current value is 0)
  "XV_CONTRAST" (range 0 to 8191)
  client settable attribute
  client gettable attribute (current value is 4096)
  "XV_SATURATION" (range 0 to 8191)
  client settable attribute
  client gettable attribute (current value is 4096)
  "XV_HUE" (range 0 to 360)
  client settable attribute
  client gettable attribute (current value is 0)
  "XV_ITURBT_709" (range 0 to 1)
  client settable attribute
  client gettable attribute (current value is 0)
maximum XvImage size: 2046 x 2046
Number of image formats: 4
  id: 0x32595559 (YUY2)
guid: 59555932--0010-8000-00aa00389b71
bits per pixel: 16
number of planes: 1
type: YUV (packed)
  id: 0x32315659 (YV12)
guid: 59563132--0010-8000-00aa00389b71
bits per pixel: 12
number of planes: 3
type: YUV (planar)
  id: 0x59565955 (UYVY)
guid: 55595659--0010-8000-00aa00389b71
bits per pixel: 16
number of planes: 1
type: YUV (packed)
  id: 0x30323449 (I420)
guid: 49343230--0010-8000-00aa00389b71
bits per pixel: 12
number of planes: 3
type: YUV (planar)
X-Video Extension version 2.2
screen #0
  Adaptor #0: "NV Video Overlay"
number of ports: 1
port base: 53
operations supported: PutImage 
supported visuals:
  depth 24, visualID 0x21
  depth 24, visualID 0x22
number of attributes: 9
  "XV_DOUBLE_BUFFER" (range 0 to 1)
  client settable attribute
  client gettable attribute (current value is 1)
  "XV_COLORKEY" (range 0 to 16777215)
  client settable attribute
  client gettable attribute (current value is 66046)
  "XV_AUTOPAINT_COLORKEY" (range 0 to 1)
  client settable attribute
  client gettable attribute (current value is 1)
  "XV_SET_DEFAULTS" (range 0 to 0)
  client settable attribute
  "XV_BRIGHTNESS" (range -512 to 511)
  client settable attribute
  client gettable attribute (current value is 0)
  "XV_CONTRAST" (range 0 to 8191)
  client settable attribute
  client gettable attribute (current value is 4096)
  "XV_SATURATION" (range 0 to 8191)
  client settable attribute
  client gettable attribute (current value is 4096)
  "XV_HUE" (range 0 to 360)
  client settable attribute
  client gettable attribute (current value is 0)
  "XV_ITURBT_709" (range 0 to 1)
  client settable attribute
  client gettable attribute (current value is 0)
maximum XvImage size: 2046 x 2046
Number of image formats: 4
  id: 0x32595559 (YUY2)
guid: 59555932--0010-8000-00aa00389b71
bits per pixel: 16
number of planes: 1
type: YUV (packed)
  id: 0x32315659 (YV12)
guid: 59563132--0010-8000-00aa00389b71
bits per pixel: 12
number of planes: 3
type: YUV (planar)
  id: 0x59565955 (UYVY)
guid: 55595659--0010-8000-00aa00389b71
bits per pixel: 16
number of planes: 1
type: YUV (packed)
  id: 0x30323449 (I420)
guid: 49343230--0010-8000-00aa00389b71
bits per pixel: 12
number of planes: 3
type: YUV (planar)
  Adaptor #1: "NV Video Blitter"
number of ports: 32