software-center crashed with TypeError in _on_property_changed(): could not convert type dbus.Int64 to (null) required for parameter 0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
aptdaemon (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Unassigned | ||
Quantal |
Fix Released
|
Medium
|
Unassigned | ||
software-center (Ubuntu) |
Invalid
|
Medium
|
Unassigned | ||
Precise |
Invalid
|
Undecided
|
Unassigned | ||
Quantal |
Invalid
|
Medium
|
Unassigned |
Bug Description
TEST CASE:
1. use a i386 version of ubuntu 12.04
2. install a really big package using software-center or a really large update
3. verify that it fails
4. install the version from precise-proposed
5. reboot
6. repeat step 2 and verify that it works this time
Crash happened after installing the Synergy 1.4.8 beta package.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: software-center 5.1.14.2
ProcVersionSign
Uname: Linux 3.2.0-23-generic i686
NonfreeKernelMo
ApportVersion: 2.0.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Fri Apr 13 15:08:45 2012
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
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
PythonArgs: ['/usr/
SourcePackage: software-center
Title: software-center crashed with TypeError in _on_property_
UpgradeStatus: Upgraded to precise on 2012-03-07 (36 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Related branches
- Colin Watson: Approve
-
Diff: 11606 lines (+11326/-22)25 files modified.pc/.quilt_patches (+1/-0)
.pc/.quilt_series (+1/-0)
.pc/.version (+1/-0)
.pc/applied-patches (+5/-0)
.pc/fix-lp-900982.patch/aptdaemon/enums.py (+698/-0)
.pc/fix-lp-932581.patch/aptdaemon/pkcompat.py (+2937/-0)
.pc/fix-lp-971748.patch/aptdaemon/networking.py (+262/-0)
.pc/fix-lp-971748.patch/aptdaemon/pkcompat.py (+2940/-0)
.pc/fix-lp-981124.patch/aptdaemon/client.py (+1697/-0)
.pc/fix_gettext_return_value_type.patch/aptdaemon/core.py (+2201/-0)
.pc/fix_gettext_return_value_type.patch/aptdaemon/utils.py (+88/-0)
aptdaemon/client.py (+8/-6)
aptdaemon/core.py (+20/-8)
aptdaemon/enums.py (+1/-1)
aptdaemon/networking.py (+11/-4)
aptdaemon/pkcompat.py (+10/-2)
aptdaemon/utils.py (+7/-1)
debian/changelog (+29/-0)
debian/patches/fix-lp-900982.patch (+19/-0)
debian/patches/fix-lp-932581.patch (+20/-0)
debian/patches/fix-lp-971748.patch (+87/-0)
debian/patches/fix-lp-981124.patch (+44/-0)
debian/patches/fix_gettext_return_value_type.patch (+171/-0)
debian/patches/series (+5/-0)
tests/regressions/test_lp768691.py (+63/-0)
tags: | removed: need-duplicate-check |
Changed in aptdaemon (Ubuntu): | |
importance: | Undecided → Medium |
Changed in software-center (Ubuntu): | |
importance: | Undecided → Medium |
Changed in aptdaemon (Ubuntu): | |
status: | Triaged → Fix Committed |
description: | updated |
Changed in software-center (Ubuntu Precise): | |
status: | New → Invalid |
Changed in software-center (Ubuntu Quantal): | |
status: | Incomplete → Invalid |
Changed in aptdaemon (Ubuntu Precise): | |
status: | New → In Progress |
Unfortunately the backtrace cut off some information, but this appears that this is happening on a property sync with aptdaemon.
Is this problem reproducable for you? Or did it only happend once?