Summary: | gconf-sanity-check-2 fails on login | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Robert Bradbury <robert.bradbury> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED INVALID | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
URL: | N/A | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge --info
Gnome .gnomerc-errors file from last attempt to login |
Description
Robert Bradbury
2010-08-01 17:41:54 UTC
Created attachment 240957 [details]
emerge --info
Created attachment 240959 [details] Gnome .gnomerc-errors file from last attempt to login Fatal errors, such as failure to start the metacity, gnome-panel and nautilus should *ALWAYS* be displayed in a login screen/pop-up windows. Otherwise the novice user has no idea what or how the login failed. If Linux/Gnome is to succeed as a desktop environment the diagnostics should be extremely clear as to "what went wrong". Messages of the form: "Could not send message to GConf daemon: Process /usr/libexec/gconfd-2 received signal 5) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information." are *NOT* helpful to the novice (or even an experienced user with 15-20 *years* of UNIX/Linux experience). The errors should be meaningful and precise! > Could not open or create the file "(null)"; this indicates that there may be a > problem with your configuration, as many programs will need to create files in > your home directory. The error was "Failed to create file '/home/chrome/.tmpdir> /gconf-test-locking-file-K8GQGV': No such file or directory" (errno = 2).
This is your problem.
|