Bug 1794874 - PyMol's Qt interface does not work [PATCH]
Summary: PyMol's Qt interface does not work [PATCH]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: pymol
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Antonio T. sagitter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-24 23:26 UTC by Ben Webb
Modified: 2020-06-26 01:07 UTC (History)
2 users (show)

Fixed In Version: pymol-2.3.0-9.fc32 pymol-2.3.0-9.fc31
Clone Of:
Environment:
Last Closed: 2020-06-26 00:45:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
pymol-sip.patch (537 bytes, patch)
2020-01-24 23:26 UTC, Ben Webb
no flags Details | Diff

Description Ben Webb 2020-01-24 23:26:52 UTC
Created attachment 1655172 [details]
pymol-sip.patch

Description of problem:
When PyMol is started on Fedora 31, the first thing it prints is

Qt not available, using GLUT/Tk interface

It then proceeds to use the older Tk interface, even though Qt is technically available.


Version-Release number of selected component (if applicable):
pymol-2.3.0-4.fc31.x86_64


How reproducible:
Always


Steps to Reproduce:
1. Run 'pymol'

Actual results:
PyMol starts, using the Tk interface (two separate windows).

Expected results:
PyMol starts with the Qt interface (one window).

Additional info:
The failure is in /usr/lib64/python3.7/site-packages/pymol/Qt/__init__.py where it tries to __import__("sip"). This does not work any more in F31 because there is no standalone sip package - it is now part of PyQt4. Patch to fix is attached.

Comment 1 Fedora Admin user for bugzilla script actions 2020-05-25 14:54:01 UTC
This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.

Comment 2 Fedora Admin user for bugzilla script actions 2020-05-26 14:57:13 UTC
This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.

Comment 3 Ben Webb 2020-06-16 05:35:14 UTC
FYI, the behavior is the same with Fedora 32, although the same patch fixes it.

Comment 4 Antonio T. sagitter 2020-06-16 10:47:08 UTC
Sorry, i missed this ticket since i became PyMol maintainer.

Comment 5 Fedora Update System 2020-06-16 20:16:06 UTC
FEDORA-2020-2c49a45958 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-2c49a45958

Comment 6 Fedora Update System 2020-06-16 20:16:07 UTC
FEDORA-2020-2c3b53c9ef has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-2c3b53c9ef

Comment 7 Fedora Update System 2020-06-18 13:41:00 UTC
FEDORA-2020-2c3b53c9ef has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-2c3b53c9ef`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-2c3b53c9ef

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2020-06-18 14:13:29 UTC
FEDORA-2020-2c49a45958 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-2c49a45958`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-2c49a45958

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2020-06-26 00:45:32 UTC
FEDORA-2020-2c49a45958 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2020-06-26 01:07:24 UTC
FEDORA-2020-2c3b53c9ef has been pushed to the Fedora 31 stable repository.
If problem still persists, 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.