User specific environment variables?
Hi, I have a question about /etc/X11/Xsession.d: When a user logs in with a dm, e.g. gdm, and chooses KDE or Gnome, then the user's .xsession is not executed, even if allowed in /etc/X11/Xsession.options. Since also the ~$HOME/.profile or $HOME/.login are never executed, the user has no chance to set individual environment variables. How is he supposed to do that? Proposal: Have another script in /etc/X11/Xsession.d, which checks whether /etc/X11/Xsession.options allows user specific environment scripts, and if so include $HOME/.profile (or anything like that). regards Hadmut
Re: ATTENTION BRANDEN ROBINSON
On Wed, Nov 03, 2004 at 02:00:49PM -0500, Branden Robinson wrote: I confirm that this configuration is deliberate. You can read into that whatever you like, but if you care to hold opinions that aren't at wide variance with reality, then you should be advised that the reason has nothing to do with spam, and everything to do with the extremely abusive tone you take with me in private communications (both in email[2] and IRC[3]). As you wish, I will not communicate with you, except where you may read anything I write via various public fora. Overfiend DANIELS: YOU'RE FUCKING DEAD Overfiend MOTHER FUCKING YEAH Overfiend augh. You know, I love Nathanael Nerode for all the help he gave me with 4.3.0, but GOD DAMN DOES THIS GUY EVER FUCKING NEED AN MUA THAT DOESN'T BREAK THREADS. AGH Overfiend FUCKING BASTARDS Overfiend FUCKING MORONIC PIECE OF **SHIT** Overfiend YOU LOOK FOR GOD DAMN FUCKING -lX11 EXACTLY WHERE YOU WERE TOLD TO, YOU GRABASSTIC PIECE OF DOG-FELLATING SHIT Overfiend THEY FUCKING REWROTE THE MOUSE DRIVER @Overfiend I'D LIKE TO RAPE THE BUILDDS WITH A CHAINSAW FOR FUCKING ME LIKE THIS @Overfiend ALL THAT FUCKING WORK AND LAMONT DIDN'T FIX THE .INSTALL FILE?!?!?!! Overfiend AND READ THE FUCKING BUG LOGS Overfiend FUCKING SCREEN BUG You may instead direct your rhetoric to public forums, where your approach to teamwork can be judged by your peers. You can communicate information to me about embargoed security issues in packages I maintain via the Debian Security Team[1]. Additionally, when such matters relate to XFree86 or any other package maintained by the X Strike Force, you can also communicate such information to me via Fabio or another person in the Uploaders: field of the package in question. As per your wish, I will deal exclusively with Fabio, who doesn't see fit to frequently post private communications to public lists. I am sorry that it has come to this where we cannot even co-operate on issues as critical to Debian as security vulnerabilites in the standard X implementations (which, it should be mentioned, are far from hypothetical). Daniel -- Daniel Stone[EMAIL PROTECTED] signature.asc Description: Digital signature
X Strike Force XFree86 SVN commit: r2011 - in trunk/debian: . patches
Author: branden
Date: 2004-11-04 09:25:23 -0500 (Thu, 04 Nov 2004)
New Revision: 2011
Modified:
trunk/debian/CHANGESETS
trunk/debian/TODO
trunk/debian/changelog
trunk/debian/patches/009_ati_r128_retry_idle_until_timeout.diff
Log:
Update patch #009 to improve the fix for the Rage128-specific problem with
engine lockups; because CCE idle commands may never finish, eventually
stop the engine altogether after a long enough period of inactivity.
Thanks to Daniel Jacobowitz for the original patch, this improved version,
and the real-world testing. (Closes: #278654)
Modified: trunk/debian/CHANGESETS
===
--- trunk/debian/CHANGESETS 2004-11-03 19:05:41 UTC (rev 2010)
+++ trunk/debian/CHANGESETS 2004-11-04 14:25:23 UTC (rev 2011)
@@ -233,4 +233,11 @@
description, per section 6.7.7 of the Debian Developers' Reference.
2009
+Update patch #009 to improve the fix for the Rage128-specific problem with
+engine lockups; because CCE idle commands may never finish, eventually
+stop the engine altogether after a long enough period of inactivity.
+Thanks to Daniel Jacobowitz for the original patch, this improved version,
+and the real-world testing. (Closes: #278654)
+2011
+
vim:set ai et sts=4 sw=4 tw=80:
Modified: trunk/debian/TODO
===
--- trunk/debian/TODO 2004-11-03 19:05:41 UTC (rev 2010)
+++ trunk/debian/TODO 2004-11-04 14:25:23 UTC (rev 2011)
@@ -55,8 +55,6 @@
because validlocale is a Perl utility provided by base-config.)
* #277699: apply NX kernel support to stop AMD64 kernel users from getting
SEGVs
from the XFree86 X server's ELF object loader [patch; BR]
-* #278654: apply Dan Jacobowitz's patch fixing a bad assumption in his previous
- patch correcting the Rage 128 engine reset logic [patch; BR]
* #279436: apply David Mosberger's PCI domain fix [patch; BR]
4.3.0.dfsg.1-10
Modified: trunk/debian/changelog
===
--- trunk/debian/changelog 2004-11-03 19:05:41 UTC (rev 2010)
+++ trunk/debian/changelog 2004-11-04 14:25:23 UTC (rev 2011)
@@ -116,6 +116,12 @@
the short description, and transitional package in the extended
description, per section 6.7.7 of the Debian Developers' Reference.
+ * Update patch #009 to improve the fix for the Rage128-specific problem with
+engine lockups; because CCE idle commands may never finish, eventually
+stop the engine altogether after a long enough period of inactivity.
+Thanks to Daniel Jacobowitz for the original patch, this improved version,
+and the real-world testing. (Closes: #278654)
+
Changes by Denis Barbier and Fabio M. Di Nitto:
* Edit xc/programs/xkbcomp/symbols/pc/Imakefile so that the new pc/us_intl
@@ -198,7 +204,7 @@
exiting upon encountering the first shell interpeter that fails on the
script; instead, attempt all the interpreters and report all that fail.
- -- Branden Robinson [EMAIL PROTECTED] Wed, 3 Nov 2004 12:47:55 -0500
+ -- Branden Robinson [EMAIL PROTECTED] Thu, 4 Nov 2004 09:22:55 -0500
xfree86 (4.3.0.dfsg.1-8) unstable; urgency=high
Modified: trunk/debian/patches/009_ati_r128_retry_idle_until_timeout.diff
===
--- trunk/debian/patches/009_ati_r128_retry_idle_until_timeout.diff
2004-11-03 19:05:41 UTC (rev 2010)
+++ trunk/debian/patches/009_ati_r128_retry_idle_until_timeout.diff
2004-11-04 14:25:23 UTC (rev 2011)
@@ -10,36 +10,21 @@
--- xc/programs/Xserver/hw/xfree86/drivers/ati/r128_accel.c~ 2004-06-01
12:17:33.0 -0500
+++ xc/programs/Xserver/hw/xfree86/drivers/ati/r128_accel.c2004-06-01
12:21:37.0 -0500
-@@ -228,25 +228,34 @@
- void R128CCEWaitForIdle(ScrnInfoPtr pScrn)
- {
- R128InfoPtr info = R128PTR(pScrn);
--int ret, i;
-+int ret, i, j;
-
- FLUSH_RING();
-
- for (;;) {
--i = 0;
--do {
--ret = drmCommandNone(info-drmFD, DRM_R128_CCE_IDLE);
+@@ -236,17 +236,23 @@
+ i = 0;
+ do {
+ ret = drmCommandNone(info-drmFD, DRM_R128_CCE_IDLE);
-} while ( ret errno == EBUSY i++ R128_IDLE_RETRY );
-+ j = 0;
-+ do {
-+ i = 0;
-+ do {
-+ ret = drmCommandNone(info-drmFD, DRM_R128_CCE_IDLE);
-+ } while ( ret errno == EBUSY i++ R128_IDLE_RETRY );
-+ } while ( ret errno == EBUSY j++ R128_TIMEOUT );
++} while ( ret errno == EBUSY i++ (R128_IDLE_RETRY *
R128_IDLE_RETRY) );
if (ret ret != -EBUSY) {
xf86DrvMsg(pScrn-scrnIndex, X_ERROR,
%s: CCE idle %d\n, __FUNCTION__, ret);
}
-+ if (i != 0 || j != 0) {
++ if (i R128_IDLE_RETRY) {
+ xf86DrvMsg(pScrn-scrnIndex, X_ERROR,
-+ %s: (DEBUG) CCE idle took
Processed: tagging 278654
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.5 # fixed in Debian X Strike Force XFree86 repository; to view, run svn diff -r 2010:2011 svn://necrotic.deadbeast.net/xfree86 tags 278654 + pending Bug#278654: xserver-xfree86: [r128] Problems with existing CCE idle fix Tags were: patch Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#279674: xnest: forgets to check the keyboard state when it receives the keyboard focus.
Package: xnest Version: 4.3.0.dfsg.1-8 Severity: normal XNest forgets to check the keyboard state when it receives the keyboard focus. It gets the modifier key press, but it can not receive the key release. so if you enter xnest with ctrl on, it's on until you press the same key again. frustrating to type with control or alt on ... thanks -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 'testing'), (300, 'unstable'), (250, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.8.1-ck7.2004.09.13.ws.ck7.1.p4 Locale: LANG=C, LC_CTYPE=en_US Versions of packages xnest depends on: ii libc6 2.3.2.ds1-13 GNU C Library: Shared libraries an ii libfreetype6 2.1.7-2.1 FreeType 2 font engine, shared lib ii libxext6 4.3.0.dfsg.1-4 X Window System miscellaneous exte ii xlibs 4.3.0.dfsg.1-4 X Window System client libraries m ii xserver-common4.3.0.dfsg.1-4 files and utilities common to all ii zlib1g1:1.2.1.1-5compression library - runtime -- no debconf information
Re: ATTENTION BRANDEN AND DANIEL
On Thu, 2004-11-04 at 00:49 -0800, Daniel Stone wrote: On Wed, Nov 03, 2004 at 02:00:49PM -0500, Branden Robinson wrote: I confirm that this configuration is deliberate. You can read into that whatever you like, but if you care to hold opinions that aren't at wide variance with reality, then you should be advised that the reason has nothing to do with spam, and everything to do with the extremely abusive tone you take with me in private communications (both in email[2] and IRC[3]). As you wish, I will not communicate with you, except where you may read anything I write via various public fora. [...] (obvious reason) You may instead direct your rhetoric to public forums, where your approach to teamwork can be judged by your peers. You can communicate information to me about embargoed security issues in packages I maintain via the Debian Security Team[1]. Additionally, when such matters relate to XFree86 or any other package maintained by the X Strike Force, you can also communicate such information to me via Fabio or another person in the Uploaders: field of the package in question. As per your wish, I will deal exclusively with Fabio, who doesn't see fit to frequently post private communications to public lists. I am sorry that it has come to this where we cannot even co-operate on issues as critical to Debian as security vulnerabilites in the standard X implementations (which, it should be mentioned, are far from hypothetical). Please, are we capable of having this mediated out. I know that the both of you are understanding people. Can we please have a bit of compromise from both of you on this issue? There is a time and a place for this kind of rhetoric, but this with Sarge Pending, is neither the time nor the place (nor the era) for this kind of thing to get in the way of getting things done. There are FAR to many things to put this energy to rather than bickering and wasting your valuable abilities on this. Both of you are valuable to me, valuable in such ways that I need not worry *IF* something is addressed, but in how I could use a stopwatch to measure the swiftness with which things are done. I know, silly me being a greedy little Debian user (actually that is funny as I am not exactly little either 330#). If I need to, I'll just sit on both of you until this is settled or at least manageable for all parties concerned. Sincerely, with an offer to mediate. With such a wonderful signature generated by the: Surrealist Compliment Generator http://www.madsci.org/cgi-bin/cgiwrap/~lynn/jardin/SCG This has got to mean something. -- greg, [EMAIL PROTECTED] REMEMBER ED CURRY! http://www.iwethey.org/ed_curry The phase of your hallucinations reminds me of those balmy days when the championship mould was breeding, when the fish were long, and so were the valued floats of men we drank through narrow straws... signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#278724: [Sarge]: xserver-xfree86 freeze on errors from gv|xmms|lopster
Processing commands for [EMAIL PROTECTED]: retitle 278724 xserver-xfree86: [nv] system hang when using gv, xmms, or lopster on NV5 [Aladdin TNT2] rev 0x20 Bug#278724: [Sarge]: xserver-xfree86 freeze on errors from gv|xmms|lopster Changed Bug title. severity 278724 important Bug#278724: xserver-xfree86: [nv] system hang when using gv, xmms, or lopster on NV5 [Aladdin TNT2] rev 0x20 Severity set to `important'. tag 278724 + moreinfo upstream Bug#278724: xserver-xfree86: [nv] system hang when using gv, xmms, or lopster on NV5 [Aladdin TNT2] rev 0x20 There were no tags set. Tags added: moreinfo, upstream thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#278724: [Sarge]: xserver-xfree86 freeze on errors from gv|xmms|lopster
retitle 278724 xserver-xfree86: [nv] system hang when using gv, xmms, or lopster on NV5 [Aladdin TNT2] rev 0x20 severity 278724 important tag 278724 + moreinfo upstream thanks On Fri, Oct 29, 2004 at 12:58:09AM +0200, [EMAIL PROTECTED] wrote: While testing a few packages running under X I experienced a total freeze of by box: as this happened with xmms, lopster and - today - with gv, the doubt is coming out that it might depend on the X Window System, although I cannot tell for sure. [...] In case you need any additional info I could obtain (which I'm not aware of at the moment) please feel free to ask. May I add, however, that the same type of freeze happened with lopster (when I tried to use something not available) and with xmms, clicking on 'play' before choosing a file to play, so it should not be too hard to reproduce the error. Thanks for your report. We appreciate you sending along your XF86Config-4 file, but we need a little more information. 1) Can you please mail [EMAIL PROTECTED] the contents of your /var/log/XFree86.0.log file? A copy of the log file after the lockup has occurred (but before the X server has started again) would be most valuable. If you run a display manager like gdm, or xdm, this may be most easily obtained by rebooting into single-user mode after the box locks, and copying /var/log/XFree86.0.log to a safe location while in single-user mode. 2) Can you reproduce the problem with xserver-xfree86-dbg? I am attaching a form letter that describes how to debug the X server. This might enable us to track down the piece of code that is causing the lockup. [The following is a form letter.] Can you reproduce the problem with xserver-xfree86-dbg? Install the package and tell debconf you want to use that X server. Then restart the X server and try to reproduce the bug (should be easy). If it doesn't crash, let us know. If it does crash, become root, enable core dumps (ulimit -c unlimited in bash), start the X server as root and reproduce the crash again: # startx $(which x-terminal-emulator) -- :1 (If no X server is running at DISPLAY=:0, you can leave off the -- :1 part). This will launch the X server running a lone terminal client with no window manager. Run the client that provokes the crash from the terminal prompt. If the X server crashes, it should leave a core dump in /etc/X11. We then run the GNU Debugger, GDB, on the core file and executable. We're interested in a backtrace of execution. The X server has a signal handler in it so it can do things like exit gracefully (restoring the text console, and so forth), so we're not actually interested in all the stack frames -- just those above the signal handler. Here's an example GDB session I logged after provoking an artificial server crash (with kill -SEGV). % gdb $(which XFree86-debug) core GNU gdb 6.1-debian Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-linux...Using host libthread_db library /lib/libthread_db.so.1. Core was generated by `/usr/X11R6/bin/X :1'. Program terminated with signal 6, Aborted. Reading symbols from /usr/lib/libfreetype.so.6...done. Loaded symbols for /usr/lib/libfreetype.so.6 Reading symbols from /usr/lib/libz.so.1...done. Loaded symbols for /usr/lib/libz.so.1 Reading symbols from /lib/libm.so.6...done. Loaded symbols for /lib/libm.so.6 Reading symbols from /lib/libc.so.6...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 #0 0x400f2721 in kill () from /lib/libc.so.6 (gdb) bt #0 0x400f2721 in kill () from /lib/libc.so.6 #1 0x400f24c5 in raise () from /lib/libc.so.6 #2 0x400f39e8 in abort () from /lib/libc.so.6 #3 0x08464b8c in ddxGiveUp () at xf86Init.c:1173 #4 0x08464c6b in AbortDDX () at xf86Init.c:1224 #5 0x08508bd7 in AbortServer () at utils.c:436 #6 0x0850a563 in FatalError (f=0x8a26ea0 Caught signal %d. Server aborting\n) at utils.c:1421 #7 0x0847fbf5 in xf86SigHandler (signo=11) at xf86Events.c:1198 #8 signal handler called #9 0x40199dd2 in select () from /lib/libc.so.6 #10 0x401f8550 in ?? () from /lib/libc.so.6 #11 0x400164a0 in ?? () from /lib/ld-linux.so.2 #12 0xb8f0 in ?? () #13 0x08502520 in WaitForSomething (pClientsReady=0xb944) at WaitFor.c:350 #14 0x084cff54 in Dispatch () at dispatch.c:379 #15 0x084e763c in main (argc=2, argv=0xbe04, envp=0xbe10) at main.c:469 (gdb) bt full -7 #9 0x40199dd2 in select () from /lib/libc.so.6 No symbol table info available. #10 0x401f8550 in ?? () from /lib/libc.so.6 No symbol table info available. #11
Processed: Re: Bug#278863: XFree86 and matrox
Processing commands for [EMAIL PROTECTED]: reassign 278863 xserver-xfree86 Bug#278863: XFree86 and matrox Bug reassigned from package `xfree86' to `xserver-xfree86'. retitle 278863 xserver-xfree86: [mga] SEGV on G400 AGP rev 4 Bug#278863: XFree86 and matrox Changed Bug title. tag 278863 + moreinfo upstream Bug#278863: xserver-xfree86: [mga] SEGV on G400 AGP rev 4 There were no tags set. Tags added: moreinfo, upstream thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#278863: XFree86 and matrox
reassign 278863 xserver-xfree86 retitle 278863 xserver-xfree86: [mga] SEGV on G400 AGP rev 4 tag 278863 + moreinfo upstream thanks On Fri, Oct 29, 2004 at 09:44:38PM +0200, Caliminours wrote: Package: XFree86 Version: 4.1.0.1 Hi I have GUI troubleshooting since I have installed this package. I join the log file Thanks for your report. We need a little more information from you so that we can handle this bug. 1) Can you please mail [EMAIL PROTECTED] your /etc/X11/XF86Config-4 file? 2) Can you tell us if the X server crash happens immediately upon start, or can you use the X Window System for a little while before the crash happens? -- G. Branden Robinson| Mob rule isn't any prettier just Debian GNU/Linux | because you call your mob a [EMAIL PROTECTED] | government. http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Processed: Re: Bug#278928: xfonts-75dpi: swapped mixed-fixed arrow glyphs
Processing commands for [EMAIL PROTECTED]: reassign 278928 xfonts-base Bug#278928: xfonts-75dpi: swapped mixed-fixed arrow glyphs Bug reassigned from package `xfonts-75dpi' to `xfonts-base'. retitle 278928 xfonts-base: glyphs for codepoints U+2198 (SOUTH EAST ARROW) and U+2199 (SOUTH WEST ARROW) are swapped Bug#278928: xfonts-75dpi: swapped mixed-fixed arrow glyphs Changed Bug title. tag 278928 + upstream Bug#278928: xfonts-base: glyphs for codepoints U+2198 (SOUTH EAST ARROW) and U+2199 (SOUTH WEST ARROW) are swapped There were no tags set. Tags added: upstream thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: Re: Bug#278897: xterm: insert-selection(...) action breaks selection insertion
Processing commands for [EMAIL PROTECTED]: tag 278897 + moreinfo Bug#278897: xterm: insert-selection(...) action breaks selection insertion There were no tags set. Tags added: moreinfo thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
X Strike Force XFree86 SVN commit: r2012 - in trunk/debian: . local
Author: branden Date: 2004-11-04 12:32:38 -0500 (Thu, 04 Nov 2004) New Revision: 2012 Modified: trunk/debian/CHANGESETS trunk/debian/local/Xsession.5 trunk/debian/local/xfs.options.5 Log: Fix more minor manpage markup problems. + Round up another unescaped hyphen. + Use .PP macros in favor of literal blank lines. (The .nf directive means no fill, not no formatting.) Modified: trunk/debian/CHANGESETS === --- trunk/debian/CHANGESETS 2004-11-04 14:25:23 UTC (rev 2011) +++ trunk/debian/CHANGESETS 2004-11-04 17:32:38 UTC (rev 2012) @@ -219,7 +219,7 @@ 1973 Tidy up and make consistent all Debian-specific manpages. -1964, 2002 +1964, 2002, 2012 Use validate-posix-sh at build time to perform syntax check on generated maintainer scripts. Increase verbosity of validate-posix-sh warnings. Stop Modified: trunk/debian/local/Xsession.5 === --- trunk/debian/local/Xsession.5 2004-11-04 14:25:23 UTC (rev 2011) +++ trunk/debian/local/Xsession.5 2004-11-04 17:32:38 UTC (rev 2012) @@ -16,7 +16,7 @@ .\ the Debian operating system, in /usr/share/common-licenses/GPL; if .\ not, write to the Free Software Foundation, Inc., 59 Temple Place, .\ Suite 330, Boston, MA 02111-1307 USA -.TH Xsession 5 2004\-10\-31 Debian Project +.TH Xsession 5 2004\-11\-04 Debian Project .SH NAME Xsession \- initialize X session .SH SYNOPSIS @@ -256,13 +256,13 @@ .nf SYSMODMAP=/etc/X11/Xmodmap USRMODMAP=$HOME/.Xmodmap - +.PP if [ \-x /usr/bin/X11/xmodmap ]; then if [ \-f $SYSMODMAP ]; then xmodmap $SYSMODMAP fi fi - +.PP if [ \-x /usr/bin/X11/xmodmap ]; then if [ \-f $USRMODMAP ]; then xmodmap $USRMODMAP Modified: trunk/debian/local/xfs.options.5 === --- trunk/debian/local/xfs.options.52004-11-04 14:25:23 UTC (rev 2011) +++ trunk/debian/local/xfs.options.52004-11-04 17:32:38 UTC (rev 2012) @@ -15,7 +15,7 @@ .\ the Debian operating system, in /usr/share/common-licenses/GPL; if .\ not, write to the Free Software Foundation, Inc., 59 Temple Place, .\ Suite 330, Boston, MA 02111-1307 USA -.TH xfs.options 5 2004\-10\-31 Debian Project +.TH xfs.options 5 2004\-11\-04 Debian Project .SH NAME xfs.options \- configuration options for the X font server .SH DESCRIPTION @@ -56,7 +56,7 @@ .B xfs will be not be stopped or started during an upgrade of its package; the administrator will have to do so by hand (with -.B invoke-rc.d xfs restart +.B invoke\-rc.d xfs restart or by rebooting the system) before the newly installed .B xfs binary is used.
Bug#278897: xterm: insert-selection(...) action breaks selection insertion
tag 278897 + moreinfo thanks On Sat, Oct 30, 2004 at 03:47:03PM -0400, Thomas Dickey wrote: On Sat, Oct 30, 2004 at 06:17:14PM +0200, Vincent Lefevre wrote: I don't think all of the relevant documentation should be included, but it wasn't clear (for someone who doesn't know the internals of X) if these translations were specific to XTerm or were general to X resources. In the latter case, the man page could still point to the relevant documentation (which should be written if it doesn't exist yet). The translations resource is a feature of Xt (X Toolkits Intrinsics), and is also used in other code such as the Athena widgets. apropos Translations shows a place to start: XtAugmentTranslations XtParseTranslationTable (3) - manage translation tables Is this not a bug, then, but rather a misunderstanding of how translation table resources work? -- G. Branden Robinson|America is at that awkward stage. Debian GNU/Linux |It's too late to work within the [EMAIL PROTECTED] |system, but too early to shoot the http://people.debian.org/~branden/ |bastards. -- Claire Wolfe signature.asc Description: Digital signature
Processed: Re: Bug#279055: xfree86-common: Keyboard configuration FAQ has some typos and is not always clear enough
Processing commands for [EMAIL PROTECTED]: tag 279055 + moreinfo Bug#279055: xfree86-common: Keyboard configuration FAQ has some typos and is not always clear enough There were no tags set. Tags added: moreinfo thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: Re: Bug#279087: Fwd: X crashing
Processing commands for [EMAIL PROTECTED]: retitle 278654 xserver-xfree86: [ati/r128] problems with existing CCE idle fix Bug#278654: xserver-xfree86: [r128] Problems with existing CCE idle fix Changed Bug title. retitle 279087 xserver-xfree86: [ati/r128] X server hanging on Rage 128 RF/SG AGP Bug#279087: Fwd: X crashing Changed Bug title. severity 279087 important Bug#279087: xserver-xfree86: [ati/r128] X server hanging on Rage 128 RF/SG AGP Severity set to `important'. merge 278654 279087 Bug#278654: xserver-xfree86: [ati/r128] problems with existing CCE idle fix Bug#279087: xserver-xfree86: [ati/r128] X server hanging on Rage 128 RF/SG AGP Merged 278654 279087. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#277360: marked as done (xserver-xfree86: [ati/atimisc] SEGV when using XVideo on Rage Mobility P/M AGP 2x rev 100)
Your message dated Thu, 4 Nov 2004 13:10:58 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#277360: xserver-xfree86: [ati] server crash when trying to use the XVideo extension 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; 19 Oct 2004 18:13:46 + From [EMAIL PROTECTED] Tue Oct 19 11:13:46 2004 Return-path: [EMAIL PROTECTED] Received: from bal.lis.inpg.fr [195.220.21.15] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CJyUT-0008OS-00; Tue, 19 Oct 2004 11:13:46 -0700 Received: from smtpc.lis.inpg.Fr (smtpc.lis.inpg.fr [195.220.21.17]) by bal.lis.inpg.fr (Postfix) with ESMTP id 0147F3067CF for [EMAIL PROTECTED]; Tue, 19 Oct 2004 20:13:07 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by smtpc.lis.inpg.Fr (Postfix) with ESMTP id 963EC2C80F9 for [EMAIL PROTECTED]; Tue, 19 Oct 2004 20:13:07 +0200 (CEST) Received: from smtpc.lis.inpg.Fr ([127.0.0.1]) by localhost (smtpc.lis.inpg.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01379-01 for [EMAIL PROTECTED]; Tue, 19 Oct 2004 20:12:55 +0200 (CEST) Received: from irancy.lis.inpg.fr (irancy.lis.inpg.fr [195.220.21.167]) by smtpc.lis.inpg.Fr (Postfix) with ESMTP id 8AFA12C80EC for [EMAIL PROTECTED]; Tue, 19 Oct 2004 20:12:55 +0200 (CEST) Subject: xserver-xfree86: [ati] server crash when trying to use the XVideo extension From: Laurent Bonnaud [EMAIL PROTECTED] To: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1 Date: Tue, 19 Oct 2004 20:12:55 +0200 Message-Id: [EMAIL PROTECTED] Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at lis.inpg.fr Content-Transfer-Encoding: quoted-printable Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-5.1 required=4.0 tests=BAYES_44,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: xserver-xfree86 Version: 4.3.0.dfsg.1-8 Severity: important Hi, this system is a Fujitsu-Siemens Lifebook laptop with the ATI Rage Mobility chip listed below. With previous xserver-xfree86 versions, the XVideo extension was not available. With the current version it is listed among supported extensions by xdpyinfo. When I use mplayer with XVideo output (-vo xv option) the X11 server crashes and at the end of /var/log/XFree86.0.log.old, I see this: Fatal server error: Caught signal 11. Server aborting I don't know if this chip can be made to support the XVideo extension, but my guess is no and the X11 server should not activate it. -- Package-specific info: Contents of /var/lib/xfree86/X.roster: xserver-xfree86 /etc/X11/X target does not match checksum in /var/lib/xfree86/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 20 2000-12-08 20:26 /etc/X11/X - /usr/bin/X11/XF= ree86 -rwxr-xr-x 1 root root 1745484 2004-09-28 14:09 /usr/bin/X11/XFree86 Contents of /var/lib/xfree86/XF86Config-4.roster: xserver-xfree86 VGA-compatible devices on PCI bus: :01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobilit= y P/M AGP 2x (rev 64) /var/lib/xfree86/XF86Config-4.md5sum does not exist. XFree86 X server configuration file status: -rw-r--r-- 1 root root 2787 2003-12-17 15:18 /etc/X11/XF86Config-4 Contents of /etc/X11/XF86Config-4: ### BEGIN DEBCONF SECTION # XF86Config-4 (XFree86 server configuration file) generated by dexconf, = the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type man XF86Config-4 at the shell prompt.) # # If you want your changes to this file preserved by dexconf, only make c= hanges # before the ### BEGIN DEBCONF SECTION line above, and/or after the # ### END DEBCONF SECTION line below. # # To change things within the debconf section, run the command: # dpkg-reconfigure xserver-xfree86 # as root. Also see How do I add custom sections to a dexconf-generated # XF86Config or XF86Config-4 file? in /usr/share/doc/xfree86-common/FAQ.= gz. Section Files FontPathunix/:7100# local font serv= er # if the local font server has problems, we can fall back on thes= e FontPath/usr/lib/X11/fonts/Type1 FontPath/usr/lib/X11/fonts/CID
Bug#279087: Fwd: X crashing
retitle 278654 xserver-xfree86: [ati/r128] problems with existing CCE idle fix retitle 279087 xserver-xfree86: [ati/r128] X server hanging on Rage 128 RF/SG AGP severity 279087 important merge 278654 279087 thanks On Sun, Oct 31, 2004 at 04:40:22PM +0100, Silvério Santos wrote: Package: xserver-xfree86 [...] The error message from /var/log/XFree86.0.log.old in the last line is: (EE) R128(0): R128CCEWaitForIdle: (DEBUG) CCE idle took j = 0 Do you have a cure, as this is getting annoying, because it happens quite often? Could you also please answer with PM, as I do not follow the bug report lists (except for trouble shooting incidents to avoid RTFM answers) and I would prefer not to miss the solution. I suspect this issue is the same as #278654 URL: http://bugs.debian.org/278654 . In the future, please use reportbug to file bugs! The following form letter explains why. [The following is a form letter.] Dear bug submitter, Since the XFree86 X server is a large and complex piece of software, some more information is required of you before this bug can be handled. Please run the following commands from a shell prompt to gather and deliver this information to us: $ /usr/share/bug/xserver-xfree86 /tmp/output 31 $ mailx -s Re: Bug#279087 followup [EMAIL PROTECTED] /tmp/output If you do not have a mailx command on your system, you can get it by installing the mailx Debian package; for example, with the aptitude install mailx or apt-get install mailx commands as root. Alternatively, you can also use a mail command that is compatible with mailx's command-line syntax, such as mutt. One very good way to file bugs with the Debian Bug Tracking System is to use the reportbug package and command of the same name. The reportbug program does a lot of automatic information-gathering that helps package maintainers to understand your system configuration, and also ensures that your message to the Debian Bug Tracking System is well-formed so that it is processed correctly by the automated tools that manage the reports. (If you've ever gotten a bounce message from the Debian Bug Tracking System that tells you your message couldn't be processed, you might appreciate this latter feature.) Therefore, I strongly urge you to give reportbug a try as your primary bug reporting tool for the Debian System in the future. If you *did* use reportbug to file your report, then you're receiving this message because the information we expected to see was not present. If you deliberately deleted this information from the report, please don't do that in the future, even if it seems like it makes the mail too large. 50 kB (kilobytes) of configuration and log data is typical. Only if the included information greatly exceeds this amount (more than 100 kB) should you consider omitting it; instead, put it up on the World Wide Web somewhere and provide URLs to it in your report, or in subsequent followup by mailing [EMAIL PROTECTED]. Thank you! -- G. Branden Robinson| Intellectual property is neither Debian GNU/Linux | intellectual nor property. [EMAIL PROTECTED] | Discuss. http://people.debian.org/~branden/ | -- Linda Richman signature.asc Description: Digital signature
Bug#277309: xserver-xfree86: [nv] My X (and whole system) freeze/hangs, when scrolling program-menus or aterm etc.
On Mon, Oct 25, 2004 at 10:10:49PM +0200, Per Blomqvist wrote: I'm sorry to tell you this, but that delta (4.1.0-16woody4 to 4.3.0.dfsg.1-8) is so huge as to be useless for determining what precisely may have caused the regression. I'd like to request a couple more pieces of information: 1) Does turning XAA acceleration off prevent the problem from recurring? (Search for NoAccel in the XF86Config-4(5x) manual page.) NoAccel is in the nv manual, I use the default installed config file, with no options on that device. Are there any other bugreport that suspect exclusion of this option cause problem? (is it an option or not?) I don't understand your question. The nv(4x) manual page does document the NoAccel option, as does the XF86Config-4(5x) manual page. I am asking for this information because it will help obtain an answer to my question: Does turning XAA acceleration off prevent the problem from recurring?. If you add the specified option to the Device section of your XF86Config-4 file, XAA acceleration will be turned off. 2) Can you try various earlier versions in the 4.3.0.dfsg.1 release series to see if any of them rectify the problem? You can find these at snapshot.debian.net. Please start with the most recent prior to yours (-7) and work your way backwards. I often update my system, so.. the problem is in the latest version (4.3.0.dfsg.1-8). A little more description of the problem: If X didn't froze at first apps, it did froze within an hour, a stress test with an open aterm and just scroll dselect could cause it, also to froze. The problem have not reapeard since: I copied one single file nv_drv.o from the woody-relise (xserver-xfree86_4.1.0-16woody4_i386.deb), too the same path as the latest debian-sarge xserver-xfree86-4.3.0.dfsg.1-8 (that I still have installed). I didn't know about http://snapshot.debian.net though, I used http://packages.debian.org.. Okay. But as I said: I'm sorry to tell you this, but that delta (4.1.0-16woody4 to 4.3.0.dfsg.1-8) is so huge as to be useless for determining what precisely may have caused the regression. Even narrowing it down to just the one file (nv_drv.o), the nv driver itself has greatly changed in the interim from 4.1.0-16woody4 to 4.3.0.dfsg.1-8. If you could use versions of the xserver-xfree86 package from snapshot.debian.net to identify where the regression specifically took place, it would help us to track down this bug. Otherwise, we might not be able to resolve it. -- G. Branden Robinson|The best place to hide something is Debian GNU/Linux |in documentation. [EMAIL PROTECTED] |-- Ethan Benson http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Bug#279698: x-window-system and drm bug
Package: x-window-system Version: 4.3.0.dfsg.1-8 Hello, Every time I have a hardware reboot the machine (Dell with an i845 Extreme Graphics Accellerator) locks up. I am running kernel-image-2.4.27-1-686 and libc6 version 2.3.2.ds1-18. Oddly enough shutting the machine off and letting fsck remount the screwed up filesystem seems to fix the problem. It's locked up twice in a row the same way, and in just the same way trying to start it again has worked both times. I'm not going to be shutting it off much any more so I don't know how consistent that behavior will be... Also I am sure that it didn't start right after I got the new version of x-window-system going. Anyway, here are the relevent logs. I will also submit a report to the XFree people. Thanks, Eric Dickner /var/log/syslog ** Nov 4 13:02:19 javagate kernel: [drm] AGP 0.99 Aperture @ 0xe000 128MB Nov 4 13:02:19 javagate kernel: [drm] Initialized i830 1.3.2 20021108 on minor 0 Nov 4 13:02:19 javagate kernel: mtrr: base(0xe002) is not aligned on a size(0x18) boundary Nov 4 13:02:29 javagate kernel: [drm:i830_wait_ring] *ERROR* space: 130664 wanted 131064 Nov 4 13:02:29 javagate kernel: [drm:i830_wait_ring] *ERROR* lockup Nov 4 13:02:34 javagate kernel: [drm:i830_wait_ring] *ERROR* space: 128944 wanted 131064 Nov 4 13:02:34 javagate kernel: [drm:i830_wait_ring] *ERROR* lockup Nov 4 13:02:36 javagate kdm[435]: Abnormal helper termination, code 1, signal 0 Nov 4 13:02:36 javagate kdm[435]: fatal IO error 32 (Broken pipe) Nov 4 13:02:36 javagate kernel: mtrr: base(0xe002) is not aligned on a size(0x18) boundary Nov 4 13:02:41 javagate kernel: [drm:i830_wait_ring] *ERROR* space: 0 wanted 131064 Nov 4 13:02:41 javagate kernel: [drm:i830_wait_ring] *ERROR* lockup Nov 4 13:02:42 javagate kdm[452]: IO Error in XOpenDisplay Nov 4 13:02:42 javagate kdm[422]: Display :0 cannot be opened Nov 4 13:02:43 javagate kernel: mtrr: base(0xe002) is not aligned on a size(0x18) boundary /var/log/XFree86.0.log.old (**) Option dpms (**) I810(0): DPMS enabled (II) I810(0): X context handle = 0x0001 (II) I810(0): [drm] installed DRM signal handler (II) I810(0): [DRI] installation complete (II) I810(0): direct rendering: Enabled Error in I830WaitLpRing(), now is 2521, start is 520 pgetbl_ctl: 0xffe0001 pgetbl_err: 0x49 ipeir: 0 iphdr: 7d8e0001 LP ring tail: 0 head: 10 len: 1f001 start 0 eir: 0 esr: 10 emr: ff7b instdone: ffc1 instpm: 0 memmode: 0 instps: 424 hwstam: ier: 0 imr: iir: 0 space: 8 wanted 504 (II) I810(0): [drm] removed 1 reserved context for kernel (II) I810(0): [drm] unmapping 8192 bytes of SAREA 0xd0b76000 at 0x40018000
Bug#279716: xfree86-common: FAQ is called FAQ.xhtml.gz, but dhelp thinks it is FAQ.xhtml
Package: xfree86-common Version: 4.3.0.dfsg.1-8 Severity: minor Hi The Debian X FAQ's file name is /usr/share/doc/xfree86-common/FAQ.xhtml.gz. However according to /usr/share/doc-base/debian-x-faq, it is /usr/share/doc/xfree86-common/FAQ.xhtml (without gz). Because of this the Link to the FAQ in the documentation index of dhelp does not work. dwww is probably also affected. To correct this problem, either include an uncompressed version of the FAQ (I would prefer this, because it is easier to open with most web browsers), or change /usr/share/doc-base/debian-x-faq to match the real file name. best regards Andreas Janssen -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.9-custom Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] Versions of packages xfree86-common depends on: ii debconf 1.4.30.8 Debian configuration management sy ii debianutils 2.8.4 Miscellaneous utilities specific t -- debconf information: xfree86-common/experimental_packages:
Bug#278897: xterm: insert-selection(...) action breaks selection insertion
On 2004-11-04 12:29:21 -0500, Branden Robinson wrote: Is this not a bug, then, but rather a misunderstanding of how translation table resources work? Well, this is a bug in the documentation, which doesn't provide enough information. It wasn't even clear that XtAugmentTranslations or XtOverrideTranslations was used. The behavior is explained by the XtParseTranslationTable(3Xt) man page: [...] The XtAugmentTranslations function nondestructively merges the new translations into the existing widget translations. If the new trans- lations contain an event or event sequence that already exists in the widget's translations, the new translation is ignored. The XtOverrideTranslations function destructively merges the new trans- lations into the existing widget translations. If the new translations contain an event or event sequence that already exists in the widget's translations, the new translation is merged in and override the wid- get's translation. [...] IMHO, there should be a man page for Xresources / app-defaults. apropos says: nothing appropriate. Shouldn't this documentation (at least for the translations) be provided by the libxt6 package? In this case, the bug should be reassigned to it. Note that the XtParseTranslationTable(3Xt) man page is provided by libxt-dev, though the end user who wants to modify X resources doesn't necessarily have this dev package. I haven't seen a libxt-doc package either. -- Vincent Lefèvre [EMAIL PROTECTED] - Web: http://www.vinc17.org/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.org/blog/ Work: CR INRIA - computer arithmetic / SPACES project at LORIA
Bug#278897: xterm: insert-selection(...) action breaks selection insertion
On Thu, Nov 04, 2004 at 06:50:14PM +0100, Branden Robinson wrote: tag 278897 + moreinfo thanks On Sat, Oct 30, 2004 at 03:47:03PM -0400, Thomas Dickey wrote: On Sat, Oct 30, 2004 at 06:17:14PM +0200, Vincent Lefevre wrote: I don't think all of the relevant documentation should be included, but it wasn't clear (for someone who doesn't know the internals of X) if these translations were specific to XTerm or were general to X resources. In the latter case, the man page could still point to the relevant documentation (which should be written if it doesn't exist yet). The translations resource is a feature of Xt (X Toolkits Intrinsics), and is also used in other code such as the Athena widgets. apropos Translations shows a place to start: XtAugmentTranslations XtParseTranslationTable (3) - manage translation tables Is this not a bug, then, but rather a misunderstanding of how translation table resources work? yes (I think so). The manpages, by the way, don't contain a comprehensive discussion of the resource mechanism - that's in the files from the doc/specs tree. But my point here was that the manpages would show where to start finding the information - that's what I do if I find something about these which puzzles me. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgpqTyfIwmeca.pgp Description: PGP signature
