Bug#854343: [Pkg-utopia-maintainers] Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS

2017-02-08 Thread Tilo Villwock
> 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

Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS

2017-02-06 Thread 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 resolv.conf (e.g. 'search domain.orgdomain.org'). Right now I have

Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS

2017-02-14 Thread Tilo Villwock
> 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

Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS

2017-02-10 Thread Tilo Villwock
> 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:

Bug#836939: gnome-settings-daemon: Screen brightness defaults to a very low value and can't be changed with Function Keys, Applet or in System Settings

2016-09-07 Thread Tilo Villwock
Am Mittwoch, den 07.09.2016, 13:35 +0200 schrieb Michael Biebl: > Am 07.09.2016 um 13:24 schrieb Tilo Villwock: > > > > > ... > > Sep  7 12:54:05 yavin4 gnome-settings-[3260]: Failed to create > > GnomeRRScreen: Methode »GetResources« gab Typ > > »(ua(uxiu

Bug#836939: gnome-settings-daemon: Screen brightness defaults to a very low value and can't be changed with Function Keys, Applet or in System Settings

2016-09-07 Thread Tilo Villwock
Am Mittwoch, den 07.09.2016, 14:06 +0200 schrieb Michael Biebl: > Am 07.09.2016 um 13:59 schrieb Tilo Villwock: > > > > Am Mittwoch, den 07.09.2016, 13:35 +0200 schrieb Michael Biebl: > > > > > > Am 07.09.2016 um 13:24 schrieb Tilo Villwock: > > > >

Bug#836939: gnome-settings-daemon: Screen brightness defaults to a very low value and can't be changed with Function Keys, Applet or in System Settings

2016-09-07 Thread Tilo Villwock
Package: gnome-settings-daemon Version: 3.21.90-2 Severity: important What led up to the situation? A: booting and logging in What exactly did you do (or not do) that was effective (or ineffective)? A: using the function keys, the applet in the top bar and tried accessing the settings panel

Bug#836939: gnome-settings-daemon: Screen brightness defaults to a very low value and can't be changed with Function Keys, Applet or in System Settings

2016-09-14 Thread Tilo Villwock
cosmetic and I don't mind it as long as the brightness controls work again. Am Mittwoch, den 07.09.2016, 15:15 +0200 schrieb Michael Biebl: > Am 07.09.2016 um 13:24 schrieb Tilo Villwock: > > > > ... > > Sep  7 12:54:05 yavin4 gnome-settings-[3260]: Failed to create >