Re: Radeon xvideo bug

2003-01-07 Thread Michel Dänzer
On Mon, 2003-01-06 at 22:32, csj wrote: I've experienced the following problem since I first installed my Radeon VE card under XFree86 4.X. The bug affects the playback of any video using the xvideo extension. When I play any video using any video player (e.g. xine, mplayer or vlc) and try

Re: Radeon xvideo bug

2003-01-07 Thread Warren Turkal
Install the CVS debs. If you need locations, search the archives of this list. I believe the servers were in Japan. The CVS Debs have this fixed. Warren -- Treasurer, GOLUM, Inc. http://www.golum.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble?

Bug#170508: fixed in upstream CVS

2003-01-07 Thread Branden Robinson
On Tue, Jan 07, 2003 at 11:43:43AM +0900, ISHIKAWA Mutsumi wrote: Log message: 700. BuildServersOnly fix when building on a system with no installed X headers or libraries (#5559, ISHIKAWA Mutsumi). Modified files: xc/config/cf/: xfree86.cf This problem is

Bug#175618: xdm fails to start X

2003-01-07 Thread Branden Robinson
severity 175618 normal tag 175618 + moreinfo unreproducible thanks On Mon, Jan 06, 2003 at 08:39:28PM -0500, Alex Coventry wrote: Package: xdm Version: 4.2.1-4 Severity: grave Justification: renders package unusable the init.d xdm script fails to start X. xdm from the command line also

Re: Bug#175618: xdm fails to start X

2003-01-07 Thread Alex Coventry
below is the output of the commands you suggested, after attempting to run xdm again. there are no processes with the name xdm, and the contents of the Xservers file looks sane. the modification time on that file is from Dec 8 last year. between then and last night, when i ran into this

Bug#175618: marked as done (xdm fails to start X)

2003-01-07 Thread Debian Bug Tracking System
Your message dated Tue, 7 Jan 2003 14:22:50 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#175618: xdm fails to start X 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 the case it is now your

Bug#173849: xfs: [type1] rasterization library handles oversized font requests very poorly

2003-01-07 Thread Juliusz Chroboczek
The current Type 1 rasteriser is being obsoleted. In the default 4.3 installation, it will only be used for CIDFonts, and I hope to kill it completely in a future release. Life is short, and I do not intend to fix this bug myself, although I'll be glad to accept a patch that does.

Bug#168794: support of synatyc touchpad

2003-01-07 Thread Juliusz Chroboczek
Would you be so kind as to write to the driver's authors and ask them why they don't get their driver included in the upstream XFree86 tree. Thanks, Juliusz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact

Re: Radeon xvideo bug

2003-01-07 Thread Nikita V. Youshchenko
I've experienced the following problem since I first installed my Radeon VE card under XFree86 4.X. The bug affects the playback of any video using the xvideo extension. When I play any video using any video player (e.g. xine, mplayer or vlc) and try to minimize the application, a freeze

Re: Radeon xvideo bug

2003-01-07 Thread Scott Henson
On Tue, 2003-01-07 at 01:09, Nikita V. Youshchenko wrote: I've experienced the following problem since I first installed my Radeon VE card under XFree86 4.X. The bug affects the playback of any video using the xvideo extension. When I play any video using any video player (e.g. xine,

Re: Radeon xvideo bug

2003-01-07 Thread Michel Dänzer
On Mon, 2003-01-06 at 22:32, csj wrote: I've experienced the following problem since I first installed my Radeon VE card under XFree86 4.X. The bug affects the playback of any video using the xvideo extension. When I play any video using any video player (e.g. xine, mplayer or vlc) and try

Re: Radeon xvideo bug

2003-01-07 Thread Warren Turkal
Install the CVS debs. If you need locations, search the archives of this list. I believe the servers were in Japan. The CVS Debs have this fixed. Warren -- Treasurer, GOLUM, Inc. http://www.golum.org

Processed: Re: Bug#175618: xdm fails to start X

2003-01-07 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: severity 175618 normal Bug#175618: xdm fails to start X Severity set to `normal'. tag 175618 + moreinfo unreproducible Bug#175618: xdm fails to start X There were no tags set. Tags added: moreinfo, unreproducible thanks Stopping processing here.

Bug#170508: fixed in upstream CVS

2003-01-07 Thread Branden Robinson
On Tue, Jan 07, 2003 at 11:43:43AM +0900, ISHIKAWA Mutsumi wrote: Log message: 700. BuildServersOnly fix when building on a system with no installed X headers or libraries (#5559, ISHIKAWA Mutsumi). Modified files: xc/config/cf/: xfree86.cf This problem is

Bug#175618: xdm fails to start X

2003-01-07 Thread Branden Robinson
severity 175618 normal tag 175618 + moreinfo unreproducible thanks On Mon, Jan 06, 2003 at 08:39:28PM -0500, Alex Coventry wrote: Package: xdm Version: 4.2.1-4 Severity: grave Justification: renders package unusable the init.d xdm script fails to start X. xdm from the command line also

Re: Bug#175618: xdm fails to start X

2003-01-07 Thread Alex Coventry
below is the output of the commands you suggested, after attempting to run xdm again. there are no processes with the name xdm, and the contents of the Xservers file looks sane. the modification time on that file is from Dec 8 last year. between then and last night, when i ran into this

Bug#175618: marked as done (xdm fails to start X)

2003-01-07 Thread Debian Bug Tracking System
Your message dated Tue, 7 Jan 2003 14:22:50 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#175618: xdm fails to start X 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 the case it is now your

Bug#173849: xfs: [type1] rasterization library handles oversized font requests very poorly

2003-01-07 Thread Juliusz Chroboczek
The current Type 1 rasteriser is being obsoleted. In the default 4.3 installation, it will only be used for CIDFonts, and I hope to kill it completely in a future release. Life is short, and I do not intend to fix this bug myself, although I'll be glad to accept a patch that does.