Binary package hint: ubiquity-frontend-kde
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 310, in run
self.process_step()
File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 750, in process_step
self.mountpoints_to_summary()
File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 1130, in mountpoints_to_summary
self.progress_loop()
File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 538, 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 455, in copy_all
os.mkdir(targetpath, mode)
OSError: [Errno 30] Read-only file system: '/target/usr/share/locale-langpack/nl/LC_MESSAGES'
I've looked at many other reports with nearly identical error messages, but none have had my second error message afterwards. In case it helps, this is how the error occurred: I installed Kubuntu 6.06 on the first of two HD's in my system, manually partitioning; the second drive I left with one NTFS partition. The drive failed (rather catastrophically), so I decided to reinstall Kubuntu on the second drive, eliminating the NTFS partition. During the partitioning step in installation, I noticed that the first (crashed) drive showed an empty table (not unpartitioned, not an empty partition, but NO TABLE)! I could not modify this first drive in any way. So, I continued with the partitioning of the second drive and install. Near the end of copying files, the above error report appeared. Please tell me I didn't just lose the second drive as well!
Seeing as this is more than 4 years old, and nobody else has commented on this, nor marked duplicates, I am going to close the report. If you think this is still an issue (which I couldn't even attempt to reproduce, as there isn't NTFS anywhere near my house), please reopen this report with further information. Thank you! Sorry it took someone so long to comment on this report.