emacs vs. dconf
Whatever is doing this should at least first check for a dconf
executable.
Doesn't happen with -nw.
# aptitude purge dconf
# su - nobody
No directory, logging in with HOME=/
nobody@jidanni2:/$ emacs -Q
** (emacs:3049): CRITICAL **: unable to create '/nonexistent/.cache/dconf'; dconf will not work properly.
nobody@jidanni2:/$ apt-cache policy emacs-snapshot
emacs-snapshot:
Installed: 2:20120208-1
Candidate: 2:20120208-1
Version table:
*** 2:20120208-1 0
500 http://emacs.naquadah.org/ unstable/ Packages
100 /var/lib/dpkg/status
Same with
# su -
# emacs -Q
** (emacs:2546): WARNING **: The connection is closed
# strace emacs -Q > /tmp/f 2>&1 #doesn't help find the culprit, with
surely is some X windows component.
Reply to: