make schemas registration use error logging

Merging package from Bug 50148 here as they are duplicates of each other.

I installed the package manager "Automatix" and updated Java and a few other codecs as well. Everything was fine until I shutdown and rebooted. When I logged in I now have the exact issues detailed in this report.

I ran the...

sudo apt-get upgrade

Which seems to have fixed the issue regarding the desk panels where as before I minimized and the windows would disapear, now the properly dock.

I also notcied that my time format has reverted back to the correct display. Before it was shown just
4:37 PM and now it is shown Sun Jun 18, 4:37 PM
------------------
I still can't run any applications that require input of the root password

I still get the theme error.

My keboard is still messed up where I can't hold down a key to repeat it I have to tap it repeatedly.

Still can't open trash bin

All my menus are still missing all the icons next to the application name.
------------------

I had the same problem after a fresh install and then a full upgrade.
To fix it I had to reregister the gconf schemas
(howto here: http://ubuntuforums.org/showpost.php?p=1164346&postcount=11)

Hope this helps someone...

Are all these bugs about Automatix? It's not supported by Ubuntu at all and a separate project.

Hi, no I hadn't used automatix at all. I have since had to do a complete reinstall so the problem is no longer an issue for me. However, I believe a fix was posted on the forums to rebuild the default schema files.

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>]On Behalf Of
Daniel Holbach
Sent: 6 July 2006 1:24 PM
To: <email address hidden>
Subject: [Bug 50150] Re: Configuration editor reports that no schema can
befound since latest dapper updates

Are all these bugs about Automatix? It's not supported by Ubuntu at all
and a separate project.

--
Configuration editor reports that no schema can be found since latest dapper updates
https://launchpad.net/bugs/50150

config-manager not involved. Closing this task.

metacity-themes not involved. Closing this task.

what schemas did people have to reinstall? Some people had similar issue but that's not likely to be due to gconf, maybe some random error on the target system leading to have the schemas not installed?

I happened to reboot this weekend and had a shock. What I ended up doing was just downgrading to Gnome 2.14. It seems to be a problem with the GConf schemas but I just decided to downgrade everything and wait until someone else fixed it.

Downgrading is rather awkward with the Debian system but I've found the easiest way is to remove Gtk and then everything that depends on it will be removed (although all your settings will remain as long as you don't purge as well). Then just make sure that you have dapper in your /etc/apt/sources.list and set to be the default in /etc/apt/preferences and reinstall what you want.

Some things like *-common are left over because they do not depend on libgtk. A simple command-line which may be helpful to downgrade these is:

$ for pkg in `dpkg -l | grep ^ii| grep 2.15 | cut -d" " -f3`; do version=`apt-cache show $pkg | grep Version | grep 2.14 | cut -d" " -f2`; sudo apt-get install $pkg=$version; done

Just make sure there's nothing else that happens to have a version number of 2.15 (I didn't have anything on my system).

Hopefully someone will fix the schema issue soon so upgrades will go smoothly.

-- Tamara

Ok, I upgraded back to Gnome 2.15 and used the fix in the link:

$ sudo gconf-schemas --register /usr/share/gconf/schemas/*.schemas

This should probably be added to the gconf2.postinst to end further confusion.

Well, here's a patch to the gconf2.postinst so hopefully it will be added.

Downgrading is not part of the normal workflow. You can do it using apt pinning by example. Your patch is not correct, there is no reason to register all the schemas on gconf installation, all the packages shipping a schemas register it themself

"Your patch is not correct, there is no reason to register all the schemas on gconf installation, all the packages shipping a schemas register it themself"

So then why were all schemas lost upon upgrading gconf?

probably a bug somewhere on an issue on your machine during the upgrade. If there is a bug the right way is to fix it and not to register all the schemas for eveybody as a workaround

marking as confirmed by the number of duplicates, sometime goes wrong with schemas registration on upgrade sometimes. We don't log schemas registration at the moment which makes not easy to know what happened after that. Something that should be worked next cycle

There's already a call to gconf-schemas --register-all in gconf's postinst on installation, I don't think we should reregister all schemas on upgrade, but we could switch to triggers to have more maintainable scripts.

Dunno what's going wrong here either.