Summary: | net-dns/dnsmasq-2.76-r1 segfault in added patch | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marinus Schraal <fosero> |
Component: | Current packages | Assignee: | Patrick McLean <chutzpah> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | conardcox, conikost, erik.badman, james05+gentoo, marduk, slashbeast |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Upstream fix |
Description
Marinus Schraal
2016-12-10 14:42:12 UTC
+1 same problem here. Please revert. It affects all my gentoo machines with DNSMasq. Created attachment 455758 [details, diff]
Upstream fix
(In reply to Felix Janda from comment #2) > Created attachment 455758 [details, diff] [details, diff] > Upstream fix Thanks! Works for me, DNSMasq no longer crashes. (In reply to Felix Janda from comment #2) > Created attachment 455758 [details, diff] [details, diff] > Upstream fix The patch works for me too, thanks. +1 Just confirming So... we got a update in portage to dnsmasq, that does crash on startup, it's been 2 days and still not fixed. Did anyone tested it above building the code? I was about to file a bug that dnsmasq-2.76-r1 prevented app-emulation/lxd from assigning ipv4 and ipv6 addresses to containers. Downgrading to dnsmasq-2.76 works fine. Reading through this bug, it seems that dnsmasq-2.76-r1 is simply crashing, and lxd is not reporting that at the top level container info. Adding to CC author of this happy change, as bug wranglers did not assigned this bug to anyone. I reverted the change, bug #601920 can wait for upstream to make a new release This was fixed since I reverted the change. |