meld crashed with TypeError in <lambda>(): <HistoryFileEntry object at 0x1e58960 (HistoryFileEntry at 0x1f08540)>: unknown signal name: changed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
meld |
Incomplete
|
Medium
|
|||
meld (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
meld crashed with TypeError in <lambda>(): <HistoryFileEntry object at 0x1e58960 (HistoryFileEntry at 0x1f08540)>: unknown signal name: changed
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: meld 1.6.1-1
ProcVersionSign
Uname: Linux 3.8.0-0-generic x86_64
NonfreeKernelMo
ApportVersion: 2.8-0ubuntu2
Architecture: amd64
Date: Tue Jan 22 15:57:30 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/meld
InstallationDate: Installed on 2010-12-05 (779 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/meld barnowl-1.10dev barnowl-
PythonArgs: ['/usr/bin/meld', 'barnowl-1.10dev', 'barnowl-
SourcePackage: meld
Title: meld crashed with TypeError in <lambda>(): <HistoryFileEntry object at 0x1e58960 (HistoryFileEntry at 0x1f08540)>: unknown signal name: changed
Traceback:
Traceback (most recent call last):
File "/usr/lib/
entry.
TypeError: <HistoryFileEntry object at 0x1e58960 (HistoryFileEntry at 0x1f08540)>: unknown signal name: changed
UpgradeStatus: Upgraded to raring on 2012-11-15 (68 days ago)
UserGroups: adm admin cdrom dialout fuse libvirtd lpadmin plugdev sambashare sudo wireshark
tags: | removed: need-duplicate-check |
Changed in meld (Ubuntu): | |
importance: | Undecided → Medium |
information type: | Private → Public |
Changed in meld: | |
importance: | Unknown → Medium |
status: | Unknown → New |
Changed in meld: | |
status: | New → Incomplete |
Status changed to 'Confirmed' because the bug affects multiple users.