-
-
Notifications
You must be signed in to change notification settings - Fork 138
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
Throium wont open #704
Comments
QT issue. fixed by adding
|
@PhantomRex123 Tested, could reproduce, tested your fix, and it fixed it. Where did you find the fix? I could add it to the FAQ |
So its kinda weird, the issue starting when i changed from gnome to kde, and by kde setting the qt5 theme it failed to work, now when i saw the issue searched it up on google and found a website which i cannot find anymore lol however found this similar post https://forum.manjaro.org/t/stable-update-2021-07-23-kernels-nvidia-mesa-wine-firefox-thunderbird-virtualbox/74937/28 and i think by setting it to rather than
now its weird cause when running this same exact configuration it seems that with specific qt themes the browser refuses to work So i'll do a bit of testing here and there and try and update you on what works and what doesnt, cause im not very sure myself right now. |
As for the images, it seems right now on my "gtk2" theme and "Windows" themes the browser doesnt work but the rest are working |
after further testing ive concluded that its the theme, and by having that line |
even with this error thorium works - so im fairly confident its something with the themes |
System Details
Problem
This used to happen a while ago, but by simply restarting my pc it would perfectly work. but now whatever i do when i click on throium or try to run it , nothing happens
Screenshots
![image](https://private-user-images.githubusercontent.com/78041469/335983574-f31c40a0-08e1-4f9f-854f-773a74e73c7a.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk4OTczODgsIm5iZiI6MTcxOTg5NzA4OCwicGF0aCI6Ii83ODA0MTQ2OS8zMzU5ODM1NzQtZjMxYzQwYTAtMDhlMS00ZjlmLTg1NGYtNzczYTc0ZTczYzdhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MDIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzAyVDA1MTEyOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWZiMWMwMGU5YzhkMmExM2M2ZDM1YzQ2YjM3N2ZiYzI1ZDE3ZWNlNzFhY2U2NmIyNjlhNmE4MzYwOGNiODE2NTEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.9l4qZ1oY-zCO6BS0pm1exLsSOaRC9IYWP__Ulz5l__8)
Additional Notes
Same thing with the SSE3 package
The text was updated successfully, but these errors were encountered: