Bug 706622

Summary: [abrt] gwibber-2.91.92-2.fc15: actions.py:39:action:AttributeError: 'NoneType' object has no attribute 'get'
Product: [Fedora] Fedora Reporter: Mads Villadsen <maxx>
Component: gwibberAssignee: Tom "spot" Callaway <tcallawa>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: redhat, tcallawa
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:4962dec76fd7e313c87e40e4ca9d220b243b42d0
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 18:55:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Mads Villadsen 2011-05-21 16:46:50 UTC
abrt version: 2.0.1
architecture:   i686
cmdline:        /usr/bin/python /usr/bin/gwibber
comment:        When clicking "reply" on a twitter post nothing happens in Gwibber and the following backtrace is logged in abrt.
component:      gwibber
executable:     /usr/bin/gwibber
kernel:         2.6.38.3-18.fc15.i686
os_release:     Fedora release 15 (Lovelock)
package:        gwibber-2.91.92-2.fc15
reason:         actions.py:39:action:AttributeError: 'NoneType' object has no attribute 'get'
time:           Wed Apr 27 17:03:01 2011
uid:            500
username:       maxx

backtrace:
:actions.py:39:action:AttributeError: 'NoneType' object has no attribute 'get'
:
:Traceback (most recent call last):
:  File "/usr/lib/python2.7/site-packages/gwibber/client.py", line 544, in on_action
:    getattr(actions, cmd).action(view, self, **query)
:  File "/usr/lib/python2.7/site-packages/gwibber/actions.py", line 39, in action
:    if msg.get("private", 0):
:AttributeError: 'NoneType' object has no attribute 'get'
:
:Local variables in innermost frame:
:msg: None
:self: <class gwibber.actions.reply at 0x9d481dc>
:client: <GwibberClient object at 0x9d4cdc4 (gwibber+client+GwibberClient at 0x9a472d0)>
:w: <SingleStreamUi object at 0x9dcb914 (gwibber+gwui+SingleStreamUi at 0x9ceb858)>

Comment 1 Vinzenz Vietzke 2011-05-22 18:14:44 UTC
Package: gwibber-3.0.0.1-2.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)


Comment
-----
Tried to reply to an identi.ca post.

Comment 2 Dagan McGregor 2011-05-29 12:59:22 UTC
Package: gwibber-3.0.0.1-2.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)


Comment
-----
When I am trying to click the reply or retweet a message in Gwibber, it crashes

Comment 3 Bob Nolty 2011-07-12 20:47:09 UTC
Package: gwibber-3.0.0.1-2.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)

Comment
-----
I clicked the reply button on a tweet I received inside gwibber.

The application is still running, but it did not open the reply dialog at the bottom of the screen.

Comment 4 Fedora End Of Life 2012-08-07 18:55:20 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping