Ubuntu
ubiquity package

oops in zlib_inflate_codes

Bug #67221 reported by Levin Fritz
This bug report is a duplicate of:  Bug #67159: oops in zlib_inflate_codes. Edit Remove
4
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I tried to install the Ubuntu 6.10 release candidate from CD and it popped up a window saying “Installer crashed” and telling me to file a bug here. The “Installing system” progress bar is now at 62%, so I guess that's when the crash happened. Here's the stack trace from the error window:

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

I ran the “Check CD for defects” thingie before installing and it didn't find any errors.

Revision history for this message
Levin Fritz (levinfritz) wrote :
Revision history for this message
Levin Fritz (levinfritz) wrote :
Revision history for this message
Diego Sánchez Román (smsxeon) wrote :

I got the same here with Spanish language. However, in US English everthing went OK.

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

Please also attach /var/log/installer/syslog too. Thanks.

Changed in ubiquity:
status: Unconfirmed → Needs Info
Revision history for this message
Levin Fritz (levinfritz) wrote :

I tried the install again after filing this bug and then it worked. Maybe the first crash was caused by the CD drive - it seemed like it had a little trouble reading the CD-RW that the installer was on. Nonetheless, the installer should not have crashed.

I don't have the logfiles from the failed install anymore. Would it help you if I attached /var/log/installer/syslog from the successful install instead?

Revision history for this message
Joel Ebel (jbebel) wrote :

I'm seeing this behavior as well, and I don't have a /var/log/install/syslog file. There is a version file in that directory, but that is all. Attached is my /var/log/syslog. I'll add the partman file next, since only one attachment appears to be added at a time.

Revision history for this message
Joel Ebel (jbebel) wrote :
Revision history for this message
Joel Ebel (jbebel) wrote :

I see another confirmed bug on this issue, and I wanted to point out that I am using an intel core 2 duo processor, with both cores enabled, and the attached logs are in that configuration. This is on an asus p5b-vm, intel G965 chipset.

Revision history for this message
Paul Dufresne (paulduf) wrote : Re: cramfs: wrong magic

Please disregard my request concerning /var/log/installer/syslog, I have learned this is not used anymore with Edgy.

Setting as confirmed, based on Joel Ebel's /var/log/syslog containing cramfs: wrong magic too.

Changed in ubiquity:
status: Needs Info → Confirmed
Revision history for this message
Colin Watson (cjwatson) wrote :

Thanks for your report. This particular error is often 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).

The crash itself is another instance of the kernel oops in bug 67159.

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.