← Back to team overview

desktop-packages team mailing list archive

[Bug 678421] Re: Error message for a faulty ~/.profile script


And I who thought it was so elegant to fix this bug with a few
characters of code. ;)

I suppose we could do a solution with zenity/kdialog, but before
spending time on such a proposal (involving gettext etc.), I would like
to know for sure that "sh -n" is an acceptable testing method. (Please
note that other ideas were rejected previously in this bug report.)

@Alec: I think Matthieu meant that if we ignore an erroneous file and
let the session start, the user may not be aware that there is an error,
and hence has no reason to go reading .xsession-errors. I think he has a

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.

  Error message for a faulty ~/.profile script

Status in Light Display Manager:
  In Progress
Status in “gdm” package in Ubuntu:
Status in “lightdm” package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: gdm

  After adding "function AddPath { PATH="$1:$PATH" }" to $HOME/.profile
  made the Xorg startup fail. (At that moment I had already forgotten
  the changes made to the .profile). As I had autologin that meant it
  kept trying to login and finally showed me the graphics
  reconfiguration screen. That sent me to a huge hunt for xorg conf and
  setup problems.

  Anyway finally tracked this down. I had used bash syntax in .profile
  file whereas it was run with sh.

  This is not a bug per se but I think a user mistake in ".profile"
  shouldn't bring the whole xorg startup to a halt as it does with
  autologin. I propose running user ".profile" and ".xprofile" scripts
  so that Xsession script continues running even if they have errors.
  I'm not sure whether this change would have some negative effects as

  1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 16 19:48:22 UTC 2010 i686 GNU/Linux
  2) gdm 2.30.2.is.2.30.0-0ubuntu4

To manage notifications about this bug go to: