Thanks for testing
Am 14.02.2017 um 10:50 schrieb Tilo Villwock:
> I only installed the newly created network-manager_1.6.0 package
> though. When this is fixed and a new version gets into the
> repositories. Will my own package be removed automatically in favor of
> the new one?
If you didn't
> Would be great if you can test with this patch applied and report
> back.
So this fixed the problem for me. I patched the source tarball I got
from apt source and created a new package with:
dpkg-buildpackage -rfakeroot -uc -b
I only installed the newly created network-manager_1.6.0
The patch you mention fixed the behavior for me.
Thx,
Martin
On 02/13/2017 10:28 PM, Michael Biebl wrote:
Am 10.02.2017 um 09:49 schrieb Tilo Villwock:
Bug report filed:
https://bugzilla.gnome.org/show_bug.cgi?id=778430
Upstream provided a patch at
Am 10.02.2017 um 09:49 schrieb Tilo Villwock:
>
> Bug report filed:
>
> https://bugzilla.gnome.org/show_bug.cgi?id=778430
Upstream provided a patch at
https://bugzilla.gnome.org/show_bug.cgi?id=778430#c10
Would be great if you can test with this patch applied and report back.
Regards,
Michael
On 10/02/17 03:00, Michael Biebl wrote:
> On Thu, 9 Feb 2017 11:31:19 +0100 =?UTF-8?Q?Martin_Haa=c3=9f?=
> wrote:
>> Same behavior happens here.
>> Is it possible that multiple search domain entries in the dhcp packet
>> trigger this problem? So instead of one entry being
> Tilo, Josh, since you are able to reproduce the issue and I'm not,
> could
> any of you file this issue upstream at
> https://bugzilla.gnome.org/enter_bug.cgi?product=NetworkManager
> and report back with the bug number.
>
> Thanks,
> Michael
>
Bug report filed:
On Mon, 06 Feb 2017 10:14:46 +0100 Tilo Villwock
wrote:
> Package: network-manager
> Version: 1.6.0-1
> Severity: important
> Tags: upstream
>
> Dear Maintainer,
>
> resolving of hostnames stopped working after updating the package and as it
> turns out the search domain
On Thu, 9 Feb 2017 11:31:19 +0100 =?UTF-8?Q?Martin_Haa=c3=9f?=
wrote:
> Same behavior happens here.
> Is it possible that multiple search domain entries in the dhcp packet
> trigger this problem? So instead of one entry being written twice it is
> two entries being
Same behavior happens here.
Is it possible that multiple search domain entries in the dhcp packet
trigger this problem? So instead of one entry being written twice it is
two entries being concatenated without a newline and an additional
'search' keyword at the start of the line.
Following is
> So, interestingly, I can reliably reproduce this on my work network,
> but
> not on VPN (which also provides a search domain, albeit a different
> one).
I can confirm this. When I connect to a VPN the domain entries are
handled correctly. Both the local and the remote domains are configured
Am 08.02.2017 um 05:33 schrieb Josh Triplett:
> So, interestingly, I can reliably reproduce this on my work network, but
> not on VPN (which also provides a search domain, albeit a different
> one).
>
> Also, can you test with just a single domain-search rather than two?
Tried both, doesn't make
On Wed, Feb 08, 2017 at 05:15:56AM +0100, Michael Biebl wrote:
> Am 08.02.2017 um 02:59 schrieb Josh Triplett:
> > On Tue, Feb 07, 2017 at 11:22:19PM +0100, Michael Biebl wrote:
> >> Am 06.02.2017 um 10:14 schrieb Tilo Villwock:
> >>> Package: network-manager
> >>> Version: 1.6.0-1
> >>> Severity:
Am 08.02.2017 um 02:59 schrieb Josh Triplett:
> On Tue, Feb 07, 2017 at 11:22:19PM +0100, Michael Biebl wrote:
>> Am 06.02.2017 um 10:14 schrieb Tilo Villwock:
>>> Package: network-manager
>>> Version: 1.6.0-1
>>> Severity: important
>>> Tags: upstream
>>>
>>> Dear Maintainer,
>>>
>>> resolving of
On Tue, Feb 07, 2017 at 11:22:19PM +0100, Michael Biebl wrote:
> Am 06.02.2017 um 10:14 schrieb Tilo Villwock:
> > Package: network-manager
> > Version: 1.6.0-1
> > Severity: important
> > Tags: upstream
> >
> > Dear Maintainer,
> >
> > resolving of hostnames stopped working after updating the
Am 06.02.2017 um 10:14 schrieb Tilo Villwock:
> Package: network-manager
> Version: 1.6.0-1
> Severity: important
> Tags: upstream
>
> Dear Maintainer,
>
> resolving of hostnames stopped working after updating the package and as it
> turns out the search domain string is being duplicated in
Package: network-manager
Version: 1.6.0-1
Severity: important
Tags: upstream
Dear Maintainer,
resolving of hostnames stopped working after updating the package and as it
turns out the search domain string is being duplicated in resolv.conf (e.g.
'search domain.orgdomain.org'). Right now I have
16 matches
Mail list logo