Re: Proposal on how to handle xorg include patches (WAS: Re: X Strike Force XOrg SVN commit: r28 - /)

2004-10-13 Thread Fabio Massimo Di Nitto

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Christoph Hellwig wrote:
| On Tue, Oct 12, 2004 at 09:20:21AM +0200, Fabio Massimo Di Nitto wrote:
|
|-BEGIN PGP SIGNED MESSAGE-
|Hash: SHA1
|
|X Strike Force SVN Repository Admin wrote:
|
|| +|
|| +|--  xorg-source-include   --  xorg-include
|
|Hi XSF,
|~  as you might have noticed, we started (at low priority) working on
|X.org packages.
|
|The commits you are seeing now are only the proof of concept that we
|will use to split the tree in a sort of modularized way, using an
|approach close to the way in which our Debian kernel is packaged.
|There are some differences, but at this point in time, until the concept
|is not proved to be working, are somehow irrelevant.
|
|
| Note that the -source vs -image package in the kernel are an sbolute
| maintaine horror, I would strongly advice against repeating that
| mistake.
|
|

The main reason why we are using this approach is because X doesn't
evolve as fast as the kernel and it is the only way at the moment to
simulate X.org modularized tree.

In this way each time a package gain its own independency, it will be
dropped silently from the -source- package and a new version of
independent-source orig.tar.gz will be uploaded. The good thing is
that all of this can be done without ftp-master manual intervention
(other than the first package approval).

Fabio

- --
user fajita: step one
fajita Whatever the problem, step one is always to look in the error log.
user fajita: step two
fajita When in danger or in doubt, step two is to scream and shout.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBbKgxhCzbekR3nhgRAoMIAJ0bsJ7j907oHjWHtbx4v9ACkjVInQCfUB6j
nKjErse8HeY8gLaa1FuQ6A8=
=hnD6
-END PGP SIGNATURE-



未承諾広 告※5 000円で開業 !人生変 えません か!!

2004-10-13 Thread redriver007jp
  
販売者  NetLake  
代表者 小笠原 耀子
所在地 京都市西京区下津林番条100−1
電話0774-56-6428 
受信拒否の方は下記のURLか又はHPよりお願いいたします  
  http://lookfor.etowns.net/scripts/deleteform.html  
  http://maillake.minidns.net/scripts/deleteform.html

 9月に集めた100万メールをサービス中!
サイドビジネスの決定版です! 
時流に乗るビジネスは必ず成功します。
成せばなる!成さねばならぬ何事も!
行動に移すか否かです。資本金は5000円!
人間地道な努力が一番大事です。
あなたの人生変わりますよ! 
後はあなたの決断しだいです!
  
http://lookfor.etowns.net/
http://maillake.minidns.net/ 
  







  



Processed: tagging 234085

2004-10-13 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.8.5
  # fixed bugs don't require more information
 tags 234085 - moreinfo
Bug#234085: xlibs: [xkb] aring, oslash, and ae keys don't work on Danish Happy 
Hacking keyboard
Tags were: moreinfo upstream
Tags removed: moreinfo


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)



Re: Bug#272493: DSA and sid uploads needed (was: Re: Bug#272493: libxpm4: Three exploitable overflows in XPM handling)

2004-10-13 Thread Branden Robinson
On Mon, Sep 20, 2004 at 06:48:28AM -0700, Daniel Stone wrote:
 On Mon, Sep 20, 2004 at 02:02:11PM +0200, Moritz M??hlenhoff wrote:
  There are three exploitable stack and integer overflows in the
  XPM handling code shipped with XFree: Full details can be found
  in this advisory from Chris Evans which I copied at the end of
  this mail for archival purposes.
 
 Branden Robinson has the patch and is handling the DSA for woody; I
 understnad he is also handling the 4.3 upload for sid.  Branden?

For the sake of posterity (read: the mailing list archives), Fabio and I
agreed that he would handle sid in this situation.

-- 
G. Branden Robinson|   The software said it required
Debian GNU/Linux   |   Windows 3.1 or better, so I
[EMAIL PROTECTED] |   installed Linux.
http://people.debian.org/~branden/ |


signature.asc
Description: Digital signature


Processed: Re: Bug#272280: xbase-clients: [xset] Document and make default mouse acceleration that doesn't suck

2004-10-13 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 retitle 272280 xserver-xfree86: [mouse] change acceleration default to 
 something that 'doesn't suck'
Bug#272280: xbase-clients: [xset] Document and make default mouse acceleration 
that doesn't suck
Changed Bug title.

 reassign 272280 xserver-xfree86
Bug#272280: xserver-xfree86: [mouse] change acceleration default to something 
that 'doesn't suck'
Bug reassigned from package `xbase-clients' to `xserver-xfree86'.

 severity 272280 wishlist
Bug#272280: xserver-xfree86: [mouse] change acceleration default to something 
that 'doesn't suck'
Severity set to `wishlist'.

 tag 272280 + upstream moreinfo
Bug#272280: xserver-xfree86: [mouse] change acceleration default to something 
that 'doesn't suck'
There were no tags set.
Tags added: upstream, moreinfo

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)



Bug#272280: xbase-clients: [xset] Document and make default mouse acceleration that doesn't suck

2004-10-13 Thread Branden Robinson
retitle 272280 xserver-xfree86: [mouse] change acceleration default to 
something that 'doesn't suck'
reassign 272280 xserver-xfree86
severity 272280 wishlist
tag 272280 + upstream moreinfo
thanks

On Sat, Sep 18, 2004 at 07:15:25PM -0400, Dylan Thurston wrote:
 Package: xbase-clients
 Version: 4.3.0.dfsg.1-7
 Severity: minor
 
 The default mouse acceleration on a new X install is abysmal.  Please
 document and make default the xset options to make it not suck.  See
 
 http://marc.theaimsgroup.com/?l=xfree-xpertm=101624642005523w=2

I don't get many bug reports about mouse acceleration -- in fact, yours is
the first I can recall -- so I suspect that you are in a minority in
feeling that the default mouse acceleration parameters suck.

That, or something unusual is going on in your particular configuration.

When you first launch the X server, what mouse acceleration is reported?

You can find out by running xset q.  For example, I get:

Pointer Control:
  acceleration:  20/10threshold:  4

...which works satisfactorily for me.

-- 
G. Branden Robinson|   The Bible is probably the most
Debian GNU/Linux   |   genocidal book ever written.
[EMAIL PROTECTED] |   -- Noam Chomsky
http://people.debian.org/~branden/ |


signature.asc
Description: Digital signature


Re: Xsession doesn't use umask setting from /etc/login.defs

2004-10-13 Thread Branden Robinson
[Redirecting to debian-devel; followups set.]

On Mon, Sep 20, 2004 at 02:29:32PM +0200, Wouter Hanegraaff wrote:
 Hi,
 
 After a fresh sarge install, I'm having problems with umask settings. In
 /etc/login.defs I set umask to 002, and that works for logging in on the
 console or remote via ssh. However, if I use {g,x,k}dm I keep getting an
 umask of 022, because Xsession is started by the display manager which
 has a default umask of 022.
 
 It seems that Xsession doesn't change the UMASK at all. Should it do so?
 If not, which program should set the umask during a graphical login?

Good question.

debian-devel folks, what do you think?  I'm having difficulty deciding how
to think about this issue.

/etc/login.defs explicitly indicates that it is Configuration control
definitions for the login package, and many of its parameters are
inapplicable to display managers, or already implemented in parallel (e.g.,
how long do wait after a failed login before displaying the prompt/greeter
again?).

By analogy, /etc/environment is a PAM thing and should only be dealt with
by PAM.  (We can't use it anyway since the umask is not an environment
variable.)

* What's the path of least resistance?
* What would violate user expectations the least?
* What would be a good ideal approach, if code changes weren't an issue?

-- 
G. Branden Robinson| You could wire up a dead rat to a
Debian GNU/Linux   | DIMM socket and the PC BIOS memory
[EMAIL PROTECTED] | test would pass it just fine.
http://people.debian.org/~branden/ | -- Ethan Benson


signature.asc
Description: Digital signature


Re: mtrr and ati-radeon

2004-10-13 Thread Branden Robinson
On Mon, Sep 20, 2004 at 08:08:46AM -0700, Jim McCloskey wrote:
 Hello. My question concerns xserver-common 4.3.0.dfsg.1-4 from Debian
 testing.

Anyone know anything about MTRRs (beyond the basic concept)?  This is far
enough beyond my ken that I can't meaningfully answer this gentleman.

-- 
G. Branden Robinson|Those who fail to remember the laws
Debian GNU/Linux   |of science are condemned to
[EMAIL PROTECTED] |rediscover some of the worst ones.
http://people.debian.org/~branden/ |-- Harold Gordon


signature.asc
Description: Digital signature


Processed: Re: Bug#272496: [radeon] resume fails on iBook2

2004-10-13 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 retitle 272496 xserver-xfree86: [ati/radeon] power resume fails on iBook with 
 Radeon Mobility M7 LW [regression from 4.3.0.dfsg.1-4]
Bug#272496: [radeon] resume fails on iBook2
Changed Bug title.

 tag 272496 + upstream moreinfo
Bug#272496: xserver-xfree86: [ati/radeon] power resume fails on iBook with 
Radeon Mobility M7 LW [regression from 4.3.0.dfsg.1-4]
There were no tags set.
Tags added: upstream, moreinfo

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)



Re: X Strike Force XFree86 SVN commit: r1832 - in trunk/debian: . local

2004-10-13 Thread Branden Robinson
On Mon, Sep 20, 2004 at 11:08:49PM +0200, Denis Barbier wrote:
 True, I will try to improve wording here.

Are you happy with the current FAQ entry?  If I'm saying anything
misleading in it, please let me know.  I don't want to ship a FAQ in sarge
with bad information in it.

 No, in my bogus terminology, position means the group number.

Okay.  I *think* I understand.  Would the follwing symbol definition
reflect an accurate notion of what a group is (assuming my bogus keysyms
actually existed)?

xkb_symbols foo {

name[Group1] = FirstGroup
name[Group2] = SecondGroup
name[Group3] = ThirdGroup
name[Group4] = FourthGroup

key AE01 = { [ UnshiftedGroup1, ShiftedGroup1 ],
   [ UnshiftedGroup2, ShiftedGroup2 ],
   [ UnshiftedGroup3, ShiftedGroup3 ],
   [ UnshiftedGroup4, ShiftedGroup4 ] }
}

-- 
G. Branden Robinson|Men use thought only to justify
Debian GNU/Linux   |their wrong doings, and speech only
[EMAIL PROTECTED] |to conceal their thoughts.
http://people.debian.org/~branden/ |-- Voltaire


signature.asc
Description: Digital signature


Bug#272496: [radeon] resume fails on iBook2

2004-10-13 Thread Branden Robinson
retitle 272496 xserver-xfree86: [ati/radeon] power resume fails on iBook with 
Radeon Mobility M7 LW [regression from 4.3.0.dfsg.1-4]
tag 272496 + upstream moreinfo
thanks

On Mon, Sep 20, 2004 at 02:12:18PM +0200, Christoph Hellwig wrote:
 Package: xserver-xfree86  
   
 Version: 4.3.0.dfsg.1-7
 
 When suspending my iBook the resume fails after resuming the sungem
 ethernet if I had been running X when suspending.  Not runing X or
 downgrading to xserver-xfree86-4.3.0.dfsg.1-4 from testing fixes the
 problem.
 
 This is running various 2.6 kernels (kernel-image-2.6.8 from debian,
 various homegrown recent 2.6 kernels).  lspci output below:
[...]
 :00:10.0 VGA compatible controller: ATI Technologies Inc Radeon
 Mobility M7 LW [Radeon Mobility 7500]

I don't experience any such problem on my iBook, but:

* I run kernel 2.4.
* I have an older iBook with a Radeon Mobility M3.

Can you try kernel 2.4.27 and see if that works around the problem?  I don't
insist that you stay with that kernel -- I just want to know if it affects
this bug.

Also, please see the following:

[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#272496 [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| I'm not going to waste my precious
Debian GNU/Linux   | flash memory with Perl when I can
[EMAIL PROTECTED] | do so much more with it.
http://people.debian.org/~branden/ | -- Joey Hess


signature.asc
Description: Digital signature


Re: your mail

2004-10-13 Thread Branden Robinson
On Mon, Sep 20, 2004 at 11:47:41PM +0200, Pascal Boulanger wrote:
 y dont want you in my computer OK GO HOME STUPID BOYS  Y DONT WANT TO AVE YOU
 IN MY COMPUTER
 CRASY  BANDITOS   I WOUD LIKE TO KIL YOU

This prick is lucky I've been behind on debian-x mail.

:-P

-- 
G. Branden Robinson|Those who fail to remember the laws
Debian GNU/Linux   |of science are condemned to
[EMAIL PROTECTED] |rediscover some of the worst ones.
http://people.debian.org/~branden/ |-- Harold Gordon


signature.asc
Description: Digital signature


Processed: retitle 272661 to xfree86-common: want Xsession to use umask setting from /etc/login.defs ...

2004-10-13 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.8.5
 retitle 272661 xfree86-common: want Xsession to use umask setting from 
 /etc/login.defs
Bug#272661: xfree86-common: Xsession doesn't use UMASK settings from 
/etc/login.defs
Changed Bug title.

 severity 272661 wishlist
Bug#272661: xfree86-common: want Xsession to use umask setting from 
/etc/login.defs
Severity set to `wishlist'.


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)



Bug#216933: Compiling XFree86 4.3.0 with -O0 seems to be a workaround

2004-10-13 Thread Branden Robinson
On Tue, Sep 21, 2004 at 06:51:18PM +1000, Chris Lange wrote:
 I've compiled XFree86 4.3.0 with the following compiler flags,
 -march=i386 -mcpu=i386 -O0 -fomit-frame-pointer -finline-functions,
 and my system has now been running without a hitch for 19 days (i was
 usually getting the BadLength error after only 2 to 4 hours after
 every reboot when using the stock Fedora XF86 rpms).
 
 NB: Around the code at line 241 of
 XFree86-4.3.0/xc/extras/Mesa/src/glapi.c I had to comment out the
 following in order to successfully compile with -O0 (gcc was complaining
 about running out of registers): 
 
 /*
 if (use_cmpxchg8b)
 for (p = _gl_entrypoint_templ + 4; p  _gl_end_table; p += 4) {
 __asm __volatile (lock; cmpxchg8b %0
 : =m (p[0]), =m (p[1]), =a (tmp1), =d (tmp2)
 : m (p[0]), m (p[1]), a (p[0]), d (p[1]),
 b (_gl_entrypoint_templ[0]),
 c (c | (p[1]  0x))
 : cc);
 }
 */

Huh.  I'm not aware that this caused gcc warnings anywhere.  Maybe it only
does so on Crusoe chips?

-- 
G. Branden Robinson| Religion is nonsense.
Debian GNU/Linux   | It's also a gold mine --
[EMAIL PROTECTED] | if you know where to dig.
http://people.debian.org/~branden/ | -- _Shine_


signature.asc
Description: Digital signature


Re: could install display manager without x-window-system

2004-10-13 Thread Branden Robinson
On Mon, Oct 04, 2004 at 11:31:00PM +0800, Dan Jacobson wrote:
 I was helping a friend install woody.  I noticed one could install
 xdm, kdm, gdm, wdm, all without installing x-window-system or perhaps
 x-window-system-core. Needless to say, we didn't get very far that
 day. Is that normal? Shouldn't there be some dependencies?

Have you read the package descriptions of x-window-system and
x-window-system core?

-- 
G. Branden Robinson|
Debian GNU/Linux   |   If ignorance is bliss,
[EMAIL PROTECTED] |   is omniscience hell?
http://people.debian.org/~branden/ |


signature.asc
Description: Digital signature


Bug#276269: backtrace

2004-10-13 Thread Tormod Volden
I finally found the core dump in /etc/X11. I had been looking in $PWD 
and / and $HOME, searched the /var and /tmp and /root trees...



# gdb /usr/X11R6/bin/XFree86-debug /etc/X11/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/

tls/libthread_db.so.1.

Core was generated by `/usr/bin/X11/X -dpi 100 -nolisten tcp'.
Program terminated with signal 11, Segmentation fault.
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  0x0838edc6 in XAAMoveDWORDS (dest=0x402a92f0, src=0x41400ff6, dwords=3)
   at xaaImage.c:58
58  xaaImage.c: No such file or directory.
   in xaaImage.c
(gdb) bt  
#0  0x0838edc6 in XAAMoveDWORDS (dest=0x402a92f0, src=0x41400ff6, dwords=3)

   at xaaImage.c:58
#1  0x0838f5fb in XAAWritePixmap (pScrn=0x8b6e5f8, x=0, y=0, w=381, h=0,
   src=0x41400d06 , srcwidth=768, rop=3, planemask=4294967295, trans=-1,
   bpp=16, depth=16) at xaaImage.c:277
#2  0x0837f5a5 in XAADoImageWrite (pSrc=0x8b70ee8, pDst=0x8bc38b8,
   pGC=0x8cca058, prgnDst=0xb710, pptSrc=0xb6a8) at 
xaaCpyArea.c:216
#3  0x0837eb7e in XAABitBlt (pSrcDrawable=0x8b70ee8, 
pDstDrawable=0x8bc38b8,

   pGC=0x8cca058, srcx=3, srcy=35, width=381, height=349, dstx=0, dsty=0,
   doBitBlt=0x837f457 XAADoImageWrite, bitPlane=0) at xaaBitBlt.c:201
#4  0x0837ef12 in XAACopyArea (pSrcDrawable=0x8b70ee8, 
pDstDrawable=0x8bc38b8,

   pGC=0x8cca058, srcx=3, srcy=35, width=381, height=349, dstx=0, dsty=0)
   at xaaCpyArea.c:53
#5  0x0863b69f in miSpriteCopyArea (pSrc=0x8b70ee8, pDst=0x8bc38b8,
   pGC=0x8cca058, srcx=3, srcy=35, w=381, h=349, dstx=0, dsty=0)
   at misprite.c:1190
#6  0x08642283 in fbShmPutImage (dst=0x8bc38b8, pGC=0x8cca058, depth=16,
   format=2, w=384, h=384, sx=3, sy=35, sw=381, sh=349, dx=0, dy=0,
   data=0x413b9000 ) at shm.c:546
#7  0x08643afb in ProcShmPutImage (client=0x8cc8958) at shm.c:875
#8  0x08644888 in ProcShmDispatch (client=0x8cc8958) at shm.c:1108
#9  0x084de350 in Dispatch () at dispatch.c:450
#10 0x084f58c4 in main (argc=5, argv=0xbdc4, envp=0xbddc) at 
main.c:469


(gdb) bt full -7
#4  0x0837ef12 in XAACopyArea (pSrcDrawable=0x8b70ee8, 
pDstDrawable=0x8bc38b8,

   pGC=0x8cca058, srcx=3, srcy=35, width=381, height=349, dstx=0, dsty=0)
   at xaaCpyArea.c:53
   infoRec = 0x8b9c0a8
#5  0x0863b69f in miSpriteCopyArea (pSrc=0x8b70ee8, pDst=0x8bc38b8,
   pGC=0x8cca058, srcx=3, srcy=35, w=381, h=349, dstx=0, dsty=0)
   at misprite.c:1190
   rgn = 0x8b70ee8
   pScreenPriv = 0x8b71bc8
   pGCPrivate = 0x8cca100
   oldFuncs = (GCFuncs *) 0x8aea480
#6  0x08642283 in fbShmPutImage (dst=0x8bc38b8, pGC=0x8cca058, depth=16,
   format=2, w=384, h=384, sx=3, sy=35, sw=381, sh=349, dx=0, dy=0,
   data=0x413b9000 ) at shm.c:546
   pPixmap = 0x8b70ee8
#7  0x08643afb in ProcShmPutImage (client=0x8cc8958) at shm.c:875
   pGC = 0x8cca058
   pDraw = 0x8bc38b8
   length = 768
   shmdesc = 0x8cc8350
   stuff = (xShmPutImageReq *) 0x8ccb1d8
#8  0x08644888 in ProcShmDispatch (client=0x8cc8958) at shm.c:1108
   stuff = (xReq *) 0x0
---Type return to continue, or q return to quit---
#9  0x084de350 in Dispatch () at dispatch.c:450
   clientReady = (int *) 0xb904
   result = 40
   client = 0x8cc8958
   nready = 0
   icheck = (HWEventQueuePtr *) 0x8b55bc8
   start_tick = 6520
#10 0x084f58c4 in main (argc=5, argv=0xbdc4, envp=0xbddc) at 
main.c:469

   i = 1
   j = 2
   k = 2
   error = -1073742396
   xauthfile = 0xbfcf /root/.Xauthority
   alwaysCheckForInput = {0, 1}
(gdb)




Bug#272661: xfree86-common: Xsession doesn't use UMASK settings from /etc/login.defs

2004-10-13 Thread Branden Robinson
On Tue, Sep 21, 2004 at 12:33:55PM +0200, Wouter Hanegraaff wrote:
 Package: xfree86-common
 Version: 4.3.0.dfsg.1-4
 Severity: normal
 
 In /etc/login.defs I set umask to 002, and that works for logging in on
 the console or remote via ssh. However, if I use {g,x,k}dm I keep
 getting an umask of 022, because Xsession is started by the display
 manager which has a default umask of 022. 
 
 It seems that Xsession doesn't change the UMASK at all. I think it
 should inherit the values from /etc/login.defs. But maybe this should be
 done by the display manager, in which case this bug applies to {g,k,x}dm
 and whatever other display managers Debian provides.

I don't think there is an obviously correct solution to this problem, so I
have submitted it to the debian-devel mailing list for discusson.

-- 
G. Branden Robinson|Lowery's Law:
Debian GNU/Linux   |If it jams -- force it.  If it
[EMAIL PROTECTED] |breaks, it needed replacing anyway.
http://people.debian.org/~branden/ |


signature.asc
Description: Digital signature


Bug#272115: /usr/X11R6/bin/xedit: Xedit crashes when language is set to tr_TR

2004-10-13 Thread ismail dönmez
It crashes on startup. 

Regards,
ismail


On Tue, 12 Oct 2004 20:00:26 -0500, Branden Robinson [EMAIL PROTECTED] wrote:
 retitle 272115 xbase-clients: [xedit] crashes with 'nowhere to longjmp' 
 message when LANG=tr_TR.UTF-8
 tag 272115 + upstream moreinfo
 thanks
 
 On Fri, Sep 17, 2004 at 05:22:59PM +0300, ismail donmez wrote:
  Package: xbase-clients
  Version: 4.3.0.dfsg.1-7
  Severity: important
  File: /usr/X11R6/bin/xedit
 
  Here it goes :
 
  [EMAIL PROTECTED]:~$ xedit
  *** DEFUN BUTLAST: OPTiONAL not allowed/implemented
  *** Fatal: nowhere to longjmp.
  İptal edildi
 
  But :
 
  [EMAIL PROTECTED]:~$ LC_ALL=POSIX xedit
 
  works fine.
 
  looks like a locale problem in turkish where toupper(i) is
  I-with-a-dot-above .
 
 Thanks for your report.  I'm sorry it has taken a little while to get back
 to you.
 
 Do you experience this problem when typing the character into the Text
 widget, when pasting it, or both?
 
 Either way, the problem appears to involve xc/programs/xedit/lisp/lisp.c.
 
 --
 G. Branden Robinson|   Convictions are more dangerous
 Debian GNU/Linux   |   enemies of truth than lies.
 [EMAIL PROTECTED] |   -- Friedrich Nietzsche
 http://people.debian.org/~branden/ |
 
 
 


-- 
Time is what you make of it




Bug#276234: xterm lost $HOME/bin and $TMPDIR

2004-10-13 Thread Thomas Dickey
On Tue, Oct 12, 2004 at 10:20:10PM +0200, Michelle Konzack wrote:
 Package: xterm
 Version: 4.1.0-16woody3
 Severity: normal
 
 Error description:
 
 I have in my ~/.bash_profile and in ~/.xsession the line 
 
 export PATH=$HOME/bin/:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R5/bin

perhaps xterm isn't being run as a login shell:

 ~/.bash_profile
  The personal initialization file,  executed  for  login
  shells

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net


pgpOKWNo5SVIU.pgp
Description: PGP signature


Bug#276234: xterm lost $HOME/bin and $TMPDIR

2004-10-13 Thread Michelle Konzack
Am 2004-10-13 05:41:37, schrieb Thomas Dickey:
 On Tue, Oct 12, 2004 at 10:20:10PM +0200, Michelle Konzack wrote:
  Package: xterm
  Version: 4.1.0-16woody3
  Severity: normal
  
  Error description:
  
  I have in my ~/.bash_profile and in ~/.xsession the line 
  
  export PATH=$HOME/bin/:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R5/bin
 
 perhaps xterm isn't being run as a login shell:

It was every time working...
Since the last update I can not use my ~/bin anymore.

I was switching from xserver from WOODY 3.0r0 to 4.1.0-16woody1
and now to Version: 4.1.0-16woody3 which does not more work
since five of six month.

I have had to rewrite all 180 BASH Scripts which was working bevore

For my Devel-Workststion I have WOODY as the base installed and the
chroots to WOODY, SARGE and SID. 

I have a fresh WOODY installation from CD 3.0r0 and it is working. 
After updating it stops to Work.

Oh yes, $HOME is availlable in fvwm and normaly xterm get it from
the invoiking Application so if I start an application like:

Exec xterm -e myprogram

myprogram does atart correctly from the $HOME/bin bot does
not know anything about $HOME.

This is probably an error and stops programs of working.

If I start my probrams like 

Exec exec myprogram

it works fine, because fvwm spans a non-login-shell which have
the $HOME because it get it from fvwm.

The Error above is only in '(u)xterm' and not in 'mlterm' or 'eterm'

Greetings
Michelle

-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/ 
Michelle Konzack   Apt. 917  ICQ #328449886
   50, rue de Soultz MSM LinuxMichi
0033/3/8845235667100 Strasbourg/France   IRC #Debian (irc.icq.com)


signature.pgp
Description: Digital signature


Bug#276234: xterm lost $HOME/bin and $TMPDIR

2004-10-13 Thread Thomas Dickey
On Wed, Oct 13, 2004 at 12:30:20PM +0200, Michelle Konzack wrote:
 Am 2004-10-13 05:41:37, schrieb Thomas Dickey:
  On Tue, Oct 12, 2004 at 10:20:10PM +0200, Michelle Konzack wrote:
   Package: xterm
   Version: 4.1.0-16woody3
   Severity: normal
   
   Error description:
   
   I have in my ~/.bash_profile and in ~/.xsession the line 
   
   export PATH=$HOME/bin/:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R5/bin
  
  perhaps xterm isn't being run as a login shell:
 
 It was every time working...
 Since the last update I can not use my ~/bin anymore.

But if xterm is not run as a login shell, it won't read the ~/.bash_profile,
and also (for a few years) setuid processes (xterm is one) will have their
environment mashed to exclude customizations such as this.
 
 The Error above is only in '(u)xterm' and not in 'mlterm' or 'eterm'

xterm runs setuid to update utmp.
Some of the other terminals don't do this.

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net


pgpEwcFWxL8TZ.pgp
Description: PGP signature


Bug#276234: xterm lost $HOME/bin and $TMPDIR

2004-10-13 Thread Thomas Dickey
  perhaps xterm isn't being run as a login shell:

by the way -

Changing xterm's behaviour doesn't rely upon scripting

man xterm (resource setting)

 loginShell (class LoginShell)
 Specifies whether or not the shell to be run in  the
 window  should  be  started  as  a login shell.  The
 default is ``false.''
-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net


pgpBujICRwUQ6.pgp
Description: PGP signature


Bug#261993:

2004-10-13 Thread Teemu Ikonen
On 08/10/04 18:08, Branden Robinson wrote:
 Can you tell us specifically which modes cause this infinite loop?

Sure. Using the wmres program mentioned previosly on this bug, I determined
that all modes with dotclock less than 17750 cause the crash, i.e. these
modes crash:

320x240 150Hz EXEC ./wmres 320 240 15750
320x240 145Hz EXEC ./wmres 320 240 15750
320x240 120Hz EXEC ./wmres 320 240 12600
320x200 170Hz EXEC ./wmres 320 200 15750
320x175 170Hz EXEC ./wmres 320 175 15750

But this doesn't:

360x200 170Hz EXEC ./wmres 360 200 17750

Teemu




Bug#263952: Pointers and Scale are invisible on secondary XINERAMA screens

2004-10-13 Thread Jan-Benedict Glaw
On Wed, 2004-10-13 00:24:44 -0400, Michel Dänzer [EMAIL PROTECTED]
wrote in message [EMAIL PROTECTED]:
 On Tue, 2004-10-12 at 15:43 +0200, Jan-Benedict Glaw wrote:
  On Wed, 2004-09-01 04:55:17 -0500, Branden Robinson [EMAIL PROTECTED]
  wrote in message [EMAIL PROTECTED]:
  I guess (but of course I'm not sure -- I'm not a X11 / XFree86 guru...)
  this means that the used widget library contains a bug. I guess it's
  responsible for providing the xwd dump data, but not the hardware
  driver...

 This is likely a driver bug; to most other components involved it
 matters little if at all which screen xclock is on. So, please provide
 the information about your setup that Branden asked for in his first
 followup.

Here we are:

Contents of /var/lib/xfree86/X.roster:
xserver-xfree86

/etc/X11/X target unchanged from checksum in /var/lib/xfree86/X.md5sum.

X server symlink status:
lrwxrwxrwx  1 root root 20 Aug  3 17:51 /etc/X11/X - /usr/bin/X11/XFree86
-rwxr-xr-x  1 root root 1745484 Sep 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 RV280 [Radeon 9200 
SE] (rev 01)
:02:09.0 VGA compatible controller: ATI Technologies Inc 3D Rage II+ 215GTB 
[Mach64 GTB] (rev 9a)
:02:0a.0 VGA compatible controller: ATI Technologies Inc 3D Rage II+ 215GTB 
[Mach64 GTB] (rev 9a)

/etc/X11/XF86Config-4 does not match checksum in 
/var/lib/xfree86/XF86Config-4.md5sum.

XFree86 X server configuration file status:
-rw---  1 root root 5475 Aug  4 12:25 /etc/X11/XF86Config-4

Contents of /etc/X11/XF86Config-4:
# XF86Config-4 (XFree86 X Window System server configuration file)
#
# This file was 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.)
#
# This file is automatically updated on xserver-xfree86 package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xfree86
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following commands as root:
#
#   cp /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.custom
#   md5sum /etc/X11/XF86Config-4  /var/lib/xfree86/XF86Config-4.md5sum
#   dpkg-reconfigure xserver-xfree86
Section Files
FontPathunix/:7100# local font server
# if the local font server has problems, we can fall back on these
FontPath/usr/lib/X11/fonts/misc
FontPath/usr/lib/X11/fonts/cyrillic
FontPath/usr/lib/X11/fonts/100dpi/:unscaled
FontPath/usr/lib/X11/fonts/75dpi/:unscaled
FontPath/usr/lib/X11/fonts/Type1
FontPath/usr/lib/X11/fonts/CID
FontPath/usr/lib/X11/fonts/Speedo
FontPath/usr/lib/X11/fonts/100dpi
FontPath/usr/lib/X11/fonts/75dpi
EndSection
Section Module
LoadGLcore
Loadbitmap
Loaddbe
Loadddc
Loaddri
Loadextmod
Loadfreetype
Loadglx
Loadint10
Loadrecord
Loadspeedo
Loadtype1
Loadvbe
EndSection
Section InputDevice
Identifier  Generic Keyboard
Driver  keyboard
Option  CoreKeyboard
Option  XkbRules  xfree86
Option  XkbModel  pc105
Option  XkbLayout de
Option  XkbVariantnodeadkeys
EndSection
Section InputDevice
Identifier  Configured Mouse scroll
Driver  mouse
Option  CorePointer
Option  Device/dev/psaux
Option  Protocol  ImPS/2
Option  Emulate3Buttons   true
Option  ZAxisMapping  4 5
EndSection

Section InputDevice
Identifier  Configured Mouse noscroll
Driver  mouse
Option  Device/dev/ttyS0
Option  Protocol  Microsoft
Option  Emulate3Buttons   true
Option  ZAxisMapping  4 5
Option  SendCoreEvents
EndSection

Section Device
Identifier  Generic Video Card mitte
Driver  ati
BusID   PCI:1:0:0
EndSection
Section Device
Identifier  Generic Video Card links
Driver  ati
BusID   PCI:2:9:0
EndSection
Section Device
Identifier  Generic Video Card rechts
Driver  ati
BusID   PCI:2:10:0
EndSection
Section Monitor
Identifier  Generic Monitor links
HorizSync   30-70
VertRefresh 50-160
Option  DPMS
EndSection

Bug#276345: copy-paste troubles with the first line of a less

2004-10-13 Thread Loïc Minier
Package: xterm
Version: 4.3.0.dfsg.1-8
Severity: normal

 Hi,

 It's been some months now that I repeatedly get a strange problem with
 a less in xterm:  if I select the first line of the xterm window, being
 the first line of the less dump too, I am pasting some sort of buffered
 data too, coming from previous lines of output.

 Say I have done a grep -r foo bar | less, and copy-paste the first
 line of the xterm (bar/xyz.c: ...), I get what I've selected plus
 some preprended text (blahblahbar/xyz.c: ...).  This happens when I
 select one or multiple lines or one or multiple words including the
 upper left word in the less in xterm.  It DOESN'T happen when I select
 character-wise (single-clicking instead of double- or triple-clicking).

 I can't reproduce deterministically but once I get it, it always happen
 with the same display.  Restarting the less usually clears things up.

 I think I already got the problem with vim a while ago, but I'm not
 copy-pasting so much from vim, either to it.

 I believe it's a but in the copy-paste word selection of xterm wich
 doesn't check if the characters selected are displayed and goes out of
 bound, but I can believe it is caused by improper terminal handling by
 less.


-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED]

Versions of packages xterm depends on:
ii  libc6 2.3.2.ds1-17   GNU C Library: Shared libraries an
ii  libexpat1 1.95.6-8   XML parsing C library - runtime li
ii  libfontconfig12.2.3-1generic font configuration library
ii  libfreetype6  2.1.7-2.2  FreeType 2 font engine, shared lib
ii  libice6   4.3.0.dfsg.1-8 Inter-Client Exchange library
ii  libncurses5   5.4-4  Shared libraries for terminal hand
ii  libsm64.3.0.dfsg.1-8 X Window System Session Management
ii  libxaw7   4.3.0.dfsg.1-8 X Athena widget set library
ii  libxext6  4.3.0.dfsg.1-8 X Window System miscellaneous exte
ii  libxft2   2.1.2-6FreeType-based font drawing librar
ii  libxmu6   4.3.0.dfsg.1-8 X Window System miscellaneous util
ii  libxpm4   4.3.0.dfsg.1-8 X pixmap library
ii  libxrender1   0.8.3-7X Rendering Extension client libra
ii  libxt64.3.0.dfsg.1-8 X Toolkit Intrinsics
ii  xlibs 4.3.0.dfsg.1-8 X Window System client libraries m
ii  xlibs-data4.3.0.dfsg.1-8 X Window System client data

-- no debconf information


   Regards,

-- 
Loïc Minier [EMAIL PROTECTED]



X Strike Force XFree86 SVN commit: r1951 - in trunk/debian: . local

2004-10-13 Thread X Strike Force SVN Repository Admin
Author: branden
Date: 2004-10-13 12:13:17 -0500 (Wed, 13 Oct 2004)
New Revision: 1951

Modified:
   trunk/debian/CHANGESETS
   trunk/debian/local/FAQ.xhtml
Log:
(cosmetic) Convert -- dashes to em-dash entities.

(cosmetic) Remove a garbage space.


Modified: trunk/debian/CHANGESETS
===
--- trunk/debian/CHANGESETS 2004-10-12 22:06:01 UTC (rev 1950)
+++ trunk/debian/CHANGESETS 2004-10-13 17:13:17 UTC (rev 1951)
@@ -9,7 +9,7 @@
 files anywhere.)
 
 Miscellaneous cosmetic fixes.
-1915, 1916, 1919, 1920, 1932, 1934, 1940
+1915, 1916, 1919, 1920, 1932, 1934, 1940, 1951
 
 Update Danish debconf template translations (thanks, Claus Hindsgaul).
 (Closes: #274101)

Modified: trunk/debian/local/FAQ.xhtml
===
--- trunk/debian/local/FAQ.xhtml2004-10-12 22:06:01 UTC (rev 1950)
+++ trunk/debian/local/FAQ.xhtml2004-10-13 17:13:17 UTC (rev 1951)
@@ -2932,7 +2932,7 @@
 alternate group.  For example, on many European keyboards, one can press
 kbdAltGr + E/kbd to produce the Euro sign (euro;).  This approach is often
 taken when most keys don't need an symbol defined for the alternate group,
-because most keys are engraved with two or fewer glyphs. /p
+because most keys are engraved with two or fewer glyphs./p
 
 pOther times, however, most or all of the printing keys on the keyboard are
 engraved with primary group emand/em alternate group glyphs.  Russian
@@ -2987,10 +2987,10 @@
 pemThanks to Jeff Licquia for contributing much of this entry./em/p
 
 pPeople sometimes find that they can use their codeCompose/code key as
-expected in some applications -- for instance, code
+expected in some applications mdash; for instance, code
 class=commanduxterm/code, code class=commandxterm/code, and
-OpenOffice.Org Writer -- but not in others, such as Mozilla, Galeon, or code
-class=commandgnome-terminal/code./p
+OpenOffice.Org Writer mdash; but not in others, such as Mozilla, Galeon, or
+code class=commandgnome-terminal/code./p
 
 pThe difference is that the latter group of applications use the GTK+ input
 method framework, and the former group does not./p



X Strike Force XFree86 SVN commit: r1952 - in branches/debconf-overhaul/debian: . local patches po

2004-10-13 Thread X Strike Force SVN Repository Admin
Author: branden
Date: 2004-10-13 12:32:42 -0500 (Wed, 13 Oct 2004)
New Revision: 1952

Added:
   
branches/debconf-overhaul/debian/patches/000_stolen_from_sourceforge_wacom_driver.diff
   
branches/debconf-overhaul/debian/patches/098_en_US.UTF-8_Compose_fix_Unicode_plane_1.diff
   
branches/debconf-overhaul/debian/patches/099i_pro_savage_ddr_set_use_bios_to_false.diff
   branches/debconf-overhaul/debian/patches/099j_xkb_new_layouts.diff
   branches/debconf-overhaul/debian/patches/099k_Compose_fix_latin1_UTF8.diff
   branches/debconf-overhaul/debian/patches/099z_xkb_level3_ralt_switch.diff
   branches/debconf-overhaul/debian/patches/101b_xkb_sun_loads_srvr_ctrl.diff
Removed:
   branches/debconf-overhaul/debian/patches/036_wacom_usb_tablet_update.diff
Modified:
   branches/debconf-overhaul/debian/MANIFEST.alpha.in
   branches/debconf-overhaul/debian/MANIFEST.amd64.in
   branches/debconf-overhaul/debian/MANIFEST.arm.in
   branches/debconf-overhaul/debian/MANIFEST.hppa.in
   branches/debconf-overhaul/debian/MANIFEST.hurd-i386.in
   branches/debconf-overhaul/debian/MANIFEST.i386.in
   branches/debconf-overhaul/debian/MANIFEST.ia64.in
   branches/debconf-overhaul/debian/MANIFEST.m68k.in
   branches/debconf-overhaul/debian/MANIFEST.mips.in
   branches/debconf-overhaul/debian/MANIFEST.mipsel.in
   branches/debconf-overhaul/debian/MANIFEST.powerpc.in
   branches/debconf-overhaul/debian/MANIFEST.s390.in
   branches/debconf-overhaul/debian/MANIFEST.sparc.in
   branches/debconf-overhaul/debian/changelog
   branches/debconf-overhaul/debian/control
   branches/debconf-overhaul/debian/local/FAQ.xhtml
   branches/debconf-overhaul/debian/local/xterm.faq.html
   branches/debconf-overhaul/debian/patches/000_stolen_from_HEAD.diff
   branches/debconf-overhaul/debian/patches/000_stolen_from_HEAD_xkb_data.diff
   branches/debconf-overhaul/debian/patches/000_stolen_from_author_xterm.diff
   branches/debconf-overhaul/debian/patches/099z_xkb_fix_rules_xfree86.diff
   branches/debconf-overhaul/debian/patches/907_debian_xterm.diff
   branches/debconf-overhaul/debian/po/da.po
   branches/debconf-overhaul/debian/rules
   branches/debconf-overhaul/debian/xfree86-common.init
   branches/debconf-overhaul/debian/xfs.init
   branches/debconf-overhaul/debian/xlibs.install
   branches/debconf-overhaul/debian/xserver-xfree86.config.in
   branches/debconf-overhaul/debian/xserver-xfree86.templates
Log:
Merge revisions 1878 to HEAD from trunk.


Including diff would make mail exceed size limit of 25 bytes.
Use svn diff -r 1951:1952 to view diff.



Bug#276234: xterm lost $HOME/bin and $TMPDIR

2004-10-13 Thread Michelle Konzack
Am 2004-10-13 08:20:16, schrieb Thomas Dickey:
   perhaps xterm isn't being run as a login shell:
 
 by the way -
 
 Changing xterm's behaviour doesn't rely upon scripting

And 'mutt' ? 
I can not use 'mutt' under in xterm anymore since this upgrade.

It was working for years since 03/1999 (SLINK)...
My fvwm2rc has not changed for more then one year.

So there was something changed in xterm since
4.1.0-16woody1 because this Version works fine. 

Greetings
Michelle

-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/ 
Michelle Konzack   Apt. 917  ICQ #328449886
   50, rue de Soultz MSM LinuxMichi
0033/3/8845235667100 Strasbourg/France   IRC #Debian (irc.icq.com)


signature.pgp
Description: Digital signature


X Strike Force XFree86 SVN property change: propchange - r1952 svn:log

2004-10-13 Thread X Strike Force SVN Repository Admin
Author: branden
Revision: 1952
Property Name: svn:log

New Property Value:
Merge revisions 1878 to HEAD from trunk.

WARNING: This merge was botched and included unrelated changes.  For the
real merge, include the subsequent revision to this branch, which reverts
the unrelated changes.




X Strike Force XFree86 SVN commit: r1953 - branches/debconf-overhaul/debian

2004-10-13 Thread X Strike Force SVN Repository Admin
Author: branden
Date: 2004-10-13 12:39:17 -0500 (Wed, 13 Oct 2004)
New Revision: 1953

Modified:
   branches/debconf-overhaul/debian/xserver-xfree86.config.in
   branches/debconf-overhaul/debian/xserver-xfree86.templates
Log:
Revert unrelated changes that got mixed in with the merge in r1952.


Modified: branches/debconf-overhaul/debian/xserver-xfree86.config.in
===
--- branches/debconf-overhaul/debian/xserver-xfree86.config.in  2004-10-13 
17:32:42 UTC (rev 1952)
+++ branches/debconf-overhaul/debian/xserver-xfree86.config.in  2004-10-13 
17:39:17 UTC (rev 1953)
@@ -26,16 +26,8 @@
 
 CONFIG_LOG=/var/log/$THIS_PACKAGE.config.log
 
-# Declare global variables unique to this script here.  They can be (and often
-# are) re-initialized to empty values upon first use for clarity.
-UPGRADING=
-PRECONFIGURED=
-DO_DETECT_DISPLAY_HARDWARE=
-DETECTED_DISPLAY=
+AUTODETECT_VIDEO_CARD=
 DEFAULT_MODES=
-PRIORITY=
-PRIORITY_CEILING=
-SKIP_XFREE86_X_SERVER_CONFIG=
 NCARDS=0
 NSERVERS=0
 NDRIVERS=0
@@ -64,22 +56,20 @@
   observe $*
 }
 
-detect_display_adapter () {
-  # syntax: detect_display_adapter
+discover_video () {
+  # syntax: discover_video
   #
   # This is a wrapper for the discover command that can distinguish Discover 
1.x
-  # and 2.x.  It uses Discover to determine which X server (and XFree86 X 
server
-  # driver, if applicable) to use for the detected display adapter.  It returns
-  # output in the following format:
+  # and 2.x.  It returns output in the following format:
   #   vendor+model server driver
   # For example:
   #   ATI Radeon 9000  XFree86 ati
   # A tab character separates each field.
 
-  local cmd detected_display discover_errorfile discover_test driver_file func 
\
+  local cmd discovered_video discover_errorfile discover_test driver_file func 
\
 server_file vendor_model_file
 
-  func=detect_display_adapter
+  func=discover_video
 
   # Validate function arguments.
   if [ -n $* ]; then
@@ -109,14 +99,14 @@
 --data-version=${SOURCE_VERSION%-*} display
   eval $cmd $driver_file || debug_report_status $CMD $?
 
-  detected_display=$(paste $vendor_model_file $server_file $driver_file)
+  discovered_video=$(paste $vendor_model_file $server_file $driver_file)
   rm -f $vendor_model_file $server_file $driver_file
 else
   # must be Discover 1.x
-  detected_display=$(discover --disable=serial,parallel \
+  discovered_video=$(discover --disable=serial,parallel \
   --format=%V %M\t%S\t%D\n video 2/dev/null)
 fi
-echo $detected_display
+echo $discovered_video
   else
 warn $func(): cannot use discover; failed with error message: \
  $(cat $discover_errorfile)
@@ -439,17 +429,22 @@
   set +e
   trace $func(): running \$input_command $priority $template\ with default 
\
 \$default_answer\
-
-  db_get $template
-  trace $func(): existing value of $template answer is \$RET\
-
-  # Are we supposed to clobber the existing answer with our default?
-  if [ -n $CLOBBER_DEFAULT ]; then
-trace $func(): setting value of $template to \$default_answer\
-db_set $template $default_answer
+  # are we re-configuring?
+  if [ -n $RECONFIGURE ]; then
+# yes, we are reconfiguring
+db_get $template
+trace $func(): (reconfiguring) preserving existing answer \$RET\
+  else
+# not reconfiguring; has the question been seen before?
+db_fget $template seen
+if [ $RET = true ]; then
+  db_get $template
+  trace $func(): (not reconfiguring) preserving existing answer \$RET\
+else
+  trace $func(): auto-answering with \$default_answer\
+  db_set $template $default_answer
+fi
   fi
-
-  # Enqueue the question.
   $input_command $priority $template
   if [ $? -eq 30 ]; then
 trace $func(): not asking $template per exit status of $input_command
@@ -543,18 +538,16 @@
   esac
 }
 
-configure_default_x_server () {
-  # syntax: configure_default_x_server
+select_default_x_server () {
+  # syntax: select_default_x_server
   #
   # Ask debconf questions that determine the destination of the default X 
server
   # symbolic link.
-  #
-  # Returns status 1 if the configuration file has been locally modified.
 
-  local bailout choices default_x_server_package display_server_report func \
-line owners
+  local bailout choices default_x_server_package func owners \
+videocard_server_report
 
-  func=configure_default_x_server
+  func=select_default_x_server
 
   # Validate function arguments.
   if [ -n $* ]; then
@@ -616,7 +609,7 @@
   if [ $owners != $choices ]; then
 trace $func(): \$owners does not equal \$choices: \$owners\ !=  \
   \$choices\
-db_subst shared/default-x-server choices $owners
+db_subst shared/default-x-server choices $owners
 db_fset shared/default-x-server seen false
   fi
 
@@ -625,71 +618,79 @@
   will not be asked
   fi
 
-  # Set a 

Bug#276234: xterm lost $HOME/bin and $TMPDIR

2004-10-13 Thread Thomas Dickey
On Wed, Oct 13, 2004 at 07:20:00PM +0200, Michelle Konzack wrote:
 Am 2004-10-13 08:20:16, schrieb Thomas Dickey:
perhaps xterm isn't being run as a login shell:
  
  by the way -
  
  Changing xterm's behaviour doesn't rely upon scripting
 
 And 'mutt' ? 
 I can not use 'mutt' under in xterm anymore since this upgrade.

I'm assuming you're doing something like
xterm -e mutt
which can't be a login shell, of course.
 
 It was working for years since 03/1999 (SLINK)...
 My fvwm2rc has not changed for more then one year.

fvwm changed its configuration though (different topic).
 
 So there was something changed in xterm since
 4.1.0-16woody1 because this Version works fine. 

I think it's more likely that someone changed the scope of environment
variable trimming on setuid programs.  That would show up in xterm,
but is unrelated to anything that might have been changed in xterm.

(I'm the upstream maintainer for xterm, cannot say what interesting things
might occur in Debian's packages).

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net


pgphpH8OuMeta.pgp
Description: PGP signature


Bug#22506: Fw: answer

2004-10-13 Thread Rodolfo Glover
So anyway, before I head out, this is what I was refering to.  
http://www.ezfilesharing.com/ref44.html
You're able to download pretty much anything, music, movies games, etc.  So 
I've downloaded 8 video games  movies so far today :).
You have to check out how many things they have in here to download - it's out 
of this world.
They walk you through the entire process of burning your choices to CD.
I saw a few areas of the movie section, and found titles in there still in 
theaters - it's nutty.
Talk to you tommorow.

Abdul


Bug#276234: xterm lost $HOME/bin and $TMPDIR

2004-10-13 Thread Michelle Konzack
But what I do not understand is, that it was working up to the UPGRADE.

If i login onto the console, I have my $HOME /home/michelle AND 
$PATH /home/michelle/bin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin
which are set by my ~/.bash_profile

Now if I 'startx' the two variables are availlable in fvwm2 (2.5.10)

Now if I call a 'xterm' as non-login-shell fvwm leaves the two 
variables to 'xterm' which was working for years. 

If I login via a DisplayManager, I set the $PATH inside the ~/.xsession
and it was working to like the login from the console.

Now it does not more work ansd you say, that you are upstream. 
So you are not the Package Maintainer of xfree86/xterm. 

Maybe they have changed something in 4.1.0-16woody2 or 4.1.0-16woody3

Installing a clean system from CD and runing the test are working fine.
Please note, that my $HOME is a nfs-mount and always the same.
So I have no errors in my Configs.

Please can you check it out with the package Maintainer ?
I am not the only person with this problem...

(and I have the same problem with my InternetCafee runing 20 WS)

Greetings
Michelle

-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/ 
Michelle Konzack   Apt. 917  ICQ #328449886
   50, rue de Soultz MSM LinuxMichi
0033/3/8845235667100 Strasbourg/France   IRC #Debian (irc.icq.com)


signature.pgp
Description: Digital signature


Bug#274457: Please test new ca, ch, hu, jp, mn and vn layouts for PC models

2004-10-13 Thread Christian Hudon

Denis Barbier wrote:


Hi,

you filed bugreports for not being able to select multiple layouts.
Could you please get new XKB files from
 http://people.debian.org/~barbier/xkb/xkb-4.3.0.dfsg.1-8+SVN.tar.bz2
and test your desired layouts?  These layouts can be loaded without
problems, but as I am not familiar with them, it is pretty hard to check
that everything works fine.  Since we are releasing soon, your feedback
is very important to quickly solve problems if needed (or to know that
it works ;)).
 

I tried the Canadian French layout, and everything seems to work 
correctly. Among other things, the AltGr key (aka ISO_Level3_Shift) is 
finally at the right place.


One small nit would be to change the shorthand string (that is used by 
the gnome keyboard applet, etc. to indicate the current keyboard) from 
ca to something a bit more descriptive (like fr_ca) for the French 
Canadian keyboard layout.


Hopefully these new keyboard layouts can be folded into a last X release 
for testing. Otherwise having a defective layout makes use of programs 
running under X pretty hard.


Thanks!

 Christian





Processed: Re: Bug#235125: xfree86-common: Decimal point on numeric part of Danish kbd doesn't work in some apps

2004-10-13 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 reassign 235125 mozilla
Bug#235125: xlibs: numeric keypad decimal point doesn't work in some apps with 
xfree86/pc105/dk
Bug reassigned from package `xlibs' to `mozilla'.

 tags 235125 = patch
Bug#235125: xlibs: numeric keypad decimal point doesn't work in some apps with 
xfree86/pc105/dk
Tags were: upstream moreinfo
Tags set to: patch

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)



Bug#274457: Please test new ca, ch, hu, jp, mn and vn layouts for PC models

2004-10-13 Thread Denis Barbier
On Wed, Oct 13, 2004 at 03:06:28PM -0400, Christian Hudon wrote:
 I tried the Canadian French layout, and everything seems to work 
 correctly. Among other things, the AltGr key (aka ISO_Level3_Shift) is 
 finally at the right place.
 
 One small nit would be to change the shorthand string (that is used by 
 the gnome keyboard applet, etc. to indicate the current keyboard) from 
 ca to something a bit more descriptive (like fr_ca) for the French 
 Canadian keyboard layout.

I tested gnome-keyboard-properties and under the Canadian menu, there
are four variants: French, French (legacy), Multilingual and
Multilingual 2nd part.  Where is ca displayed?
I do not know GNOME, do not hesitate to send lengthy explanations ;)

Denis




Bug#274457: Please test new ca, ch, hu, jp, mn and vn layouts for PC models

2004-10-13 Thread Christian Hudon

Denis Barbier wrote:


On Wed, Oct 13, 2004 at 03:06:28PM -0400, Christian Hudon wrote:
 

I tried the Canadian French layout, and everything seems to work 
correctly. Among other things, the AltGr key (aka ISO_Level3_Shift) is 
finally at the right place.


One small nit would be to change the shorthand string (that is used by 
the gnome keyboard applet, etc. to indicate the current keyboard) from 
ca to something a bit more descriptive (like fr_ca) for the French 
Canadian keyboard layout.
   



I tested gnome-keyboard-properties and under the Canadian menu, there
are four variants: French, French (legacy), Multilingual and
Multilingual 2nd part.  Where is ca displayed?
I do not know GNOME, do not hesitate to send lengthy explanations ;)
 

First this is under Gnome 2.6 or 2.8. Earlier versions used a different 
applet for the keyboard switching. Not sure how to make a lenghty 
explanation of it, though. When you add the keyboard switching applet on 
a panel, it displays (on the panel) a letter code to indicate the 
current keyboard. For the US English keyboard it's us. For the Spanish 
keyboard it's es. And for the French Canadian keyboard it's (right 
now) ca.


Don't hesitate to ask again if the explanation is not long enough. :-)

 Christian





Bug#276400: RFE: lndir should be a separate package

2004-10-13 Thread Ambrose Li
Package: xfree86-common
Version: 4.3.0.dfsg.1-8
Severity: wishlist


lndir only depends on glibc, and it has uses outside of X. It seems wrong to
download the rest of XFree86-common just to get lndir, if the box is never
going to run X.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-ow1
Locale: LANG=zh_TW.Big5, LC_CTYPE=zh_TW.Big5

Versions of packages xfree86-common depends on:
ii  debconf   1.4.39 Debian configuration management sy
ii  debianutils   2.10.2 Miscellaneous utilities specific t

-- debconf information:
  xfree86-common/experimental_packages:



Bug#276234: xterm lost $HOME/bin and $TMPDIR

2004-10-13 Thread Thomas Dickey
On Wed, Oct 13, 2004 at 08:09:06PM +0200, Michelle Konzack wrote:
 But what I do not understand is, that it was working up to the UPGRADE.

I'm running Debian/testing, and see that about half the contents of /lib
was changed when I updated in mid-September (file dates are a month
earlier, but ctimes show me when the files got there).  I'd expect
environment-variable tinkering to be done in libc.
 
 If i login onto the console, I have my $HOME /home/michelle AND 
 $PATH /home/michelle/bin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin
 which are set by my ~/.bash_profile

generally I use tcsh (and set my path in .cshrc).  Aside from (a few years
ago) noticing that shared libraries in /usr/local/lib wouldn't get loaded
nicely (because of the environment-variable trimming), I haven't seen any
recent changes that would add variables to be trimmed.

A quick check (now that I'm home) with

xterm -e sh
or
SHELL=/bin/sh xterm

doesn't show a loss of variables.  So perhaps that's not the problem.
I'm not sure what is.
 
 Please can you check it out with the package Maintainer ?
 I am not the only person with this problem...

I think that's Branden Robinson - who'll be reading this (soon, perhaps).

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net


pgp3Ufmt0rH46.pgp
Description: PGP signature


Bug#274457: Please test new ca, ch, hu, jp, mn and vn layouts for PC models

2004-10-13 Thread Denis Barbier
On Wed, Oct 13, 2004 at 04:45:37PM -0400, Christian Hudon wrote:
 First this is under Gnome 2.6 or 2.8. Earlier versions used a different 
 applet for the keyboard switching. Not sure how to make a lenghty 
 explanation of it, though. When you add the keyboard switching applet on 
 a panel, it displays (on the panel) a letter code to indicate the 
 current keyboard. For the US English keyboard it's us. For the Spanish 
 keyboard it's es. And for the French Canadian keyboard it's (right 
 now) ca.

It looks like this applet does only take XkbLayout into account, you
should file a bug against it and request that XKbVariant be appended
when it does exist, e.g. in your case it could be displayed as ca(fr).

Denis




Re: Xsession doesn't use umask setting from /etc/login.defs

2004-10-13 Thread Tomas Fasth

Branden Robinson wrote:

[Redirecting to debian-devel; followups set.]

On Mon, Sep 20, 2004 at 02:29:32PM +0200, Wouter Hanegraaff
wrote:


Hi,

After a fresh sarge install, I'm having problems with umask
settings. In /etc/login.defs I set umask to 002, and that works
for logging in on the console or remote via ssh. However, if I
use {g,x,k}dm I keep getting an umask of 022, because Xsession
is started by the display manager which has a default umask of
022.

It seems that Xsession doesn't change the UMASK at all. Should
it do so? If not, which program should set the umask during a
graphical login?


Searching Google for xsession umask will give you some hints.


/etc/login.defs explicitly indicates that it is Configuration
control definitions for the login package, and many of its
parameters are inapplicable to display managers, or already
implemented in parallel (e.g., how long do wait after a failed
login before displaying the prompt/greeter again?).


I believe that /etc/login.defs _is_ the right place to define the
default umask property.

// Tomas

--
Tomas Fasth [EMAIL PROTECTED]
GnuPG 0x9FE8D504



Bug#276415: xvfb: xvfb-run doesn't handle quoted arguments correctly

2004-10-13 Thread Jason Lunz
Package: xvfb
Version: 4.3.0.dfsg.1-8
Severity: normal
Tags: patch

When passing xvfb-run a command that uses quotes, the quoting is lost
and the command doesn't work as intended.

an example:

$ xvfb-run wine 'c:\Program Files\NSIS\makensis.exe' 'win\client.nsi'
/usr/bin/wine.bin: cannot find 'c:\Program'
Wine failed with return code 1

With the following patch applied, this works as expected.


--- xvfb-run2004-10-13 18:16:13.0 -0400
+++ xvfb-run.fix2004-10-13 18:16:26.0 -0400
@@ -126,7 +126,7 @@
 
 # start the command and save its exit status
 set +e
-DISPLAY=:$SERVERNUM XAUTHORITY=$AUTHFILE $@ 21
+DISPLAY=:$SERVERNUM XAUTHORITY=$AUTHFILE $@ 21
 RETVAL=$?
 set -e
 


-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8.1
Locale: LANG=en_US, LC_CTYPE=en_US

Versions of packages xvfb depends on:
ii  libc6   2.3.2.ds1-17 GNU C Library: Shared libraries an
ii  libfreetype62.1.7-2.2FreeType 2 font engine, shared lib
ii  zlib1g  1:1.2.2-1compression library - runtime

-- no debconf information



Bug#56179: Harassing phone calls from collectors, allow us to show you how to stop them.

2004-10-13 Thread zofia barnes
Stop the hassle and worry of calls and late notices.
We have pioneered an advanced system of proven strategies 
that will get the creditors and debt collectors off your back for good

Our debt termination program has legally stopped millions of dollars worth
of debt from being collected.


check out our Elimination Program here
http://www.uniquemallitems.com/e2/



i am busy, no thank you, go above




The crippled condition of his traveling machine was now his chief trouble,
and although a good breeze had sprung up to fill the sails and the little
bark was making fair headway, Rob knew he could never expect to reach home
unless he could discover a better mode of conveyance than this. He
unstrapped the machine from his wrist to examine it better, and while
holding it carelessly in his hand it slipped and fell with a bang to the
deck, striking upon its round edge and rolling quickly past the cabin and
out of sight
With a cry of alarm he ran after it, and after much search found it lying
against the bulwark near the edge of a scupper hole, where the least jar of
the ship would have sent it to the bottom of the ocean



Bug#276417: xterm removes variable TMPDIR from the child's process environment

2004-10-13 Thread Debian Bug Tracking System

Package: xterm
Version: 4.1.0-16woody1
Severity: important
Tags: security


xterm removes the environment variable TMPDIR from the process environment:

To reproduce the error, run the following command, which starts a xterm
showing the value of the TMPDIR environment variable:

$ env TMPDIR=/tmp xterm -hold -e printenv TMPDIR

As can be seen in that xterm:  TMPDIR has no value.

Compare it with the following variant, which shows the value of the tmpdir
environment variable:

$ env tmpdir=/tmp xterm -hold -e printenv tmpdir

This time, xterm displays the value, which is /tmp.


-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux kugelfisch 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686
Locale: LANG=C, LC_CTYPE=de_DE

Versions of packages xterm depends on:
ii  debconf  1.0.32  Debian configuration management sy
ii  libc62.2.5-11.5  GNU C Library: Shared libraries an
ii  libfreetype6 2.0.9-1 FreeType 2 font engine, shared lib
ii  libncurses5  5.2.20020112a-7 Shared libraries for terminal hand
ii  libxaw7  4.1.0-16woody1  X Athena widget set library
ii  xlibs4.1.0-16woody1  X Window System client libraries

-- 
Wenn Sie mir E-Mail schreiben, stellen |  When writing me e-mail, please
Sie bitte vor meine E-Mail-Adresse |  precede my e-mail address with
meinen Vor- und Nachnamen, etwa so:|  my full name, like
Helmut Waitzmann [EMAIL PROTECTED], (Helmut Waitzmann) [EMAIL PROTECTED]



Bug#276234: xterm lost $HOME/bin and $TMPDIR

2004-10-13 Thread Michelle Konzack
Am 2004-10-13 16:45:36, schrieb Thomas Dickey:

 A quick check (now that I'm home) with
 
   xterm -e sh

This works for $HOME but not $PATH

 or
   SHELL=/bin/sh xterm

Not tried.

 doesn't show a loss of variables.  So perhaps that's not the problem.
 I'm not sure what is.

But I have cheched the /etc/profile adn the defaulte to the xserver:

PATH=/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games

which I overide.I have the source of 4.1.0-16woody3 here and
I have not found anything (maybe lake of experience :-/ )

It is wired, why it does not only cut $HOME but all up to the first :

  Please can you check it out with the package Maintainer ?
  I am not the only person with this problem...
 
 I think that's Branden Robinson - who'll be reading this (soon, perhaps).

OK 

Thanks and good night
Michelle

-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/ 
Michelle Konzack   Apt. 917  ICQ #328449886
   50, rue de Soultz MSM LinuxMichi
0033/3/8845235667100 Strasbourg/France   IRC #Debian (irc.icq.com)


signature.pgp
Description: Digital signature


Bug#276417: xterm removes variable TMPDIR from the child's process environment

2004-10-13 Thread Michelle Konzack
Hello Maintainer and Upstream,

This is related to BUG #276234

Greetings
Michelle


Am 2004-10-13 18:54:29, schrieb Helmut Waitzmann:
 
 Package: xterm
 Version: 4.1.0-16woody1
 Severity: important
 Tags: security
 
 
 xterm removes the environment variable TMPDIR from the process environment:
 
 To reproduce the error, run the following command, which starts a xterm
 showing the value of the TMPDIR environment variable:
 
 $ env TMPDIR=/tmp xterm -hold -e printenv TMPDIR
 
 As can be seen in that xterm:  TMPDIR has no value.
 
 Compare it with the following variant, which shows the value of the tmpdir
 environment variable:
 
 $ env tmpdir=/tmp xterm -hold -e printenv tmpdir
 
 This time, xterm displays the value, which is /tmp.
 
 
 -- System Information
 Debian Release: 3.0
 Architecture: i386
 Kernel: Linux kugelfisch 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686
 Locale: LANG=C, LC_CTYPE=de_DE
 
 Versions of packages xterm depends on:
 ii  debconf  1.0.32  Debian configuration management 
 sy
 ii  libc62.2.5-11.5  GNU C Library: Shared libraries 
 an
 ii  libfreetype6 2.0.9-1 FreeType 2 font engine, shared 
 lib
 ii  libncurses5  5.2.20020112a-7 Shared libraries for terminal 
 hand
 ii  libxaw7  4.1.0-16woody1  X Athena widget set library
 ii  xlibs4.1.0-16woody1  X Window System client libraries


-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/ 
Michelle Konzack   Apt. 917  ICQ #328449886
   50, rue de Soultz MSM LinuxMichi
0033/3/8845235667100 Strasbourg/France   IRC #Debian (irc.icq.com)


signature.pgp
Description: Digital signature


Spam mail warning notification! (Attachment Removal)

2004-10-13 Thread Support Spam
 eManager Notification *

The following mail was blocked since it contains sensitive content.

Source mailbox: debian-x@lists.debian.org
Destination mailbox(es): [EMAIL PROTECTED]
Policy: Attachment Removal
Attachment file name: data02.txt.exe - application/octet-stream
Action: Replaced with text

Clasquin AntiSpam/AntiVirus software has removed a sensitive attachment file in 
the email.

*** End of message *
Received: from clasquin.com ([61.171.132.192])
by mail.clasquin.net (8.12.5/8.12.5) with ESMTP id i9E0UqCT021090
for [EMAIL PROTECTED]; Thu, 14 Oct 2004 02:30:54 +0200
Message-Id: [EMAIL PROTECTED]
From: debian-x@lists.debian.org
To: [EMAIL PROTECTED]
Subject: Re: Request
Date: Thu, 14 Oct 2004 08:31:28 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary==_NextPart_000_0016=_NextPart_000_0016
X-Priority: 3
X-MSMail-Priority: Normal


Re: Xsession doesn't use umask setting from /etc/login.defs

2004-10-13 Thread GOTO Masanori
At Thu, 14 Oct 2004 00:14:58 +0200,
Tomas Fasth wrote:
  /etc/login.defs explicitly indicates that it is Configuration
  control definitions for the login package, and many of its
  parameters are inapplicable to display managers, or already
  implemented in parallel (e.g., how long do wait after a failed
  login before displaying the prompt/greeter again?).
 
 I believe that /etc/login.defs _is_ the right place to define the
 default umask property.

It's just my wishlist, but I think it's good idea to provide a summary
that describes what file affects the bootstrap configuration in
debian, by a professional of this kind of area...

Regards,
-- gotom