gnome-appearance-properties is very slow and its GUI does not refresh

[Allan Caeg]

I installed Gutsy Beta. Before, I was not having any problem with the new GNOME appearance Preferences App. I do not know what caused this but now, it runs very slowly and the GUI does not refresh. By that, I mean, I can click the App's window and the theme changes but the GUI of the app does not change.

I ran it on the terminal and what I got was

:~$ gnome-appearance-properties

(gnome-appearance-properties:8389): Gtk-CRITICAL **: gtk_radio_button_set_group: assertion `!g_slist_find (group, radio_button)' failed
/bin/sh: /usr/bin/esd: not found

(gnome-appearance-properties:8390): Gtk-CRITICAL **: gtk_widget_map: assertion `GTK_WIDGET_VISIBLE (widget)' failed

(gnome-appearance-properties:8390): Gtk-CRITICAL **: gtk_widget_map: assertion `GTK_WIDGET_VISIBLE (widget)' failed

[Juan Pablo Salazar Bertín (snifer)]

Your terminal output looks like bug #145059, but I don't know if that's causing the slowness.

[Sebastien Bacher (seb128)]

Thank you for your bug. Does it eat CPU while it slow? Does it happen with an another user on the same configuration?

[Allan Caeg (allancaeg)]

Thank you for the replies.

I followed the tip of the guys from https://bugs.launchpad.net/ubuntu/+source/gtk-qt-engine/+bug/138726 and found out that i just have to remove the gtk-qt-engine package. Now it works fine, but I do not know if doing that is the best solution and if it has no unwanted side effect.

As for Sebastien Bacher's question, I cannot test it now that it is fixed for me, but I remember that when I ran the app as root, it was fine.

[Sebastien Bacher (seb128)]

Thank you for the update, look like another gtk-qt-engine issue, reassigning the bug to this one

[Andy Riordan (andycr-mailshack)]

I can confirm having the same problem.

[Andy Riordan (andycr-mailshack)]

I can also confirm that removing gtk-qt-engine fixes it immediately. The problem occurs even if the qt theme is not in use.

[Rob Frohne (frohro)]

I found the same thing. Removing gtk-qt-engine fixes the problem.

[Victor Marin (vms368)]

Hi,

In Ubuntu 6.06 and in 7.04 I remember that gnome-appearance-properties did work like a charm. As soon as one did change the color it had immediate effect in all applications, selected items and window borders. Fast and stable. Reliable.

But in 7.10 and now in 8.04 it does not work so well, regarding that it is not so fast and also it does not change the color of the window borders, even if one closes and starts again the different windows. Also, the selected text within a window (in Firefox or in Gedit, as 2 examples), it also does not change to the new color.

I've found out that for the new color to be reflected in the windows border one has to close and re-start the gnome-appearance-properties application (it does not work to close and start other windows or applications).

And then, for the new color to be in the texts, one has also to close and re-start the respective applications.

The only things which still change correctly and immediately the color it are the selected elements in the menu bars of Gnome and those within the different applications.

[Victor Marin (vms368)]

Hi again,

Not always the colors change even when re-starting gnome-appearance-properties... It simply resist the colors to be changed.

As well, I tried to start gnome-appearance-properties from the terminal as sudo but I get an ERROR message. I attach you the screen image with the error (in Spanish).

It says that: "It cannot be started manager configuration "gnome-settings-daemon". If the agent of configuration of GNOME is not being executed, it is possible that some of the preferences won't work. This can be the symptom of a problem with Bonobo or that an agent of configuration that is not of GNOME (for example KDE) already is active and in conflict with the agent of configuration of GNOME."

And I do not have installed the gtk-qt-engine.

[Jonathan Thomas (echidnaman)]

Is this still an issue in Intrepid?

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!