please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1723956
Title:
Pretty much every single one that would do a hostname lookup it seems.
Tried ping, ping6, nc, wget; they all crash.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1723956
Thanks, adding a systemd task to this bug for libnss-resolve.
It may be that this bug is only reproducible in 17.04 because that was
the only release in which libnss-resolve was installed by default. (We
dropped this package from ubuntu-standard in 17.10.)
This also may not be fixable on the
btw, the bug description says 'several network applets'. Which besides
nslookup do you see this with?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1723956
Title:
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1723956
Title:
busybox-static: several
Sure, here we go. It might be worth to note that this system was
installed as 12.04 or 12.10 and dist-upgraded ever since, so maybe this
would explain some oddities, although in general everything works just
fine.
libc6:
Installed: 2.24-9ubuntu2.2
Candidate: 2.24-9ubuntu2.2
Version table:
Thanks. Loading busybox-static-dbgsym and retracing this with gdb, I
see the following backtrace:
(gdb) thread apply all bt full
Thread 1 (Thread 0x11bb880 (LWP 31592)):
#0 0x in ?? ()
No symbol table info available.
#1 0x7f601bb0af90 in
Steve, so I just manually gather a core dump and attach it here? I
assumed this is what apport is for. I uploaded the crash report using
the standard crash report window that pops up when I opened the issue.
Do they just go straight to /dev/null instead of the maintainers?
** Attachment added:
$ busybox nslookup google.com 8.8.8.8
Server:8.8.8.8
Address 1: 8.8.8.8 google-public-dns-a.google.com
Name: google.com
Address 1: 2607:f8b0:400a:809::200e sea15s12-in-x0e.1e100.net
Address 2: 172.217.3.206 sea15s12-in-f14.1e100.net
$
Not reproducible here. Would need a backtrace in
9 matches
Mail list logo
