Bug 581822

Summary: [abrt] crash in virtaal-0.5.2-2.fc12: undomodel.py:93:push:ValueError: Invalid undo dictionary!
Product: [Fedora] Fedora Reporter: kruvalig <kruvalig>
Component: virtaalAssignee: Dwayne Bailey <dwayne>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: dwayne, sergey.linux, vpvainio
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:f4018074
Fixed In Version: virtaal-0.6.1-1.fc13 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-01 18:53:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description kruvalig 2010-04-13 11:08:41 UTC
abrt 1.0.8 detected a crash.

architecture: i686
cmdline: /usr/bin/python /usr/bin/virtaal
component: virtaal
executable: /usr/bin/virtaal
kernel: 2.6.32.11-99.fc12.i686.PAE
package: virtaal-0.5.2-2.fc12
reason: undomodel.py:93:push:ValueError: Invalid undo dictionary!
release: Fedora release 12 (Constantine)

backtrace
-----
undomodel.py:93:push:ValueError: Invalid undo dictionary!

Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/virtaal/controllers/undocontroller.py", line 87, in enabled_method
    return method(self, *args, **kwargs)
  File "/usr/lib/python2.6/site-packages/virtaal/controllers/undocontroller.py", line 200, in _on_unit_delete_text
    self.model.push(self._paste_undo_info)
  File "/usr/lib/python2.6/site-packages/virtaal/models/undomodel.py", line 93, in push
    raise ValueError('Invalid undo dictionary!')
ValueError: Invalid undo dictionary!

Local variables in innermost frame:
undo_dict: {'targetn': 0, 'cursorpos': 143, 'unit': <translate.storage.pypo.pounit object at 0x96d044c>}
self: <UndoModel object at 0x91d6554 (BaseModel at 0x93376b0)>
key: 'action'

Comment 1 kruvalig 2010-04-13 11:08:43 UTC
Created attachment 406207 [details]
File: backtrace

Comment 2 Dwayne Bailey 2010-04-14 11:41:09 UTC
Hi, thanks for the bug report.  Do you have a small test case that can replicate this problem, this might help upstream to resolve this more quickly.

I've reported this upstream http://bugs.locamotion.org/show_bug.cgi?id=1411

Comment 3 Dwayne Bailey 2010-04-15 16:11:43 UTC
This has been fixed upstream, thanks again for the report.  There is a new bugfix related release coming out shortly from upstream that will include this fix.  I'll wait for that before implementing the fix.

Comment 4 Ville-Pekka Vainio 2010-05-06 18:19:04 UTC
Package: virtaal-0.5.2-2.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


Comment
-----
Copy-pasted text from the original text to the translation

Comment 5 Fedora Update System 2010-06-07 12:09:46 UTC
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

Comment 6 Fedora Update System 2010-06-08 19:33:00 UTC
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

Comment 7 Fedora Update System 2010-06-25 18:21:41 UTC
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

Comment 8 Fedora Update System 2010-07-01 18:53:27 UTC
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.