[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#354523: marked as done (xserver-xorg: .bashrc can cause Xsession error on login)

Your message dated Tue, 10 Apr 2007 21:39:03 -0400
with message-id <9f694b820704101839wb5d921dia9cbd4de21b4b1b6@mail.gmail.com>
and subject line About your bug #354523 "xserver-xorg: .bashrc can cause Xsession error on login" in Debian BTS
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)
--- Begin Message --- 
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-----

--- End Message ---
--- Begin Message --- 
Submitter was asked to provide more information about this bug
( http://bugs.debian.org/354523 ) four weeks ago.

Since more info was not provided, we are closing the bug.
Feel free to reopen this bug if you are still experiencing this issue
and you have extra information on how reproduce the issue.

Thanks,
Olivier



2007/3/8, Olivier Vitrat <ovit.debian@gmail.com>:

Hello,

Are you still able to reproduce this problem with a recent version of
this package ?

Thanks,
Olivier Vitrat

--- End Message ---
Reply to: