[Touch-packages] [Bug 2021956] Re: crash cups-proxyd
I can confirm the issue on 23.10 with no printers configured -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2021956 Title: crash cups-proxyd Status in cups package in Ubuntu: Confirmed Bug description: Ubuntu IOT Desktop 22.04 LTS # cat /etc/os-release PRETTY_NAME="Ubuntu 22.04.2 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.2 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; UBUNTU_CODENAME=jammy Kernel Version: 5.15.0-1028-intel-iotg # journalctl --no-hostname -b --no-pager | grep cups-proxyd mai 31 11:51:22 cups.cupsd[949]: + PROXY_DAEMON=cups-proxyd mai 31 11:51:22 cups.cupsd[3032]: exec cups-proxyd /var/snap/cups/common/run/cups.sock /run/cups/cups.sock -l --logdir /var/snap/cups/872/var/log mai 31 11:51:23 audit[3032]: SECCOMP auid=4294967295 uid=0 gid=0 ses=4294967295 subj=snap.cups.cupsd pid=3032 comm="cups-proxyd" exe="/snap/cups/872/sbin/cups-proxyd" sig=0 arch=c03e syscall=314 compat=0 ip=0x7fb050c2973d code=0x5 mai 31 11:51:23 kernel: audit: type=1326 audit(1685523083.773:85): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=snap.cups.cupsd pid=3032 comm="cups-proxyd" exe="/snap/cups/872/sbin/cups-proxyd" sig=0 arch=c03e syscall=314 compat=0 ip=0x7fb050c2973d code=0x5 mai 31 11:51:24 kernel: cups-proxyd[3032]: segfault at 18 ip 558e95990d6e sp 7ffe2436a230 error 4 in cups-proxyd[558e9598d000+7000] Error: cups-proxyd[3032]: segfault at 18 ip 558e95990d6e sp 7ffe2436a230 error 4 in cups-proxyd[558e9598d000+7000] Snap list: # snap list Name Version RevTracking Publisher Notes bare 1.0 5 latest/stable canonical✓ base chromium 113.0.5672.1262477 latest/stable canonical✓ - core20 20230503 1891 latest/stable canonical✓ base core22 20230503 634latest/stable canonical✓ base cups 2.4.2-5 872latest/stable openprinting✓ - firefox111.0-2 2432 latest/stable/… mozilla✓ - gnome-3-38-20040+git.6f39565 140latest/stable/… canonical✓ - gnome-42-2204 0+git.587e965 102latest/stable canonical✓ - gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - snap-store 41.3-71-g709398e 959latest/stable/… canonical✓ - snapd 2.59.219122 latest/stable canonical✓ snapd snapd-desktop-integration 0.9 83 latest/stable/… canonical✓ - Reproduced: At every boot OS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2021956/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1978738] Re: systemd-oomd and zram-config services: "Swap is currently not detected; memory pressure usage will be degraded"
@mantas Thanks for letting me know about the bug/fix. Looks like my version was not affected due to slightly different systemd config. Nevertheless, I've added the fix (just in case) and pushed it to lp:~eugenesan/+git/zram-config PPA was updated as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1978738 Title: systemd-oomd and zram-config services: "Swap is currently not detected; memory pressure usage will be degraded" Status in systemd package in Ubuntu: Invalid Status in zram-config package in Ubuntu: Fix Released Bug description: Problem summary: I've installed the zram-config package. By default it creates a zram swap device with half the physical memory size of the system. For instance, in an 8GB RAM system: # swapon NAME TYPE SIZE USED PRIO /dev/zram0 partition 3,8G 1M5 #zramctl NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT /dev/zram0 lzo-rle 3,8G 496K 74,9K 376K 4 [SWAP] The problem is that when systemd-oomd.service is started during boot it doesn't detect that zram swap device because zram-config.service is started later. So when systemd-oomd.service was started the zram device didn't exists yet. This is the message shown during boot: systemd-oomd[587]: Swap is currently not detected; memory pressure usage will be degraded If you restart systemd-oomd.service after boot it's correctly started because zram-config.service was previously loaded and zram device exists. So I think it's just a matter of dependencies during boot process; it's necessary to make zram-config.service be started before systemd-oomd.service (or to make systemd-oomd.service be restarted when zram-config.service is started). Aditional info: --- # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy systemd-oomd systemd-oomd: Instalados: 249.11-0ubuntu3.1 Candidato: 249.11-0ubuntu3.1 Tabla de versión: *** 249.11-0ubuntu3.1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages # apt-cache policy zram-config zram-config: Instalados: 0.7build1 Candidato: 0.7build1 Tabla de versión: *** 0.7build1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/universe arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1978738/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend
Confirming the bug in Xenial. ** Tags removed: amd64 ** Tags added: xenial ** Description changed: After upgrading to Yakkety, when my Ubuntu GNOME laptop resumes from suspend DNS resolution stops working. + + * Also affect Xenial (Unity/GnomeFlashback)since Network-Manager stack + was upgraded to 1.2.6. After resuming, systemd-resolved is running and libnss-resolve is installed, but /etc/resolv.conf contains 127.0.1.1 as the the only name server. The dnsmasq-base package is installed since it is pulled in by both network-manager and lxc1, and both NM and libvirt have spawned instances of dnsmasq: > 1155 pts/2S+ 0:00 grep dnsmasq > 2724 ?S 0:00 dnsmasq -u lxc-dnsmasq --strict-order --bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --listen-address 10.0.3.1 --dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override --except-interface=lo --interface=lxcbr0 --dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative > 2992 ?S 0:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper > 2993 ?S 0:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper > 22879 ?S 0:00 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 --cache-size=0 --conf-file=/dev/null --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d Let me know if you need any extra info. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libnss-resolve 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 7 13:52:40 2016 InstallationDate: Installed on 2015-07-22 (443 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-05 (1 days ago) -- 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/1631241 Title: Name resolution stops working after resume from suspend Status in dnsmasq: Fix Released Status in dnsmasq package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: After upgrading to Yakkety, when my Ubuntu GNOME laptop resumes from suspend DNS resolution stops working. * Also affect Xenial (Unity/GnomeFlashback)since Network-Manager stack was upgraded to 1.2.6. After resuming, systemd-resolved is running and libnss-resolve is installed, but /etc/resolv.conf contains 127.0.1.1 as the the only name server. The dnsmasq-base package is installed since it is pulled in by both network-manager and lxc1, and both NM and libvirt have spawned instances of dnsmasq: > 1155 pts/2S+ 0:00 grep dnsmasq > 2724 ?S 0:00 dnsmasq -u lxc-dnsmasq --strict-order --bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --listen-address 10.0.3.1 --dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override --except-interface=lo --interface=lxcbr0 --dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative > 2992 ?S 0:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper > 2993 ?S 0:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper > 22879 ?S 0:00 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 --cache-size=0 --conf-file=/dev/null --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d Let me know if you need any extra info. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libnss-resolve 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 7 13:52:40 2016 InstallationDate: Installed on 2015-07-22 (443 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-05 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dnsmasq/+bug/1631241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-pac
[Touch-packages] [Bug 1646859] Re: Wifi not working after suspend on 16.10
*** This bug is a duplicate of bug 1639776 *** https://bugs.launchpad.net/bugs/1639776 ** This bug is no longer a duplicate of bug 1631241 Name resolution stops working after resume from suspend ** This bug has been marked a duplicate of bug 1639776 dnsmasq fails to send queries out after suspend disconnects the interface -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1646859 Title: Wifi not working after suspend on 16.10 Status in network-manager package in Ubuntu: New Bug description: After waking from suspend, nm doesn't automatically connect to WiFi, instead nm indicator is showing RJ45 icon like it's connected on wired network but it's not. NM indicator panel doesn't show any WiFi networks and there is no connection. restarting the service or stopping the WiFi antenna using keyboard shortcut don't fix the problem. Only relogging the account or restart fixes the issue. OS: Ubuntu 16.10 Device: DELL Inspiron 13" 7000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1646859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1642507] Re: Not internet after waking from suspend
*** This bug is a duplicate of bug 1639776 *** https://bugs.launchpad.net/bugs/1639776 ** This bug is no longer a duplicate of bug 1631241 Name resolution stops working after resume from suspend ** This bug has been marked a duplicate of bug 1639776 dnsmasq fails to send queries out after suspend disconnects the interface -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1642507 Title: Not internet after waking from suspend Status in network-manager package in Ubuntu: Confirmed Bug description: Release Information: Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety Package Information: network-manager: Installed: 1.2.4-0ubuntu1 Candidate: 1.2.4-0ubuntu1 Version table: *** 1.2.4-0ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status System Information: Dell XPS 15 9550 Wireless: Network controller: Broad com Limited BCM43602 802.11ac Wireless LAN SoC (rev 01) Wired: Wired Ethernet via Apple USB Ethernet Adapter (ID 05ac:1402 Apple, Inc. Ethernet Adapter [A1277]) Problem Description: I have noticed the problem on both wired and wireless. Ever since upgrading to 16.10(from 16.04), the system loses internet after waking from suspend. Internet works fine after a reboot or when powering on normally. "service network-manager restart" fixes the problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 17 09:37:30 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-31 (169 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.80.1 dev enx7cc3a187f0f2 proto static metric 100 default via 192.168.80.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.80.0/24 dev enx7cc3a187f0f2 proto kernel scope link src 192.168.80.209 metric 100 192.168.80.0/24 dev wlp2s0 proto kernel scope link src 192.168.80.225 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2016-10-28 (19 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enx7cc3a187f0f2 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 e6493319-b925-3b33-92a7-259922dccdaa /org/freedesktop/NetworkManager/ActiveConnection/1 wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/1 whymusticry_fast 1 b51f9098-d053-45d7-ba42-97bf2e87bda2 /org/freedesktop/NetworkManager/ActiveConnection/0 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.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1642507/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1633912] Re: Problem with DNS resolution after suspend
*** This bug is a duplicate of bug 1639776 *** https://bugs.launchpad.net/bugs/1639776 ** This bug is no longer a duplicate of bug 1631241 Name resolution stops working after resume from suspend ** This bug has been marked a duplicate of bug 1639776 dnsmasq fails to send queries out after suspend disconnects the interface -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1633912 Title: Problem with DNS resolution after suspend Status in network-manager package in Ubuntu: Confirmed Bug description: I upgraded my laptop to 16.10 yesterday. Sometimes after suspend I have network issues, one time I was not able to connect to a wifi network (might report another bug if this occurees again, but maybe it is related, as in network-manager is in some broken state after suspend). Here is whats happening pretty often: After resume from suspend I have a solid network connection, no problem to ping machines in LAN or on the internet. But DNS resolution is broken until I restart the network-manager service. I ran ubuntu-bug while DNS was broken, so if anything gets log-ed it should be in there. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 16 21:01:09 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-09-28 (18 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.0.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev br-541a0f9bec93 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-541a0f9bec93 proto kernel scope link src 172.18.0.1 192.168.0.0/24 dev wlp58s0 proto kernel scope link src 192.168.0.118 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2016-10-15 (1 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1633845] Re: network-manager does not connect to wifi
*** This bug is a duplicate of bug 1639776 *** https://bugs.launchpad.net/bugs/1639776 ** This bug is no longer a duplicate of bug 1631241 Name resolution stops working after resume from suspend ** This bug has been marked a duplicate of bug 1639776 dnsmasq fails to send queries out after suspend disconnects the interface -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1633845 Title: network-manager does not connect to wifi Status in network-manager package in Ubuntu: Confirmed Bug description: When trying to connect to wifi network, network-manager remains blocked in waiting for authentification state then fails after cca 1min. This started to happen after I updated to kubuntu 16.10. Stopping network manager from service and trying to manually connect with wpa_supplicant works fine. The only way to fix this for me was to stop network manager and/or networking and restart the services sometimes more than once. os: Kubuntu 16.10 network-manager: 1.2.4 hardware: dell xps 9550 network controller: BCM43602 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633845/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1637700] Re: Caching dnsmasq stops resolving after some time
*** This bug is a duplicate of bug 1639776 *** https://bugs.launchpad.net/bugs/1639776 ** This bug is no longer a duplicate of bug 1631241 Name resolution stops working after resume from suspend ** This bug has been marked a duplicate of bug 1639776 dnsmasq fails to send queries out after suspend disconnects the interface -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1637700 Title: Caching dnsmasq stops resolving after some time Status in network-manager package in Ubuntu: New Bug description: Since upgrading to yakkety my network sometimes stops working - it might be related to suspending the laptop. The NetworkManager-managed caching dnsmasq just stops resolving at some point: dig google.com @127.0.1.1 ; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com @127.0.1.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 22521 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;google.com.IN A ;; Query time: 0 msec ;; SERVER: 127.0.1.1#53(127.0.1.1) ;; WHEN: Sat Oct 29 09:12:33 CEST 2016 ;; MSG SIZE rcvd: 28 Networking and upstream DNS are fine: dig google.com @8.8.8.8 ; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com @8.8.8.8 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63345 ;; flags: qr rd ra; QUERY: 1, ANSWER: 16, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;google.com.IN A ;; ANSWER SECTION: google.com. 299 IN A 46.134.208.30 [...] ;; Query time: 43 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Sat Oct 29 09:12:31 CEST 2016 ;; MSG SIZE rcvd: 295 Killing it resolves the issue, dnsmasq gets restarted and works again: ps aux | grep dnsmasq nobody4262 0.0 0.0 54308 2740 ?S01:30 0:00 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 --cache-size=0 --conf-file=/dev/null --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d sudo kill 4262 dig google.com @127.0.1.1 ; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com @127.0.1.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58324 ;; flags: qr rd ra; QUERY: 1, ANSWER: 16, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;google.com.IN A ;; ANSWER SECTION: google.com. 299 IN A 46.134.208.59 [...] ;; Query time: 41 msec ;; SERVER: 127.0.1.1#53(127.0.1.1) ;; WHEN: Sat Oct 29 09:12:54 CEST 2016 ;; MSG SIZE rcvd: 295 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: dnsmasq (not installed) ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 29 09:13:04 2016 InstallationDate: Installed on 2016-05-06 (175 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-06 (175 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: network-manager 1.2.4-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Tags: yakkety third-party-packages Uname: Linux 4.8.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt libvirtd lpadmin lxd plugdev sambashare sbuild sudo vboxusers _MarkForUpload: True modified.conffile..etc.polkit-1.localauthority.50-local.d.org.freedesktop.NetworkManager.pkla: [deleted] nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+so
[Touch-packages] [Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface
I have merged in another bug(s) and updated the name of the bug to be a
bit more "user friendly".
** Summary changed:
- dnsmasq fails to send queries out after suspend disconnects the interface
+ name resolution (dnsmasq) fails to send queries out after suspend/resume
reconnects the interface
--
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/1639776
Title:
name resolution (dnsmasq) fails to send queries out after
suspend/resume reconnects the interface
Status in dnsmasq package in Ubuntu:
Fix Released
Status in network-manager package in Ubuntu:
Invalid
Status in dnsmasq source package in Xenial:
Fix Committed
Status in network-manager source package in Xenial:
Invalid
Status in dnsmasq source package in Yakkety:
Fix Committed
Status in network-manager source package in Yakkety:
Invalid
Status in dnsmasq package in Debian:
Fix Released
Bug description:
[Impact]
* suspend/resume (which involves disconnection of network devices)
leads to dnsmasq failures.
[Test Case]
* suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
failures upon resume.
[Regression Potential]
* The fix was NMU'd in Debian in the version immediately after
16.10's. I believe the regression potential is very low as this is a
clear bug-fix from upstream.
---
Failure is caused by ENODEV return for all dns queries like:
sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33,
0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)
Problem is reported and fixed:
https://bugzilla.redhat.com/show_bug.cgi?id=1367772
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b
I didn't yet test if applying that patch to ubuntu package works. I
will try the patch in a few hours.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: dnsmasq-base 2.76-4
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Nov 7 14:11:51 2016
InstallationDate: Installed on 2037-12-25 (-7718 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: dnsmasq
UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1639568] Re: dnsmasq not updated by NetworkManager on system resume
*** This bug is a duplicate of bug 1639776 *** https://bugs.launchpad.net/bugs/1639776 ** This bug is no longer a duplicate of bug 1631241 Name resolution stops working after resume from suspend ** This bug has been marked a duplicate of bug 1639776 dnsmasq fails to send queries out after suspend disconnects the interface -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1639568 Title: dnsmasq not updated by NetworkManager on system resume Status in network-manager package in Ubuntu: Confirmed Bug description: When the system resumes after sleep dnsmasq is either not updated with new dns information of never resumes operation. Restarting the network-manager service will manually resolve the problem. Everything else seems correct, the DHCP information is correct and shows the correct nameservers, resolv.conf is updated correctly. I am unable to determine if the issue is with dnsmasq not resuming or if the dbus message with the name servers is getting lost. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 6 07:24:44 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-11-03 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) IpRoute: default via 192.168.1.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev wlp58s0 scope link metric 1000 192.168.1.0/24 dev wlp58s0 proto kernel scope link src 192.168.1.218 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 STATE DBUS-PATH CONNECTIONCON-UUID CON-PATH wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/0 The_Magical_Mystery_Tour 4e4fe235-20a0-414a-8ec3-97f65060250e /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1639568/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1629620] Re: DNS resolver stops accepting queries
*** This bug is a duplicate of bug 1639776 *** https://bugs.launchpad.net/bugs/1639776 ** This bug is no longer a duplicate of bug 1631241 Name resolution stops working after resume from suspend ** This bug has been marked a duplicate of bug 1639776 dnsmasq fails to send queries out after suspend disconnects the interface -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1629620 Title: DNS resolver stops accepting queries Status in network-manager package in Ubuntu: Confirmed Bug description: After a while / after resume from suspend, the system becomes unable to respond to DNS queries, with the following output for example: $ nslookup google.com 127.0.1.1 Server: 127.0.1.1 Address: 127.0.1.1#53 ** server can't find google.com: REFUSED This is on an up to date yakkety install. Changing resolv.conf to use 8.8.8.8, or restarting network-manager appears to fix this, at least until it recurs again. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 1 21:28:51 2016 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-08-21 (407 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) IpRoute: default via 192.168.1.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.5 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2016-09-29 (2 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH docker0bridgeconnected /org/freedesktop/NetworkManager/Devices/1 docker0 63f0b05b-f699-4a68-81ce-f62d2c1a247d /org/freedesktop/NetworkManager/ActiveConnection/0 wlp3s0 wifi connected /org/freedesktop/NetworkManager/Devices/4 HOME-1622-5 6df3f2f0-fb86-43b5-802a-d59bc5734be3 /org/freedesktop/NetworkManager/ActiveConnection/2 24:DA:9B:B9:09:0E btdisconnected /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629620/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend
*** This bug is a duplicate of bug 1639776 *** https://bugs.launchpad.net/bugs/1639776 ** This bug has been marked a duplicate of bug 1639776 dnsmasq fails to send queries out after suspend disconnects the interface -- 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/1631241 Title: Name resolution stops working after resume from suspend Status in dnsmasq: Fix Released Status in dnsmasq package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: After upgrading to Yakkety, when my Ubuntu GNOME laptop resumes from suspend DNS resolution stops working. * Also affect Xenial (Unity/GnomeFlashback)since Network-Manager stack was upgraded to 1.2.6. After resuming, systemd-resolved is running and libnss-resolve is installed, but /etc/resolv.conf contains 127.0.1.1 as the the only name server. The dnsmasq-base package is installed since it is pulled in by both network-manager and lxc1, and both NM and libvirt have spawned instances of dnsmasq: > 1155 pts/2S+ 0:00 grep dnsmasq > 2724 ?S 0:00 dnsmasq -u lxc-dnsmasq --strict-order --bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --listen-address 10.0.3.1 --dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override --except-interface=lo --interface=lxcbr0 --dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative > 2992 ?S 0:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper > 2993 ?S 0:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper > 22879 ?S 0:00 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 --cache-size=0 --conf-file=/dev/null --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d Let me know if you need any extra info. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libnss-resolve 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 7 13:52:40 2016 InstallationDate: Installed on 2015-07-22 (443 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-05 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dnsmasq/+bug/1631241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618839] Re: Regression: WiFi connection reconnects, but dead, after waking from standby
*** This bug is a duplicate of bug 1639776 *** https://bugs.launchpad.net/bugs/1639776 ** This bug is no longer a duplicate of bug 1631241 Name resolution stops working after resume from suspend ** This bug has been marked a duplicate of bug 1639776 dnsmasq fails to send queries out after suspend disconnects the interface -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1618839 Title: Regression: WiFi connection reconnects, but dead, after waking from standby Status in network-manager package in Ubuntu: Confirmed Bug description: Bug introduced somewhere between Ubuntu 14.04.3 and 16.04.1 If my Thinkpad T420s awakes from standby, very often the last connected WiFi network is reconnected immediately, but the connection is dysfunctional. ifconfig shows a valid connection with an IPv4 address assigned for the wlp3s0 interface. But there is no traffic, no success on DNS queries on the connection. If I reconnect by clicking the connection in the nm-applet menu, all is fine again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1618839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377924] Re: ecryptfs fails to mount (Unable to link the KEY_SPEC_USER_KEYRING into the KEY_SPEC_SESSION_KEYRING)
The reason for the failure seems to be in default configuration of PAM for SSH. If I understand correctly, PAM is configured to enforce session keys revocation upon termination of parent SSHD process: --- /etc/pam.d/sshd --- ... # Create a new session keyring. sessionoptional pam_keyinit.so force revoke ... --- Some environments connect using ssh and then "detach" from it, which probably causes session key termination. As a workaround I propose commenting out "force revoke" in /etc/pam.d/sshd. Note: There might be security related repercussions! ** Package changed: apparmor (Ubuntu) => pam (Ubuntu) ** Package changed: linux (Ubuntu) => x2goclient (Ubuntu) ** Changed in: x2goclient (Ubuntu) Status: Opinion => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1377924 Title: ecryptfs fails to mount (Unable to link the KEY_SPEC_USER_KEYRING into the KEY_SPEC_SESSION_KEYRING) Status in openssh package in Ubuntu: Confirmed Status in pam package in Ubuntu: Confirmed Status in x2goclient package in Ubuntu: Confirmed Bug description: This is a reincarnation of Bug #1234412. Looks like issue is not related to specific kernel versions. Currently I am observing two Trusty (14.04) machines, with very close configuration, running same kernel: 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64. One is able to mount without the problem but the other is refusing: $ mount -t ecryptfs sec sec Unable to link the KEY_SPEC_USER_KEYRING into the KEY_SPEC_SESSION_KEYRING; there is something wrong with your kernel keyring. Did you build key retention support into your kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1377924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1554878] Re: fix up usage of XDG_CURRENT_DESKTOP
** Also affects: indicator-bluetooth (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1554878 Title: fix up usage of XDG_CURRENT_DESKTOP Status in GLib: Confirmed Status in Python XDG App: Confirmed Status in empathy package in Ubuntu: Fix Released Status in eog package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in indicator-bluetooth package in Ubuntu: New Status in nautilus package in Ubuntu: Triaged Status in pyxdg package in Ubuntu: Confirmed Status in totem package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Confirmed Status in yelp package in Ubuntu: Fix Released Bug description: Since being standardised XDG_CURRENT_DESKTOP supports specifying multiple Desktop Names seperated by a colon, however many of the patches in Ubuntu pre-date this change so don't correctly support the current format in some cases. These days XDG_CURRENT_DESKTOP will look something like Unity GNOME (gnome-shell) GNOME-Classic:GNOME (gnome-shell classic mode) GNOME-Flashback:Unity (Flashback sesison, although upstream and debian use GNOME-Flashack:GNOME for this) Many of the patches only check for == "Unity" or == "GNOME", so misbehave for the latter cases in the list above. I suspect this will be more widespread than just nautilus, but fixing that would be a good start. Since most of this code is still Ubuntu specific (upstream mainly use XDG_CURRENT_DESKTOP for onlyShowIn etc), probably taking the last value in the string would get the desired result of Unity vs GNOME3 behaviour ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Mar 9 15:04:36 2016 SourcePackage: nautilus UpgradeStatus: Upgraded to xenial on 2015-11-28 (102 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1554878/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1554878] Re: fix up usage of XDG_CURRENT_DESKTOP
** Also affects: python-xdgapp Importance: Undecided Status: New ** Also affects: pyxdg (Ubuntu) Importance: Undecided Status: New ** Also affects: syncthing-gtk (Ubuntu) Importance: Undecided Status: New ** Also affects: dropbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pyxdg in Ubuntu. https://bugs.launchpad.net/bugs/1554878 Title: fix up usage of XDG_CURRENT_DESKTOP Status in GLib: Confirmed Status in Python XDG App: New Status in dropbox package in Ubuntu: New Status in empathy package in Ubuntu: Fix Released Status in eog package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in gtk+ package in Ubuntu: Fix Committed Status in nautilus package in Ubuntu: Triaged Status in pyxdg package in Ubuntu: New Status in syncthing-gtk package in Ubuntu: New Status in totem package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Confirmed Status in yelp package in Ubuntu: Fix Released Bug description: Since being standardised XDG_CURRENT_DESKTOP supports specifying multiple Desktop Names seperated by a colon, however many of the patches in Ubuntu pre-date this change so don't correctly support the current format in some cases. These days XDG_CURRENT_DESKTOP will look something like Unity GNOME (gnome-shell) GNOME-Classic:GNOME (gnome-shell classic mode) GNOME-Flashback:Unity (Flashback sesison, although upstream and debian use GNOME-Flashack:GNOME for this) Many of the patches only check for == "Unity" or == "GNOME", so misbehave for the latter cases in the list above. I suspect this will be more widespread than just nautilus, but fixing that would be a good start. Since most of this code is still Ubuntu specific (upstream mainly use XDG_CURRENT_DESKTOP for onlyShowIn etc), probably taking the last value in the string would get the desired result of Unity vs GNOME3 behaviour ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Mar 9 15:04:36 2016 SourcePackage: nautilus UpgradeStatus: Upgraded to xenial on 2015-11-28 (102 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1554878/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1535048] Re: i915 driver seems to cause system crash at random
*** This bug is a duplicate of bug 1554613 *** https://bugs.launchpad.net/bugs/1554613 ** This bug is no longer a duplicate of bug 1522922 Screen flickering in Intel i915 driver ** This bug has been marked a duplicate of bug 1554613 screen flickering on XPS13 9350/9550 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1535048 Title: i915 driver seems to cause system crash at random Status in libdrm package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: the system crashes totally at random... sometimes after hours sometimes after minutes... hardware reboot is required no problem under windows before it crashes though it always screw up the video for a few seconds lspci -nnk | egrep -i '3d|aphics|display|nouveau|nvidia|radeon|trident|vesa|vga'; uname -a; Xorg -version; sudo apt-get update; sudo apt-get install mesa-utils hardinfo fbset nux-tools; sudo fbset -i; apt-cache show xserver-xorg | grep Version; xrandr; fglrxinfo; nvidia-settings -g |head -n 30 ; sudo lshw -short; sudo lshw -C display; dpkg -l | egrep -i 'fgl|intel|mesa|mesa-utils|nvidia|nouveau|radeon|trident|video-ati'; cat /etc/lsb-release; dmesg | egrep -i 'abort|ailed|bug|error|fail|fgl|GLX|GPU|intel|missing|nouveau|NVIDIA|radeon|segment|trident|VESA|VGA|wfb|\(EE\)|\(WW\)'; cat /proc/cpuinfo | grep -I model; cat /var/log/Xorg.0.log | egrep -i 'abort|ailed|bug|display|error|fail|fgl|GLX|GPU|intel|issing|nouveau|nvidia|radeon|segment|trident|VESA|VGA|wfb|\(EE\)|\(WW\)'; sudo dmidecode|egrep 'anufact|roduct|erial|elease'; cat /etc/X11/xorg.conf; /usr/lib/nux/unity_support_test -p; ubuntu-support-status ; sudo lsmod 00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) Linux box 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux X.Org X Server 1.17.3 Release Date: 2015-10-26 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.19.0-33-generic x86_64 Ubuntu Current Operating System: Linux box 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.3.0-5-generic root=UUID=1406f1b3-ed81-4320-a7df-aba3cb5d60e6 ro quiet splash vt.handoff=7 Build Date: 25 November 2015 04:17:13PM xorg-server 2:1.17.3-2ubuntu2 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.33.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Hit:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease Hit:2 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease Hit:3 http://de.archive.ubuntu.com/ubuntu xenial-backports InRelease Hit:4 http://security.ubuntu.com/ubuntu xenial-security InRelease Reading package lists... Done Reading package lists... Done Building dependency tree Reading state information... Done fbset is already the newest version (2.1-28). nux-tools is already the newest version (4.0.8+16.04.20151210-0ubuntu1). hardinfo is already the newest version (0.5.1-1.4ubuntu1). mesa-utils is already the newest version (8.3.0-1). The following package was automatically installed and is no longer required: libvpx2:i386 Use 'sudo apt autoremove' to remove it. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. mode "1280x1024" geometry 1280 1024 1280 1024 32 timings 0 0 0 0 0 0 0 accel true rgba 8/16,8/8,8/0,0/0 endmode Frame buffer device information: Name : inteldrmfb Address : 0xd052 Size : 5242880 Type : PACKED PIXELS Visual : TRUECOLOR XPanStep : 1 YPanStep : 1 YWrapStep : 0 LineLength : 5120 Accelerator : No Version: 1:7.7+12ubuntu1 Screen 0: minimum 8 x 8, current 1280 x 1024, maximum 32767 x 32767 VGA1 connected primary 1280x1024+0+0 (normal left inverted right x axis y axis) 338mm x 270mm 1280x1024 60.02*+ 75.02 1152x864 75.00 1024x768 75.08 70.07 60.00 832x624 74.55 800x600 72.19 75.00 60.32 56.25 640x480 75.00 72.81 66.67 60.00 720x400 70.08 VIRTUAL1 disconnected (normal left inverted right x axis y axis) The program 'fglrxinfo' can be found in the following packages: * fglrx * fglrx-updates Try: sudo apt-get install The program 'nvidia-settings' is currently not installed. You can install it by typing: sudo apt-get install nvidia-settings H/W path Device Class Description === system Computer /0 bus Motherboard /0/0 memory 1991MiB System memory /0/1 processor Intel(R) Pentium(R) Dual CPU E2180 @ 2.00GHz /0/100 bridge 82945G/GZ/P/PL Memory Controller Hub /0/100/2 display 82945G/GZ
[Touch-packages] [Bug 1572361] [NEW] Dialog "Authentication is required to change your own user data" appears when chnaging keyboard language inside non-physical session
Public bug reported: Dialog "Authentication is required to change your own user data" appears when changing keyboard language inside non-physical session. This is reincarnation of https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1512002. I am experiencing the bug on 16.04 with gnome-flashback session inside x2go session. The dialog pops-up when I try to switch keyboard language using indicator. The irony that there is no way to enter the password when switching back to the language of the password. This what systemd log shows when request is denied: polkitd(authority=local)[740]: Operator of unix-session:1 FAILED to authenticate to gain authorization for action org.freedesktop.accounts.change-own-user-data for system-bus-name::1.105 [/usr/lib/unity-settings-daemon/unity-settings-daemon] (owned by unix-user:testuser) ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1572361 Title: Dialog "Authentication is required to change your own user data" appears when chnaging keyboard language inside non-physical session Status in accountsservice package in Ubuntu: New Bug description: Dialog "Authentication is required to change your own user data" appears when changing keyboard language inside non-physical session. This is reincarnation of https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1512002. I am experiencing the bug on 16.04 with gnome-flashback session inside x2go session. The dialog pops-up when I try to switch keyboard language using indicator. The irony that there is no way to enter the password when switching back to the language of the password. This what systemd log shows when request is denied: polkitd(authority=local)[740]: Operator of unix-session:1 FAILED to authenticate to gain authorization for action org.freedesktop.accounts.change-own-user-data for system-bus-name::1.105 [/usr/lib/unity-settings-daemon/unity-settings-daemon] (owned by unix-user:testuser) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1572361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1480340] [NEW] initramfs-tools calls dpkg with obsolete parameter
Public bug reported: initramfs-tools calls dpkg with obsolete parameter: ... Processing triggers for initramfs-tools (0.103ubuntu16) ... dpkg: warning: --compare-versions used with obsolete relation operator '>' ... ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1480340 Title: initramfs-tools calls dpkg with obsolete parameter Status in initramfs-tools package in Ubuntu: New Bug description: initramfs-tools calls dpkg with obsolete parameter: ... Processing triggers for initramfs-tools (0.103ubuntu16) ... dpkg: warning: --compare-versions used with obsolete relation operator '>' ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1480340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377924] Re: ecryptfs fails to mount (Unable to link the KEY_SPEC_USER_KEYRING into the KEY_SPEC_SESSION_KEYRING)
** No longer affects: apparmor ** Also affects: openssh (Ubuntu) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags added: ssh x2go -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1377924 Title: ecryptfs fails to mount (Unable to link the KEY_SPEC_USER_KEYRING into the KEY_SPEC_SESSION_KEYRING) Status in “apparmor” package in Ubuntu: New Status in “linux” package in Ubuntu: Opinion Status in “openssh” package in Ubuntu: New Bug description: This is a reincarnation of Bug #1234412. Looks like issue is not related to specific kernel versions. Currently I am observing two Trusty (14.04) machines, with very close configuration, running same kernel: 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64. One is able to mount without the problem but the other is refusing: $ mount -t ecryptfs sec sec Unable to link the KEY_SPEC_USER_KEYRING into the KEY_SPEC_SESSION_KEYRING; there is something wrong with your kernel keyring. Did you build key retention support into your kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1377924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2084251] Re: Only single LUKS device unlocked on boot
While I agree that moving systemd-cryptsetup to 'recommended' (or even 'depends') is the solution, it doesn't solve the issue with installs using LiveCDs. Install ISOs must be updated to make systems with separate encrypted /home bootable and systems with 2+ encrypted volumes usable. Which project should be added to the loop to initiate discussion regarding new ISOs? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2084251 Title: Only single LUKS device unlocked on boot Status in cryptsetup package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in cryptsetup source package in Oracular: Invalid Status in systemd source package in Oracular: Confirmed Bug description: Hi, I just upgraded from Noble to Oracular. It seems post-upgrade, only a single LUKS device is decrypted on boot. My `/etc/crypttab` is as follows: | nvme0n1p3_crypt UUID=c82c8c6c-e363-473f-a655-a325d4e6cf3b none luks,discard | nvme0n1p4_crypt UUID=3de219b7-3e0c-437b-a0eb-d3cb8087d74e none luks,discard `lsblk -o +UUID` showing UUIDs: | ├─nvme0n1p3 259:30 384G 0 part c82c8c6c-e363-473f-a655-a325d4e6cf3b | │ └─nvme0n1p3_crypt 252:00 384G 0 crypt / f48e2583-013f-474c-9f57-5deabef8d833 | └─nvme0n1p4 259:40 546.8G 0 part 3de219b7-3e0c-437b-a0eb-d3cb8087d74e | └─nvme0n1p4_crypt 252:10 546.7G 0 crypt /home dfea2d4c-f43e-4ef9-8938-3255f7987dfa I can confirm that the `crypttab` entry is correct because I can run `cryptdisks_start nvme0n1p4_crypt` on the recovery prompt and it decrypts it. I haven't yet tried downgrading `cryptsetup`, will give that a try tomorrow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2084251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2084251] Re: Only single LUKS device unlocked on boot
@vorlon Currently when installing using Calamares (Kubuntu, Lubuntu etc) and probably Ubiquity (Mate etc), manual partitioning allows arbitrary number of luks volumes including one them being /home. Configurations with /home on luks which is not the first one, are "unbootable". Configurations with just 2+ luks volumes are barely usable due to all the symptoms described in this bug. I was unable to even login to install the missing package. Had to resort to chrooting from Livefs. The above also applies to existing systems with 2+ luks volumes prior to install/upgrade. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2084251 Title: Only single LUKS device unlocked on boot Status in cryptsetup package in Ubuntu: Invalid Status in systemd package in Ubuntu: Triaged Status in cryptsetup source package in Oracular: Invalid Status in systemd source package in Oracular: Triaged Bug description: Hi, I just upgraded from Noble to Oracular. It seems post-upgrade, only a single LUKS device is decrypted on boot. My `/etc/crypttab` is as follows: | nvme0n1p3_crypt UUID=c82c8c6c-e363-473f-a655-a325d4e6cf3b none luks,discard | nvme0n1p4_crypt UUID=3de219b7-3e0c-437b-a0eb-d3cb8087d74e none luks,discard `lsblk -o +UUID` showing UUIDs: | ├─nvme0n1p3 259:30 384G 0 part c82c8c6c-e363-473f-a655-a325d4e6cf3b | │ └─nvme0n1p3_crypt 252:00 384G 0 crypt / f48e2583-013f-474c-9f57-5deabef8d833 | └─nvme0n1p4 259:40 546.8G 0 part 3de219b7-3e0c-437b-a0eb-d3cb8087d74e | └─nvme0n1p4_crypt 252:10 546.7G 0 crypt /home dfea2d4c-f43e-4ef9-8938-3255f7987dfa I can confirm that the `crypttab` entry is correct because I can run `cryptdisks_start nvme0n1p4_crypt` on the recovery prompt and it decrypts it. I haven't yet tried downgrading `cryptsetup`, will give that a try tomorrow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2084251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2084251] Re: Only single LUKS device unlocked on boot
I can confirm. Not mounting luks volumes is not the only issue. Among the issues are: very long boo times, inability to login using graphical login managers and random hangs all over the place. Systems with /home on separate encrypted location are completely broken even with fresh installs. The issue is so severe that I would recommend re-issuing of 24.10 ISOs. How exactly did the release pass even basic QA? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2084251 Title: Only single LUKS device unlocked on boot Status in cryptsetup package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in cryptsetup source package in Oracular: Confirmed Status in systemd source package in Oracular: Confirmed Bug description: Hi, I just upgraded from Noble to Oracular. It seems post-upgrade, only a single LUKS device is decrypted on boot. My `/etc/crypttab` is as follows: | nvme0n1p3_crypt UUID=c82c8c6c-e363-473f-a655-a325d4e6cf3b none luks,discard | nvme0n1p4_crypt UUID=3de219b7-3e0c-437b-a0eb-d3cb8087d74e none luks,discard `lsblk -o +UUID` showing UUIDs: | ├─nvme0n1p3 259:30 384G 0 part c82c8c6c-e363-473f-a655-a325d4e6cf3b | │ └─nvme0n1p3_crypt 252:00 384G 0 crypt / f48e2583-013f-474c-9f57-5deabef8d833 | └─nvme0n1p4 259:40 546.8G 0 part 3de219b7-3e0c-437b-a0eb-d3cb8087d74e | └─nvme0n1p4_crypt 252:10 546.7G 0 crypt /home dfea2d4c-f43e-4ef9-8938-3255f7987dfa I can confirm that the `crypttab` entry is correct because I can run `cryptdisks_start nvme0n1p4_crypt` on the recovery prompt and it decrypts it. I haven't yet tried downgrading `cryptsetup`, will give that a try tomorrow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2084251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
