Ubuntu
ubiquity package

The Ubunutu installer crashed

Bug #122184 reported by Njnetsfan
4
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Thomas Meire

Bug Description

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/gtkui.py", line 266, in run
    self.process_step()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 755, in process_step
    self.mountpoints_to_summary()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 1114, in mountpoints_to_summary
    self.progress_loop()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 550, in progress_loop
    raise RuntimeError, ("Install failed with exit code %s\n%s" %
RuntimeError: Install failed with exit code 1
Traceback (most recent call last):
  File "/usr/share/ubiquity/install.py", line 1263, in ?
    if install.run():
  File "/usr/share/ubiquity/install.py", line 284, in run
    if not self.copy_all():
  File "/usr/share/ubiquity/install.py", line 469, in copy_all
    os.lchown(targetpath, st.st_uid, st.st_gid)
OSError: [Errno 30] Read-only file system: '/target/home'

Revision history for this message
Thomas Meire (blackskad) wrote :

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information. Can you please attach the required files as separate attachments - as described on https://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs .

Changed in ubiquity:
assignee: nobody → blackskad
status: New → Incomplete
Revision history for this message
Colin Watson (cjwatson) wrote :

I apologise for this bug having been improperly marked as a duplicate.

Still, I'm afraid that there is nothing we can do about this without the requested log files. If you (the original reporter) can reproduce this bug with a current release and can get us the log files, feel free to reopen this bug. (Anyone else reading this who believes they have a similar problem should open a new bug instead.)

"Read-only file system" rather suggests that the kernel gave up trying to write to disk after encountering too many errors. This sometimes happens due to a faulty (or just too hot) hard disk.

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