CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/01/12 06:15:33 Log message: Use libpng from the NetBSD packages system. Modified files: xc/programs/Xserver/hw/xfree86/etc/bindist/NetBSD-ix86/: host.def Revision ChangesPath 1.6 +5 -1 xc/programs/Xserver/hw/xfree86/etc/bindist/NetBSD-ix86/host.def ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED]03/01/12 18:22:51 Log message: Modified files: xc/programs/Xserver/hw/xfree86/: CHANGELOG Revision ChangesPath 3.2472+2 -1 xc/programs/Xserver/hw/xfree86/CHANGELOG ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED]03/01/12 18:27:31 Log message: Modified files: xc/programs/Xserver/hw/xfree86/: CHANGELOG Revision ChangesPath 3.2473+2 -1 xc/programs/Xserver/hw/xfree86/CHANGELOG ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/01/12 19:57:59 Log message: o Minor change in how objects are gc protected while being read, this was done as an experiment to avoid fragmentation and a pseudo copying-gc, since the gains where smaller than 10% I kept the old simpler gc for now, but having more long lived objets stored sequentially isn't a bad idea. o Added a call to XFlush before entering the lisp interpreter from the C code, this is an attempt to fix a problem that may happen when the computer is heavily loaded, and Xlib routines are called from the timeout signal handler to check for user requested interrupts. o Some fixes for the automatic indentation for the C language. Now it will ignore spaces followed by a collon, since it joins everything in a single :expression token, it was treating ternary expressions and bitfield declarations as labels (and dedenting when the collon was typed). Fixed also the code for fastly finding a safe point from where to start calculating the indentation; could become confused with code like: for (exp1, exp2; test; inc) Also added handling for code like: if (t1) if (t2) do exp; while (test); Now it should correctly align the while with the do. This isn't a very important feature, as writting code without braces may become confusing. Modified files: xc/programs/xedit/lisp/: read.c xedit.c xc/programs/xedit/lisp/modules/progmodes/: c.lsp Revision ChangesPath 1.34 +10 -11xc/programs/xedit/lisp/read.c 1.24 +2 -1 xc/programs/xedit/lisp/xedit.c 1.24 +23 -2 xc/programs/xedit/lisp/modules/progmodes/c.lsp ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
[Fonts] (no subject)
Dear sir, Brighsun Int'l Trading Co., Ltd. is a major export company in China. We can provide all sorts of Chinese products with very competitive prices. If you are in need of something, please don't hesitate to send me the specifications and quantities you need. Prompt response is guaranteed. Best regards, Frank Brighsun Int'l Trading Co., Ltd. Add: 379 Pudongnan Rd., Shanghai 200120, China Tel: 86-21-68869063,68869065,50540311-223 Fax: 86-21-58769500 Wesite: http://www.keytochina.net Mailto: [EMAIL PROTECTED] ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
[XFree86]Re: XFree86 4.2.99.3
Title: Message Have you checked out http://www.xfree86.org/support.html for information on the i845 driver and its support. I would recommend that as your first step. Georgina - Original Message - From: csgoh To: [EMAIL PROTECTED] Sent: Sunday, January 12, 2003 7:01 AM Subject: XFree86 4.2.99.3 Hi, I have problems trying to use XFree86 4.2.99.3on my Red Hat Linux 8.0. Installed and received the error "Fatal Server Error: Caught signal 11. Server aborting". The reason for the installation is that I am using an Intel 845GL chipset with Intel Extreme Graphics card and I only managed to get 1024X768 on 256 colours. Would really appreciate if somebody can help me with this. Please be more specific in the steps as I am very new to all this. Thanks in advance. csgoh
Re: [XFree86] [XFree86(TM) Bug Report] Incorrect DPI calculation
On Sun, 12 Jan 2003, Yury Tarasievich wrote: I don't know about X internals, what restrains X from calculating DPI once the mode is switched? Or perhaps the apps arer going to be somehow impacted? If we changed the DPI when the mode changed, the the apps would need to know, but there is no way for the server to tell the app the new value (unless the RENDER extension make s it possible this). -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] problems with XFree86 4.2.1 on OpenBSD 3.2
Christino Tamon wrote (in a message from Sunday 12) Dear XFree86 developers: I'm having some problems with the XFree86 4.2.1 version that I ran along with a new OpenBSD 3.2. I used to run OpenBSD 3.1 with XFre86 4.x.x which gave me no problems. The machine that I used is a Dell 500MHz Pentium III (circa 1999). I'm planning to backtrace to OpenBSD 3.1 again and/or reinstall OpenBSD 3.2. I'm trying to see if it's OpenBSD or the XFree86 version that might be the cause. But if you have anyone with similar X problems, I'd be happy to hear their stories. Remove the contents of the /tmp/.X11-unix directory and try again. The messages you're seeing here are caused by a stale Unix domain socket here. There is probably another error that you're going to see get in XFree86.0.log if this directory is empty before X startup, but this error causes the X server to abort before it has installed the handler that would normally clean up /tmp/.X11-unix on exit. Matthieu ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] problem on powermac G4 dualie
I have a powermac G4 dual 533 snakebite with GForce 2MX. I am using Linux pmac 2.4.21-pre2 #2 SMP Thu Jan 2 07:32:33 EST 2003 ppc unknown. The last couple CVS compiles of XFree with gcc (GCC) 3.2.2 20021212 (Debian prerelease) just cause one CPU to be used up. The screen just goes black and there is no X Window. XFree86 Version 4.2.99.3 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 6 January 2003 X Applications run remotely seem to work though. Anyone else had this or similar problem? Fred ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] problem on powermac G4 dualie
On Sun, Jan 12, 2003 at 06:35:54PM -0500, Fred Heitkamp scrawled: I have a powermac G4 dual 533 snakebite with GForce 2MX. I am using Linux pmac 2.4.21-pre2 #2 SMP Thu Jan 2 07:32:33 EST 2003 ppc unknown. The last couple CVS compiles of XFree with gcc (GCC) 3.2.2 20021212 (Debian prerelease) just cause one CPU to be used up. The screen just goes black and there is no X Window. XFree86 Version 4.2.99.3 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 6 January 2003 X Applications run remotely seem to work though. Anyone else had this or similar problem? If you have a flat panel display, you need 'Option FlatPanel'. -- Daniel Stone [EMAIL PROTECTED] Developer, Trinity College, University of Melbourne msg00160/pgp0.pgp Description: PGP signature
[XFree86] crash problem
Hi!, my english is bad,but i still hope that you will understand what i'm trying to say... -- linux red-hat XFree86 Version 4.0.3 WindowMaker kylix3(open) when i execute startx command, Xwindows run with windowmaker windowmanager. windowmaker runs xterm and kylix(startdelphi) automaticly.. i make simple program with one button and one Edit which is used to display text from files (i can send you program). when i run program i start pasting some strings into it's Edit by pressing ctrl+v...after a while Xserver crashes with message: -- Fatal server error:Caught signal 11. Server abortingWhen reporting a problem related to a server crash, please sendthe full server output, not just the last messages.This can be found in the log file /var/log/XFree86.0.log.Please report problems to [EMAIL PROTECTED]^Vxinit: connection to X server lost.[root@localhost /root]# ^Vxterm: fatal IO error 32 (Broken pipe) orKillClienton X server :0.0xterm: fatal IO error 32 (Broken pipe) or KillClient on X server :0.0/usr/bin/wmaker warning: got signal 1 (Hangup) - exiting... --- i've tested this crashing without xterm run,and X didn't crash... -- Viktor Bojoviæ, [EMAIL PROTECTED] on 01.13.2003 XFree86.0.log Description: Binary data
[XFree86] [XFree86(TM) Bug Report] the IS (Icelandic) keymap is incorrect
Regarding: the IS (Icelandic) keymap is incorrect
Email: [EMAIL PROTECTED]
XFree86 Version: XFree86 Version 4.2.0 (Red Hat Linux release: 4.2.0-72)
OS: Red Hat Linux release 8.0 (Psyche)
Area: Xserver
Server: XFree86 (The XFree86 4.x server)
Video Card:
Im using a NVidia card, but that doesnt matter.
Description:
The file /usr/X11R6/lib/X11/xkb/symbols/is is bad.
The problem is:
key AC11 {[ dead_acute, Adiaeresis ],
[ dead_circumflex ] };
That Adiaeresis should not be there. In stead it should be:
key AC11 {[ dead_acute, dead_diaeresis ],
[ dead_circumflex ] };
Repeat By:
See the description.
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] IRC channels that might be useful for many XFree86 developers andusers.
Many people are aware of these IRC channels already, but many may also not be aware. I thought I would post a quick note here to let everyone know that there are some unofficial XFree86 related IRC channels for both development discussion as well as end user help, etc. that people can use. The following channels are all on the irc.freenode.net network, which was previously known as irc.openprojects.net. Please use the irc.freenode.net address when connecting as the latter address is obsolete. The channels are: #xfree86 Average number of users is approx 45 A general XFree86 chat forum for end users, developers and others looking to discuss XFree86 related items, including, but not limited to: XFree86 configuration help, compiling XFree86, troubleshooting problems, and other general topics of discussion. GNOME/KDE and other similar higher level GUI things are not on topic, and those projects have their own respective channels for discussion. Some XFree86/X11 developers frequent this channel and help people out when they can as time permits. Developmental discussions sometimes occur here as well, however people are encouraged to use the #xfree86-devel or #dri-devel channels below first when discussing developmental issues. #xfree86-devel Average number of users is approx 14, but growing lately This channel is intended for developers to discuss topics related to all sides of X development, including X server debugging and troubleshooting, video driver programming, or any similar discussion regarding the development of XFree86 itself. Questions about X client application development, X APIs, and similar are also welcome. The channel is rather young however and there isn't always someone present who has an answer to a given question. Developers are welcome, and in fact encouraged to lurk in the channel and help other developers also. Some XFree86/X11 developers also frequent this channel and will generally respond to questions if they are at the keyboard, are able to answer the question, and are free to chat. #dri Average number of users is approx 15 This channel is for end user discussion of issues related to DRI, 3D acceleration, configuration, etc. I don't frequent this channel so I'm not familiar with the channel's policies, or details of the types of discussions that make up the general content though. If you've got DRI questions, it is probably worth checking out. DRI related end user questions are also welcome in the #xfree86 channel. #dri-devel Average number of users is approx 20 This channel is quite a bit different than the ones above on a day to day basis. The channel's focus is strictly developmental discussion of DRI (Direct Rendering Infrastructure), Mesa, and the kernel side of DRI - the DRM. End user questions, configuration help, and similar should not be asked here, but should be asked in either #dri or #xfree86. DRI development meetings are held every Monday at 5:00pm EST (2200 UTC) for a couple of hours generally in which DRI developers get together to interactively discuss DRI developmental issues. The meetings are open to anyone to attend, and not restricted to DRI developers. Note that end users asking for help configuring DRI or XFree86 is very off topic on #dri-devel, and should be asked instead on #xfree86 or #dri, however end users are welcome to participate in discussions, ask questions about development, how to get started developing DRI, and also provide feedback that may help developers. Most of the above channels have been available on irc.freenode.net (formerly irc.openprojects.net) for a year or more, however some are a bit newer. All XFree86 users and developers are welcome to drop by and participate, ask questions, help others. Some people hate IRC of course, and won't at all be interested in any of this. I used to be one of those people for about 6 years myself, so I understand where you're coming from. ;o) I've since found IRC can however be a useful tool for communication with other developers and users though, and thought I'd post a note here to let people know these discussion forums exist should they wish to participate. Take care, TTYL -- Mike A. Harris ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
