Bug 1194976 - [abrt] fros: screencastgnome.py:152:IsSuitable:TypeError: argument of type 'NoneType' is not iterable
Summary: [abrt] fros: screencastgnome.py:152:IsSuitable:TypeError: argument of type 'N...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: fros
Version: 22
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Filak
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:99a9f054449c735eda7b8a0caf1...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-21 13:20 UTC by Joachim Frieben
Modified: 2016-12-01 00:49 UTC (History)
13 users (show)

Fixed In Version: 1.1-2.fc22
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-24 08:27:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (644 bytes, text/plain)
2015-02-21 13:20 UTC, Joachim Frieben
no flags Details
File: environ (3.36 KB, text/plain)
2015-02-21 13:20 UTC, Joachim Frieben
no flags Details

Description Joachim Frieben 2015-02-21 13:20:48 UTC
Version-Release number of selected component:
fros-1.1-1.fc22

Additional info:
reporter:       libreport-2.4.0
cmdline:        /usr/bin/python3 /bin/fros --is-available
executable:     /bin/fros
kernel:         3.20.0-0.rc0.git10.1.fc22.x86_64
runlevel:       N 3
type:           Python3
uid:            1000

Truncated backtrace:
screencastgnome.py:152:IsSuitable:TypeError: argument of type 'NoneType' is not iterable

Traceback (most recent call last):
  File "/bin/fros", line 81, in <module>
    available_plugins = load_plugins()
  File "/bin/fros", line 62, in load_plugins
    if plugin_instance.IsSuitable() > 0:  # append only suitable plugins
  File "/usr/lib/python3.4/site-packages/pyfros/plugins/screencastgnome.py", line 152, in IsSuitable
    if "gnome" in os.getenv("DESKTOP_SESSION"):
TypeError: argument of type 'NoneType' is not iterable

Local variables in innermost frame:
self: <pyfros.plugins.screencastgnome.ScreencastGnome object at 0x7f7960b9aeb8>

Comment 1 Joachim Frieben 2015-02-21 13:20:51 UTC
Created attachment 994166 [details]
File: backtrace

Comment 2 Joachim Frieben 2015-02-21 13:20:52 UTC
Created attachment 994167 [details]
File: environ

Comment 3 Reinier Balt 2015-04-11 11:50:56 UTC
Another user experienced a similar problem:

trying to log in after fedup to 22

reporter:       libreport-2.5.1
cmdline:        /usr/bin/python3 /usr/bin/fros --is-available
event_log:      2015-04-11-13:50:03> ('report_uReport' completed successfully)
executable:     /usr/bin/fros
kernel:         4.0.0-0.rc5.git4.1.fc22.x86_64
package:        fros-1.1-1.fc22
reason:         screencastgnome.py:152:IsSuitable:TypeError: argument of type 'NoneType' is not iterable
runlevel:       N 5
type:           Python3
uid:            1000

Comment 4 q2dg 2015-08-22 11:02:11 UTC
Me too. Every day (or two), at random times, it seems. It's really ANNOYING!

Comment 5 Paul Wouters 2015-08-22 23:21:22 UTC
is this run by the bug reporting that is crashing itself?

Comment 6 Jakub Filak 2015-08-24 08:05:03 UTC
I am sorry for the delayed fix, I just submitted the following patch for review:
https://github.com/jfilak/fros/commit/7518baa6861d68a1581616fa104b50d70d8a63ba

Comment 7 Fedora Update System 2015-08-25 07:21:24 UTC
fros-1.1-2.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-14188

Comment 8 Fedora Update System 2015-08-26 17:27:49 UTC
fros-1.1-2.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update fros'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-14188

Comment 9 Fedora Update System 2015-09-24 08:27:06 UTC
fros-1.1-2.fc22 has been pushed to the Fedora 22 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.