Bug 1665366 - Cannot run AttributeError: module 'wx' has no attribute 'TaskBarIcon'
Summary: Cannot run AttributeError: module 'wx' has no attribute 'TaskBarIcon'
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: pyhoca-gui
Version: 29
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
URL: http://bugs.x2go.org/cgi-bin/bugrepor...
Whiteboard:
: 1677634 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-11 07:15 UTC by Rastislav Janci
Modified: 2019-11-27 22:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-27 22:23:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Rastislav Janci 2019-01-11 07:15:55 UTC
Description of problem:
Cannot execute puhoca-gui application because of the changes in wxpython4 - wx.TaskBarIcon is moved to wx.adv.TaskBarIcon

Version-Release number of selected component (if applicable):
pyhoca-gui-0.5.0.7-6.fc29.noarch
python3-cups-1.9.72-22.fc29.x86_64
python3-setproctitle-1.1.10-9.fc29.x86_64
python3-gobject-base-3.30.4-1.fc29.x86_64
python3-wxpython4-4.0.1-9.fc29.x86_64
python3-x2go-0.6.0.2-1.fc29.noarch


How reproducible:
run pyhoca-gui


Steps to Reproduce:
1. Open command line
2. run pyhoca-gui

Actual results:
Traceback (most recent call last):
  File "/usr/bin/pyhoca-gui", line 35, in <module>
    from pyhoca.wxgui.launcher import PyHocaGUI_Launcher
  File "/usr/lib/python3.7/site-packages/pyhoca/wxgui/launcher.py", line 44, in <module>
    from .frontend import PyHocaGUI
  File "/usr/lib/python3.7/site-packages/pyhoca/wxgui/frontend.py", line 42, in <module>
    from . import taskbar
  File "/usr/lib/python3.7/site-packages/pyhoca/wxgui/taskbar.py", line 83, in <module>
    class PyHocaGUI_TaskBarIcon(wx.TaskBarIcon):
AttributeError: module 'wx' has no attribute 'TaskBarIcon'


Expected results:
executed

Comment 1 Orion Poplawski 2019-01-11 17:48:01 UTC
Filed upstream

Comment 2 Orion Poplawski 2019-02-17 23:00:40 UTC
*** Bug 1677634 has been marked as a duplicate of this bug. ***

Comment 3 Rastislav Janci 2019-05-02 10:55:49 UTC
New Fedora 30 release, the same problem. Nothing has changed.

Comment 4 Ben Cotton 2019-10-31 19:26:44 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 '29'.

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 29 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 5 Ben Cotton 2019-11-27 22:23:16 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.