Re: random sig 11 in 4.0.2
Seth Arnold [EMAIL PROTECTED] writes: [Branden, also note that I would find the XFree86.?.log file more useful if it date-time stamped once in a while similar to crontab's --mark-- facility -- consider asking the good people at xf86 to add such a feature to help debugging. If the 1000 lines of mode changes happened when I loaded X, fine. If one line was printed for each desktop switch I do (with windowmaker's ^+alt+left|right hot keys), fine. If the 1000 lines were printed in the second before horrible death, it sure would be nice to know. :] That's VidModeExtension doing that, normally a game. There isn't a "SwithToMode" line, so I suspect something *tried* to switch modes. In particular this doesn't happen when you press c-a-[+-], and it most definitely doesn't happen when you switch workspaces with wmaker (why would it?) -- Marcelo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: broken key configuration in unstable / policy rules needed?
On Sun, Mar 25, 2001 at 08:40:24PM +0200, Eduard Bloch wrote: First: I am sick of the stuff I am writting about. 1) there is a known problem with xterm. It is an upstream bug. Not sure what causes the breakage in all the other programs. 2) You could try going through the debugging steps described in the Debian X FAQ so that you can provide more info than "it's broken". -- G. Branden Robinson | Psychology is really biology. Debian GNU/Linux| Biology is really chemistry. [EMAIL PROTECTED] | Chemistry is really physics. http://www.debian.org/~branden/ | Physics is really math. PGP signature
fresh batch of X policy proposals
Hello folks, I have made some proposed revisions to Debian X policy. None of them should come as a surprise to readers of this mailing list. Please check out the debian-policy mailing list. I'd appreciate discussion of these proposals (remember to mail the bugs under which they were filed, not the debian-policy mailing list). You can also find these proposals at the following URL's: http://bugs.debian.org/91249 http://bugs.debian.org/91252 http://bugs.debian.org/91257 http://bugs.debian.org/91259 http://bugs.debian.org/91260 http://bugs.debian.org/91261 I still need seconds for 91252, 91257, and 91261. Here are the one-line summaries: 91249 [PROPOSED] bring X support policy into line with must/should/may usage 91252 [PROPOSED] enhanced x-terminal-emulator policy, second try 91257 [PROPOSED] changes to X font policy 91259 [PROPOSED] minor changes to app-defaults policy 91260 [PROPOSED] reclarifying the policy about X and the FHS 91261 [PROPOSED] modernized rewording of X/Motif policy -- G. Branden Robinson | Debian GNU/Linux| If existence exists, [EMAIL PROTECTED] | why create a creator? http://www.debian.org/~branden/ | PGP signature
Re: Help needed, TDFX [Re: Release-critical Bugreport for March 23, 2001]
* Zephaniah E. Hull [EMAIL PROTECTED] [010324 13:48]: (FWIW, almost all 2D/3D cards have the same.) Uh. uh. ah. uh. Are you trying to say that windowed opengl with multiple opengl contexts and 2d-apps side-by-side doesn't work on most pc cards? Nvidia cards do it fine. -- Scott Dier [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.ringworld.org/ #linuxos@efnet "When's the last time you used duct tape on a duct?" -Larry Wall PGP signature
Re: Help needed, TDFX [Re: Release-critical Bugreport for March 23, 2001]
Scott Dier [EMAIL PROTECTED] writes: Uh. uh. ah. uh. Are you trying to say that windowed opengl with multiple opengl contexts and 2d-apps side-by-side doesn't work on most pc cards? Nvidia cards do it fine. No. He's saying that you have to pay attention to what you are doing at the driver level if you want to have multiple contexts. What do you think that kernel module you load does? If you get the chance, open two OpenGL contexts side by side on a SGI box. Very different experience. -- Marcelo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CVS DRI packages.
On Sun, Mar 25, 2001 at 05:15:09AM +0200, Marcelo E. Magallon wrote: I'm sorry, I forgot one important bit. Zephaniah E. Hull [EMAIL PROTECTED] writes: My rough naming scheme is as follows: xlibmesa3-dri, xlibmesa-dri-dev, xlibosmesa3-dri, xlibosmesa-dri-dev, and xserver-dri. You might want to provide xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel (or whatever the actual path is), as every now and then the DRM modules in the kernel get out of sync with the ones in CVS. Yes, this should be provided. Shouldn't it be provided in a package like drm- modules-src, though, like lm-sensors-src and alsa-src? This would mean breaking that part of the trunk off and placing it in /usr/src/modules/drm or the like, and having the dri modules built whenever make-kpkg makes a modules_image. I'm getting ahead of Zeph here, though, and I'm of no skill to volunteer help... :) -- -=|JP|=-This space intentionally left blank. Jon Pennington | Debian 2.4 -o) [EMAIL PROTECTED] | Auto Enthusiast/\\ Kansas City, MO, USA| Proud Husband and Father _\_V
random sig 11 in 4.0.2
Greetings! :) [Sent to debian-x because I do not know the proper package against which to submit a bug report. Branden, please advise for general X bug reports.] This is the second sig11 I have seen lately. I have also seen cut'n'paste fail miserably for the last few days. (Well, the cut seems fine, but the paste is often noise, sometimes text from elsewhere on screen, and often one of my rxvt-xpm terminals dies during the 'paste' operation.) I do not know if the cut'n'paste problem is related to the signal 11s. This sig11, I was running windowmaker, xmms, wmxmms, wmbiff, about ten rxvt-xpm terminals (most running bash, one mutt, probably a few vims) konqueror, and xscreensaver. The xscreensaver was running a screen hack, though I did not notice which one. :( xmms was stopped but still open. I was not interacting with my computer myself, though it does do stuff on its own once in a while in typical unix fashion. :) I am running Linux kernel: Linux amidala 2.4.2 #2 SMP Tue Mar 20 20:34:01 PST 2001 i686 unknown I built it myself from kernel.org sources, gpg verified etc. The video card is a matrox g400max running with only a single monitor attached. Does anyone know what other information would be useful in tracking down this crash? (I've found that I can also reliably cause an X crash through BitKeeper's 'citool' application, though I haven't put any effort into figuring out a simpler test case than my whole source tree + BitKeeper. Are these two related?) The machine has otherwise been very stable -- it is only in the last few days (two weeks at most, probably only one week) that I have had these problems. I try to keep fairly up-to-date with debian unstable. Thanks all. :) [Branden, also note that I would find the XFree86.?.log file more useful if it date-time stamped once in a while similar to crontab's --mark-- facility -- consider asking the good people at xf86 to add such a feature to help debugging. If the 1000 lines of mode changes happened when I loaded X, fine. If one line was printed for each desktop switch I do (with windowmaker's ^+alt+left|right hot keys), fine. If the 1000 lines were printed in the second before horrible death, it sure would be nice to know. :] -- Earthlink: The #1 provider of unsolicited bulk email to the Internet. XFree86 Version 4.0.2 / X Window System (protocol Version 11, revision 0, vendor release 6400) Release Date: 18 December 2000 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Operating System: Linux 2.2.18 i686 [ELF] Module Loader present (==) Log file: /var/log/XFree86.0.log, Time: Thu Mar 22 18:49:07 2001 (==) Using config file: /etc/X11/XF86Config-4 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (??) unknown. (==) ServerLayout Single (**) |--Screen Screen0 (0) (**) | |--Monitor Mitsubishi (**) | |--Device G400_0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (WW) The directory /usr/X11R6/lib/X11/fonts/PEX/ does not exist. Entry deleted from font path. (**) FontPath set to /usr/X11R6/lib/X11/fonts/freefont/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/:noscale,/usr/X11R6/lib/X11/fonts/misc/:noscale (==) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (--) using VT number 7 (WW) Cannot open APM (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.3 XFree86 XInput driver : 0.1 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.2 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.0.2, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.2 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.0.2, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.3 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,7190 card , rev 03 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,7191 card , rev 03 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 8086,7110 card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 8086,7111 card , rev 01 class 01,01,80 hdr 00 (II) PCI: 00:07:2: chip 8086,7112 card , rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:07:3: chip 8086,7113 card , rev 02 class
Re: random sig 11 in 4.0.2
Seth Arnold [EMAIL PROTECTED] writes: [Branden, also note that I would find the XFree86.?.log file more useful if it date-time stamped once in a while similar to crontab's --mark-- facility -- consider asking the good people at xf86 to add such a feature to help debugging. If the 1000 lines of mode changes happened when I loaded X, fine. If one line was printed for each desktop switch I do (with windowmaker's ^+alt+left|right hot keys), fine. If the 1000 lines were printed in the second before horrible death, it sure would be nice to know. :] That's VidModeExtension doing that, normally a game. There isn't a SwithToMode line, so I suspect something *tried* to switch modes. In particular this doesn't happen when you press c-a-[+-], and it most definitely doesn't happen when you switch workspaces with wmaker (why would it?) -- Marcelo
broken key configuration in unstable / policy rules needed?
Hi people! First: I am sick of the stuff I am writting about. I have more and more problems with configuration of HOME and END keys in the current unstable. On my system, they work today in Gnome Terminal in any environment konsole on !KDE rxvt wterm any X apps, including Tk, Gtk, Qt, ... slang and ncurses apps in any terminals (local) and they are broken in readline apps in konsole in KDE! and completely broken in xterm Eterm remote shells in any x-terminals Is this a known bug? I remember the Del/Backspace trouble while Potato frozen, the current situation is similar to this. Do we need a new policy rule to force all maintainers of x-terminal-emulators to fix the key configuration? What is going wrong there? While trying to find the reason for the chaos, I noticed that there are no up-to-date Xressources in /etc/X11/Xressources/! But this directory is searched by Xsession for Xressource files. What about all the files in /etc/X11/app-defaults/? If I do xrdb -merge them into running X, I get strange results. (Got many error messages, high CPU usage, misconfigured X-Server where no X apps could start, Xressource settings were completely fucked up etc.). So which file should be loaded while startx? Questions, questions... MfG, Eduard. -- Eduard Bloch [EMAIL PROTECTED]; HP: http://eduard.bloch.com/edecosi 0xEDF008C5(GnuPG): E6EB 98E2 B885 8FF0 6C04 5C1D E106 481E EDF0 08C5
Re: broken key configuration in unstable / policy rules needed?
On Sun, Mar 25, 2001 at 08:40:24PM +0200, Eduard Bloch wrote: First: I am sick of the stuff I am writting about. 1) there is a known problem with xterm. It is an upstream bug. Not sure what causes the breakage in all the other programs. 2) You could try going through the debugging steps described in the Debian X FAQ so that you can provide more info than it's broken. -- G. Branden Robinson | Psychology is really biology. Debian GNU/Linux| Biology is really chemistry. [EMAIL PROTECTED] | Chemistry is really physics. http://www.debian.org/~branden/ | Physics is really math. pgpUpExxM75rc.pgp Description: PGP signature
fresh batch of X policy proposals
Hello folks, I have made some proposed revisions to Debian X policy. None of them should come as a surprise to readers of this mailing list. Please check out the debian-policy mailing list. I'd appreciate discussion of these proposals (remember to mail the bugs under which they were filed, not the debian-policy mailing list). You can also find these proposals at the following URL's: http://bugs.debian.org/91249 http://bugs.debian.org/91252 http://bugs.debian.org/91257 http://bugs.debian.org/91259 http://bugs.debian.org/91260 http://bugs.debian.org/91261 I still need seconds for 91252, 91257, and 91261. Here are the one-line summaries: 91249 [PROPOSED] bring X support policy into line with must/should/may usage 91252 [PROPOSED] enhanced x-terminal-emulator policy, second try 91257 [PROPOSED] changes to X font policy 91259 [PROPOSED] minor changes to app-defaults policy 91260 [PROPOSED] reclarifying the policy about X and the FHS 91261 [PROPOSED] modernized rewording of X/Motif policy -- G. Branden Robinson | Debian GNU/Linux| If existence exists, [EMAIL PROTECTED] | why create a creator? http://www.debian.org/~branden/ | pgpRs67ii302D.pgp Description: PGP signature
Re: Help needed, TDFX [Re: Release-critical Bugreport for March 23, 2001]
* Zephaniah E. Hull [EMAIL PROTECTED] [010324 13:48]: (FWIW, almost all 2D/3D cards have the same.) Uh. uh. ah. uh. Are you trying to say that windowed opengl with multiple opengl contexts and 2d-apps side-by-side doesn't work on most pc cards? Nvidia cards do it fine. -- Scott Dier [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.ringworld.org/ [EMAIL PROTECTED] When's the last time you used duct tape on a duct? -Larry Wall pgpUaTHJRq53Z.pgp Description: PGP signature
Re: Help needed, TDFX [Re: Release-critical Bugreport for March 23, 2001]
Scott Dier [EMAIL PROTECTED] writes: Uh. uh. ah. uh. Are you trying to say that windowed opengl with multiple opengl contexts and 2d-apps side-by-side doesn't work on most pc cards? Nvidia cards do it fine. No. He's saying that you have to pay attention to what you are doing at the driver level if you want to have multiple contexts. What do you think that kernel module you load does? If you get the chance, open two OpenGL contexts side by side on a SGI box. Very different experience. -- Marcelo
