Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 942853[details]
VNC startup log
Description of problem:
Enabling python27 via scl interferes with successful launch of vncserver
Version-Release number of selected component (if applicable):
Xvnc TigerVNC 1.1.0 - built Jan 28 2014 04:21:52
Python 2.7.5
How reproducible:
Consistently reproducible
Steps to Reproduce:
1.source /opt/rh/python27/enable
2.vncserver
Actual results:
A blank vnc session is created with just an x for a cursor
Expected results:
A proper vnc session should be created
Additional info:
python: error while loading shared libraries: libpython2.7.so.1.0: cannot open shared object file: No such file or directory
I'm sorry but I have to close this. You are not supposed to source the enable scriptlet directly, that's just helper script used by the scl utility.
That being said, I assume the problem is caused by the scriptlet modifying setup of your environment in such a way that is incompatible with vnc server (maybe it relies on a specific python version?) and there is not much scl-utils can do about it. If anything, this would be a vncserver bug although I am not sure about that either, it is simply possible that the vncserver and software collections are not compatible with each other.
Sourcing the scriptlet directly is not causing the problem. For instance, one could do "scl enable python27 bash", followed by vncserver, and end up with the same result. I think this falls under scl's domain since scl modifies the environment to provide alternate versions of applications. The main error that vnc throws is "python: error while loading shared libraries: libpython2.7.so.1.0: cannot open shared object file: No such file or directory", which probably points to an incorrect handling of environment variables by scl's wrapper scripts.
Again, this is not within scope of scl-utils, as the component is not responsible for scriptlets that individual collections deliver. I suggest consulting this with maintainer of python27 collection - it's really likely that vnc is incompatible with the collection.
Created attachment 942853 [details] VNC startup log Description of problem: Enabling python27 via scl interferes with successful launch of vncserver Version-Release number of selected component (if applicable): Xvnc TigerVNC 1.1.0 - built Jan 28 2014 04:21:52 Python 2.7.5 How reproducible: Consistently reproducible Steps to Reproduce: 1.source /opt/rh/python27/enable 2.vncserver Actual results: A blank vnc session is created with just an x for a cursor Expected results: A proper vnc session should be created Additional info: python: error while loading shared libraries: libpython2.7.so.1.0: cannot open shared object file: No such file or directory