Bug 1471456 - [abrt] fusion-icon: util.py:79:__set:TypeError: Can't convert 'bool' object to str implicitly
Summary: [abrt] fusion-icon: util.py:79:__set:TypeError: Can't convert 'bool' object t...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: fusion-icon
Version: 25
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Wolfgang Ulbrich
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:ab7ff385fd2559aba24bea1f3f3...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-16 02:32 UTC by Adan Schwindt
Modified: 2017-12-12 10:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:22:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (573 bytes, text/plain)
2017-07-16 02:32 UTC, Adan Schwindt
no flags Details
File: environ (1.41 KB, text/plain)
2017-07-16 02:32 UTC, Adan Schwindt
no flags Details

Description Adan Schwindt 2017-07-16 02:32:34 UTC
Version-Release number of selected component:
fusion-icon-0.2.4-1.fc25

Additional info:
reporter:       libreport-2.8.0
cmdline:        /usr/bin/python3 -s /usr/bin/fusion-icon
executable:     /usr/bin/fusion-icon
kernel:         4.11.9-200.fc25.x86_64
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           Python3
uid:            1000

Truncated backtrace:
util.py:79:__set:TypeError: Can't convert 'bool' object to str implicitly

Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/FusionIcon/interface_gtk/main.py", line 173, in activate
    options[self.option].enabled = widget.get_active()
  File "/usr/lib/python3.5/site-packages/FusionIcon/util.py", line 79, in __set
    print(' * Setting option ' + self.label + ' to ' + value)
TypeError: Can't convert 'bool' object to str implicitly

Local variables in innermost frame:
value: True
self: <FusionIcon.util.CompizOption object at 0x7f707116f8d0>

Comment 1 Adan Schwindt 2017-07-16 02:32:39 UTC
Created attachment 1299192 [details]
File: backtrace

Comment 2 Adan Schwindt 2017-07-16 02:32:40 UTC
Created attachment 1299193 [details]
File: environ

Comment 3 Fedora End Of Life 2017-11-16 14:23:47 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

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

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is 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  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

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.

Comment 4 Fedora End Of Life 2017-12-12 10:22:25 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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