Bug#181815: marked as done (xlibs: [Xrender] bad length computation in XRenderCompositeString16()/XRenderCompositeString32())

2003-05-11 Thread Debian Bug Tracking System
Your message dated Sun, 11 May 2003 12:56:53 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#181815: fixed in xrender 0.8.1-1 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 yo

Bug#187187: marked as done (libxft2: using anti-aliased fonts with gnome-terminal causes BadValue X protocol error)

2003-05-11 Thread Debian Bug Tracking System
Your message dated Sun, 11 May 2003 12:56:53 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#181815: fixed in xrender 0.8.1-1 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 yo

Bug#186704: marked as done (libxft2: using anti-aliased fonts with gnome-terminal causes BadValue X protocol error)

2003-05-11 Thread Debian Bug Tracking System
Your message dated Sun, 11 May 2003 12:56:53 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#181815: fixed in xrender 0.8.1-1 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 yo

Bug#189019: marked as done (libxft2: Mozilla/Galeon crash when run over VNC link and RENDER extension not available; causes BadValue X protocol error)

2003-05-11 Thread Debian Bug Tracking System
Your message dated Sun, 11 May 2003 12:56:53 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#181815: fixed in xrender 0.8.1-1 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 yo

Bug#191071: marked as done (libxft2: using anti-aliased fonts with gnome-terminal causes BadValue X protocol error)

2003-05-11 Thread Debian Bug Tracking System
Your message dated Sun, 11 May 2003 12:56:53 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#181815: fixed in xrender 0.8.1-1 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 yo

Bug#186758: marked as done (libxft2: causes mozilla-xft to crash when browsing http://xinehq.de/ and http://www.linux.org.uk/diary/)

2003-05-11 Thread Debian Bug Tracking System
Your message dated Sun, 11 May 2003 12:56:53 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#181815: fixed in xrender 0.8.1-1 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 yo

Bug#182850: marked as done (xlibs: [Xrender] bad length computation in XRenderCompositeString16()/XRenderCompositeString32())

2003-05-11 Thread Debian Bug Tracking System
Your message dated Sun, 11 May 2003 12:56:53 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#181815: fixed in xrender 0.8.1-1 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 yo

Bug#188488: marked as done (libxft2: mozilla-xft crashes on several websites)

2003-05-11 Thread Debian Bug Tracking System
Your message dated Sun, 11 May 2003 12:56:53 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#181815: fixed in xrender 0.8.1-1 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 yo

Bug#191419: marked as done (libxft2: mozilla-xft crashes when viewing www.debian.org with BadValue X protocol error)

2003-05-11 Thread Debian Bug Tracking System
Your message dated Sun, 11 May 2003 12:56:53 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#181815: fixed in xrender 0.8.1-1 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 yo

Bug#191555: marked as done (libxft2: using anti-aliased fonts with gnome-terminal causes BadValue X protocol error)

2003-05-11 Thread Debian Bug Tracking System
Your message dated Sun, 11 May 2003 12:56:53 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#181815: fixed in xrender 0.8.1-1 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 yo

Bug#192930: xserver on pc used as xterminal fails to interact with xdm on server

2003-05-11 Thread Helge Hafting
Package: xserver-xfree86 Version: 4.2.1-6 I try running /usr/bin/X11/X -ac -query 10.0.0.3 -from 10.0.0.4 The xdm on 10.0.0.3 logs this: Sat May 10 19:34:33 2003 xdm info (pid 839): starting X server on mini:0 X Error of failed request: BadDrawable (invalid Pixmap or Window parameter) Major o

FontFilePriorityRegisterRenderer is unresolved

2003-05-11 Thread Mark Zimmerman
Greetings: Since updating my ThinkPad 560X running testing a few days ago, X will not start. The error is: Symbol FontFilePriorityRegisterRenderer from module /usr/X11R6/lib/modules/fonts/libxtt.a is unresolved! The full log file is attached. Thanks, -- Mark This is a pre-release version of XF