Ubuntu
apport package

apport-gtk crashed with UnicodeEncodeError in get_modified_files(): 'ascii' codec can't encode character '\xed' in position 40: ordinal not in range(128)

Bug #1054099 reported by rajesh on 2012-09-21

This bug report is a duplicate of: Bug #1044014: apport-gtk crashed with UnicodeEncodeError in get_modified_files(): 'ascii' codec can't encode character '\xed' in position 40: ordinal not in range(128). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	apport (Ubuntu)	New	Medium	Unassigned

Bug Description

apport-gtk crashed with UnicodeEncodeError in get_modified_files(): 'ascii' codec can't encode character '\xed' in position 40: ordinal not in range(128). Thius crash report was generated after the first login.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: apport-gtk 2.5.2-0ubuntu4
Uname: Linux 3.5.0-15-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Fri Sep 21 19:59:05 2012
ExecutablePath: /usr/share/apport/apport-gtk
InterpreterPath: /usr/bin/python3.2mu
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
ProcCwd: /home/anubhav
PythonArgs: ['/usr/share/apport/apport-gtk']
SourcePackage: apport
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

rajesh (bhatt-rajesh20) wrote on 2012-09-21:

Dependencies.txt Edit (560 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (258 bytes, text/plain; charset="utf-8")
Traceback.txt Edit (1.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2012-09-21: This bug is a duplicate

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 #1044014, 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.