Ubuntu
ubiquity package

installation crashed

Bug #78186 reported by Krzysztof Tataradziński
4
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Colin Watson

Bug Description

Binary package hint: ubuntu-live

raceback (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 741, in process_step
    self.mountpoints_to_summary()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 1029, in mountpoints_to_summary
    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; see "
RuntimeError: Install failed with exit code 1; see /var/log/installer/syslog and /var/log/syslog

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

How were you trying to install Ubuntu and from which media?

Changed in ubuntu-meta:
status: Unconfirmed → Needs Info
Revision history for this message
Krzysztof Tataradziński (tatar111) wrote : Re: [Bug 78186] Re: installation crashed

Ubuntu 6.10 amd64. desktop.

2007/1/24, Brian <email address hidden>:
>
> How were you trying to install Ubuntu and from which media?
>
> ** Changed in: ubuntu-meta (Ubuntu)
> Sourcepackagename: ubuntu-meta => ubiquity
> Status: Unconfirmed => Needs Info
>
> --
> installation crashed
> https://launchpad.net/bugs/78186
>

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

Could you please attach /var/log/installer/syslog, /var/log/syslog, and /var/log/partman to this bug, following the directions in http://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs? Thanks in advance.

Changed in ubiquity:
assignee: nobody → kamion
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

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.