Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
Summary: [abrt] crash in ibus-1.3.3-1.fc13: keyboardshortcut.py:140:get_shortcuts:TypeError: 'NoneType' object is not iterable
https://bugzilla.redhat.com/show_bug.cgi?id=597594
Summary: [abrt] crash in ibus-1.3.3-1.fc13: keyboardshortcut.py:140:get_shortcuts:TypeError: 'NoneType' object is not iterable Product: Fedora Version: 13 Platform: x86_64 OS/Version: Linux Status: NEW Status Whiteboard: abrt_hash:2fb74671 Severity: medium Priority: low Component: ibus AssignedTo: phuang@redhat.com ReportedBy: mad.kanie@gmail.com QAContact: extras-qa@fedoraproject.org CC: phuang@redhat.com, i18n-bugs@lists.fedoraproject.org Classification: Fedora
abrt 1.1.0 detected a crash.
architecture: x86_64 cmdline: python /usr/share/ibus/setup/main.py comment: error is consistently reproducible. component: ibus executable: /usr/share/ibus/setup/main.py kernel: 2.6.33.4-95.fc13.x86_64 package: ibus-1.3.3-1.fc13 reason: keyboardshortcut.py:140:get_shortcuts:TypeError: 'NoneType' object is not iterable release: Fedora release 13 (Goddard)
backtrace ----- keyboardshortcut.py:140:get_shortcuts:TypeError: 'NoneType' object is not iterable
Traceback (most recent call last): File "/usr/share/ibus/setup/keyboardshortcut.py", line 223, in __keycode_entry_notify_cb self.__update_add_and_apply_buttons() File "/usr/share/ibus/setup/keyboardshortcut.py", line 208, in __update_add_and_apply_buttons shortcuts = self.get_shortcuts() File "/usr/share/ibus/setup/keyboardshortcut.py", line 140, in get_shortcuts return [i[0] for i in model] TypeError: 'NoneType' object is not iterable
Local variables in innermost frame: _[1]: [] model: None self: <KeyboardShortcutSelection object at 0x1666e10 (GtkVBox at 0x18e4800)>
How to reproduce ----- 1. select preferences from ibus icon tray (with anthy engine). 2. click on button [...] (next input method) from "general" tab. dialog will be displayed. 3. click on "cancel". error notification is showed.
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=597594
--- Comment #1 from F.Prates mad.kanie@gmail.com 2010-05-29 14:03:29 EDT --- Created an attachment (id=417902) --> (https://bugzilla.redhat.com/attachment.cgi?id=417902) File: backtrace
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=597594
Peng Huang phuang@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Flag| |needinfo?(mad.kanie@gmail.c | |om)
--- Comment #2 from Peng Huang phuang@redhat.com 2010-05-30 20:29:58 EDT --- Sorry. I can not reproduce this problem. Can you always reproduce this problem?
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=597594
F.Prates mad.kanie@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Flag|needinfo?(mad.kanie@gmail.c | |om) |
--- Comment #3 from F.Prates mad.kanie@gmail.com 2010-05-31 19:01:24 EDT --- (In reply to comment #2)
Sorry. I can not reproduce this problem. Can you always reproduce this problem?
I've just tried to reproduce this error in a fedora 13 32-bit install, and the problem doesn't happen. That's why I've never noticed it before (first time that I use a 64 bit install).
Yes, in 64 bit, I can always reproduce this problem.
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=597594
Peng Huang phuang@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|phuang@redhat.com |pwu@redhat.com
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=597594
Peng Huang phuang@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ON_DEV
--- Comment #4 from Peng Huang phuang@redhat.com 2010-05-31 23:39:09 EDT --- Thank you for the information. This problem has been fixed in upstream. I will build it for fedora soon.
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=597594
Peng Wu pwu@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ON_DEV |CLOSED Resolution| |CURRENTRELEASE
--- Comment #5 from Peng Wu pwu@redhat.com 2010-07-01 22:17:59 EDT --- Check with the latest ibus rpm from Fedora 13 updates. As the upstream code is in Fedora 13 updates now, close this bug.
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=597594
--- Comment #6 from F.Prates mad.kanie@gmail.com 2010-07-02 18:41:14 EDT --- I've had no more crashes in ibus preferences on 64 bit fedora.
thanks for the fix.
i18n-bugs@lists.fedoraproject.org