.profile not running after making screen default at login

Hi, and thanks for the report.

As far as I know, bash is first looking for ~/.bash_profile, ~/.bash_login, and ~/.profile in this order. You either should change your .bash_profile or call the .profile in the first line of .bash_profile.

Hi,

I've just created a brand new test user and ubuntu creates the following files by default

-rw-r--r-- 1 test test 220 2009-01-27 16:48 .bash_logout
-rw-r--r-- 1 test test 3115 2009-01-27 16:48 .bashrc
-rw-r--r-- 1 test test 675 2009-01-27 16:48 .profile

and .profile is the one that adds $HOME/bin to the PATH, it also seems to run .bashrc

So wouldn't it be better to add /usr/bin/screen-launcher to .profile instead of .bash_profile?

Is this really invalid? I got hit by this too; why does this package require use of .bash_profile instead of .profile?

Hi guys-

The next upload will address this.

:-Dustin

The new code will install/uninstall to ~/.profile.

It will then check if ~/.bash_profile and/or ~/.bash_login exist and will also write there as well.

Unfortunately, if perhaps screen-profiles inadvertently created your ~/.bash_profile, you will need to delete it manually. (Such is life with Jaunty Alpha, sorry about that...)

:-Dustin

This bug was fixed in the package screen-profiles - 1.19-0ubuntu1

---------------
screen-profiles (1.19-0ubuntu1) jaunty; urgency=low

  * screen: wrapper script should add a -c arg, and specify your chosen
    profile, and ensure that .screenrc at least exists, prevent recursion
    from happening to upgrading users by pruning source of ~/.screenrc-profile
    from ~/.screenrc, LP: #323756
  * screen-launcher-install: test executability of screen-launcher; install to
    .profile unconditionally, and only .bash_profile and .bash_login if they
    exist; sanitize the environment; LP: #319691, LP: #321869
  * screen-launcher-uninstall: test writability of file to prune; prune from
    .profile, .bash_profile, and .bash_login
  * screen-profiles-helper: update auto-launch-on-login detection accordingly
  * windows/common: start counting at 1, add a window for watching /etc/motd
  * profiles/profile.skel, profiles/*: source the user's local ~/.screenrc
    as a last step (allowing for overrides)
  * select-screen-profile: don't mess with the user's ~/.screenrc file here;
    only set up the ~/.screenrc-profile symlink

 -- Dustin Kirkland <email address hidden> Tue, 03 Feb 2009 10:24:28 +0100

Thanks! This is great.