Bug#166335: Bad default configuration for XftConfig
On Sun, Oct 27, 2002 at 07:19:35PM -0500, [EMAIL PROTECTED] wrote: Could you come up with, and test, a patch to the stock Debian /etc/X11/XftConfig file that would work well with xfonts-scalable? Please generate a diff -u of the original and patched file, and mail that diff to this bug report. Here you are. At least, this gives reasonable default. If not satisfying, I could try to include defaults using packages ttf-freefont and xfonts-scalable. --- XftConfig 2002-10-26 12:32:36.0 +0200 +++ XftConfig.orig 2002-10-30 10:09:32.0 +0100 @@ -19,12 +19,3 @@ # match any family == charter edit family += bitstream charter; match any family == bitstream charter edit family =+ charter; - -match any spacing == 110 edit family =+ Courier 10 Pitch ; -match any spacing == 100 edit family =+ Courier 10 Pitch ; -match any spacing == 0 edit family =+ Bitstream Charter ; -match any size 1 edit - family =+ Helvetica ; - family =+ Arial ; - family =+ Bitstream Charter ; - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#167009: Additional details
On Mit, 2002-10-30 at 05:01, John Goerzen wrote: I tried downgrading to 4.2.1-1 (from 4.2.1-3) to see if that would improve matters. It apparently did not, although after one sleep my mouse alone remained responsive. However, I discovered that the machine was still listening on its airport interface and was able to log in and do some more debugging. It turns out that when X throws one of these fits, it's spinlocking. Running strace on it yields this sort of result, repeated over and over: ioctl(6, 0x20006444, 0) = -1 EBUSY (Device or resource busy) ioctl(6, 0x20006444, 0) = -1 EBUSY (Device or resource busy) --- SIGALRM (Alarm clock) --- ioctl(6, 0x20006444, 0) = -1 EBUSY (Device or resource busy) ioctl(6, 0x20006444, 0) = -1 EBUSY (Device or resource busy) --- SIGALRM (Alarm clock) --- ioctl(6, 0x20006444, 0) = -1 EBUSY (Device or resource busy) ioctl(6, 0x20006444, 0) = -1 EBUSY (Device or resource busy) ioctl(6, 0x20006444, 0) = -1 EBUSY (Device or resource busy) Now, looking at the X server process, I see that fd 6 is attached to /dev/dri/card0. Maybe a clue. As discussed many times on the debian-powerpc list, make sure APM emulation is enabled in the kernel, that /dev/apm_bios exists and that the X server log contains contains a line (II) Open APM successful Failing that, the X server can't react to the sleep cycle, and you need to switch to console for sleep. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#167009: Additional details
On Wed, Oct 30, 2002 at 11:05:32AM +0100, Michel D?nzer wrote: As discussed many times on the debian-powerpc list, make sure APM emulation is enabled in the kernel, that /dev/apm_bios exists and that the X server log contains contains a line I will check on these things and report back later today; however, I am still concerned that an X upgrade broke this. It worked fine before upgrading. Seems to me that if it could handle it before, it should be able to handle it now? Don't you think, too, that it should not require this emulation to work properly? (II) Open APM successful Failing that, the X server can't react to the sleep cycle, and you need to switch to console for sleep. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Configuration file handling (Re: [desktop] Unix configuration nightmare)
On Mon, Oct 28, 2002 at 11:54:54PM -0500, Branden Robinson wrote: On Wed, Oct 23, 2002 at 08:10:43PM -0400, Matt Zimmerman wrote: I don't think that existing .config handling necessarily needs to change at this point, unless we want to provide a standard way to suppress all attempts at automatic configuration for a particular config file. Well, Joey Hess is of the opinion that manage this config file with debconf-style questions are Evil and Wrong. So, assuming I want to get with the Debconf orthodoxy, I would be changing my config scripts to eliminate this sort of prompting. I can't speak for joeyh, but I think his beef is that maintainers use this kind of question to be lazy about preserving changes. I'm guilty of this myself, because I do not want to parse some arbitrary config format using shell commands to seed debconf with the appropriate responses. We're all about preserving changes here, so the light of the One True Way should guide us to salvation. I was thinking of things more similar to --force-confnew/--force-confold than to manage this config file with debconf questions. In other maintainer scripts, we need to be able to say I have generated a configuration file /tmp/blah as a possible replacement for /etc/foo/bar. At that point, the maintainer script is done with the file, and passes control to us. Here we run into a problem: * For most packages, the other maintainer script is going to be the postinst. In fact it's difficult for me to imagine a scenario when anything but the postinst would be generating a config file.[1] From my perspective, the tool doesn't care from which maintainer script it's called. postinst would seem to be the only useful place to call it, I agree. * The postinst, by definition, runs during the configuration phase. Your proposal is going to pull us farther away from the utopia of being able to handle all interactivity before packages are even unpacked, a la dpkg-preconfigure. While dpkg's conffile prompts already violate this, they *can* be replaced with pre-unpack prompting, because dpkg-preconfigure can suck new conffiles out of a package just as well as it can config and templates files. Non-conffile config files cannot enjoy this luxury, because they don't exist within the package. Right. As we discussed on IRC, there seems to be a fundamental conflict between preconfiguration and generated configuration files because the package is by definition not configured yet (for the new version) at preconfiguration time. Packages with simple requirements could theoretically generate a configuration in .config, but that is not the right place for it, and packages with simple requirements can use conffiles. I had not considered that one day dpkg could prompt about conffiles ahead of time. That weakens my no worse than conffiles argument considerably. Preconfiguration should remain unchanged in (IMO) the two most important cases: initial installation, and novice user. In the former case, we will never need to prompt in postinst, and in the latter, we should have a reasonable default for them. * On the other hand, if we're doing an upgrade instead of an install, the tool(s) we use to generate the config file may already be on the system at pre-configure time. However, if those tools change, and a package's .config script needs to be able to use the config-generation tool that's in the corresponding version of the package, you'd need to have a way of declaring this requirement so that config file generation could be deferred to package configuration. Not to mention the fact that the runtime dependencies of the tools used to generate the configuration files would need to be present at pre-configure time. Oy vey. Yes, this would be a mess. Upgrades from one Debian release to the next would be fragile and difficult to maintain and test effectively. We check again whether the file has been modified since last time by comparing it to a saved copy or checksum (the copy is optional, but gives much more flexibility than storing only a checksum). Why not just a checksum? Do you have a specific application in mind, or do you think the copy is a good idea for the sake of people cleverer than we? :) The copy makes it possible to calculate the merge. Since I am pretty confident that we will want merges, I think we should go ahead and use the copy for the comparison as well. It might be marginally more efficient to cache checksums for the comparison, but I doubt it will be worth worrying about. [prompts for various cases] In the common cases, this should be possible with a single prompt, though it could be split into two phases or selected from either a simple or advanced method, or even suppressed entirely for novice users if a sane default action sequence could be decided (always preserve? merge, and if that fails, preserve? warn?). As you
Bug#160182: ISO 8859-13 support for TrueType is incorrect
Does the directory with the fonts contain a proper encodings.dir file? In other words, have you run mkfontdir with the proper -e option? I am fairly positive that ISO 8859-13 does work correctly. However, it is not a built-in encoding, and the server relies on an encodings.dir file to locate its definition. (In 4.3.0, the server will automagically find the encoding file if it is at a standard location. The encodings.dir mechanism is still supported, though.) Juliusz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#164034: Resolution 1400x1050
...and neither does it support my IBM ThinkPad with a 1400x1050 resolution. Or my 16:9 monitor with 1920x1200 pixels. As an advanced option, one should be able to enter arbitrary sizes. -- |=| Michael Piefel |=| Humboldt-Universität zu Berlin |=| Tel. (+49 30) 2093 3831 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#156540: Impossible de demarrer X
J'ai fait l'aquistion de la distribution Debian Education. Je posséde un PC avec écran 17 pouces et carte graphique NVIDIA Geforce2. L'installation se déroule correctement mais impossible de démarrer XWindows. Que puis-je faire pour le démarrer? I need this bug report translated into English before I can address it. « I acquired the distribution Debian Education. I own a PC with a 17 « inch display and an NVIDIA Geforce2 graphic card. The installation « proceeds correctly but it is impossible to start XWindows. What can I « do to start it? » This is an installation problem, not a bug as such. Le plus probable est que vous n'avez pas installé X ; vérifiez la documentation de votre distribution pour vérifier. Si vous avez installé X et il est mal configuré, il créera un log (journal) dans le fichier /var/log/XFree86.0. Je vous suggère d'en envoyer le contenu sur la liste debian-users. Voyez sur www.debian.org pour la liste des listes de discussion. Attention : les listes Debian sont de langue anglaise. Si vous envoyez un message en français, vous risquez de vous faire mal voir. Salutations, Juliusz Chroboczek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#156598: GLX extension missing
Sorry to ask the obvious: you do ``Load glx'' in your XF86Config-4? Juliusz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#149631: [ati/atimisc] DoS attack possible when viewing absurdly huge fonts on Mach64 GT rev 65
This issue should hopefully be fixed upstream in 4.3.0. There will be no fix for 4.2. Juliusz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#162880: [s3virge] server causes sound distortion on ViRGE/DX or /GX rev 1
Does playing with the pci_burst and pci_retry options change anything? (See the s3virge manual page.) Juliusz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#156115: X server generates bogus font names for scalable fonts
No reply... Could I please ask you to tell me whether you can reproduce the problem without Tk, i.e. what happens if you do xfd -fn '-adobe-helvetica-medium-r-normal--12-*-75-75-p-*-iso8859-1' If the problem is not reproducible with xfd, it's a Tk bug, not an X bug. If it is reproducible with xfd, I will need the output of xlsfonts -ll -fn '-adobe-helvetica-medium-r-normal--12-*-75-75-p-*-iso8859-1' Regards, Juliusz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#151780: xfs: would like documentation on font install in doc/xfs
Font installation is documented in the README.fonts file (under xfree86-common). This file does not metion xfs as I (the author of the document) believe that xfs is a Bad Idea and do not wish to promote its use. However, font installation using xfs is documented in the xfs(1) manual page. With specifics of TrueType being described in README.fonts, all the information is indeed being provided. Juliusz P.S. Branden, the README.fonts file will undergo a partial rewrite for 4.3.0. I'm open to suggestions. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#165793: /usr/X11R6/man/man1/xlsfonts.1x.gz doesn't explain pattern good enough
The xlsfonts man page doesn't explain pattern good enough. $ man xlfonts ... Xlsfonts lists the fonts that match the given pattern. The wildcard character * may be used to match any sequence of characters (includ- ing none), and ? to match any single character. If no pattern is given, * is assumed. ... In what way is that not clear? Also the --help info should mention -fn in the latter part. Also it should say -l will tie up your machine, like it does on the man page. The included help is only a quick summary in case you know the command but forget an option. It should not contain explanations, which is what the man page is for. Juliusz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#148655: dex-mode selection doesn't provide 1400x1050 resolution
Note by the way that two default modelines for 1400x1050 have been included in XFree86 4.2.0 (after Debian 3.0). The list of default X server modelines is in hw/xfree86/common/xf86DefModes.c, and configuration tools could probably link against this file. Juliusz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#139826: please add en_GB@euro support
Please note that the en_GB.ISO8859-15 locale *is* supported by the X server (at least in current CVS). It uses the ISO 8859-15 character encoding, which makes the Euro sign available. However, it differs from an ``@euro'' variant because it uses the Pound, not the Euro, as the currency symbol. I believe that en_GB.ISO8859-15, not en_GB@euro, is what you want. The creation of an en_GB@euro locale before the UK commits to joining the Euro zone would be a political statement. Juliusz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#162880: [s3virge] server causes sound distortion on ViRGE/DX or /GX rev 1
Does playing with the pci_burst and pci_retry options change anything? (See the s3virge manual page.) DE I wish it did. I spent a couple of days with the s3virge manpage trying DE every possible combinition of variables I could think of, with no luck. I suspect you may have a hardware issue, then. I suggest you raise the issue on [EMAIL PROTECTED] Please do not omit to mention your X server version (4.1.0 as hacked by Debian, probably) and that you did try the pci_* options. Good luck, Juliusz P.S. Branden, that looks like an upstream issue to me. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#162880: [s3virge] server causes sound distortion on ViRGE/DX or /GX rev 1
Does playing with the pci_burst and pci_retry options change anything? (See the s3virge manual page.) I wish it did. I spent a couple of days with the s3virge manpage trying every possible combinition of variables I could think of, with no luck. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#162880: [s3virge] server causes sound distortion on ViRGE/DX or /GX rev 1
I suspect you may have a hardware issue, then. Not sure what hardware issue means. I do have a cheap card, but I don't experience problems with the old (version 3) xserver. Anyway, I appreciate your help and the Debian project. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#160182: ISO 8859-13 support for TrueType is incorrect
Does the directory with the fonts contain a proper encodings.dir file? In other words, have you run mkfontdir with the proper -e option? No, I do not have any encodings.dir files. What I run is: ttmkfdir fonts.scale mkfontdir All other encodings work fine except for ISO 8859-13. Please note that these are all TrueType fonts. -- \\// Peter - http://www.softwolves.pp.se/ I do not read or respond to mail with HTML attachments. Statement concerning unsolicited e-mail according to Swedish law: http://www.softwolves.pp.se/peter/reklampost.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#156115: X server generates bogus font names for scalable fonts
No reply... Could I please ask you to tell me whether you can reproduce the problem without Tk, i.e. what happens if you do xfd -fn '-adobe-helvetica-medium-r-normal--12-*-75-75-p-*-iso8859-1' If the problem is not reproducible with xfd, it's a Tk bug, not an X bug. If it is reproducible with xfd, I will need the output of xlsfonts -ll -fn '-adobe-helvetica-medium-r-normal--12-*-75-75-p-*-iso8859-1' Regards, Juliusz The problem can't be reproduced with your commands but the following shows a problem similar to the one with Tk: xfd -fn `xlsfonts -fn -*-helvetica-medium-r-normal-*-12-*-*-*-*-*-iso8859-1 | head -1` The problem is that xserver generates fontnames with fixed size for Type1 scalable fonts and some (or all?) of these fonts look considerable worse than the corresponding fixed size fonts: $ xlsfonts -fn -*-helvetica-medium-r-normal-*-12-*-*-*-*-*-iso8859-1 -adobe-helvetica-medium-r-normal--12-116-75-75-p-0-iso8859-1 -adobe-helvetica-medium-r-normal--12-116-75-75-p-0-iso8859-1 -adobe-helvetica-medium-r-normal--12-120-75-75-p-67-iso8859-1 -adobe-helvetica-medium-r-normal--12-120-75-75-p-67-iso8859-1 $ xlsfonts -fn -*-helvetica-medium-r-normal-*-*-120-*-*-*-*-iso8859-1 -adobe-helvetica-medium-r-normal--12-120-75-75-p-0-iso8859-1 -adobe-helvetica-medium-r-normal--12-120-75-75-p-0-iso8859-1 -adobe-helvetica-medium-r-normal--12-120-75-75-p-67-iso8859-1 -adobe-helvetica-medium-r-normal--12-120-75-75-p-67-iso8859-1 -adobe-helvetica-medium-r-normal--17-120-100-100-p-88-iso8859-1 -adobe-helvetica-medium-r-normal--17-120-100-100-p-88-iso8859-1 Note that this happens only with certain sizes, for example a search for Helvetica 16 returns only fixed fonts: $ xlsfonts -fn -*-helvetica-medium-r-normal-*-16-*-*-*-*-*-iso8859-1 -adobe-helvetica-medium-r-normal--16-154-75-75-p-0-iso8859-1 -adobe-helvetica-medium-r-normal--16-154-75-75-p-0-iso8859-1 $ xlsfonts -fn -*-helvetica-medium-r-normal-*-*-160-*-*-*-*-iso8859-1 -adobe-helvetica-medium-r-normal--17-160-75-75-p-0-iso8859-1 -adobe-helvetica-medium-r-normal--17-160-75-75-p-0-iso8859-1 Can you explain why a search for Helvetica 12 returns a variable fixed font while Helvetica 16 returns only fixed fonts? The output of xlsfonts -ll with the two fonts gives the following result: $ xlsfonts -ll -fn '-adobe-helvetica-medium-r-normal--12-116-75-75-p-0-iso8859-1' name: -adobe-helvetica-medium-r-normal--12-116-75-75-p-0-iso8859-1 direction:left to right indexing: linear rows: 0x00 thru 0x00 (0 thru 0) columns: 0x00 thru 0xff (0 thru 255) all chars exist: no default char: 0x (0) ascent: 11 descent: 3 font type:Proportional (min and max widths not equal) bounds: width left right asc desc attr keysym min2 0 0-1-7 0x00bf max 12 21112 3 0x03f7 properties: 24 FOUNDRY urw FAMILY_NAME nimbus sans l WEIGHT_NAME regular SLANT r SETWIDTH_NAME normal ADD_STYLE_NAME PIXEL_SIZE12 POINT_SIZE116 RESOLUTION_X 75 RESOLUTION_Y 75 SPACING p AVERAGE_WIDTH 65 CHARSET_REGISTRY iso8859 CHARSET_ENCODING 1 FONT -urw-nimbus sans l-regular-r-normal--12-116-75-75-p-65-iso8859-1 COPYRIGHT (URW)++,Copyright 1999 by (URW)++ Design Development. See the file COPYING (GNU General se) for license conditions. As a special exception, permission is granted to include this font program in a Postscrip that consists of a document that contains text to be displayed or printed using this font, regardless of the conditi e applying to the document itself. RAW_PIXEL_SIZE1000 RAW_POINT_SIZE964 RAW_ASCENT953 RAW_DESCENT 285 RAW_AVERAGE_WIDTH 5435 FACE_NAME NimbusSanL-Regue FONT_TYPE Type 1 RASTERIZER_NAME X Consortium Type 1 Rasterizer $ xlsfonts -ll -fn '-adobe-helvetica-medium-r-normal--12-120-75-75-p-67-iso8859-1' name: -adobe-helvetica-medium-r-normal--12-120-75-75-p-67-iso8859-1 direction:left to right indexing: linear rows: 0x00 thru 0x00 (0 thru 0) columns: 0x00 thru 0xff (0 thru 255) all chars exist: no default char: 0x (0) ascent: 11 descent: 3 font type:Proportional (min and max widths not equal) bounds: width left right asc desc attr keysym min2 0 1-1-8 0x max
Processed: tagging 162880
Processing commands for [EMAIL PROTECTED]: tag 162880 + moreinfo Bug#162880: xserver-xfree86: [s3virge] server causes sound distortion on ViRGE/DX or /GX rev 1 Tags added: moreinfo End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
i845 patch for 4.2.1 debs
First off, I'd like to say thank you to Branden for your amazing
work. I've been working on your debs for the last few days, and they
build flawlessly.
I've been asked by my employer to backport the Intel i845 2d driver so
that we can support it in our next release, and so I did. For anyone
interested, the patch is attached. I didn't follow your naming scheme
exactly, so the patch is not 000 even though it's stolen_from_HEAD. I
did this because I didn't want to have to adjust all of your other
patches which were complaining about offsets, just to get the debs to
compile.
One problem I did encounter is that when I do a dpkg-buildpackage
-nc the object files still seem to get cleaned. Is there something
I'm misunderstanding?
For now, I've only done the most basic testing. RedHat backported the
same driver and includes it in limbo, which I believe is rh8, so it
must be somewhat stable. As I get more results from our testing dept,
I will forward them to you, if you're interested.
Thanks again,
michael
--
michael cardenas | lead software engineer, lindows.com
hyperpoem.net | GNU/Linux software developer
people.debian.org/~mbc | encrypted mail preferred
The secrets of this earth are not for all men to see, but only for those who will
seek them
- Ayn Rand, Anthem
Index: Imakefile
===
RCS file: /cvs/xc/programs/Xserver/hw/xfree86/drivers/i810/Imakefile,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- xc/programs/Xserver/hw/xfree86/drivers/i810/Imakefile 2001/10/04 18:28:21
1.18
+++ xc/programs/Xserver/hw/xfree86/drivers/i810/Imakefile 2002/05/10 12:50:05
+ 1.19
-1,4 +1,4
-XCOMM $XFree86: xc/programs/Xserver/hw/xfree86/drivers/i810/Imakefile,v 1.18
2001/10/04 18:28:21 alanh Exp $
+XCOMM $XFree86: xc/programs/Xserver/hw/xfree86/drivers/i810/Imakefile,v 1.19
+2002/05/10 12:50:05 alanh Exp $
XCOMM
XCOMM This is the Imakefile for the i810 driver.
XCOMM
-31,7 +31,7
-I$(SERVERSRC)/fb -I$(XF86SRC)/xaa -I$(XF86SRC)/ramdac \
-I$(XF86SRC)/vgahw -I$(XF86SRC)/ddc -I$(XF86SRC)/i2c \
-I$(XF86OSSRC)/vbe -I$(XF86SRC)/int10\
- -I$(SERVERSRC)/Xext -I$(XF86SRC)/xf24_32bpp \
+ -I$(SERVERSRC)/Xext \
-I$(FONTINCSRC) -I$(SERVERSRC)/include -I$(XINCLUDESRC) \
-I$(EXTINCSRC) -I$(SERVERSRC)/render \
$(DRIINCLUDES)
Index: i810.h
===
RCS file: /cvs/xc/programs/Xserver/hw/xfree86/drivers/i810/i810.h,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- xc/programs/Xserver/hw/xfree86/drivers/i810/i810.h 2002/01/25 21:56:03 1.30
+++ xc/programs/Xserver/hw/xfree86/drivers/i810/i810.h 2002/05/10 12:50:05 1.31
-824,6 +824,7
pI810-PciInfo-chipType == PCI_CHIP_I810_E)
#define IS_I815(pI810) (pI810-PciInfo-chipType == PCI_CHIP_I815)
#define IS_I830(pI810) (pI810-PciInfo-chipType == PCI_CHIP_I830_M)
+#define IS_845G(pI810) (pI810-PciInfo-chipType == PCI_CHIP_845_G)
#endif
Index: i810_cursor.c
===
RCS file: /cvs/xc/programs/Xserver/hw/xfree86/drivers/i810/i810_cursor.c,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- xc/programs/Xserver/hw/xfree86/drivers/i810/i810_cursor.c 2001/10/10 14:08:36
1.4
+++ xc/programs/Xserver/hw/xfree86/drivers/i810/i810_cursor.c 2002/05/10 12:50:05
+ 1.5
-25,7 +25,7
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
**/
-/* $XFree86: xc/programs/Xserver/hw/xfree86/drivers/i810/i810_cursor.c,v 1.4
2001/10/10 14:08:36 alanh Exp $ */
+/* $XFree86: xc/programs/Xserver/hw/xfree86/drivers/i810/i810_cursor.c,v 1.5
+2002/05/10 12:50:05 alanh Exp $ */
/*
* Authors:
-77,6 +77,13
infoPtr-ShowCursor = I810ShowCursor;
infoPtr-UseHWCursor = I810UseHWCursor;
+ if (IS_845G (pI810))
+{
+ OUTREG(0x700A0,0x00040040);
+ OUTREG(0x70084,pI810-CursorStart);
+}
+
+
if (!pI810-CursorPhysical)
return FALSE;
-158,7 +165,10
OUTREG8( CURSOR_Y_HI, (((y 8) 0x07) | flag));
/* FIXME */
- OUTREG(CURABASE, pI810-CursorPhysical);
+ if (IS_845G (pI810))
+OUTREG(CURABASE,pI810-CursorStart);
+ else
+OUTREG(CURABASE, pI810-CursorPhysical);
}
static void
-174,7 +184,17
temp |= CURSORA_MODE_64_AND_XOR;
OUTREG(CURACNTR, temp);
OUTREG(CURABASE, pI810-CursorPhysical);
- } else {
+ DPRINTF(PFX,Value of CursorPhysical is %x Value of CursorStart is %x
+,pI810-CursorPhysical,pI810-CursorStart);
+
+ } else if (IS_845G (pI810))
+{
+
Bug#156540: marked as done (impossible de démarrer X)
Your message dated Wed, 30 Oct 2002 16:20:13 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#156540: Impossible de demarrer X has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your 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; 13 Aug 2002 11:37:06 + From [EMAIL PROTECTED] Tue Aug 13 06:37:06 2002 Return-path: [EMAIL PROTECTED] Received: from relay-1v.club-internet.fr [194.158.96.112] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 17eZz0-0006WP-00; Tue, 13 Aug 2002 06:37:06 -0500 Received: from PORTABLE (vlp1a-228.n.club-internet.fr [212.195.0.228]) by relay-1v.club-internet.fr (Postfix) with SMTP id D942116AB for [EMAIL PROTECTED]; Tue, 13 Aug 2002 13:37:02 +0200 (CEST) Reply-To: [EMAIL PROTECTED] From: Pascal FRACAROS [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: =?iso-8859-1?Q?impossible_de_d=E9marrer_X?= Date: Tue, 13 Aug 2002 13:36:58 +0200 Message-ID: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600. Delivered-To: [EMAIL PROTECTED] Package: startx Version: Debian Education J'ai fait l'aquistion de la distribution Debian Education. Je posséde un PC avec écran 17 pouces et carte graphique NVIDIA Geforce2. L'installation se déroule correctement mais impossible de démarrer XWindows. Que puis-je faire pour le démarrer? --- Received: (at 156540-done) by bugs.debian.org; 30 Oct 2002 21:20:19 + From [EMAIL PROTECTED] Wed Oct 30 15:20:18 2002 Return-path: [EMAIL PROTECTED] Received: from pcp942041pcs.cstltn01.in.comcast.net (apocalypse.deadbeast.net) [68.57.244.226] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 1870G6-0003AT-00; Wed, 30 Oct 2002 15:20:14 -0600 Received: by apocalypse.deadbeast.net (Postfix, from userid 1000) id B62794372; Wed, 30 Oct 2002 16:20:13 -0500 (EST) Date: Wed, 30 Oct 2002 16:20:13 -0500 From: Branden Robinson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Bug#156540: Impossible de demarrer X Message-ID: [EMAIL PROTECTED] References: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol=application/pgp-signature; boundary=faJ0ivz08JzDjTH2 Content-Disposition: inline In-Reply-To: [EMAIL PROTECTED] User-Agent: Mutt/1.4i Delivered-To: [EMAIL PROTECTED] X-Spam-Status: No, hits=-15.2 required=5.0 tests=IN_REP_TO,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES, SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_MUTT version=2.41 X-Spam-Level: --faJ0ivz08JzDjTH2 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 30, 2002 at 05:24:07PM +0100, Juliusz Chroboczek wrote: I need this bug report translated into English before I can address it. =20 =AB I acquired the distribution Debian Education. I own a PC with a 17 =AB inch display and an NVIDIA Geforce2 graphic card. The installation =AB proceeds correctly but it is impossible to start XWindows. What can I =AB do to start it? =BB =20 This is an installation problem, not a bug as such. Closing this bug report per M. Chroboczek. --=20 G. Branden Robinson| The last Christian died on the Debian GNU/Linux | cross. [EMAIL PROTECTED] | -- Friedrich Nietzsche http://people.debian.org/~branden/ | --faJ0ivz08JzDjTH2 Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iEYEARECAAYFAj3ATQ0ACgkQ6kxmHytGonwTBgCeMlDFhczeAeXA2LI+XKv11W0m UXoAn25w7sGcksc455D2y7mdL+rIhnEq =GlYY -END PGP SIGNATURE- --faJ0ivz08JzDjTH2-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#167009: Followup
Michael et al, My kernel is compiled with: CONFIG_PMAC_APM_EMU=y Indeed, /dev/apm_bios does not exist. But MAKEDEV does not even know how to create it. My XFree86.log does show: (WW) Open APM failed (/dev/apm_bios) (No such file or directory) Notwithstanding any of this, I believe that it is still a bug. It worked fine before, why this sudden requirement now? -- John -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#166335: Bad default configuration for XftConfig
On Wed, Oct 30, 2002 at 10:12:53AM +0100, Jean-Christophe Dubacq wrote: Here you are. At least, this gives reasonable default. If not satisfying, I could try to include defaults using packages ttf-freefont and xfonts-scalable. No, this is fine. At least, I think it is; I haven't tried it yet. :) --- XftConfig 2002-10-26 12:32:36.0 +0200 +++ XftConfig.orig 2002-10-30 10:09:32.0 +0100 Just FYI, the convention for diffing is original file first. Don't worry, I'm not going to make you submit the diff before I do anything about this report, I just thought you might like to know, for future reference. -- G. Branden Robinson| The noble soul has reverence for Debian GNU/Linux | itself. [EMAIL PROTECTED] | -- Friedrich Nietzsche http://people.debian.org/~branden/ | msg04488/pgp0.pgp Description: PGP signature
Bug#164034: Resolution 1400x1050
On Wed, Oct 30, 2002 at 04:50:55PM +0100, Michael Piefel wrote: As an advanced option, one should be able to enter arbitrary sizes. I disagree. That is beyond the intended scope of the X server debconf support. Quoting dexconf(8): It is also important to note that dexconf, and the corresponding deb- conf questions whose answers it retrieves, are not intended to replace a full-featured X server configuration tool; that is the province of xf86cfg(1), currently under development by the XFree86 Project, Inc. In the meantime, however, users inexperienced with the syntax of the XF86Config (or XF86Config-4) file may use dexconf to generate the X server configuration file with a minimal amount of detailed knowledge of their hardware characteristics. The purpose of this config tool is to get a usable single-head configuration going for people who know nothing of the X Window System or XFree86. -- G. Branden Robinson| Debian GNU/Linux | kernel panic -- causal failure [EMAIL PROTECTED] | universe will now reboot http://people.debian.org/~branden/ | msg04489/pgp0.pgp Description: PGP signature
Re: Bug#167009: Additional details
On Mit, 2002-10-30 at 15:14, John Goerzen wrote: On Wed, Oct 30, 2002 at 11:05:32AM +0100, Michel D?nzer wrote: As discussed many times on the debian-powerpc list, make sure APM emulation is enabled in the kernel, that /dev/apm_bios exists and that the X server log contains contains a line I will check on these things and report back later today; however, I am still concerned that an X upgrade broke this. It worked fine before upgrading. The r128 driver does 2D acceleration with DRI enabled differently (like the radeon driver has always done) since 4.2.0. Did OpenGL programs work after sleep before? If you don't need 3D hardware acceleration on your main session, just run with DRI disabled and it might work as before. Seems to me that if it could handle it before, it should be able to handle it now? Don't you think, too, that it should not require this emulation to work properly? (II) Open APM successful Failing that, the X server can't react to the sleep cycle, and you need to switch to console for sleep. This is still the important point. That it used to work was basically luck. PS: cd /dev; MAKEDEV apm -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#165793: /usr/X11R6/man/man1/xlsfonts.1x.gz doesn't explain pattern good enough
J == Juliusz Chroboczek [EMAIL PROTECTED] writes: The xlsfonts man page doesn't explain pattern good enough. J $ man xlfonts J ... JXlsfonts lists the fonts that match the given pattern. The wildcard Jcharacter * may be used to match any sequence of characters (includ- Jing none), and ? to match any single character. If no pattern is Jgiven, * is assumed. J ... J In what way is that not clear? I see. hummm, BTW we would expect it to act like ls. Obviously it matches more: $ xlsfonts taip* -eten-fixed-medium-r-normal--16-150-75-75-c-160-big5.eten-0 -eten-fixed-medium-r-normal--24-230-75-75-c-240-big5.eten-0 taipei16 taipei24 OK, mention it will get aliases etc. -- http://jidanni.org/ Taiwan(04)25854780 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: i845 patch for 4.2.1 debs
On Wed, Oct 30, 2002 at 01:32:00PM -0800, Michael Cardenas wrote: First off, I'd like to say thank you to Branden for your amazing work. I've been working on your debs for the last few days, and they build flawlessly. Glad to hear it! I've been asked by my employer to backport the Intel i845 2d driver so that we can support it in our next release, and so I did. For anyone interested, the patch is attached. I didn't follow your naming scheme exactly, so the patch is not 000 even though it's stolen_from_HEAD. I did this because I didn't want to have to adjust all of your other patches which were complaining about offsets, just to get the debs to compile. No problem, I'll pick those nits. One problem I did encounter is that when I do a dpkg-buildpackage -nc the object files still seem to get cleaned. Is there something I'm misunderstanding? Hmm, I never use the -nc option, so I am not sure. I'm pretty sure my rules file isn't written wrongly in this respect. For now, I've only done the most basic testing. RedHat backported the same driver and includes it in limbo, which I believe is rh8, so it must be somewhat stable. As I get more results from our testing dept, I will forward them to you, if you're interested. Yes, please. I'll see if I can get this into 4.2.1-4. Thanks for your efforts. -- G. Branden Robinson|The best place to hide something is Debian GNU/Linux |in documentation. [EMAIL PROTECTED] |-- Ethan Benson http://people.debian.org/~branden/ | msg04492/pgp0.pgp Description: PGP signature
Bug#167009: acknowledged by developer (Re: Bug#167009: Additional details)
On Wed, Oct 30, 2002 at 09:47:57PM -0500, John Goerzen wrote: On Wed, Oct 30, 2002 at 08:18:05PM -0600, Debian Bug Tracking System wrote: Once cannot expect power management-related functionality to work when one's kernel doesn't support power management, or when the interfaces to the kernel's power management support are not set up. One can expect Debian packages to set up the prerequisites they need to operate properly. Power management support packages aren't prerequisites for systems that don't have power management. Perhaps the bug is not with X, but I submit that it is still a bug. Well, why don't you go ask debian-devel what package should handle this sort of thing? If these lockups are occuring becuase there is no /dev/apm_bios, couldn't X's postinst at least create it? Why shouldn't the makedev package? Interestingly, powermgmt-base presents a question about this. On x86 machines, apmd depends on this package, but nothing does on powerpc. Perhaps xserver-xfree86 should do so, to ensure that proper power management interfaces are available to userland? And what of people using other X server packages, or with no X server at all? Shall we just assume those folks don't need power management support? powermgmt-base also appears to take care of the situation properly for people using devfs. Moreover, its size is 128K installed and depends only on makedev, libc6, and debconf. It should not pose any problem for the X server. Sounds like you have a problem with Debian's PowerPC architecture support, and not a problem with XFree86 at all. -- G. Branden Robinson| Convictions are more dangerous Debian GNU/Linux | enemies of truth than lies. [EMAIL PROTECTED] | -- Friedrich Nietzsche http://www.deadbeast.net/~branden/ | msg04495/pgp0.pgp Description: PGP signature
Bug#160182: ISO 8859-13 support for TrueType is incorrect
Miros/law Baran: It is always good to check the generated .scale file; Actually I run it through a pipe that removes a few encodings from the list now (among other iso-8859-13 since it works). and you need to use mkfontdir with '-e' option, e.g. Hmmm. All the other encodings work perfectly even without this. But I'll have to have a look and see if it makes any difference. -- \\// Peter - I do not read or respond to mail with HTML attachments. Statement concerning unsolicited e-mail according to Swedish law: http://www.softwolves.pp.se/peter/reklampost.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 160841
Processing commands for [EMAIL PROTECTED]: tag 160841 + upstream Bug#160841: xserver-xfree86: [tdfx] exhausts virtual memory and arouses Linux OOM killer when changing video modes on Voodoo5 rev 1 Tags added: upstream End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#164063: out-of-date pt_BR translation for xserver-xfree86
Processing commands for [EMAIL PROTECTED]: tag 164063 - patch Bug#164063: xserver-xfree86: updated Debconf template translations for pt_BR Tags removed: patch On Thu, Oct 10, 2002 at 12:23:06AM -0500, Steve Langasek wrote: Unknown command or malformed arguments to command. Please find attached an updated Portuguese translation for the Unknown command or malformed arguments to command. xserver-xfree86 debconf templates. With this update, only two templates Unknown command or malformed arguments to command. remain untranslated to Portuguese; I'm leaving those for a better Unknown command or malformed arguments to command. translator than I to pick up at a later date. 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) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#166335: Bad default configuration for XftConfig
On Sun, Oct 27, 2002 at 07:19:35PM -0500, [EMAIL PROTECTED] wrote: Could you come up with, and test, a patch to the stock Debian /etc/X11/XftConfig file that would work well with xfonts-scalable? Please generate a diff -u of the original and patched file, and mail that diff to this bug report. Here you are. At least, this gives reasonable default. If not satisfying, I could try to include defaults using packages ttf-freefont and xfonts-scalable. --- XftConfig 2002-10-26 12:32:36.0 +0200 +++ XftConfig.orig 2002-10-30 10:09:32.0 +0100 @@ -19,12 +19,3 @@ # match any family == charter edit family += bitstream charter; match any family == bitstream charter edit family =+ charter; - -match any spacing == 110 edit family =+ Courier 10 Pitch ; -match any spacing == 100 edit family =+ Courier 10 Pitch ; -match any spacing == 0 edit family =+ Bitstream Charter ; -match any size 1 edit - family =+ Helvetica ; - family =+ Arial ; - family =+ Bitstream Charter ; -
Bug#167009: Additional details
On Mit, 2002-10-30 at 05:01, John Goerzen wrote: I tried downgrading to 4.2.1-1 (from 4.2.1-3) to see if that would improve matters. It apparently did not, although after one sleep my mouse alone remained responsive. However, I discovered that the machine was still listening on its airport interface and was able to log in and do some more debugging. It turns out that when X throws one of these fits, it's spinlocking. Running strace on it yields this sort of result, repeated over and over: ioctl(6, 0x20006444, 0) = -1 EBUSY (Device or resource busy) ioctl(6, 0x20006444, 0) = -1 EBUSY (Device or resource busy) --- SIGALRM (Alarm clock) --- ioctl(6, 0x20006444, 0) = -1 EBUSY (Device or resource busy) ioctl(6, 0x20006444, 0) = -1 EBUSY (Device or resource busy) --- SIGALRM (Alarm clock) --- ioctl(6, 0x20006444, 0) = -1 EBUSY (Device or resource busy) ioctl(6, 0x20006444, 0) = -1 EBUSY (Device or resource busy) ioctl(6, 0x20006444, 0) = -1 EBUSY (Device or resource busy) Now, looking at the X server process, I see that fd 6 is attached to /dev/dri/card0. Maybe a clue. As discussed many times on the debian-powerpc list, make sure APM emulation is enabled in the kernel, that /dev/apm_bios exists and that the X server log contains contains a line (II) Open APM successful Failing that, the X server can't react to the sleep cycle, and you need to switch to console for sleep. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast
Bug#167009: Additional details
On Wed, Oct 30, 2002 at 11:05:32AM +0100, Michel D?nzer wrote: As discussed many times on the debian-powerpc list, make sure APM emulation is enabled in the kernel, that /dev/apm_bios exists and that the X server log contains contains a line I will check on these things and report back later today; however, I am still concerned that an X upgrade broke this. It worked fine before upgrading. Seems to me that if it could handle it before, it should be able to handle it now? Don't you think, too, that it should not require this emulation to work properly? (II) Open APM successful Failing that, the X server can't react to the sleep cycle, and you need to switch to console for sleep.
Re: Configuration file handling (Re: [desktop] Unix configuration nightmare)
On Mon, Oct 28, 2002 at 11:54:54PM -0500, Branden Robinson wrote: On Wed, Oct 23, 2002 at 08:10:43PM -0400, Matt Zimmerman wrote: I don't think that existing .config handling necessarily needs to change at this point, unless we want to provide a standard way to suppress all attempts at automatic configuration for a particular config file. Well, Joey Hess is of the opinion that manage this config file with debconf-style questions are Evil and Wrong. So, assuming I want to get with the Debconf orthodoxy, I would be changing my config scripts to eliminate this sort of prompting. I can't speak for joeyh, but I think his beef is that maintainers use this kind of question to be lazy about preserving changes. I'm guilty of this myself, because I do not want to parse some arbitrary config format using shell commands to seed debconf with the appropriate responses. We're all about preserving changes here, so the light of the One True Way should guide us to salvation. I was thinking of things more similar to --force-confnew/--force-confold than to manage this config file with debconf questions. In other maintainer scripts, we need to be able to say I have generated a configuration file /tmp/blah as a possible replacement for /etc/foo/bar. At that point, the maintainer script is done with the file, and passes control to us. Here we run into a problem: * For most packages, the other maintainer script is going to be the postinst. In fact it's difficult for me to imagine a scenario when anything but the postinst would be generating a config file.[1] From my perspective, the tool doesn't care from which maintainer script it's called. postinst would seem to be the only useful place to call it, I agree. * The postinst, by definition, runs during the configuration phase. Your proposal is going to pull us farther away from the utopia of being able to handle all interactivity before packages are even unpacked, a la dpkg-preconfigure. While dpkg's conffile prompts already violate this, they *can* be replaced with pre-unpack prompting, because dpkg-preconfigure can suck new conffiles out of a package just as well as it can config and templates files. Non-conffile config files cannot enjoy this luxury, because they don't exist within the package. Right. As we discussed on IRC, there seems to be a fundamental conflict between preconfiguration and generated configuration files because the package is by definition not configured yet (for the new version) at preconfiguration time. Packages with simple requirements could theoretically generate a configuration in .config, but that is not the right place for it, and packages with simple requirements can use conffiles. I had not considered that one day dpkg could prompt about conffiles ahead of time. That weakens my no worse than conffiles argument considerably. Preconfiguration should remain unchanged in (IMO) the two most important cases: initial installation, and novice user. In the former case, we will never need to prompt in postinst, and in the latter, we should have a reasonable default for them. * On the other hand, if we're doing an upgrade instead of an install, the tool(s) we use to generate the config file may already be on the system at pre-configure time. However, if those tools change, and a package's .config script needs to be able to use the config-generation tool that's in the corresponding version of the package, you'd need to have a way of declaring this requirement so that config file generation could be deferred to package configuration. Not to mention the fact that the runtime dependencies of the tools used to generate the configuration files would need to be present at pre-configure time. Oy vey. Yes, this would be a mess. Upgrades from one Debian release to the next would be fragile and difficult to maintain and test effectively. We check again whether the file has been modified since last time by comparing it to a saved copy or checksum (the copy is optional, but gives much more flexibility than storing only a checksum). Why not just a checksum? Do you have a specific application in mind, or do you think the copy is a good idea for the sake of people cleverer than we? :) The copy makes it possible to calculate the merge. Since I am pretty confident that we will want merges, I think we should go ahead and use the copy for the comparison as well. It might be marginally more efficient to cache checksums for the comparison, but I doubt it will be worth worrying about. [prompts for various cases] In the common cases, this should be possible with a single prompt, though it could be split into two phases or selected from either a simple or advanced method, or even suppressed entirely for novice users if a sane default action sequence could be decided (always preserve? merge, and if that fails, preserve? warn?). As you
Bug#160182: ISO 8859-13 support for TrueType is incorrect
Does the directory with the fonts contain a proper encodings.dir file? In other words, have you run mkfontdir with the proper -e option? I am fairly positive that ISO 8859-13 does work correctly. However, it is not a built-in encoding, and the server relies on an encodings.dir file to locate its definition. (In 4.3.0, the server will automagically find the encoding file if it is at a standard location. The encodings.dir mechanism is still supported, though.) Juliusz
Bug#164034: Resolution 1400x1050
...and neither does it support my IBM ThinkPad with a 1400x1050 resolution. Or my 16:9 monitor with 1920x1200 pixels. As an advanced option, one should be able to enter arbitrary sizes. -- |=| Michael Piefel |=| Humboldt-Universität zu Berlin |=| Tel. (+49 30) 2093 3831
Bug#156540: Impossible de demarrer X
J'ai fait l'aquistion de la distribution Debian Education. Je posséde un PC avec écran 17 pouces et carte graphique NVIDIA Geforce2. L'installation se déroule correctement mais impossible de démarrer XWindows. Que puis-je faire pour le démarrer? I need this bug report translated into English before I can address it. « I acquired the distribution Debian Education. I own a PC with a 17 « inch display and an NVIDIA Geforce2 graphic card. The installation « proceeds correctly but it is impossible to start XWindows. What can I « do to start it? » This is an installation problem, not a bug as such. Le plus probable est que vous n'avez pas installé X ; vérifiez la documentation de votre distribution pour vérifier. Si vous avez installé X et il est mal configuré, il créera un log (journal) dans le fichier /var/log/XFree86.0. Je vous suggère d'en envoyer le contenu sur la liste debian-users. Voyez sur www.debian.org pour la liste des listes de discussion. Attention : les listes Debian sont de langue anglaise. Si vous envoyez un message en français, vous risquez de vous faire mal voir. Salutations, Juliusz Chroboczek
Bug#156598: GLX extension missing
Sorry to ask the obvious: you do ``Load glx'' in your XF86Config-4? Juliusz
Bug#149631: [ati/atimisc] DoS attack possible when viewing absurdly huge fonts on Mach64 GT rev 65
This issue should hopefully be fixed upstream in 4.3.0. There will be no fix for 4.2. Juliusz
Bug#162880: [s3virge] server causes sound distortion on ViRGE/DX or /GX rev 1
Does playing with the pci_burst and pci_retry options change anything? (See the s3virge manual page.) Juliusz
Bug#156115: X server generates bogus font names for scalable fonts
No reply... Could I please ask you to tell me whether you can reproduce the problem without Tk, i.e. what happens if you do xfd -fn '-adobe-helvetica-medium-r-normal--12-*-75-75-p-*-iso8859-1' If the problem is not reproducible with xfd, it's a Tk bug, not an X bug. If it is reproducible with xfd, I will need the output of xlsfonts -ll -fn '-adobe-helvetica-medium-r-normal--12-*-75-75-p-*-iso8859-1' Regards, Juliusz
Bug#151780: xfs: would like documentation on font install in doc/xfs
Font installation is documented in the README.fonts file (under xfree86-common). This file does not metion xfs as I (the author of the document) believe that xfs is a Bad Idea and do not wish to promote its use. However, font installation using xfs is documented in the xfs(1) manual page. With specifics of TrueType being described in README.fonts, all the information is indeed being provided. Juliusz P.S. Branden, the README.fonts file will undergo a partial rewrite for 4.3.0. I'm open to suggestions.
Bug#165793: /usr/X11R6/man/man1/xlsfonts.1x.gz doesn't explain pattern good enough
The xlsfonts man page doesn't explain pattern good enough. $ man xlfonts ... Xlsfonts lists the fonts that match the given pattern. The wildcard character * may be used to match any sequence of characters (includ- ing none), and ? to match any single character. If no pattern is given, * is assumed. ... In what way is that not clear? Also the --help info should mention -fn in the latter part. Also it should say -l will tie up your machine, like it does on the man page. The included help is only a quick summary in case you know the command but forget an option. It should not contain explanations, which is what the man page is for. Juliusz
Bug#148655: dex-mode selection doesn't provide 1400x1050 resolution
Note by the way that two default modelines for 1400x1050 have been included in XFree86 4.2.0 (after Debian 3.0). The list of default X server modelines is in hw/xfree86/common/xf86DefModes.c, and configuration tools could probably link against this file. Juliusz
Bug#139826: please add en_GB@euro support
Please note that the en_GB.ISO8859-15 locale *is* supported by the X server (at least in current CVS). It uses the ISO 8859-15 character encoding, which makes the Euro sign available. However, it differs from an [EMAIL PROTECTED]'' variant because it uses the Pound, not the Euro, as the currency symbol. I believe that en_GB.ISO8859-15, not [EMAIL PROTECTED], is what you want. The creation of an [EMAIL PROTECTED] locale before the UK commits to joining the Euro zone would be a political statement. Juliusz
Bug#162880: [s3virge] server causes sound distortion on ViRGE/DX or /GX rev 1
Does playing with the pci_burst and pci_retry options change anything? (See the s3virge manual page.) DE I wish it did. I spent a couple of days with the s3virge manpage trying DE every possible combinition of variables I could think of, with no luck. I suspect you may have a hardware issue, then. I suggest you raise the issue on [EMAIL PROTECTED] Please do not omit to mention your X server version (4.1.0 as hacked by Debian, probably) and that you did try the pci_* options. Good luck, Juliusz P.S. Branden, that looks like an upstream issue to me.
Bug#162880: [s3virge] server causes sound distortion on ViRGE/DX or /GX rev 1
Does playing with the pci_burst and pci_retry options change anything? (See the s3virge manual page.) I wish it did. I spent a couple of days with the s3virge manpage trying every possible combinition of variables I could think of, with no luck.
Bug#162880: [s3virge] server causes sound distortion on ViRGE/DX or /GX rev 1
I suspect you may have a hardware issue, then. Not sure what hardware issue means. I do have a cheap card, but I don't experience problems with the old (version 3) xserver. Anyway, I appreciate your help and the Debian project.
Bug#160182: ISO 8859-13 support for TrueType is incorrect
Does the directory with the fonts contain a proper encodings.dir file? In other words, have you run mkfontdir with the proper -e option? No, I do not have any encodings.dir files. What I run is: ttmkfdir fonts.scale mkfontdir All other encodings work fine except for ISO 8859-13. Please note that these are all TrueType fonts. -- \\// Peter - http://www.softwolves.pp.se/ I do not read or respond to mail with HTML attachments. Statement concerning unsolicited e-mail according to Swedish law: http://www.softwolves.pp.se/peter/reklampost.html
Bug#156115: X server generates bogus font names for scalable fonts
No reply... Could I please ask you to tell me whether you can reproduce the problem without Tk, i.e. what happens if you do xfd -fn '-adobe-helvetica-medium-r-normal--12-*-75-75-p-*-iso8859-1' If the problem is not reproducible with xfd, it's a Tk bug, not an X bug. If it is reproducible with xfd, I will need the output of xlsfonts -ll -fn '-adobe-helvetica-medium-r-normal--12-*-75-75-p-*-iso8859-1' Regards, Juliusz The problem can't be reproduced with your commands but the following shows a problem similar to the one with Tk: xfd -fn `xlsfonts -fn -*-helvetica-medium-r-normal-*-12-*-*-*-*-*-iso8859-1 | head -1` The problem is that xserver generates fontnames with fixed size for Type1 scalable fonts and some (or all?) of these fonts look considerable worse than the corresponding fixed size fonts: $ xlsfonts -fn -*-helvetica-medium-r-normal-*-12-*-*-*-*-*-iso8859-1 -adobe-helvetica-medium-r-normal--12-116-75-75-p-0-iso8859-1 -adobe-helvetica-medium-r-normal--12-116-75-75-p-0-iso8859-1 -adobe-helvetica-medium-r-normal--12-120-75-75-p-67-iso8859-1 -adobe-helvetica-medium-r-normal--12-120-75-75-p-67-iso8859-1 $ xlsfonts -fn -*-helvetica-medium-r-normal-*-*-120-*-*-*-*-iso8859-1 -adobe-helvetica-medium-r-normal--12-120-75-75-p-0-iso8859-1 -adobe-helvetica-medium-r-normal--12-120-75-75-p-0-iso8859-1 -adobe-helvetica-medium-r-normal--12-120-75-75-p-67-iso8859-1 -adobe-helvetica-medium-r-normal--12-120-75-75-p-67-iso8859-1 -adobe-helvetica-medium-r-normal--17-120-100-100-p-88-iso8859-1 -adobe-helvetica-medium-r-normal--17-120-100-100-p-88-iso8859-1 Note that this happens only with certain sizes, for example a search for Helvetica 16 returns only fixed fonts: $ xlsfonts -fn -*-helvetica-medium-r-normal-*-16-*-*-*-*-*-iso8859-1 -adobe-helvetica-medium-r-normal--16-154-75-75-p-0-iso8859-1 -adobe-helvetica-medium-r-normal--16-154-75-75-p-0-iso8859-1 $ xlsfonts -fn -*-helvetica-medium-r-normal-*-*-160-*-*-*-*-iso8859-1 -adobe-helvetica-medium-r-normal--17-160-75-75-p-0-iso8859-1 -adobe-helvetica-medium-r-normal--17-160-75-75-p-0-iso8859-1 Can you explain why a search for Helvetica 12 returns a variable fixed font while Helvetica 16 returns only fixed fonts? The output of xlsfonts -ll with the two fonts gives the following result: $ xlsfonts -ll -fn '-adobe-helvetica-medium-r-normal--12-116-75-75-p-0-iso8859-1' name: -adobe-helvetica-medium-r-normal--12-116-75-75-p-0-iso8859-1 direction:left to right indexing: linear rows: 0x00 thru 0x00 (0 thru 0) columns: 0x00 thru 0xff (0 thru 255) all chars exist: no default char: 0x (0) ascent: 11 descent: 3 font type:Proportional (min and max widths not equal) bounds: width left right asc desc attr keysym min2 0 0-1-7 0x00bf max 12 21112 3 0x03f7 properties: 24 FOUNDRY urw FAMILY_NAME nimbus sans l WEIGHT_NAME regular SLANT r SETWIDTH_NAME normal ADD_STYLE_NAME PIXEL_SIZE12 POINT_SIZE116 RESOLUTION_X 75 RESOLUTION_Y 75 SPACING p AVERAGE_WIDTH 65 CHARSET_REGISTRY iso8859 CHARSET_ENCODING 1 FONT -urw-nimbus sans l-regular-r-normal--12-116-75-75-p-65-iso8859-1 COPYRIGHT (URW)++,Copyright 1999 by (URW)++ Design Development. See the file COPYING (GNU General se) for license conditions. As a special exception, permission is granted to include this font program in a Postscrip that consists of a document that contains text to be displayed or printed using this font, regardless of the conditi e applying to the document itself. RAW_PIXEL_SIZE1000 RAW_POINT_SIZE964 RAW_ASCENT953 RAW_DESCENT 285 RAW_AVERAGE_WIDTH 5435 FACE_NAME NimbusSanL-Regue FONT_TYPE Type 1 RASTERIZER_NAME X Consortium Type 1 Rasterizer $ xlsfonts -ll -fn '-adobe-helvetica-medium-r-normal--12-120-75-75-p-67-iso8859-1' name: -adobe-helvetica-medium-r-normal--12-120-75-75-p-67-iso8859-1 direction:left to right indexing: linear rows: 0x00 thru 0x00 (0 thru 0) columns: 0x00 thru 0xff (0 thru 255) all chars exist: no default char: 0x (0) ascent: 11 descent: 3 font type:Proportional (min and max widths not equal) bounds: width left right asc desc attr keysym min2 0 1-1-8 0x
Bug#160182: ISO 8859-13 support for TrueType is incorrect
30.10.2002 pisze Peter Karlsson ([EMAIL PROTECTED]): Does the directory with the fonts contain a proper encodings.dir file? In other words, have you run mkfontdir with the proper -e option? No, I do not have any encodings.dir files. What I run is: ttmkfdir fonts.scale mkfontdir It is always good to check the generated .scale file; and you need to use mkfontdir with '-e' option, e.g. mkfontdir -e /usr/X11R6/lib/X11/fonts/encodings man mkfontdir should say more. Best regards, Jubal -- [ Miros/law L Baran, baran-at-knm-org-pl, neg IQ, cert AI ] [ 0101010 is ] [ BOF2510053411, makabra.knm.org.pl/~baran/, alchemy pany ] [ The Answer ] Deliberation: The act of examining one's bread to determine which side it is buttered on.
Processed: tagging 162880
Processing commands for [EMAIL PROTECTED]: tag 162880 + moreinfo Bug#162880: xserver-xfree86: [s3virge] server causes sound distortion on ViRGE/DX or /GX rev 1 Tags added: moreinfo End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
i845 patch for 4.2.1 debs
First off, I'd like to say thank you to Branden for your amazing
work. I've been working on your debs for the last few days, and they
build flawlessly.
I've been asked by my employer to backport the Intel i845 2d driver so
that we can support it in our next release, and so I did. For anyone
interested, the patch is attached. I didn't follow your naming scheme
exactly, so the patch is not 000 even though it's stolen_from_HEAD. I
did this because I didn't want to have to adjust all of your other
patches which were complaining about offsets, just to get the debs to
compile.
One problem I did encounter is that when I do a dpkg-buildpackage
-nc the object files still seem to get cleaned. Is there something
I'm misunderstanding?
For now, I've only done the most basic testing. RedHat backported the
same driver and includes it in limbo, which I believe is rh8, so it
must be somewhat stable. As I get more results from our testing dept,
I will forward them to you, if you're interested.
Thanks again,
michael
--
michael cardenas | lead software engineer, lindows.com
hyperpoem.net | GNU/Linux software developer
people.debian.org/~mbc | encrypted mail preferred
The secrets of this earth are not for all men to see, but only for those who
will seek them
- Ayn Rand, AnthemIndex: Imakefile
===
RCS file: /cvs/xc/programs/Xserver/hw/xfree86/drivers/i810/Imakefile,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- xc/programs/Xserver/hw/xfree86/drivers/i810/Imakefile 2001/10/04
18:28:21 1.18
+++ xc/programs/Xserver/hw/xfree86/drivers/i810/Imakefile 2002/05/10
12:50:05 1.19
@@ -1,4 +1,4 @@
-XCOMM $XFree86: xc/programs/Xserver/hw/xfree86/drivers/i810/Imakefile,v 1.18
2001/10/04 18:28:21 alanh Exp $
+XCOMM $XFree86: xc/programs/Xserver/hw/xfree86/drivers/i810/Imakefile,v 1.19
2002/05/10 12:50:05 alanh Exp $
XCOMM
XCOMM This is the Imakefile for the i810 driver.
XCOMM
@@ -31,7 +31,7 @@
-I$(SERVERSRC)/fb -I$(XF86SRC)/xaa -I$(XF86SRC)/ramdac \
-I$(XF86SRC)/vgahw -I$(XF86SRC)/ddc -I$(XF86SRC)/i2c \
-I$(XF86OSSRC)/vbe -I$(XF86SRC)/int10\
- -I$(SERVERSRC)/Xext -I$(XF86SRC)/xf24_32bpp \
+ -I$(SERVERSRC)/Xext \
-I$(FONTINCSRC) -I$(SERVERSRC)/include -I$(XINCLUDESRC) \
-I$(EXTINCSRC) -I$(SERVERSRC)/render \
$(DRIINCLUDES)
Index: i810.h
===
RCS file: /cvs/xc/programs/Xserver/hw/xfree86/drivers/i810/i810.h,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- xc/programs/Xserver/hw/xfree86/drivers/i810/i810.h 2002/01/25 21:56:03
1.30
+++ xc/programs/Xserver/hw/xfree86/drivers/i810/i810.h 2002/05/10 12:50:05
1.31
@@ -824,6 +824,7 @@
pI810-PciInfo-chipType == PCI_CHIP_I810_E)
#define IS_I815(pI810) (pI810-PciInfo-chipType == PCI_CHIP_I815)
#define IS_I830(pI810) (pI810-PciInfo-chipType == PCI_CHIP_I830_M)
+#define IS_845G(pI810) (pI810-PciInfo-chipType == PCI_CHIP_845_G)
#endif
Index: i810_cursor.c
===
RCS file: /cvs/xc/programs/Xserver/hw/xfree86/drivers/i810/i810_cursor.c,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- xc/programs/Xserver/hw/xfree86/drivers/i810/i810_cursor.c 2001/10/10
14:08:36 1.4
+++ xc/programs/Xserver/hw/xfree86/drivers/i810/i810_cursor.c 2002/05/10
12:50:05 1.5
@@ -25,7 +25,7 @@
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
**/
-/* $XFree86: xc/programs/Xserver/hw/xfree86/drivers/i810/i810_cursor.c,v 1.4
2001/10/10 14:08:36 alanh Exp $ */
+/* $XFree86: xc/programs/Xserver/hw/xfree86/drivers/i810/i810_cursor.c,v 1.5
2002/05/10 12:50:05 alanh Exp $ */
/*
* Authors:
@@ -77,6 +77,13 @@
infoPtr-ShowCursor = I810ShowCursor;
infoPtr-UseHWCursor = I810UseHWCursor;
+ if (IS_845G (pI810))
+{
+ OUTREG(0x700A0,0x00040040);
+ OUTREG(0x70084,pI810-CursorStart);
+}
+
+
if (!pI810-CursorPhysical)
return FALSE;
@@ -158,7 +165,10 @@
OUTREG8( CURSOR_Y_HI, (((y 8) 0x07) | flag));
/* FIXME */
- OUTREG(CURABASE, pI810-CursorPhysical);
+ if (IS_845G (pI810))
+OUTREG(CURABASE,pI810-CursorStart);
+ else
+OUTREG(CURABASE, pI810-CursorPhysical);
}
static void
@@ -174,7 +184,17 @@
temp |= CURSORA_MODE_64_AND_XOR;
OUTREG(CURACNTR, temp);
OUTREG(CURABASE, pI810-CursorPhysical);
- } else {
+ DPRINTF(PFX,Value of CursorPhysical is %x Value of CursorStart is
%x ,pI810-CursorPhysical,pI810-CursorStart);
+
+ } else if (IS_845G (pI810))
Bug#139826: please add en_GB@euro support
On Wed, Oct 30, 2002 at 05:54:32PM +0100, Juliusz Chroboczek wrote: I believe that en_GB.ISO8859-15, not [EMAIL PROTECTED], is what you want. The creation of an [EMAIL PROTECTED] locale before the UK commits to joining the Euro zone would be a political statement. Well, I don't necessarily think that's the case, since my understanding is that the @euro modifier refers to the characteristics of the locale setting as opposed to the details of economic zones. However, given that you're a citizen of the EU and I'm not -- and particularly given American media empires work very hard to ensure that U.S. citizens know nothing of the world outside our country except when it's time to grandstand with our military forces -- I'll defer to your judgement on this issue. At least until someone comes up with a better argument. :) -- G. Branden Robinson| The only way to get rid of a Debian GNU/Linux | temptation is to yield to it. [EMAIL PROTECTED] | -- Oscar Wilde http://people.debian.org/~branden/ | pgp9qU2RaVuTf.pgp Description: PGP signature
Bug#156540: marked as done (impossible de démarrer X)
Your message dated Wed, 30 Oct 2002 16:20:13 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#156540: Impossible de demarrer X has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your 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; 13 Aug 2002 11:37:06 + From [EMAIL PROTECTED] Tue Aug 13 06:37:06 2002 Return-path: [EMAIL PROTECTED] Received: from relay-1v.club-internet.fr [194.158.96.112] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 17eZz0-0006WP-00; Tue, 13 Aug 2002 06:37:06 -0500 Received: from PORTABLE (vlp1a-228.n.club-internet.fr [212.195.0.228]) by relay-1v.club-internet.fr (Postfix) with SMTP id D942116AB for [EMAIL PROTECTED]; Tue, 13 Aug 2002 13:37:02 +0200 (CEST) Reply-To: [EMAIL PROTECTED] From: Pascal FRACAROS [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: =?iso-8859-1?Q?impossible_de_d=E9marrer_X?= Date: Tue, 13 Aug 2002 13:36:58 +0200 Message-ID: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600. Delivered-To: [EMAIL PROTECTED] Package: startx Version: Debian Education J'ai fait l'aquistion de la distribution Debian Education. Je posséde un PC avec écran 17 pouces et carte graphique NVIDIA Geforce2. L'installation se déroule correctement mais impossible de démarrer XWindows. Que puis-je faire pour le démarrer? --- Received: (at 156540-done) by bugs.debian.org; 30 Oct 2002 21:20:19 + From [EMAIL PROTECTED] Wed Oct 30 15:20:18 2002 Return-path: [EMAIL PROTECTED] Received: from pcp942041pcs.cstltn01.in.comcast.net (apocalypse.deadbeast.net) [68.57.244.226] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 1870G6-0003AT-00; Wed, 30 Oct 2002 15:20:14 -0600 Received: by apocalypse.deadbeast.net (Postfix, from userid 1000) id B62794372; Wed, 30 Oct 2002 16:20:13 -0500 (EST) Date: Wed, 30 Oct 2002 16:20:13 -0500 From: Branden Robinson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Bug#156540: Impossible de demarrer X Message-ID: [EMAIL PROTECTED] References: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol=application/pgp-signature; boundary=faJ0ivz08JzDjTH2 Content-Disposition: inline In-Reply-To: [EMAIL PROTECTED] User-Agent: Mutt/1.4i Delivered-To: [EMAIL PROTECTED] X-Spam-Status: No, hits=-15.2 required=5.0 tests=IN_REP_TO,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES, SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_MUTT version=2.41 X-Spam-Level: --faJ0ivz08JzDjTH2 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 30, 2002 at 05:24:07PM +0100, Juliusz Chroboczek wrote: I need this bug report translated into English before I can address it. =20 =AB I acquired the distribution Debian Education. I own a PC with a 17 =AB inch display and an NVIDIA Geforce2 graphic card. The installation =AB proceeds correctly but it is impossible to start XWindows. What can I =AB do to start it? =BB =20 This is an installation problem, not a bug as such. Closing this bug report per M. Chroboczek. --=20 G. Branden Robinson| The last Christian died on the Debian GNU/Linux | cross. [EMAIL PROTECTED] | -- Friedrich Nietzsche http://people.debian.org/~branden/ | --faJ0ivz08JzDjTH2 Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iEYEARECAAYFAj3ATQ0ACgkQ6kxmHytGonwTBgCeMlDFhczeAeXA2LI+XKv11W0m UXoAn25w7sGcksc455D2y7mdL+rIhnEq =GlYY -END PGP SIGNATURE- --faJ0ivz08JzDjTH2--
Re: Bug#139826: please add en_GB@euro support
On Wed, Oct 30, 2002 at 04:23:51PM -0500, Branden Robinson wrote: On Wed, Oct 30, 2002 at 05:54:32PM +0100, Juliusz Chroboczek wrote: I believe that en_GB.ISO8859-15, not [EMAIL PROTECTED], is what you want. The creation of an [EMAIL PROTECTED] locale before the UK commits to joining the Euro zone would be a political statement. Well, I don't necessarily think that's the case, since my understanding is that the @euro modifier refers to the characteristics of the locale setting as opposed to the details of economic zones. However, given that you're a citizen of the EU and I'm not -- and particularly given American media empires work very hard to ensure that U.S. citizens know nothing of the world outside our country except when it's time to grandstand with our military forces -- I'll defer to your judgement on this issue. At least until someone comes up with a better argument. :) Stupid question from a EU citizen that happens to be in the US for a while. Which locale setting do I have to use to be able to type and display the Euro character on my US keyboard (ie no Euro key) and monitor? The only english locale including the Euro character I found was the irish one, but for some reason, which I forgot right now, I wasn't completely happy with it. Shouldn't all citizens, and non citizens, be able to type all currency symbols of the world, and not only $ and maybe the pound sign? I still have a euro sticker on my 12 year old keyboard, so I know where the key should be mapped to. But probably people in the US didn't get these stickers in the mail... Christian who hopes that he didn't screw up by replacing Branden with debian-x in the To: line, some time ago mutt used to handle follow ups correctly...
Bug#167009: Followup
Michael et al, My kernel is compiled with: CONFIG_PMAC_APM_EMU=y Indeed, /dev/apm_bios does not exist. But MAKEDEV does not even know how to create it. My XFree86.log does show: (WW) Open APM failed (/dev/apm_bios) (No such file or directory) Notwithstanding any of this, I believe that it is still a bug. It worked fine before, why this sudden requirement now? -- John
Bug#166335: Bad default configuration for XftConfig
On Wed, Oct 30, 2002 at 10:12:53AM +0100, Jean-Christophe Dubacq wrote: Here you are. At least, this gives reasonable default. If not satisfying, I could try to include defaults using packages ttf-freefont and xfonts-scalable. No, this is fine. At least, I think it is; I haven't tried it yet. :) --- XftConfig 2002-10-26 12:32:36.0 +0200 +++ XftConfig.orig 2002-10-30 10:09:32.0 +0100 Just FYI, the convention for diffing is original file first. Don't worry, I'm not going to make you submit the diff before I do anything about this report, I just thought you might like to know, for future reference. -- G. Branden Robinson| The noble soul has reverence for Debian GNU/Linux | itself. [EMAIL PROTECTED] | -- Friedrich Nietzsche http://people.debian.org/~branden/ | pgp9L7WahjrkD.pgp Description: PGP signature
Bug#164034: Resolution 1400x1050
On Wed, Oct 30, 2002 at 04:50:55PM +0100, Michael Piefel wrote: As an advanced option, one should be able to enter arbitrary sizes. I disagree. That is beyond the intended scope of the X server debconf support. Quoting dexconf(8): It is also important to note that dexconf, and the corresponding deb- conf questions whose answers it retrieves, are not intended to replace a full-featured X server configuration tool; that is the province of xf86cfg(1), currently under development by the XFree86 Project, Inc. In the meantime, however, users inexperienced with the syntax of the XF86Config (or XF86Config-4) file may use dexconf to generate the X server configuration file with a minimal amount of detailed knowledge of their hardware characteristics. The purpose of this config tool is to get a usable single-head configuration going for people who know nothing of the X Window System or XFree86. -- G. Branden Robinson| Debian GNU/Linux | kernel panic -- causal failure [EMAIL PROTECTED] | universe will now reboot http://people.debian.org/~branden/ | pgpHB94SCzjZn.pgp Description: PGP signature
Re: Bug#167009: Additional details
On Mit, 2002-10-30 at 15:14, John Goerzen wrote: On Wed, Oct 30, 2002 at 11:05:32AM +0100, Michel D?nzer wrote: As discussed many times on the debian-powerpc list, make sure APM emulation is enabled in the kernel, that /dev/apm_bios exists and that the X server log contains contains a line I will check on these things and report back later today; however, I am still concerned that an X upgrade broke this. It worked fine before upgrading. The r128 driver does 2D acceleration with DRI enabled differently (like the radeon driver has always done) since 4.2.0. Did OpenGL programs work after sleep before? If you don't need 3D hardware acceleration on your main session, just run with DRI disabled and it might work as before. Seems to me that if it could handle it before, it should be able to handle it now? Don't you think, too, that it should not require this emulation to work properly? (II) Open APM successful Failing that, the X server can't react to the sleep cycle, and you need to switch to console for sleep. This is still the important point. That it used to work was basically luck. PS: cd /dev; MAKEDEV apm -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast
Bug#165793: /usr/X11R6/man/man1/xlsfonts.1x.gz doesn't explain pattern good enough
J == Juliusz Chroboczek [EMAIL PROTECTED] writes: The xlsfonts man page doesn't explain pattern good enough. J $ man xlfonts J ... JXlsfonts lists the fonts that match the given pattern. The wildcard Jcharacter * may be used to match any sequence of characters (includ- Jing none), and ? to match any single character. If no pattern is Jgiven, * is assumed. J ... J In what way is that not clear? I see. hummm, BTW we would expect it to act like ls. Obviously it matches more: $ xlsfonts taip* -eten-fixed-medium-r-normal--16-150-75-75-c-160-big5.eten-0 -eten-fixed-medium-r-normal--24-230-75-75-c-240-big5.eten-0 taipei16 taipei24 OK, mention it will get aliases etc. -- http://jidanni.org/ Taiwan(04)25854780
Re: i845 patch for 4.2.1 debs
On Wed, Oct 30, 2002 at 01:32:00PM -0800, Michael Cardenas wrote: First off, I'd like to say thank you to Branden for your amazing work. I've been working on your debs for the last few days, and they build flawlessly. Glad to hear it! I've been asked by my employer to backport the Intel i845 2d driver so that we can support it in our next release, and so I did. For anyone interested, the patch is attached. I didn't follow your naming scheme exactly, so the patch is not 000 even though it's stolen_from_HEAD. I did this because I didn't want to have to adjust all of your other patches which were complaining about offsets, just to get the debs to compile. No problem, I'll pick those nits. One problem I did encounter is that when I do a dpkg-buildpackage -nc the object files still seem to get cleaned. Is there something I'm misunderstanding? Hmm, I never use the -nc option, so I am not sure. I'm pretty sure my rules file isn't written wrongly in this respect. For now, I've only done the most basic testing. RedHat backported the same driver and includes it in limbo, which I believe is rh8, so it must be somewhat stable. As I get more results from our testing dept, I will forward them to you, if you're interested. Yes, please. I'll see if I can get this into 4.2.1-4. Thanks for your efforts. -- G. Branden Robinson|The best place to hide something is Debian GNU/Linux |in documentation. [EMAIL PROTECTED] |-- Ethan Benson http://people.debian.org/~branden/ | pgpwJAIi6DjXC.pgp Description: PGP signature
Processed: tagging 162880
Processing commands for [EMAIL PROTECTED]: tag 162880 + upstream Bug#162880: xserver-xfree86: [s3virge] server causes sound distortion on ViRGE/DX or /GX rev 1 Tags added: upstream End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#167009: acknowledged by developer (Re: Bug#167009: Additional details)
On Wed, Oct 30, 2002 at 08:18:05PM -0600, Debian Bug Tracking System wrote: Once cannot expect power management-related functionality to work when one's kernel doesn't support power management, or when the interfaces to the kernel's power management support are not set up. One can expect Debian packages to set up the prerequisites they need to operate properly. Perhaps the bug is not with X, but I submit that it is still a bug. We should not be shipping a system configured by default in a way such that we have these lockups. If these lockups are occuring becuase there is no /dev/apm_bios, couldn't X's postinst at least create it? Interestingly, powermgmt-base presents a question about this. On x86 machines, apmd depends on this package, but nothing does on powerpc. Perhaps xserver-xfree86 should do so, to ensure that proper power management interfaces are available to userland? powermgmt-base also appears to take care of the situation properly for people using devfs. Moreover, its size is 128K installed and depends only on makedev, libc6, and debconf. It should not pose any problem for the X server. -- John
Bug#167009: acknowledged by developer (Re: Bug#167009: Additional details)
On Wed, Oct 30, 2002 at 09:47:57PM -0500, John Goerzen wrote: On Wed, Oct 30, 2002 at 08:18:05PM -0600, Debian Bug Tracking System wrote: Once cannot expect power management-related functionality to work when one's kernel doesn't support power management, or when the interfaces to the kernel's power management support are not set up. One can expect Debian packages to set up the prerequisites they need to operate properly. Power management support packages aren't prerequisites for systems that don't have power management. Perhaps the bug is not with X, but I submit that it is still a bug. Well, why don't you go ask debian-devel what package should handle this sort of thing? If these lockups are occuring becuase there is no /dev/apm_bios, couldn't X's postinst at least create it? Why shouldn't the makedev package? Interestingly, powermgmt-base presents a question about this. On x86 machines, apmd depends on this package, but nothing does on powerpc. Perhaps xserver-xfree86 should do so, to ensure that proper power management interfaces are available to userland? And what of people using other X server packages, or with no X server at all? Shall we just assume those folks don't need power management support? powermgmt-base also appears to take care of the situation properly for people using devfs. Moreover, its size is 128K installed and depends only on makedev, libc6, and debconf. It should not pose any problem for the X server. Sounds like you have a problem with Debian's PowerPC architecture support, and not a problem with XFree86 at all. -- G. Branden Robinson| Convictions are more dangerous Debian GNU/Linux | enemies of truth than lies. [EMAIL PROTECTED] | -- Friedrich Nietzsche http://www.deadbeast.net/~branden/ | pgpx42gW6LZ2V.pgp Description: PGP signature
