-
-
Notifications
You must be signed in to change notification settings - Fork 69
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
Export to Materia does not work #387
Comments
do you mean it happens only when you use themix-gui and not happens when you manually run ./change-color.sh script from bare materia repo? |
I'm also having this issue. So far I've only tested it with themix-gui. |
test it separately, otherwise issue gonna be closed as not enough info |
What exactly should I be looking for? What info do you need? I'm pretty sure this issue is happening to everyone. |
It appears to also be an issue when manually running ./change-color.sh . |
then, obviously, not a bug of themix app but thanks for checking anyway :) |
btw those permanent random issues with inkscape/resvg are the reason why oomox-gtk-theme (unlike Numix/Materia/Adwaita/etc) is not using any rendered assets and for similar reasons, after it will be updated for gtk4 after gtk4 itself will get a bit more stable than now - i also planning to get rid of scss into direction of bare css |
related ticket: nana-4/materia-theme#594 |
I had the same problem. Dug a little in While these are clearly upstream issues, Themix could at least warn of this. The first time I tried to render the theme, my X server was unresponsive for a few hours and finally crashed. Also, closing the Themix GUI doesn’t actually end the rendering processes, that’s the main issue for me. |
feel free to submit a PR if that's a problem for you :) you could also integrate an antivirus into themix gui, in case if somebody would put a virus into third-party plugin :D |
That’s not serious, is it? But I will see what I can do about the other issues. Happy holidays first of all :) |
Sadly this has had me kinda scratching my head too. If I export oomox it's like 2 seconds and done. If I try materia it's hours, with every CPU core at 100% and nearly chewing up 512Gb of RAM. So for all the people who report "unresponsive" or crashes it's probably because you just ran out of RAM hehe. |
Yes I read the whole thread, doesn't change the fact it's borked. I used oomox years ago, then heard it was scrapped/abandoned. I just found this and gave it a try is all. When I thought maybe there was a mem leak I came looking for some answers and this thread was all that showed up for my terms/phrasing. While this is for the gui with the underlying script borked...this by extension is borked heh. |
then your logic is "borken" - materia is just a dependency - if it's not working itself, it's just not working |
The Materia version that themix-gui-1.15.1 uses is still from May 12, 2021 Some notible changes is that I had to switch from inkscape to resvg since exporting using inkscape has been borked since 2021. Hopefully things still render properly. Issue on themix-gui's repository regarding inkscape and materia. themix-project/themix-gui#387 How I got materia to export with resvg. nana-4/materia-theme#591
I can't seem to force the program to use resvg, I even tried uninstalling inkscape
When using inkscape it takes FOREVER to export the theme and inevitably fails. Is there some way to force resvg that i'm missing?
inkscape gives a ton of
"More than 32 iteration while updating document" errors while going, if you need logs/something to test with please let me know, I can't seem to extract the logs from the program and am not familiar with how it works.
Compiled on arch with themix-full-git, themix-gui-git and themix-materia-git all compiled today.
The text was updated successfully, but these errors were encountered: