Description of problem: When launching frescobaldi the interface doesn't start and issue the following error: Traceback (most recent call last): File "/bin/frescobaldi", line 7, in <module> import main File "/usr/lib/python3.5/site-packages/frescobaldi_app/main.py", line 42, in <module> import remote # IPC with other Frescobaldi instances File "/usr/lib/python3.5/site-packages/frescobaldi_app/remote/__init__.py", line 29, in <module> from PyQt5.QtNetwork import QLocalServer, QLocalSocket ImportError: No module named 'PyQt5.QtNetwork' Version-Release number of selected component (if applicable): 3.0.0-2 How reproducible: Each time Installing manually the python3-qt5 package seems to have solved that issue, but I'm unsure whether this is sufficient. The spec file contains both python3 and 2 refs whereas the frescobaldi script referes python3 only: $ head -1 /usr/bin/frescobaldi #!/usr/bin/python3 -s I think that these lines should be removed: Requires: python-qt5-core Requires: python-qt5-gui Requires: python-qt5-network Requires: python-qt5-printsupport Requires: python-qt5-svg Requires: python-qt5-webkit Requires: python-qt5-webkitwidgets Requires: python-qt5-widgets Requires: python-qt5-xml And that that line should be added: Requires: python3-qt5 WDYT ? Bruno.
Assigning to the registered maintainer.
CC: (none) => marja11Assignee: bugsquad => rverschelde
Bruno, I've compiled a test rpm. Can you try it and let me know if the fix worked. If the test works for you, I'll give Remi the patch and he may push it publicly. ftp://kekepower.myftp.org/linux/frescobaldi/ Cheers, Stig
CC: (none) => smelror
May I do anything to help? I've never contributed to QA before but I just upgraded to Mageia 6 and I got this Frescobaldi error. I would be happy to try a test package but the link above doesn't appear to be working now. Best regards, Jim
CC: (none) => jimgarrett001
@Stig-Ørjan, could you commit your fix in SVN so I can test it ? (Your packages do not seem to be there anymore, which seems normal after so long for me to test :-()
(In reply to Bruno Cornec from comment #4) > @Stig-Ørjan, could you commit your fix in SVN so I can test it ? > (Your packages do not seem to be there anymore, which seems normal after so > long for me to test :-() Bruno, I think I just did what you suggested in your original post. Can't remember now and I've since deleted everything. Cheers, Stig
Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer maintained, which means that it will not receive any further security or bug fix updates. 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 Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 6's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. 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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ Best regards, Aurélien Bugsquad Team
CC: (none) => ouaurelienResolution: (none) => OLDStatus: NEW => RESOLVED