Bug#854343: [Pkg-utopia-maintainers] Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS
> 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 properly. --Tilo
Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS
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 to configure the connection manually to resolve this. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages network-manager depends on: ii adduser3.115 ii dbus 1.10.14-1 ii init-system-helpers1.47 ii libaudit1 1:2.6.7-1 ii libbluetooth3 5.43-1 ii libc6 2.24-9 ii libglib2.0-0 2.50.2-2 ii libgnutls303.5.8-1 ii libgudev-1.0-0 230-3 ii libjansson42.9-1 ii libmm-glib01.6.4-1 ii libndp01.6-1 ii libnewt0.520.52.19-1 ii libnl-3-2003.2.27-1 ii libnm0 1.6.0-1 ii libpam-systemd 232-15 ii libpolkit-agent-1-00.105-17 ii libpolkit-gobject-1-0 0.105-17 ii libreadline7 7.0-2 ii libselinux12.6-3 ii libsoup2.4-1 2.56.0-2 ii libsystemd0232-15 ii libteamdctl0 1.26-1 ii libuuid1 2.29.1-1 ii lsb-base 9.20161125 ii policykit-10.105-17 ii udev 232-15 ii wpasupplicant 2.5-2+v2.4-3+b1 Versions of packages network-manager recommends: ii crda 3.18-1 ii dnsmasq-base 2.76-5 ii iptables 1.6.0+snapshot20161117-5 ii iputils-arping 3:20161105-1 ii isc-dhcp-client 4.3.5-3 ii modemmanager 1.6.4-1 ii ppp 2.4.7-1+4 Versions of packages network-manager suggests: pn libteam-utils -- Configuration Files: /etc/NetworkManager/NetworkManager.conf changed: [main] plugins=ifupdown,keyfile [ifupdown] managed=true -- no debconf information
Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS
> 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 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? Thanks --Tilo
Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS
> 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: https://bugzilla.gnome.org/show_bug.cgi?id=778430 --Tilo
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
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(uxiuaua{sv})a(uxiausauaua{sv})a(uxuud)ii)« zurück, aber
> > »(ua(uxiuaua{sv})a(uxiausauaua{sv})a(uxuudu)ii)« wurde erwartet
> > Sep 7 12:54:05 yavin4 gnome-settings-[3260]: failed to get
> > screens: Methode »GetResources« gab Typ
> > »(ua(uxiuaua{sv})a(uxiausauaua{sv})a(uxuud)ii)« zurück, aber
> > »(ua(uxiuaua{sv})a(uxiausauaua{sv})a(uxuudu)ii)« wurde erwartet
> > Sep 7 12:54:06 yavin4 gnome-settings-[3260]: Failed to construct
> > RR screen: Methode »GetResources« gab Typ
> > »(ua(uxiuaua{sv})a(uxiausauaua{sv})a(uxuud)ii)« zurück, aber
> > »(ua(uxiuaua{sv})a(uxiausauaua{sv})a(uxuudu)ii)« wurde erwartet
> > ...
> > Sep 7 12:54:12 yavin4 gnome-shell[3137]: JS LOG: Could not set
> > property Brightness on remote object
> > /org/gnome/SettingsDaemon/Power:
> > GDBus.Error:org.freedesktop.DBus.Error.Failed: Manager is starting
> > or stopping
>
> Does this issue persist after you've restarted gnome-settings-daemon?
>
Frankly I'm not sure how to restart the daemon. I simply killed the
process and after it started again it still wouldn't work. The same log
messages appeared too (about not being able to create a GnomePRScreen
object).
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
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:
> > >
> > > >
> > > >
> > > > ...
> > > > Sep 7 12:54:05 yavin4 gnome-settings-[3260]: Failed to create
> > > > GnomeRRScreen: Methode »GetResources« gab Typ
> > > > »(ua(uxiuaua{sv})a(uxiausauaua{sv})a(uxuud)ii)« zurück,
> > > > aber
> > > > »(ua(uxiuaua{sv})a(uxiausauaua{sv})a(uxuudu)ii)« wurde
> > > > erwartet
> > > > Sep 7 12:54:05 yavin4 gnome-settings-[3260]: failed to get
> > > > screens: Methode »GetResources« gab Typ
> > > > »(ua(uxiuaua{sv})a(uxiausauaua{sv})a(uxuud)ii)« zurück,
> > > > aber
> > > > »(ua(uxiuaua{sv})a(uxiausauaua{sv})a(uxuudu)ii)« wurde
> > > > erwartet
> > > > Sep 7 12:54:06 yavin4 gnome-settings-[3260]: Failed to
> > > > construct
> > > > RR screen: Methode »GetResources« gab Typ
> > > > »(ua(uxiuaua{sv})a(uxiausauaua{sv})a(uxuud)ii)« zurück,
> > > > aber
> > > > »(ua(uxiuaua{sv})a(uxiausauaua{sv})a(uxuudu)ii)« wurde
> > > > erwartet
> > > > ...
> > > > Sep 7 12:54:12 yavin4 gnome-shell[3137]: JS LOG: Could not set
> > > > property Brightness on remote object
> > > > /org/gnome/SettingsDaemon/Power:
> > > > GDBus.Error:org.freedesktop.DBus.Error.Failed: Manager is
> > > > starting
> > > > or stopping
> > >
> > > Does this issue persist after you've restarted gnome-settings-
> > > daemon?
> > >
> >
> > Frankly I'm not sure how to restart the daemon. I simply killed the
> > process and after it started again it still wouldn't work. The same
> > log
> > messages appeared too (about not being able to create a
> > GnomePRScreen
> > object).
>
> rebooting the system is probably the easiest. This way you are sure
> to
> have no leftover processes.
>
>
Sorry I should have mentioned that. I did that too. This occurred first
after I updated the system and rebooted.
Apt history below:
Start-Date: 2016-09-07 09:51:17
Commandline: apt upgrade
Install: libdap23:amd64 (3.18.0-2, automatic), libvpx4:amd64 (1.6.0-2,
automatic), libsimple-http-java:amd64 (4.1.21-1, automatic), libpcre2-
8-0:amd64 (10.22-2, automatic), libefiboot27:amd64 (27-1, automatic),
libefivar27:amd64 (27-1, automatic)
Upgrade: libgnutls28-dev:amd64 (3.5.3-3, 3.5.3-4), libgirepository1.0-
dev:amd64 (1.48.0-3, 1.49.1-2), libgnutlsxx28:amd64 (3.5.3-3, 3.5.3-4),
libsoup-gnome2.4-1:amd64 (2.54.1-1, 2.55.90-1), gnome-control-center-
data:amd64 (1:3.20.1-2, 1:3.21.90-1), libcogl20:amd64 (1.22.0-2,
1.22.2-2), python2.7-dev:amd64 (2.7.12-2, 2.7.12-3), libpangoft2-1.0-
0:amd64 (1.40.1-1, 1.40.2-1), icedove:amd64 (1:45.2.0-4, 1:45.2.0-
4+b1), qtdeclarative5-dev:amd64 (5.6.1-5, 5.6.1-7), glib-networking-
services:amd64 (2.48.2-1, 2.49.90-1), qtdeclarative5-doc:amd64 (5.6.1-
5, 5.6.1-7), libvte-2.91-0:amd64 (0.44.2-1, 0.45.90-2), qml-module-
qtquick-window2:amd64 (5.6.1-5, 5.6.1-7), libgtop2-common:amd64
(2.34.0-1, 2.34.1-2), libserf-1-1:amd64 (1.3.8-3, 1.3.9-1), gir1.2-gtk-
3.0:amd64 (3.20.9-1, 3.21.5-3), gvfs-backends:amd64 (1.28.3-1, 1.29.91-
1), gnome-logs:amd64 (3.20.1-1, 3.21.90-1), gnome-control-center:amd64
(1:3.20.1-2, 1:3.21.90-1), gir1.2-soup-2.4:amd64 (2.54.1-1, 2.55.90-1),
gvfs-bin:amd64 (1.28.3-1, 1.29.91-1), gnome-system-monitor:amd64
(3.20.1-1, 3.21.91-1), qml-module-qtquick2:amd64 (5.6.1-5, 5.6.1-7),
libgirepository-1.0-1:amd64 (1.48.0-3, 1.49.1-2), libcogl-path20:amd64
(1.22.0-2, 1.22.2-2), libfakeroot:amd64 (1.21-1, 1.21-2), foomatic-db-
compressed-ppds:amd64 (20160705-1, 20160830-1), libgnutls-
openssl27:amd64 (3.5.3-3, 3.5.3-4), qt5-qmltooling-plugins:amd64
(5.6.1-5, 5.6.1-7), ardour-data:amd64 (1:5.0~dfsg-2, 1:5.3~dfsg-1),
libgweather-3-6:amd64 (3.20.2-1, 3.20.3-1), libpulsedsp:amd64 (9.0-2,
9.0-3), glib-networking:amd64 (2.48.2-1, 2.49.90-1), libgtk-3-
common:amd64 (3.20.9-1, 3.21.5-3), libgtk-3-0:amd64 (3.20.9-1, 3.21.5-
3), libgjs0e:amd64 (1.45.4-1, 1.45.4-2), gradle:amd64 (2.13-3, 2.13-4),
libpango1.0-0:amd64 (1.40.1-1, 1.40.2-1), pulseaudio:amd64 (9.0-2, 9.0-
3), gstreamer1.0-plugins-good:amd64 (1.8.3-1, 1.8.3-1+b1), python-
imaging:amd64 (3.3.0-1, 3.3.1-1), libcogl-common:amd64 (1.22.0-2,
1.22.2-2), efibootmgr:amd64 (0.12-4, 13-1), gnome-desktop3-data:amd64
(3.20.2-1, 3.21.90-3), bnd:amd64 (2.4.1-4, 2.4.1-5), python2.7-
minimal:amd64 (2.7.12-2, 2.7.12-3), liborc-0.4-0:amd64 (1:0.4.25-1,
1:0.4.26-1), liborc-0.4-0:i386 (1:0.4.25-1, 1:0.4.26-1),
qt
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
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 in System Settings
What was the outcome of this action?
A: nothing happened, but see logs
What outcome did you expect instead?
A: brightes adjusts as expected
---
This is on a Macbook Pro late 2010 with a GeForce 320m using the Nouveau driver.
The following log messages seem to be related:
...
Sep 7 12:54:05 yavin4 gnome-settings-[3260]: Failed to create GnomeRRScreen:
Methode »GetResources« gab Typ
»(ua(uxiuaua{sv})a(uxiausauaua{sv})a(uxuud)ii)« zurück, aber
»(ua(uxiuaua{sv})a(uxiausauaua{sv})a(uxuudu)ii)« wurde erwartet
Sep 7 12:54:05 yavin4 gnome-settings-[3260]: failed to get screens: Methode
»GetResources« gab Typ »(ua(uxiuaua{sv})a(uxiausauaua{sv})a(uxuud)ii)«
zurück, aber »(ua(uxiuaua{sv})a(uxiausauaua{sv})a(uxuudu)ii)« wurde erwartet
Sep 7 12:54:06 yavin4 gnome-settings-[3260]: Failed to construct RR screen:
Methode »GetResources« gab Typ
»(ua(uxiuaua{sv})a(uxiausauaua{sv})a(uxuud)ii)« zurück, aber
»(ua(uxiuaua{sv})a(uxiausauaua{sv})a(uxuudu)ii)« wurde erwartet
...
Sep 7 12:54:12 yavin4 gnome-shell[3137]: JS LOG: Could not set property
Brightness on remote object /org/gnome/SettingsDaemon/Power:
GDBus.Error:org.freedesktop.DBus.Error.Failed: Manager is starting or stopping
...
I was able to set the screen brightness directly by entering the following:
echo 100 > /sys/class/backlight/nv_backlight/brightness
Let me know what else I can provide to track this down.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.6.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gnome-settings-daemon depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.26.0-1
ii gsettings-desktop-schemas3.21.4-2
ii libasound2 1.1.2-1
ii libc62.23-5
ii libcairo21.14.6-1+b1
ii libcanberra-gtk3-0 0.30-3
ii libcanberra0 0.30-3
ii libcolord2 1.3.2-1
ii libcups2 2.1.4-4
ii libfontconfig1 2.11.0-6.7
ii libgdk-pixbuf2.0-0 2.34.0-1
ii libgeoclue-2-0 2.4.3-1
ii libgeocode-glib0 3.20.1-1
ii libglib2.0-0 2.49.6-1
ii libgnome-desktop-3-123.21.90-3
ii libgtk-3-0 3.21.5-3
ii libgudev-1.0-0 230-3
ii libgweather-3-6 3.20.3-1
ii liblcms2-2 2.7-1
ii libnm0 1.2.4-2
ii libnotify4 0.7.6-2
ii libnspr4 2:4.12-2
ii libnss3 2:3.25-1
ii libpam-systemd 231-4
ii libpango-1.0-0 1.40.2-1
ii libpangocairo-1.0-0 1.40.2-1
ii libpolkit-gobject-1-00.105-16
ii libpulse-mainloop-glib0 9.0-3
ii libpulse09.0-3
ii librsvg2-2 2.40.16-1
ii libupower-glib3 0.99.4-3
ii libwacom20.19-1
ii libwayland-client0 1.11.0-2
ii libx11-6 2:1.6.3-1
ii libxext6 2:1.3.3-1
ii libxi6 2:1.7.6-1
ii libxtst6 2:1.2.2-1+b1
ii nautilus-data3.20.3-1
Versions of packages gnome-settings-daemon recommends:
ii iio-sensor-proxy 1.1-1
ii pulseaudio9.0-3
gnome-settings-daemon suggests no packages.
-- no debconf information
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
The mutter update came in today and I can confirm, that everything is
working as expected again. So I guess we can close this bug?
The only thing that's kind of odd is that the overlay for brightness
does this small but noticable wiggling motion on the horizontal axis
now. But that's rather 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
> > GnomeRRScreen: Methode »GetResources« gab Typ
> > »(ua(uxiuaua{sv})a(uxiausauaua{sv})a(uxuud)ii)« zurück, aber
> > »(ua(uxiuaua{sv})a(uxiausauaua{sv})a(uxuudu)ii)« wurde erwartet
> > Sep 7 12:54:05 yavin4 gnome-settings-[3260]: failed to get
> > screens: Methode »GetResources« gab Typ
> > »(ua(uxiuaua{sv})a(uxiausauaua{sv})a(uxuud)ii)« zurück, aber
> > »(ua(uxiuaua{sv})a(uxiausauaua{sv})a(uxuudu)ii)« wurde erwartet
> > Sep 7 12:54:06 yavin4 gnome-settings-[3260]: Failed to construct
> > RR screen: Methode »GetResources« gab Typ
> > »(ua(uxiuaua{sv})a(uxiausauaua{sv})a(uxuud)ii)« zurück, aber
> > »(ua(uxiuaua{sv})a(uxiausauaua{sv})a(uxuudu)ii)« wurde erwartet
> > ...
> > Sep 7 12:54:12 yavin4 gnome-shell[3137]: JS LOG: Could not set
> > property Brightness on remote object
> > /org/gnome/SettingsDaemon/Power:
> > GDBus.Error:org.freedesktop.DBus.Error.Failed: Manager is starting
> > or stopping
>
> I guess you still use mutter 3.20.* but you already have gnome-
> desktop3
> 3.21.*
> I think this one is related to
>
> https://tracker.debian.org/news/794829
>
> Maybe we need a versioned Breaks in mutter to enforce a lock-step
> upgrade.
>
> Let's see if your problem still persists once mutter/libmutter has
> been
> updated.
>
>
