Third Installer Crash - Kubuntu 6.06.1

Bug #190094 reported by George Izzo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

This crash is the third that I've experienced with Kubuntu 6.06.1. I have tried two different CDs without success. Furthermore, I had even changed hard drives because I suspected faulty hardware. Finally, I did a low-level format using Kill Disk. Nothing seems to work. The information below was requested for a "new bug report."
===============

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 308, in run
    self.progress_loop()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 541, in progress_loop
    raise RuntimeError, ("Install failed with exit code %s; see "
RuntimeError: Install failed with exit code -11; see /var/log/installer/syslog and /var/log/syslog

 SORRY - I am not familiar with the linux file system; therefore, I wasn't sure how to attach files and there's no help to show how to do it. I can send an email under separate cover -- I just need an email address.
Thanks,
George

Revision history for this message
TerryG (tgalati4) wrote :

Marking as incomplete pending more info about hardware. See similar bugs with ubiquity install.

Changed in ubiquity:
status: New → Incomplete
Revision history for this message
TerryG (tgalati4) wrote :

To start with, how much RAM and how large is the hard disk that you are installing to? Did you check the CD with the Check CD option?

Revision history for this message
George Izzo (yowsaah) wrote : Re: [Bug 190094] Re: Third Installer Crash - Kubuntu 6.06.1

Terry,
THANK YOU for your response. I discovered that I had a bad RAM stick in
that box. After replacing the RAM I decided to install Ubuntu 8.04 as of
yesterday. That installation and subsequent updates went flawlessly. I'll
stick with 8 for awhile to familiarize myself with the Linux enviornment.
I'm at a point where I can't stand Microsoft any longer. (I've been using
its "products" since Windows 3.0 so I've lived through countless crashes and
frustration.)
PEACE!

On 2/29/08, TerryG <email address hidden> wrote:
>
> To start with, how much RAM and how large is the hard disk that you are
> installing to? Did you check the CD with the Check CD option?
>
> --
> Third Installer Crash - Kubuntu 6.06.1
> https://bugs.launchpad.net/bugs/190094
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Source Package "ubiquity" in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: ubiquity
>
> This crash is the third that I've experienced with Kubuntu 6.06.1. I have
> tried two different CDs without success. Furthermore, I had even changed
> hard drives because I suspected faulty hardware. Finally, I did a low-level
> format using Kill Disk. Nothing seems to work. The information below was
> requested for a "new bug report."
> ===============
>
> 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
> 308, in run
> self.progress_loop()
> File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line
> 541, in progress_loop
> raise RuntimeError, ("Install failed with exit code %s; see "
> RuntimeError: Install failed with exit code -11; see
> /var/log/installer/syslog and /var/log/syslog
>
> SORRY - I am not familiar with the linux file system; therefore, I wasn't
> sure how to attach files and there's no help to show how to do it. I can
> send an email under separate cover -- I just need an email address.
> Thanks,
> George
>

Revision history for this message
Evan (ev) wrote :

Closing as the reporter traced the problem to a bad stick of RAM.

Changed in ubiquity:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.