zim crashed with TypeError: autosave() takes exactly 2 arguments (4 given)

Bug #549655 reported by silvio1964
32
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Zim
Fix Released
High
Jaap Karssenberg
zim (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: zim

After Creating a new field.....

ProblemType: Crash
Architecture: i386
Date: Sat Mar 27 16:53:43 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/zim
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: zim 0.43-2
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/zim
ProcEnviron:
 LANG=it_IT.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
PythonArgs: ['/usr/bin/zim']
SourcePackage: zim
Title: zim crashed with TypeError: autosave() takes exactly 2 arguments (4 given)
Traceback: TypeError: autosave() takes exactly 2 arguments (4 given)
Uname: Linux 2.6.32-17-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
silvio1964 (verdecchiasilvio) wrote :
tags: removed: need-duplicate-check
visibility: private → public
Revision history for this message
Michael Nagel (nailor) wrote :

from duplicate:

crashed when moving a page via drag&drop

it did not actually crash but i was able to continue writing, apport popped up, however...

apparently this also happens when renaming a file by other means (e.g. right click in index -> rename)
apport pops up for every rename, but i can continue to use the application

Changed in zim (Ubuntu):
status: New → Confirmed
Revision history for this message
Jaap Karssenberg (jaap.karssenberg) wrote :

I'm the developer for this application and would like to investigate. Unfortunately these apport reports don't mean much to me. Please include the actual error output from zim.

You can get output on stderr by running zim from a terminal with "zim -D".

Revision history for this message
Michael Nagel (nailor) wrote :
Revision history for this message
Jaap Karssenberg (jaap.karssenberg) wrote :

Thanks Michael. Just confirmed this issue is still present in zim 0.46 :(

Changed in zim:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Jaap Karssenberg (pardus-cpan)
Revision history for this message
Jaap Karssenberg (jaap.karssenberg) wrote :

Fix committed in revision 224, will be included in next release (zim 0.47).

Changed in zim:
status: Confirmed → Fix Committed
Revision history for this message
Michael Nagel (nailor) wrote :

that patch should be backported and included into the ubuntu package

Revision history for this message
Jaap Karssenberg (jaap.karssenberg) wrote :

I linked a branch with the patch against zim 0.43, this can be used to update the package.

Revision history for this message
silvio1964 (verdecchiasilvio) wrote :

J'm not able to post here the output of zim -D while i had a crash of the system and now is running a new installation,sorry.

Revision history for this message
Jaap Karssenberg (jaap.karssenberg) wrote :

Fix released in zim 0.47

Changed in zim:
status: Fix Committed → Fix Released
Revision history for this message
Michael Nagel (nailor) wrote :

recent ubuntu packages do not contain that bug.

Changed in zim (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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