update-manager crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I installed this precise pangolin Beta 2 from scratch in this not so up-to-date notebook - a Pentium Dual Core of about 4 years of age. It's video card is a SIS 671 which is not supported in standard UBUNTU, so I had to do some tricks in order to make it usable. Basically I installed git, xorg-dev, mesa-common-dev, libdrm-dev, libtool, build-essential and compiled a new driver found with:
git clone git://github.
And that was all I did so far. After that, when I launched the update manager, I say that is able only to do partial upgrades, and after that it says that cannot recognise which ubuntu version I am using, and asked me to install ubuntu-desktop or kbuntu or something else so it could recognise which version I have. I'm not sure wheather the changes I've made are related to the bug, but anyway, I'm reporting it.
Hope this is helpful
Marco
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: update-manager 1:0.156.10
ProcVersionSign
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu2
Architecture: amd64
Date: Thu Apr 12 20:51:38 2012
ExecutablePath: /usr/bin/
GsettingsChanges:
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
TERM=unknown
Signal: 6
SourcePackage: update-manager
StacktraceTop:
raise () from /lib/x86_
abort () from /lib/x86_
?? () from /lib/x86_
__assert_fail () from /lib/x86_
?? () from /usr/lib/
Title: update-manager crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #930839, 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.