[Desktop-packages] [Bug 1613751] Re: journald forwards to syslog with facility=KERN on everything
** No longer affects: network-manager (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1613751 Title: journald forwards to syslog with facility=KERN on everything Status in systemd: New Status in systemd package in Ubuntu: Confirmed Status in systemd package in Debian: Confirmed Bug description: NetworkManager's copious syslog output is for some reason making its way into my /var/log/kern.log file. This includes a couple dozen lines at startup and a similar amount when connecting to WiFi with DHCP. The NM man page states that the default facility should be DAEMON, as does the NM wiki -- see http://manpages.ubuntu.com/manpages/xenial/man8/NetworkManager.8.html and https://wiki.gnome.org/Projects/NetworkManager/Debugging Hopefully, it goes without saying that the KERN facility is reserved for the kernel and shouldn't be messed with by anything from userland. Nothing in the rsyslog configs references kern.log except the one expected line: /etc/rsyslog.d/50-default.conf:kern.* -/var/log/kern.log Nothing in NetworkManager.conf references syslog or its facilities. Oh, and these messages do also correctly make it to syslog.log. I've no idea how or why they also end up in kern.log, though. This doesn't happen on Ubuntu 14.04: % zgrep -cv kernel: /var/log/kern.log* /var/log/kern.log:0 /var/log/kern.log.1:0 /var/log/kern.log.2.gz:0 /var/log/kern.log.3.gz:0 /var/log/kern.log.4.gz:0 On Ubuntu 16.04.1, NM is the major culprit, although there were also a few lines from gnome-session: % zgrep -cv kernel: /mnt/var/log/kern.log* /mnt/var/log/kern.log:402 /mnt/var/log/kern.log.1:722 % zgrep -v kernel: /mnt/var/log/kern.log* | grep -vc NetworkManager 17 % zgrep -v kernel: /mnt/var/log/kern.log* | fgrep -cve NetworkManager -e 'gnome-session-binary' 0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.0-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 16 06:53:42 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-13 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.0.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.5 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/1 86180F 674c9d27-1bb1-4055-a6e4-07de9abbb586 /org/freedesktop/NetworkManager/ActiveConnection/0 enp0s25 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.0connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1613751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1613751] Re: journald forwards to syslog with facility=KERN on everything
** Bug watch added: Debian Bug tracker #837893 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837893 ** Also affects: systemd (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837893 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1613751 Title: journald forwards to syslog with facility=KERN on everything Status in systemd: Unknown Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in systemd package in Debian: Unknown Bug description: NetworkManager's copious syslog output is for some reason making its way into my /var/log/kern.log file. This includes a couple dozen lines at startup and a similar amount when connecting to WiFi with DHCP. The NM man page states that the default facility should be DAEMON, as does the NM wiki -- see http://manpages.ubuntu.com/manpages/xenial/man8/NetworkManager.8.html and https://wiki.gnome.org/Projects/NetworkManager/Debugging Hopefully, it goes without saying that the KERN facility is reserved for the kernel and shouldn't be messed with by anything from userland. Nothing in the rsyslog configs references kern.log except the one expected line: /etc/rsyslog.d/50-default.conf:kern.* -/var/log/kern.log Nothing in NetworkManager.conf references syslog or its facilities. Oh, and these messages do also correctly make it to syslog.log. I've no idea how or why they also end up in kern.log, though. This doesn't happen on Ubuntu 14.04: % zgrep -cv kernel: /var/log/kern.log* /var/log/kern.log:0 /var/log/kern.log.1:0 /var/log/kern.log.2.gz:0 /var/log/kern.log.3.gz:0 /var/log/kern.log.4.gz:0 On Ubuntu 16.04.1, NM is the major culprit, although there were also a few lines from gnome-session: % zgrep -cv kernel: /mnt/var/log/kern.log* /mnt/var/log/kern.log:402 /mnt/var/log/kern.log.1:722 % zgrep -v kernel: /mnt/var/log/kern.log* | grep -vc NetworkManager 17 % zgrep -v kernel: /mnt/var/log/kern.log* | fgrep -cve NetworkManager -e 'gnome-session-binary' 0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.0-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 16 06:53:42 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-13 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.0.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.5 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/1 86180F 674c9d27-1bb1-4055-a6e4-07de9abbb586 /org/freedesktop/NetworkManager/ActiveConnection/0 enp0s25 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.0connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1613751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1613751] Re: journald forwards to syslog with facility=KERN on everything
** Summary changed: - NM and gnome-session seem to be syslogging with facility KERN + journald forwards to syslog with facility=KERN on everything ** Package changed: gnome-session (Ubuntu) => systemd (Ubuntu) ** Bug watch added: github.com/systemd/systemd/issues #5640 https://github.com/systemd/systemd/issues/5640 ** Also affects: systemd via https://github.com/systemd/systemd/issues/5640 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1613751 Title: journald forwards to syslog with facility=KERN on everything Status in systemd: Unknown Status in network-manager package in Ubuntu: New Status in systemd package in Ubuntu: New Status in systemd package in Debian: Unknown Bug description: NetworkManager's copious syslog output is for some reason making its way into my /var/log/kern.log file. This includes a couple dozen lines at startup and a similar amount when connecting to WiFi with DHCP. The NM man page states that the default facility should be DAEMON, as does the NM wiki -- see http://manpages.ubuntu.com/manpages/xenial/man8/NetworkManager.8.html and https://wiki.gnome.org/Projects/NetworkManager/Debugging Hopefully, it goes without saying that the KERN facility is reserved for the kernel and shouldn't be messed with by anything from userland. Nothing in the rsyslog configs references kern.log except the one expected line: /etc/rsyslog.d/50-default.conf:kern.* -/var/log/kern.log Nothing in NetworkManager.conf references syslog or its facilities. Oh, and these messages do also correctly make it to syslog.log. I've no idea how or why they also end up in kern.log, though. This doesn't happen on Ubuntu 14.04: % zgrep -cv kernel: /var/log/kern.log* /var/log/kern.log:0 /var/log/kern.log.1:0 /var/log/kern.log.2.gz:0 /var/log/kern.log.3.gz:0 /var/log/kern.log.4.gz:0 On Ubuntu 16.04.1, NM is the major culprit, although there were also a few lines from gnome-session: % zgrep -cv kernel: /mnt/var/log/kern.log* /mnt/var/log/kern.log:402 /mnt/var/log/kern.log.1:722 % zgrep -v kernel: /mnt/var/log/kern.log* | grep -vc NetworkManager 17 % zgrep -v kernel: /mnt/var/log/kern.log* | fgrep -cve NetworkManager -e 'gnome-session-binary' 0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.0-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 16 06:53:42 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-13 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.0.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.5 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/1 86180F 674c9d27-1bb1-4055-a6e4-07de9abbb586 /org/freedesktop/NetworkManager/ActiveConnection/0 enp0s25 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.0connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1613751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1613751] Re: NM and gnome-session seem to be syslogging with facility KERN
This is actually getting worse in Debian stretch, and there affects almost 2 dozen packages, so it might not even be the packages' (NetworkManager, gnome-session) fault. Anyway, https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=858399 ** Bug watch added: Debian Bug tracker #858399 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858399 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1613751 Title: NM and gnome-session seem to be syslogging with facility KERN Status in gnome-session package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: NetworkManager's copious syslog output is for some reason making its way into my /var/log/kern.log file. This includes a couple dozen lines at startup and a similar amount when connecting to WiFi with DHCP. The NM man page states that the default facility should be DAEMON, as does the NM wiki -- see http://manpages.ubuntu.com/manpages/xenial/man8/NetworkManager.8.html and https://wiki.gnome.org/Projects/NetworkManager/Debugging Hopefully, it goes without saying that the KERN facility is reserved for the kernel and shouldn't be messed with by anything from userland. Nothing in the rsyslog configs references kern.log except the one expected line: /etc/rsyslog.d/50-default.conf:kern.* -/var/log/kern.log Nothing in NetworkManager.conf references syslog or its facilities. Oh, and these messages do also correctly make it to syslog.log. I've no idea how or why they also end up in kern.log, though. This doesn't happen on Ubuntu 14.04: % zgrep -cv kernel: /var/log/kern.log* /var/log/kern.log:0 /var/log/kern.log.1:0 /var/log/kern.log.2.gz:0 /var/log/kern.log.3.gz:0 /var/log/kern.log.4.gz:0 On Ubuntu 16.04.1, NM is the major culprit, although there were also a few lines from gnome-session: % zgrep -cv kernel: /mnt/var/log/kern.log* /mnt/var/log/kern.log:402 /mnt/var/log/kern.log.1:722 % zgrep -v kernel: /mnt/var/log/kern.log* | grep -vc NetworkManager 17 % zgrep -v kernel: /mnt/var/log/kern.log* | fgrep -cve NetworkManager -e 'gnome-session-binary' 0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.0-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 16 06:53:42 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-13 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.0.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.5 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/1 86180F 674c9d27-1bb1-4055-a6e4-07de9abbb586 /org/freedesktop/NetworkManager/ActiveConnection/0 enp0s25 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.0connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1613751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1670875] Re: "Fake" transparency, w/ Flashback session and non-compositing WM, no longer works
Nevermind, it looks like support for background images in terminal widgets has been removed altogether, as explained here- https://bugs.launchpad.net/terminator/+bug/1635704 ** Changed in: gnome-terminal (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1670875 Title: "Fake" transparency, w/ Flashback session and non-compositing WM, no longer works Status in gnome-terminal package in Ubuntu: Invalid Bug description: In Ubuntu 14.04 and earlier, gnome-terminal's transparent background option works well with gnome-session-flashback and a non-compositing window manager. I actually use xmonad, but metacity --no-composite shows the same behavior: instead of real transparency, the portion of the desktop background corresponding to the terminal window's relative position is drawn as the background, and is updated when the window moves. The attached screenshot demonstrates what this looks like in 14.04 with metacity. In Ubuntu 16.04, this no longer works: a solid black background is displayed instead. However, if I downgrade gnome-terminal to the trusty packages, it works as before. To reproduce: 1. execute sudo apt-get install gnome-session-flashback 2. log in with 'GNOME Flashback (Metacity)' session 3. start gnome-terminal and set background to transparent 4. execute metacity --no-composite --replace ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Mar 7 14:52:53 2017 InstallationDate: Installed on 2017-02-19 (16 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1670875/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1670875] [NEW] "Fake" transparency, w/ Flashback session and non-compositing WM, no longer works
Public bug reported: In Ubuntu 14.04 and earlier, gnome-terminal's transparent background option works well with gnome-session-flashback and a non-compositing window manager. I actually use xmonad, but metacity --no-composite shows the same behavior: instead of real transparency, the portion of the desktop background corresponding to the terminal window's relative position is drawn as the background, and is updated when the window moves. The attached screenshot demonstrates what this looks like in 14.04 with metacity. In Ubuntu 16.04, this no longer works: a solid black background is displayed instead. However, if I downgrade gnome-terminal to the trusty packages, it works as before. To reproduce: 1. execute sudo apt-get install gnome-session-flashback 2. log in with 'GNOME Flashback (Metacity)' session 3. start gnome-terminal and set background to transparent 4. execute metacity --no-composite --replace ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Mar 7 14:52:53 2017 InstallationDate: Installed on 2017-02-19 (16 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "Screenshot_ubutest-legacy-bios_2017-03-07_14:50:53.png" https://bugs.launchpad.net/bugs/1670875/+attachment/4833193/+files/Screenshot_ubutest-legacy-bios_2017-03-07_14%3A50%3A53.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1670875 Title: "Fake" transparency, w/ Flashback session and non-compositing WM, no longer works Status in gnome-terminal package in Ubuntu: New Bug description: In Ubuntu 14.04 and earlier, gnome-terminal's transparent background option works well with gnome-session-flashback and a non-compositing window manager. I actually use xmonad, but metacity --no-composite shows the same behavior: instead of real transparency, the portion of the desktop background corresponding to the terminal window's relative position is drawn as the background, and is updated when the window moves. The attached screenshot demonstrates what this looks like in 14.04 with metacity. In Ubuntu 16.04, this no longer works: a solid black background is displayed instead. However, if I downgrade gnome-terminal to the trusty packages, it works as before. To reproduce: 1. execute sudo apt-get install gnome-session-flashback 2. log in with 'GNOME Flashback (Metacity)' session 3. start gnome-terminal and set background to transparent 4. execute metacity --no-composite --replace ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Mar 7 14:52:53 2017 InstallationDate: Installed on 2017-02-19 (16 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1670875/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1613751] [NEW] NM and gnome-session seem to be syslogging with facility KERN
Public bug reported: NetworkManager's copious syslog output is for some reason making its way into my /var/log/kern.log file. This includes a couple dozen lines at startup and a similar amount when connecting to WiFi with DHCP. The NM man page states that the default facility should be DAEMON, as does the NM wiki -- see http://manpages.ubuntu.com/manpages/xenial/man8/NetworkManager.8.html and https://wiki.gnome.org/Projects/NetworkManager/Debugging Hopefully, it goes without saying that the KERN facility is reserved for the kernel and shouldn't be messed with by anything from userland. Nothing in the rsyslog configs references kern.log except the one expected line: /etc/rsyslog.d/50-default.conf:kern.* -/var/log/kern.log Nothing in NetworkManager.conf references syslog or its facilities. Oh, and these messages do also correctly make it to syslog.log. I've no idea how or why they also end up in kern.log, though. This doesn't happen on Ubuntu 14.04: % zgrep -cv kernel: /var/log/kern.log* /var/log/kern.log:0 /var/log/kern.log.1:0 /var/log/kern.log.2.gz:0 /var/log/kern.log.3.gz:0 /var/log/kern.log.4.gz:0 On Ubuntu 16.04.1, NM is the major culprit, although there were also a few lines from gnome-session: % zgrep -cv kernel: /mnt/var/log/kern.log* /mnt/var/log/kern.log:402 /mnt/var/log/kern.log.1:722 % zgrep -v kernel: /mnt/var/log/kern.log* | grep -vc NetworkManager 17 % zgrep -v kernel: /mnt/var/log/kern.log* | fgrep -cve NetworkManager -e 'gnome-session-binary' 0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.0-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 16 06:53:42 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-13 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.0.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.5 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/1 86180F 674c9d27-1bb1-4055-a6e4-07de9abbb586 /org/freedesktop/NetworkManager/ActiveConnection/0 enp0s25 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.0connected started full enabled enabled enabled enabled enabled ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "kern.log" https://bugs.launchpad.net/bugs/1613751/+attachment/4721988/+files/kern.log ** Also affects: gnome-session (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1613751 Title: NM and gnome-session seem to be syslogging with facility KERN Status in gnome-session package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: NetworkManager's copious syslog output is for some reason making its way into my /var/log/kern.log file. This includes a couple dozen lines at startup and a similar amount when connecting to WiFi with DHCP. The NM man page states that the default facility should be DAEMON, as does the NM wiki -- see http://manpages.ubuntu.com/manpages/xenial/man8/NetworkManager.8.html and https://wiki.gnome.org/Projects/NetworkManager/Debugging Hopefully, it goes without saying that the KERN facility is reserved for the kernel and shouldn't be messed with by anything from userland. Nothing in the rsyslog configs references kern.log except the one expected line: /etc/rsyslog.d/50-default.conf:kern.* -/var/log/kern.log Nothing in NetworkManager.conf references syslog or its facilities. Oh, and these messages do also correctly
[Desktop-packages] [Bug 1069793] Re: Can't install search engines (Tramples over window.external)
I ended up removing all four addons from my system (since they seem to be unmaintained and/or deprecated); here are the package names: xul-ext-ubufox - Ubuntu modifications for Firefox xul-ext-unity - Firefox extension: Unity Integration xul-ext-webaccounts - Ubuntu Online Accounts extension for firefox xul-ext-websites-integration - Firefox extension: Website Integration -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-firefox-extension in Ubuntu. https://bugs.launchpad.net/bugs/1069793 Title: Can't install search engines (Tramples over window.external) Status in unity-firefox-extension package in Ubuntu: Confirmed Bug description: The addon "Unity Desktop Integration" replaces windows.external with its own object, breaking the ability to install Opensearch plugins from JS ( window.external.AddSearchProvider() ) TESTCASE: 1) Go to http://mycroftproject.com/dlstats.html 2) Choose any of the OpenSearch plugins and click on the name EXPECTED BEHAVIOUR: A modal window should pop up asking if the chosen plugin really should be installed ACTUAL BEHAVIOUR: A modal window pops up stating that the browser does not support OpenSearch plugins To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-firefox-extension/+bug/1069793/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1069793] Re: Can't install search engines (Tramples over window.external)
Bug also exists in fresh installation of 14.04.3. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-firefox-extension in Ubuntu. https://bugs.launchpad.net/bugs/1069793 Title: Can't install search engines (Tramples over window.external) Status in unity-firefox-extension package in Ubuntu: Confirmed Bug description: The addon "Unity Desktop Integration" replaces windows.external with its own object, breaking the ability to install Opensearch plugins from JS ( window.external.AddSearchProvider() ) TESTCASE: 1) Go to http://mycroftproject.com/dlstats.html 2) Choose any of the OpenSearch plugins and click on the name EXPECTED BEHAVIOUR: A modal window should pop up asking if the chosen plugin really should be installed ACTUAL BEHAVIOUR: A modal window pops up stating that the browser does not support OpenSearch plugins To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-firefox-extension/+bug/1069793/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1491969] [NEW] Search extensions from addons.mozilla.org can't be installed
Public bug reported: This seems to be a bug in the Ubuntu version of Firefox -- started with a Mozilla ticket here https://bugzilla.mozilla.org/show_bug.cgi?id=1166508 The short version is that search extensions from addons.mozilla.org fail to install with the error "Sorry, you need a Mozilla-based browser (such as Firefox) to install a search plugin." This can be observed either by navigating directly to, e.g., https://addons.mozilla.org/en- US/firefox/addon/wolfram-alpha-searchextension/ OR by going to Preferences | Search | Add more search engines... in the Firefox menu. I just got a chance to try this immediately after a fresh install of 14.04.3 x64 desktop, fresh /home and everything, and got the same error. So, it seems to clearly be an Ubuntu bug. However, deleting the preinstalled plugins in /usr/lib/mozilla/plugins/ doesn't work around the issue. The only thing that does is restarting in safe mode (via the Firefox help menu). ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1491969 Title: Search extensions from addons.mozilla.org can't be installed Status in firefox package in Ubuntu: New Bug description: This seems to be a bug in the Ubuntu version of Firefox -- started with a Mozilla ticket here https://bugzilla.mozilla.org/show_bug.cgi?id=1166508 The short version is that search extensions from addons.mozilla.org fail to install with the error "Sorry, you need a Mozilla-based browser (such as Firefox) to install a search plugin." This can be observed either by navigating directly to, e.g., https://addons.mozilla.org/en-US/firefox/addon/wolfram-alpha- searchextension/ OR by going to Preferences | Search | Add more search engines... in the Firefox menu. I just got a chance to try this immediately after a fresh install of 14.04.3 x64 desktop, fresh /home and everything, and got the same error. So, it seems to clearly be an Ubuntu bug. However, deleting the preinstalled plugins in /usr/lib/mozilla/plugins/ doesn't work around the issue. The only thing that does is restarting in safe mode (via the Firefox help menu). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1491969/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1001842] Re: No Audio from HDMI After Switching Monitor Off / On
I'm having the same problem in Ubuntu 14.04.1 LTS using on-board Intel graphics, no binary drivers in sight. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1001842 Title: No Audio from HDMI After Switching Monitor Off / On Status in fglrx-installer package in Ubuntu: Confirmed Bug description: After the 12.04 Update my HDMI audio stops working anytime I turn off or on, my 2nd monitor(plasma TV) System SettingsSound - Output HDMI audio disappears from the list when monitor is turned off or on and does not reappear. see http://askubuntu.com/questions/133575/hdmi-audio-stops-after-tv- turned-off/139265#139265 I'm guessing it has something to do with sink detection and ATI video The only info I've found is after running pactl list Partial copy Sink #0 State: SUSPENDED Name: alsa_output.pci-_01_00.1.hdmi-stereo Description: Turks HDMI Audio [Radeon HD 6000 Series] Digital Stereo (HDMI) Driver: module-alsa-card.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 4 Mute: no Volume: 0: 100% 1: 100% 0: 0.00 dB 1: 0.00 dB balance 0.00 Base Volume: 100% 0.00 dB Monitor Source: alsa_output.pci-_01_00.1.hdmi-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE DECIBEL_VOLUME LATENCY SET_FORMATS Properties: alsa.resolution_bits = 16 device.api = alsa device.class = sound alsa.class = generic alsa.subclass = generic-mix alsa.name = HDMI 0 alsa.id = HDMI 0 alsa.subdevice = 0 alsa.subdevice_name = subdevice #0 alsa.device = 3 alsa.card = 1 alsa.card_name = HD-Audio Generic alsa.long_card_name = HD-Audio Generic at 0xfddfc000 irq 48 alsa.driver_name = snd_hda_intel device.bus_path = pci-:01:00.1 sysfs.path = /devices/pci:00/:00:02.0/:01:00.1/sound/card1 device.bus = pci device.vendor.id = 1002 device.vendor.name = Advanced Micro Devices [AMD] nee ATI device.product.name = Turks HDMI Audio [Radeon HD 6000 Series] device.string = hdmi:1 device.buffering.buffer_size = 65536 device.buffering.fragment_size = 32768 device.access_mode = mmap+timer device.profile.name = hdmi-stereo device.profile.description = Digital Stereo (HDMI) device.description = Turks HDMI Audio [Radeon HD 6000 Series] Digital Stereo (HDMI) alsa.mixer_name = ATI R6xx HDMI alsa.components = HDA:1002aa01,00aa0100,00100200 module-udev-detect.discovered = 1 device.icon_name = audio-card-pci Ports: hdmi-output-0: HDMI / DisplayPort (priority: 5900, not available) Active Port: hdmi-output-0 Formats: pcm I checked before and after. The only difference is hdmi-output-0: HDMI / DisplayPort (priority: 5900, not available) Where not available is the only change I found. Removing cable from HDMI socket and plugging in again, restores audio. Logging in and out again restores audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1001842/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 264691] Re: Please add NM option for connecting to L2TP IPSEC VPN
The network-manager-l2tp package in #37 works very well for me, using Ubuntu 14.04 to connect to a Cisco L2TP/IPsec VPN. (Just a couple of minor tweaks needed to get the IPsec part working, for me.) This project works, is well-integrated with Network Manager, and has an active and helpful developer. It should be added to Ubuntu ASAP, IMO. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/264691 Title: Please add NM option for connecting to L2TP IPSEC VPN Status in NetworkManager: Confirmed Status in “network-manager” package in Ubuntu: Confirmed Status in “network-manager” package in Debian: Invalid Bug description: Binary package hint: network-manager Missing feature: You cannot connect to a (Microsoft) L2TP IPSEC VPN with Network Manager. The server I want to connect to expects a login / password and a PSK. When you do a connection in XP you can see the following details on a connection: Device name: L2TP Server type: PPP Authentication: MS CHAP v2 IPSEC Encryption: IPSEC ESP 3DES Compression: MPPC To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/264691/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
