From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: 19780@debbugs.gnu.org
Subject: bug#19780: “User has no home directory”
Date: Tue, 13 Oct 2015 14:29:25 +0200 [thread overview]
Message-ID: <87d1wjost6.fsf@gnu.org> (raw)
In-Reply-To: <idj4mhv15e4.fsf@bimsb-sys02.mdc-berlin.net> (Ricardo Wurmus's message of "Tue, 13 Oct 2015 11:31:31 +0200")
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:
> I can confirm that the error disappears when nscd is running. Emacs no
> longer tells me
>
> Error (initialization): User rwurmus has no home directory
>
> when starting it as long as nscd is running.
>
> I would like to note that the version of Emacs that is available through
> Fedora repositories does not need nscd to run (this is on the same
> machine). The error only appears when nscd is not running and the Emacs
> installed via Guix is used.
Earlier, you wrote:
--8<---------------cut here---------------start------------->8---
It is mentioned in /etc/nsswitch.conf:
~~~~~~~
...
passwd: files sss
shadow: files sss
group: files sss
services: files sss
netgroup: files sss
...
~~~~~~~
--8<---------------cut here---------------end--------------->8---
(See <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=19780#74>.)
What happens is that libnss_sss.so was being loaded in your Emacs
process. However, the Emacs process was linked against Guix’s libc,
whereas libnss_sss.so was linked against Fedora’s libc. Hence the
crash.
When nscd is running, NSS extensions are loaded in the nscd process so
there is no such problem.
> Thanks for the help! Now that I’m sure that this is not a general
> problem I can prepare to replace Fedora with GuixSD on my office
> workstation.
\o/
Thanks!
Ludo’.
prev parent reply other threads:[~2015-10-13 12:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <idj4mhv15e4.fsf@bimsb-sys02.mdc-berlin.net>
2015-02-05 13:55 ` bug#19781: 13 failing tests Ricardo Wurmus
2015-02-07 15:45 ` bug#19781: Close Andreas Enge
2015-02-07 17:19 ` bug#19780: 13 failing tests Ludovic Courtès
2015-02-10 12:03 ` Ricardo Wurmus
2015-02-10 12:42 ` Ludovic Courtès
2015-02-10 14:15 ` Ricardo Wurmus
2015-02-10 14:30 ` Ludovic Courtès
2015-02-10 14:59 ` Ricardo Wurmus
2015-02-10 15:49 ` Ludovic Courtès
2015-02-10 16:45 ` Ricardo Wurmus
2015-02-10 17:08 ` Ludovic Courtès
2015-02-11 11:25 ` Ricardo Wurmus
2015-02-11 11:47 ` Ricardo Wurmus
2015-02-11 12:40 ` Ricardo Wurmus
2015-02-13 9:14 ` Ludovic Courtès
2015-02-13 10:33 ` Ricardo Wurmus
2015-02-13 13:20 ` Ludovic Courtès
2015-02-26 16:49 ` Ludovic Courtès
2015-02-28 21:58 ` Ricardo Wurmus
2015-03-02 15:57 ` Ricardo Wurmus
2015-03-03 8:04 ` Ludovic Courtès
2015-03-31 21:18 ` Ludovic Courtès
2015-02-13 13:23 ` Ludovic Courtès
2015-02-13 15:14 ` Ricardo Wurmus
2015-02-13 22:38 ` Ludovic Courtès
2015-10-13 9:59 ` bug#19780: “User has no home directory” (was: bug#19780: 13 failing tests) Ricardo Wurmus
2015-10-13 12:29 ` Ludovic Courtès [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d1wjost6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=19780@debbugs.gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).