Shell Works Great as Root | TurnKey GNU/Linux

Bash works great as root. Just as I'd expect. However, with my created non-root user it acts badly. Can't do basic stuff like tab to complete file names or even delete characters correctly.

Works totally fine as root though. Any ideas?

Replies (8)

Done :)

Reply 1 2012-01-10

Blueprints are on LaunchPad. Here is the one I just registered.

That sounds right

Reply 2 2012-01-10

Please register the blueprint & then point me to it. I'm curious to see where that's being done.

AFAIK useradd uses files from /etc/skel by default

Reply 3 2012-01-10

So perhaps we want the TKL devs to copy the ones found in root to be added to /etc/skel?

What do you think about that? If you agree that that would be the ideal situation then either register a blueprint, or just post back and I'll register it.

I'd used the skel code which

Reply 4 2012-01-10

I'd used the skel code which I'd used in the past with different distros.

$ ls -la /etc/skel/
total 24
drwxr-xr-x   3 root root 4096 Jan 9 02:31 .
drwxr-xr-x 111 root root 4096 Jan 7 18:35 ..
-rw-r--r--   1 root root 220 Apr 19 2010 .bash_logout
-rw-r--r--   1 root root 2924 Dec 20 2010 .bashrc
drwxr-xr-x   2 root root 4096 Dec 20 2010 .bashrc.d
-rw-r--r--   1 root root 675 Apr 19 2010 .profile

Replacing these files with the ones from root is making it work better.

Sounds like the profile files not copying across

Reply 5 2012-01-09

The root user has some hidden files in the home directory which set this stuff up. Generally they are copied across automatically when a new user acount is created. But I suspect that they didn't in this case. How did you set up the new user?

Hmm...

Reply 6 2012-01-11

Hmmm... maybe it was converting a question to a bug. No worries...

Sorry Alon I didn't actually test

Reply 7 2012-01-10

And I guess I considered it more of a feature request rather than an actual bug...

I had a look and I can't see how to change it either. I did a quick google and could only find a blueprint where it was suggested that launchpad should be able to do that but it says that it has been 'completed' (although to be fair it is suggesting the other way around, not both ways ie bug to blueprint).

Can't reproduce

Reply 8 2012-01-10

I tried reproducing the issue but couldn't, everything seems OK (see below). How did you add the new user?

BTW, this should be registered as a bug in launchpad, not a blueprint. IIRC, there was an option to convert a blueprint into a bug on LP, but I can't find it, @Jeremy any ideas?

root@core # adduser testuser1
Adding user `testuser1' ...
Adding new group `testuser1' (1002) ...
Adding new user `testuser1' (1001) with group `testuser1' ...
Creating home directory `/home/testuser1' ...
Copying files from `/etc/skel' ...
Enter new UNIX password:
Retype new UNIX password:
passwd: password updated successfully
Changing the user information for testuser1
Enter the new value, or press ENTER for the default
        Full Name []:
        Room Number []:
        Work Phone []:
        Home Phone []:
        Other []:
Is the information correct? [Y/n] y

root@core /# su testuser1
testuser1@core /$ cd ~
testuser1@core ~$ find .
  ./.bash_history
  ./.bash_logout
  ./.bashrc
  ./.profile
  ./.bashrc.d
  ./.bashrc.d/defaults
  ./.bashrc.d/git
  ./.bashrc.d/user-path
  ./.bashrc.d/bash_completion
  ./.bashrc.d/penv

testuser1@core ~$ find /etc/skel/
  /etc/skel/
  /etc/skel/.bash_logout
  /etc/skel/.bashrc
  /etc/skel/.profile
  /etc/skel/.bashrc.d
  /etc/skel/.bashrc.d/defaults
  /etc/skel/.bashrc.d/git
  /etc/skel/.bashrc.d/user-path
  /etc/skel/.bashrc.d/bash_completion
  /etc/skel/.bashrc.d/penv

testuser1@core ~$ diff /etc/skel/.bashrc /home/testuser1/.bashrc