After installing upgrade to ubuntu 9.10 the system needed to be powered down manually. Pressing restart button locked up the system.

Bug #464310 reported by tomnic
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: apport

I was running ubuntu 9.04 via wubi. Downloaded and installed upgrade to 9.10. Pressed restart button after installation. Screen became scrambled and system locked up. Needed to power down manually and then restart manually.

ProblemType: Crash
ApportLog:
 apport (pid 23510) Thu Oct 29 23:31:45 2009: called for pid 23509, signal 6
 apport (pid 23510) Thu Oct 29 23:31:45 2009: executable: /usr/sbin/cupsd (command line "/usr/sbin/cupsd")
 apport (pid 23510) Thu Oct 29 23:31:45 2009: Ignoring SIGABRT
Architecture: i386
CrashReports:
 600:0:0:6853:2009-10-29 23:30:39.000000000 -0700:2009-10-30 00:11:25.000000000 -0700:/var/crash/_usr_lib_hal_scripts_hal_lpadmin.0.crash
 600:0:0:29818:2009-10-30 00:11:42.000000000 -0700:2009-10-30 00:11:57.000000000 -0700:/var/crash/_usr_share_apport_apport-gtk.0.crash
Date: Fri Oct 30 00:11:43 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apport-gtk
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: apport-gtk 1.9.3-0ubuntu4
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gtk
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
PythonArgs: ['/usr/share/apport/apport-gtk']
SourcePackage: apport
Title: apport-gtk crashed with KeyError in __getitem__()
Uname: Linux 2.6.31-14-generic i686
UserGroups:

Revision history for this message
tomnic (p-launchpad-1to1products-com) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #424965, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-duplicate-check
visibility: private → public
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.