zim crashed with AttributeError in __getattr__()

Bug #559964 reported by Paul Broadhead
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
zim (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: zim

Description: Ubuntu lucid (development branch)
Release: 10.04

zim:
  Installed: 0.43-2
  Candidate: 0.43-2
  Version table:
 *** 0.43-2 0
        500 http://gb.archive.ubuntu.com/ubuntu/ lucid/universe Packages
        100 /var/lib/dpkg/status

I started zim on a new install and received the error via the crash reporting system. However, zim continues working fine without actually crashing. Subsequent restarts were fine until I tried deleting the notes directory and the ~/.config/zim directory. When starting with this clean set-up, the error happens again.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: zim 0.43-2
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
Date: Sat Apr 10 12:14:53 2010
ExecutablePath: /usr/bin/zim
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/zim
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/zim']
SourcePackage: zim
Title: zim crashed with AttributeError in __getattr__()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Paul Broadhead (pjbroad) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #533095, 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.

tags: removed: need-duplicate-check
Revision history for this message
Paul Broadhead (pjbroad) wrote :

Following the link to the other bug fails:
"Not allowed here
Sorry, you don't have permission to access this page. "

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.