Hi Rostislav!
Am 12.03.2016 um 01:08 schrieb Rostislav Pehlivanov:
> Actually, I'm still getting a crash.
> Managed to run systemd-resolved with gdb, here's the output
>
>
> sudo gdb --args /lib/systemd/systemd-resolved
> [0]
...
>
> Maybe it's an upstream bug?
I g
Actually, I'm still getting a crash.
Managed to run systemd-resolved with gdb, here's the output
sudo gdb --args /lib/systemd/systemd-resolved
[0]
GNU gdb (Debian 7.10-1+b1) 7.10
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or la
On 03/09/16, Rostislav Pehlivanov wrote:
> Upgrading to the latest libnss3 (3.23) fixes the problem.
libnss3 is crypto library by mozilla, it is not related anyhow to name
resolution and glibc nss subsystem, it is not used by systemd, and very
unlikely to affect this bug anyhow. So, if this pro
Upgrading to the latest libnss3 (3.23) fixes the problem.
Since the bug has been fixed could the maintainers close it?
Thanks
Package: libnss-resolve
Version: 229-2
Severity: important
Dear maintainer:
If systemd-resolve is used as the default system dns resolver
(by replacing "dns" inside /etc/nsswitch.conf with "resolve"),
the process handling the resolving "/lib/systemd/systemd-resolved"
started by the service system
5 matches
Mail list logo
