Bug#229628: ezmlm response
Hi! This is the ezmlm program. I'm managing the suse-linux-e@suse.com mailing list. I'm working for my owner, who can be reached at [EMAIL PROTECTED] Here is a list of the command addresses supported: Send mail to the following for info and FAQ for this list: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> To get messages 123 through 145 (a maximum of 100 per request), mail: <[EMAIL PROTECTED]> To get an index with subject and author for messages 123-456, mail: <[EMAIL PROTECTED]> To receive all messages with the same subject as message 12345, send an empty message to: <[EMAIL PROTECTED]> The messages do not really need to be empty, but I will ignore their content. Only the ADDRESS you send to is important. You can start a subscription for an alternate address, for example "[EMAIL PROTECTED]", just add a hyphen and your address (with '=' instead of '@') after the command word: <[EMAIL PROTECTED]> To stop subscription for this address, mail: <[EMAIL PROTECTED]> --- Administrative commands for the suse-linux-e list --- I can handle administrative requests automatically. Please do not send them to the list address! Instead, send your message to the correct command address: To subscribe to the list, send a message to: <[EMAIL PROTECTED]> To remove your address from the list, send a message to: <[EMAIL PROTECTED]> Send mail to the following for info and FAQ for this list: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> To get message 12 from the archive, send a message to: <[EMAIL PROTECTED]> The messages do not really need to be empty, but I will ignore their content. Only the ADDRESS you send to is important. You can start a subscription for an alternate address, for example "[EMAIL PROTECTED]", just add a hyphen and your address (with '=' instead of '@') after the command word: <[EMAIL PROTECTED]> To stop subscription for this address, mail: <[EMAIL PROTECTED]> In both cases, I'll send a confirmation message to that address. When you receive it, simply reply to it to complete your subscription. If despite following these instructions, you do not get the desired results, please contact my owner at [EMAIL PROTECTED] Please be patient, my owner is a lot slower than I am ;-) --- Enclosed is a copy of the request I received. Return-Path: <[EMAIL PROTECTED]> Received: (qmail 17228 invoked from network); 23 Apr 2004 05:10:16 - Received: from unknown (HELO hermes.suse.de) (195.135.221.8) by 0 with SMTP; 23 Apr 2004 05:10:16 - Received: from scanhost.suse.de (scanhost.suse.de [10.0.0.5]) by hermes.suse.de (Postfix) with ESMTP id 620B531B4A for <[EMAIL PROTECTED]>; Fri, 23 Apr 2004 07:10:16 +0200 (CEST) Received: by scanhost.suse.de (Postfix, from userid 0) id 578DE48628; Fri, 23 Apr 2004 07:10:16 +0200 (CEST) Delivered-To: virus-quarantine X-Quarantine-id: Received: from Cantor.suse.de (ns.suse.de [195.135.220.2]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by hermes.suse.de (Postfix) with ESMTP id 68A9E31B4A for <[EMAIL PROTECTED]>; Fri, 23 Apr 2004 07:05:30 +0200 (CEST) Received: from suse.com (languedoc-5-82-225-110-15.fbx.proxad.net [82.225.110.15]) by Cantor.suse.de (Postfix) with ESMTP id 8FFF84BCD31 for <[EMAIL PROTECTED]>; Fri, 23 Apr 2004 07:03:40 +0200 (CEST) From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Spamed? Date: Sat, 24 Apr 2004 06:00:50 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-Id: <[EMAIL PROTECTED]> X-AMaViS-Alert: INFECTED, message contains virus: Worm.SomeFool.P X-Converted-To-Plain-Text: from multipart/mixed by demime 1.1d X-Converted-To-Plain-Text: Alternative section used was text/plain I have visited this website and I found you in the spammer list. Is that true? [the SUSE virus scanner removed an attachment of type application/octet-stream which had a name of websitelist01.zip] [if you need the message in its original form including all attachments, please ask the SENDER for a version free of viruses]
X Strike Force XFree86 SVN commit: r1304 - in trunk/debian: . patches
Author: branden
Date: 2004-04-23 00:44:56 -0500 (Fri, 23 Apr 2004)
New Revision: 1304
Modified:
trunk/debian/changelog
trunk/debian/patches/000_stolen_from_HEAD.diff
Log:
Revert patch from XFree86 CVS upstream authored by David Dawes after the
XFree86 license. Reportedly, all changes by David Dawes to XFree86 CVS are
under the new copyright license whether there is any indication of this
fact or not.
changeset: reverts 1190
Modified: trunk/debian/changelog
===
--- trunk/debian/changelog 2004-04-21 19:01:41 UTC (rev 1303)
+++ trunk/debian/changelog 2004-04-23 05:44:56 UTC (rev 1304)
@@ -74,13 +74,6 @@
packages' config scripts, invoke the discover command such that an
abnormal exit on its part does not crash the script.
- * Fix loud chatter from Linux 2.6 such as: "atkbd.c: This is an XFree86 bug.
-It shouldn't access hardware directly." by performing KDKDBREP ioctl() on
-the correct file descriptor, avoiding the fallback method for changing the
-keyboard repeat rate that triggers this warning. Patch by David Dawes,
-from XFree86 CVS 2004-03-04 (XXX: POTENTIAL LICENSING PROBLEM). (Closes:
-#230204)
-
* Grab fixes to the X server's DIX events processing from XFree86 CVS
(none later than 2004-01-23).
+ Fix a potential hang in Xinerama caused by an uninitialized
Modified: trunk/debian/patches/000_stolen_from_HEAD.diff
===
--- trunk/debian/patches/000_stolen_from_HEAD.diff 2004-04-21 19:01:41 UTC
(rev 1303)
+++ trunk/debian/patches/000_stolen_from_HEAD.diff 2004-04-23 05:44:56 UTC
(rev 1304)
@@ -76,14 +76,6 @@
751. Fix some rules in en_US.UTF-8 Compose file (Bugzilla #1071,
Matthew Fischer).
-xc/programs/Xserver/hw/xfree86/os-support/linux/lnx_io.c @ 3.27
-xc/programs/Xserver/hw/xfree86/os-support/linux/lnx_kbd.c @ 1.6
- 6. Do the Linux KDKBDREP ioctl on the correct fd. This prevents the
- fallback that tries to directly program the keyboard repeat rate,
- and the related warning messages that recent Linux kernels generate
- (David Dawes).
-XXX: POTENTIAL LICENSE PROBLEM IN THE ABOVE
-
xc/programs/Xserver/dix/events.c @ 3.48
Fix a potential hang in Xinerama caused by an uninitialized
sprite.hotShape. [Mark Vojkovich]
@@ -738,8 +730,9 @@
}
if (versions[version_index].major_version > Dont_Check)
xc/programs/Xserver/hw/xfree86/os-support/linux/lnx_io.c~ 2004-03-26
14:02:57.0 -0500
-+++ xc/programs/Xserver/hw/xfree86/os-support/linux/lnx_io.c 2004-03-26
14:03:22.0 -0500
+diff -urN xc.orig/programs/Xserver/hw/xfree86/os-support/linux/lnx_io.c
xc/programs/Xserver/hw/xfree86/os-support/linux/lnx_io.c
+--- xc.orig/programs/Xserver/hw/xfree86/os-support/linux/lnx_io.c
2003-11-12 18:00:24.0 +1100
xc/programs/Xserver/hw/xfree86/os-support/linux/lnx_io.c 2003-11-12
18:01:33.0 +1100
@@ -67,6 +67,7 @@
* from util-linux-2.9t package */
@@ -748,45 +741,10 @@
#ifdef __sparc__
#include
#include
-@@ -80,7 +81,7 @@
- #endif
-
- static int
--KDKBDREP_ioctl_ok(int rate, int delay) {
-+KDKBDREP_ioctl_ok(int fd, int rate, int delay) {
- #if defined(KDKBDREP) && !defined(__sparc__)
- /* This ioctl is defined in but is not
- implemented anywhere - must be in some m68k patches. */
-@@ -89,7 +90,7 @@
-/* don't change, just test */
-kbdrep_s.rate = -1;
-kbdrep_s.delay = -1;
-- if (ioctl( 0, KDKBDREP, &kbdrep_s )) {
-+ if (ioctl( fd, KDKBDREP, &kbdrep_s )) {
-return 0;
-}
-
-@@ -104,7 +105,7 @@
-if (kbdrep_s.delay < 1)
- kbdrep_s.delay = 1;
-
-- if (ioctl( 0, KDKBDREP, &kbdrep_s )) {
-+ if (ioctl( fd, KDKBDREP, &kbdrep_s )) {
- return 0;
-}
-
-@@ -178,7 +179,7 @@
- delay = xf86Info.kbdDelay;
-
-
-- if(KDKBDREP_ioctl_ok(rate, delay)) /* m68k? */
-+ if(KDKBDREP_ioctl_ok(xf86Info.consoleFd, rate, delay)) /* m68k? */
- return;
-
- if(KIOCSRATE_ioctl_ok(rate, delay)) /* sparc? */
xc/programs/Xserver/hw/xfree86/os-support/linux/lnx_kbd.c~ 2004-03-26
14:03:00.0 -0500
-+++ xc/programs/Xserver/hw/xfree86/os-support/linux/lnx_kbd.c 2004-03-26
14:03:22.0 -0500
-@@ -93,14 +93,22 @@
+diff -urN xc.orig/programs/Xserver/hw/xfree86/os-support/linux/lnx_kbd.c
xc/programs/Xserver/hw/xfree86/os-support/linux/lnx_kbd.c
+--- xc.orig/programs/Xserver/hw/xfree86/os-support/linux/lnx_kbd.c
2003-11-12 18:00:24.0 +1100
xc/programs/Xserver/hw/xfree86/os-support/linux/lnx_kbd.c 2003-11-12
18:01:33.0 +1100
+@@ -93,12 +93,20 @@
/* kbd rate stuff based on kbdrate.c from Rik Faith <[EMAIL PROTECTED]> et.al.
* from util-linux-2.9t package */
@@ -806,29 +764,8 @@
+#endif
+
static int
--KDKBDREP_ioctl_ok(int rate, int delay) {
-+KDKBDREP_ioctl_ok(int fd, int rate, int delay) {
+ KDKBDREP_ioctl_ok(in
Bug#237895: Related to font servers
On Thu, Apr 22, 2004 at 12:14:55PM -0400, Anthony DeRobertis wrote: > On Tue, Apr 20, 2004 at 09:21:00PM -0500, Branden Robinson wrote: > > This looks like exactly the same pair of video cards the submitter had > > -- at the same PCI bus addresses, no less. > > > > What's *your* configuration? Please supply your XF86Config-4 and > > XFree86.0.log. > > Branden, you need more sleep... I am the submitter... > > You and I are the only two people who appear in the bug log. Hmmm. Since I don't take mind-altering drugs, maybe I should start. Sorry for the confusion. -- G. Branden Robinson|Religion is regarded by the common Debian GNU/Linux |people as true, by the wise as [EMAIL PROTECTED] |false, and by the rulers as useful. http://people.debian.org/~branden/ |-- Lucius Annaeus Seneca signature.asc Description: Digital signature
X Strike Force XFree86 SVN property change: propchange - r1190 svn:log
Author: branden Revision: 1190 Property Name: svn:log New Property Value: Grab patches from upstream CVS HEAD (not under X-Oz or XFree86 1.1 license) that fix loud chatter from Linux 2.6 such as: "atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.". + Do the Linux KDKBDREP ioctl on the correct fd. This prevents the fallback that tries to directly program the keyboard repeat rate, and the related warning messages that recent Linux kernels generate (David Dawes). (Closes: #230204) changeset: reverted by 1304
X Strike Force XFree86 SVN commit: r1305 - in trunk/debian: . patches
Author: branden
Date: 2004-04-23 01:00:04 -0500 (Fri, 23 Apr 2004)
New Revision: 1305
Added:
trunk/debian/patches/088_fix_keyboard_rate_ioctls.diff
Modified:
trunk/debian/changelog
Log:
Fix AT keyboard rate I/O controls by operating on the actual console file
descriptor, not on file descriptor zero (thanks, Keith Packard).
Suppresses warning messages from Linux 2.6. (Closes: #224909)
Modified: trunk/debian/changelog
===
--- trunk/debian/changelog 2004-04-23 05:44:56 UTC (rev 1304)
+++ trunk/debian/changelog 2004-04-23 06:00:04 UTC (rev 1305)
@@ -288,8 +288,12 @@
override current definitions of Alt keys or the Mod1 modifier map (thanks,
Denis Barbier). (Closes: #234081)
- -- Branden Robinson <[EMAIL PROTECTED]> Wed, 21 Apr 2004 13:46:08 -0500
+ * Fix AT keyboard rate I/O controls by operating on the actual console file
+descriptor, not on file descriptor zero (thanks, Keith Packard).
+Suppresses warning messages from Linux 2.6. (Closes: #224909)
+ -- Branden Robinson <[EMAIL PROTECTED]> Fri, 23 Apr 2004 00:58:44 -0500
+
xfree86 (4.3.0-7) unstable; urgency=medium
* Urgency due to fix for FTBFS. Yes -- I too am begging for it to stop.
Added: trunk/debian/patches/088_fix_keyboard_rate_ioctls.diff
===
--- trunk/debian/patches/088_fix_keyboard_rate_ioctls.diff 2004-04-23
05:44:56 UTC (rev 1304)
+++ trunk/debian/patches/088_fix_keyboard_rate_ioctls.diff 2004-04-23
06:00:04 UTC (rev 1305)
@@ -0,0 +1,50 @@
+$Id$
+
+Fix AT keyboard rate I/O controls by operating on the actual console file
+descriptor, not on file descriptor zero. Suppresses warning messages from
+Linux 2.6. See Debian #224909.
+
+This patch by Keith Packard.
+
+diff -urN xc/programs/Xserver/hw/xfree86/os-support/linux~/lnx_io.c
xc/programs/Xserver/hw/xfree86/os-support/linux/lnx_io.c
+--- xc/programs/Xserver/hw/xfree86/os-support/linux~/lnx_io.c 2004-04-23
00:45:50.0 -0500
xc/programs/Xserver/hw/xfree86/os-support/linux/lnx_io.c 2004-04-23
00:48:01.0 -0500
+@@ -92,7 +92,7 @@
+/* don't change, just test */
+kbdrep_s.rate = -1;
+kbdrep_s.delay = -1;
+- if (ioctl( 0, KDKBDREP, &kbdrep_s )) {
++ if (ioctl( xf86Info.consoleFd, KDKBDREP, &kbdrep_s )) {
+return 0;
+}
+
+@@ -107,7 +107,7 @@
+if (kbdrep_s.delay < 1)
+ kbdrep_s.delay = 1;
+
+- if (ioctl( 0, KDKBDREP, &kbdrep_s )) {
++ if (ioctl( xf86Info.consoleFd, KDKBDREP, &kbdrep_s )) {
+ return 0;
+}
+
+diff -urN xc/programs/Xserver/hw/xfree86/os-support/linux~/lnx_kbd.c
xc/programs/Xserver/hw/xfree86/os-support/linux/lnx_kbd.c
+--- xc/programs/Xserver/hw/xfree86/os-support/linux~/lnx_kbd.c 2004-04-23
00:45:50.0 -0500
xc/programs/Xserver/hw/xfree86/os-support/linux/lnx_kbd.c 2004-04-23
00:48:01.0 -0500
+@@ -120,7 +120,7 @@
+/* don't change, just test */
+kbdrep_s.rate = -1;
+kbdrep_s.delay = -1;
+- if (ioctl( 0, KDKBDREP, &kbdrep_s )) {
++ if (ioctl( xf86Info.consoleFd, KDKBDREP, &kbdrep_s )) {
+return 0;
+}
+
+@@ -135,7 +135,7 @@
+if (kbdrep_s.delay < 1)
+ kbdrep_s.delay = 1;
+
+- if (ioctl( 0, KDKBDREP, &kbdrep_s )) {
++ if (ioctl( xf86Info.consoleFd, KDKBDREP, &kbdrep_s )) {
+ return 0;
+}
+
Property changes on: trunk/debian/patches/088_fix_keyboard_rate_ioctls.diff
___
Name: svn:keywords
+ Id
Bug#179407: xterm: not only bold fonts do not work with widechars
On Thu, 22 Apr 2004, Thomas Dickey wrote: > It really sounds as if you are running into more/less expected problems > with applications (not particularly xterm) that do not work with UTF-8. Sure - as I said my belover MC is one of them. BUt I wanted to give the transition a start, once Debian changelogs start loocking fancy on my side because of UTF-8 codings. > For instance, I see that the Debian package for mc is built using the > internal version of slang (and to satisfy some issue with gpm, also > ncurses - which can be confusing). Yes. Also manpages loocked strange but I suspected that it is connected to the xterm problems, but I'm not sure. > While there is an unofficial patch for slang to handle UTF-8, I'm told > that it is incomplete and not very robust. Without that patch, slang > can handle only 8-bit encodings (such as the ISO-8859-1 to ISO-8859-15). > In UTF-8, the characters in the range 160-255 are not sent as a single > byte but as two or more. If the application does not know how to do > this, the terminal running in UTF-8 mode is likely to treat those as > incomplete sequences and doesn't show the characters that were intended. Well I just regard my first attempt to switch to UTF-8 as failed and went back to my normal work, waiting for further enhancements. On the other hand I think we should clarify why the resource setting of *utf8: 2 differs from -u8 command line option. If I understand the manual right this should not be the case. Kind regards Andreas.
Processed: tagging 224909
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.7.95.1 > # fixed in Debian X Strike Force XFree86 repository; to view, run "svn diff > -r 1304:1305 svn://necrotic.deadbeast.net/xfree86" > tags 224909 + pending Bug#224909: xserver-xfree86: [core server] kernel complains about XFree86 accessing hardware directly Tags were: pending fixed-upstream sid patch upstream Bug#230204: xserver-xfree86: some keys on Logitech Cordless MX not recognized; Linux kernel 2.6.2 spews noise (atkbd.c) Bug#230636: xserver-xfree86: makes kernel say 'This is an XFree86 bug. It shouldn't access hardware directly.' Bug#239179: xserver-xfree86: kernel says 'This is an XFree86 bug. It shouldn't access hardware directly.' Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#179407: xterm: not only bold fonts do not work with widechars
On Fri, Apr 23, 2004 at 07:29:04AM +0200, Andreas Tille wrote: > On Thu, 22 Apr 2004, Thomas Dickey wrote: > > > It really sounds as if you are running into more/less expected problems > > with applications (not particularly xterm) that do not work with UTF-8. > Sure - as I said my belover MC is one of them. BUt I wanted to give > the transition a start, once Debian changelogs start loocking fancy on > my side because of UTF-8 codings. > > > For instance, I see that the Debian package for mc is built using the > > internal version of slang (and to satisfy some issue with gpm, also > > ncurses - which can be confusing). > Yes. Also manpages loocked strange but I suspected that it is connected > to the xterm problems, but I'm not sure. Such as the soft-hyphens at the ends of lines (that's partly a font problem, partly how the pager is setup). For the font, since it was an 8859 (8-bit) font, codes past 255 would show up as missing glyphs. > > While there is an unofficial patch for slang to handle UTF-8, I'm told > > that it is incomplete and not very robust. Without that patch, slang > > can handle only 8-bit encodings (such as the ISO-8859-1 to ISO-8859-15). > > In UTF-8, the characters in the range 160-255 are not sent as a single > > byte but as two or more. If the application does not know how to do > > this, the terminal running in UTF-8 mode is likely to treat those as > > incomplete sequences and doesn't show the characters that were intended. > Well I just regard my first attempt to switch to UTF-8 as failed and > went back to my normal work, waiting for further enhancements. On the > other hand I think we should clarify why the resource setting of > > *utf8: 2 > > differs from -u8 command line option. If I understand the manual right > this should not be the case. I'll take another look this afternoon. It occurs to me that your environment was perhaps the UTF-8 flavor rather than the euro one, and that some part of the gdm/xrdb/X11 code may treat the resource setting differently. > Kind regards > > Andreas. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgpo3r8GFzElP.pgp Description: PGP signature
Bug#179407: xterm: not only bold fonts do not work with widechars
On Fri, 23 Apr 2004, Thomas Dickey wrote: > > *utf8: 2 > > > > differs from -u8 command line option. If I understand the manual right > > this should not be the case. > > I'll take another look this afternoon. It occurs to me that your environment > was perhaps the UTF-8 flavor rather than the euro one, and that some part of > the gdm/xrdb/X11 code may treat the resource setting differently. Thanks. Feel free to ask me for further information / tests. Kind regards and thanks for caring for xterm Andreas.
X Strike Force XFree86 SVN commit: r1306 - trunk/debian
Author: fabbione Date: 2004-04-23 05:41:46 -0500 (Fri, 23 Apr 2004) New Revision: 1306 Modified: trunk/debian/MANIFEST.alpha trunk/debian/MANIFEST.hurd-i386 trunk/debian/MANIFEST.i386 trunk/debian/MANIFEST.ia64 trunk/debian/MANIFEST.sparc trunk/debian/changelog trunk/debian/xserver-xfree86.install.alpha trunk/debian/xserver-xfree86.install.hurd-i386 trunk/debian/xserver-xfree86.install.i386 trunk/debian/xserver-xfree86.install.ia64 trunk/debian/xserver-xfree86.install.sparc Log: Update MANIFEST and xserver-xfree86.install files for alpha, hurd-i386, i386, ia64 and sparc to reflect the removal of files containing object code with no corresponding source, in reference to #242865. Problem spotted building from source on i386 by MANIFEST file automatic check. Modified: trunk/debian/MANIFEST.alpha === --- trunk/debian/MANIFEST.alpha 2004-04-23 06:00:04 UTC (rev 1305) +++ trunk/debian/MANIFEST.alpha 2004-04-23 10:41:46 UTC (rev 1306) @@ -6117,8 +6117,6 @@ usr/X11R6/lib/modules/libxf8_32bpp.a usr/X11R6/lib/modules/linux/libdrm.a usr/X11R6/lib/modules/linux/libfbdevhw.a -usr/X11R6/lib/modules/v10002d.uc -usr/X11R6/lib/modules/v20002d.uc usr/X11R6/man/man1/XFree86.1x usr/X11R6/man/man1/Xmark.1x usr/X11R6/man/man1/Xnest.1x Modified: trunk/debian/MANIFEST.hurd-i386 === --- trunk/debian/MANIFEST.hurd-i386 2004-04-23 06:00:04 UTC (rev 1305) +++ trunk/debian/MANIFEST.hurd-i386 2004-04-23 10:41:46 UTC (rev 1306) @@ -5956,8 +5956,6 @@ usr/X11R6/lib/modules/libxf4bpp.a usr/X11R6/lib/modules/libxf8_16bpp.a usr/X11R6/lib/modules/libxf8_32bpp.a -usr/X11R6/lib/modules/v10002d.uc -usr/X11R6/lib/modules/v20002d.uc usr/X11R6/man/man1/XFree86.1x usr/X11R6/man/man1/Xmark.1x usr/X11R6/man/man1/Xnest.1x Modified: trunk/debian/MANIFEST.i386 === --- trunk/debian/MANIFEST.i386 2004-04-23 06:00:04 UTC (rev 1305) +++ trunk/debian/MANIFEST.i386 2004-04-23 10:41:46 UTC (rev 1306) @@ -6142,8 +6142,6 @@ usr/X11R6/lib/modules/linux/libdrm.a usr/X11R6/lib/modules/linux/libfbdevhw.a usr/X11R6/lib/modules/linux/libint10.a -usr/X11R6/lib/modules/v10002d.uc -usr/X11R6/lib/modules/v20002d.uc usr/X11R6/man/man1/XFree86.1x usr/X11R6/man/man1/Xmark.1x usr/X11R6/man/man1/Xnest.1x Modified: trunk/debian/MANIFEST.ia64 === --- trunk/debian/MANIFEST.ia64 2004-04-23 06:00:04 UTC (rev 1305) +++ trunk/debian/MANIFEST.ia64 2004-04-23 10:41:46 UTC (rev 1306) @@ -6139,8 +6139,6 @@ usr/X11R6/lib/modules/libxf8_32bpp.a usr/X11R6/lib/modules/linux/libdrm.a usr/X11R6/lib/modules/linux/libfbdevhw.a -usr/X11R6/lib/modules/v10002d.uc -usr/X11R6/lib/modules/v20002d.uc usr/X11R6/man/man1/XFree86.1x usr/X11R6/man/man1/Xmark.1x usr/X11R6/man/man1/Xnest.1x Modified: trunk/debian/MANIFEST.sparc === --- trunk/debian/MANIFEST.sparc 2004-04-23 06:00:04 UTC (rev 1305) +++ trunk/debian/MANIFEST.sparc 2004-04-23 10:41:46 UTC (rev 1306) @@ -6128,8 +6128,6 @@ usr/X11R6/lib/modules/libxf8_32wid.a usr/X11R6/lib/modules/linux/libdrm.a usr/X11R6/lib/modules/linux/libfbdevhw.a -usr/X11R6/lib/modules/v10002d.uc -usr/X11R6/lib/modules/v20002d.uc usr/X11R6/man/man1/XFree86.1x usr/X11R6/man/man1/Xmark.1x usr/X11R6/man/man1/Xnest.1x Modified: trunk/debian/changelog === --- trunk/debian/changelog 2004-04-23 06:00:04 UTC (rev 1305) +++ trunk/debian/changelog 2004-04-23 10:41:46 UTC (rev 1306) @@ -7,8 +7,10 @@ XFree86 at build or run time). Add these files to the prune-non-free script. Document these DFSG violations in copyright file. Update patch #025 to stop patching one of the affected files (part of the kernel DRM -sources, so again, it's not used by XFree86 as built by Debian). Thanks -to Nathanael Nerode for his assistance with this issue. (Closes: #242865) +sources, so again, it's not used by XFree86 as built by Debian). Update +MANIFEST and xserver-xfree86.install files for alpha, hurd-i386, i386, +ia64 and sparc accordingly. Thanks to Nathanael Nerode for his assistance +with this issue. (Closes: #242865) * The tar achive within the .orig tar archive (stored this way due to the requirements of dbs) has been re-packed using gzip instead of bzip2. This Modified: trunk/debian/xserver-xfree86.install.alpha === --- trunk/debian/xserver-xfree86.install.alpha 2004-04-23 06:00:04 UTC (rev 1305) +++ trunk/debian/xserver-xfree86.install.alpha 2004-04-23 10:41:46 UTC (rev 1306) @@ -113,8 +113,6 @@ usr/X11R6/lib/modules/libxf8_32bpp.a usr/X11R6/lib/modules/linux/libdrm.a usr/X11R6/lib/modules/linux/libfbd
X Strike Force XFree86 SVN commit: r1307 - in trunk/debian: . patches
Author: fabbione
Date: 2004-04-23 06:27:55 -0500 (Fri, 23 Apr 2004)
New Revision: 1307
Modified:
trunk/debian/changelog
trunk/debian/patches/104_sparc_fix_GL_library.diff
Log:
Fix 104_sparc_fix_GL_library.diff to compile lib/GL/glx/glxext.c on non-sparc
architectures and removed unrequired #else #endif block.
Problem detected building from source on i386.
Fix tested rebuilding from source on i386.
NOTE: sparc code has not been modified and it is expected to work as before.
Modified: trunk/debian/changelog
===
--- trunk/debian/changelog 2004-04-23 10:41:46 UTC (rev 1306)
+++ trunk/debian/changelog 2004-04-23 11:27:55 UTC (rev 1307)
@@ -167,7 +167,8 @@
* Fix SEGV when attempting to use GLX extension on SPARC due to failure of
extension to initialize a Mesa context; patch by Ferris McCormick,
-backported from XFree86 CVS 2003-12-08 by Christian Guggenberger.
+backported from XFree86 CVS 2003-12-08 by Christian Guggenberger,
+and updated to build on non-sparc architectures by Fabio M. Di Nitto.
(Closes: #241331)
* Disable RandR extension support in siliconmotion driver when the driver's
Modified: trunk/debian/patches/104_sparc_fix_GL_library.diff
===
--- trunk/debian/patches/104_sparc_fix_GL_library.diff 2004-04-23 10:41:46 UTC
(rev 1306)
+++ trunk/debian/patches/104_sparc_fix_GL_library.diff 2004-04-23 11:27:55 UTC
(rev 1307)
@@ -68,7 +68,7 @@
return gc->majorOpcode;
} else {
/*
-@@ -1029,3 +1062,64 @@
+@@ -1029,3 +1062,60 @@
}
}
#endif
@@ -126,10 +126,6 @@
+ __glapi_sparc_icache_flush(&insn_ptr[0]);
+ insn_ptr += 5;
+# endif
-+#else
-+ /*
-+ * Just no-op
-+ */
-+#endif /* sparc ASM in use */
+ }
++#endif /* sparc ASM in use */
+}
X Strike Force XFree86 SVN commit: r1308 - in trunk/debian: . patches
Author: fabbione
Date: 2004-04-23 08:02:56 -0500 (Fri, 23 Apr 2004)
New Revision: 1308
Added:
trunk/debian/patches/913_debian_remove_code_ref_to_object_code_files.diff
Modified:
trunk/debian/changelog
Log:
Add patch #913 to remove references to object code files inside the source
tree and be able to build again. Patch is debian specific (as per
debian/README)
Problem discovered building from source on i386.
Fix to the FTBFS tested building from source on i386.
Unable to test the fix on affect hardware (fabbione doesn't have these cards).
Modified: trunk/debian/changelog
===
--- trunk/debian/changelog 2004-04-23 11:27:55 UTC (rev 1307)
+++ trunk/debian/changelog 2004-04-23 13:02:56 UTC (rev 1308)
@@ -4,13 +4,12 @@
* Re-generate .orig tar archive to eliminate files containing object code
with no corresponding source (none of which are actually needed or used by
-XFree86 at build or run time). Add these files to the prune-non-free
-script. Document these DFSG violations in copyright file. Update patch
-#025 to stop patching one of the affected files (part of the kernel DRM
-sources, so again, it's not used by XFree86 as built by Debian). Update
-MANIFEST and xserver-xfree86.install files for alpha, hurd-i386, i386,
-ia64 and sparc accordingly. Thanks to Nathanael Nerode for his assistance
-with this issue. (Closes: #242865)
+XFree86 at run time). Add these files to the prune-non-free script.
+Update patch #025 to stop patching one of the affected files and add patch
+#913 to remove all references to the affected files inside the code
+required to build. Update MANIFEST and xserver-xfree86.install files for
+alpha, hurd-i386, i386, ia64 and sparc accordingly. Thanks to Nathanael
+Nerode for his assistance with this issue. (Closes: #242865)
* The tar achive within the .orig tar archive (stored this way due to the
requirements of dbs) has been re-packed using gzip instead of bzip2. This
Added: trunk/debian/patches/913_debian_remove_code_ref_to_object_code_files.diff
===
--- trunk/debian/patches/913_debian_remove_code_ref_to_object_code_files.diff
2004-04-23 11:27:55 UTC (rev 1307)
+++ trunk/debian/patches/913_debian_remove_code_ref_to_object_code_files.diff
2004-04-23 13:02:56 UTC (rev 1308)
@@ -0,0 +1,157 @@
+diff -Nur xc.orig/programs/Xserver/hw/xfree86/drivers/mga/Imakefile
xc/programs/Xserver/hw/xfree86/drivers/mga/Imakefile
+--- xc.orig/programs/Xserver/hw/xfree86/drivers/mga/Imakefile 2004-04-23
09:24:58.0 +0200
xc/programs/Xserver/hw/xfree86/drivers/mga/Imakefile 2004-04-23
09:31:29.0 +0200
+@@ -143,7 +143,6 @@
+ InstallDriverSDKNonExecFile(mga_dri.c,$(DRIVERSDKDIR)/drivers/mga)
+ InstallDriverSDKNonExecFile(mgareg_flags.h,$(DRIVERSDKDIR)/drivers/mga)
+ InstallDriverSDKNonExecFile(mga_sarea.h,$(DRIVERSDKDIR)/drivers/mga)
+-InstallDriverSDKNonExecFile(mga_ucode.h,$(DRIVERSDKDIR)/drivers/mga)
+ InstallDriverSDKNonExecFile(client.h,$(DRIVERSDKDIR)/drivers/mga)
+ InstallDriverSDKNonExecFile(clientlx.c,$(DRIVERSDKDIR)/drivers/mga)
+
InstallDriverSDKNonExecFile(HALlib/binding.h,$(DRIVERSDKDIR)/drivers/mga/HALlib)
+diff -Nur xc.orig/programs/Xserver/hw/xfree86/drivers/rendition/Imakefile
xc/programs/Xserver/hw/xfree86/drivers/rendition/Imakefile
+--- xc.orig/programs/Xserver/hw/xfree86/drivers/rendition/Imakefile
2003-02-17 18:06:43.0 +0100
xc/programs/Xserver/hw/xfree86/drivers/rendition/Imakefile 2004-04-23
09:51:54.0 +0200
+@@ -44,8 +44,6 @@
+ ObjectFromSpecialSource(accel, accelX, -DPSZ=16)
+
+ InstallObjectModule(rendition,$(MODULEDIR),drivers)
+-InstallNonExecFile(v10002d.uc,$(MODULEDIR))
+-InstallNonExecFile(v20002d.uc,$(MODULEDIR))
+
+ #if !defined(XF86DriverSDK)
+ InstallModuleManPage(rendition)
+@@ -85,9 +83,6 @@
+ InstallDriverSDKNonExecFile(accelX.c,$(DRIVERSDKDIR)/drivers/rendition)
+ InstallDriverSDKNonExecFile(cmd2d.h,$(DRIVERSDKDIR)/drivers/rendition)
+
+-InstallDriverSDKNonExecFile(v10002d.uc,$(DRIVERSDKDIR)/drivers/rendition)
+-InstallDriverSDKNonExecFile(v20002d.uc,$(DRIVERSDKDIR)/drivers/rendition)
+-
+ InstallDriverSDKNonExecFile(README.uc,$(DRIVERSDKDIR)/drivers/rendition)
+
+ InstallDriverSDKObjectModule(rendition,$(DRIVERSDKMODULEDIR),drivers)
+diff -Nur xc.orig/programs/Xserver/hw/xfree86/drivers/rendition/vboard.c
xc/programs/Xserver/hw/xfree86/drivers/rendition/vboard.c
+--- xc.orig/programs/Xserver/hw/xfree86/drivers/rendition/vboard.c
2002-12-11 18:23:33.0 +0100
xc/programs/Xserver/hw/xfree86/drivers/rendition/vboard.c 2004-04-23
09:50:23.0 +0200
+@@ -88,14 +88,6 @@
+ /* reset memory endian */
+ verite_out8(iob+MEMENDIAN, memendian);
+
+-if (V1000_DEVICE == pRendition->board.chip){
+- c=verite_load_ucfile(pScreenInfo, strcat ((char
*)MICROCODE
Re: X Strike Force XFree86 SVN commit: r1308 - in trunk/debian: . patches
On Fri, 23 Apr 2004, X Strike Force SVN Repository Admin wrote: > Author: fabbione > Date: 2004-04-23 08:02:56 -0500 (Fri, 23 Apr 2004) > New Revision: 1308 > > Added: >trunk/debian/patches/913_debian_remove_code_ref_to_object_code_files.d= > iff > Modified: >trunk/debian/changelog > Log: > Add patch #913 to remove references to object code files inside the sourc= > e > tree and be able to build again. Patch is debian specific (as per > debian/README) > > Problem discovered building from source on i386. > Fix to the FTBFS tested building from source on i386. > Unable to test the fix on affect hardware (fabbione doesn't have these ca= > rds). Branden, please be so kind to add your magic touch with $ID to the patch (hounestly i didn't check how to do that yet) and kill my itaglish here and there. I am trying hard to improve my english but i am sure that you will spot something wrong with it. 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.
supersedx
Are you ready to boost your serx life? get super viakgra at only 3 dol! http://superdr.com/sv/index.php?pid=eph9058
Call for testers: xfree86 (4.3.0.dfsg.1-1)
Hi all, I just commited a bunch of changes to the svn repo. Since these changes affects specific architectures (even if the changes are trivial) i would like to at least a build report on the following archs: alpha, hurd-i386, i386 (*), ia64 and sparc (*) I did test i386 but another shot is always a good idea. Hardwarewise with the removal of the code to have a dfsg compliant tree, people that have a rendition chipset must test the driver since the microcode has been removed (and code modified accordingly). The other hardware shouldn't be affected (Ati and matrox G200/G400). On my own I tested a simple upgrade from -7 and it was ok. Please report problems in case! Regards 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.
RE: Re: Your software
Recebemos a sua mensagem. Assim que possível terá uma resposta do nosso Serviço de Assistência a Clientes. A equipa infoxadrez.com
Re: Call for testers: xfree86 (4.3.0.dfsg.1-1)
On Fri, 23 Apr 2004 [EMAIL PROTECTED] wrote: > On Fri, Apr 23, 2004 at 03:31:20PM +0200, Fabio Massimo Di Nitto wrote: > > > > Hi all, > > I just commited a bunch of changes to the svn repo. > > Since these changes affects specific architectures (even if the changes > > are trivial) i would like to at least a build report on the following > > archs: > > > > alpha, hurd-i386, i386 (*), ia64 and sparc > > > > (*) I did test i386 but another shot is always a good idea. > > > > Hi Fabio, > > is your svn repo really 4.3.0 or is it 4.3.99 (prior to > Oz License 1.1)? > I always thought that 4.3.0 is debian compliant. the svn repo is the Debian one that Branden is hosting for the community: http://necrotic.deadbeast.net/xsf/XFree86/ Please direct any question to the mailing list next time since other people can answer them as well when i am not available. Regards 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.
X Strike Force XFree86 SVN property change: propchange - r1306 svn:log
Author: branden Revision: 1306 Property Name: svn:log New Property Value: Update MANIFEST and xserver-xfree86.install files for alpha, hurd-i386, i386, ia64 and sparc to reflect the removal of files containing object code with no corresponding source. changeset: follows 1294
X Strike Force XFree86 SVN property change: propchange - r1294 svn:log
Author: branden Revision: 1294 Property Name: svn:log New Property Value: Re-christen next release as 4.3.0.dfsg.1, which uses a regenerated .orig.tar.gz (maintained outside SVN). (Closes: #242865) Update patch #025 to stop patching one of the files removed due to #242865. changeset: followed by 1306
X Strike Force XFree86 SVN commit: r1309 - trunk/debian
Author: branden Date: 2004-04-23 10:48:07 -0500 (Fri, 23 Apr 2004) New Revision: 1309 Modified: trunk/debian/changelog Log: Give fabbione credit for assisting with the object code removal. Modified: trunk/debian/changelog === --- trunk/debian/changelog 2004-04-23 13:02:56 UTC (rev 1308) +++ trunk/debian/changelog 2004-04-23 15:48:07 UTC (rev 1309) @@ -1,6 +1,6 @@ xfree86 (4.3.0.dfsg.1-1) unstable; urgency=low - Changes by Branden Robinson: + Changes by Branden Robinson and Fabio Massimo di Nitto: * Re-generate .orig tar archive to eliminate files containing object code with no corresponding source (none of which are actually needed or used by @@ -11,6 +11,8 @@ alpha, hurd-i386, i386, ia64 and sparc accordingly. Thanks to Nathanael Nerode for his assistance with this issue. (Closes: #242865) + Changes by Branden Robinson: + * The tar achive within the .orig tar archive (stored this way due to the requirements of dbs) has been re-packed using gzip instead of bzip2. This increases the size of the .orig tar archive by 10MB (a 21% increase), but
X Strike Force XFree86 SVN property change: propchange - r1307 svn:log
Author: branden Revision: 1307 Property Name: svn:log New Property Value: Fix 104_sparc_fix_GL_library.diff to compile lib/GL/glx/glxext.c on non-SPARC architectures. Remove unneeded #else #endif block. changeset: follows 1236 test: i386 build, fabbione
X Strike Force XFree86 SVN property change: propchange - r1236 svn:log
Author: branden Revision: 1236 Property Name: svn:log New Property Value: Fix SEGV when attempting to use GLX extension on SPARC due to failure of extension to initialize a Mesa context; patch by Ferris McCormick, backported from XFree86 CVS by Christian Guggenberger. (Closes: #241331) changeset: followed by 1307
X Strike Force XFree86 SVN commit: r1310 - trunk/debian
Author: branden Date: 2004-04-23 10:53:21 -0500 (Fri, 23 Apr 2004) New Revision: 1310 Modified: trunk/debian/changelog Log: Move item to the joint branden-fabbione section, since fabbione made it actually work on non-SPARC machines. Modified: trunk/debian/changelog === --- trunk/debian/changelog 2004-04-23 15:48:07 UTC (rev 1309) +++ trunk/debian/changelog 2004-04-23 15:53:21 UTC (rev 1310) @@ -11,6 +11,12 @@ alpha, hurd-i386, i386, ia64 and sparc accordingly. Thanks to Nathanael Nerode for his assistance with this issue. (Closes: #242865) + * Fix SEGV when attempting to use GLX extension on SPARC due to failure of +extension to initialize a Mesa context; patch by Ferris McCormick, +backported from XFree86 CVS 2003-12-08 by Christian Guggenberger, +and updated to build on non-SPARC architectures by Fabio M. Di Nitto. +(Closes: #241331) + Changes by Branden Robinson: * The tar achive within the .orig tar archive (stored this way due to the @@ -166,12 +172,6 @@ + Use shell's && and || operators instead of test(1)'s -a and -o operators, since the former is POSIX-compliant and the latter is not. - * Fix SEGV when attempting to use GLX extension on SPARC due to failure of -extension to initialize a Mesa context; patch by Ferris McCormick, -backported from XFree86 CVS 2003-12-08 by Christian Guggenberger, -and updated to build on non-sparc architectures by Fabio M. Di Nitto. -(Closes: #241331) - * Disable RandR extension support in siliconmotion driver when the driver's "Rotate" option is used (thanks, Jim Paris). (Closes: #241286)
X Strike Force XFree86 SVN property change: propchange - r1294 svn:log
Author: branden Revision: 1294 Property Name: svn:log New Property Value: Re-christen next release as 4.3.0.dfsg.1, which uses a regenerated .orig.tar.gz (maintained outside SVN). (Closes: #242865) Update patch #025 to stop patching one of the files removed due to #242865. changeset: followed by 1306, 1308
X Strike Force XFree86 SVN property change: propchange - r1306 svn:log
Author: branden Revision: 1306 Property Name: svn:log New Property Value: Update MANIFEST and xserver-xfree86.install files for alpha, hurd-i386, i386, ia64 and sparc to reflect the removal of files containing object code with no corresponding source. changeset: follows 1294, followed by 1308
X Strike Force XFree86 SVN property change: propchange - r1308 svn:log
Author: branden Revision: 1308 Property Name: svn:log New Property Value: Add Debian-specific patch #913 to remove references to object code files inside the source tree, fixing FTBFS. changeset: follows 1294, 1306 test: i386 build, fabbione
X Strike Force XFree86 SVN commit: r1311 - trunk/debian/patches
Author: branden Date: 2004-04-23 11:00:57 -0500 (Fri, 23 Apr 2004) New Revision: 1311 Modified: trunk/debian/patches/913_debian_remove_code_ref_to_object_code_files.diff Log: Add patch annotation. Add Id keyword and set svn:keywords property to "Id". changeset: follows 1294, 1306, 1308 Modified: trunk/debian/patches/913_debian_remove_code_ref_to_object_code_files.diff === --- trunk/debian/patches/913_debian_remove_code_ref_to_object_code_files.diff 2004-04-23 15:53:21 UTC (rev 1310) +++ trunk/debian/patches/913_debian_remove_code_ref_to_object_code_files.diff 2004-04-23 16:00:57 UTC (rev 1311) @@ -1,3 +1,10 @@ +$Id$ + +Eliminate references to sourceless object code pruned from the source +distribution in Debian packages. + +This patch by Fabio Massimo Di Nitto. + diff -Nur xc.orig/programs/Xserver/hw/xfree86/drivers/mga/Imakefile xc/programs/Xserver/hw/xfree86/drivers/mga/Imakefile --- xc.orig/programs/Xserver/hw/xfree86/drivers/mga/Imakefile 2004-04-23 09:24:58.0 +0200 +++ xc/programs/Xserver/hw/xfree86/drivers/mga/Imakefile 2004-04-23 09:31:29.0 +0200 Property changes on: trunk/debian/patches/913_debian_remove_code_ref_to_object_code_files.diff ___ Name: svn:keywords + Id
X Strike Force XFree86 SVN property change: propchange - r1294 svn:log
Author: branden Revision: 1294 Property Name: svn:log New Property Value: Re-christen next release as 4.3.0.dfsg.1, which uses a regenerated .orig.tar.gz (maintained outside SVN). (Closes: #242865) Update patch #025 to stop patching one of the files removed due to #242865. changeset: followed by 1306, 1308, 1311
X Strike Force XFree86 SVN property change: propchange - r1306 svn:log
Author: branden Revision: 1306 Property Name: svn:log New Property Value: Update MANIFEST and xserver-xfree86.install files for alpha, hurd-i386, i386, ia64 and sparc to reflect the removal of files containing object code with no corresponding source. changeset: follows 1294, followed by 1308, 1311
X Strike Force XFree86 SVN property change: propchange - r1308 svn:log
Author: branden Revision: 1308 Property Name: svn:log New Property Value: Add Debian-specific patch #913 to remove references to object code files inside the source tree, fixing FTBFS. changeset: follows 1294, 1306; followed by 1308 test: i386 build, fabbione
Re: description of fix for #230204 for clean-room reimplmentation
On Wed, Apr 21, 2004 at 08:36:19PM -0700, Keith Packard wrote:
>
> Around 16 o'clock on Apr 21, Branden Robinson wrote:
>
> > In the source file
> > :
>
> I'll note that the version of KDKBDREP_ioctl_ok in X.Org CVS does:
>
> static int
> KDKBDREP_ioctl_ok(int rate, int delay) {
> #if defined(KDKBDREP) && !defined(__sparc__)
> /* This ioctl is defined in but is not
> implemented anywhere - must be in some m68k patches. */
the ifndef __sparc__ here is totally bogus as the code is in the
generic vt code and enabled for all architectures. similarly the
comment is rather strange. Might be best to just removed them..
Processed: tagging 242830
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.7.95.1 > # debian/control issue; not upstream > tags 242830 - upstream Bug#242830: libxtst-dev: XTest.h #includes X11/extensions/XInput.h without depending on libxi-dev Tags were: pending upstream Tags removed: upstream > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: a little triage on pending bugs
Processing commands for [EMAIL PROTECTED]: > retitle 224909 xserver-xfree86: [os-support/linux] kernel complains about > XFree86 accessing hardware directly Bug#224909: xserver-xfree86: [core server] kernel complains about XFree86 accessing hardware directly Changed Bug title. > # XKB data comes from upstream > tag 236604 + upstream Bug#236604: xlibs: [XKB] symbols file for hr (pc/latin/type3) lost minus and underscore at AB10 Tags were: pending Tags added: upstream > retitle 238340 xserver-xfree86: [debconf] stop setting VideoRam default for > users of i810 driver Bug#238340: xserver-xfree86: fix debconfage to stop setting VideoRam default for users of i810 driver Changed Bug title. > retitle 207543 xserver-xfree86: [pci] add option to restrict PCI resets to > one detected device Bug#207543: xserver-xfree86: please consider patch to implement "preferred PCI bus ID" Changed Bug title. > retitle 237046 xserver-xfree86: [debconf] config script takes a very long > time because discover probes ISA parallel and serial ports Bug#237046: xserver-xfree86: config script takes very long time Changed Bug title. > retitle 238276 xserver-xfree86: [pci] add IA64 zx1 PCI support Bug#238276: xserver-xfree86: IA64 zx1 PCI support Changed Bug title. > retitle 241336 xserver-xfree86: mouse doesn't work after xfree86 upgrade; > using GPM as repeater, port /dev/psaux, protocol ImPS/2 Bug#241336: Mouse doesn't work after xfree86 upgrade Changed Bug title. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#198037: XFree86 crash while starting.
reassign 198037 xserver-xfree86 tag 198037 + moreinfo On Thu, Jun 19, 2003 at 11:26:43AM +0200, Gerard Sanromà Güell wrote: > Package: XFree86 > Version: 4.2.1-6 [...] > I reach to view the KDE screen but it crashes when is initializing > peripherals because of a signal 11 caught. > The curious thing is that during the short time is the kde screen i view > the mouse pointer and i can move it. > > I think it's due to the mouse because is the last output on XFree86.0.log > before it crashes. I've tried with several mouses and no one has work. > > in attachment XF86Config-4 and XFree86.0.log. [...] > Hw -> video card: ati radeon 9100 (driver vesa) > -> mouse: tried with several. I have a few questions: 1) Are you still experiencing this problem with XFree86 4.3.0-7, currently in Debian unstable (sid) and testing (sarge)? 2) If the answer to 1) is "yes", does X work if you change the "Driver" in the "Device" section of XF86Config-4 to "ati", instead of "vesa"? 3) If the answer to 1) is "yes", try commenting out all the "InputDevice" sections in your XF86Config-4 that use the "mouse" driver, then start the XFree86 X server with the "-allowMouseOpenFail" option; e.g. "startx -- -allowMouseOpenFail". Does the X server stay up for more than a few seconds then? -- G. Branden Robinson| If you have the slightest bit of Debian GNU/Linux | intellectual integrity you cannot [EMAIL PROTECTED] | support the government. http://people.debian.org/~branden/ | -- anonymous signature.asc Description: Digital signature
Processed: Re: Bug#198037: XFree86 crash while starting.
Processing commands for [EMAIL PROTECTED]: > reassign 198037 xserver-xfree86 Bug#198037: xserver-xfree86: [vesa] SEGV when starting on ATI unknown chipset (0x514d) Bug reassigned from package `xfree86' to `xserver-xfree86'. > tag 198037 + moreinfo Bug#198037: xserver-xfree86: [vesa] SEGV when starting on ATI unknown chipset (0x514d) Tags were: upstream Tags added: moreinfo > On Thu, Jun 19, 2003 at 11:26:43AM +0200, Gerard Sanromà Güell wrote: Unknown command or malformed arguments to command. > > Package: XFree86 Unknown command or malformed arguments to command. > > Version: 4.2.1-6 Unknown command or malformed arguments to command. > [...] Unknown command or malformed arguments to command. > > I reach to view the KDE screen but it crashes when is initializing Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#215076: xbase-clients: [xftcache] SEGV on Type1 directory
As of XFree86 4.3.0, the xftcache executable is no longer shipped as part of the Debian packages (in fact, it isn't compiled anymore in the upstream build process). XFree86 4.3.0-7 is now in Debian unstable (sid) and testing (sarge). That which is not built cannot segfault. Closing this bug as resolved. -- G. Branden Robinson| Exercise your freedom of religion. Debian GNU/Linux | Set fire to a church of your [EMAIL PROTECTED] | choice. http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Bug#213267: xfree86 problems
tag 213267 + moreinfo thanks On Mon, Sep 29, 2003 at 02:14:57PM -0300, Marco Figueira wrote: > Package: XFree86 > Version: 4.1.0.1 > > rouxinol:~# uname -a > Linux rouxinol.proderj.rj.gov.br 2.4.18-bf2.4 #1 Son > Apr 14 09:53:28 CEST 2002 i686 unknown > rouxinol:~# Can you please describe the problem you are experiencing? Also, please supply some more information as described below: [The following is a form letter.] Dear bug submitter, Since the XFree86 X server is a large and complex piece of software, some more informtion is required of you before this bug can be handled. Please run the following commands from a shell prompt to gather and deliver this information to us: $ /usr/share/bug/xserver-xfree86 > /tmp/output 3>&1 $ mailx -s "Re: Bug#213267" [EMAIL PROTECTED] < /tmp/output If you do not have a "mailx" command on your system, you can get by installing the "mailx" Debian package; for example, with the "aptitude install mailx" or "apt-get install mailx" commands as root. Alternatively, you can also use a mail command that is compatible with mailx's command-line syntax, such as "mutt". One very good way to file bugs with the Debian Bug Tracking System is to use the "reportbug" package and command of the same name. The reportbug program does a lot of automatic information-gathering that helps package maintainers to understand your system configuration, and also ensures that your message to the Debian Bug Tracking System is well-formed so that it is processed correctly by the automated tools that manage the reports. (If you've ever gotten a "bounce" message from the Debian Bug Tracking System that tells you your message couldn't be processed, you might appreciate this latter feature.) Therefore, I strongly urge you to give "reportbug" a try as your primary bug reporting tool for the Debian System in the future. If you *did* use reportbug to file your report, then you'r receiving this message because the information we expected to see was not present. If you deliberately deleted this information from the report, please don't do that in the future, even if it seems like it makes the mail too large. 50 kB (kilobytes) of configuration and log data is typical. Only if the included information greatly exceeds this amount (more than 100 kB) should you consider omitting it; instead, put it up on the World Wide Web somewhere and provide URLs to it in your report, or in subsequent followup by mailing <[EMAIL PROTECTED]>. Thank you! -- G. Branden Robinson| A fundamentalist is someone who Debian GNU/Linux | hates sin more than he loves [EMAIL PROTECTED] | virtue. http://people.debian.org/~branden/ | -- John H. Schaar signature.asc Description: Digital signature
Bug#205129: XFree86 and ATI Radeon 7500. (2)
tag 205129 + moreinfo thanks On Wed, Aug 13, 2003 at 12:00:55AM +0200, Goldfinger wrote: > Package: XFree86 > Version 4.1.0.1 > > > I use graphics card ATI RADEON 7500 built by ATI. > After installation Debian 3.0 r1 and windowmaker I wrote in text mode > "startx" and mistake appeared, (Fatal server error: no screens found) > which content is in enclosure. > I ask about help. > > Configuration: > Iiyama HM 704 UTC > MSI KT3 Ultra Aru > AMI® BIOS ver. 5.7 > AMD Duron 1300 Morgan > DDR 512 Nanya [The following is a form letter.] Dear bug submitter, Since the XFree86 X server is a large and complex piece of software, some more informtion is required of you before this bug can be handled. Please run the following commands from a shell prompt to gather and deliver this information to us: $ /usr/share/bug/xserver-xfree86 > /tmp/output 3>&1 $ mailx -s "Re: Bug#205129" [EMAIL PROTECTED] < /tmp/output If you do not have a "mailx" command on your system, you can get by installing the "mailx" Debian package; for example, with the "aptitude install mailx" or "apt-get install mailx" commands as root. Alternatively, you can also use a mail command that is compatible with mailx's command-line syntax, such as "mutt". One very good way to file bugs with the Debian Bug Tracking System is to use the "reportbug" package and command of the same name. The reportbug program does a lot of automatic information-gathering that helps package maintainers to understand your system configuration, and also ensures that your message to the Debian Bug Tracking System is well-formed so that it is processed correctly by the automated tools that manage the reports. (If you've ever gotten a "bounce" message from the Debian Bug Tracking System that tells you your message couldn't be processed, you might appreciate this latter feature.) Therefore, I strongly urge you to give "reportbug" a try as your primary bug reporting tool for the Debian System in the future. If you *did* use reportbug to file your report, then you'r receiving this message because the information we expected to see was not present. If you deliberately deleted this information from the report, please don't do that in the future, even if it seems like it makes the mail too large. 50 kB (kilobytes) of configuration and log data is typical. Only if the included information greatly exceeds this amount (more than 100 kB) should you consider omitting it; instead, put it up on the World Wide Web somewhere and provide URLs to it in your report, or in subsequent followup by mailing <[EMAIL PROTECTED]>. Thank you! -- G. Branden Robinson|If a man ate a pound of pasta and a Debian GNU/Linux |pound of antipasto, would they [EMAIL PROTECTED] |cancel out, leaving him still http://people.debian.org/~branden/ |hungry? -- Scott Adams signature.asc Description: Digital signature
Bug#213851: Updating xfree86 on testing breaks some fonts
tag 213851 + moreinfo unreproducible thanks On Thu, Oct 02, 2003 at 08:28:54PM -0700, Mason Thomas wrote: > Package: xfree86 > Version: 4.2.1-11 > > After upgrading from xfree86 4.2.1-6 to xfree86 4.2.1-11 (during an > apt-get upgrade), I have encountered font problems with various X > packages. For example, running xcalc from a terminal results in the > following error message: > > Warning: Cannot convert string "-adobe-symbol-*-*-*-*-*-120-*-*-*-*-*-*" > to type FontStruct > Warning: Unable to load any usable ISO8859 font > Warning: Unable to load any usable ISO8859 font > Segmentation fault > > I receive a similar error from gv (with a different font listed) and > xfontsel (no font listed), and other X programs. I cannot reproduce this problem with any of these clients. XFree86 4.3.0-7 is now in Debian unstable (sid) and testing (sarge). Are you still experiencing this problem? -- G. Branden Robinson| Our ignorance is God; what we Debian GNU/Linux | know is science. [EMAIL PROTECTED] | -- Robert Green Ingersoll http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Bug#220515: Bug #220515: debian installer
tag 220515 + moreinfo thanks > Harware autodetect is a very welcome feature. Unfortunately, > autodetect of my video card (S3) apparently didn't work, or Xfree > configuration didn't see it, I had to enter it by hand. It would be > really nice to have a kernel with XFS built in, either 2.6.x or > patched 2.4. This is probably a deficiency in the discover database, but to be sure we need to see some information from the XFree86 X server. The following describes how to get it and provide it to us. You can disregard the parts that don't apply to you (since you did a d-i installation report); the important bits are the shell commands. [The following is a form letter.] Dear bug submitter, Since the XFree86 X server is a large and complex piece of software, some more informtion is required of you before this bug can be handled. Please run the following commands from a shell prompt to gather and deliver this information to us: $ /usr/share/bug/xserver-xfree86 > /tmp/output 3>&1 $ mailx -s "Re: Bug#220515" [EMAIL PROTECTED] < /tmp/output If you do not have a "mailx" command on your system, you can get by installing the "mailx" Debian package; for example, with the "aptitude install mailx" or "apt-get install mailx" commands as root. Alternatively, you can also use a mail command that is compatible with mailx's command-line syntax, such as "mutt". One very good way to file bugs with the Debian Bug Tracking System is to use the "reportbug" package and command of the same name. The reportbug program does a lot of automatic information-gathering that helps package maintainers to understand your system configuration, and also ensures that your message to the Debian Bug Tracking System is well-formed so that it is processed correctly by the automated tools that manage the reports. (If you've ever gotten a "bounce" message from the Debian Bug Tracking System that tells you your message couldn't be processed, you might appreciate this latter feature.) Therefore, I strongly urge you to give "reportbug" a try as your primary bug reporting tool for the Debian System in the future. If you *did* use reportbug to file your report, then you'r receiving this message because the information we expected to see was not present. If you deliberately deleted this information from the report, please don't do that in the future, even if it seems like it makes the mail too large. 50 kB (kilobytes) of configuration and log data is typical. Only if the included information greatly exceeds this amount (more than 100 kB) should you consider omitting it; instead, put it up on the World Wide Web somewhere and provide URLs to it in your report, or in subsequent followup by mailing <[EMAIL PROTECTED]>. Thank you! -- G. Branden Robinson|It may be difficult to to determine Debian GNU/Linux |where religious beliefs end and [EMAIL PROTECTED] |mental illness begins. http://people.debian.org/~branden/ |-- Elaine Cassel signature.asc Description: Digital signature
Bug#222976: pb matrox G450
tag 222976 + moreinfo thanks On Fri, Dec 05, 2003 at 02:09:55PM +0100, Georges Herfeld wrote: > Package: XFree86 > Version: 4.1.0.1 > > X is not starting please help me [...] > (--) PCI:*(1:0:0) Matrox MGA G400 AGP rev 133, Mem @ 0xf600/25, > 0xf500/ [...] > (**) MGA(0): Option "UseFBDev" "true" > (II) Loading sub module "mga_hal" > (II) LoadModule: "mga_hal" > (WW) Warning, couldn't open module mga_hal > (II) UnloadModule: "mga_hal" > (EE) MGA: Failed to load module "mga_hal" (module does not exist, 0) > (II) MGA(0): Matrox HAL module not found - using builtin mode setup instead > (--) MGA(0): Chipset: "mgag400" > (==) MGA(0): Using AGP 1x mode > (**) MGA(0): Using framebuffer device > (II) Loading sub module "fbdevhw" > (II) LoadModule: "fbdevhw" > (II) Loading /usr/X11R6/lib/modules/linux/libfbdevhw.a > (II) Module fbdevhw: vendor="The XFree86 Project" > compiled for 4.1.0.1, module version = 0.0.2 > ABI class: XFree86 Video Driver, version 0.4 > (II) UnloadModule: "mga" > (II) UnloadModule: "fbdevhw" > (II) Unloading /usr/X11R6/lib/modules/linux/libfbdevhw.a > (II) UnloadModule: "vgahw" > (II) Unloading /usr/X11R6/lib/modules/libvgahw.a > (EE) Screen(s) found, but none have a usable configuration. > > Fatal server error: > no screens found It looks like "UseFBDev" is set to "true" when it should not be. (If the file /proc/fb does not exist or is empty, it should not be.) Try running "dpkg-reconfigure xserver-xfree86", and when you are asked: Use kernel framebuffer device interface? Decline the option instead of accepting it. You can leave all the other settings at their current values. Then try restarting the server. Does that work? -- G. Branden Robinson| Exercise your freedom of religion. Debian GNU/Linux | Set fire to a church of your [EMAIL PROTECTED] | choice. http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Processed: Re: Bug#205129: XFree86 and ATI Radeon 7500. (2)
Processing commands for [EMAIL PROTECTED]: > tag 205129 + moreinfo Bug#205129: XFree86 and ATI Radeon 7500. (2) There were no tags set. Tags added: moreinfo > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: Re: Bug#213267: xfree86 problems
Processing commands for [EMAIL PROTECTED]: > tag 213267 + moreinfo Bug#213267: xfree86 problems There were no tags set. Tags added: moreinfo > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
X Strike Force XFree86 SVN commit: r1312 - trunk/debian
Author: branden Date: 2004-04-23 12:52:46 -0500 (Fri, 23 Apr 2004) New Revision: 1312 Modified: trunk/debian/TODO Log: Document bug number corresponding to Sven Luther's DDK patch. Modified: trunk/debian/TODO === --- trunk/debian/TODO 2004-04-23 16:00:57 UTC (rev 1311) +++ trunk/debian/TODO 2004-04-23 17:52:46 UTC (rev 1312) @@ -79,7 +79,7 @@ Message-Id: <[EMAIL PROTECTED]> * #240581: xserver-xfree86: [ati/radeon] support "ForceMinDotClock" option * Apply Adam Conrad's VIA driver patch (on debian-x). -* Evaluate Sven Luther's driver DDK package patch: +* #245541: Evaluate Sven Luther's driver DDK package patch: http://lists.debian.org/debian-x/2003/debian-x-200311/msg2.html * #240889: add AMD64 support * #243288: xfree86-common: DebianRed should be in rgb.txt
Bug#40667: the XFree86 LinkKit is dead, long live the XFree86 DDK
clone 40667 -1 tag -1 - wontfix submitter -1 Sven Luther <[EMAIL PROTECTED]> close 40667 thanks Well, the 3.x-era XFree86 LinkKit is dead (and XFree86 3.x is neither maintained upstream nor by Debian anymore), but the XFree86 DDK has arisen to take its place. In fact, the following item is on the XFree86 package TODO: Evaluate Sven Luther's driver DDK package patch: http://lists.debian.org/debian-x/2003/debian-x-200311/msg2.html Resurrecting "[EMAIL PROTECTED]"'s wontfix wishlist item as Sven Luther's willfix wishlist item. -- G. Branden Robinson| Yesterday upon the stair, Debian GNU/Linux | I met a man who wasn't there. [EMAIL PROTECTED] | He wasn't there again today, http://people.debian.org/~branden/ | I think he's from the CIA. signature.asc Description: Digital signature
Bug#172962: IPv6 support
On Sun, Mar 09, 2003 at 08:57:47PM +0100, Fabio Massimo Di Nitto wrote: > Hi Juliusz, > thanks for the information. Im already in the process of > testing the patches based on DanielS X4.3 packageds and fixing a bunch of > small issues to prepare a more complete report to the X people. I already > subscribed there since a while. I hope to get the support from all of you > guys :-) > > Thanks > Fabio Hey Fabio, What exactly *is* going on with IPv6 support these days? I understand it's caused a lot of grief for X.Org and XFree86 4.4, crazy breakage in xdm and stuff. But maybe things have settled down. Can you send a status report to this bug some time when you get a chance? Also, if you're still the overlord of this issue, please mail the following to [EMAIL PROTECTED]: owner 172962 [EMAIL PROTECTED] :) -- G. Branden Robinson| Debian GNU/Linux | Music is the brandy of the damned. [EMAIL PROTECTED] | -- George Bernard Shaw http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Bug#29194: Bug #29194: xfree86: have all XFree86 packages symlink to xfree86-common for copyright and changelog(s)
tag 29194 + wontfix thanks Well, after almost five and a half years, this idea still hasn't caught on in Debian. It may be unwise to not physically pack copyright info into every .deb, but as for the changelog, well, that's probably a matter of taste. I will note that if debhelper were to do this for me, I'd probably meekly follow along. Tagging wontfix, as I haven't the courage to explore this particular frontier. If you no longer feel this should be done, please close the bug. -- G. Branden Robinson| Religious bondage shackles and Debian GNU/Linux | debilitates the mind and unfits it [EMAIL PROTECTED] | for every noble enterprise. http://people.debian.org/~branden/ | -- James Madison signature.asc Description: Digital signature
Bug#220493: Want a more recent version of the XFree86-server
retitle 220493 xfree86: please package XFree86 4.4 tag 220493 + wontfix On Thu, Nov 13, 2003 at 12:34:50AM +0100, Uwe Storbeck wrote: > in general I'm a friend of the somewhat conservative strategie of the > Debian project, but ... > > The XFree86 project is going to release version 4.4 of it's server > in about a month. Unfortunately, The XFree86 Project, Inc.'s decision to change the XFree86 source distribution's licensing to be GPL-incompatible has rendered the prospect of packaging it unappealing to the Debian Project. We've seen no volunteers on the debian-x list, and most other GNU/Linux and BSD distributors are avoiding 4.4 as well. Updating this bug's attributes accordingly. -- G. Branden Robinson|Religion is regarded by the common Debian GNU/Linux |people as true, by the wise as [EMAIL PROTECTED] |false, and by the rulers as useful. http://people.debian.org/~branden/ |-- Lucius Annaeus Seneca signature.asc Description: Digital signature
Bug#205564: Processed: severity of 199111 is wishlist, merging 199111 205564
close 205564 merge 199111 205564 thanks On Fri, Feb 20, 2004 at 10:03:04PM -0800, Debian Bug Tracking System wrote: > Processing commands for [EMAIL PROTECTED]: > > > # Automatically generated email from bts, devscripts version 2.7.95.1 > > severity 199111 wishlist > Bug#199111: xfs: taking Juliusz Chrobocek's font path ordering advice results > in ugly fonts > Severity set to `wishlist'. > > > merge 199111 205564 > Bug#199111: xfs: taking Juliusz Chrobocek's font path ordering advice results > in ugly fonts > Bug#205564: xfree86: have dexconf and xfs use Type1 font path after bitmapped > font paths > Mismatch - only Bugs in same state can be merged: > Values for `done mark' don't match: > #199111 has `done'; > #205564 has `open' Closing this duplicate report. -- G. Branden Robinson| I don't care if it has a GUI, or Debian GNU/Linux | command line, or is carved in mud [EMAIL PROTECTED] | with a sharp spoon. http://people.debian.org/~branden/ | -- Barry Smith signature.asc Description: Digital signature
Bug#227005: xfree86: Patch to build XDirectFB server
tag 227005 - patch tag 227005 + moreinfo retitle 227005 xfree86: build XDirectFB X server thanks On Fri, Jan 09, 2004 at 04:24:54PM +0100, Micha Nelissen wrote: > I have also submitted a RFP item on wnpp for this: #225010, because this > patch makes a XDirectFB executable which is a different X server with > DirectFB as backend and should be in a seperate binary package, but be > generated from the same source package. [...] > - Apply patch "xc-directfb.diff" with "-p0" within "xc/" [...] > Basically, it's a patch for the xfree86 source package generating a > XDirectFB binary. Only this binary is different from the ordinary > xserver-xfree86 installation. Er, uh, where's the patch? -- G. Branden Robinson| Never underestimate the power of Debian GNU/Linux | human stupidity. [EMAIL PROTECTED] | -- Robert Heinlein http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Bug#201871: marked as done (Problems with XFree86 in Debian Woody)
Your message dated Fri, 23 Apr 2004 12:04:03 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#201871: Problems with XFree86 in Debian Woody 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 responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 18 Jul 2003 10:54:43 + >From [EMAIL PROTECTED] Fri Jul 18 05:54:41 2003 Return-path: <[EMAIL PROTECTED]> Received: from smtp5.poczta.onet.pl [213.180.130.32] by master.debian.org with esmtp (Exim 3.35 1 (Debian)) id 19dSsq-00063J-00; Fri, 18 Jul 2003 05:54:40 -0500 Received: from route4.sk2.am.poznan.pl ([150.254.208.4]:34594 "HELO Psychologneur") by ps5.test.onet.pl with SMTP id ; Fri, 18 Jul 2003 12:53:56 +0200 Message-ID: <[EMAIL PROTECTED]> From: =?iso-8859-2?B?TWljaGGz?= <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Subject: Problems with XFree86 in Debian Woody Date: Fri, 18 Jul 2003 13:00:00 +0200 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=_NextPart_000_01A0_01C34D2C.7EF39BE0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Delivered-To: [EMAIL PROTECTED] X-Spam-Status: No, hits=-5.0 required=4.0 tests=HAS_PACKAGE version=2.53-bugs.debian.org_2003_06_27 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_06_27 (1.174.2.15-2003-03-30-exp) This is a multi-part message in MIME format. --=_NextPart_000_01A0_01C34D2C.7EF39BE0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Package: XFree86 Version: 4.1.0.1 I installed Linux Debian 3.0 (WOODY) (bf24 flavor) on Intel P4 1.8GHz machine with 256Mb of RAM, graphics card NVIDIA GeForce2 MX/MX 400 (AGP) (BIOS version 3.11.0148), monitor Vobis Highscreen MS15AS. Unfortunately some problems with XFree86 are occuring when loading (server crash) - XFree86.0.log and XFree86.8.log files attached. --=_NextPart_000_01A0_01C34D2C.7EF39BE0 Content-Type: application/octet-stream; name="Xfree86.8.log" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="Xfree86.8.log" =0A= This is a pre-release version of XFree86, and is not supported in any=0A= way. Bugs may be reported to XFree86@XFree86.Org and patches submitted=0A= to [EMAIL PROTECTED] Before reporting bugs in pre-release versions,=0A= please check the latest version in the XFree86 CVS repository=0A= (http://www.XFree86.Org/cvs)=0A= =0A= XFree86 Version 4.1.0.1 / X Window System=0A= (protocol Version 11, revision 0, vendor release 6510)=0A= Release Date: 21 December 2001=0A= If the server is older than 6-12 months, or if your card is=0A= newer than the above date, look for a newer version before=0A= reporting problems. (See http://www.XFree86.Org/FAQ)=0A= Build Operating System: Linux 2.4.17 i686 [ELF] =0A= Module Loader present=0A= (=3D=3D) Log file: "/var/log/XFree86.8.log", Time: Wed Jul 16 22:38:41 = 2003=0A= (++) Using config file: "//XF86Config.new"=0A= Markers: (--) probed, (**) from config file, (=3D=3D) default setting,=0A= (++) from command line, (!!) notice, (II) informational,=0A= (WW) warning, (EE) error, (NI) not implemented, (??) unknown.=0A= (=3D=3D) ServerLayout "XFree86 Configured"=0A= (**) |-->Screen "Screen0" (0)=0A= (**) | |-->Monitor "Monitor0"=0A= (**) | |-->Device "Card0"=0A= (**) |-->Input Device "Mouse0"=0A= (**) |-->Input Device "Keyboard0"=0A= (=3D=3D) Keyboard: CustomKeycode disabled=0A= (WW) The directory "/usr/X11R6/lib/X11/fonts/CID/" does not exist.=0A= Entry deleted from font path.=0A= (**) FontPath set to = "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11= R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X1= 1/fonts/100dpi/"=0A= (**) RgbPath set to "/usr/X11R6/lib/X11/rgb"=0A= (**) ModulePath set to "/usr/X11R6/lib/modules"=0A= (--) using VT number 8=0A= =0A= (WW) Cannot open APM=0A= (II) Module ABI versions:=0A= XFree86 ANSI C Emulation: 0.1=0A= XFree86 Video Driver: 0.4=0A= XFree86 XInput driver : 0.2=0A= XFree86 Server Extension : 0.1=0A= XFree86 Font Renderer : 0.2=0A= (II) Loader running on linux=0A= (II) LoadModule: "bitmap"=0A= (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a=0A= (II) Module bitmap: vendor=3D"The XFree86 Project"=0A= compiled for 4.1.0.1, module version =3D 1.0.0=0A=
Bug#233569: xlibs: raise the number of maximum clients to 512
tag 233569 + wontfix thanks On Tue, Feb 24, 2004 at 12:56:21AM +0100, Michel Dänzer wrote: > On Sat, 2004-02-21 at 19:12, Branden Robinson wrote: > > On Fri, Feb 20, 2004 at 11:05:55PM -0500, xavier wrote: > > > > > > Is there a drawback in doing such thing ? > > > > I don't know. Possibly resource consumption in the X server, but most > > machines today have a lot more to spare in the way of resources than > > machines did when this limit was probably initially set. > > > > > If not, do you think there might be a possibility for debian > > > to compile it with 512 max clients ? > > > > I do think it's a possibility yes. I just want to find out from someone > > who knows whether there would be any serious drawbacks to doing so. > > See http://www.mail-archive.com/devel@xfree86.org/msg01104.html (Start > of thread: http://www.mail-archive.com/devel@xfree86.org/msg01095.html) No one has rebutted the cited concerns. Breaking binary compatibility with Xlib modules is probably a very bad idea. Tagging this bug wontfix. -- G. Branden Robinson| Never underestimate the power of Debian GNU/Linux | human stupidity. [EMAIL PROTECTED] | -- Robert Heinlein http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Bug#202128: marked as done ([Fwd([Fwd:xwindow's not starting for me in Debian 3.0 woody])])
Your message dated Fri, 23 Apr 2004 12:05:31 -0500 with message-id <[EMAIL PROTECTED]> and subject line closing bug 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 responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 20 Jul 2003 01:38:48 + >From [EMAIL PROTECTED] Sat Jul 19 20:38:45 2003 Return-path: <[EMAIL PROTECTED]> Received: from ims.macau.ctm.net [202.175.36.220] by master.debian.org with esmtp (Exim 3.35 1 (Debian)) id 19e39w-0002t5-00; Sat, 19 Jul 2003 20:38:44 -0500 Received: from macau.ctm.net (c51line129.dialup2.ctm.net [202.175.35.130]) by ims.macau.ctm.net (8.12.9/8.12.9) with ESMTP id h6K1cZ2N011684 for <[EMAIL PROTECTED]>; Sun, 20 Jul 2003 09:38:36 +0800 (CST) Sender: [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> Date: Sun, 20 Jul 2003 09:38:30 +0800 From: Godfrey Harrison <[EMAIL PROTECTED]> X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.20-18.7 i686) X-Accept-Language: en MIME-Version: 1.0 To: [EMAIL PROTECTED] Subject: [Fwd([Fwd:xwindow's not starting for me in Debian 3.0 woody])] Content-Type: multipart/mixed; boundary="EEB7C5DEF1EF22F854D2416D" Delivered-To: [EMAIL PROTECTED] X-Spam-Status: No, hits=-6.4 required=4.0 tests=BAYES_20,HAS_PACKAGE,MAILTO_TO_SPAM_ADDR, USER_AGENT_MOZILLA_XM version=2.53-bugs.debian.org_2003_06_27 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_06_27 (1.174.2.15-2003-03-30-exp) This is a multi-part message in MIME format. --EEB7C5DEF1EF22F854D2416D Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Package: XFree86 Version: 4.1.0.1 / X window system protocol: Version 11 revision 0 vendor release 6510 --EEB7C5DEF1EF22F854D2416D Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Return-path: <[EMAIL PROTECTED]> Received: from mailscan3.macau.ctm.net (mailscan3.macau.ctm.net [202.175.36.180]) by mailserver.macau.ctm.net (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <[EMAIL PROTECTED]> for [EMAIL PROTECTED]; Sun, 20 Jul 2003 09:08:06 +0800 (CST) Received: from mailscan3.macau.ctm.net (localhost [127.0.0.1]) by mailscan3.macau.ctm.net (8.12.7/8.12.7) with ESMTP id h6K190N9020421 for <[EMAIL PROTECTED]>; Sun, 20 Jul 2003 09:09:00 +0800 (CST) Received: from master.debian.org (master.debian.org [146.82.138.7]) by mailscan3.macau.ctm.net (8.12.7/8.12.7) with ESMTP id h6K18wN0020408 for <[EMAIL PROTECTED]>; Sun, 20 Jul 2003 09:08:58 +0800 (CST) Received: from debbugs by master.debian.org with local (Exim 3.35 1 (Debian)) id 19e2bO-0007hQ-00; Sat, 19 Jul 2003 20:03:02 -0500 Date: Sat, 19 Jul 2003 20:03:02 -0500 From: [EMAIL PROTECTED] (Debian Bug Tracking System) Subject: Message with no Package: tag cannot be processed! ([Fwd: xwindow's not starting for me in Debian 3.0 woody]) In-reply-to: <[EMAIL PROTECTED]> Sender: Debian BTS <[EMAIL PROTECTED]> To: Godfrey Harrison <[EMAIL PROTECTED]> Message-id: <[EMAIL PROTECTED]> Precedence: bulk X-Loop: [EMAIL PROTECTED] X-Debian-PR-Message: error References: <[EMAIL PROTECTED]> Original-recipient: rfc822;[EMAIL PROTECTED] X-Mozilla-Status2: Your message didn't have a Package: line at the start (in the pseudo-header following the real mail header), or didn't have a pseudo-header at all. This makes it much harder for us to categorise and deal with your problem report. Please _resubmit_ your report to [EMAIL PROTECTED] and tell us which package the report is on. For help, check out http://www.debian.org/Bugs/Reporting. Your message was dated Sun, 20 Jul 2003 08:49:32 +0800 and had message-id <[EMAIL PROTECTED]> and subject [Fwd: xwindow's not starting for me in Debian 3.0 woody]. The complete text of it is attached to this message. If you need any assistance or explanation please contact me. Debian bug tracking system administrator (administrator, Debian Bugs database) --- Received: (at submit) by bugs.debian.org; 20 Jul 2003 00:49:52 + >From [EMAIL PROTECTED] Sat Jul 19 19:49:49 2003 Return-path: <[EMAIL PROTECTED]> Received: from ims.macau.ctm.net [202.175.36.220] by master.debian.org with esmtp (Exim 3.35 1 (Debian)) id 19e2Oa-0005mV-00; Sat, 19 Jul 2003 19:49:48 -0500 Received: from macau.ctm.net (c51line129.dialup2.ctm.net [202.175.35.130]) by ims.macau.ctm.
Processed: Re: Bug#213851: Updating xfree86 on testing breaks some fonts
Processing commands for [EMAIL PROTECTED]: > tag 213851 + moreinfo unreproducible Bug#213851: Updating xfree86 on testing breaks some fonts There were no tags set. Tags added: moreinfo, unreproducible > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: Re: Bug #220515: debian installer
Processing commands for [EMAIL PROTECTED]: > tag 220515 + moreinfo Bug#220515: debian installer There were no tags set. Tags added: moreinfo > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: Re: Bug#222976: pb matrox G450
Processing commands for [EMAIL PROTECTED]: > tag 222976 + moreinfo Bug#222976: pb matrox G450 There were no tags set. Tags added: moreinfo > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Re: XFree86 X server: does loading the dri module still hose sunffb users?
On Wed, Apr 21, 2004 at 06:14:01PM +0200, Joerg Friedrich wrote: > first, this restriction seems not to work, I get dri as an option. It's not supposed to be removed from the option list, just not enabled by default. > second, I try to get the xserver run with my Ultra60/Elite3D (sunffb) > but X starts and then suddenly stops before any (x|g|k)dm or a simple > windowmanager starts. > I attach my config and the log, I hope you can see something there. Please use reportbug to file a bug against xserver-xfree86. -- G. Branden Robinson| Debian GNU/Linux |Yeah, that's what Jesus would do. [EMAIL PROTECTED] |Jesus would bomb Afghanistan. Yeah. http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Bug#227005: xfree86: Patch to build XDirectFB server
On Friday 23 April 2004 19:59, Branden Robinson wrote: > > Basically, it's a patch for the xfree86 source package generating a > > XDirectFB binary. Only this binary is different from the ordinary > > xserver-xfree86 installation. > > Er, uh, where's the patch? Sorry, here. Taken from http://directfb.org/download/XDirectFB/XDirectFB-1.0-rc5.tar.gz. Micha Index: config/cf/linux.cf === RCS file: /cvs/xc/config/cf/linux.cf,v retrieving revision 3.203 diff -p -u -r3.203 linux.cf --- config/cf/linux.cf 2003/04/24 22:14:53 3.203 +++ config/cf/linux.cf 2003/05/22 23:32:03 @@ -958,6 +958,8 @@ InstallNamedTargetNoClobber(install,file #include #ifdef KDriveXServer # include +#elif defined (XDirectFBServer) +# include #else # include #endif Index: programs/Xserver/Imakefile === RCS file: /cvs/xc/programs/Xserver/Imakefile,v retrieving revision 3.284 diff -p -u -r3.284 Imakefile --- programs/Xserver/Imakefile 2003/05/14 05:27:53 3.284 +++ programs/Xserver/Imakefile 2003/05/22 23:32:04 @@ -488,6 +488,25 @@ ServerTarget(Xhp,$(HPSUBDIRS),$(HPOBJS), #endif /* XhpServer */ +#if XDirectFBServer +XCOMM +XCOMM X DirectFB server +XCOMM +FBDIR = fb +DIRECTFBDDXDIR = hw/directfb +DIRECTFBDIRS = $(STDDIRS) $(FBDIR) $(DIRECTFBDDXDIR) $(DEPDIRS) +DIRECTFBOBJS = +DIRECTFBLIBS = PreFbLibs $(DIRECTFBDDXDIR)/LibraryTargetName(directfb) FbPostFbLibs +DIRECTFBSYSLIBS = $(FONTLIBS) $(SYSLIBS) $(XLIB) `directfb-config --libs` +SetUIDServerTarget(XDirectFB,$(DIRECTFBDIRS),$(DIRECTFBOBJS), \ + $(DIRECTFBLIBS),$(DIRECTFBSYSLIBS)) + +#ifndef ServerToInstall +#define ServerToInstall XDirectFB +#endif +#endif /* XDirectFBServer */ + + #if HasParallelMake XCOMM XCOMM force non-parallel build of XF86 servers to prevent MUTEX overrides @@ -1339,7 +1358,7 @@ MIEXTDIRS = $(SHADOWDIR) $(LAYERDIR) $(R IPLANDIRS = $(IPLAN2P2DIR) $(IPLAN2P4DIR) $(IPLAN2P8DIR) DDXDIRS = $(DECWSDDXDIR) $(SUNDDXDIR) $(LYNXDDXDIR) \ $(HPDDXDIR) $(XFREE86DDXDIR) $(XWINDDXDIR) $(DARWINDDXDIR) \ - $(XVFBDDXDIR) $(XNESTDDXDIR) + $(DIRECTFBDDXDIR) $(XVFBDDXDIR) $(XNESTDDXDIR) SUBDIRS = $(STDDIRS) $(MFBDIR) $(CFBDIRS) $(IPLANDIRS) $(ILBMDIR) $(AFBDIR) \ $(LMFCFBDIR) $(DDXDIRS) $(FBDIR) $(KDRIVEDIRS) $(MIEXTDIRS) \ $(XWINPARSERDIR) Index: programs/Xserver/Xserver.man === RCS file: /cvs/xc/programs/Xserver/Xserver.man,v retrieving revision 3.23 diff -p -u -r3.23 Xserver.man --- programs/Xserver/Xserver.man 2003/04/14 20:37:17 3.23 +++ programs/Xserver/Xserver.man 2003/05/22 23:32:04 @@ -713,7 +713,7 @@ Controlling the server once started: \fI .PP Server-specific man pages: \fIXdec\fP(1), \fIXmacII\fP(1), \fIXsun\fP(1), \fIXnest\fP(1), -\fIXvfb\fP(1), \fIXFree86\fP(1), \fIXDarwin\fP(1). +\fIXvfb\fP(1), \fIXFree86\fP(1), \fIXDarwin\fP(1), \fIXDirectFB\fP(1). .PP Server internal documentation: .I "Definition of the Porting Layer for the X v11 Sample Server" Index: programs/Xserver/fb/fbcmap.c === RCS file: /cvs/xc/programs/Xserver/fb/fbcmap.c,v retrieving revision 1.6 diff -p -u -r1.6 fbcmap.c --- programs/Xserver/fb/fbcmap.c 2001/10/28 03:33:08 1.6 +++ programs/Xserver/fb/fbcmap.c 2003/05/22 23:32:04 @@ -37,7 +37,7 @@ THE USE OR PERFORMANCE OF THIS SOFTWARE. #include "resource.h" #include "fb.h" -#ifndef XFree86Server +#if !defined(XFree86Server) && !defined(DIRECTFBSERVER) ColormapPtr FbInstalledMaps[MAXSCREENS]; int
Processed: Re: Bug #29194: xfree86: have all XFree86 packages symlink to xfree86-common for copyright and changelog(s)
Processing commands for [EMAIL PROTECTED]: > tag 29194 + wontfix Bug#29194: xfree86: have all XFree86 packages symlink to xfree86-common for copyright and changelog(s) There were no tags set. Tags added: wontfix > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: the XFree86 LinkKit is dead, long live the XFree86 DDK
Processing commands for [EMAIL PROTECTED]: > clone 40667 -1 Bug#40667: xfree86: would like X server LinkKit package Bug 40667 cloned as bug 245541. > tag -1 - wontfix Bug#245541: xfree86: would like X server LinkKit package Tags were: wontfix Tags removed: wontfix > submitter -1 Sven Luther <[EMAIL PROTECTED]> Bug#245541: xfree86: would like X server LinkKit package Changed Bug submitter from [EMAIL PROTECTED] to Sven Luther <[EMAIL PROTECTED]>. > close 40667 Bug#40667: xfree86: would like X server LinkKit package 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to [EMAIL PROTECTED] > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#245548: xserver-xfree86: extreme slowness when backingstore is enabled
Package: xserver-xfree86
Version: 4.3.0-7
Severity: minor
I'm not sure if this is the right place to report this kind of "bug", but I
just noticed that using Option "BackingStore" "on" in XF86Config does affect
tremendously the performance in certain conditions. I'm using the "radeon"
driver, I don't know if this is specific to this driver. When I run the
following source code:
#include
#include
#include
int main() {
Display *display;
Window rootwin;
int i, n = 20, cnt = 0;
Window w[n];
display = XOpenDisplay(getenv("DISPLAY"));
rootwin = RootWindow(display, 0);
do {
for (i=0; i < n; ++i) {
if (cnt == 0) {
XSetWindowAttributes wa;
w[i] = XCreateSimpleWindow(display, rootwin, 0, 0, 32, 32, 0,
0L,0L);
wa.override_redirect = True;
wa.save_under = True;
XChangeWindowAttributes(display, w[i],
CWSaveUnder | CWOverrideRedirect, &wa);
XMapWindow(display, w[i]);
} else {
int x = rand() % 1024, y = rand() % 1024;
XMoveWindow(display, w[i], x, y);
}
}
usleep(3);
printf("plop! %d\n", cnt);
} while (1 + cnt++);
}
just opens 20 windows and moves them around. With BackingStore enabled, and
with a large window mapped on the desktop (mozilla for example), the xfree86
uses 100% of cpu on an athlon-2400. When I kill the test program after 200
iterations, xfree still eats 100% of cpu for 10 or 20 seconds! When
backingstore is disabled in the XF86Config, everything runs smoothly and xfree
uses about 10% of cpu.
Maybe there is a logical explanation to this, but I really don't understand:
backingstore is supposed to speed the refresh, not slow it ! And it should not
be involved in that case since the windows here use SaveUnder, and mozilla does
not use BackingStore. I'm quite puzzled.
-- Package-specific info:
Contents of /var/lib/xfree86/X.roster:
xserver-xfree86
X server symlink status:
lrwxrwxrwx1 root root 20 2002-11-10 02:39 /etc/X11/X ->
/usr/bin/X11/XFree86
-rwxr-xr-x1 root root 1742316 2004-03-18 06:42 /usr/bin/X11/XFree86
/etc/X11/X target unchanged from checksum in /var/lib/xfree86/X.md5sum.
Contents of /var/lib/xfree86/XF86Config-4.roster:
xserver-xfree86
VGA-compatible devices on PCI bus:
:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV250 If
[Radeon 9000] (rev 01)
:01:00.0 Class 0300: 1002:4966 (rev 01)
XFree86 X server configuration file status:
-rw-r--r--1 root root 6091 2004-04-23 19:33
/etc/X11/XF86Config-4
Contents of /etc/X11/XF86Config-4:
# XF86Config-4 (XFree86 server configuration file) 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.)
#
# If you want your changes to this file preserved by dexconf, only make changes
# before the "### BEGIN DEBCONF SECTION" line above, and/or after the
# "### END DEBCONF SECTION" line below.
#
# To change things within the debconf section, run the command:
# dpkg-reconfigure xserver-xfree86
# as root. Also see "How do I add custom sections to a dexconf-generated
# XF86Config or XF86Config-4 file?" in /usr/share/doc/xfree86-common/FAQ.gz.
# XF86Config-4 (XFree86 server configuration file) 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.)
#
# If you want your changes to this file preserved by dexconf, only make changes
# before the "### BEGIN DEBCONF SECTION" line above, and/or after the
# "### END DEBCONF SECTION" line below.
#
# To change things within the debconf section, run the command:
# dpkg-reconfigure xserver-xfree86
# as root. Also see "How do I add custom sections to a dexconf-generated
# XF86Config or XF86Config-4 file?" in /usr/share/doc/xfree86-common/FAQ.gz.
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/Speedo"
FontPath"/usr/lib/X11/fonts/100dpi"
FontPath"/usr/lib/X11/fonts/75dpi"
FontPath"/usr/share/fonts/truetype"
FontPath"/usr/share/fonts/truetype/freefont"
EndSection
Section "Module"
Load"GLcore"
Load"bitmap"
Load"dbe"
Load"ddc"
# Load"dri"
Load"extmod"
Load"freetype"
Re: Processed: 008_fix_xgetpw_macro.diff breaks Xlib API.
On Thu, Apr 22, 2004 at 12:12:24AM -0700, Chris Waters wrote: > So technically, what we have here is two bugs. One against OpenMotif > for depending on X internal symbols (symbols with mandatorily > undefined behavior, at that). And one against X upstream for code > with undefined behavior. I don't see why why a private function shouldn't be able to do whatever it wants. Stop using the internal symbol. -- G. Branden Robinson|The best place to hide something is Debian GNU/Linux |in documentation. [EMAIL PROTECTED] |-- Ethan Benson http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Re: Preparing -8
On Thu, Apr 22, 2004 at 01:48:36AM -0400, Joey Hess wrote: > Branden Robinson wrote: > > IIRC, you generally want to use invoke-rc.d because it is cognizant of > > runlevel policy (i.e., start service $FOO in runlevel 3 but not runlevel > > 2, and so forth). > > That's true of maintainer scripts, but not when a human is driving the > machine and knows that they definitely want xdm started or stopped right > now. > > For example, I have X installed inside a chroot. This chroot has a local > policy-rc.d that prohibits any daemons being started, because I don't > want port conflicts with systems outside the chroot to occur when I > install or upgrade a package. So if I want to manually start xdm or some > other daemon, invoke-rc.d is useless to me. > > Another example: I may be in single user mode, and want to start bind, > so I can do some network administration. invoke-rc.d's default policy > would not let it start. This kind of thing makes invoke-rc.d a poor > choice of software for an admin who wants the compter to do what he > tells it to do. It's name is also longer to type. ;-) Well, the scope of this discussion is a pair of manpages, xdm.options(5) and xfs.options(5). Do you object to me documenting invoke-rc.d there instead of /etc/init.d? -- G. Branden Robinson| Never attribute to human stupidity Debian GNU/Linux | that which can be adequately [EMAIL PROTECTED] | explained by GNU Libtool. http://people.debian.org/~branden/ | -- Scott James Remnant signature.asc Description: Digital signature
Bug#226162: marked as done (Some patches have a name mismatch)
Your message dated Fri, 23 Apr 2004 12:30:26 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#226162: Some patches have a name mismatch 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 responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at maintonly) by bugs.debian.org; 4 Jan 2004 22:05:15 + >From [EMAIL PROTECTED] Sun Jan 04 16:05:14 2004 Return-path: <[EMAIL PROTECTED]> Received: from smtp3.libero.it [193.70.192.127] by master.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Ad68f-00077T-00; Sun, 04 Jan 2004 05:09:45 -0600 Received: from Steffi (151.41.185.46) by smtp3.libero.it (7.0.020-DD01) id 3F6F04A601E62B2A for [EMAIL PROTECTED]; Sun, 4 Jan 2004 12:09:45 +0100 Received: from paolo by Steffi with local (Exim 3.36 #1 (Debian 3.0/Woody)) id 1Ad64u-00023E-00 for <[EMAIL PROTECTED]>; Sun, 04 Jan 2004 12:05:52 +0100 From: Paolo Ulivi <[EMAIL PROTECTED]> Organization: Lusty & Gorgeous Software, Ltd. To: [EMAIL PROTECTED] Subject: Some patches have a name mismatch Date: Sun, 4 Jan 2004 12:05:52 +0100 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <[EMAIL PROTECTED]> Sender: Paolo Ulivi <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-master.debian.org_2003_11_25-bugs.debian.org_2004_1_3 (1.212-2003-09-23-exp) on master.debian.org X-Spam-Status: No, hits=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no version=2.60-master.debian.org_2003_11_25-bugs.debian.org_2004_1_3 X-Spam-Level: Package: xfree86 Version: 4.2.1-15 Running debian/rules checksource on my system gives the following results: Applying patch debian/patches/001b_m68k_haslinuxinput_too.diff...dry run failed. patching file config/cf/linux.cf Hunk #1 FAILED at 157. 1 out of 1 hunk FAILED -- saving rejects to file config/cf/linux.cf.rej make: *** [debian/stampdir/patchapply] Error 1 Another run after correcting the problem shows another one: # make sure all the patches applied cleanly debian/stampdir/ patches/011a_recognize_glibc_2.3.2_locale_names.diff.log:Hunk #1 succeeded at 839 (offset 1 line). debian/stampdir/patches/011_chinese_locale_fixups.diff.log:Hunk #1 succeeded at 636 (offset 1 line). Some patches did not apply cleanly. Please investigate. make: *** [checksource] Error 1 After investigating I found that my system sort the patches names in an alphabetical order which doesn't correspond to the correct order of their application. I solved renaming all offending patches in this manner: 001a_linux_cf.diff(was 001_linux_cf.diff) 001b_damn_cpp_3.3_to_hell.diff(was 001a_damn_cpp_3.3_to_hell.diff 001c_m68k_haslinuxinput_too.diff (was 001b_m68k_haslinuxinput_too.diff) 011a_chinese_locale_fixups.diff (was 011_chinese_locale_fixups.diff) 011b_recognize_glibc_2.3.2_locale_names.diff (was 011a_recognize_glibc_2.3.2_locale_names.diff) 011c_recognize_ko_KR.EUC-KR_locale.diff (was 011b_recognize_ko_KR.EUC-KR_locale.diff) Dunno if this is happening to me only in all of the world :-) Have a happy new year, Paolo -- Paolo Ulivi pulivi AT libero DOT it GPG KeyID: 5C4F3D94 GPG Fingerprint: 3AF7 BFA2 3DE6 6A73 5379 5E0A 0949 6A1E 5C4F 3D94 If Linux is not Unix then Windows are not Gates Anonymous, XXI Century --- Received: (at 226162-done) by bugs.debian.org; 23 Apr 2004 17:30:27 + >From [EMAIL PROTECTED] Fri Apr 23 10:30:27 2004 Return-path: <[EMAIL PROTECTED]> Received: from dhcp065-026-182-085.indy.rr.com (redwald.deadbeast.net) [65.26.182.85] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1BH4VP-0002sg-00; Fri, 23 Apr 2004 10:30:27 -0700 Received: by redwald.deadbeast.net (Postfix, from userid 1000) id AD6F5642B7; Fri, 23 Apr 2004 12:30:26 -0500 (EST) Date: Fri, 23 Apr 2004 12:30:26 -0500 From: Branden Robinson <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: Bug#226162: Some patches have a name mismatch Message-ID: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="w2xx78T4DcG3O+DJ" Content-Disposition: inline In-Reply-To: <[EMAIL PROTECTED]> User-Agent: Mutt/1.5.5.1+cvs20040105i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.
Processed: Re: Processed: severity of 199111 is wishlist, merging 199111 205564
Processing commands for [EMAIL PROTECTED]: > close 205564 Bug#205564: xfree86: have dexconf and xfs use Type1 font path after bitmapped font paths 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Eduard Bloch <[EMAIL PROTECTED]> > merge 199111 205564 Bug number 199111 not found. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: Re: Bug#220493: Want a more recent version of the XFree86-server
Processing commands for [EMAIL PROTECTED]: > retitle 220493 xfree86: please package XFree86 4.4 Bug#220493: xfree86: new upstream version is going to be available, please package it before it's released Changed Bug title. > tag 220493 + wontfix Bug#220493: xfree86: please package XFree86 4.4 There were no tags set. Tags added: wontfix > On Thu, Nov 13, 2003 at 12:34:50AM +0100, Uwe Storbeck wrote: Unknown command or malformed arguments to command. > > in general I'm a friend of the somewhat conservative strategie of the Unknown command or malformed arguments to command. > > Debian project, but ... Unknown command or malformed arguments to command. > > Unknown command or malformed arguments to command. > > The XFree86 project is going to release version 4.4 of it's server Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: Re: Bug#227005: xfree86: Patch to build XDirectFB server
Processing commands for [EMAIL PROTECTED]: > tag 227005 - patch Bug#227005: xfree86: Patch to build XDirectFB server There were no tags set. Tags removed: patch > tag 227005 + moreinfo Bug#227005: xfree86: Patch to build XDirectFB server There were no tags set. Tags added: moreinfo > retitle 227005 xfree86: build XDirectFB X server Bug#227005: xfree86: Patch to build XDirectFB server Changed Bug title. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#229850: xserver-xfree86: Nokia 446Xpro properly detected but sync incorrect
On Wed, Apr 21, 2004 at 04:33:22AM -0400, Jay Berkenbilt wrote: > Here it is. I see the correct ranges in the output below. When > Debian Installer beta 4 is released, I'll probably do a reinstall from > scratch and see what happens. > > For kicks, I just moved my /etc/X11/XF86Config-4 out of the way, ran > dpkg-reconfigure xserver-xfree86 in high priority mode accepting > defaults (where the system did actually believe that 1280x1024 at 85 > Hz was my best mode) and then reran dexconfig. I got the same default > values as reported in my original bug report, not the values detected > below. I don't know whether that information is useful to you. > > My system is very current -- my last apt-get dist-upgrade was on April > 18. [...] > Section "Monitor" > # Block type: 2:0 3:fd > # Block type: 2:0 3:ff > # Block type: 2:0 3:fc > Identifier "Nokia 446XproNOK" > VendorName "NOK" > ModelName "Nokia 446XproNOK" > # Block type: 2:0 3:fd > HorizSync 30-107 > VertRefresh 50-150 [...] Hmmm. Okay, can you please do the following? 1) su 2) mv /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.previous 3) dpkg -P --force-depends xserver-xfree86 4) export DEBUG_XFREE86_DEBCONF=yes DEBIAN_FRONTEND=readline 5) script 6) apt-get install xserver-xfree86 7) exit 8) exit 9) mailx -s "Bug#229850: xserver-xfree86: Nokia 446Xpro properly detected but sync incorrect" \ [EMAIL PROTECTED] < typescript -- G. Branden Robinson| If God had intended for man to go Debian GNU/Linux | about naked, we would have been [EMAIL PROTECTED] | born that way. http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Bug#218614: marked as done (Branden, please apply attached patch (Was Re: Driver SDK.))
Your message dated Fri, 23 Apr 2004 12:53:36 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#218614: Branden, please apply attached patch (Was Re: Driver SDK.) 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 responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 1 Nov 2003 16:11:42 + >From [EMAIL PROTECTED] Sat Nov 01 10:11:29 2003 Return-path: <[EMAIL PROTECTED]> Received: from smtp4.wanadoo.fr (mwinf0404.wanadoo.fr) [193.252.22.27] by master.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1AFyLZ-0008JM-00; Sat, 01 Nov 2003 10:11:29 -0600 Received: from iliana (AStrasbourg-206-1-21-96.w81-50.abo.wanadoo.fr [81.50.14.96]) by mwinf0404.wanadoo.fr (SMTP Server) with ESMTP id A9A0238000B7; Sat, 1 Nov 2003 17:11:27 +0100 (CET) Received: from luther by iliana with local (Exim 3.36 #1 (Debian)) id 1AFyLW-0003Z1-00; Sat, 01 Nov 2003 17:11:26 +0100 Date: Sat, 1 Nov 2003 17:11:26 +0100 To: [EMAIL PROTECTED] Cc: debian-x@lists.debian.org Subject: Branden, please apply attached patch (Was Re: Driver SDK.) Message-ID: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="OgqxwSJOaUobr8KG" Content-Disposition: inline In-Reply-To: <[EMAIL PROTECTED]> User-Agent: Mutt/1.5.4i From: Sven Luther <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Status: No, hits=-14.6 required=4.0 tests=BAYES_30,EMAIL_ATTRIBUTION,HAS_PACKAGE,PATCH_UNIFIED_DIFF, QUOTED_EMAIL_TEXT autolearn=ham version=2.53-bugs.debian.org_2003_11_1 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_11_1 (1.174.2.15-2003-03-30-exp) --OgqxwSJOaUobr8KG Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Package: xfree86 Version: 4.3.0-0pre1v4 Severity: wishlist On Fri, Oct 31, 2003 at 04:14:15PM +0100, Sven Luther wrote: > Hello, > > I attach here a draft of the smallish patch to enable the building of > the driver SDK. The patch only patches the debian directory, and no > upstream patch is needed anymore, since the 000_post430.diff patch > already includes them. Ok, here attached is what i think a final version of the driver sdk. The only remaining thing is to attach some documentation in the README.Debian file, but i will first need to actually use the package to build some drivers before i write it. I will probably add some make-kpkg like stuff to the tarball in future, so users can simply do a dpkg-buildpackage in the unpacked directory, and build an alternative driver package, but this can be done later on. Anyway Branden, please apply this patch to your main tree, it is fully orthogonal to anything else. Maybe you would like to have a DONT_BUILD_SDK or something such option added though, like you have a DONT_BUILD_SERVER one, if so, ask me about it, and i will implement it. The patch come in two parts, the actual patch sdk.diff, which add the needed stuff to debian/rules and debian/control, and the MANIFEST.diff, which is the diff for the added SDK files on x86. Friendly, Sven Luther --OgqxwSJOaUobr8KG Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: attachment; filename="sdk.diff" diff -urN debian.orig/control debian/control --- debian.orig/control 2003-10-31 13:33:23.0 +0100 +++ debian/control 2003-10-31 13:25:43.0 +0100 @@ -1195,3 +1195,13 @@ This package smooths upgrades from Debian 3.0 by depending on xlibs-static-pic. This pseudopackage is only depended upon by packages that haven't yet corrected their dependencies to reflect the new package name. + +Package: xfree86-driver-sdk +Architecture: any +Depends: xlibs-dev +Description: XFree86 driver development kit. + The XFree86 driver SDK (DDK would have been a better name) contain everything + that is needed to rebuild the video drivers. It can be used either to apply + some patch to the driver and rebuild them or to build the drivers from the + xfree86 CVS HEAD or from other third party sources. + diff -urN debian.orig/rules debian/rules --- debian.orig/rules 2003-10-31 13:33:22.0 +0100 +++ debian/rules2003-10-31 13:26:00.0 +0100 @@ -244,7 +244,7 @@ ifndef test_rules umask 022 dh_clean -k - $(MAKE) -C $(SOURCE_TREE) SHELL="/bin/sh -e" DESTDIR=$(DEBTREEDIR) install install.man install.sdk + $(MAKE) -C $(SOURCE_TREE) SHELL="/bin/sh -e" DESTDIR=$(DEBTREEDIR) install install.man # install Debian's font
Processed: Re: Bug#233569: xlibs: raise the number of maximum clients to 512
Processing commands for [EMAIL PROTECTED]: > tag 233569 + wontfix Bug#233569: xfree86: kick MAXCLIENTS up to 512 in Xserver, xfs, lbxproxy Tags were: upstream Tags added: wontfix > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: retitle 180689 to xserver-xfree86: [debconf] want question about mouse resolution parameter
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.7.95.1 > # damn typos > retitle 180689 xserver-xfree86: [debconf] want question about mouse > resolution parameter Bug#180689: xserver-xfree86: [dbeconf] want question about mouse resolution parameter Changed Bug title. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: retitle 245541 to xfree86: package XFree86 DDK
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.7.95.1 > retitle 245541 xfree86: package XFree86 DDK Bug#245541: xfree86: would like X server LinkKit package Changed Bug title. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: triage: xfree86 "source" package
Processing commands for [EMAIL PROTECTED]: > # #201871: Problems with XFree86 in Debian Woody > # Package: xfree86; Reported by: =?iso-8859-2?B?TWljaGGz?= <[EMAIL > PROTECTED]>; Tags: moreinfo; 280 days old. > retitle 201871 xserver-xfree86: [nv] server will not start with 'UseFBDev' > 'true' on GeForce2 MX rev 178 Bug#201871: Problems with XFree86 in Debian Woody Changed Bug title. (By the way, that Bug is currently marked as done.) > reassign 201871 xserver-xfree86 Bug#201871: xserver-xfree86: [nv] server will not start with 'UseFBDev' 'true' on GeForce2 MX rev 178 Bug reassigned from package `xfree86' to `xserver-xfree86'. > # #202128: [Fwd([Fwd:xwindow's not starting for me in Debian 3.0 woody])] > # Package: xfree86; Reported by: Godfrey Harrison <[EMAIL PROTECTED]>; Tags: > moreinfo; 278 days old. > retitle 202128 xserver-xfree86: [i810] server will not start on unknown > chipset (0x2562) rev 1 Bug#202128: [Fwd([Fwd:xwindow's not starting for me in Debian 3.0 woody])] Changed Bug title. (By the way, that Bug is currently marked as done.) > reassign 202128 xserver-xfree86 Bug#202128: xserver-xfree86: [i810] server will not start on unknown chipset (0x2562) rev 1 Bug reassigned from package `xfree86' to `xserver-xfree86'. > # #205129: XFree86 and ATI Radeon 7500. (2) > # Package: xfree86; Reported by: Goldfinger <[EMAIL PROTECTED]>; 254 days old. > retitle 205129 xserver-xfree86: server will not start on ATI Radeon 7500 Bug#205129: XFree86 and ATI Radeon 7500. (2) Changed Bug title. > reassign 205129 xserver-xfree86 Bug#205129: xserver-xfree86: server will not start on ATI Radeon 7500 Bug reassigned from package `xfree86' to `xserver-xfree86'. > # #213267: xfree86 problems > # Package: xfree86; Reported by: =?iso-8859-1?q?Marco=20Figueira?= <[EMAIL > PROTECTED]>; 206 days old. > retitle 213267 xserver-xfree86: [sis] unspecified problem on 6326 rev 11 Bug#213267: xfree86 problems Changed Bug title. > reassign 213267 xserver-xfree86 Bug#213267: xserver-xfree86: [sis] unspecified problem on 6326 rev 11 Bug reassigned from package `xfree86' to `xserver-xfree86'. > # #213851: Updating xfree86 on testing breaks some fonts > # Package: xfree86; Reported by: Mason Thomas <[EMAIL PROTECTED]>; 203 days > old. > reassign 213851 xbase-clients: [xcalc] SEGVs when Type1 fonts in the FontPath Bug#213851: Updating xfree86 on testing breaks some fonts Warning: Unknown package 'xcalc' Warning: Unknown package 'segvs' Warning: Unknown package 'when' Warning: Unknown package 'type1' Warning: Unknown package 'fonts' Warning: Unknown package 'in' Warning: Unknown package 'fontpath' Bug reassigned from package `xfree86' to `xbase-clients: [xcalc] segvs when type1 fonts in the fontpath'. > severity 213851 important Bug#213851: Updating xfree86 on testing breaks some fonts Warning: Unknown package 'xcalc' Warning: Unknown package 'segvs' Warning: Unknown package 'when' Warning: Unknown package 'type1' Warning: Unknown package 'fonts' Warning: Unknown package 'in' Warning: Unknown package 'fontpath' Severity set to `important'. > # #220515: debian installer > # Package: xfree86; Reported by: Liam Healy <[EMAIL PROTECTED]>; 162 days old. > retitle 220515 xserver-xfree86: server will not start on S3 Trio 64 3D Bug#220515: debian installer Changed Bug title. > reassign 220515 xserver-xfree86 Bug#220515: xserver-xfree86: server will not start on S3 Trio 64 3D Bug reassigned from package `xfree86' to `xserver-xfree86'. > # #222976: pb matrox G450 > # Package: xfree86; Reported by: Georges Herfeld <[EMAIL PROTECTED]>; 140 > days old. > retitle 222976 xserver-xfree86: [mga] server will not start with 'UseFBDev' > 'true' on MGA G400 AGP rev 133 Bug#222976: pb matrox G450 Changed Bug title. > reassign 222976 xserver-xfree86 Bug#222976: xserver-xfree86: [mga] server will not start with 'UseFBDev' 'true' on MGA G400 AGP rev 133 Bug reassigned from package `xfree86' to `xserver-xfree86'. > # #226162: Some patches have a name mismatch > # Package: xfree86; Reported by: Paolo Ulivi <[EMAIL PROTECTED]>; 109 days > old. > retitle 226162 xfree86: patches don't apply in correct order when locale > collation order is not C Bug#226162: Some patches have a name mismatch Changed Bug title. (By the way, that Bug is currently marked as done.) > # #239827: wrong keymap for XFree86 at install > # Package: xfree86; Reported by: Patrice Fortier <[EMAIL PROTECTED]>; 30 days > old. > retitle 239827 xserver-xfree86: [debconf] wrong keymap for XFree86 at install Bug#239827: wrong keymap for XFree86 at install Changed Bug title. > reassign 239827 xserver-xfree86 Bug#239827: xserver-xfree86: [debconf] wrong keymap for XFree86 at install Bug reassigned from package `xfree86' to `xserver-xfree86'. > merge 238778 239827 Bug#238778: xserver-xfree86: [debconf] set XKB question defaults based on debian-installer/keymap Bug#239827: xserver-xfree86: [debconf] wrong keymap for XFree86 at install Bug#242321: xserver-xfree86: [debconf] de
Processed: retitle 242605 to xserver-xfree86 [debconf] why default to U.S. keyboard layout?
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.7.95.1 > retitle 242605 xserver-xfree86 [debconf] why default to U.S. keyboard layout? Bug#242605: xserver-xfree86: [i18n] Why american keyboard layout? Changed Bug title. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: retitle 197156 to xfree86: dexconf and xfs should use x-ttcidfont-conf font paths by default
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.7.95.1 > retitle 197156 xfree86: dexconf and xfs should use x-ttcidfont-conf font > paths by default Bug#197156: dexconf and xfs should include the fontpaths by x-ttcidfont-conf Changed Bug title. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: reassign 213851 to xbase-clients ...
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.7.95.1 > reassign 213851 xbase-clients Bug#213851: Updating xfree86 on testing breaks some fonts Warning: Unknown package 'xcalc' Warning: Unknown package 'segvs' Warning: Unknown package 'when' Warning: Unknown package 'type1' Warning: Unknown package 'fonts' Warning: Unknown package 'in' Warning: Unknown package 'fontpath' Bug reassigned from package `xbase-clients: [xcalc] segvs when type1 fonts in the fontpath' to `xbase-clients'. > retitle 213851 xbase-clients: [xcalc] SEGVs when Type1 fonts in the FontPath Bug#213851: Updating xfree86 on testing breaks some fonts Changed Bug title. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#223089: xserver-xfree86-dbg: daily to weekly hang on rage 128 hardware
On Wed, Apr 21, 2004 at 07:01:19PM -0700, Matthew Hughes wrote: > No, I haven't seen this in a couple of months. Thanks! > Matt Ordinarily I'd close this, but other people are reporting the same problem, and very recently, so I don't think the problem is truly resolved. -- G. Branden Robinson|Those who fail to remember the laws Debian GNU/Linux |of science are condemned to [EMAIL PROTECTED] |rediscover some of the worst ones. http://people.debian.org/~branden/ |-- Harold Gordon signature.asc Description: Digital signature
Bug#227005: xfree86: Patch to build XDirectFB server
On Friday 23 April 2004 19:59, Branden Robinson wrote: > > Basically, it's a patch for the xfree86 source package generating a > > XDirectFB binary. Only this binary is different from the ordinary > > xserver-xfree86 installation. > > Er, uh, where's the patch? Sorry, here. Taken from http://directfb.org/download/XDirectFB/XDirectFB-1.0-rc5.tar.gz. Micha Index: config/cf/linux.cf === RCS file: /cvs/xc/config/cf/linux.cf,v retrieving revision 3.203 diff -p -u -r3.203 linux.cf --- config/cf/linux.cf 2003/04/24 22:14:53 3.203 +++ config/cf/linux.cf 2003/05/22 23:32:03 @@ -958,6 +958,8 @@ InstallNamedTargetNoClobber(install,file #include #ifdef KDriveXServer # include +#elif defined (XDirectFBServer) +# include #else # include #endif Index: programs/Xserver/Imakefile === RCS file: /cvs/xc/programs/Xserver/Imakefile,v retrieving revision 3.284 diff -p -u -r3.284 Imakefile --- programs/Xserver/Imakefile 2003/05/14 05:27:53 3.284 +++ programs/Xserver/Imakefile 2003/05/22 23:32:04 @@ -488,6 +488,25 @@ ServerTarget(Xhp,$(HPSUBDIRS),$(HPOBJS), #endif /* XhpServer */ +#if XDirectFBServer +XCOMM +XCOMM X DirectFB server +XCOMM +FBDIR = fb +DIRECTFBDDXDIR = hw/directfb +DIRECTFBDIRS = $(STDDIRS) $(FBDIR) $(DIRECTFBDDXDIR) $(DEPDIRS) +DIRECTFBOBJS = +DIRECTFBLIBS = PreFbLibs $(DIRECTFBDDXDIR)/LibraryTargetName(directfb) FbPostFbLibs +DIRECTFBSYSLIBS = $(FONTLIBS) $(SYSLIBS) $(XLIB) `directfb-config --libs` +SetUIDServerTarget(XDirectFB,$(DIRECTFBDIRS),$(DIRECTFBOBJS), \ + $(DIRECTFBLIBS),$(DIRECTFBSYSLIBS)) + +#ifndef ServerToInstall +#define ServerToInstall XDirectFB +#endif +#endif /* XDirectFBServer */ + + #if HasParallelMake XCOMM XCOMM force non-parallel build of XF86 servers to prevent MUTEX overrides @@ -1339,7 +1358,7 @@ MIEXTDIRS = $(SHADOWDIR) $(LAYERDIR) $(R IPLANDIRS = $(IPLAN2P2DIR) $(IPLAN2P4DIR) $(IPLAN2P8DIR) DDXDIRS = $(DECWSDDXDIR) $(SUNDDXDIR) $(LYNXDDXDIR) \ $(HPDDXDIR) $(XFREE86DDXDIR) $(XWINDDXDIR) $(DARWINDDXDIR) \ - $(XVFBDDXDIR) $(XNESTDDXDIR) + $(DIRECTFBDDXDIR) $(XVFBDDXDIR) $(XNESTDDXDIR) SUBDIRS = $(STDDIRS) $(MFBDIR) $(CFBDIRS) $(IPLANDIRS) $(ILBMDIR) $(AFBDIR) \ $(LMFCFBDIR) $(DDXDIRS) $(FBDIR) $(KDRIVEDIRS) $(MIEXTDIRS) \ $(XWINPARSERDIR) Index: programs/Xserver/Xserver.man === RCS file: /cvs/xc/programs/Xserver/Xserver.man,v retrieving revision 3.23 diff -p -u -r3.23 Xserver.man --- programs/Xserver/Xserver.man 2003/04/14 20:37:17 3.23 +++ programs/Xserver/Xserver.man 2003/05/22 23:32:04 @@ -713,7 +713,7 @@ Controlling the server once started: \fI .PP Server-specific man pages: \fIXdec\fP(1), \fIXmacII\fP(1), \fIXsun\fP(1), \fIXnest\fP(1), -\fIXvfb\fP(1), \fIXFree86\fP(1), \fIXDarwin\fP(1). +\fIXvfb\fP(1), \fIXFree86\fP(1), \fIXDarwin\fP(1), \fIXDirectFB\fP(1). .PP Server internal documentation: .I "Definition of the Porting Layer for the X v11 Sample Server" Index: programs/Xserver/fb/fbcmap.c === RCS file: /cvs/xc/programs/Xserver/fb/fbcmap.c,v retrieving revision 1.6 diff -p -u -r1.6 fbcmap.c --- programs/Xserver/fb/fbcmap.c 2001/10/28 03:33:08 1.6 +++ programs/Xserver/fb/fbcmap.c 2003/05/22 23:32:04 @@ -37,7 +37,7 @@ THE USE OR PERFORMANCE OF THIS SOFTWARE. #include "resource.h" #include "fb.h" -#ifndef XFree86Server +#if !defined(XFree86Server) && !defined(DIRECTFBSERVER) ColormapPtr FbInstalledMaps[MAXSCREENS]; int
Bug#172962: IPv6 support
On Fri, 23 Apr 2004, Branden Robinson wrote: > What exactly *is* going on with IPv6 support these days? I understand > it's caused a lot of grief for X.Org and XFree86 4.4, crazy breakage in > xdm and stuff. But maybe things have settled down. Yes i have been following the development for a while. The patch that is in svn compiles but there is an error in CreateWellKnownSockets (or something similar) down into xlibs that i didn't had the time to fix yet. The breakage were fixed (at least according to the discussions on some xfree86 mailing lists) and they were all related to the different behaviour of bsd, solaris and linux kernel in handling sockets. That required some bits to be tuned here and there. > Can you send a status report to this bug some time when you get a > chance? Status: we the actual amount of tasks and the things going on i doubt i can manage to do anything useful in less than a few weeks ( around a month i think ). We will see how far we can go otherwise tough luck. IPv6 is nice but we need to be realistic that it might not be in for sarge, until someone wants to help (debian-ipv6 in CC). > Also, if you're still the overlord of this issue, please mail the > following to [EMAIL PROTECTED]: > > owner 172962 [EMAIL PROTECTED] done :-) 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.
Processed: your mail
Processing commands for [EMAIL PROTECTED]: > owner 172962 [EMAIL PROTECTED] Bug#172962: xfree86: want IPv6 support Bug#153075: xfree86: clients unable to connect to X server via IPv6 Owner recorded as [EMAIL PROTECTED] > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Re: Processed: 008_fix_xgetpw_macro.diff breaks Xlib API.
On Fri, Apr 23, 2004 at 01:58:24PM -0500, Branden Robinson wrote: > On Thu, Apr 22, 2004 at 12:12:24AM -0700, Chris Waters wrote: > > So technically, what we have here is two bugs. One against OpenMotif > > for depending on X internal symbols (symbols with mandatorily > > undefined behavior, at that). And one against X upstream for code > > with undefined behavior. > I don't see why why a private function shouldn't be able to do whatever > it wants. Can you name a private function "errno"? No, that's a reserved name. Can you name an private function "_x11_fobar"? Technically, no, you cannot, that's a reserved name! All names that start with underscore are reserved by the language standard. Now, I freely grant that in practice, if you're careful, you'll get away with it 999,999 times out of a million. But that doesn't make it legal. It simply makes it relatively unimportant. It's similar to (though MUCH safer than) code that uses "void main()", which also tends to work in practice. Note that I have not filed any bug reports about this. The only reason I even mentioned it is that Daniel was harrassing some poor fellow who happened to mention, in passing, the fact that such identifiers are technically forbidden. Well, Daniel was wrong, and the original poster was right, so I quoted chapter and verse to show that Daniel was wrong. It's not a big deal, I was just defending the poor guy. And I have to say, after reading Daniel's irrelevant and incoherent response to my post, I have a much greater understanding of why you decided to stop working with him! :) cheers p.s. note that I removed [EMAIL PROTECTED] from the followup, because I'm not discussing, nor interested in, what openmotif is doing. -- Chris Waters | Pneumonoultra-osis is too long [EMAIL PROTECTED] | microscopicsilico-to fit into a single or [EMAIL PROTECTED] | volcaniconi- standalone haiku
X Strike Force XFree86 SVN commit: r1313 - trunk/debian
Author: branden Date: 2004-04-23 17:16:08 -0500 (Fri, 23 Apr 2004) New Revision: 1313 Modified: trunk/debian/changelog Log: (cosmetic) Technically, Branden has a PowerPC 750 processor, not a 740. Modified: trunk/debian/changelog === --- trunk/debian/changelog 2004-04-23 17:52:46 UTC (rev 1312) +++ trunk/debian/changelog 2004-04-23 22:16:08 UTC (rev 1313) @@ -23,7 +23,7 @@ requirements of dbs) has been re-packed using gzip instead of bzip2. This increases the size of the .orig tar archive by 10MB (a 21% increase), but speeds unpacking of the stored tar achive from 2m49s to 39s on a 400MHz -PowerPC 740 (G3) processor with 512MB of RAM. +PowerPC 750 (G3) processor with 512MB of RAM. * Add FAQ entry about the key problem. Edit news item about the problem to tidy up the wording a little and direct people to the
Re: Outstanding ITP - gatos-drm-source
Michel Dänzer wrote: >> > Also, are you aware of the bugs being filed about the non-free >> > microcode in the DRM? >> >> No, I'll look at that. You mean DRM from DRI or from GATOS ? > > Any flavour, the microcode is the same everywhere. I've been trying to figure out who really holds the microcode copyright; I suspect the DRI tree is inaccurate on this point (claiming that the ATI microcode copyright is held by VALinux). Because of this, I believe there's no explicit permission to redistribute it, and I hope someone calls ATI soon. :-) -- There are none so blind as those who will not see.
Re: Bug#242865: The "moreinfo" for these drivers/binary executables
Branden Robinson wrote: > tag 242865 - moreinfo > thanks > > On Fri, Apr 16, 2004 at 07:24:16PM -0400, Nathanael Nerode wrote: >> This is the list of files known to be affected by this bug: >> >> xc/programs/Xserver/hw/xfree86/drivers/mga/mga_ucodexch >> xc/programs/Xserver/hw/xfree86/drivers/rendition/v10002dxcuc >> xc/programs/Xserver/hw/xfree86/drivers/rendition/v20002dxcuc >> xc/programs/Xserver/hw/xfree86/os-support/shared/drm/kernel/r128_ccexcc >> xc/programs/Xserver/hw/xfree86/os-support/shared/drm/kernel/radeon_cpxcc >> xc/programs/Xserver/hw/xfree86/os-support/shared/drm/kernel/mga_ucode.h > > I think you mean: > > xc/programs/Xserver/hw/xfree86/drivers/mga/mga_ucode.h > xc/programs/Xserver/hw/xfree86/drivers/rendition/v10002d.uc > xc/programs/Xserver/hw/xfree86/drivers/rendition/v20002d.uc > xc/programs/Xserver/hw/xfree86/os-support/shared/drm/kernel/r128_cce.c > xc/programs/Xserver/hw/xfree86/os-support/shared/drm/kernel/radeon_cp.c > xc/programs/Xserver/hw/xfree86/os-support/shared/drm/kernel/mga_ucode.h > > (global search and replace gone wrong?) Yes! Heh. Thanks for figuring out what I meant. :-) > >> These files all contain binary executables (to run on graphics card >> chips) >> with no source code at all. Therefore they fail the DFSG's requirements. >> >> Luckily, none of these files are actually *used* in Debian's XFree86 >> build, so removing them from the .tar.gz of Debian's XFree86 source >> should be an easy and trivial solution to this bug for sarge. >> >> (Different copies of the same binaries are present and used in the kernel >> packages, but those are being addressed elsewhere.) >> >> I don't think, therefore, that this bug needs to be tagged "moreinfo" any >> longer... > > Agreed. Thanks! > -- There are none so blind as those who will not see.
Bug#202128: acknowledged by developer (closing bug)
Hello Deb & Branden, too Thanks for the e-mail below. I don't understand your not getting more information: I sent some extra. What I sent I don't know now - so long ago! I've given up on Debian for the while so not to worry! Regards Godfrey Harrison On Saturday 24 April 2004 01:18, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > #202128: [Fwd([Fwd:xwindow's not starting for me in Debian 3.0 woody])], > which was filed against the xfree86 package. > > It has been closed by one of the developers, namely > Branden Robinson <[EMAIL PROTECTED]>. > > Their explanation is attached below. If this explanation is > unsatisfactory and you have not received a better one in a separate > message then please contact the developer, by replying to this email. > > Debian bug tracking system administrator > (administrator, Debian Bugs database) > > Received: (at 202128-done) by bugs.debian.org; 23 Apr 2004 17:05:32 + > From [EMAIL PROTECTED] Fri Apr 23 10:05:32 2004 > Return-path: <[EMAIL PROTECTED]> > Received: from dhcp065-026-182-085.indy.rr.com (redwald.deadbeast.net) > [65.26.182.85] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) > id 1BH47H-6H-00; Fri, 23 Apr 2004 10:05:32 -0700 > Received: by redwald.deadbeast.net (Postfix, from userid 1000) > id 2E057642B7; Fri, 23 Apr 2004 12:05:31 -0500 (EST) > Date: Fri, 23 Apr 2004 12:05:31 -0500 > From: Branden Robinson <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: closing bug > Message-ID: <[EMAIL PROTECTED]> > Mime-Version: 1.0 > Content-Type: multipart/signed; micalg=pgp-sha1; > protocol="application/pgp-signature"; boundary="tmoQ0UElFV5VgXgH" > Content-Disposition: inline > User-Agent: Mutt/1.5.5.1+cvs20040105i > Delivered-To: [EMAIL PROTECTED] > X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 > (1.212-2003-09-23-exp) on spohr.debian.org > X-Spam-Status: No, hits=-2.0 required=4.0 tests=BAYES_00 autolearn=no > version=2.60-bugs.debian.org_2004_03_25 > X-Spam-Level: > X-CrossAssassin-Score: 1 > > > --tmoQ0UElFV5VgXgH > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > Submitter was asked for more information on 24 July 2003. > > No reply. > > Closing bug from unresponsive submitter. > > --=20 > G. Branden Robinson|The basic test of freedom is > Debian GNU/Linux |perhaps less in what we are free to > [EMAIL PROTECTED] |do than in what we are free not to > http://people.debian.org/~branden/ |do. -- Eric Hoffer > > --tmoQ0UElFV5VgXgH > Content-Type: application/pgp-signature; name="signature.asc" > Content-Description: Digital signature > Content-Disposition: inline > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.2.4 (GNU/Linux) > > iEYEARECAAYFAkCJTNoACgkQ6kxmHytGonyslACgiFl4w9UYfKJWgaFuSa25+D4q > 0KcAnA7R9ww3YnE4ggJKiCvx8Vxqcf3+ > =PT+p > -END PGP SIGNATURE- > > --tmoQ0UElFV5VgXgH--
Re: Preparing -8
On Fri, 23 Apr 2004, Branden Robinson wrote: > Well, the scope of this discussion is a pair of manpages, xdm.options(5) > and xfs.options(5). > > Do you object to me documenting invoke-rc.d there instead of > /etc/init.d? Both arguments are valid imho and perhaps we can document both underlining that /etc/init.d is to be used by experienced people only that know what they are doing. Simple, easy and it will make everyone happy ;) 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.
