Bug#354523: xserver-xorg: .bashrc can cause Xsession error on login

2006-02-26 Thread Adam Porter
Package: xserver-xorg
Version: 6.9.0.dfsg.1-4
Severity: minor

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


For quite a while now, every time I logged in with a certain user, an X dialog 
box would pop up that said that there were too many arguments provided, and 
that it was falling back to the default session.  I'd click okay, and then it 
would happen one more time, and after dismissing it KDE would log in fine.

Finally I used rgrep to track down that error message, and added a line in 
/etc/X11/Xsession.d/20x11-common_process-args to write the arguments it was 
receiving to a file.  Then I checked that file, and found that it was receiving 
bell-style none arguments.  I found those in my .bashrc file, above these 
lines:

# If running interactively, then:
if [ $PS1 ]; then

I moved set bell-style none below that, and the problem--finally--went away.

I'm filing this bug because it doesn't seem like this should happen.  There 
should, at the very least, be a comment in .bashrc explaining that anything 
above those two lines will get passed to Xsession, which could cause problems.  
Even better would be a smarter Xsession script that would intelligently handle 
things like that.  Perhaps even better than that (might be talking over my head 
here) would be for Xsession to not read the .bashrc file, because it already 
reads .Xsession, as far as I understand.  Does it need to read both?  I'm not 
sure how .bashrc (or .bash_profile, since it often sources .bashrc, as in my 
case) is supposed to fit into the Xsession system.

Finally, I hope that this bug report, once indexed by Google, might help 
someone else who goes crazy trying to fix this annoying problem.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFEAl+j5+GdyTDsrJsRAg3MAJ4wvm9kFY+Xp0vhQ9Eo1IweKUajXACggES3
4QKRV9sV/OyErl3txUMSLRw=
=13ek
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#354523: xserver-xorg: .bashrc can cause Xsession error on login

2006-02-26 Thread Eugene Konev
At Sun, 26 Feb 2006 20:10:43 -0600,
Adam Porter wrote:
 
 Package: xserver-xorg
 Version: 6.9.0.dfsg.1-4
 Severity: minor
 
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 
 For quite a while now, every time I logged in with a certain user, an X 
 dialog box would pop up that said that there were too many arguments 
 provided, and that it was falling back to the default session.  I'd click 
 okay, and then it would happen one more time, and after dismissing it KDE 
 would log in fine.
 
 Finally I used rgrep to track down that error message, and added a line in 
 /etc/X11/Xsession.d/20x11-common_process-args to write the arguments it was 
 receiving to a file.  Then I checked that file, and found that it was 
 receiving bell-style none arguments.  I found those in my .bashrc file, 
 above these lines:
 

Are you using kdm?



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#354523: xserver-xorg: .bashrc can cause Xsession error on login

2006-02-26 Thread Adam Porter
On Sunday 26 February 2006 20:45, Eugene Konev wrote:
 At Sun, 26 Feb 2006 20:10:43 -0600,

 Adam Porter wrote:
  Package: xserver-xorg
  Version: 6.9.0.dfsg.1-4
  Severity: minor
 
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1
 
 
  For quite a while now, every time I logged in with a certain user, an X
  dialog box would pop up that said that there were too many arguments
  provided, and that it was falling back to the default session.  I'd click
  okay, and then it would happen one more time, and after dismissing it
  KDE would log in fine.
 
  Finally I used rgrep to track down that error message, and added a line
  in /etc/X11/Xsession.d/20x11-common_process-args to write the arguments
  it was receiving to a file.  Then I checked that file, and found that it
  was receiving bell-style none arguments.  I found those in my .bashrc
  file, above these lines:

 Are you using kdm?

Yes.


pgp7br5izMCEw.pgp
Description: PGP signature


Bug#354523: xserver-xorg: .bashrc can cause Xsession error on login

2006-02-26 Thread Eugene Konev
reassign 354523 kdm
thanks

At Sun, 26 Feb 2006 21:05:33 -0600,
Adam Porter wrote:
 
 On Sunday 26 February 2006 20:45, Eugene Konev wrote:
  At Sun, 26 Feb 2006 20:10:43 -0600,
 
  Adam Porter wrote:
   Package: xserver-xorg
   Version: 6.9.0.dfsg.1-4
   Severity: minor
  
   -BEGIN PGP SIGNED MESSAGE-
   Hash: SHA1
  
  
   For quite a while now, every time I logged in with a certain user, an X
   dialog box would pop up that said that there were too many arguments
   provided, and that it was falling back to the default session.  I'd click
   okay, and then it would happen one more time, and after dismissing it
   KDE would log in fine.
  
   Finally I used rgrep to track down that error message, and added a line
   in /etc/X11/Xsession.d/20x11-common_process-args to write the arguments
   it was receiving to a file.  Then I checked that file, and found that it
   was receiving bell-style none arguments.  I found those in my .bashrc
   file, above these lines:
 
  Are you using kdm?
 
 Yes.

This is a bug in kdm's Xsession script, which sources $HOME/.bashrc
and then /etc/X11/Xsession. Reassigning...

Probably severity of this bug should be raised as it allows any user
to override system policy through .bashrc.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Processed: Re: Bug#354523: xserver-xorg: .bashrc can cause Xsession error on login

2006-02-26 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 reassign 354523 kdm
Bug#354523: xserver-xorg: .bashrc can cause Xsession error on login
Bug reassigned from package `xserver-xorg' to `kdm'.

 thanks
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]