abrt 1.0.4 detected a crash. architecture: i686 cmdline: /usr/bin/python /usr/bin/virtaal comment: This happens when translation suggestions should occur component: virtaal executable: /usr/bin/virtaal kernel: 2.6.31.9-174.fc12.i686 package: virtaal-0.5.1-1.fc12 release: Fedora release 12 (Constantine) backtrace ----- Summary: TBc2c385a5 xmlrpclib.py:838:close:Fault: <Fault 1: "<class 'pysqlite2.dbapi2.OperationalError'>:database is locked"> Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/virtaal/support/opentranclient.py", line 72, in call_callback widget, widget.id, self.format_suggestions(widget.id, response) File "/usr/lib/python2.6/site-packages/virtaal/support/opentranclient.py", line 129, in format_suggestions (suggestions,), fish = xmlrpclib.loads(response) File "/usr/lib/python2.6/xmlrpclib.py", line 1184, in loads return u.close(), u.getmethodname() File "/usr/lib/python2.6/xmlrpclib.py", line 838, in close raise Fault(**self._stack[0]) Fault: <Fault 1: "<class 'pysqlite2.dbapi2.OperationalError'>:database is locked"> Local variables in innermost frame: self: <xmlrpclib.Unmarshaller instance at 0xa5ab8cc> How to reproduce ----- 1. Open a PO file 2. Try to translate a string
Created attachment 387107 [details] File: backtrace
Thanks for the report. I'm busy checking upstream to see if they have any ideas.
This bug is now upstream at: http://bugs.locamotion.org/show_bug.cgi?id=1355 The issue started with this problem at Open-Tran.eu (the plugin is on by default) http://groups.google.com/group/open-tran/browse_frm/thread/e3b95fde393f36f1?hl=en It is caused by unhandled SQLite errors. The upstream bug is looking to handle those errors.
Bruce, a question from upstream. Did Virtaal crash or was this just a traceback while translating? If it crashed its a more urgent fix, if its a traceback then its as critical.
This didn't cause a crash, only a traceback. However, open-tran.eu is back again, so this doesn't happen any more.
Actually, spoke too soon. Thanks for all your work on this.
This is now fixed upstream. I'll integrate it into the next release.
virtaal-0.5.2-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/virtaal-0.5.2-1.fc12
virtaal-0.5.2-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update virtaal'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1915
I can't comment on the F12 package, but 0.5.2-1.fc13 fixes this issue.
virtaal-0.5.2-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
I'm using 0.5.2-2.fc13, it happens everytime.
I'm reopening, upstream was also reopened and has been fixed. Simple explanation. The issues are seen when open-tran.eu is down, which seems to be happening more frequently now. The fix unfortunately didn't wrap all xmlrpc calls, but the upstream fix has now done that and should ensure this error disappears completely. This is in Virtaal 0.6.1 which I hope to release shortly.
virtaal-0.6.1-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/virtaal-0.6.1-1.fc13
Package: virtaal-0.5.2-2.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. After openning the "Open file" window 2. 3.
virtaal-0.6.1-1.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update virtaal'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/virtaal-0.6.1-1.fc13
Package: virtaal-0.5.2-2.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- I was trying to translate using Virtaal, and it crashed.
Package: virtaal-0.5.2-2.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Open Virtaal Comment ----- I just open virtaal and this error popped up. Virtaal keeps running well, but ABRT notifies of a crash.
virtaal-0.6.1-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.