Ubuntu
user-setup package

warn about use of reserved user names

Bug #50036 reported by Jeff Ference
72
Affects Status Importance Assigned to Milestone
user-setup (Ubuntu)
Fix Released
Undecided
Colin Watson

Bug Description

Same error as in Bug #47647. After reading his info, I got all the files prior to doing anything else in the system.

Traceback (most recent call last):
  File "/usr/bin/ubiquity", line 120, in ?
    install(sys.argv[1])
  File "/usr/bin/ubiquity", line 54, in install
    ret = wizard.run()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 264, in run
    self.progress_loop()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 538, in progress_loop
    raise RuntimeError, "Install failed with exit code %s" % ret
RuntimeError: Install failed with exit code 1

Files to attach /var/log/installer/syslog and /var/log/partman

Revision history for this message
Jeff Ference (jeffreyference) wrote : syslog

syslog file from crash during install

Revision history for this message
Jeff Ference (jeffreyference) wrote : Partman file from install crash

file as requested.

Revision history for this message
Colin Watson (cjwatson) wrote : Re: Installer Crashed at 91% Creating User.

"shadow" is a name used by the system, and I'm afraid you can't use it. The installer should have warned you about this, though.

Changed in ubiquity:
status: Unconfirmed → Confirmed
Revision history for this message
Jeff Ference (jeffreyference) wrote :

Thank you for your quick response. I've just finished a successful install using a diffrent user name.

Revision history for this message
Colin Watson (cjwatson) wrote :

I've committed a fix for this upstream (SVN r40643).

Changed in user-setup:
status: Confirmed → Fix Committed
assignee: nobody → kamion
Revision history for this message
Colin Watson (cjwatson) wrote :

user-setup (1.2ubuntu4) edgy; urgency=low

  * Backport from trunk (closes: Malone #50036):
    - Detect and error out on reserved usernames, i.e. those that are
      already used by some parts of the system. Unfortunately there's no
      particularly straightforward way to identify a reserved username, and
      the only way I can think of is to maintain a blacklist; so I've
      collated this from the base-passwd master files and those user and
      group names I found on some of my systems. Feel free to extend this as
      the need arises.
  * Backport from trunk (Christian Perrier):
    - Spell "username" consistently.
  * Update translations from trunk.

 -- Colin Watson <email address hidden> Wed, 4 Oct 2006 14:37:38 +0100

Changed in user-setup:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.