Ubuntu
ubiquity package

Install failed with exit code 139 (no logs available)

Bug #67206 reported by Luis Flores III
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I was trying to install a fresh copy of Edgy on my laptop, ran the live CD, and was given this message after more then half (53%) of the installation was completed. The following is is the error messege that I recived, except that their are no log files, at least not that I can find, I think because I am running the Live CD.

We're sorry; the installer crashed. Please file a new bug report at https://launchpad.net/distros/ubuntu/+source/ubiquity/+filebug (do not attach your details to any existing bug) and a developer will attend to the problem as soon as possible. To help the developers understand what went wrong, include the following detail in your bug report, and attach the files /var/log/syslog and /var/log/partman:

Traceback (most recent call last):
  File "/usr/bin/ubiquity", line 166, in ?
    main()
  File "/usr/bin/ubiquity", line 161, in main
    install(sys.argv[1])
  File "/usr/bin/ubiquity", line 57, in install
    ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtkui.py", line 305, in run
    self.process_step()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtkui.py", line 856, in process_step
    self.progress_loop()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtkui.py", line 631, in progress_loop
    raise RuntimeError, ("Install failed with exit code %s; see "
RuntimeError: Install failed with exit code 139; see /var/log/syslog

Wish I had more for you!

Revision history for this message
Paul Dufresne (paulduf) wrote :

If you could attach /var/log/installer/syslog, /var/log/syslog, and /var/log/partman to this bug, by commenting on the bug's web page, that would greatly help us finding out what have been going wrong.
Thanks.

Changed in ubiquity:
status: Unconfirmed → Needs Info
Revision history for this message
Luis Flores III (luisflores3) wrote : Re: [Bug 67206] Re: Installer Crashed

I had commented that due to the fact that I was installing from the live CD,
the log files were no where to be found, and even if they were somewhere, I
have since restarted the computer and and reinstalled Dapper, reformatting
the hard drive in the process, so I am sorry that I do not have them.

Luis

On 10/21/06, Paul Dufresne <email address hidden> wrote:
>
> If you could attach /var/log/installer/syslog, /var/log/syslog, and
> /var/log/partman to this bug, by commenting on the bug's web page, that
> would greatly help us finding out what have been going wrong.
> Thanks.
>
> ** Changed in: ubiquity (Ubuntu)
> Status: Unconfirmed => Needs Info
>
> --
> Installer Crashed
> https://launchpad.net/bugs/67206
>

--
<email address hidden>
http://www.myoddlittleworld.com
(267)994-2563

Revision history for this message
Paul Dufresne (paulduf) wrote :

Oh, sorry.
Then could you attach /var/log/syslog on Dapper?
That would give us a good idea of the hardware of that computer that have problem with edgy?
Thanks.

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

There normally are logs when installing from the live CD. I didn't ask for them in the live-CD-specific installer just for fun, you know. :-)

Anyway, this particular error is usually due to a faulty CD/DVD disk or drive. It may help to clean the CD/DVD, to burn the CD/DVD at a lower speed, or to clean the CD/DVD drive lens (cleaning kits are often available from electronics suppliers).

Changed in ubiquity:
status: Needs Info → Rejected
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.