Ubuntu
aptdaemon package

<type 'exceptions.UnicodeDecodeError'>: 'ascii' codec can't decode byte 0xc3 in position 8: ordinal not in range(128)

Bug #722649 reported by poffy on 2011-02-21

This bug report is a duplicate of: Bug #724735: aptd crashed with UnicodeDecodeError in _set_status_details(): 'ascii' codec can't decode byte 0xd0 in position 0: ordinal not in range(128). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	aptdaemon (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: aptdaemon

Tried to update

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: aptdaemon 0.40+bzr541-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-3.30-generic 2.6.38-rc4
Uname: Linux 2.6.38-3-generic i686
Annotation: Refreshing the software list failed
Architecture: i386
Date: Mon Feb 21 16:10:05 2011
DesktopFile: /usr/share/aptdaemon/aptdaemon.desktop
ExecutablePath: /usr/sbin/aptd
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
PackageArchitecture: all
SourcePackage: aptdaemon
Title: <type 'exceptions.UnicodeDecodeError'>: 'ascii' codec can't decode byte 0xc3 in position 8: ordinal not in range(128)
TransactionDepends: [[], [], [], [], [], [], []]
TransactionKwargs: {'sources_list': None}
TransactionLocale: nb_NO.UTF8
TransactionPackages: [[], [], [], [], [], []]
TransactionRole: role-update-cache

Tags:

Revision history for this message

poffy (erlijohn) wrote on 2011-02-21:

AptConfig.txt Edit (5.4 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.9 KiB, text/plain; charset="utf-8")
SourcesList.txt Edit (3.2 KiB, text/plain; charset="utf-8")
TraceBack.txt Edit (532 bytes, text/plain; charset="utf-8")

Revision history for this message

Robert Roth (evfool) wrote on 2011-03-11:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #729247, so it 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. Feel free to continue to report any other bugs you may find.