Ubuntu
ubiquity package

chpasswd: line 1: unknown user shadow (was ubiquity & python installer failure)

Bug #160822 reported by SHADOW
2
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: ubiquity

 Traceback (most recent call last):
  File "/usr/bin/ubiquity", line 130, in ?
    install(sys.argv[1])
  File "/usr/bin/ubiquity", line 55, in install
    ret = wizard.run()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 311, in run
    self.process_step()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 734, in process_step
    self.mountpoints_to_summary()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 1047, in mountpoints_to_summary
    self.progress_loop()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 524, in progress_loop
    raise RuntimeError, ("Install failed with exit code %s; see "
RuntimeError: Install failed with exit code 1; see /var/log/installer/syslog and /var/log/syslog

Revision history for this message
SHADOW (shakeeldow) wrote : My partman log for the error
Revision history for this message
SHADOW (shakeeldow) wrote : My syslog file for the error
Revision history for this message
Paul Dufresne (paulduf) wrote : Re: ubiquity & python installer failure

Extracting some hopefully useful info from syslog.txt:
chpasswd: line 1: unknown user shadow
chpasswd: error detected, changes ignored
ubiquity: ['/usr/lib/ubiquity/user-setup/user-setup-apply', '/target'] exited with code 1
ubiquity: ['/usr/share/ubiquity/install.py'] exited with code 1
Exception in KDE frontend (invoking crash handler):
Traceback (most recent call last):
  File "/usr/bin/ubiquity", line 130, in ?

Thank you for taking the time to report this bug and helping to make Ubuntu better.
We are Confirming this bug, as useful files have been attached.

Changed in ubiquity:
status: New → Confirmed
Revision history for this message
Paul Dufresne (paulduf) wrote :

Could it be that shadow would be an unacceptable name because of possible 'clash' with shadow password?
Just a wild guess.

Revision history for this message
Brian Murray (brian-murray) wrote :

shadow is indeed a reserved username as I found in the ubiquity-1.6.8/d-i/source/user-setup/reserved-usernames file - so that is probably the cause of the bug. However, I would have expected ubiquity to raise an error.

Changed in ubiquity:
importance: Undecided → Medium
Revision history for this message
SHADOW (shakeeldow) wrote :

Thanks for replying. I think the problem is as Brian Murray said above...!!!
But KUBUNTU 7.10 is working fine now and I'm no longer using shadow as 'username';

Thanks again friends.

Revision history for this message
Evan (ev) wrote :

This bug was fixed post-dapper.

Changed in ubiquity:
status: Confirmed → 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.