New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Environmental variable "QT_PLUGIN_PATH" conflict for RStudio 1.2 on Win10 #4694
Comments
|
Thanks for filing this! I'm removing the bug label because I think respecting Do you have a proposal for a more elegant approach? (One I thought of was trying to rename this variable for our use, e.g. |
|
I tried appending RStudio plugin directory to I don't know how |
|
IMHO setting QT_PLUGIN_PATH globally as you have is a bit of an anti-pattern, as it means all applications on your system will now look in that path for Qt plugins (regardless of what version of Qt that particular application is using). I can understand it's a required workaround for some cases, but if possible I'd recommend only setting that environment variable as required and not globally. If required, you could create your own shortcut / batch script that launched RStudio with QT_PLUGIN_PATH set, e.g. https://superuser.com/questions/424001/launch-windows-program-with-custom-environment-variable |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs, per https://github.com/rstudio/rstudio/wiki/Issue-Grooming. Thank you for your contributions. |
|
This issue has been automatically closed due to inactivity. |
|
It's a bit of a security issue too, isn't it? Running into the same problem with an application I'm developing... |
|
This issue should be reopened as it is unresolved. Currently, I am dealing with the same issue; is it possible to implement @jmcphers suggestion of using a less generic env variable name? That way we can avoid conflicts? |
System details
Steps to reproduce the problem
QT_PLUGIN_PATHin environment beforehand.Describe the problem in detail
Refer to this thread on RStudio Community.
Describe the behavior you expected
It is now mitigated by resetting the environmental variable. But I expect a more elegant solution to minimize the impacts to other softwares.
The text was updated successfully, but these errors were encountered: