Re: Problems found in /var/log/messages: gdm related.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dan Thurman wrote:

Hum...  I cannot figure out how to fix this particular issue.
I have tried to look for information in forums and mailers
but have not found any solutions to this.  Can you take a
look at the following and perhaps you might already know
of a solution?

/var/log/messages:
==============================================
Oct 30 16:42:26 bronze gdm-simple-greeter[15590]: WARNING: gconf key '/apps/gdm/simple-greeter/recent-languages' is unset Oct 30 16:42:26 bronze gconfd (gdm-15650): Error setting value for `/apps/gdm/simple-greeter/recent-languages': Unable to store a value at key '/apps/gdm/simple-greeter/recent-languages', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf

Oct 30 16:42:26 bronze gdm-simple-greeter[15590]: WARNING: gconf key '/apps/gdm/simple-greeter/recent-languages' is unset Oct 30 16:42:26 bronze gdm-simple-greeter[15590]: CRITICAL: gdm_option_widget_set_default_item: assertion `item == NULL || gdm_option_widget_lookup_item (widget, item, NULL, NULL, NULL)' failed Oct 30 16:42:31 bronze gconfd (gdm-15650): Could not open saved state file '/var/lib/gdm/.gconfd/saved_state.tmp' for writing: Permission denied
Oct 30 16:42:31 bronze gconfd (gdm-15650): Exiting
Oct 30 16:42:31 bronze gconfd (admin-15784): starting (version 2.22.0), pid 15784 user 'admin' Oct 30 16:42:31 bronze gconfd (admin-15784): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0 Oct 30 16:42:31 bronze gconfd (admin-15784): Resolved address "xml:readwrite:/home/admin/.gconf" to a writable configuration source at position 1 Oct 30 16:42:31 bronze gconfd (admin-15784): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
==============================================

1) Not sure how to set the gconf key and path
   /apps/gdm/simple-greeter/recent-languages
   and /apps does not exist.

2) Seems that gconf path file is there:
 # cd /etc/gconf/2
 # ls
 evoldap.conf  local-defaults.path  local-mandatory.path  path

3) gconfd was not doubly started, AFAIK - checked pgrep gconfd
   and only one processID exist.

4) There are no locks located in ~/.gconf*/*locks

I have removed and reinstalled gdm but that did not help.

Not sure what to do at this point...

Thanks!
Dan

Sorry, I missed the very beginning of gdm start, so here it is...

================================================
Oct 30 16:42:09 bronze gconfd (gdm-15650): starting (version 2.22.0), pid 15650 user 'gdm' Oct 30 16:42:09 bronze gconfd (gdm-15650): Failed to load source "xml:readwrite:/var/lib/gdm/.gconf": Couldn't resolve address for configuration source: Can't read from or write to the XML root directory in the address "xml:readwrite:/var/lib/gdm/.gconf" Oct 30 16:42:09 bronze gconfd (gdm-15650): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0 Oct 30 16:42:09 bronze gconfd (gdm-15650): Resolved address "xml:readonly:/etc/gconf/gconf.xml.system" to a read-only configuration source at position 1 Oct 30 16:42:09 bronze gconfd (gdm-15650): Resolved address "xml:readonly:/var/lib/gdm/.gconf.mandatory" to a read-only configuration source at position 2 Oct 30 16:42:09 bronze gconfd (gdm-15650): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 3 Oct 30 16:42:09 bronze gconfd (gdm-15650): None of the resolved addresses are writable; saving configuration settings will not be possible Oct 30 16:42:09 bronze gconfd (gdm-15650): No writable configuration sources successfully resolved. May be unable to save some configuration changes Oct 30 16:42:09 bronze gconfd (gdm-15650): Unable to open saved state file '/var/lib/gdm/.gconfd/saved_state': Permission denied Oct 30 16:42:09 bronze gconfd (gdm-15650): Failed to open saved state file: Failed: Failed to open gconfd logfile; won't be able to restore listeners after gconfd shutdown (Permission denied) Oct 30 16:42:12 bronze gconfd (gdm-15650): Failed to log addition of listener gdm-simple-greeter (Failed: Failed to open gconfd logfile; won't be able to restore listeners after gconfd shutdown (Permission denied)); will not be able to restore this listener on gconfd restart, resulting in unreliable notification of configuration changes. Oct 30 16:42:13 bronze gdm-simple-greeter[15590]: WARNING: StartWithSettingsPrefix org.freedesktop.DBus.Error.NoReply raised: Message did not receive a reply (timeout by message bus)#012 Oct 30 16:42:13 bronze gdm-simple-greeter[15590]: WARNING: Couldn't start settings daemon Oct 30 16:42:13 bronze gdm-simple-greeter[15590]: WARNING: gconf key '/apps/gdm/simple-greeter/recent-languages' is unset Oct 30 16:42:13 bronze gconfd (gdm-15650): Failed to open saved state file: Failed: Failed to open gconfd logfile; won't be able to restore listeners after gconfd shutdown (Permission denied)
================================================

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux