| Summary: | Latest qt5ct won't start | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jim <jdean55> |
| Component: | qt5ct | Assignee: | Christian Dersch <lupinix.fedora> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 24 | CC: | lupinix.fedora |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-01-25 15:41:06 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Jim
2016-08-31 01:27:57 UTC
The behavior is correct, that's the way how Qt5 platform support works. Qt reads there environment variables and uses the values shipped by the plugin. Technically qt5ct is such a plugin, so changes made in qt5ct only work if the environment variables are set. But I do not set these by default, as the user might also have other platform like LXQt. So variables would conflict. Have to check what the best solution is. Maybe some script in /etc/profile.d which sets these variables if not yet set. But I have to check possible conflicts. (In reply to Christian Dersch from comment #1) > The behavior is correct, that's the way how Qt5 platform support works. Qt > reads there environment variables and uses the values shipped by the plugin. > Technically qt5ct is such a plugin, so changes made in qt5ct only work if > the environment variables are set. But I do not set these by default, as the > user might also have other platform like LXQt. So variables would conflict. > > Have to check what the best solution is. Maybe some script in /etc/profile.d > which sets these variables if not yet set. But I have to check possible > conflicts. Thanks for the explanation. |