Bug 602651 - [abrt] crash in gwibber-1:1.2.0-3.349bzr.fc12: memory:0xb0ff56c:34:msgstyle:AttributeError: Message instance has no attribute 'color'
Summary: [abrt] crash in gwibber-1:1.2.0-3.349bzr.fc12: memory:0xb0ff56c:34:msgstyle:A...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gwibber
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:fd6bb7e0
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-10 12:11 UTC by eblix08
Modified: 2010-08-20 02:12 UTC (History)
1 user (show)

Fixed In Version: gwibber-2.31.4-1.fc12
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-08-20 01:58:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.82 KB, text/plain)
2010-06-10 12:11 UTC, eblix08
no flags Details

Description eblix08 2010-06-10 12:11:06 UTC
abrt 1.0.9 detected a crash.

architecture: i686
cmdline: /usr/bin/python /usr/bin/gwibber
component: gwibber
executable: /usr/bin/gwibber
kernel: 2.6.32.11-99.fc12.i686.PAE
package: gwibber-1:1.2.0-3.349bzr.fc12
reason: memory:0xb0ff56c:34:msgstyle:AttributeError: Message instance has no attribute 'color'
release: Fedora release 12 (Constantine)

backtrace
-----
memory:0xb0ff56c:34:msgstyle:AttributeError: Message instance has no attribute 'color'

Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/gwibber/client.py", line 1118, in update_view_contents
    view.load_messages()
  File "/usr/lib/python2.6/site-packages/gwibber/gwui.py", line 98, in load_messages
    _=_)
  File "/usr/lib/python2.6/site-packages/mako/template.py", line 133, in render
    return runtime._render(self, self.callable_, args, data)
  File "/usr/lib/python2.6/site-packages/mako/runtime.py", line 347, in _render
    _render_context(template, callable_, context, *args, **_kwargs_for_callable(callable_, data))
  File "/usr/lib/python2.6/site-packages/mako/runtime.py", line 364, in _render_context
    _exec_template(inherit, lclcontext, args=args, kwargs=kwargs)
  File "/usr/lib/python2.6/site-packages/mako/runtime.py", line 397, in _exec_template
    callable_(context, *args, **kwargs)
  File "memory:0xb0ff56c", line 78, in render_body
  File "/usr/lib/python2.6/site-packages/mako/runtime.py", line 255, in <lambda>
    return lambda *args, **kwargs:callable_(self.context, *args, **kwargs)
  File "base_mako", line 615, in render_messages
  File "/usr/lib/python2.6/site-packages/mako/runtime.py", line 255, in <lambda>
    return lambda *args, **kwargs:callable_(self.context, *args, **kwargs)
  File "base_mako", line 268, in render_message
  File "base_mako", line 232, in messagebox
  File "base_mako", line 337, in render_messagebox
  File "memory:0xb0ff56c", line 34, in msgstyle
AttributeError: Message instance has no attribute 'color'

Local variables in innermost frame:
context: <mako.runtime.Context object at 0xc1ab2cc>
data: <gwibber.microblog.facebook.Message instance at 0xbcadbec>
__M_writer: <built-in method write of cStringIO.StringO object at 0xb211be0>
hasattr: <built-in function hasattr>

Comment 1 eblix08 2010-06-10 12:11:09 UTC
Created attachment 422887 [details]
File: backtrace

Comment 2 Fedora Update System 2010-07-26 19:24:09 UTC
gwibber-2.31.2-7.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/gwibber-2.31.2-7.fc12

Comment 3 Fedora Update System 2010-07-26 19:29:10 UTC
gwibber-2.31.2-7.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/gwibber-2.31.2-7.fc13

Comment 4 Fedora Update System 2010-07-27 02:25:22 UTC
gwibber-2.31.2-7.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 gwibber'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gwibber-2.31.2-7.fc13

Comment 5 Fedora Update System 2010-07-27 02:33:04 UTC
gwibber-2.31.2-7.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 gwibber'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gwibber-2.31.2-7.fc12

Comment 6 Fedora Update System 2010-08-09 20:28:46 UTC
gwibber-2.31.4-1.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/gwibber-2.31.4-1.fc12

Comment 7 Fedora Update System 2010-08-09 20:33:41 UTC
gwibber-2.31.4-1.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/gwibber-2.31.4-1.fc13

Comment 8 Fedora Update System 2010-08-10 21:30:38 UTC
gwibber-2.31.4-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 gwibber'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gwibber-2.31.4-1.fc12

Comment 9 Fedora Update System 2010-08-10 21:36:25 UTC
gwibber-2.31.4-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 gwibber'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gwibber-2.31.4-1.fc13

Comment 10 Fedora Update System 2010-08-20 01:53:12 UTC
gwibber-2.31.4-1.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2010-08-20 02:07:43 UTC
gwibber-2.31.4-1.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.