-
-
Notifications
You must be signed in to change notification settings - Fork 57
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
mate-appearance-properties loads a CPU core to 100%
#71
Comments
|
Do you have a old .gtkrc or .gtkrc-2.0 file in your user configuration? |
|
Can you remove/save those files for testing? |
|
This file is broken because it pointed to a missing include "/home/ondra/.gtkrc-2.0.mine" |
|
There is also a I am remote from the workstation, but will test it on Monday 14th October. |
|
This may be some other program, like the qt-config tool, that is doing this. I am not sure yet but I'll keep an eye on it. |
|
I deleted |
|
This is very easilly reproducable with kde's "application appearance" system setting. Go to this and setup a gtk theme that is not the default, for example TraditionalOk. This will create 2 files, a proper gtkrc file and a symlink to this. The content of this is: # File created by KDE Gtk Config
# Configs for GTK2 programs
include "/usr/share/themes/TraditionalOk/gtk-2.0/gtkrc"
style "user-font"
{
font_name="Sans Serif "
}
widget_class "*" style "user-font"
gtk-font-name="Sans Serif 9"
gtk-theme-name="TraditionalOk"
gtk-icon-theme-name="oxygen"
gtk-fallback-icon-theme="menta"
gtk-toolbar-style=GTK_TOOLBAR_BOTH
gtk-menu-images=0
gtk-button-images=0This should be handled more elegantly by mate's appearance property setting :) |
|
After some more testing we found that for me the include line causes the problem. In my example this is the line below, commenting it makes all go back to normal. include "/usr/share/themes/TraditionalOk/gtk-2.0/gtkrcI checked and that file does exist, I hope this narrows it down :) |
|
And I tried @flexiondotorg gtkrc and here it is the following line. |
|
Related issue mate-desktop/caja#350 (comment) |
|
For what it's worth, I also just saw this. Deleting the file fixes it: --- begin --- This file was written by KDEYou can edit it in the KDE control center, under "GTK Styles and Fonts"include "/usr/share/themes/Clearlooks/gtk-2.0/gtkrc" style "user-font" gtk-theme-name="Clearlooks" |
|
Ok, I can also confirm the mentioned config file causes 100% CPU load. |
|
Same thing here. MATE 1.10.2 |
|
http://forums.mate-desktop.org/viewtopic.php?f=2&t=1674 here it's advised to simply delete all .gtkrc* files |
|
lol, i had the same thing.... in 2017.... Isn't this actually a GTK bug? |
|
Not sure, but might be GTK+ bug, yes. Were there any upstream reports on that? |
|
Or maybe not. We have some old gtkrc parsing code here... |
|
I can reproduce the issue with gtk2 and mate-control-center 1.8.3 I can't reproduce the issue with gtk3 and mate-control-center 1.18.2 It is solved? |
|
I can no longer reproduce this bug using MATE 1.22, 1.24 or 1.26. I will close this. |
Hi,
When I start I start
System -> Preferences -> AppearanceI see that many of the themes don't have thumbnails and show a question mark icon instead.As a result,
mate-appearance-propertiestries to generate the required thumbnails. This activity loads a single CPU core to 100% and never completes. Upon closingmate-appearance-propertiesthe window is closed but the process continues to run, indefinitely in the background, occupying 100% of a CPU.If I kill the process then CPU load returns to normal, but the next time
mate-appearance-propertiesis executed a CPU core is fully utilised again.Regards, Martin.
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/6615051-mate-appearance-properties-loads-a-cpu-core-to-100?utm_campaign=plugin&utm_content=tracker%2F559197&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F559197&utm_medium=issues&utm_source=github).The text was updated successfully, but these errors were encountered: