gnome-appearance-properties tabs don't work/display

Bug #138726 reported by disturbedsaint
28
Affects Status Importance Assigned to Milestone
gtk-qt-engine (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: gnome-control-center

When running gnome-appearance-properties only the first tab (Theme) sort of works (I can click on different themes, but they aren't really selected.

When clicking on any of the other tabs it seems like nothing happens (it still shows the Theme tab), but when I click inside the window it is possible to hit the buttons that should be there (ie open the font-select window), but this window only displays the window itself, all boxes are just white squared.

This happens both with and without compositing.

When running gnome-appearance-properties from the console the only output I get (for whatever reason) is:
/bin/sh: /usr/bin/esd: not found
sh: kde-config: not found
sh: kde-config: not found

There is at least 1 more report from this, which can be found @ the ubuntuforums, http://ubuntuforums.org/showthread.php?p=3338105&highlight=appearance#post3338105

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Are you running Kubuntu? The apperance-capplet works fine here with Ubuntu Gutsy Gibbon. Did you tried to create another user and run the app with it?

Changed in gnome-control-center:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
disturbedsaint (disturbedsaint) wrote :

I used to be running Ubuntu, but later on I installed kubuntu-desktop, to give KDE a try.
I didn't like it, so I removed all KDE related packages, so basically it should've been a generale Ubuntu install.

I didn't try another user.
Unfortunately I won't be able to try it, because I had to format that PC.

For what it's worth:
I upgraded from Feisty, before upgrading I disabled all 3rd party repositories and removed the software that was supplied through them.
Yet it might be an upgrading (KDE related) problem.

Someone in the forums mentioned that with the update from 11.09.2007 (about 130 MB download) it was fixed, see: http://ubuntuforums.org/showthread.php?p=3343081#post3343081
But it didn't fix the problem for me.

Revision history for this message
Joseph Price (pricechild) wrote :

I'm experiencing this problem also.

Since installing this system at tribe 5 I have installed then removed kubuntu-desktop with apt-get

This also affects new users created on the system.

Revision history for this message
Jon (jonathan-semczyk) wrote :

Same here,

Sarted from a feisty and upgraded to tribe 6, I tried kubuntu-desktop and removed it (and all kde related packages)

The gnome-appearance-properties hangs taking all CPU, looks like if I scroll it sometimes refreshes the window.

  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
 2788 jon 25 0 39888 18m 11m R 99.0 3.6 0:17.65 gnome-appearanc

I have the same with new users.

Revision history for this message
sinecure (dave-launchpad) wrote :

Same problem here. Feisty upgraded to Gutsy, installed kubuntu-desktop and xubuntu-desktop, and uninstalled both since starting to use Gutsy. I noticed that clicking on the 'Close' button works, although nothing happens except the window goes away, and the process terminates (iow: the button doesn't react, but still works).

As this isn't exactly a crash, what other information would be useful to help track this down?

Revision history for this message
JMO (jmo707) wrote :

Me too.
It's pretty annoying. I've tried with and withou compositing, and under diferent WM's.

However... before (but after the upgrade from Feisty to Gutsy) it didn't happened. Don't know why it started.

Revision history for this message
sinecure (dave-launchpad) wrote :

For me, this problem started not with the upgrade to Gutsy, but sometime within the last two weeks. For me, however, it's not that the appearance dialog doesn't work, it's display just doesn't update to reflect what you are doing to it.

For now, my workaround is to run:
 gnome-appearance-properties --show-page=(theme|background|fonts|interface|effects)

Note that 'effects' is not in the man page. I can make changes I need to make using that, but I have to remember not to click on a button that would bring another dialog box up. Any dialog box that shows up as a child of the gnome-appearance-properties one is empty, so I can't tell where the buttons are.

Revision history for this message
JMO (jmo707) wrote :

Any dialog, and, in my case at least, any other tab after the firsth one. I can click only on one of them, and the next one has the same problem than the dialog box.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Revision history for this message
JMO (jmo707) wrote :

Here is my backtrace. Wow, firsth time I do that =)

Revision history for this message
Tri Maryanto (antok-tm) wrote :

Here's a hint. Try running as root:

$ sudo su
# gnome-appearance-properties

It won't change any settings but the interface works well.

Revision history for this message
antok.tm (antok-elect-eng) wrote :

I'm guessing it has some connections with gconf backend.

Revision history for this message
Sebastien Bacher (seb128) wrote :

The gdb log seems to indicate that the program exited normally and didn't hang or crash. Could people having the issue try with an another user? Does moving .themes somewhere else makes it work correctly? That might be due to theme installed there. Do you have gtk-qt-engine installed?

Revision history for this message
antok.tm (antok-elect-eng) wrote :

After I removed gtk-qt-engine, the bug seems to disappear.
But I think it's not the best solution.

Revision history for this message
Sebastien Bacher (seb128) wrote :

that's not meant to be a solution bug seems to indicates that's another gtk-qt-engine issue and should be reassigning to it if that's confirmed by other users having the bug

Revision history for this message
JMO (jmo707) wrote : Re: [Bug 138726] Re: gnome-appearance-properties tabs don't work/display

I've tried removing gtk-qt-engine and executing it as root, but it's still
there. However, it seems that moveing .themes to other place solve the
problem.

On 9/26/07, Sebastien Bacher <email address hidden> wrote:
>
> that's not meant to be a solution bug seems to indicates that's another
> gtk-qt-engine issue and should be reassigning to it if that's confirmed
> by other users having the bug
>
> --
> gnome-appearance-properties tabs don't work/display
> https://bugs.launchpad.net/bugs/138726
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
"Así que a través de los crespúsculos interminables soñé y esperé, aunque no
sabía que esperaba. Entonces en la soledad sombría mi añoranza de la luz
creció tanto que no pude descansar más, y levante las manos unidas a la
torre solitaria y ruinosa que se alzaba sobre el bosque al firmamento
desconocido.
Y finalmente decidí escalar esa torre, aunque pudiera caer; ya que es mejor
contemplar el cielo y perecer, que vivir no viendo jamás el día."

H.P. Lovecraft, "El Extraño"

Revision history for this message
Jon (jonathan-semczyk) wrote :

Same here, removing gtk-qt-engine made it work.

2007/9/26, antok.tm <email address hidden>:
>
> After I removed gtk-qt-engine, the bug seems to disappear.
> But I think it's not the best solution.
>
> --
> gnome-appearance-properties tabs don't work/display
> https://bugs.launchpad.net/bugs/138726
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Sebastien Bacher (seb128) wrote :

reassigning to gtk-qt-engine, kubuntu should consider stopping to use this buggy software

Changed in gnome-control-center:
assignee: desktop-bugs → nobody
status: Incomplete → New
Revision history for this message
figjam (figjam) wrote :

Exactly my issue too. (Ok, I dislike 'me-too' responses..)

Upgrade from Feisty to Gutsy, KDE as a 'lets see what it does' option, did not like it and uninstalled it.

Will try the suggestions in this report though.

Revision history for this message
figjam (figjam) wrote :

Works for me too. Brilliant !

Revision history for this message
Davide Saurino (dsaurino) wrote :

Same problem for me. It worked fine in Feisty but it stopped to work after my upgrade to Gusty.
I removed gtk-qt-engine and now it seems to work ok...

Thank you!

Revision history for this message
michelem (michele-marcucci) wrote :
Download full text (7.9 KiB)

I removed that package but I still have the problem:

m1k@goa:~$ gnome-appearance-properties
/usr/share/themes/Clearlooks-gperfection2/gtk-2.0/gtkrc:52: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored.
/usr/share/themes/Clearlooks-gperfection2/gtk-2.0/gtkrc:53: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored.
/usr/share/themes/Clearlooks-gperfection2/gtk-2.0/gtkrc:54: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored.
/usr/share/themes/Peace/gtk-2.0/gtkrc:55: Clearlooks configuration option "sunkenmenu" is not supported and will be ignored.
/usr/share/themes/Peace/gtk-2.0/gtkrc:56: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored.
/usr/share/themes/Peace/gtk-2.0/gtkrc:57: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored.
/usr/share/themes/LegacyHuman/gtk-2.0/gtkrc:55: Clearlooks configuration option "sunkenmenu" is not supported and will be ignored.
/usr/share/themes/LegacyHuman/gtk-2.0/gtkrc:56: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored.
/usr/share/themes/LegacyHuman/gtk-2.0/gtkrc:57: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored.

(gnome-appearance-properties:11164): appearance-properties-WARNING **: Unknown Tag: comment

(gnome-appearance-properties:11164): appearance-properties-WARNING **: Unknown Tag: comment

(gnome-appearance-properties:11164): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_option: assertion `GDK_IS_PIXBUF (pixbuf)' failed

(gnome-appearance-properties:11164): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_option: assertion `GDK_IS_PIXBUF (pixbuf)' failed

(gnome-appearance-properties:11164): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_bits_per_sample: assertion `pixbuf != NULL' failed

(gnome-appearance-properties:11164): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed

(gnome-appearance-properties:11164): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed

(gnome-appearance-properties:11164): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride: assertion `pixbuf != NULL' failed

(gnome-appearance-properties:11164): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_has_alpha: assertion `pixbuf != NULL' failed

(gnome-appearance-properties:11164): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_pixels: assertion `pixbuf != NULL' failed

(gnome-appearance-properties:11164): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(gnome-appearance-properties:11164): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_option: assertion `GDK_IS_PIXBUF (pixbuf)' failed

(gnome-appearance-properties:11164): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_option: assertion `GDK_IS_PIXBUF (pixbuf)' failed

(gnome-appearance-properties:11164): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_bits_per_sample: assertion `pixbuf != NULL' failed

(gnome-appearance-properties:11164): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed

(gnome-appearance-properties:11164): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `...

Read more...

Revision history for this message
grigoris (gregili) wrote :

Removing gtk-qt-engine worked for me too ..

Revision history for this message
vijay (vijayrvijayr) wrote :

Same here,
I upgraded to gutsy gibson recently, I tried kubuntu-desktop and removed it.

The gnome-appearance-properties hangs taking all CPU, looks like if I scroll it sometimes refreshes the window.

I removed the gtk-qt-engine and not it is working.

This thread was very useful,
Thanks everyone.

Revision history for this message
Luca Aluffi (aluffilu) wrote :

Question: if I remove gtk-qt-engine, what will come? I use ubuntu with kubuntu-desktop package installed: will this hardly interfere with "kubuntu side of the street".

Best of my wishes
Luca

Revision history for this message
travis (travisw149) wrote :

On a fresh install of 7.10 server, installed kubuntu then Gnome, I had the problem where the gnome-appearance-properties wasn't updating any of it's tab or controls. Removing gtk-qt-engine fixed the problem for me.
Thanks everyone for the solution.

Revision history for this message
deathwithafi (deathwithafireinside-gmail) wrote :

removing gtk-qt-engine fixed this bug for me as well. thank you all

Revision history for this message
Edgar Almonte (samudhio) wrote :

i dont have gtk-qt-engine and any kde app only gtk app/gnome i can´t change the background using gnome-appearance-properties or even from a image viewer app , when i run gnome-appearance-properties from a terminal i get this :

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

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

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

i try : gnome-appearance-properties --show-page=background

but i get :
(gnome-appearance-properties:7938): Gtk-CRITICAL **: gtk_widget_map: assertion `GTK_WIDGET_VISIBLE (widget)' failed

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

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

and still can´t change the background

Revision history for this message
Yondaime (simulator) wrote :

maybe i have the same error

Feb 2 23:00:30 linux kernel: [ 162.659616] Clocksource tsc unstable (delta = -122025003 ns)
Feb 2 23:00:30 linux anacron[6652]: Anacron 2.3 started on 2008-02-02
Feb 2 23:00:30 linux anacron[6652]: Normal exit (0 jobs run)
Feb 2 23:00:30 linux /usr/sbin/cron[6682]: (CRON) INFO (pidfile fd = 3)
Feb 2 23:00:30 linux /usr/sbin/cron[6683]: (CRON) STARTUP (fork ok)
Feb 2 23:00:30 linux /usr/sbin/cron[6683]: (CRON) INFO (Running @reboot jobs)
Feb 2 23:00:31 linux avahi-daemon[6563]: Server startup complete. Host name is linux.local. Local service cookie is 1558561202.
Feb 2 23:00:37 linux gdmgreeter[6773]: GdkPixbuf-CRITICAL: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed
Feb 2 23:00:37 linux gdmgreeter[6773]: GdkPixbuf-CRITICAL: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed
Feb 2 23:00:37 linux gdmgreeter[6773]: GLib-GObject-CRITICAL: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Feb 2 23:00:38 linux kernel: [ 167.995987] eth1: no IPv6 routers present
Feb 2 23:02:01 linux gdm[6605]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0
Feb 2 23:02:05 linux gdmgreeter[7047]: GdkPixbuf-CRITICAL: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed
Feb 2 23:02:05 linux gdmgreeter[7047]: GdkPixbuf-CRITICAL: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed
Feb 2 23:02:05 linux gdmgreeter[7047]: GLib-GObject-CRITICAL: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Feb 2 23:02:15 linux gdm[7029]: GLib-CRITICAL: g_key_file_get_string: assertion `key_file != NULL' failed
Feb 2 23:02:15 linux gdm[7029]: GLib-CRITICAL: g_key_file_free: assertion `key_file != NULL' failed
Feb 2 23:02:15 linux gdm[7067]: Gtk-WARNING: Ignoring the separator setting
Feb 2 23:02:18 linux kernel: [ 226.856252] mixer_applet2[7001]: segfault at 00000000 eip b796259a esp bfd64080 error 4
Feb 2 23:02:38 linux gdm[7029]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0
Feb 2 23:02:42 linux gdmgreeter[7158]: GdkPixbuf-CRITICAL: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed
Feb 2 23:02:42 linux gdmgreeter[7158]: GdkPixbuf-CRITICAL: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed
Feb 2 23:02:42 linux gdmgreeter[7158]: GLib-GObject-CRITICAL: g_object_unref: assertion `G_IS_OBJECT (object)' failed

after login desktop freeze

Revision history for this message
Mike Basinger (mike.basinger) wrote :

Installing kdelibs4c2a fixes this problem also.

Revision history for this message
Robuntu (rob-cambre) wrote :

That was crazy. It broke (OK I broke it) after uninstalling Kubuntu Desktop or the gOS thing. Which by the way is kinda cool. I did the gtk-qt-engine fix and BAM! Fixed it

Revision history for this message
DarkRaven (holylightsyx) wrote :

Just remove the ".kde" directory under the /home/[your username]/
Then the gnome-appearance-properties will be OK.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Still an issue in Intrepid?

Changed in gtk-qt-engine:
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

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!

Changed in gtk-qt-engine:
status: Incomplete → Invalid
BobSongs (bobspcrepair)
Changed in gtk-qt-engine:
status: Invalid → New
Revision history for this message
BobSongs (bobspcrepair) wrote :

As requested, I'm placing this bug back into "active" status.

I'm currently using Ubuntu Ultimate Edition, 1.9 based on Hardy Heron. Perhaps I have some insight on why this problem is happening. Interestingly, when I run 'gnome-appearance-properties' from my son's account, this issue of the processor hitting 100% doesn't happen. But it does with mine.

I have logged into KDE prior to this. KDE's not my favorite either. But that's not the issue. KDE may be linked to this problem.

I run 'gnome-appearance-properties' from the command line. There is no indication of a problem. The processor just jumps up to 100% functioning and remains there. If I close the applet down, the processor continues to run at 100%.

There is no 'man' entry for this application. So I'm unaware of any switches that will cause this application to run in some kind of "verbose" mode, display everything it's doing. If there's a log file somewhere, I'd be glad to include it for further information.

Steps taken:

* The "sudo apt-get remove gtk-qt-engine" routine failed to resolve the issue.
* The folders .kde and .kde4 were renamed .kde_old and .kde4_old. No success.
* kdelibs4c2a is already installed (mentioned in this thread as a solution). No success.

Revision history for this message
BobSongs (bobspcrepair) wrote :

As root all files/folders were removed from this folder:

/usr/share/themes

Then gnome-appearance-properties was run again. All personally created themes were removed.

Then gnome-appearance-properties was run again. This time a few error messages were thrown, similar to:

"(gnome-appearance-properties:7671): Gtk-WARNING **: Theme directory scalable/stock/128 of theme OSX_Iconset has no size field"

Once the messages stopped (there were about 6 or 8) the processor dropped down to 0%. Closing the application also sees its disappearance from the System Monitor's list (it wouldn't leave before, stuck in its infinite loop).

I will now restore gtk-qt-engine. I doubt this is the cause of the problem.

Revision history for this message
BobSongs (bobspcrepair) wrote :

Synaptic Package Manager was invoked and the standard themes were re-installed. Apart from typical error messages sent to the screen (such as: "/usr/share/themes/Clearlooks-gperfection2/gtk-2.0/gtkrc:52: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored") the gnome-appearance-properties dialog box functions as per usual. gtk-qt-engine was re-installed prior to this.

NOTE: I did not think this important because it did not affect any other user. But at the Ubuntu Ultimate website a 475 Mb package of themes is available. They were installed and working fine under my son's account.

All this to say: there must be some setting in some hidden folder in my session that reacts badly when a larger number of themes are installed. Again: logging out and then logging in to someone else's account did NOT produce this same error.

I am tempted to run Puppy Linux (live), wipe out almost all my hidden folders in my /home/bob folder and try installing this large package again. It won't help to pinpoint the source of the problem. But it will allow me to use this large number of themes again.

NOTE: Compiz-fusion was NOT enabled while gnome-appearance-properties was running.

Revision history for this message
BobSongs (bobspcrepair) wrote :

All personal hidden folders were removed. However, the problem persisted. I did not, however, remove hidden individual files.

Ubuntu was removed and re-installed. I was 99.9997% sure this procedure would result in failure. I was correct.

I have since created a new user account and all works perfectly.

It's obvious that the problem lies in the user's account settings. This is likely due to many of these settings files existing through a few installations and a few upgrades, no doubt.

But which config file? gnome-appearance-properties does not show what it relates to as it runs so the rogue setting file cannot be located. I am at a loss to supply any specific detail such as one particular file or an entry within that file.

What worked for me:
I created a new user account for myself. I opened a terminal. Then I executed 'gksu nautilus' and moved my personal documents to the new folder.

Changed in gtk-qt-engine:
status: New → Incomplete
Revision history for this message
figjam (figjam) wrote :

I was going to ask what happened if you just ran gnome-appearance-properties from the command line.

You could then see if it complains about something specifically.

Revision history for this message
BobSongs (bobspcrepair) wrote :

@figjam:

Actually: no. Entering the command results in ... nothing. The display simply shows a flashing cursor. The processor then jumps to a full 100%, the applet appears, and the processor simply remains at 100%. The wait begins. No changes.

The applet is terminated via normal means (i.e., the Close button). The prompt returns to "normal" and the processor remains at 100%. The System Monitor is required to locate the run-away process and terminate it.

That's the physical effects of the rogue process.

Revision history for this message
BobSongs (bobspcrepair) wrote :

Is there some kind of command-line binary that will force an application into a state of verbosity?

There was once such an application I used when I regularly used <b>Windows</b>. It would display every call an application made, highlighting lines in red whenever some error was encountered (such as attempting to open a non-existent folder, or failing to find a .dll file, that sort of thing).

This sort of application would help immensely in debugging.

@figjam: I don't believe the software is the issue. When run under my son's account, all went as it should. When run under my account, one that sees far more usage (and a greater likelihood of personal config files getting messed up), things went very wrong. Now, this account had a few extra themes added from the Art Manager (gnome-art). That adds to the possibility. However, all personal themes were removed from my /home/bob folder as well (more detail about files in above posts).

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

If you are having problems with gnome-appearance-properties itself please open a separate bug report. This bug is about g-a-s not working in conjunction with gtk-qt-engine in KDE environment.

Changed in gtk-qt-engine:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.