← Back to team overview

desktop-packages team mailing list archive

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



I also confirm that this bug can still be annoying with the latest versions of GDM and LightDM :-)
And it can be an easy way to make some jokes just by modifying the .profile! Then it will be hard for the user to understand why he can no longer start a new session.

Is it maybe possible to just add an error message if there are problems with the .profile file?
We can easily detect if there are errors in this .profile file as already written before:

    . ~/.profile || echo ERROR

But also without executing any code:

    sh -n ~/.profile || echo ERROR

Thank you for maintaining GDM and LightDM!

** Also affects: lightdm
   Importance: Undecided
       Status: New

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:
Status in “gdm” package in Ubuntu:
Status in “lightdm” package in Ubuntu:

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: