Take the 2-minute tour ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems.. It's 100% free, no registration required.

A lot of times when I (un)install packages, I get strange warning messages. Here's a snippet:

Processing triggers for libglib2.0-0 ...
Processing triggers for man-db ...
Processing triggers for desktop-file-utils ...
Processing triggers for gnome-menus ...
Processing triggers for menu ...
Processing triggers for gconf2 ...
WARNING: node <gettext_domain> not understood below <schema>
WARNING: node <gettext_domain> not understood below <schema>
WARNING: node <gettext_domain> not understood below <schema>
WARNING: node <gettext_domain> not understood below <schema>
WARNING: node <gettext_domain> not understood below <schema>
WARNING: node <gettext_domain> not understood below <schema>
WARNING: node <gettext_domain> not understood below <schema>
WARNING: node <gettext_domain> not understood below <schema>
Processing triggers for hicolor-icon-theme ...
Processing triggers for shared-mime-info ...

Anyone knows what causes this? These seem like harmless messages, but what do they mean? How to I get rid of them?

[update] Running sudo gconf-schemas --register-all doesn't help, and gives me the same warning messages.

[note] I use Debian Squeeze.

share|improve this question
3  
They are Gnome warning messages. Given that Gnome's CRITICAL messages are commonplace and not considered bugs by the Gnome maintainers, I wouldn't worry about a mere WARNING. –  Gilles Feb 4 '11 at 23:33
add comment

3 Answers

up vote 1 down vote accepted
+100

Use grep gettext /usr/share/gconf/schemas/*. Identify the .schemas file containing the issue and then take action upon the related package(either reinstall or update to later version).

Anjuta for eg. had an issue just like that.

share|improve this answer
    
Was it a bug in Anjuta? –  Tshepang Mar 24 '11 at 9:44
1  
add comment

I think this has something to do with gconf2's schema files located at /usr/share/gconf/schemas.

Try to register the schemas again:

$ sudo gconf-schemas --register-all

gconf-schemas(8) says:

--register-all  
      clean up the GConf database and register all schemas again.  
      This might be neccessary if your gconf database becomes corrupted.
share|improve this answer
add comment

This fixed it for me:

$ sudo apt-get install gconf-defaults-service
share|improve this answer
2  
This didn't work for me. Do you have an example... which package you installed resulted in the warning messages getting displayed, which got fixed by installing gconf-defaults-service? –  Tshepang Aug 1 '11 at 8:56
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.