touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #108849
[Bug 1502226] Re: error message "dnsmasq: failed to create listening socket for 0.0.0.0: Address already in use" doesn't explain which port number it refers to
Marking Incomplete pending an answer to Simon's question. Once answered,
please change the bug status back to New.
It does sound like a fix would need to go upstream though, rather than
this being fixed in Ubuntu only.
** Changed in: dnsmasq (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1502226
Title:
error message "dnsmasq: failed to create listening socket for 0.0.0.0:
Address already in use" doesn't explain which port number it refers to
Status in dnsmasq package in Ubuntu:
Incomplete
Bug description:
The error message "dnsmasq: failed to create listening socket for
0.0.0.0: Address already in use" doesn't explain which port number it
refers to. In case it's an OS message it needs to be catched and
enhanced with necessary information (in order to get any use of the
message).
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: dnsmasq 2.72-3ubuntu0.1
ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl fglrx
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
Date: Fri Oct 2 18:22:22 2015
InstallationDate: Installed on 2015-04-20 (165 days ago)
InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2)
PackageArchitecture: all
ProcEnviron:
TERM=screen
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: dnsmasq
UpgradeStatus: Upgraded to vivid on 2015-04-24 (160 days ago)
mtime.conffile..etc.dnsmasq.conf: 2015-06-13T18:46:46.597888
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1502226/+subscriptions
References