.pam_environment not applied on first login but applied on successive logins

Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
I have a ~/.pam_environment file. When I start my computer and login, those environment variables are not applied, but when I logout and login again they are applied.
ecryptfs pam-environment
add a comment |Â
up vote
0
down vote
favorite
I have a ~/.pam_environment file. When I start my computer and login, those environment variables are not applied, but when I logout and login again they are applied.
ecryptfs pam-environment
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a ~/.pam_environment file. When I start my computer and login, those environment variables are not applied, but when I logout and login again they are applied.
ecryptfs pam-environment
I have a ~/.pam_environment file. When I start my computer and login, those environment variables are not applied, but when I logout and login again they are applied.
ecryptfs pam-environment
ecryptfs pam-environment
asked Feb 7 at 22:20
Bram Geron
12811
12811
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
If you are using encrypted home directories using ecryptfs, then perhaps the system attempts to read ~/.pam_environment before unlocking your home directory.
Here's a workaround which makes the file unencrypted. You will need sudo powers.
- Close all programs, because some programs are going to crash using this method.
- Open a terminal.
- Go to your home directory by running
cd - Move the file to the unencrypted
~/.ecryptfsdirectory by runningmv .pam_environment .ecryptfs/ - Make the file accessible from the decrypted environment:
ln -s .ecryptfs/.pam_environment Exit the decrypted environment by running
ecryptfs-umount-private. Although you will likely get a "Sessions still open, not unmounting" warning, it seems that the exiting still worked. You can confirm by attempting to runecryptfs-umount-privateagain.Your decrypted home directory is now not accessible, and it is normal to get lots of errors on your terminal because programs (e.g. shells) weren't built for this. You should be able to continue nonetheless. Avoid starting programs as much as possible until you reboot in step 8.
- Make the file accessible from the non-decrypted environment by running
sudo ln -s ~/.ecryptfs/.pam_environment. - Reboot your computer. You should now hopefully have
.pam_environmentapplied from the first login.
Related link:
- https://bugs.launchpad.net/ubuntu/+source/pam/+bug/584249
- https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1748036
(Per StackExchange policy, it is ~fine~ encouraged to self-answer your questions if you want to document a solution to a problem you had: stackoverflow.blog/2011/07/01/â¦)
â Bram Geron
Feb 7 at 22:22
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
If you are using encrypted home directories using ecryptfs, then perhaps the system attempts to read ~/.pam_environment before unlocking your home directory.
Here's a workaround which makes the file unencrypted. You will need sudo powers.
- Close all programs, because some programs are going to crash using this method.
- Open a terminal.
- Go to your home directory by running
cd - Move the file to the unencrypted
~/.ecryptfsdirectory by runningmv .pam_environment .ecryptfs/ - Make the file accessible from the decrypted environment:
ln -s .ecryptfs/.pam_environment Exit the decrypted environment by running
ecryptfs-umount-private. Although you will likely get a "Sessions still open, not unmounting" warning, it seems that the exiting still worked. You can confirm by attempting to runecryptfs-umount-privateagain.Your decrypted home directory is now not accessible, and it is normal to get lots of errors on your terminal because programs (e.g. shells) weren't built for this. You should be able to continue nonetheless. Avoid starting programs as much as possible until you reboot in step 8.
- Make the file accessible from the non-decrypted environment by running
sudo ln -s ~/.ecryptfs/.pam_environment. - Reboot your computer. You should now hopefully have
.pam_environmentapplied from the first login.
Related link:
- https://bugs.launchpad.net/ubuntu/+source/pam/+bug/584249
- https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1748036
(Per StackExchange policy, it is ~fine~ encouraged to self-answer your questions if you want to document a solution to a problem you had: stackoverflow.blog/2011/07/01/â¦)
â Bram Geron
Feb 7 at 22:22
add a comment |Â
up vote
1
down vote
If you are using encrypted home directories using ecryptfs, then perhaps the system attempts to read ~/.pam_environment before unlocking your home directory.
Here's a workaround which makes the file unencrypted. You will need sudo powers.
- Close all programs, because some programs are going to crash using this method.
- Open a terminal.
- Go to your home directory by running
cd - Move the file to the unencrypted
~/.ecryptfsdirectory by runningmv .pam_environment .ecryptfs/ - Make the file accessible from the decrypted environment:
ln -s .ecryptfs/.pam_environment Exit the decrypted environment by running
ecryptfs-umount-private. Although you will likely get a "Sessions still open, not unmounting" warning, it seems that the exiting still worked. You can confirm by attempting to runecryptfs-umount-privateagain.Your decrypted home directory is now not accessible, and it is normal to get lots of errors on your terminal because programs (e.g. shells) weren't built for this. You should be able to continue nonetheless. Avoid starting programs as much as possible until you reboot in step 8.
- Make the file accessible from the non-decrypted environment by running
sudo ln -s ~/.ecryptfs/.pam_environment. - Reboot your computer. You should now hopefully have
.pam_environmentapplied from the first login.
Related link:
- https://bugs.launchpad.net/ubuntu/+source/pam/+bug/584249
- https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1748036
(Per StackExchange policy, it is ~fine~ encouraged to self-answer your questions if you want to document a solution to a problem you had: stackoverflow.blog/2011/07/01/â¦)
â Bram Geron
Feb 7 at 22:22
add a comment |Â
up vote
1
down vote
up vote
1
down vote
If you are using encrypted home directories using ecryptfs, then perhaps the system attempts to read ~/.pam_environment before unlocking your home directory.
Here's a workaround which makes the file unencrypted. You will need sudo powers.
- Close all programs, because some programs are going to crash using this method.
- Open a terminal.
- Go to your home directory by running
cd - Move the file to the unencrypted
~/.ecryptfsdirectory by runningmv .pam_environment .ecryptfs/ - Make the file accessible from the decrypted environment:
ln -s .ecryptfs/.pam_environment Exit the decrypted environment by running
ecryptfs-umount-private. Although you will likely get a "Sessions still open, not unmounting" warning, it seems that the exiting still worked. You can confirm by attempting to runecryptfs-umount-privateagain.Your decrypted home directory is now not accessible, and it is normal to get lots of errors on your terminal because programs (e.g. shells) weren't built for this. You should be able to continue nonetheless. Avoid starting programs as much as possible until you reboot in step 8.
- Make the file accessible from the non-decrypted environment by running
sudo ln -s ~/.ecryptfs/.pam_environment. - Reboot your computer. You should now hopefully have
.pam_environmentapplied from the first login.
Related link:
- https://bugs.launchpad.net/ubuntu/+source/pam/+bug/584249
- https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1748036
If you are using encrypted home directories using ecryptfs, then perhaps the system attempts to read ~/.pam_environment before unlocking your home directory.
Here's a workaround which makes the file unencrypted. You will need sudo powers.
- Close all programs, because some programs are going to crash using this method.
- Open a terminal.
- Go to your home directory by running
cd - Move the file to the unencrypted
~/.ecryptfsdirectory by runningmv .pam_environment .ecryptfs/ - Make the file accessible from the decrypted environment:
ln -s .ecryptfs/.pam_environment Exit the decrypted environment by running
ecryptfs-umount-private. Although you will likely get a "Sessions still open, not unmounting" warning, it seems that the exiting still worked. You can confirm by attempting to runecryptfs-umount-privateagain.Your decrypted home directory is now not accessible, and it is normal to get lots of errors on your terminal because programs (e.g. shells) weren't built for this. You should be able to continue nonetheless. Avoid starting programs as much as possible until you reboot in step 8.
- Make the file accessible from the non-decrypted environment by running
sudo ln -s ~/.ecryptfs/.pam_environment. - Reboot your computer. You should now hopefully have
.pam_environmentapplied from the first login.
Related link:
- https://bugs.launchpad.net/ubuntu/+source/pam/+bug/584249
- https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1748036
edited Feb 7 at 22:48
answered Feb 7 at 22:20
Bram Geron
12811
12811
(Per StackExchange policy, it is ~fine~ encouraged to self-answer your questions if you want to document a solution to a problem you had: stackoverflow.blog/2011/07/01/â¦)
â Bram Geron
Feb 7 at 22:22
add a comment |Â
(Per StackExchange policy, it is ~fine~ encouraged to self-answer your questions if you want to document a solution to a problem you had: stackoverflow.blog/2011/07/01/â¦)
â Bram Geron
Feb 7 at 22:22
(Per StackExchange policy, it is ~fine~ encouraged to self-answer your questions if you want to document a solution to a problem you had: stackoverflow.blog/2011/07/01/â¦)
â Bram Geron
Feb 7 at 22:22
(Per StackExchange policy, it is ~fine~ encouraged to self-answer your questions if you want to document a solution to a problem you had: stackoverflow.blog/2011/07/01/â¦)
â Bram Geron
Feb 7 at 22:22
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1004034%2fpam-environment-not-applied-on-first-login-but-applied-on-successive-logins%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password