[Touch-packages] [Bug 1538284] Re: Unescaped left brace in regex is deprecated
I have fixed the problem with an editor and have manually added the escape where required. There seems to be a fix on Debian since January 2017. This is 16.04 that'd be an LTS. What's the reason for holding this change (someone else did) back? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1538284 Title: Unescaped left brace in regex is deprecated Status in pam package in Ubuntu: Confirmed Status in pam package in Debian: Fix Released Bug description: When installing postgresql on Ubuntu 16.04 (xenial), the following warning are raised: Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/(?https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1538284/+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 1721704] [NEW] Printer settings stuck on loading drivers database
Public bug reported: 1) Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 2) ubuntu-settings: Installed: 17.10.17 Candidate: 17.10.17 3) The printer configuration goes fine and I can print 4) Printer settings stuck on loading drivers database and finally no drivers list available. Only 'cancel' button active. Note: I'm trying to configure a Brother HL-2030 connected to Network through a FritzBox 7940 router. The printer works fine both on Fedora and macOS X systems. I opened 'System Settings', then select 'Devices' > 'Printers' > 'Add a Printer'. I entered the router address and the window shows me correctly a 'JetDirect-Printer' on 192.168.178.1. I selected the printer and pressed the 'Add' button, a window 'Select Printer Driver' appears and stuck with 'Loading drivers database...'. After about 2 minutes, stopped loading and remains blank. No drivers selection is available and I can only push the 'Cancel' button. ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1721704 Title: Printer settings stuck on loading drivers database Status in ubuntu-settings package in Ubuntu: New Bug description: 1) Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 2) ubuntu-settings: Installed: 17.10.17 Candidate: 17.10.17 3) The printer configuration goes fine and I can print 4) Printer settings stuck on loading drivers database and finally no drivers list available. Only 'cancel' button active. Note: I'm trying to configure a Brother HL-2030 connected to Network through a FritzBox 7940 router. The printer works fine both on Fedora and macOS X systems. I opened 'System Settings', then select 'Devices' > 'Printers' > 'Add a Printer'. I entered the router address and the window shows me correctly a 'JetDirect-Printer' on 192.168.178.1. I selected the printer and pressed the 'Add' button, a window 'Select Printer Driver' appears and stuck with 'Loading drivers database...'. After about 2 minutes, stopped loading and remains blank. No drivers selection is available and I can only push the 'Cancel' button. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1721704/+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 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.
version we release in oem project is: 1.4.12-1ubuntu1somerville1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1693756 Title: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication. Status in ModemManager: New Status in OEM Priority Project: Triaged Status in modemmanager package in Ubuntu: New Bug description: # issue: * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 1.4.12-1ubuntu1 on xenial. - but works well on on Yakkety. # investgation: * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried install followed packages from Yakkety ppa on Xenial and wwan card works on 1st boot but failed after 2nd boot sometimes. - libmbim-glib4_1.14.0-1_amd64.deb - libmbim-glib-dev_1.14.0-1_amd64.deb - libmbim-proxy_1.14.0-1_amd64.deb - libmbim-utils_1.14.0-1_amd64.deb - libqmi-glib5_1.16.0-1_amd64.deb - libqmi-proxy_1.16.0-1_amd64.deb * different from ModemManager --debug - In passed case, it received message from /dev/cdc-wdm1 after send "Read max control message size from descriptors file: 4096" , but not happens to failed case. So, it prints "[mm-port-probe.c:261] mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in failed case. - passed case: http://paste.ubuntu.com/24664908/ - failed case: http://paste.ubuntu.com/24664910/ # Plan: * let the newer version packages could also works well on Xenial. * find out needed patches on newer version packages. * packport needed patches to older version packages on Xenial. # environment information: * modinfo cdc_mbim for original kernel module: http://paste.ubuntu.com/24662359/ - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 4.4.0 and yakkety kernel 4.8.0. * uname -r: 4.4.0-73-generic * lsusb -v: http://paste.ubuntu.com/24662332/ FCC authentication reference: * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html * https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704 To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1693756/+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 1721655] Re: a mistype of the kernel version can do you in
** Tags removed: wayland-session -- 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/1721655 Title: a mistype of the kernel version can do you in Status in initramfs-tools package in Ubuntu: New Bug description: I mistyped the kernel version when running update-initramfs e.g.: sudo update-initramfs -u -k 4.1.3.0-11-generic [sudo] password for bdmurray: update-initramfs: Generating /boot/initrd.img-4.1.3.0-11-generic WARNING: missing /lib/modules/4.1.3.0-11-generic Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.1.3.0-11-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_MQwUHq/lib/modules/4.1.3.0-11-generic/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_MQwUHq/lib/modules/4.1.3.0-11-generic/modules.builtin: No such file or directory I now have a bad(?) initrd in my /boot partition: ls -lh /boot ... -rw-r--r-- 1 root root 8.8M Oct 5 15:10 initrd.img-4.1.3.0-11-generic -rw-r--r-- 1 root root 32M Oct 4 14:46 initrd.img-4.13.0-11-generic -rw-r--r-- 1 root root 32M Oct 4 14:49 initrd.img-4.13.0-12-generic ... And that version number was written to /var/lib/initramfs-tools/, so every time update-initramfs is run that bad(?) initrd will be recreated. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: initramfs-tools 0.125ubuntu11 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 5 15:14:04 2017 InstallationDate: Installed on 2016-01-22 (622 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1721655/+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 1717951] Re: UIFe: Drop imagemagick-display from the default install
While the visual side of this bug is fixed now (the ugly wizard-icon is gone from the launcher), the usability side is still alive: You can still test the "imagemagick" app from within Ubuntu Software and decide to remove it from there. With the ugly side-effect of removing printing support without even realizing that this is printing related at all. Jeremy, Ian, can you remove the app from being listed in Ubuntu Software as well? Or at least move it to the "System Apps" section to prevent useres to unvoluntarily remove CUPS? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1717951 Title: UIFe: Drop imagemagick-display from the default install Status in ubuntu-settings package in Ubuntu: Fix Released Status in imagemagick package in Debian: New Bug description: Impact == I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10. It is visible in the Show Applications view of the Activities Overview so this could impact screenshots. Justification = imagemagick is a collection of commandline utilities for working with images, photos, etc. It is a required dependency for many things and will still be installed by default. Bundled with imagemagick is the "display" app, which is an app with an unusual, difficult-to-use UI. It was not intentionally included in the default Ubuntu install but was only there because it was packaged together. I am proposing splitting the display app to a separate binary package so that it is available for install for the few who do want to use the app. I tried proposing this to Debian. See comment #60 on the attached Debian bug but the Debian maintainer doesn't seem interested in accepting my proposal any time soon. (I emailed him directly a few months ago too.) List Notifications == https://lists.ubuntu.com/archives/ubuntu-doc/2017-September/020534.html https://lists.ubuntu.com/archives/ubuntu-translators/2017-September/007403.html Other Info == I will be attaching a patch for review by the Desktop Team here soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1717951/+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 1721712] [NEW] Missing: /usr/share/ca-certificates/mozilla/SwissSign_Platinum_CA_-_G2.crt
Public bug reported: Version: ca-certificates 20170717~16.04.1 Please add /usr/share/ca-certificates/mozilla/SwissSign_Platinum_CA_- _G2.crt back again as soon as possible. File /usr/share/ca-certificates/mozilla/SwissSign_Platinum_CA_-_G2.crt is missing in ca-certificates, even though after everything I found it should be there. AFAIK there is no reason for removing it (and I work for SwissSign, so I should know if it were so). apt-file search reports that it should be there $ apt-file search SwissSign ca-certificates: /usr/share/ca-certificates/mozilla/SwissSign_Gold_CA_-_G2.crt ca-certificates: /usr/share/ca-certificates/mozilla/SwissSign_Platinum_CA_-_G2.crt ca-certificates: /usr/share/ca-certificates/mozilla/SwissSign_Silver_CA_-_G2.crt but in fact it is not: marc@dev0001:~/svn/websites/plugins$ lsb_release -d Description:Ubuntu 16.04.3 LTS marc@dev0001:~/svn/websites/plugins$ dpkg -L ca-certificates | grep SwissSign /usr/share/ca-certificates/mozilla/SwissSign_Gold_CA_-_G2.crt /usr/share/ca-certificates/mozilla/SwissSign_Silver_CA_-_G2.crt marc@dev0001:~/svn/websites/plugins$ in both, Ubuntu 14.04 und 16.04: $ dpkg -S *SwissSign* ca-certificates: /usr/share/ca-certificates/mozilla/SwissSign_Gold_CA_-_G2.crt ca-certificates: /usr/share/ca-certificates/mozilla/SwissSign_Silver_CA_-_G2.crt → Platinum is missing! Install old version: sudo apt-get install --reinstall ca-certificates=20130906ubuntu2 $ dpkg -S SwissSign ca-certificates: /usr/share/ca-certificates/mozilla/SwissSign_Platinum_CA_- _G2.crt ca-certificates: /usr/share/ca-certificates/mozilla/SwissSign_Silver_CA_-_G2.crt ca-certificates: /usr/share/ca-certificates/mozilla/SwissSign_Gold_CA_-_G2.crt → Platinum is back again! ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New ** Tags: certificates mozilla swisssign -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1721712 Title: Missing: /usr/share/ca-certificates/mozilla/SwissSign_Platinum_CA_- _G2.crt Status in ca-certificates package in Ubuntu: New Bug description: Version: ca-certificates 20170717~16.04.1 Please add /usr/share/ca-certificates/mozilla/SwissSign_Platinum_CA_- _G2.crt back again as soon as possible. File /usr/share/ca-certificates/mozilla/SwissSign_Platinum_CA_-_G2.crt is missing in ca-certificates, even though after everything I found it should be there. AFAIK there is no reason for removing it (and I work for SwissSign, so I should know if it were so). apt-file search reports that it should be there $ apt-file search SwissSign ca-certificates: /usr/share/ca-certificates/mozilla/SwissSign_Gold_CA_-_G2.crt ca-certificates: /usr/share/ca-certificates/mozilla/SwissSign_Platinum_CA_-_G2.crt ca-certificates: /usr/share/ca-certificates/mozilla/SwissSign_Silver_CA_-_G2.crt but in fact it is not: marc@dev0001:~/svn/websites/plugins$ lsb_release -d Description:Ubuntu 16.04.3 LTS marc@dev0001:~/svn/websites/plugins$ dpkg -L ca-certificates | grep SwissSign /usr/share/ca-certificates/mozilla/SwissSign_Gold_CA_-_G2.crt /usr/share/ca-certificates/mozilla/SwissSign_Silver_CA_-_G2.crt marc@dev0001:~/svn/websites/plugins$ in both, Ubuntu 14.04 und 16.04: $ dpkg -S *SwissSign* ca-certificates: /usr/share/ca-certificates/mozilla/SwissSign_Gold_CA_-_G2.crt ca-certificates: /usr/share/ca-certificates/mozilla/SwissSign_Silver_CA_-_G2.crt → Platinum is missing! Install old version: sudo apt-get install --reinstall ca-certificates=20130906ubuntu2 $ dpkg -S SwissSign ca-certificates: /usr/share/ca-certificates/mozilla/SwissSign_Platinum_CA_- _G2.crt ca-certificates: /usr/share/ca-certificates/mozilla/SwissSign_Silver_CA_-_G2.crt ca-certificates: /usr/share/ca-certificates/mozilla/SwissSign_Gold_CA_-_G2.crt → Platinum is back again! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1721712/+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 1720976] Re: no DNS resolution via systemd
bp1@dimension:~$ nmcli enp8s0: connected to Ethernet connection 1 "Broadcom Limited NetXtreme BCM5754 Gigabit Ethernet PCI Express (Precision T5400)" ethernet (tg3), 00:1E:4F:E9:F1:C1, hw, mtu 1500 ip4 default inet4 192.168.1.5/24 route4 169.254.0.0/16 inet6 fe80::99f:fae5:1467:a576/64 lo: unmanaged "lo" loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536 DNS configuration: servers: 192.168.1.1 interface: enp8s0 ** Attachment added: "Screenshot from 2017-10-06 08-20-59.png" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1720976/+attachment/4963441/+files/Screenshot%20from%202017-10-06%2008-20-59.png -- 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/1720976 Title: no DNS resolution via systemd Status in network-manager package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: 1) root@dimension:/home/bp1# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 Codename: artful root@dimension:/home/bp1# 2) systemd: Installed: 234-2ubuntu10 Candidate: 234-2ubuntu10 Version table: *** 234-2ubuntu10 500 500 http://gb.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status 3) DNS resolution 4) No DNS resolution from my configured DNS (in my case 192.168.1.1) Workarounds: Enable FallbackDNS=8.8.8.8 8.8.4.4 in resolved.conf Or running dhclient Fresh boot of Artful (static IP via network manager and DNS should be at 192.168.1.1): bp1@dimension:~$ ifconfig enp8s0: flags=4163 mtu 1500 inet 192.168.1.5 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::99f:fae5:1467:a576 prefixlen 64 scopeid 0x20 ether 00:1e:4f:e9:f1:c1 txqueuelen 1000 (Ethernet) RX packets 141 bytes 14707 (14.7 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 234 bytes 29807 (29.8 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 16 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 556 bytes 33758 (33.7 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 556 bytes 33758 (33.7 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 bp1@dimension:~$ ping www.dn.se ping: www.dn.se: Name or service not known bp1@dimension:~$ su Password: root@dimension:/home/bp1# systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (enp8s0) Current Scopes: LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no root@dimension:/home/bp1# ping www.dn.se ping: www.dn.se: Name or service not known root@dimension:/home/bp1# nano /etc/systemd/resolved.conf root@dimension:/home/bp1# cat /etc/systemd/resolved.conf # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. # # Entries in this file show the compile time defaults. # You can change settings by editing this file. # Defaults can be restored by simply deleting this file. # # See resolved.conf(5) for details [Resolve] #DNS= FallbackDNS=8.8.8.8 8.8.4.4 #Domains= #LLMNR=yes #MulticastDNS=yes #DNSSEC=no #Cache=yes #DNSStubListener=udp root@dimensio
[Touch-packages] [Bug 1720976] Re: no DNS resolution via systemd
Should also add that there is the same problem when I enable dhcp and let the network manager do dhcp. -- 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/1720976 Title: no DNS resolution via systemd Status in network-manager package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: 1) root@dimension:/home/bp1# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 Codename: artful root@dimension:/home/bp1# 2) systemd: Installed: 234-2ubuntu10 Candidate: 234-2ubuntu10 Version table: *** 234-2ubuntu10 500 500 http://gb.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status 3) DNS resolution 4) No DNS resolution from my configured DNS (in my case 192.168.1.1) Workarounds: Enable FallbackDNS=8.8.8.8 8.8.4.4 in resolved.conf Or running dhclient Fresh boot of Artful (static IP via network manager and DNS should be at 192.168.1.1): bp1@dimension:~$ ifconfig enp8s0: flags=4163 mtu 1500 inet 192.168.1.5 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::99f:fae5:1467:a576 prefixlen 64 scopeid 0x20 ether 00:1e:4f:e9:f1:c1 txqueuelen 1000 (Ethernet) RX packets 141 bytes 14707 (14.7 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 234 bytes 29807 (29.8 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 16 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 556 bytes 33758 (33.7 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 556 bytes 33758 (33.7 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 bp1@dimension:~$ ping www.dn.se ping: www.dn.se: Name or service not known bp1@dimension:~$ su Password: root@dimension:/home/bp1# systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (enp8s0) Current Scopes: LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no root@dimension:/home/bp1# ping www.dn.se ping: www.dn.se: Name or service not known root@dimension:/home/bp1# nano /etc/systemd/resolved.conf root@dimension:/home/bp1# cat /etc/systemd/resolved.conf # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. # # Entries in this file show the compile time defaults. # You can change settings by editing this file. # Defaults can be restored by simply deleting this file. # # See resolved.conf(5) for details [Resolve] #DNS= FallbackDNS=8.8.8.8 8.8.4.4 #Domains= #LLMNR=yes #MulticastDNS=yes #DNSSEC=no #Cache=yes #DNSStubListener=udp root@dimension:/home/bp1# ps ax | grep systemd 254 ?Ss 0:00 /lib/systemd/systemd-journald 292 ?Ss 0:00 /lib/systemd/systemd-udevd 573 ?Ssl0:00 /lib/systemd/systemd-timesyncd 585 ?Ss 0:00 /lib/systemd/systemd-networkd 701 ?Ss 0:00 /lib/systemd/systemd-logind 735 ?Ss 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation 844 ?Ss 0:00 /lib/systemd/systemd-resolved 1138 ?Ss 0:00 /lib/systemd/systemd --user 1219 ?Ss 0:00 /usr/bin/dbu
[Touch-packages] [Bug 961679] Re: gtkrc is producing light menus from dark elements
** Changed in: ubuntu-themes (Ubuntu) Status: Expired => In Progress ** Changed in: ubuntu-themes (Ubuntu) Importance: Undecided => Low ** Changed in: ubuntu-themes (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Branch linked: lp:~3v1n0/ubuntu-themes/gtk2-revive -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/961679 Title: gtkrc is producing light menus from dark elements Status in ubuntu-themes package in Ubuntu: In Progress Bug description: Examples - Right click on any window's title bar In app window menus of gtk 2 apps, examples - synaptic, browsers where global menus aren't used, vlc with no global menu, ect. Right click in a browser's menu bar Systray right click menus The in app window context menu of gtk2 windows is correctly light, maybe there is no way to have both, ie., it's either all dark or all light? The choice here would be to go with all dark if there is no other way ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: light-themes 0.1.8.31-0ubuntu1 [modified: usr/share/themes/Ambiance/gtk-2.0/gtkrc usr/share/themes/Ambiance/gtk-3.0/apps/nautilus.css usr/share/themes/Ambiance/gtk-3.0/gtk-widgets.css usr/share/themes/Ambiance/gtk-3.0/gtk.css usr/share/themes/Ambiance/gtk-3.0/settings.ini usr/share/themes/Ambiance/metacity-1/close.png usr/share/themes/Ambiance/metacity-1/close_focused_normal.png usr/share/themes/Ambiance/metacity-1/close_focused_prelight.png usr/share/themes/Ambiance/metacity-1/close_focused_pressed.png usr/share/themes/Ambiance/metacity-1/metacity-theme-1.xml] ProcVersionSignature: Ubuntu 3.2.0-19.30-generic-pae 3.2.11 Uname: Linux 3.2.0-19-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 Date: Wed Mar 21 17:42:27 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: light-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/961679/+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 1721712] Re: Missing: /usr/share/ca-certificates/mozilla/SwissSign_Platinum_CA_-_G2.crt
According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858064 it has been removed when all 1024-bit root certificates have been removed, but this certificate is 4096bit, so it is obviously a mistake: $ openssl x509 -in /usr/share/ca-certificates/mozilla/SwissSign_Platinum_CA_-_G2.crt -text -noout Certificate: Data: Version: 3 (0x2) Serial Number: 4e:b2:00:67:0c:03:5d:4f Signature Algorithm: sha1WithRSAEncryption| grep "RSA Public Key" Issuer: C=CH, O=SwissSign AG, CN=SwissSign Platinum CA - G2 Validity Not Before: Oct 25 08:36:00 2006 GMT Not After : Oct 25 08:36:00 2036 GMT Subject: C=CH, O=SwissSign AG, CN=SwissSign Platinum CA - G2 Subject Public Key Info: Public Key Algorithm: rsaEncryption Public-Key: (4096 bit) Modulus: 00:ca:df:a2:02:e2:da:f8:fc:07:16:b1:de:60:aa: de:96:5c:64:1f:c7:2f:7e:cf:67:fa:44:42:d6:76: 63:95:ae:eb:af:72:20:8a:45:47:86:62:78:86:d6: 20:39:26:f4:ae:a3:fd:23:e7:a5:9c:b5:22:21:19: b7:37:93:22:c0:50:9c:82:7b:d4:d5:04:44:5c:cb: b4:c2:9f:92:be:24:d8:7b:67:22:e2:69:5f:e5:05: 78:d4:87:d9:71:70:33:25:53:b4:87:3b:29:90:28: 36:9a:55:44:30:68:a4:83:97:7f:0d:1e:9c:76:ff: 15:9d:60:97:00:8d:8a:85:03:ec:80:be:ea:2c:6e: 10:51:92:cc:7e:d5:a3:33:d8:d6:49:de:58:2a:af: f6:16:eb:4b:7b:90:32:97:b9:ba:9d:58:f1:f8:57: 49:04:1e:a2:5d:06:70:dd:71:db:f9:dd:8b:9a:1b: 8c:cf:3d:a3:4d:ce:cb:7c:f6:bb:9c:a0:fa:09:ce: 23:62:b2:e9:0d:1f:e2:72:28:8f:9f:ac:68:20:7d: 6f:3b:a8:85:31:09:7f:0b:c7:e8:65:e9:e3:78:0e: 09:67:30:8b:34:82:fb:5d:e0:cc:9d:81:6d:62:ee: 08:1e:04:2c:4e:9b:ec:fe:a9:4f:5f:fd:69:78:ef: 09:1f:a1:b4:bf:fa:f3:ef:90:1e:4c:05:8b:1e:ea: 7a:91:7a:c3:d7:e5:fb:30:bc:6c:1b:10:58:98:f7: 1a:5f:d0:29:32:03:13:46:4d:61:6a:85:4c:52:74: 2f:06:1f:7b:11:e2:84:97:c6:99:f3:6d:7f:d7:67: 83:7e:13:68:d8:71:28:5a:d8:ce:dd:e8:10:14:9a: fe:6d:23:87:6e:8e:5a:70:3c:d5:8d:09:00:a7:aa: bc:b0:31:37:6d:c8:84:14:1e:5b:bd:45:63:20:6b: 4b:74:8c:bd:db:3a:0e:c1:cf:5a:16:8f:a5:98:f2: 76:89:b2:13:12:3b:0b:77:77:ac:bb:e5:3c:29:4a: 92:72:ca:61:1a:2b:5e:4c:e2:83:74:77:fa:35:48: 7a:85:4d:8d:9a:53:c4:df:78:ca:97:91:48:2b:45: 2b:01:f7:1c:1a:a2:ed:18:ba:0a:bd:83:fa:6f:bc: 8d:57:93:3b:d4:d4:a6:ce:1e:f1:a0:b1:ce:ab:fd: 2b:28:9a:4f:1b:d7:c3:72:db:a4:c4:bf:5d:4c:f5: dd:7b:96:69:ee:68:80:e6:e7:98:ba:36:b7:fe:6e: ed:2b:bd:20:f8:65:19:da:55:09:7e:25:dc:fe:61: 62:72:f9:7e:18:02:ef:63:b4:d0:fb:af:e5:3b:63: 8c:67:8f Exponent: 65537 (0x10001) X509v3 extensions: X509v3 Key Usage: critical Certificate Sign, CRL Sign X509v3 Basic Constraints: critical CA:TRUE X509v3 Subject Key Identifier: 50:AF:CC:07:87:15:47:6F:38:C5:B4:65:D1:DE:95:AA:E9:DF:9C:CC X509v3 Authority Key Identifier: keyid:50:AF:CC:07:87:15:47:6F:38:C5:B4:65:D1:DE:95:AA:E9:DF:9C:CC X509v3 Certificate Policies: Policy: 2.16.756.1.89.1.1.1.1 CPS: http://repository.swisssign.com/ Signature Algorithm: sha1WithRSAEncryption 08:85:a6:f5:16:0c:fc:44:1a:c1:63:e0:f9:55:46:08:fc:70: 1c:42:28:96:8e:b7:c5:c1:41:75:4e:09:71:79:e5:6d:96:ca: 4b:a5:88:60:d0:30:74:b8:ca:08:dc:b4:30:9e:40:07:16:6b: 65:95:77:01:ae:a4:b7:35:0b:81:da:71:15:a9:74:17:38:7b: 58:ca:f9:2f:fb:c0:65:76:8d:5b:01:b9:7d:de:82:3d:64:b8: be:14:74:a3:0a:54:d3:2c:95:18:17:35:f5:51:6b:3f:8f:a2: 96:61:39:78:6b:4b:e5:a6:a0:f8:53:df:51:10:93:62:e7:80: 2f:e2:d1:e0:bc:8e:36:46:77:33:ec:b8:fb:8e:9a:2c:89:4d: 31:11:0f:26:9e:04:bb:b7:04:8d:0b:f2:b9:fc:5a:9d:3b:16: b7:2f:c8:98:ab:fe:8a:50:59:2e:a3:3b:fc:29:5d:8b:c1:4b: c9:e2:8a:13:1d:b1:bf:bb:42:1d:52:dd:4e:d8:14:5e:10:c6: 31:07:ef:71:27:f7:1b:39:09:dc:82:ea:8b:b3:95:86:5e:fd: f5:da:5d:31:a6:e0:31:b6:94:e6:44:49:74:c5:16:e5:f7:1f: 03:61:28:c5:c8:cb:12:a0:42:4b:f9:6b:88:08:8d:b4:32:18: f3:75:9f:c4:7f:00:4f:05:95:9c:a3:17:02:c3:b3:53:9b:aa: 20:39:29:2b:66:fa:9d:af:5e:b3:92:d2:b5:a6:e1:1a:f9:2d: 41:69:81:14:b4:b4:b5:ed:89:3d:ce:fb:a9:9d:35:42:44:b1: 1c:14:73:81:cf:2a:01:35:9a:31:d5:2d:8f:6d:84:df:80:4d: 57:e3:3f:c5:84:75:
[Touch-packages] [Bug 1662031] Re: Switching language and format broken
Testing in an up-to-date artful VM, when switching languages in g-c-c, both LANG and LANGUAGE are updated in both ~/.pam_environment and /etc/default/locale. That VM is an artful install that has been updated daily, not an upgrade from a previous release. -- 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/1662031 Title: Switching language and format broken Status in Ubuntu GNOME: New Status in accountsservice package in Ubuntu: New Status in gdm3 package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: New Status in accountsservice source package in Artful: New Status in gdm3 source package in Artful: Confirmed Status in gnome-control-center source package in Artful: New Bug description: In Ubuntu GNOME 16.10 it doesn't matter what display language I select - the effective language is still the one stated in /etc/default/locale. ~/.pam_environment is changed as expected, but the variables set in /etc/default/locale override ~/.pam_environment. In Ubuntu GNOME 16.04 language switching takes effect, but the reason for that seems to be that /etc/default/locale is changed as well, so when a user changes the display language (or format), it changes it for all users on the system. The overriding by /etc/default/locale is probably caused by some other package(s) but g-c-c. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1662031/+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 1662031] Re: Switching language and format broken
Olivier: Is /etc/default/locale written to also?? That's not what Sebastien and I observed. I'll go to a (relatively) fresh artful install and recheck then. If that's the case, the issue may not be so urgent. But it's poor design, since it means that if a user changes language, s/he changes it for all users on the system. -- 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/1662031 Title: Switching language and format broken Status in Ubuntu GNOME: New Status in accountsservice package in Ubuntu: New Status in gdm3 package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: New Status in accountsservice source package in Artful: New Status in gdm3 source package in Artful: Confirmed Status in gnome-control-center source package in Artful: New Bug description: In Ubuntu GNOME 16.10 it doesn't matter what display language I select - the effective language is still the one stated in /etc/default/locale. ~/.pam_environment is changed as expected, but the variables set in /etc/default/locale override ~/.pam_environment. In Ubuntu GNOME 16.04 language switching takes effect, but the reason for that seems to be that /etc/default/locale is changed as well, so when a user changes the display language (or format), it changes it for all users on the system. The overriding by /etc/default/locale is probably caused by some other package(s) but g-c-c. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1662031/+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 1721750] [NEW] package libwind0-heimdal:amd64 7.1.0+dfsg-9ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemp
Public bug reported: when i try to installl "sudo apt install git" it getting errror i guesst ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libwind0-heimdal:amd64 7.1.0+dfsg-9ubuntu1.1 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 AptOrdering: liberror-perl:amd64: Install git-man:amd64: Install git:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Oct 6 17:38:08 2017 Dependencies: gcc-6-base 6.3.0-12ubuntu2 libc6 2.24-9ubuntu2.2 libcomerr2 1.43.4-2 libgcc1 1:6.3.0-12ubuntu2 libroken18-heimdal 7.1.0+dfsg-9ubuntu1.1 DpkgHistoryLog: Start-Date: 2017-10-06 17:38:01 Commandline: apt install git Requested-By: ramdhan (1000) Install: git-man:amd64 (1:2.11.0-2ubuntu0.3, automatic), git:amd64 (1:2.11.0-2ubuntu0.3), liberror-perl:amd64 (0.17024-1, automatic) ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-09-24 (11 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: heimdal Title: package libwind0-heimdal:amd64 7.1.0+dfsg-9ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: heimdal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1721750 Title: package libwind0-heimdal:amd64 7.1.0+dfsg-9ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in heimdal package in Ubuntu: New Bug description: when i try to installl "sudo apt install git" it getting errror i guesst ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libwind0-heimdal:amd64 7.1.0+dfsg-9ubuntu1.1 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 AptOrdering: liberror-perl:amd64: Install git-man:amd64: Install git:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Oct 6 17:38:08 2017 Dependencies: gcc-6-base 6.3.0-12ubuntu2 libc6 2.24-9ubuntu2.2 libcomerr2 1.43.4-2 libgcc1 1:6.3.0-12ubuntu2 libroken18-heimdal 7.1.0+dfsg-9ubuntu1.1 DpkgHistoryLog: Start-Date: 2017-10-06 17:38:01 Commandline: apt install git Requested-By: ramdhan (1000) Install: git-man:amd64 (1:2.11.0-2ubuntu0.3, automatic), git:amd64 (1:2.11.0-2ubuntu0.3), liberror-perl:amd64 (0.17024-1, automatic) ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-09-24 (11 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: heimdal Title: package libwind0-heimdal:amd64 7.1.0+dfsg-9ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1721750/+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 1720331] Re: Whoopsie continually relaunching
** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1720331 Title: Whoopsie continually relaunching Status in gnome-control-center package in Ubuntu: Triaged Status in whoopsie package in Ubuntu: Triaged Bug description: Today for the first time, and coincidentally looking for a different setting, I went to the Settings->Privacy dialogue. I was also (coincidentally for a different reason, relating to #1720149) already tailing /var/log/syslog to a terminal. Immediately on opening that dialogue, the syslog tail flooded with whoopsie continually relaunching, causing enough work to raise the fan speeds. This is a representative section from towards the end of me letting it, before I killed the service, with some necessary viciousness. Specifically systemctl stop whoopsie (didn't stop it) systemctl disable whoopsie (didn't stop it) (find pid for whoopsie's root process and kill it) (that stopped it) Also for good measure ensured the automatic bug reporting option in the privacy settings dialog was set to manual, which I think was done anyway when I disabled whoopsie, though the dialog wasn't on top at the time for me to be sure. It had been set to automatic when I first opened the dialog. Snippet from syslog attached. It was just repeating this continually for several minutes before I stopped it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: whoopsie 0.2.58 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashReports: 664:1000:119:0:2017-09-25 18:16:58.760134901 +0100:2017-09-25 18:16:58.760134901 +0100:/var/crash/_opt_google_chrome_chrome.1000.upload 640:1000:119:102847031:2017-09-27 20:28:45.352315425 +0100:2017-09-28 09:02:32.195212507 +0100:/var/crash/_usr_bin_gnome-shell.1000.crash 640:1000:119:34020328:2017-09-25 18:16:57.656132936 +0100:2017-09-25 18:16:58.760134901 +0100:/var/crash/_opt_google_chrome_chrome.1000.crash 600:111:119:0:2017-09-25 18:16:59.348145502 +0100:2017-09-25 18:16:59.348145502 +0100:/var/crash/_opt_google_chrome_chrome.1000.uploaded CurrentDesktop: GNOME Date: Fri Sep 29 10:00:34 2017 InstallationDate: Installed on 2017-07-30 (60 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie UpgradeStatus: Upgraded to artful on 2017-08-22 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1720331/+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 1720331] Re: Whoopsie continually relaunching
This is definitely a gnome-control-center bug rather than whoopsie. I can reproduce it like so: 1. open gnome-control-center, and select the privacy panel. 2. ensure that problem reporting is turned on. 3. wait for whoopsie-preferences to exit on timeout (or manually kill it). I then see traffic like the following on the system bus: method call time=1507286449.661622 sender=:1.325 -> destination=:1.336 serial=96 path=/com/ubuntu/WhoopsiePreferences; interface=com.ubuntu.WhoopsiePreferences; member=SetReportCrashes boolean false method call time=1507286449.918969 sender=:1.325 -> destination=:1.336 serial=97 path=/com/ubuntu/WhoopsiePreferences; interface=com.ubuntu.WhoopsiePreferences; member=SetReportCrashes boolean true method call time=1507286450.216068 sender=:1.325 -> destination=:1.336 serial=98 path=/com/ubuntu/WhoopsiePreferences; interface=com.ubuntu.WhoopsiePreferences; member=SetReportCrashes boolean false method call time=1507286450.529908 sender=:1.325 -> destination=:1.336 serial=99 path=/com/ubuntu/WhoopsiePreferences; interface=com.ubuntu.WhoopsiePreferences; member=SetReportCrashes boolean true ... which continues until I kill gnome-control-center. Whoopsie relaunching is a direct consequence of these D-Bus method calls coming from gnome- control-center. It looks like the logic controlling the GtkSwitch gets into a loop when whoopsie-preferences stops. The D-Bus method calls are synchronous, so this also ends up locking the UI. I'll have a look into this properly next week. ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => James Henstridge (jamesh) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1720331 Title: Whoopsie continually relaunching Status in gnome-control-center package in Ubuntu: Triaged Status in whoopsie package in Ubuntu: Triaged Bug description: Today for the first time, and coincidentally looking for a different setting, I went to the Settings->Privacy dialogue. I was also (coincidentally for a different reason, relating to #1720149) already tailing /var/log/syslog to a terminal. Immediately on opening that dialogue, the syslog tail flooded with whoopsie continually relaunching, causing enough work to raise the fan speeds. This is a representative section from towards the end of me letting it, before I killed the service, with some necessary viciousness. Specifically systemctl stop whoopsie (didn't stop it) systemctl disable whoopsie (didn't stop it) (find pid for whoopsie's root process and kill it) (that stopped it) Also for good measure ensured the automatic bug reporting option in the privacy settings dialog was set to manual, which I think was done anyway when I disabled whoopsie, though the dialog wasn't on top at the time for me to be sure. It had been set to automatic when I first opened the dialog. Snippet from syslog attached. It was just repeating this continually for several minutes before I stopped it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: whoopsie 0.2.58 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashReports: 664:1000:119:0:2017-09-25 18:16:58.760134901 +0100:2017-09-25 18:16:58.760134901 +0100:/var/crash/_opt_google_chrome_chrome.1000.upload 640:1000:119:102847031:2017-09-27 20:28:45.352315425 +0100:2017-09-28 09:02:32.195212507 +0100:/var/crash/_usr_bin_gnome-shell.1000.crash 640:1000:119:34020328:2017-09-25 18:16:57.656132936 +0100:2017-09-25 18:16:58.760134901 +0100:/var/crash/_opt_google_chrome_chrome.1000.crash 600:111:119:0:2017-09-25 18:16:59.348145502 +0100:2017-09-25 18:16:59.348145502 +0100:/var/crash/_opt_google_chrome_chrome.1000.uploaded CurrentDesktop: GNOME Date: Fri Sep 29 10:00:34 2017 InstallationDate: Installed on 2017-07-30 (60 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie UpgradeStatus: Upgraded to artful on 2017-08-22 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1720331/+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 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
** Attachment removed: "2EB8BC253FCD8C93.jpg" https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/349469/+attachment/4961171/+files/2EB8BC253FCD8C93.jpg ** Attachment removed: "1FAF9B9AA6AC21C2.jpg" https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/349469/+attachment/4961658/+files/1FAF9B9AA6AC21C2.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/349469 Title: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable Status in Aptdaemon: Confirmed Status in Debconf: New Status in aptdaemon package in Ubuntu: Incomplete Status in debconf package in Ubuntu: Triaged Bug description: Upgrading packages that use debconf sometimes fail with the following error: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/aptdaemon/+bug/349469/+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 1662031] Re: Switching language and format broken
The /etc/default/locale file was not altered when I just tested on an updated artful. -- 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/1662031 Title: Switching language and format broken Status in Ubuntu GNOME: New Status in accountsservice package in Ubuntu: New Status in gdm3 package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: New Status in accountsservice source package in Artful: New Status in gdm3 source package in Artful: Confirmed Status in gnome-control-center source package in Artful: New Bug description: In Ubuntu GNOME 16.10 it doesn't matter what display language I select - the effective language is still the one stated in /etc/default/locale. ~/.pam_environment is changed as expected, but the variables set in /etc/default/locale override ~/.pam_environment. In Ubuntu GNOME 16.04 language switching takes effect, but the reason for that seems to be that /etc/default/locale is changed as well, so when a user changes the display language (or format), it changes it for all users on the system. The overriding by /etc/default/locale is probably caused by some other package(s) but g-c-c. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1662031/+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 1662031] Re: Switching language and format broken
To clarify: I used the g-c-c interface to switch language. If I had clicked "Manage Installed Languages" to open Language Support and then clicked "Apply System-Wide", /etc/default/locale would have been updated too. But that 'does not count'. Language Support is available to work around the fact that installation of new languages from g-c-c does not work currently. -- 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/1662031 Title: Switching language and format broken Status in Ubuntu GNOME: New Status in accountsservice package in Ubuntu: New Status in gdm3 package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: New Status in accountsservice source package in Artful: New Status in gdm3 source package in Artful: Confirmed Status in gnome-control-center source package in Artful: New Bug description: In Ubuntu GNOME 16.10 it doesn't matter what display language I select - the effective language is still the one stated in /etc/default/locale. ~/.pam_environment is changed as expected, but the variables set in /etc/default/locale override ~/.pam_environment. In Ubuntu GNOME 16.04 language switching takes effect, but the reason for that seems to be that /etc/default/locale is changed as well, so when a user changes the display language (or format), it changes it for all users on the system. The overriding by /etc/default/locale is probably caused by some other package(s) but g-c-c. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1662031/+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 1662031] Re: Switching language and format broken
I didn't click "Apply System-Wide". When I changed the language in g-c-c /etc/default/locale was written to (LANG and LANGUAGE were updated). I agree that this is unexpected behaviour though, I wouldn't expect the current user's setting to be applied system-wide unless explicitly requested. -- 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/1662031 Title: Switching language and format broken Status in Ubuntu GNOME: New Status in accountsservice package in Ubuntu: New Status in gdm3 package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: New Status in accountsservice source package in Artful: New Status in gdm3 source package in Artful: Confirmed Status in gnome-control-center source package in Artful: New Bug description: In Ubuntu GNOME 16.10 it doesn't matter what display language I select - the effective language is still the one stated in /etc/default/locale. ~/.pam_environment is changed as expected, but the variables set in /etc/default/locale override ~/.pam_environment. In Ubuntu GNOME 16.04 language switching takes effect, but the reason for that seems to be that /etc/default/locale is changed as well, so when a user changes the display language (or format), it changes it for all users on the system. The overriding by /etc/default/locale is probably caused by some other package(s) but g-c-c. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1662031/+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 1721712] Re: Missing: /usr/share/ca-certificates/mozilla/SwissSign_Platinum_CA_-_G2.crt
Hi, In the 20170717 package, we no longer ship email signing certificates. Per Mozilla, "SwissSign Platinum CA - G2" is marked as an email signing certificate only: CKA_TRUST_SERVER_AUTH CK_TRUST CKT_NSS_MUST_VERIFY_TRUST CKA_TRUST_EMAIL_PROTECTION CK_TRUST CKT_NSS_TRUSTED_DELEGATOR CKA_TRUST_CODE_SIGNING CK_TRUST CKT_NSS_TRUSTED_DELEGATOR CKA_TRUST_STEP_UP_APPROVED CK_BBOOL CK_FALSE This is the Debian bug where email signing certificates were removed: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721976 ** Bug watch added: Debian Bug tracker #721976 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721976 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1721712 Title: Missing: /usr/share/ca-certificates/mozilla/SwissSign_Platinum_CA_- _G2.crt Status in ca-certificates package in Ubuntu: New Bug description: Version: ca-certificates 20170717~16.04.1 Please add /usr/share/ca-certificates/mozilla/SwissSign_Platinum_CA_- _G2.crt back again as soon as possible. File /usr/share/ca-certificates/mozilla/SwissSign_Platinum_CA_-_G2.crt is missing in ca-certificates, even though after everything I found it should be there. AFAIK there is no reason for removing it (and I work for SwissSign, so I should know if it were so). apt-file search reports that it should be there $ apt-file search SwissSign ca-certificates: /usr/share/ca-certificates/mozilla/SwissSign_Gold_CA_-_G2.crt ca-certificates: /usr/share/ca-certificates/mozilla/SwissSign_Platinum_CA_-_G2.crt ca-certificates: /usr/share/ca-certificates/mozilla/SwissSign_Silver_CA_-_G2.crt but in fact it is not: marc@dev0001:~/svn/websites/plugins$ lsb_release -d Description:Ubuntu 16.04.3 LTS marc@dev0001:~/svn/websites/plugins$ dpkg -L ca-certificates | grep SwissSign /usr/share/ca-certificates/mozilla/SwissSign_Gold_CA_-_G2.crt /usr/share/ca-certificates/mozilla/SwissSign_Silver_CA_-_G2.crt marc@dev0001:~/svn/websites/plugins$ in both, Ubuntu 14.04 und 16.04: $ dpkg -S *SwissSign* ca-certificates: /usr/share/ca-certificates/mozilla/SwissSign_Gold_CA_-_G2.crt ca-certificates: /usr/share/ca-certificates/mozilla/SwissSign_Silver_CA_-_G2.crt → Platinum is missing! Install old version: sudo apt-get install --reinstall ca-certificates=20130906ubuntu2 $ dpkg -S SwissSign ca-certificates: /usr/share/ca-certificates/mozilla/SwissSign_Platinum_CA_- _G2.crt ca-certificates: /usr/share/ca-certificates/mozilla/SwissSign_Silver_CA_-_G2.crt ca-certificates: /usr/share/ca-certificates/mozilla/SwissSign_Gold_CA_-_G2.crt → Platinum is back again! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1721712/+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 1721763] [NEW] ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart
Public bug reported: I really do not know which package to assign this incident, please excuse me. Any way, the release candidates is near, and this problem continues to occur since linux kernel was updated from 4.11 to 4.12 ... and now with version 4.13 the problem continues. I noticed that this problem does not occur with my other two older notebooks (one Sony Vaio and the other a generic one integrated by me) both old notes use NVIDIA video card in versions of more than 5 years ago. My new Dell notebook has a GTX 1050 video card ... but I also do not know if the cause of this problem may be linked to the video card and the fact that Nouveau driver and linux Kernel have received recent implementations for compatibilities with this new NVIDIA technology. The fact is that Ubuntu 17.10 has potential to be distributed with this problem and I think this may not be interesting, so I am reporting this case. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.402 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 08:25:20 2017 InstallationDate: Installed on 2017-09-29 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1721763 Title: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart Status in ubuntu-meta package in Ubuntu: New Bug description: I really do not know which package to assign this incident, please excuse me. Any way, the release candidates is near, and this problem continues to occur since linux kernel was updated from 4.11 to 4.12 ... and now with version 4.13 the problem continues. I noticed that this problem does not occur with my other two older notebooks (one Sony Vaio and the other a generic one integrated by me) both old notes use NVIDIA video card in versions of more than 5 years ago. My new Dell notebook has a GTX 1050 video card ... but I also do not know if the cause of this problem may be linked to the video card and the fact that Nouveau driver and linux Kernel have received recent implementations for compatibilities with this new NVIDIA technology. The fact is that Ubuntu 17.10 has potential to be distributed with this problem and I think this may not be interesting, so I am reporting this case. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.402 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 08:25:20 2017 InstallationDate: Installed on 2017-09-29 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1721763/+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 1721763] Re: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart
By the way, the issue I want to relate is just that one on the sumary: All times I shut down or reboot my notebook, ubuntu stay stuck in black screen whit blinking cursor at top left side... No text login prompt to appears, as expected. I noticed that this issue was alredy reported some time ago... and there was too much workarounds... related to changing the grub splash screen configuration or changing the USB 3.0 configuration at the bios setup... But nothing of that solved my case. I have a similar problem when I try to change de workarea of linux using Ctrl+Alt+F2 or Ctrl+Alt+F3 etc. At the same way, linux not show me the prompt but stay stuck in a black screen with blinking cursor. To get out of this I have to give severals changes by repetig Ctrl+Alt+F5 ...Ctrl+Alt+F6 Ctrl+Alt+F7 Ctrl+Alt+F6 Ctrl+Alt+F5... because I noticed that this seems to force the text login prompt to appear. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1721763 Title: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart Status in ubuntu-meta package in Ubuntu: New Bug description: I really do not know which package to assign this incident, please excuse me. Any way, the release candidates is near, and this problem continues to occur since linux kernel was updated from 4.11 to 4.12 ... and now with version 4.13 the problem continues. I noticed that this problem does not occur with my other two older notebooks (one Sony Vaio and the other a generic one integrated by me) both old notes use NVIDIA video card in versions of more than 5 years ago. My new Dell notebook has a GTX 1050 video card ... but I also do not know if the cause of this problem may be linked to the video card and the fact that Nouveau driver and linux Kernel have received recent implementations for compatibilities with this new NVIDIA technology. The fact is that Ubuntu 17.10 has potential to be distributed with this problem and I think this may not be interesting, so I am reporting this case. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.402 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 08:25:20 2017 InstallationDate: Installed on 2017-09-29 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1721763/+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 1721763] Re: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart
Most of the time, such problem means a non responding task still running in the background. So be sure your system is cleaned (use gtkorphan & bleachbit to clean it). While shutting down, hitting 'Esc' key will swicth to text mode (like quite splash removal into grub). Or make the journald permanent, then on the next boot, you can know whats is going on. https://ibhagat.blogspot.co.uk/2016/01/rhel7-configure-persistent-systemd.html ** Changed in: ubuntu-meta (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1721763 Title: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: I really do not know which package to assign this incident, please excuse me. Any way, the release candidates is near, and this problem continues to occur since linux kernel was updated from 4.11 to 4.12 ... and now with version 4.13 the problem continues. I noticed that this problem does not occur with my other two older notebooks (one Sony Vaio and the other a generic one integrated by me) both old notes use NVIDIA video card in versions of more than 5 years ago. My new Dell notebook has a GTX 1050 video card ... but I also do not know if the cause of this problem may be linked to the video card and the fact that Nouveau driver and linux Kernel have received recent implementations for compatibilities with this new NVIDIA technology. The fact is that Ubuntu 17.10 has potential to be distributed with this problem and I think this may not be interesting, so I am reporting this case. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.402 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 08:25:20 2017 InstallationDate: Installed on 2017-09-29 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1721763/+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 1721763] Re: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart
Also note that nvidia driver have issue with wayland (see ubuntuforums u+1), so select a xorg session instead at login time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1721763 Title: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: I really do not know which package to assign this incident, please excuse me. Any way, the release candidates is near, and this problem continues to occur since linux kernel was updated from 4.11 to 4.12 ... and now with version 4.13 the problem continues. I noticed that this problem does not occur with my other two older notebooks (one Sony Vaio and the other a generic one integrated by me) both old notes use NVIDIA video card in versions of more than 5 years ago. My new Dell notebook has a GTX 1050 video card ... but I also do not know if the cause of this problem may be linked to the video card and the fact that Nouveau driver and linux Kernel have received recent implementations for compatibilities with this new NVIDIA technology. The fact is that Ubuntu 17.10 has potential to be distributed with this problem and I think this may not be interesting, so I am reporting this case. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.402 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 08:25:20 2017 InstallationDate: Installed on 2017-09-29 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1721763/+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 1707929] Re: [FFe] Revert blacklisting of Indic layouts
uploaded ** Changed in: xkeyboard-config (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1707929 Title: [FFe] Revert blacklisting of Indic layouts Status in xkeyboard-config: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Committed Status in xkeyboard-config package in Debian: Fix Released Bug description: In xkeyboard-config 2.19-1 several Indic keyboard layouts were moved to "extras". https://cgit.freedesktop.org/xkeyboard-config/commit/?id=913af7 The measure has been criticized and has been reverted afterwards at both freedesktop.org and Debian. We should make sure it's reverted in Ubuntu 17.10 as well. To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1707929/+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 1721750] Re: package libwind0-heimdal:amd64 7.1.0+dfsg-9ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempti
Thanks for filing this bug in Ubuntu. Could you please try the following: sudo apt update sudo apt install --reinstall libwind0-heimdal:amd64 sudo apt -f install ** Changed in: heimdal (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1721750 Title: package libwind0-heimdal:amd64 7.1.0+dfsg-9ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in heimdal package in Ubuntu: Incomplete Bug description: when i try to installl "sudo apt install git" it getting errror i guesst ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libwind0-heimdal:amd64 7.1.0+dfsg-9ubuntu1.1 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 AptOrdering: liberror-perl:amd64: Install git-man:amd64: Install git:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Oct 6 17:38:08 2017 Dependencies: gcc-6-base 6.3.0-12ubuntu2 libc6 2.24-9ubuntu2.2 libcomerr2 1.43.4-2 libgcc1 1:6.3.0-12ubuntu2 libroken18-heimdal 7.1.0+dfsg-9ubuntu1.1 DpkgHistoryLog: Start-Date: 2017-10-06 17:38:01 Commandline: apt install git Requested-By: ramdhan (1000) Install: git-man:amd64 (1:2.11.0-2ubuntu0.3, automatic), git:amd64 (1:2.11.0-2ubuntu0.3), liberror-perl:amd64 (0.17024-1, automatic) ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-09-24 (11 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: heimdal Title: package libwind0-heimdal:amd64 7.1.0+dfsg-9ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1721750/+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 1706052] Re: cupsd crashes with SIGSEGV on ubuntu 17.04 on start
Thanks, so the adding of said line to usr.sbin.cupsd helps? Can you test Artful (on a virtual machine or as a live system) to see whether it has the same problem and whether it can be fixed the same way? Note that the problems of HPLIP you mention do not have anything to do with the CUPS package or the AppArmor profile of CUPS. Please report a bug on hplip for them. -- 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/1706052 Title: cupsd crashes with SIGSEGV on ubuntu 17.04 on start Status in cups package in Ubuntu: Incomplete Bug description: Hey, I upgraded to Ubuntu 17.04, but CUPS crashes on boot, and when I run cupsd it segfaults. Attaching strace ouput. --- ApportVersion: 2.20.4-0ubuntu4.4 Architecture: amd64 CupsErrorLog: CurrentDesktop: KDE DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2012-12-20 (1698 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: ASUSTeK COMPUTER INC. UX303LB NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: cups 2.2.2-1ubuntu1 PackageArchitecture: amd64 Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 pcie_aspm=force drm.vblankoffdelay=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 pcie_aspm=force drm.vblankoffdelay=1 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Tags: zesty Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: Upgraded to zesty on 2017-04-19 (117 days ago) UserGroups: adm bluetooth bumblebee cdrom dialout dip lp lpadmin netdev nvidia-persistenced plugdev sambashare sudo usrp _MarkForUpload: True dmi.bios.date: 03/17/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LB.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX303LB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.cups.cupsd.conf: 2015-10-21T13:38:49.740915 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1706052/+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 1717951] Re: UIFe: Drop imagemagick-display from the default install
amano, please file a separate bug for the cups issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1717951 Title: UIFe: Drop imagemagick-display from the default install Status in ubuntu-settings package in Ubuntu: Fix Released Status in imagemagick package in Debian: New Bug description: Impact == I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10. It is visible in the Show Applications view of the Activities Overview so this could impact screenshots. Justification = imagemagick is a collection of commandline utilities for working with images, photos, etc. It is a required dependency for many things and will still be installed by default. Bundled with imagemagick is the "display" app, which is an app with an unusual, difficult-to-use UI. It was not intentionally included in the default Ubuntu install but was only there because it was packaged together. I am proposing splitting the display app to a separate binary package so that it is available for install for the few who do want to use the app. I tried proposing this to Debian. See comment #60 on the attached Debian bug but the Debian maintainer doesn't seem interested in accepting my proposal any time soon. (I emailed him directly a few months ago too.) List Notifications == https://lists.ubuntu.com/archives/ubuntu-doc/2017-September/020534.html https://lists.ubuntu.com/archives/ubuntu-translators/2017-September/007403.html Other Info == I will be attaching a patch for review by the Desktop Team here soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1717951/+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 1682102] Re: libseccomp should support GA and HWE kernels
** Description changed: - Currently libseccomp version in Ubuntu are: + [Impact] - libseccomp | 2.2.3-3ubuntu3 | xenial | source - libseccomp | 2.3.1-2ubuntu2 | yakkety| source - libseccomp | 2.3.1-2.1ubuntu1 | zesty | source + out of date libseccomp w.r.t. custom and hwe kernels provides sub-par userspace protection, which is otherwise available on the running kernel and hardware combination. + This results in subpar security of systems running new architectures (s390x & ppc64el) and newer hwe/custom kernels. - The difference between 2.2.3 and 2.3.1 is 63 upstream commits. + * Version 2.3.1 - April 20, 2016 + - Fixed a problem with 32-bit x86 socket syscalls on some systems + - Fixed problems with ipc syscalls on 32-bit x86 + - Fixed problems with socket and ipc syscalls on s390 and s390x + + * Version 2.3.0 - February 29, 2016 + - Added support for the s390 and s390x architectures + - Added support for the ppc, ppc64, and ppc64le architectures + - Update the internal syscall tables to match the Linux 4.5-rcX releases + - Filter generation for both multiplexed and direct socket syscalls on x86 + - Support for the musl libc implementation + - Additions to the API to enable runtime version checking of the library + - Enable the use of seccomp() instead of prctl() on supported systems + - Added additional tests to the regression test suite - Of those commits, 7 are already cherrypicked into xenial for s390x - support. + There is no ABI/API break - However that s390x support is incomplete as multiplexed syscalls are not - supported. + There are no packaging changes, apart from dropping patches included in + this upstream release and updating new symbols. - A request has been filed to support multiplexed syscalls in libseccomp - in xenial at - https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1679691 + Doing wholesome update is safer and carries less risk, than individually + cherrypicking effectively all of the above. - That is a request for further 18 commits to backport, bringing the total - to 25. + This is a backport to an LTS release under the banner of safe + introduction of new features and new hardware support. - Looking at the remaining 38 commits there are: - - documentation updates - - tools updates - - tests updates - - bugfixes - - updates to syscall tables for linux 4.3, 4.5-rc4+ + It is expected that container technologies will take advantage of the + newly available libseccomp. - IMHO, in the future when libseccomp is updated to support 4.10 kernel - syscalls, it should be backported back to xenial too, to properly suppor - the HWE kernels. + This may need to be uploaded as a security update. + + Currently, s390x support in xenial libssecomp is incomplete. And there + are v4.5+ syscall tables missing as used by hwe
[Touch-packages] [Bug 1719934] Re: Missing fonts in list of languages
Fix verified in today's ISO ** Changed in: ubuntu-meta (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1719934 Title: Missing fonts in list of languages Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: There is a font missing on the ISO and one of the language is shown as unicode characters (cf screenshot) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 11:22:24 2017 InstallationDate: Installed on 2013-09-03 (1484 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1719934/+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 1717216] Re: FFe: Sync libsoup2.4 2.60.0-1 (main) from Debian unstable (main)
** Tags added: artful upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsoup2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1717216 Title: FFe: Sync libsoup2.4 2.60.0-1 (main) from Debian unstable (main) Status in libsoup2.4 package in Ubuntu: New Bug description: Please sync libsoup2.4 2.60.0-1 (main) from Debian unstable (main) Explanation of FeatureFreeze exception: libsoup follows the GNOME release cycle and we're shipping the rest of GNOME 3.26. Also, libsoup is a security sensitive package. (And 2.59.90.1 fixes CVE-2017-2885). I think it's (slightly) easier for the Security Team to backport security fixes for newer releases. https://git.gnome.org/browse/libsoup/tree/NEWS https://git.gnome.org/browse/libsoup/log/ Changelog entries since current artful version 2.56.1-1: libsoup2.4 (2.60.0-1) unstable; urgency=medium * New upstream translations release -- Jeremy Bicha Tue, 12 Sep 2017 11:03:12 -0400 libsoup2.4 (2.59.90.1-1) unstable; urgency=medium * New upstream release * Drop all patches, applied in new release * debian/libsoup2.4-1.symbols: Add new symbols * debian/control.in: - Build-depend on apache2 and php-xmlrpc for build tests * Bump Standards-Version to 4.1.0 -- Jeremy Bicha Wed, 30 Aug 2017 20:59:56 -0400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1717216/+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 1718055] Re: update-initramfs fails for MODULES=dep when root is on LVM wich uses nvme device
the linux autopkgtest failure is due to the kernel team change to only build a single kernel 'flavour' to reduce test rebuild time, but the autopkgtest still expects the (no longer built) -lpae flavor on armhf. The kernel team has a bug open for it and is fixing it in the next build. -- 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/1718055 Title: update-initramfs fails for MODULES=dep when root is on LVM wich uses nvme device Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Trusty: Fix Committed Bug description: [impact] On a trusty system, if using MODULES=dep with lvm-on-nvme then update- initramfs fails to rebuild the initramfs. This prevents using MODULES=dep for building an initramfs on trusty, with a rootfs that uses lvm on nvme. [test case] install a system where the rootfs uses a LVM logical volume that is located on a physical volume on a NVMe drive. Edit the /etc /initramfs-tools/initramfs.conf file and change the MODULES line to MODULES=dep and save the file. Then run sudo update-initramfs -u which will fail with: $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-3.13.0-129-generic mkinitramfs: for root /dev/dm-0 missing nvme /sys/block/ entry mkinitramfs: workaround is MODULES=most mkinitramfs: Error please report the bug update-initramfs: failed for /boot/initrd.img-3.13.0-129-generic with 1. [regression potential] This changes initramfs creation for rootfs that are on nvme or lvm, so has the potential to break it for any system with its rootfs on either or both of those. It is likely to only break initramfs creation, not system booting. [other info] related to bug 1532146 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1718055/+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 1719934] Re: Missing fonts in list of languages
I used fix committed since we still have to do a new ubuntu-meta upload to update the metapackage to match the seed. I'm planning on doing that this weekend for LP: #1720809 anyway. ** Changed in: ubuntu-meta (Ubuntu) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1719934 Title: Missing fonts in list of languages Status in ubuntu-meta package in Ubuntu: Fix Committed Bug description: There is a font missing on the ISO and one of the language is shown as unicode characters (cf screenshot) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 11:22:24 2017 InstallationDate: Installed on 2013-09-03 (1484 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1719934/+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 1662031] Re: Switching language and format broken
In /etc/pam.d/gdm-launch-environment: session requiredpam_env.so readenv=1 user_readenv=1 envfile=/etc/default/locale In pam_env.c (handle_env function), the env should be set from /etc/default/locale and then overridden by ~/.pam_environment. If I add the 'debug' parameter to the module invokation, I see only the calls to pam_putenv corresponding to /etc/default/locale, which means that for some reason to be determined ~/.pam_environment is not being sourced. -- 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/1662031 Title: Switching language and format broken Status in Ubuntu GNOME: New Status in accountsservice package in Ubuntu: New Status in gdm3 package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: New Status in accountsservice source package in Artful: New Status in gdm3 source package in Artful: Confirmed Status in gnome-control-center source package in Artful: New Bug description: In Ubuntu GNOME 16.10 it doesn't matter what display language I select - the effective language is still the one stated in /etc/default/locale. ~/.pam_environment is changed as expected, but the variables set in /etc/default/locale override ~/.pam_environment. In Ubuntu GNOME 16.04 language switching takes effect, but the reason for that seems to be that /etc/default/locale is changed as well, so when a user changes the display language (or format), it changes it for all users on the system. The overriding by /etc/default/locale is probably caused by some other package(s) but g-c-c. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1662031/+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 1721795] [NEW] Move Recommends: gnome-getting-started-docs from ubuntu-docs to ubuntu-desktop
Public bug reported: Ubuntu Budgie includes ubuntu-docs since it's generally useful and they don't have another docs system. But Ubuntu Budgie does not need gnome-getting-started-docs https://help.gnome.org/users/gnome-help/stable/getting-started.html We can fix this issue by having ubuntu-desktop recommend gnome-getting- started-docs and dropping that recommends from ubuntu-docs. ** Affects: ubuntu-docs (Ubuntu) Importance: Undecided Status: Fix Committed ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: Confirmed ** Also affects: ubuntu-docs (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-docs (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1721795 Title: Move Recommends: gnome-getting-started-docs from ubuntu-docs to ubuntu-desktop Status in ubuntu-docs package in Ubuntu: Fix Committed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Ubuntu Budgie includes ubuntu-docs since it's generally useful and they don't have another docs system. But Ubuntu Budgie does not need gnome-getting-started-docs https://help.gnome.org/users/gnome-help/stable/getting-started.html We can fix this issue by having ubuntu-desktop recommend gnome- getting-started-docs and dropping that recommends from ubuntu-docs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1721795/+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 1721795] Re: Move Recommends: gnome-getting-started-docs from ubuntu-docs to ubuntu-desktop
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1721795 Title: Move Recommends: gnome-getting-started-docs from ubuntu-docs to ubuntu-desktop Status in ubuntu-docs package in Ubuntu: Fix Committed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Ubuntu Budgie includes ubuntu-docs since it's generally useful and they don't have another docs system. But Ubuntu Budgie does not need gnome-getting-started-docs https://help.gnome.org/users/gnome-help/stable/getting-started.html We can fix this issue by having ubuntu-desktop recommend gnome- getting-started-docs and dropping that recommends from ubuntu-docs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1721795/+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 1717794] Re: apport-gtk crashed with SIGABRT in g_assertion_message()
** Changed in: apport (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1717794 Title: apport-gtk crashed with SIGABRT in g_assertion_message() Status in apport package in Ubuntu: Incomplete Bug description: just this say ERROR ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: apport-gtk 2.20.7-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-10.11-generic 4.13.1 Uname: Linux 4.13.0-10-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 17 13:38:44 2017 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2017-07-24 (54 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_AR.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 3.6.1-0ubuntu3 PythonDetails: /usr/bin/python2.7, Python 2.7.14rc1, python-minimal, 2.7.13-2 Signal: 6 SourcePackage: apport StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1717794/+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 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore
I spend a bit of time debugging this with xnox. Here some of the results: # How to reproduce: I setup a isc-dhcp-server with a fixed IP for my test rpi2 set to default/max lifetime of 120sec. The rpi2 was connected to the network with the isc-dhcp-server but unmodified otherwise. Once the pi2 connected and got an IP I switched the default IP to +1 and reloaded the isc-dhcp-server configuration. When the lease expired I could see the same as the OP - i.e. both IPs got removed. # Related upstream bugs: The patch from https://github.com/systemd/systemd/issues/5625 did not help with the issue # Log The full log of systemd-networkd is available here: http://paste.ubuntu.com/25686225/ - it was obtained by adding [Service]\nEnvironment=SYSTEMD_LOG_LEVEL=debug for the systemd-networkd.service. The relevant lines: Mar 14 21:02:52 localhost.localdomain systemd-networkd[7660]: eth0: Adding address: 192.168.1.124/24 (valid for 2min) Mar 14 21:02:52 localhost.localdomain systemd-networkd[7660]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/network1/link/_33 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=16 reply_cookie=0 error=n/a Mar 14 21:02:52 localhost.localdomain systemd-networkd[7660]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/network1 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=17 reply_cookie=0 error=n/a Mar 14 21:02:52 localhost.localdomain systemd-timesyncd[995]: Network configuration changed, trying to establish connection. Mar 14 21:02:52 localhost.localdomain systemd[1]: Starting Update resolvconf for networkd DNS... Mar 14 21:02:56 localhost.localdomain systemd-networkd[7660]: NDISC: Sent Router Solicitation Mar 14 21:03:00 localhost.localdomain systemd-networkd[7660]: NDISC: Sent Router Solicitation Mar 14 21:03:04 localhost.localdomain systemd-networkd[7660]: NDISC: Invoking callback for 't'. Mar 14 21:03:22 localhost.localdomain systemd[1]: Started Update resolvconf for networkd DNS. Mar 14 21:03:51 localhost.localdomain systemd-networkd[7660]: DHCP CLIENT (0x22f0fd4b): REQUEST (renewing) Mar 14 21:04:36 localhost.localdomain systemd-networkd[7660]: DHCP CLIENT (0x22f0fd4b): REQUEST (rebinding) Mar 14 21:04:36 localhost.localdomain systemd-networkd[7660]: DHCP CLIENT (0x22f0fd4b): NAK: requested address is incorrect Mar 14 21:04:36 localhost.localdomain systemd-networkd[7660]: DHCP CLIENT (0x4d15b90b): REBOOT in 0 Mar 14 21:04:36 localhost.localdomain systemd-networkd[7660]: DHCP CLIENT (0x4d15b90b): DISCOVER Mar 14 21:04:36 localhost.localdomain systemd-networkd[7660]: DHCP CLIENT (0x4d15b90b): OFFER Mar 14 21:04:36 localhost.localdomain systemd-networkd[7660]: DHCP CLIENT (0x4d15b90b): REQUEST (requesting) Mar 14 21:04:36 localhost.localdomain systemd-networkd[7660]: DHCP CLIENT (0x4d15b90b): ACK Mar 14 21:04:36 localhost.localdomain systemd-networkd[7660]: DHCP CLIENT (0x4d15b90b): lease expires in 1min 57s Mar 14 21:04:36 localhost.localdomain systemd-networkd[7660]: DHCP CLIENT (0x4d15b90b): T2 expires in 1min 43s Mar 14 21:04:36 localhost.localdomain systemd-networkd[7660]: DHCP CLIENT (0x4d15b90b): T1 expires in 1min Mar 14 21:04:36 localhost.localdomain systemd-networkd[7660]: eth0: DHCPv4 address 192.168.1.125/24 Mar 14 21:04:36 localhost.localdomain systemd-timesyncd[995]: Network configuration changed, trying to establish connection. Mar 14 21:04:36 localhost.localdomain systemd-networkd[7660]: eth0: Updating address: 192.168.1.125/24 (valid for 2min) Mar 14 21:04:36 localhost.localdomain systemd[1]: Starting Update resolvconf for networkd DNS... Mar 14 21:04:52 localhost.localdomain systemd-networkd[7660]: eth0: Removing address: 192.168.1.125/24 (valid for 1min 44s) Mar 14 21:04:52 localhost.localdomain systemd-networkd[7660]: eth0: Removing address: 192.168.1.124/24 (valid for 0) Mar 14 21:04:52 localhost.localdomain systemd-networkd[7660]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/network1/link/_33 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=18 reply_cookie=0 error=n/a Mar 14 21:04:52 localhost.localdomain systemd-networkd[7660]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/network1 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=19 reply_cookie=0 error=n/a Mar 14 21:04:52 localhost.localdomain systemd-timesyncd[995]: Network configuration changed, trying to establish connection. Mar 14 21:05:06 localhost.localdomain systemd[1]: Started Update resolvconf for networkd DNS. ** Bug watch added: github.com/systemd/systemd/issues #5625 https://github.com/systemd/systemd/issues/5625 -- 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/1721223 Title: Networkd fail to set ip address
[Touch-packages] [Bug 1718055] Re: update-initramfs fails for MODULES=dep when root is on LVM wich uses nvme device
** Description changed: [impact] On a trusty system, if using MODULES=dep with lvm-on-nvme then update- initramfs fails to rebuild the initramfs. This prevents using MODULES=dep for building an initramfs on trusty, with a rootfs that uses lvm on nvme. [test case] install a system where the rootfs uses a LVM logical volume that is located on a physical volume on a NVMe drive. Edit the /etc/initramfs- tools/initramfs.conf file and change the MODULES line to MODULES=dep and save the file. Then run sudo update-initramfs -u which will fail with: $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-3.13.0-129-generic mkinitramfs: for root /dev/dm-0 missing nvme /sys/block/ entry mkinitramfs: workaround is MODULES=most mkinitramfs: Error please report the bug update-initramfs: failed for /boot/initrd.img-3.13.0-129-generic with 1. - [regression potential] This changes initramfs creation for rootfs that are on nvme or lvm, so has the potential to break it for any system with its rootfs on either or both of those. It is likely to only break initramfs creation, not system booting. + About the autopkgtest failure, explanation can be found here: + https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1718055/comments/9 + [other info] related to bug 1532146 -- 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/1718055 Title: update-initramfs fails for MODULES=dep when root is on LVM wich uses nvme device Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Trusty: Fix Committed Bug description: [impact] On a trusty system, if using MODULES=dep with lvm-on-nvme then update- initramfs fails to rebuild the initramfs. This prevents using MODULES=dep for building an initramfs on trusty, with a rootfs that uses lvm on nvme. [test case] install a system where the rootfs uses a LVM logical volume that is located on a physical volume on a NVMe drive. Edit the /etc /initramfs-tools/initramfs.conf file and change the MODULES line to MODULES=dep and save the file. Then run sudo update-initramfs -u which will fail with: $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-3.13.0-129-generic mkinitramfs: for root /dev/dm-0 missing nvme /sys/block/ entry mkinitramfs: workaround is MODULES=most mkinitramfs: Error please report the bug update-initramfs: failed for /boot/initrd.img-3.13.0-129-generic with 1. [regression potential] This changes initramfs creation for rootfs that are on nvme or lvm, so has the potential to break it for any system with its rootfs on either or both of those. It is likely to only break initramfs creation, not system booting. About the autopkgtest failure, explanation can be found here: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1718055/comments/9 [other info] related to bug 1532146 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1718055/+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 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore
Some more data point are the output of "ip addr": http://paste.ubuntu.com/25685527/ The interessting part if: ... 3: eth0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether b8:27:eb:85:3f:94 brd ff:ff:ff:ff:ff:ff inet 192.168.1.116/24 brd 192.168.1.255 scope global dynamic eth0 valid_lft 7sec preferred_lft 7sec inet 192.168.1.117/24 brd 192.168.1.255 scope global secondary dynamic eth0 valid_lft 109sec preferred_lft 109sec inet6 fe80::ba27:ebff:fe85:3f94/64 scope link valid_lft forever preferred_lft forever ... and then 3: eth0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether b8:27:eb:85:3f:94 brd ff:ff:ff:ff:ff:ff inet6 fe80::ba27:ebff:fe85:3f94/64 scope link valid_lft forever preferred_lft forever -- 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/1721223 Title: Networkd fail to set ip address between leases if ip address changes on UbuntuCore Status in Snappy: New Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: New Bug description: Hi there, we found a replicable issue that involves the Ubuntu Core networking and causes complete loss of connectivity. We run a custom board with ubuntu core: the architecure is amrhf. We replicated this issue with an official Ubuntu Core image on a Raspberry Pi: other platform was been tested. It shows that it is a snap core problem which interests networkd: we use the default network stack based on networkd + netplan. Below steps to replicate the issue. 1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes). 2)Boot the board and wait for get an ip from dhcp server 3)Before the lease expires, set a reservation for a different ip address Depending on lease duration before the lease expires( for 10 minute we have 2 minutes before ), networkd configure the new address in addition to the previous one. When the lease expire both ip address ( the prevoius and the new one ) disappear from the interested network interface. Depending on lease duration before the second lease expires ( for 10 minure we have 2 minutes before ) networkd configure only the new ip address on the network interface and the ping toward an outside host work properly. During the test the dhcp server records correctly leases and their duration. We check directly from console the network interface setting with the tool ip, checking continuously the value for ip address and valid_lft fields for the interested network interface. Please note that if the ip address setting are the same between leases the problem doesn’t jump out. Please note that if the ip address setting are different between lease the problem jumps out and it is very bad: Typically the lease time on consumer router are about some day, then a board that change ip between lease loses the network connectivity for some day without a direct action. Please, after a confirmation from your side of the issue, could you fix the problem or escalate the issue at the upstream project? We are available for further testing. Below syslog annotated with ip address state: Oct 4 09:48:06 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:49:36 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:49:25 localhost systemd-timesyncd[996]: Network configuration changed, trying to establish connection. Oct 4 09:49:26 localhost systemd-timesyncd[996]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com). Oct 4 09:49:26 localhost systemd[1]: Starting Update resolvconf for networkd DNS... Oct 4 09:49:26 localhost systemd[1]: Started Update resolvconf for networkd DNS. Oct 4 09:49:37 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:51:07 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:51:09 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:52:39 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:52:40 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:54:10 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:54:11 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:55:41 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:54:23 localhost systemd-timesyncd[996]: Network configuration changed, trying to establish connection. Oct 4 09:54:23 localhost systemd[1]: Starting Update resolvconf for networkd DNS... Oct 4 09:54:23 localhost systemd-timesyncd[996]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com). Oct 4 09:54:23 localhost systemd[1]: Started Update resolvconf for networkd DNS. Oct 4 09:55:43 localhost rsyslogd-2007: action
[Touch-packages] [Bug 1682102] Re: libseccomp should support GA and HWE kernels
** Description changed: [Impact] out of date libseccomp w.r.t. custom and hwe kernels provides sub-par userspace protection, which is otherwise available on the running kernel and hardware combination. This results in subpar security of systems running new architectures (s390x & ppc64el) and newer hwe/custom kernels. - * Version 2.3.1 - April 20, 2016 - - Fixed a problem with 32-bit x86 socket syscalls on some systems - - Fixed problems with ipc syscalls on 32-bit x86 - - Fixed problems with socket and ipc syscalls on s390 and s390x - - * Version 2.3.0 - February 29, 2016 - - Added support for the s390 and s390x architectures - - Added support for the ppc, ppc64, and ppc64le architectures - - Update the internal syscall tables to match the Linux 4.5-rcX releases - - Filter generation for both multiplexed and direct socket syscalls on x86 - - Support for the musl libc implementation - - Additions to the API to enable runtime version checking of the library - - Enable the use of seccomp() instead of prctl() on supported systems - - Added additional tests to the regression test suite + * Version 2.3.1 - April 20, 2016 + - Fixed a problem with 32-bit x86 socket syscalls on some systems + - Fixed problems with ipc syscalls on 32-bit x86 + - Fixed problems with socket and ipc syscalls on s390 and s390x + + * Version 2.3.0 - February 29, 2016 + - Added support for the s390 and s390x architectures + - Added support for the ppc, ppc64, and ppc64le architectures + - Update the internal syscall tables to match the Linux 4.5-rcX releases + - Filter generation for both multiplexed and direct socket syscalls on x86 + - Support for the musl libc implementation + - Additions to the API to enable runtime version checking of the library + - Enable the use of seccomp() instead of prctl() on supported systems + - Added additional tests to the regression test suite There is no ABI/API break There are no packaging changes, apart from dropping patches included in this upstream release and updating new symbols. Doing wholesome update is safer and carries less risk, than individually cherrypicking effectively all of the above. This is a backport to an LTS release under the banner of safe introduction of new features and new hardware support. It is expected that container technologies will take advantage of the newly available libseccomp. This may need to be uploaded as a security update. Currently, s390x support in xenial libssecomp is incomplete. And there are v4.5+ syscall tables missing as used by hwe kernels and some custom kernels. [Testcase] Validate that all main contianer technologies are operational and do not regress, e.g.: - - lxc - - lxd - - docker - - snapd + - lxc + - lxd + - docker + - snapd [Regression Potential] Userspace components may detect at runtime newly available libseccomp, and thus
[Touch-packages] [Bug 1706052] Re: cupsd crashes with SIGSEGV on ubuntu 17.04 on start
Yes,
@{PROC}/*/cmdline r,
and resetting to enforce fixed the printing problem. For the record, the same
solution also worked for a problem I was having with the dhclient apparmor
profile that was stopping NetworkManager from connecting.
As for 17.10 Artful, I'm not entirely willing to do that just yet. I
upgraded to Zesty only to attempt to fix a Bluetooth audio problem (it
didn't) without testing the waters first, and got spanked for it. It's
taken me a week just to root out the critical bugs.
As for HPLIP systray, I feel it might be related, since systray will
work with apparmor set to complain on cups (both with and without the
profile edit), but not when set to enforce. Nonetheless, I will file a
bug with HPLIP.
--
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/1706052
Title:
cupsd crashes with SIGSEGV on ubuntu 17.04 on start
Status in cups package in Ubuntu:
Incomplete
Bug description:
Hey,
I upgraded to Ubuntu 17.04, but CUPS crashes on boot, and when I run cupsd it
segfaults. Attaching strace ouput.
---
ApportVersion: 2.20.4-0ubuntu4.4
Architecture: amd64
CupsErrorLog:
CurrentDesktop: KDE
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2012-12-20 (1698 days ago)
InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64
(20121017.1)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad
file descriptor
MachineType: ASUSTeK COMPUTER INC. UX303LB
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Package: cups 2.2.2-1ubuntu1
PackageArchitecture: amd64
Papersize: letter
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791
pcie_aspm=force drm.vblankoffdelay=1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791
pcie_aspm=force drm.vblankoffdelay=1
ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
Tags: zesty
Uname: Linux 4.10.0-28-generic x86_64
UpgradeStatus: Upgraded to zesty on 2017-04-19 (117 days ago)
UserGroups: adm bluetooth bumblebee cdrom dialout dip lp lpadmin netdev
nvidia-persistenced plugdev sambashare sudo usrp
_MarkForUpload: True
dmi.bios.date: 03/17/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX303LB.203
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX303LB
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX303LB
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
mtime.conffile..etc.cups.cupsd.conf: 2015-10-21T13:38:49.740915
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1706052/+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 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore
And the output of "ip monitor eth0": http://paste.ubuntu.com/25686711/ ... 2: eth0inet 192.168.1.130/24 brd 192.168.1.255 scope global secondary dynamic eth0 valid_lft 120sec preferred_lft 120sec local 192.168.1.130 table local proto kernel scope host src 192.168.1.129 Deleted 2: eth0inet 192.168.1.130/24 brd 192.168.1.255 scope global secondary dynamic eth0 valid_lft 110sec preferred_lft 110sec Deleted local 192.168.1.130 table local proto kernel scope host src 192.168.1.129 Deleted 2: eth0inet 192.168.1.129/24 brd 192.168.1.255 scope global dynamic eth0 valid_lft 0sec preferred_lft 0sec Deleted 192.168.1.0/24 proto kernel scope link src 192.168.1.129 Deleted broadcast 192.168.1.255 table local proto kernel scope link src 192.168.1.129 Deleted broadcast 192.168.1.0 table local proto kernel scope link src 192.168.1.129 Deleted local 192.168.1.129 table local proto kernel scope host src 192.168.1.129 Deleted 192.168.1.114 lladdr 00:24:7e:11:b8:aa STALE -- 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/1721223 Title: Networkd fail to set ip address between leases if ip address changes on UbuntuCore Status in Snappy: New Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: New Bug description: Hi there, we found a replicable issue that involves the Ubuntu Core networking and causes complete loss of connectivity. We run a custom board with ubuntu core: the architecure is amrhf. We replicated this issue with an official Ubuntu Core image on a Raspberry Pi: other platform was been tested. It shows that it is a snap core problem which interests networkd: we use the default network stack based on networkd + netplan. Below steps to replicate the issue. 1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes). 2)Boot the board and wait for get an ip from dhcp server 3)Before the lease expires, set a reservation for a different ip address Depending on lease duration before the lease expires( for 10 minute we have 2 minutes before ), networkd configure the new address in addition to the previous one. When the lease expire both ip address ( the prevoius and the new one ) disappear from the interested network interface. Depending on lease duration before the second lease expires ( for 10 minure we have 2 minutes before ) networkd configure only the new ip address on the network interface and the ping toward an outside host work properly. During the test the dhcp server records correctly leases and their duration. We check directly from console the network interface setting with the tool ip, checking continuously the value for ip address and valid_lft fields for the interested network interface. Please note that if the ip address setting are the same between leases the problem doesn’t jump out. Please note that if the ip address setting are different between lease the problem jumps out and it is very bad: Typically the lease time on consumer router are about some day, then a board that change ip between lease loses the network connectivity for some day without a direct action. Please, after a confirmation from your side of the issue, could you fix the problem or escalate the issue at the upstream project? We are available for further testing. Below syslog annotated with ip address state: Oct 4 09:48:06 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:49:36 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:49:25 localhost systemd-timesyncd[996]: Network configuration changed, trying to establish connection. Oct 4 09:49:26 localhost systemd-timesyncd[996]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com). Oct 4 09:49:26 localhost systemd[1]: Starting Update resolvconf for networkd DNS... Oct 4 09:49:26 localhost systemd[1]: Started Update resolvconf for networkd DNS. Oct 4 09:49:37 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:51:07 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:51:09 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:52:39 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:52:40 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:54:10 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:54:11 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:55:41 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:54:23 localhost systemd-timesyncd[996]: Network configuration changed, trying to establish connection. Oct 4 09:54:23 localhost systemd[1]: Starting Update resolvconf for networkd DNS... Oct 4 09:54:23 local
[Touch-packages] [Bug 1721821] [NEW] Lightdm freezes 50 seconds before KDE Plasma starts
Public bug reported: I upgraded my Kubuntu 17.04 to 17.10 four days ago. My PC is booting fast: ~10 seconds to see the greeter. But when I connect to my Plasma session, the greeter is staying ~50 seconds at screen, before Plasma is starting (in ~10 more seconds). There was no problem before upgrading to Kubuntu 17.10. I connected to a terminal session just after having entered my password in the greeter, and I launched the htop command: all I can say is that there is no cpu eating process. The cpu is nearly idle during these 50 seconds. Lightdm version : 1.24.0-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: lightdm 1.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu2 Architecture: i386 CurrentDesktop: KDE Date: Fri Oct 6 18:13:42 2017 InstallationDate: Installed on 2012-07-31 (1893 days ago) InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) SourcePackage: lightdm UpgradeStatus: Upgraded to artful on 2017-10-02 (3 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug artful i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1721821 Title: Lightdm freezes 50 seconds before KDE Plasma starts Status in lightdm package in Ubuntu: New Bug description: I upgraded my Kubuntu 17.04 to 17.10 four days ago. My PC is booting fast: ~10 seconds to see the greeter. But when I connect to my Plasma session, the greeter is staying ~50 seconds at screen, before Plasma is starting (in ~10 more seconds). There was no problem before upgrading to Kubuntu 17.10. I connected to a terminal session just after having entered my password in the greeter, and I launched the htop command: all I can say is that there is no cpu eating process. The cpu is nearly idle during these 50 seconds. Lightdm version : 1.24.0-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: lightdm 1.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu2 Architecture: i386 CurrentDesktop: KDE Date: Fri Oct 6 18:13:42 2017 InstallationDate: Installed on 2012-07-31 (1893 days ago) InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) SourcePackage: lightdm UpgradeStatus: Upgraded to artful on 2017-10-02 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1721821/+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 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore
With ip monitor all: http://paste.ubuntu.com/25686763/ -- 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/1721223 Title: Networkd fail to set ip address between leases if ip address changes on UbuntuCore Status in Snappy: New Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: New Bug description: Hi there, we found a replicable issue that involves the Ubuntu Core networking and causes complete loss of connectivity. We run a custom board with ubuntu core: the architecure is amrhf. We replicated this issue with an official Ubuntu Core image on a Raspberry Pi: other platform was been tested. It shows that it is a snap core problem which interests networkd: we use the default network stack based on networkd + netplan. Below steps to replicate the issue. 1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes). 2)Boot the board and wait for get an ip from dhcp server 3)Before the lease expires, set a reservation for a different ip address Depending on lease duration before the lease expires( for 10 minute we have 2 minutes before ), networkd configure the new address in addition to the previous one. When the lease expire both ip address ( the prevoius and the new one ) disappear from the interested network interface. Depending on lease duration before the second lease expires ( for 10 minure we have 2 minutes before ) networkd configure only the new ip address on the network interface and the ping toward an outside host work properly. During the test the dhcp server records correctly leases and their duration. We check directly from console the network interface setting with the tool ip, checking continuously the value for ip address and valid_lft fields for the interested network interface. Please note that if the ip address setting are the same between leases the problem doesn’t jump out. Please note that if the ip address setting are different between lease the problem jumps out and it is very bad: Typically the lease time on consumer router are about some day, then a board that change ip between lease loses the network connectivity for some day without a direct action. Please, after a confirmation from your side of the issue, could you fix the problem or escalate the issue at the upstream project? We are available for further testing. Below syslog annotated with ip address state: Oct 4 09:48:06 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:49:36 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:49:25 localhost systemd-timesyncd[996]: Network configuration changed, trying to establish connection. Oct 4 09:49:26 localhost systemd-timesyncd[996]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com). Oct 4 09:49:26 localhost systemd[1]: Starting Update resolvconf for networkd DNS... Oct 4 09:49:26 localhost systemd[1]: Started Update resolvconf for networkd DNS. Oct 4 09:49:37 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:51:07 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:51:09 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:52:39 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:52:40 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:54:10 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:54:11 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:55:41 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:54:23 localhost systemd-timesyncd[996]: Network configuration changed, trying to establish connection. Oct 4 09:54:23 localhost systemd[1]: Starting Update resolvconf for networkd DNS... Oct 4 09:54:23 localhost systemd-timesyncd[996]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com). Oct 4 09:54:23 localhost systemd[1]: Started Update resolvconf for networkd DNS. Oct 4 09:55:43 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:57:13 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:57:14 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:58:44 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:58:46 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 10:00:16 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 10:00:17 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 10:01:47 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 10:01:48 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 10:03:18 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 10
[Touch-packages] [Bug 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore
The output if dhclient is running with the same scenario: http://paste.ubuntu.com/25686791/ -- 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/1721223 Title: Networkd fail to set ip address between leases if ip address changes on UbuntuCore Status in Snappy: New Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: New Bug description: Hi there, we found a replicable issue that involves the Ubuntu Core networking and causes complete loss of connectivity. We run a custom board with ubuntu core: the architecure is amrhf. We replicated this issue with an official Ubuntu Core image on a Raspberry Pi: other platform was been tested. It shows that it is a snap core problem which interests networkd: we use the default network stack based on networkd + netplan. Below steps to replicate the issue. 1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes). 2)Boot the board and wait for get an ip from dhcp server 3)Before the lease expires, set a reservation for a different ip address Depending on lease duration before the lease expires( for 10 minute we have 2 minutes before ), networkd configure the new address in addition to the previous one. When the lease expire both ip address ( the prevoius and the new one ) disappear from the interested network interface. Depending on lease duration before the second lease expires ( for 10 minure we have 2 minutes before ) networkd configure only the new ip address on the network interface and the ping toward an outside host work properly. During the test the dhcp server records correctly leases and their duration. We check directly from console the network interface setting with the tool ip, checking continuously the value for ip address and valid_lft fields for the interested network interface. Please note that if the ip address setting are the same between leases the problem doesn’t jump out. Please note that if the ip address setting are different between lease the problem jumps out and it is very bad: Typically the lease time on consumer router are about some day, then a board that change ip between lease loses the network connectivity for some day without a direct action. Please, after a confirmation from your side of the issue, could you fix the problem or escalate the issue at the upstream project? We are available for further testing. Below syslog annotated with ip address state: Oct 4 09:48:06 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:49:36 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:49:25 localhost systemd-timesyncd[996]: Network configuration changed, trying to establish connection. Oct 4 09:49:26 localhost systemd-timesyncd[996]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com). Oct 4 09:49:26 localhost systemd[1]: Starting Update resolvconf for networkd DNS... Oct 4 09:49:26 localhost systemd[1]: Started Update resolvconf for networkd DNS. Oct 4 09:49:37 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:51:07 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:51:09 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:52:39 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:52:40 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:54:10 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:54:11 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:55:41 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:54:23 localhost systemd-timesyncd[996]: Network configuration changed, trying to establish connection. Oct 4 09:54:23 localhost systemd[1]: Starting Update resolvconf for networkd DNS... Oct 4 09:54:23 localhost systemd-timesyncd[996]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com). Oct 4 09:54:23 localhost systemd[1]: Started Update resolvconf for networkd DNS. Oct 4 09:55:43 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:57:13 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:57:14 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:58:44 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:58:46 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 10:00:16 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 10:00:17 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 10:01:47 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 10:01:48 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 10:03:18 2017 [v8.16.0 try http://
[Touch-packages] [Bug 1721821] Re: Lightdm freezes 50 seconds before KDE Plasma starts
I made an error: my system is using sddm and not lightdm (although this package is also installed). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1721821 Title: sddm freezes 50 seconds before KDE Plasma starts Status in sddm package in Ubuntu: New Bug description: I upgraded my Kubuntu 17.04 to 17.10 four days ago. My PC is booting fast: ~10 seconds to see the greeter. But when I connect to my Plasma session, the greeter is staying ~50 seconds at screen, before Plasma is starting (in ~10 more seconds). There was no problem before upgrading to Kubuntu 17.10. I connected to a terminal session just after having entered my password in the greeter, and I launched the htop command: all I can say is that there is no cpu eating process. The cpu is nearly idle during these 50 seconds. Lightdm version : 1.24.0-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: lightdm 1.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu2 Architecture: i386 CurrentDesktop: KDE Date: Fri Oct 6 18:13:42 2017 InstallationDate: Installed on 2012-07-31 (1893 days ago) InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) SourcePackage: lightdm UpgradeStatus: Upgraded to artful on 2017-10-02 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1721821/+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 1721821] Re: Lightdm freezes 50 seconds before KDE Plasma starts
My system is using sddm, not lightdm (sorry) ** Package changed: lightdm (Ubuntu) => sddm (Ubuntu) ** Summary changed: - Lightdm freezes 50 seconds before KDE Plasma starts + sddm freezes 50 seconds before KDE Plasma starts ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1721821/+attachment/4963843/+files/Dependencies.txt ** Attachment removed: "LightdmConfig.txt" https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1721821/+attachment/4963845/+files/LightdmConfig.txt ** Attachment removed: "LightdmUsersConfig.txt" https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1721821/+attachment/4963846/+files/LightdmUsersConfig.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1721821 Title: sddm freezes 50 seconds before KDE Plasma starts Status in sddm package in Ubuntu: New Bug description: I upgraded my Kubuntu 17.04 to 17.10 four days ago. My PC is booting fast: ~10 seconds to see the greeter. But when I connect to my Plasma session, the greeter is staying ~50 seconds at screen, before Plasma is starting (in ~10 more seconds). There was no problem before upgrading to Kubuntu 17.10. I connected to a terminal session just after having entered my password in the greeter, and I launched the htop command: all I can say is that there is no cpu eating process. The cpu is nearly idle during these 50 seconds. Lightdm version : 1.24.0-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: lightdm 1.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu2 Architecture: i386 CurrentDesktop: KDE Date: Fri Oct 6 18:13:42 2017 InstallationDate: Installed on 2012-07-31 (1893 days ago) InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) SourcePackage: lightdm UpgradeStatus: Upgraded to artful on 2017-10-02 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1721821/+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 1720331] Re: Whoopsie continually relaunching
** Changed in: whoopsie (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1720331 Title: Whoopsie continually relaunching Status in gnome-control-center package in Ubuntu: Triaged Status in whoopsie package in Ubuntu: Invalid Bug description: Today for the first time, and coincidentally looking for a different setting, I went to the Settings->Privacy dialogue. I was also (coincidentally for a different reason, relating to #1720149) already tailing /var/log/syslog to a terminal. Immediately on opening that dialogue, the syslog tail flooded with whoopsie continually relaunching, causing enough work to raise the fan speeds. This is a representative section from towards the end of me letting it, before I killed the service, with some necessary viciousness. Specifically systemctl stop whoopsie (didn't stop it) systemctl disable whoopsie (didn't stop it) (find pid for whoopsie's root process and kill it) (that stopped it) Also for good measure ensured the automatic bug reporting option in the privacy settings dialog was set to manual, which I think was done anyway when I disabled whoopsie, though the dialog wasn't on top at the time for me to be sure. It had been set to automatic when I first opened the dialog. Snippet from syslog attached. It was just repeating this continually for several minutes before I stopped it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: whoopsie 0.2.58 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashReports: 664:1000:119:0:2017-09-25 18:16:58.760134901 +0100:2017-09-25 18:16:58.760134901 +0100:/var/crash/_opt_google_chrome_chrome.1000.upload 640:1000:119:102847031:2017-09-27 20:28:45.352315425 +0100:2017-09-28 09:02:32.195212507 +0100:/var/crash/_usr_bin_gnome-shell.1000.crash 640:1000:119:34020328:2017-09-25 18:16:57.656132936 +0100:2017-09-25 18:16:58.760134901 +0100:/var/crash/_opt_google_chrome_chrome.1000.crash 600:111:119:0:2017-09-25 18:16:59.348145502 +0100:2017-09-25 18:16:59.348145502 +0100:/var/crash/_opt_google_chrome_chrome.1000.uploaded CurrentDesktop: GNOME Date: Fri Sep 29 10:00:34 2017 InstallationDate: Installed on 2017-07-30 (60 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie UpgradeStatus: Upgraded to artful on 2017-08-22 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1720331/+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 1721795] Re: Move Recommends: gnome-getting-started-docs from ubuntu-docs to ubuntu-desktop
** Changed in: ubuntu-docs (Ubuntu) Status: Fix Committed => Confirmed ** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1721795 Title: Move Recommends: gnome-getting-started-docs from ubuntu-docs to ubuntu-desktop Status in ubuntu-docs package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Fix Committed Bug description: Ubuntu Budgie includes ubuntu-docs since it's generally useful and they don't have another docs system. But Ubuntu Budgie does not need gnome-getting-started-docs https://help.gnome.org/users/gnome-help/stable/getting-started.html We can fix this issue by having ubuntu-desktop recommend gnome- getting-started-docs and dropping that recommends from ubuntu-docs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1721795/+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 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore
Fwiw, my current suspicion is that adding the new IP from the dhcp as a secondary IP is buggy. Secondary IPs will get removed when the kernel removes the primary IP (see kernels __inet_del_ifa() code). -- 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/1721223 Title: Networkd fail to set ip address between leases if ip address changes on UbuntuCore Status in Snappy: New Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: New Bug description: Hi there, we found a replicable issue that involves the Ubuntu Core networking and causes complete loss of connectivity. We run a custom board with ubuntu core: the architecure is amrhf. We replicated this issue with an official Ubuntu Core image on a Raspberry Pi: other platform was been tested. It shows that it is a snap core problem which interests networkd: we use the default network stack based on networkd + netplan. Below steps to replicate the issue. 1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes). 2)Boot the board and wait for get an ip from dhcp server 3)Before the lease expires, set a reservation for a different ip address Depending on lease duration before the lease expires( for 10 minute we have 2 minutes before ), networkd configure the new address in addition to the previous one. When the lease expire both ip address ( the prevoius and the new one ) disappear from the interested network interface. Depending on lease duration before the second lease expires ( for 10 minure we have 2 minutes before ) networkd configure only the new ip address on the network interface and the ping toward an outside host work properly. During the test the dhcp server records correctly leases and their duration. We check directly from console the network interface setting with the tool ip, checking continuously the value for ip address and valid_lft fields for the interested network interface. Please note that if the ip address setting are the same between leases the problem doesn’t jump out. Please note that if the ip address setting are different between lease the problem jumps out and it is very bad: Typically the lease time on consumer router are about some day, then a board that change ip between lease loses the network connectivity for some day without a direct action. Please, after a confirmation from your side of the issue, could you fix the problem or escalate the issue at the upstream project? We are available for further testing. Below syslog annotated with ip address state: Oct 4 09:48:06 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:49:36 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:49:25 localhost systemd-timesyncd[996]: Network configuration changed, trying to establish connection. Oct 4 09:49:26 localhost systemd-timesyncd[996]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com). Oct 4 09:49:26 localhost systemd[1]: Starting Update resolvconf for networkd DNS... Oct 4 09:49:26 localhost systemd[1]: Started Update resolvconf for networkd DNS. Oct 4 09:49:37 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:51:07 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:51:09 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:52:39 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:52:40 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:54:10 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:54:11 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:55:41 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:54:23 localhost systemd-timesyncd[996]: Network configuration changed, trying to establish connection. Oct 4 09:54:23 localhost systemd[1]: Starting Update resolvconf for networkd DNS... Oct 4 09:54:23 localhost systemd-timesyncd[996]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com). Oct 4 09:54:23 localhost systemd[1]: Started Update resolvconf for networkd DNS. Oct 4 09:55:43 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:57:13 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:57:14 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:58:44 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:58:46 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 10:00:16 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 10:00:17 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 10:01:47 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 10:01:48 local
[Touch-packages] [Bug 1588998] Re: [master] package console-setup-linux 1.108ubuntu15 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in packa
>From what I can tell console-setup-linux version 1.143 is provided by the Kali Linux developers in their repository and this is not an official Ubuntu package provided by Ubuntu Developers. Subsequently, this is something you'll need to bring up with the Kali Linux developers in whatever bug tracker they use. $ rmadison console-setup-linux console-setup-linux | 1.108ubuntu5| vivid | all console-setup-linux | 1.108ubuntu15 | xenial | all console-setup-linux | 1.108ubuntu15.3 | xenial-updates | all console-setup-linux | 1.142ubuntu5| zesty | all console-setup-linux | 1.166ubuntu7| artful | all ** Changed in: console-setup (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1588998 Title: [master] package console-setup-linux 1.108ubuntu15 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console- setup.service', which is also in package keyboard-configuration 1.108ubuntu15 Status in console-setup package in Ubuntu: Won't Fix Bug description: Preparing to unpack .../console-setup-linux_1.143_all.deb ... Unpacking console-setup-linux (1.143) over (1.108ubuntu15) ... dpkg: error processing archive /var/cache/apt/archives/console-setup-linux_1.143_all.deb (--unpack): trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Preparing to unpack .../console-setup_1.143_all.deb ... Unpacking console-setup (1.143) over (1.108ubuntu15) ... Preparing to unpack .../keyboard-configuration_1.143_all.deb ... Unpacking keyboard-configuration (1.143) over (1.108ubuntu15) ... Preparing to unpack .../xkb-data_2.17-1_all.deb ... Unpacking xkb-data (2.17-1) over (2.16-1ubuntu1) ... Preparing to unpack .../gcc-6-base_6.1.1-4_amd64.deb ... Unpacking gcc-6-base:amd64 (6.1.1-4) over (6.0.1-0ubuntu1) ... Processing triggers for systemd (229-4ubuntu6) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for doc-base (0.10.7) ... Processing 1 changed doc-base file... Errors were encountered while processing: ProblemType: Package DistroRelease: Kali 2016.1 Package: console-setup-linux 1.108ubuntu15 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Jun 3 18:24:08 2016 DuplicateSignature: package:console-setup-linux:1.108ubuntu15 Unpacking console-setup-linux (1.143) over (1.108ubuntu15) ... dpkg: error processing archive /var/cache/apt/archives/console-setup-linux_1.143_all.deb (--unpack): trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15 ErrorMessage: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15 InstallationDate: Installed on 2016-06-03 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.7 apt 1.2.12~ubuntu16.04.1 SourcePackage: console-setup Title: package console-setup-linux 1.108ubuntu15 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1588998/+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 1721828] [NEW] gtk 3.22.24 breaks software-properties tests (Gdk-Message: setup.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :99.)
Public bug reported: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful/artful/amd64/s/software- properties/20171005_224025_dcec3@/log.gz I think this is real, although maybe there's a chance it's a bug in software-properties. test_add_remove_source_by_line (tests.test_dbus.TestDBus) ... Gdk- Message: setup.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :99. xauth/Xrdb output: Gdk-Message: setup.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :99. autopkgtest [22:38:16]: test run-tests: ---] autopkgtest [22:38:17]: test run-tests: - - - - - - - - - - results - - - - - - - - - - run-testsFAIL non-zero exit status 1 ** Affects: gtk Importance: Unknown Status: Unknown ** Affects: gtk+3.0 (Ubuntu) Importance: High Assignee: Iain Lane (laney) Status: Triaged ** Affects: gtk+3.0 (Ubuntu Artful) Importance: High Assignee: Iain Lane (laney) Status: Triaged ** Also affects: gtk+3.0 (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: gtk+3.0 (Ubuntu Artful) Assignee: (unassigned) => Iain Lane (laney) ** Bug watch added: GNOME Bug Tracker #788604 https://bugzilla.gnome.org/show_bug.cgi?id=788604 ** Also affects: gtk via https://bugzilla.gnome.org/show_bug.cgi?id=788604 Importance: Unknown Status: Unknown ** Changed in: gtk+3.0 (Ubuntu Artful) Status: New => Triaged ** Changed in: gtk+3.0 (Ubuntu Artful) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1721828 Title: gtk 3.22.24 breaks software-properties tests (Gdk-Message: setup.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :99.) Status in GTK+: Unknown Status in gtk+3.0 package in Ubuntu: Triaged Status in gtk+3.0 source package in Artful: Triaged Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful/artful/amd64/s/software- properties/20171005_224025_dcec3@/log.gz I think this is real, although maybe there's a chance it's a bug in software-properties. test_add_remove_source_by_line (tests.test_dbus.TestDBus) ... Gdk- Message: setup.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :99. xauth/Xrdb output: Gdk-Message: setup.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :99. autopkgtest [22:38:16]: test run-tests: ---] autopkgtest [22:38:17]: test run-tests: - - - - - - - - - - results - - - - - - - - - - run-testsFAIL non-zero exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1721828/+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 1721795] Re: Move Recommends: gnome-getting-started-docs from ubuntu-docs to ubuntu-desktop
** Branch linked: lp:ubuntu-docs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1721795 Title: Move Recommends: gnome-getting-started-docs from ubuntu-docs to ubuntu-desktop Status in ubuntu-docs package in Ubuntu: Fix Committed Status in ubuntu-meta package in Ubuntu: Fix Committed Bug description: Ubuntu Budgie includes ubuntu-docs since it's generally useful and they don't have another docs system. But Ubuntu Budgie does not need gnome-getting-started-docs https://help.gnome.org/users/gnome-help/stable/getting-started.html We can fix this issue by having ubuntu-desktop recommend gnome- getting-started-docs and dropping that recommends from ubuntu-docs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1721795/+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 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore
As a workaround for now, it looks like with: "echo 1 > /proc/sys/net/ipv4/conf/all/promote_secondaries" on the device the problem goes away. -- 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/1721223 Title: Networkd fail to set ip address between leases if ip address changes on UbuntuCore Status in Snappy: New Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: New Bug description: Hi there, we found a replicable issue that involves the Ubuntu Core networking and causes complete loss of connectivity. We run a custom board with ubuntu core: the architecure is amrhf. We replicated this issue with an official Ubuntu Core image on a Raspberry Pi: other platform was been tested. It shows that it is a snap core problem which interests networkd: we use the default network stack based on networkd + netplan. Below steps to replicate the issue. 1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes). 2)Boot the board and wait for get an ip from dhcp server 3)Before the lease expires, set a reservation for a different ip address Depending on lease duration before the lease expires( for 10 minute we have 2 minutes before ), networkd configure the new address in addition to the previous one. When the lease expire both ip address ( the prevoius and the new one ) disappear from the interested network interface. Depending on lease duration before the second lease expires ( for 10 minure we have 2 minutes before ) networkd configure only the new ip address on the network interface and the ping toward an outside host work properly. During the test the dhcp server records correctly leases and their duration. We check directly from console the network interface setting with the tool ip, checking continuously the value for ip address and valid_lft fields for the interested network interface. Please note that if the ip address setting are the same between leases the problem doesn’t jump out. Please note that if the ip address setting are different between lease the problem jumps out and it is very bad: Typically the lease time on consumer router are about some day, then a board that change ip between lease loses the network connectivity for some day without a direct action. Please, after a confirmation from your side of the issue, could you fix the problem or escalate the issue at the upstream project? We are available for further testing. Below syslog annotated with ip address state: Oct 4 09:48:06 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:49:36 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:49:25 localhost systemd-timesyncd[996]: Network configuration changed, trying to establish connection. Oct 4 09:49:26 localhost systemd-timesyncd[996]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com). Oct 4 09:49:26 localhost systemd[1]: Starting Update resolvconf for networkd DNS... Oct 4 09:49:26 localhost systemd[1]: Started Update resolvconf for networkd DNS. Oct 4 09:49:37 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:51:07 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:51:09 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:52:39 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:52:40 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:54:10 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:54:11 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:55:41 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:54:23 localhost systemd-timesyncd[996]: Network configuration changed, trying to establish connection. Oct 4 09:54:23 localhost systemd[1]: Starting Update resolvconf for networkd DNS... Oct 4 09:54:23 localhost systemd-timesyncd[996]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com). Oct 4 09:54:23 localhost systemd[1]: Started Update resolvconf for networkd DNS. Oct 4 09:55:43 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:57:13 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:57:14 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:58:44 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:58:46 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 10:00:16 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 10:00:17 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 10:01:47 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 10:01:48 localhost rsyslogd-2007: action 'action 11' suspended, next retry
[Touch-packages] [Bug 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore
Or "net.ipv4.conf.all.promote_secondaries=1" in /etc/sysctl.d/50-ipv4.conf (or similar). -- 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/1721223 Title: Networkd fail to set ip address between leases if ip address changes on UbuntuCore Status in Snappy: New Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: New Bug description: Hi there, we found a replicable issue that involves the Ubuntu Core networking and causes complete loss of connectivity. We run a custom board with ubuntu core: the architecure is amrhf. We replicated this issue with an official Ubuntu Core image on a Raspberry Pi: other platform was been tested. It shows that it is a snap core problem which interests networkd: we use the default network stack based on networkd + netplan. Below steps to replicate the issue. 1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes). 2)Boot the board and wait for get an ip from dhcp server 3)Before the lease expires, set a reservation for a different ip address Depending on lease duration before the lease expires( for 10 minute we have 2 minutes before ), networkd configure the new address in addition to the previous one. When the lease expire both ip address ( the prevoius and the new one ) disappear from the interested network interface. Depending on lease duration before the second lease expires ( for 10 minure we have 2 minutes before ) networkd configure only the new ip address on the network interface and the ping toward an outside host work properly. During the test the dhcp server records correctly leases and their duration. We check directly from console the network interface setting with the tool ip, checking continuously the value for ip address and valid_lft fields for the interested network interface. Please note that if the ip address setting are the same between leases the problem doesn’t jump out. Please note that if the ip address setting are different between lease the problem jumps out and it is very bad: Typically the lease time on consumer router are about some day, then a board that change ip between lease loses the network connectivity for some day without a direct action. Please, after a confirmation from your side of the issue, could you fix the problem or escalate the issue at the upstream project? We are available for further testing. Below syslog annotated with ip address state: Oct 4 09:48:06 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:49:36 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:49:25 localhost systemd-timesyncd[996]: Network configuration changed, trying to establish connection. Oct 4 09:49:26 localhost systemd-timesyncd[996]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com). Oct 4 09:49:26 localhost systemd[1]: Starting Update resolvconf for networkd DNS... Oct 4 09:49:26 localhost systemd[1]: Started Update resolvconf for networkd DNS. Oct 4 09:49:37 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:51:07 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:51:09 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:52:39 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:52:40 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:54:10 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:54:11 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:55:41 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:54:23 localhost systemd-timesyncd[996]: Network configuration changed, trying to establish connection. Oct 4 09:54:23 localhost systemd[1]: Starting Update resolvconf for networkd DNS... Oct 4 09:54:23 localhost systemd-timesyncd[996]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com). Oct 4 09:54:23 localhost systemd[1]: Started Update resolvconf for networkd DNS. Oct 4 09:55:43 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:57:13 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:57:14 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:58:44 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:58:46 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 10:00:16 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 10:00:17 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 10:01:47 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 10:01:48 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 10:03:18 2017 [v8.16.0 try http://ww
[Touch-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones
May I add that for me it's hwC1D0 You maybe should check what file exists in /dev/snd/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1648183 Title: Crackling and popping sound when using headphones Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Arch Linux: New Bug description: Laptop is HP Pavilion - 15-au118tx. The laptop has B and O play and the output from speakers are just fine, when using headphones there is some kind of crackling and popping sound in both ears but prominently in the left ear. The issue happens only when the sound is played, if i reduce the PCM way low using alsamixer, the effect is minimized but the volume is also reduced. Increasing the volume in the panel increases the PCM as well. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antony 1719 F pulseaudio CurrentDesktop: Unity Date: Wed Dec 7 23:30:05 2016 InstallationDate: Installed on 2016-11-20 (17 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8216 dmi.board.vendor: HP dmi.board.version: 83.13 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+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 1721795] Re: Move Recommends: gnome-getting-started-docs from ubuntu-docs to ubuntu-desktop
Change committed to the ubuntu-docs branch. Planning to upload the package on October 11 when the translators are done. ** Changed in: ubuntu-docs (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: ubuntu-docs (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1721795 Title: Move Recommends: gnome-getting-started-docs from ubuntu-docs to ubuntu-desktop Status in ubuntu-docs package in Ubuntu: Fix Committed Status in ubuntu-meta package in Ubuntu: Fix Committed Bug description: Ubuntu Budgie includes ubuntu-docs since it's generally useful and they don't have another docs system. But Ubuntu Budgie does not need gnome-getting-started-docs https://help.gnome.org/users/gnome-help/stable/getting-started.html We can fix this issue by having ubuntu-desktop recommend gnome- getting-started-docs and dropping that recommends from ubuntu-docs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1721795/+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 1721840] [NEW] dl module is missing?
Public bug reported: The Python 2.7 documentation documents the "dl" module (I know it's deprecated and has been removed in Python 3), but it doesn't actually exist: >>> import dl Traceback (most recent call last): File "", line 1, in ImportError: No module named dl Seen with both 2.7.12-1ubuntu0~16.04.1 (xenial amd64) and 2.7.14-2ubuntu2 (artful amd64). ** Affects: python2.7 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1721840 Title: dl module is missing? Status in python2.7 package in Ubuntu: New Bug description: The Python 2.7 documentation documents the "dl" module (I know it's deprecated and has been removed in Python 3), but it doesn't actually exist: >>> import dl Traceback (most recent call last): File "", line 1, in ImportError: No module named dl Seen with both 2.7.12-1ubuntu0~16.04.1 (xenial amd64) and 2.7.14-2ubuntu2 (artful amd64). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1721840/+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 1721839] [NEW] Services asked for by UDEV do not get triggered
Public bug reported:
The packages system-config-printer-udev and ippusbxd are installed,
having the following UDEV rule files:
/lib/udev/rules.d/70-printers.rules
--
# Low-level USB device add trigger
ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{ID_USB_INTERFACES}=="*:0701??:*", TAG+="udev-configure-printer",
TAG+="systemd", PROGRAM="/bin/systemd-escape
--template=udev-configure-printer@.service %p", ENV{SYSTEMD_WANTS}+="%c"
# Low-level USB device remove trigger
ACTION=="remove", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{ID_USB_INTERFACES}=="*:0701*:*", RUN+="udev-configure-printer remove %p"
--
/lib/udev/rules.d/55-ippusbxd.rules
--
# ippusbxd udev rules file
ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device"
ENV{ID_USB_INTERFACES}=="*:070104:*", OWNER="root", GROUP="lp", MODE="0664",
PROGRAM="/bin/systemd-escape --template=ippusbxd@.service
$env{BUSNUM}:$env{DEVNUM}", ENV{SYSTEMD_WANTS}+="%c"
--
If I turn on an appropriate printer (USB, supporting IPP-over-USB, here
the HP DeskJet 2540) I get in the output of "udevadm monitor
--environment"
--
UDEV [17527.514150] add /devices/pci:00/:00:14.0/usb2/2-2 (usb)
ACTION=add
BUSNUM=002
DEVNAME=/dev/bus/usb/002/033
DEVNUM=033
DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2
DEVTYPE=usb_device
DRIVER=usb
ID_BUS=usb
ID_MODEL=Deskjet_2540_series
ID_MODEL_ENC=Deskjet\x202540\x20series
ID_MODEL_ID=c211
ID_REVISION=0100
ID_SERIAL=HP_Deskjet_2540_series_BR54BFB02C05XK
ID_SERIAL_SHORT=BR54BFB02C05XK
ID_USB_INTERFACES=:ffcc00:070104:070102:ff0401:
ID_VENDOR=HP
ID_VENDOR_ENC=HP
ID_VENDOR_FROM_DATABASE=Hewlett-Packard
ID_VENDOR_ID=03f0
MAJOR=189
MINOR=160
PRODUCT=3f0/c211/100
SEQNUM=9891
SUBSYSTEM=usb
SYSTEMD_WANTS=ippusbxd@002:033.service
udev-configure-printer@-devices-pci:00-:00:14.0-usb2-2\x2d2.service
printer.target
TAGS=:udev-configure-printer:systemd:
TYPE=0/0/0
USEC_INITIALIZED=17527513940
UDEV [17527.517724] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0
(usb)
.MM_USBIFNUM=00
ACTION=add
DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0
DEVTYPE=usb_interface
ID_VENDOR_FROM_DATABASE=Hewlett-Packard
INTERFACE=255/204/0
MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00icFFiscCCip00in00
PRODUCT=3f0/c211/100
SEQNUM=9892
SUBSYSTEM=usb
TYPE=0/0/0
USEC_INITIALIZED=17527517478
UDEV [17527.522565] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.2
(usb)
.MM_USBIFNUM=02
ACTION=add
DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.2
DEVTYPE=usb_interface
ID_VENDOR_FROM_DATABASE=Hewlett-Packard
INTERFACE=255/4/1
MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00icFFisc04ip01in02
PRODUCT=3f0/c211/100
SEQNUM=9895
SUBSYSTEM=usb
TYPE=0/0/0
USEC_INITIALIZED=17527522332
UDEV [17527.523761] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1
(usb)
.MM_USBIFNUM=01
ACTION=add
DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1
DEVTYPE=usb_interface
DRIVER=usblp
ID_VENDOR_FROM_DATABASE=Hewlett-Packard
INTERFACE=7/1/2
MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00ic07isc01ip02in01
PRODUCT=3f0/c211/100
SEQNUM=9893
SUBSYSTEM=usb
TYPE=0/0/0
USEC_INITIALIZED=17527523500
UDEV [17527.527275] add
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1/usbmisc/lp1 (usbmisc)
.MM_USBIFNUM=01
ACTION=add
DEVNAME=/dev/usb/lp1
DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1/usbmisc/lp1
MAJOR=180
MINOR=1
SEQNUM=9894
SUBSYSTEM=usbmisc
USEC_INITIALIZED=17527527175
--
Here one can see that the UDEV rules files are correct, leading to the
correct systemd services being requested
SYSTEMD_WANTS=ippusbxd@002:033.service udev-configure-printer@-devices-
pci:00-:00:14.0-usb2-2\x2d2.service printer.target
but neither the service ippusbxd@002:033.service nor the service udev-
configure-printer@-devices-pci:00-:00:14.0-usb2-2\x2d2.service
get started (note that I have put the .service file for ippusbxd in
place by "sudo cp /usr/share/doc/ippusbxd/examples/ippusbxd@.service
/lib/systemd/system/").
I can start each of these services manually though:
sudo systemctl start 'udev-configure-printer@-devices-
pci:00-:00:14.0-usb2-2\x2d2.service'
sudo systemctl start ippusbxd@002:033.service
In each case ippusbxd gets started for this printer and a print queue
auto-created.
What I expect is that the services get automatically started (and that
worked in 17.04) so that after plugging in an USB printer I can
immediately print as the print queue gets created automatically.
The "udev-configure-printer..." service works for all USB printers, not
only IPP-over-USB (it automatically recognizes the printer typ and does
an appropriate setup).
This is a regression as we had always automatic setup of USB printers.
** Affects: systemd (Ubuntu)
Importance: Critical
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https:/
[Touch-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1567597 Title: implement 'complain mode' in seccomp for developer mode with snaps Status in Snappy: In Progress Status in libseccomp package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in libseccomp source package in Xenial: In Progress Status in linux source package in Xenial: Fix Committed Status in libseccomp source package in Zesty: In Progress Status in linux source package in Zesty: Fix Committed Bug description: A requirement for snappy is that a snap may be placed in developer mode which will put the security sandbox in complain mode such that violations against policy are logged, but permitted. In this manner learning tools can be written to parse the logs, etc and make developing on snappy easier. Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while we can set complain mode to permit all calls, they are not logged at this time. I've discussed this with upstream and we are working together on the approach. This may require a kernel patch and an update to libseccomp, to filing this bug for now as a placeholder and we'll add other tasks as necessary. UPDATE: ubuntu-core-launcher now supports the '@complain' directive that is a synonym for '@unrestricted' so people can at least turn on developer mode and not be blocked by seccomp. Proper complain mode for seccomp needs to still be implemented (this bug). [Impact] Snapd needs a way to log seccomp actions without blocking any syscalls in order to have a more useful complain mode. Such functionality has been acked upstream and patches are on their way into the Linux 4.14 kernel (backported to 4.12.0-13.14 in artful). The corresponding libseccomp changes are still undergoing review (https://github.com/seccomp/libseccomp/pull/92). The pull request adds a number of new symbols and probably isn't appropriate to backport until upstream has acked the pull request. However, only a small part of that larger pull request is needed by snapd and that change can be safely backported since the only added symbol, the SCMP_ACT_LOG macro, must match the SECCOMP_RET_LOG macro that has already been approved and merged in the upstream Linux kernel. [libseccomp Test Case] A large number of tests are ran as part of the libseccomp build. However, the "live" tests which test libseccomp with actual kernel enforcement are not ran at that time. They can be manually exercised to help catch any regressions. Note that on Artful, there's an existing test failure (20-live-basic_die%%002-1): $ sudo apt build-dep -y libseccomp $ sudo apt install -y cython $ apt source libseccomp $ cd libseccomp-* $ autoreconf -ivf && ./configure --enable-python && make check-build $ (cd tests && ./regression -T live) All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, you'll see one pre-existing failure: ... Test 20-live-basic_die%%002-1 result: FAILURE 20-live-basic_die TRAP rc=159 ... Regression Test Summary tests run: 12 tests skipped: 0 tests passed: 11 tests failed: 1 tests errored: 0 Now we can build and run a small test program to test the SCMP_ACT_LOG action in the way that snapd wants to use it for developer mode: $ sudo apt install -y libseccomp-dev $ gcc -o lp1567597-test lp1567597-test.c -lseccomp $ ./lp1567597-test With a kernel that contains the logging patches and an updated libseccomp, the exit code should be 0 and you should have an entry in the system log that looks like this: audit: type=1326 audit(1505859630.994:69): auid=1000 uid=1000 gid=1000 ses=2 pid=18451 comm="lp1567597-test" exe="/home/tyhicks/lp1567597-test" sig=0 arch=c03e syscall=2 compat=0 ip=0x7f547352c5c0 code=0x7ffc If you have an updated libseccomp with an old kernel, you'll see that seccomp_init() fails due to the added compatibility check inside of libseccomp determines that the kernel doesn't have proper support for the new log action: $ ./lp1567597-test ERROR: seccomp_init: Invalid argument [Linux Kernel Test Case] All of the libseccomp test cases apply here. Running the seccomp kernel selftests is also a great to exercise seccomp and the kernel patch set proposed for the SRU includes additional seccomp selftests. To build, enter into the root of the kernel source tree and build the seccomp test binary: $ make -C tools/testing/selftests TARGETS=seccomp Now you can execute tools/testing/selftests/seccomp/seccomp_bpf or even copy it to a test machine a
[Touch-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps
** Changed in: linux (Ubuntu Zesty) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1567597 Title: implement 'complain mode' in seccomp for developer mode with snaps Status in Snappy: In Progress Status in libseccomp package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in libseccomp source package in Xenial: In Progress Status in linux source package in Xenial: Fix Committed Status in libseccomp source package in Zesty: In Progress Status in linux source package in Zesty: Fix Committed Bug description: A requirement for snappy is that a snap may be placed in developer mode which will put the security sandbox in complain mode such that violations against policy are logged, but permitted. In this manner learning tools can be written to parse the logs, etc and make developing on snappy easier. Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while we can set complain mode to permit all calls, they are not logged at this time. I've discussed this with upstream and we are working together on the approach. This may require a kernel patch and an update to libseccomp, to filing this bug for now as a placeholder and we'll add other tasks as necessary. UPDATE: ubuntu-core-launcher now supports the '@complain' directive that is a synonym for '@unrestricted' so people can at least turn on developer mode and not be blocked by seccomp. Proper complain mode for seccomp needs to still be implemented (this bug). [Impact] Snapd needs a way to log seccomp actions without blocking any syscalls in order to have a more useful complain mode. Such functionality has been acked upstream and patches are on their way into the Linux 4.14 kernel (backported to 4.12.0-13.14 in artful). The corresponding libseccomp changes are still undergoing review (https://github.com/seccomp/libseccomp/pull/92). The pull request adds a number of new symbols and probably isn't appropriate to backport until upstream has acked the pull request. However, only a small part of that larger pull request is needed by snapd and that change can be safely backported since the only added symbol, the SCMP_ACT_LOG macro, must match the SECCOMP_RET_LOG macro that has already been approved and merged in the upstream Linux kernel. [libseccomp Test Case] A large number of tests are ran as part of the libseccomp build. However, the "live" tests which test libseccomp with actual kernel enforcement are not ran at that time. They can be manually exercised to help catch any regressions. Note that on Artful, there's an existing test failure (20-live-basic_die%%002-1): $ sudo apt build-dep -y libseccomp $ sudo apt install -y cython $ apt source libseccomp $ cd libseccomp-* $ autoreconf -ivf && ./configure --enable-python && make check-build $ (cd tests && ./regression -T live) All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, you'll see one pre-existing failure: ... Test 20-live-basic_die%%002-1 result: FAILURE 20-live-basic_die TRAP rc=159 ... Regression Test Summary tests run: 12 tests skipped: 0 tests passed: 11 tests failed: 1 tests errored: 0 Now we can build and run a small test program to test the SCMP_ACT_LOG action in the way that snapd wants to use it for developer mode: $ sudo apt install -y libseccomp-dev $ gcc -o lp1567597-test lp1567597-test.c -lseccomp $ ./lp1567597-test With a kernel that contains the logging patches and an updated libseccomp, the exit code should be 0 and you should have an entry in the system log that looks like this: audit: type=1326 audit(1505859630.994:69): auid=1000 uid=1000 gid=1000 ses=2 pid=18451 comm="lp1567597-test" exe="/home/tyhicks/lp1567597-test" sig=0 arch=c03e syscall=2 compat=0 ip=0x7f547352c5c0 code=0x7ffc If you have an updated libseccomp with an old kernel, you'll see that seccomp_init() fails due to the added compatibility check inside of libseccomp determines that the kernel doesn't have proper support for the new log action: $ ./lp1567597-test ERROR: seccomp_init: Invalid argument [Linux Kernel Test Case] All of the libseccomp test cases apply here. Running the seccomp kernel selftests is also a great to exercise seccomp and the kernel patch set proposed for the SRU includes additional seccomp selftests. To build, enter into the root of the kernel source tree and build the seccomp test binary: $ make -C tools/testing/selftests TARGETS=seccomp Now you can execute tools/testing/selftests/seccomp/seccomp_bpf or even copy it to a test machine an
[Touch-packages] [Bug 1662031] Re: Switching language and format broken
Wonder if there is a problem with this code: https://git.gnome.org/browse/gdm/tree/daemon/gdm-session-worker.c#n993 @Steve: gdm3 seems to not read ~/.pam_environment. Do you possibly have an idea off the top of your head? -- 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/1662031 Title: Switching language and format broken Status in Ubuntu GNOME: New Status in accountsservice package in Ubuntu: New Status in gdm3 package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: New Status in accountsservice source package in Artful: New Status in gdm3 source package in Artful: Confirmed Status in gnome-control-center source package in Artful: New Bug description: In Ubuntu GNOME 16.10 it doesn't matter what display language I select - the effective language is still the one stated in /etc/default/locale. ~/.pam_environment is changed as expected, but the variables set in /etc/default/locale override ~/.pam_environment. In Ubuntu GNOME 16.04 language switching takes effect, but the reason for that seems to be that /etc/default/locale is changed as well, so when a user changes the display language (or format), it changes it for all users on the system. The overriding by /etc/default/locale is probably caused by some other package(s) but g-c-c. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1662031/+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 1721763] Re: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart
" Most of the time, such problem means a non responding task still running in the background. So be sure your system is cleaned (use gtkorphan & bleachbit to clean it). " Well I have a fresh instalation done when Beta2 was released (about 8 days ago). Anyway I installed gtkorphan and bleachbit, runned and there was some trash to clean... what I did it... rebooted sometimes but the issue continues. I will try this "hitting 'Esc'" tecnic and make the journald permanent. See! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1721763 Title: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: I really do not know which package to assign this incident, please excuse me. Any way, the release candidates is near, and this problem continues to occur since linux kernel was updated from 4.11 to 4.12 ... and now with version 4.13 the problem continues. I noticed that this problem does not occur with my other two older notebooks (one Sony Vaio and the other a generic one integrated by me) both old notes use NVIDIA video card in versions of more than 5 years ago. My new Dell notebook has a GTX 1050 video card ... but I also do not know if the cause of this problem may be linked to the video card and the fact that Nouveau driver and linux Kernel have received recent implementations for compatibilities with this new NVIDIA technology. The fact is that Ubuntu 17.10 has potential to be distributed with this problem and I think this may not be interesting, so I am reporting this case. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.402 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 08:25:20 2017 InstallationDate: Installed on 2017-09-29 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1721763/+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 1712858] Re: system freezes occasionally for several minutes
> the problem might not be audio-related at all. It might be some other part of > your kernel that's hanging This is quite possible indeed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1712858 Title: system freezes occasionally for several minutes Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Occasionally, the system freezes: display does not show mouse move, clock display does not update itself, ssh impossible. But the machine remains pingable. This lasts for 2 to 20 minutes. This is with Ubuntu 16.04.2, now upgraded to kernel version 4.8.0-46-generic. At the end of the freeze, a bunch of messages get written to /var/log/syslog. Examples: Aug 19 00:03:48 quimper rtkit-daemon[2276]: The canary thread is apparently starving. Taking action. Aug 19 00:03:48 quimper rtkit-daemon[2276]: Demoting known real-time threads. Aug 19 00:03:48 quimper rtkit-daemon[2276]: Successfully demoted thread 2607 of process 2275 (n/a). Aug 19 00:03:48 quimper rtkit-daemon[2276]: Successfully demoted thread 2606 of process 2275 (n/a). Aug 19 00:03:48 quimper rtkit-daemon[2276]: Successfully demoted thread 2604 of process 2275 (n/a). Aug 19 00:03:48 quimper rtkit-daemon[2276]: Successfully demoted thread 2275 of process 2275 (n/a). Aug 19 00:03:48 quimper rtkit-daemon[2276]: Demoted 4 threads. Aug 19 08:06:19 quimper rtkit-daemon[2276]: The canary thread is apparently starving. Taking action. Aug 19 08:06:19 quimper rtkit-daemon[2276]: Demoting known real-time threads. Aug 19 08:06:19 quimper rtkit-daemon[2276]: Successfully demoted thread 2607 of process 2275 (n/a). Aug 19 08:06:19 quimper rtkit-daemon[2276]: Successfully demoted thread 2606 of process 2275 (n/a). Aug 19 08:06:19 quimper rtkit-daemon[2276]: Successfully demoted thread 2604 of process 2275 (n/a). Aug 19 08:06:19 quimper rtkit-daemon[2276]: Successfully demoted thread 2275 of process 2275 (n/a). Aug 19 08:06:19 quimper rtkit-daemon[2276]: Demoted 4 threads. Aug 19 08:06:20 quimper systemd[1]: systemd-udevd.service: Watchdog timeout (limit 3min)! Aug 19 08:06:20 quimper systemd[1]: systemd-udevd.service: Main process exited, code=killed, status=6/ABRT Aug 19 08:06:20 quimper systemd[1]: systemd-udevd.service: Unit entered failed state. Aug 19 08:06:20 quimper systemd[1]: systemd-udevd.service: Failed with result 'signal'. Aug 19 08:06:20 quimper systemd[1]: systemd-udevd.service: Service has no hold-off time, scheduling restart. Aug 19 08:06:20 quimper systemd[1]: Stopped udev Kernel Device Manager. Aug 19 08:06:20 quimper systemd[1]: Starting udev Kernel Device Manager... Aug 19 08:06:24 quimper systemd[1]: Started udev Kernel Device Manager. Aug 19 15:04:55 quimper rtkit-daemon[2276]: The canary thread is apparently starving. Taking action. Aug 19 15:04:55 quimper rtkit-daemon[2276]: Demoting known real-time threads. Aug 19 15:04:55 quimper rtkit-daemon[2276]: Successfully demoted thread 2607 of process 2275 (n/a). Aug 19 15:04:55 quimper rtkit-daemon[2276]: Successfully demoted thread 2606 of process 2275 (n/a). Aug 19 15:04:55 quimper rtkit-daemon[2276]: Successfully demoted thread 2604 of process 2275 (n/a). Aug 19 15:04:55 quimper rtkit-daemon[2276]: Successfully demoted thread 2275 of process 2275 (n/a). Aug 19 15:04:55 quimper rtkit-daemon[2276]: Demoted 4 threads. Aug 19 15:04:55 quimper systemd[1]: systemd-timesyncd.service: Watchdog timeout (limit 3min)! Aug 19 15:04:59 quimper systemd[1]: systemd-timesyncd.service: Main process exited, code=killed, status=6/ABRT Aug 19 15:04:59 quimper systemd[1]: systemd-timesyncd.service: Unit entered failed state. Aug 19 15:04:59 quimper systemd[1]: systemd-timesyncd.service: Failed with result 'signal'. Aug 19 15:05:00 quimper systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart. Aug 19 15:05:00 quimper systemd[1]: Stopped Network Time Synchronization. Aug 19 15:05:00 quimper systemd[1]: Starting Network Time Synchronization... Aug 19 15:05:00 quimper systemd[1]: Started Network Time Synchronization. Aug 19 15:05:00 quimper systemd-timesyncd[26894]: Synchronized to time server 91.189.89.198:123 (ntp.ubuntu.com). Aug 20 06:03:28 quimper rtkit-daemon[2276]: The canary thread is apparently starving. Taking action. Aug 20 06:03:28 quimper rtkit-daemon[2276]: Demoting known real-time threads. Aug 20 06:03:28 quimper rtkit-daemon[2276]: Successfully demoted thread 2607 of process 2275 (n/a). Aug 20 06:03:28 quimper rtkit-daemon[2276]: Successfully demoted thread 2606 of process 2275 (n/a). Aug 20 06:03:28 quimper rtkit-daemon[2276]: Successfully demoted thread 2604 of process 2275 (n/a). Aug 20 06:03:28 quimper rtkit-daemon[2276]: Successfully demot
[Touch-packages] [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)
** Changed in: maas
Milestone: 2.3.0 => 2.3.0beta2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
[2.3] resolv.conf is not set (during commissioning or testing)
Status in MAAS:
Confirmed
Status in cloud-init package in Ubuntu:
Confirmed
Status in resolvconf package in Ubuntu:
In Progress
Bug description:
Using MAAS 2.3, during commissioning (and likely in the rest of the
ephemeral environment) we have noticed that resolv.conf is not set
with the DNS server.
That said, during the commissioning process, MAAS does not send any
metadata to cloud-init to configure the network, rather, we expect the
image to boot from the network via DHCP. So, cloud-init writes:
ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
auto lo
iface lo inet loopback
# control-manual ens3
iface ens3 inet dhcp
broadcast 192.168.122.255
dns-nameservers 192.168.122.2
gateway 192.168.122.1
netmask 255.255.255.0
Which correctly includes the DNS server. However:
ubuntu@manual:~$ ping google.com
ping: unknown host google.com
If restart the interfacE:
ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
ifdown: interface ens3 not configured
Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/ens3/52:54:00:ea:57:31
Sending on LPF/ens3/52:54:00:ea:57:31
Sending on Socket/fallback
DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67
(xid=0x5403eb14)
DHCPOFFER of 192.168.122.195 from 192.168.122.2
DHCPACK of 192.168.122.195 from 192.168.122.2
Restarting ntp (via systemctl): ntp.service.
bound to 192.168.122.195 -- renewal in 290 seconds.
ubuntu@manual:~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.122.2
search maas
ubuntu@manual:~$ ping google.com
PING google.com (216.58.192.46) 56(84) bytes of data.
64 bytes from mia07s46-in-f14.1e100.net (216.58.192.46): icmp_seq=1 ttl=52
time=7.47 ms
^C
--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 7.472/7.472/7.472/0.000 ms
As such, this either seems like a bug in Ubuntu, or caused by cloud-
init when writing e/n/i.d/50-cloud-init.cfg
ubuntu@manual:~$ dpkg -l | grep cloud-init
ii cloud-init 0.7.9-153-g16a7302f-0ubuntu1~16.04.2
all Init scripts for cloud instances
ii cloud-initramfs-copymods 0.27ubuntu1.4
all copy initramfs modules into root filesystem for later use
ii cloud-initramfs-dyn-netconf 0.27ubuntu1.4
all write a network interface file in /run for BOOTIF
ubuntu@manual:~$ uname -a
Linux manual 4.4.0-92-generic #115-Ubuntu SMP Thu Aug 10 09:04:33 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@manual:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename: xenial
ubuntu@manual:~$ pastebinit /var/log/cloud-init.log
http://paste.ubuntu.com/25342738/
ubuntu@manual:~$ pastebinit /var/log/cloud-init-output.log
http://paste.ubuntu.com/25342740/
Related bugs:
* bug 1714308: dns does not work in initramfs after configure_networking
* bug 1713803: replacement of resolvconf with systemd needs integration
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1711760/+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 1712858] Re: system freezes occasionally for several minutes
A measure to reduce the frequency of the hangs is to use little swap space. Here's an extract of my system log: syslog.7.gz:Sep 28 19:20:00 quimper rtkit-daemon[2231]: The canary thread is apparently starving. Taking action. syslog.7.gz:Sep 28 22:19:03 quimper rtkit-daemon[2231]: The canary thread is apparently starving. Taking action. syslog.7.gz:Sep 29 04:47:32 quimper rtkit-daemon[2231]: The canary thread is apparently starving. Taking action. syslog.7.gz:Sep 29 07:16:44 quimper rtkit-daemon[2231]: The canary thread is apparently starving. Taking action. syslog.6.gz:Sep 29 13:35:04 quimper rtkit-daemon[2231]: The canary thread is apparently starving. Taking action. syslog.6.gz:Sep 29 13:35:04 quimper rtkit-daemon[2231]: The canary thread is apparently starving. Taking action. syslog.6.gz:Sep 29 17:27:41 quimper rtkit-daemon[2231]: The canary thread is apparently starving. Taking action. syslog.6.gz:Sep 29 21:43:55 quimper rtkit-daemon[2231]: The canary thread is apparently starving. Taking action. syslog.6.gz:Sep 29 21:43:55 quimper rtkit-daemon[2231]: The canary thread is apparently starving. Taking action. syslog.6.gz:Sep 30 03:30:53 quimper rtkit-daemon[2231]: The canary thread is apparently starving. Taking action. syslog.6.gz:Sep 30 07:50:10 quimper rtkit-daemon[2231]: The canary thread is apparently starving. Taking action. syslog.5.gz:Sep 30 12:48:52 quimper rtkit-daemon[2231]: The canary thread is apparently starving. Taking action. syslog.5.gz:Sep 30 12:48:55 quimper rtkit-daemon[2231]: The canary thread is apparently starving. Taking action. syslog.5.gz:Sep 30 22:07:09 quimper rtkit-daemon[2231]: The canary thread is apparently starving. Taking action. syslog.5.gz:Oct 1 04:49:01 quimper rtkit-daemon[2231]: The canary thread is apparently starving. Taking action. syslog.4.gz:Oct 1 11:07:24 quimper rtkit-daemon[2231]: The canary thread is apparently starving. Taking action. syslog.4.gz:Oct 1 13:33:58 quimper rtkit-daemon[2231]: The canary thread is apparently starving. Taking action. syslog.3.gz:Oct 2 10:59:56 quimper rtkit-daemon[2231]: The canary thread is apparently starving. Taking action. syslog.3.gz:Oct 2 13:52:15 quimper rtkit-daemon[2231]: The canary thread is apparently starving. Taking action. syslog.3.gz:Oct 2 13:52:16 quimper rtkit-daemon[2231]: The canary thread is apparently starving. Taking action. syslog.3.gz:Oct 2 21:44:36 quimper rtkit-daemon[2231]: The canary thread is apparently starving. Taking action. syslog.3.gz:Oct 3 01:08:25 quimper rtkit-daemon[2231]: The canary thread is apparently starving. Taking action. syslog.3.gz:Oct 3 09:26:54 quimper rtkit-daemon[2231]: The canary thread is apparently starving. Taking action. syslog.3.gz:Oct 3 13:30:52 quimper rtkit-daemon[2231]: The canary thread is apparently starving. Taking action. syslog.3.gz:Oct 3 17:25:08 quimper rtkit-daemon[2231]: The canary thread is apparently starving. Taking action. syslog.3.gz:Oct 3 21:44:55 quimper rtkit-daemon[2231]: The canary thread is apparently starving. Taking action. Up until Oct 3, I got 2 to 6 hangs per day (each lasting minutes or hours). In these times I was using between 6 and 10 GB of swap space (in addition to the 16 GB of RAM my machine has). In the evening of Oct 3, I killed and restarted a process which was eating several GB of virtual memory (plasmashell - a well-known memory hog). Now, the last 3 days, I'm using less than 1 GB of swap space - and zero hangs happened. So this leaves two hypotheses: a) The hangs occur when a lot of swap space is in use. b) plasmashell not only leaks memory but also some other kind of resources. When these resources get scarce, the hangs occur. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1712858 Title: system freezes occasionally for several minutes Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Occasionally, the system freezes: display does not show mouse move, clock display does not update itself, ssh impossible. But the machine remains pingable. This lasts for 2 to 20 minutes. This is with Ubuntu 16.04.2, now upgraded to kernel version 4.8.0-46-generic. At the end of the freeze, a bunch of messages get written to /var/log/syslog. Examples: Aug 19 00:03:48 quimper rtkit-daemon[2276]: The canary thread is apparently starving. Taking action. Aug 19 00:03:48 quimper rtkit-daemon[2276]: Demoting known real-time threads. Aug 19 00:03:48 quimper rtkit-daemon[2276]: Successfully demoted thread 2607 of process 2275 (n/a). Aug 19 00:03:48 quimper rtkit-daemon[2276]: Successfully demoted thread 2606 of process 2275 (n/a). Aug 19 00:03:48 quimper rtkit-daemon[2276]: Successfully demoted thread 2604 of process 2275 (n/a). Aug 19 00:03:48 quimper rtkit-daemon[2276]: Successfully de
[Touch-packages] [Bug 1628866] Re: After upgrading to 16.10, Chrome has become unusable because of extremely slow update
** Changed in: xorg-server Status: Unknown => Confirmed ** Changed in: xorg-server Importance: Unknown => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1628866 Title: After upgrading to 16.10, Chrome has become unusable because of extremely slow update Status in X.Org X server: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Both Chrome and Firefox actually were extremely slow regarding visual update (1 second after clicking a tab, lagging when entering text). Examining this old report: https://bugs.launchpad.net/ubuntu- gnome/+bug/1386721, I tried disbling bootloader graphics and VESA framebuffer, which suddenly made firefox behave as it used to, but chrome shows no improvement. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7 Date: Thu Sep 29 12:19:56 2016 DistUpgraded: 2016-09-28 22:48:16,082 DEBUG icon theme changed, re-reading DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2227] InstallationDate: Installed on 2016-04-28 (153 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20BTS26N00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic root=UUID=96f314f8-7e1b-4d70-b372-84febb180710 ro vesafb.invalid=1 quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-09-28 (0 days ago) dmi.bios.date: 03/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET28W (1.06 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BTS26N00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET28W(1.06):bd03/12/2015:svnLENOVO:pn20BTS26N00:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS26N00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BTS26N00 dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Thu Sep 29 12:15:18 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1628866/+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 1721828] Re: gtk 3.22.24 breaks software-properties tests (Gdk-Message: setup.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :99.)
** Changed in: gtk Status: Unknown => Confirmed ** Changed in: gtk Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1721828 Title: gtk 3.22.24 breaks software-properties tests (Gdk-Message: setup.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :99.) Status in GTK+: Confirmed Status in gtk+3.0 package in Ubuntu: Triaged Status in gtk+3.0 source package in Artful: Triaged Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful/artful/amd64/s/software- properties/20171005_224025_dcec3@/log.gz I think this is real, although maybe there's a chance it's a bug in software-properties. test_add_remove_source_by_line (tests.test_dbus.TestDBus) ... Gdk- Message: setup.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :99. xauth/Xrdb output: Gdk-Message: setup.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :99. autopkgtest [22:38:16]: test run-tests: ---] autopkgtest [22:38:17]: test run-tests: - - - - - - - - - - results - - - - - - - - - - run-testsFAIL non-zero exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1721828/+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 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)
** Merge proposal linked:
https://code.launchpad.net/~andreserl/maas/+git/maas/+merge/331968
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
[2.3] resolv.conf is not set (during commissioning or testing)
Status in MAAS:
Confirmed
Status in cloud-init package in Ubuntu:
Confirmed
Status in resolvconf package in Ubuntu:
In Progress
Bug description:
Using MAAS 2.3, during commissioning (and likely in the rest of the
ephemeral environment) we have noticed that resolv.conf is not set
with the DNS server.
That said, during the commissioning process, MAAS does not send any
metadata to cloud-init to configure the network, rather, we expect the
image to boot from the network via DHCP. So, cloud-init writes:
ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
auto lo
iface lo inet loopback
# control-manual ens3
iface ens3 inet dhcp
broadcast 192.168.122.255
dns-nameservers 192.168.122.2
gateway 192.168.122.1
netmask 255.255.255.0
Which correctly includes the DNS server. However:
ubuntu@manual:~$ ping google.com
ping: unknown host google.com
If restart the interfacE:
ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
ifdown: interface ens3 not configured
Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/ens3/52:54:00:ea:57:31
Sending on LPF/ens3/52:54:00:ea:57:31
Sending on Socket/fallback
DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67
(xid=0x5403eb14)
DHCPOFFER of 192.168.122.195 from 192.168.122.2
DHCPACK of 192.168.122.195 from 192.168.122.2
Restarting ntp (via systemctl): ntp.service.
bound to 192.168.122.195 -- renewal in 290 seconds.
ubuntu@manual:~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.122.2
search maas
ubuntu@manual:~$ ping google.com
PING google.com (216.58.192.46) 56(84) bytes of data.
64 bytes from mia07s46-in-f14.1e100.net (216.58.192.46): icmp_seq=1 ttl=52
time=7.47 ms
^C
--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 7.472/7.472/7.472/0.000 ms
As such, this either seems like a bug in Ubuntu, or caused by cloud-
init when writing e/n/i.d/50-cloud-init.cfg
ubuntu@manual:~$ dpkg -l | grep cloud-init
ii cloud-init 0.7.9-153-g16a7302f-0ubuntu1~16.04.2
all Init scripts for cloud instances
ii cloud-initramfs-copymods 0.27ubuntu1.4
all copy initramfs modules into root filesystem for later use
ii cloud-initramfs-dyn-netconf 0.27ubuntu1.4
all write a network interface file in /run for BOOTIF
ubuntu@manual:~$ uname -a
Linux manual 4.4.0-92-generic #115-Ubuntu SMP Thu Aug 10 09:04:33 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@manual:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename: xenial
ubuntu@manual:~$ pastebinit /var/log/cloud-init.log
http://paste.ubuntu.com/25342738/
ubuntu@manual:~$ pastebinit /var/log/cloud-init-output.log
http://paste.ubuntu.com/25342740/
Related bugs:
* bug 1714308: dns does not work in initramfs after configure_networking
* bug 1713803: replacement of resolvconf with systemd needs integration
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1711760/+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 1720519] Re: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
This would seem to happen because start-pulseaudio-x11 tries to load module-device-manager that unfortunately conflicts with module-switch- on-connect. https://bugs.freedesktop.org/show_bug.cgi?id=95104 ** Bug watch added: freedesktop.org Bugzilla #95104 https://bugs.freedesktop.org/show_bug.cgi?id=95104 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1720519 Title: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1720519/+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 1721278] Re: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed"
Which kernel are you using? On my development 17.10 Desktop, I get the same as you but only for mainline kernels 4.14-rc2 and 4.14-rc3. Earlier kernels, including mainline 4.14-rc1, seem to be fine with respect to this issue. -- 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/1721278 Title: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" Status in apparmor package in Ubuntu: New Bug description: With Ubuntu 16.04.3 LTS (Xenial Xerus), and apparmor 2.10.95-0ubuntu2.7, in the system log each second the error message below is printed to. ``` […] [Mi Okt 4 16:57:52 2017] audit: type=1400 audit(1507129072.882:554): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:53 2017] audit: type=1400 audit(1507129073.886:555): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:54 2017] audit: type=1400 audit(1507129074.886:556): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:55 2017] audit: type=1400 audit(1507129075.886:557): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" […] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1721278/+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 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)
** Changed in: maas
Assignee: (unassigned) => Andres Rodriguez (andreserl)
** Changed in: maas
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
[2.3] resolv.conf is not set (during commissioning or testing)
Status in MAAS:
In Progress
Status in cloud-init package in Ubuntu:
Confirmed
Status in resolvconf package in Ubuntu:
In Progress
Bug description:
Using MAAS 2.3, during commissioning (and likely in the rest of the
ephemeral environment) we have noticed that resolv.conf is not set
with the DNS server.
That said, during the commissioning process, MAAS does not send any
metadata to cloud-init to configure the network, rather, we expect the
image to boot from the network via DHCP. So, cloud-init writes:
ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
auto lo
iface lo inet loopback
# control-manual ens3
iface ens3 inet dhcp
broadcast 192.168.122.255
dns-nameservers 192.168.122.2
gateway 192.168.122.1
netmask 255.255.255.0
Which correctly includes the DNS server. However:
ubuntu@manual:~$ ping google.com
ping: unknown host google.com
If restart the interfacE:
ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
ifdown: interface ens3 not configured
Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/ens3/52:54:00:ea:57:31
Sending on LPF/ens3/52:54:00:ea:57:31
Sending on Socket/fallback
DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67
(xid=0x5403eb14)
DHCPOFFER of 192.168.122.195 from 192.168.122.2
DHCPACK of 192.168.122.195 from 192.168.122.2
Restarting ntp (via systemctl): ntp.service.
bound to 192.168.122.195 -- renewal in 290 seconds.
ubuntu@manual:~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.122.2
search maas
ubuntu@manual:~$ ping google.com
PING google.com (216.58.192.46) 56(84) bytes of data.
64 bytes from mia07s46-in-f14.1e100.net (216.58.192.46): icmp_seq=1 ttl=52
time=7.47 ms
^C
--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 7.472/7.472/7.472/0.000 ms
As such, this either seems like a bug in Ubuntu, or caused by cloud-
init when writing e/n/i.d/50-cloud-init.cfg
ubuntu@manual:~$ dpkg -l | grep cloud-init
ii cloud-init 0.7.9-153-g16a7302f-0ubuntu1~16.04.2
all Init scripts for cloud instances
ii cloud-initramfs-copymods 0.27ubuntu1.4
all copy initramfs modules into root filesystem for later use
ii cloud-initramfs-dyn-netconf 0.27ubuntu1.4
all write a network interface file in /run for BOOTIF
ubuntu@manual:~$ uname -a
Linux manual 4.4.0-92-generic #115-Ubuntu SMP Thu Aug 10 09:04:33 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@manual:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename: xenial
ubuntu@manual:~$ pastebinit /var/log/cloud-init.log
http://paste.ubuntu.com/25342738/
ubuntu@manual:~$ pastebinit /var/log/cloud-init-output.log
http://paste.ubuntu.com/25342740/
Related bugs:
* bug 1714308: dns does not work in initramfs after configure_networking
* bug 1713803: replacement of resolvconf with systemd needs integration
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1711760/+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 1721763] Re: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart
The "hitting 'Esc'" technic gaves me no much: appears: "/dev/sda2: clean, files, blocks" Then I expected about 5 to 10 minutes and apeears: "power down" ... and the computer was off. I made the journald permanent as explained. But it gaves me a 7 thousand lines report that I can't undestand. I could see some errors in red but can't be sure about its relations with the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1721763 Title: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: I really do not know which package to assign this incident, please excuse me. Any way, the release candidates is near, and this problem continues to occur since linux kernel was updated from 4.11 to 4.12 ... and now with version 4.13 the problem continues. I noticed that this problem does not occur with my other two older notebooks (one Sony Vaio and the other a generic one integrated by me) both old notes use NVIDIA video card in versions of more than 5 years ago. My new Dell notebook has a GTX 1050 video card ... but I also do not know if the cause of this problem may be linked to the video card and the fact that Nouveau driver and linux Kernel have received recent implementations for compatibilities with this new NVIDIA technology. The fact is that Ubuntu 17.10 has potential to be distributed with this problem and I think this may not be interesting, so I am reporting this case. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.402 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 08:25:20 2017 InstallationDate: Installed on 2017-09-29 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1721763/+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 1721763] Re: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart
There go some errors: out 06 16:02:20 etm kernel: mce: [Hardware Error]: Machine check events logged out 06 16:02:20 etm kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ee200040110a out 06 16:02:20 etm kernel: mce: [Hardware Error]: TSC 0 ADDR fef1ffc0 MISC 7880010086 out 06 16:02:20 etm kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1507316536 SOCKET 0 APIC 0 microcode 5e out 06 16:02:20 etm kernel: mce: [Hardware Error]: Machine check events logged out 06 16:02:20 etm kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 7: ee200040110a out 06 16:02:20 etm kernel: mce: [Hardware Error]: TSC 0 ADDR fef1ce40 MISC 47880010086 out 06 16:02:20 etm kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1507316536 SOCKET 0 APIC 0 microcode 5e out 06 16:02:20 etm kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 8: ee200040110a out 06 16:02:20 etm kernel: mce: [Hardware Error]: TSC 0 ADDR fef1ff40 MISC 7880010086 out 06 16:02:20 etm kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1507316536 SOCKET 0 APIC 0 microcode 5e out 06 16:02:20 etm kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 9: ee200040110a out 06 16:02:20 etm kernel: mce: [Hardware Error]: TSC 0 ADDR fef1ff00 MISC 3880010086 out 06 16:02:20 etm kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1507316536 SOCKET 0 APIC 0 microcode 5e out 06 16:02:20 etm kernel: Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1721763 Title: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: I really do not know which package to assign this incident, please excuse me. Any way, the release candidates is near, and this problem continues to occur since linux kernel was updated from 4.11 to 4.12 ... and now with version 4.13 the problem continues. I noticed that this problem does not occur with my other two older notebooks (one Sony Vaio and the other a generic one integrated by me) both old notes use NVIDIA video card in versions of more than 5 years ago. My new Dell notebook has a GTX 1050 video card ... but I also do not know if the cause of this problem may be linked to the video card and the fact that Nouveau driver and linux Kernel have received recent implementations for compatibilities with this new NVIDIA technology. The fact is that Ubuntu 17.10 has potential to be distributed with this problem and I think this may not be interesting, so I am reporting this case. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.402 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 08:25:20 2017 InstallationDate: Installed on 2017-09-29 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1721763/+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 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore
Xnox pointed out that the above net.ipv4.conf.all.promote_secondaries=1 is actually a default of systemd (added in https://github.com/systemd/systemd/commit/ad8bc9ea508740074cead005aa3cfd1ba10a5dac). This looks like we will enable it for everybody via a systemd SRU. -- 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/1721223 Title: Networkd fail to set ip address between leases if ip address changes on UbuntuCore Status in Snappy: New Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: New Bug description: Hi there, we found a replicable issue that involves the Ubuntu Core networking and causes complete loss of connectivity. We run a custom board with ubuntu core: the architecure is amrhf. We replicated this issue with an official Ubuntu Core image on a Raspberry Pi: other platform was been tested. It shows that it is a snap core problem which interests networkd: we use the default network stack based on networkd + netplan. Below steps to replicate the issue. 1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes). 2)Boot the board and wait for get an ip from dhcp server 3)Before the lease expires, set a reservation for a different ip address Depending on lease duration before the lease expires( for 10 minute we have 2 minutes before ), networkd configure the new address in addition to the previous one. When the lease expire both ip address ( the prevoius and the new one ) disappear from the interested network interface. Depending on lease duration before the second lease expires ( for 10 minure we have 2 minutes before ) networkd configure only the new ip address on the network interface and the ping toward an outside host work properly. During the test the dhcp server records correctly leases and their duration. We check directly from console the network interface setting with the tool ip, checking continuously the value for ip address and valid_lft fields for the interested network interface. Please note that if the ip address setting are the same between leases the problem doesn’t jump out. Please note that if the ip address setting are different between lease the problem jumps out and it is very bad: Typically the lease time on consumer router are about some day, then a board that change ip between lease loses the network connectivity for some day without a direct action. Please, after a confirmation from your side of the issue, could you fix the problem or escalate the issue at the upstream project? We are available for further testing. Below syslog annotated with ip address state: Oct 4 09:48:06 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:49:36 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:49:25 localhost systemd-timesyncd[996]: Network configuration changed, trying to establish connection. Oct 4 09:49:26 localhost systemd-timesyncd[996]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com). Oct 4 09:49:26 localhost systemd[1]: Starting Update resolvconf for networkd DNS... Oct 4 09:49:26 localhost systemd[1]: Started Update resolvconf for networkd DNS. Oct 4 09:49:37 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:51:07 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:51:09 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:52:39 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:52:40 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:54:10 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:54:11 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:55:41 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:54:23 localhost systemd-timesyncd[996]: Network configuration changed, trying to establish connection. Oct 4 09:54:23 localhost systemd[1]: Starting Update resolvconf for networkd DNS... Oct 4 09:54:23 localhost systemd-timesyncd[996]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com). Oct 4 09:54:23 localhost systemd[1]: Started Update resolvconf for networkd DNS. Oct 4 09:55:43 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:57:13 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:57:14 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:58:44 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:58:46 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 10:00:16 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 10:00:17 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 10:01:47 2017 [v8
[Touch-packages] [Bug 1721763] Re: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart
out 06 16:02:20 etm kernel: [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon out 06 16:02:20 etm kernel: [drm:intel_ddi_init [i915]] *ERROR* LSPCON init failed on port B -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1721763 Title: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: I really do not know which package to assign this incident, please excuse me. Any way, the release candidates is near, and this problem continues to occur since linux kernel was updated from 4.11 to 4.12 ... and now with version 4.13 the problem continues. I noticed that this problem does not occur with my other two older notebooks (one Sony Vaio and the other a generic one integrated by me) both old notes use NVIDIA video card in versions of more than 5 years ago. My new Dell notebook has a GTX 1050 video card ... but I also do not know if the cause of this problem may be linked to the video card and the fact that Nouveau driver and linux Kernel have received recent implementations for compatibilities with this new NVIDIA technology. The fact is that Ubuntu 17.10 has potential to be distributed with this problem and I think this may not be interesting, so I am reporting this case. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.402 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 08:25:20 2017 InstallationDate: Installed on 2017-09-29 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1721763/+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 1721763] Re: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart
out 06 16:02:20 etm kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed4-0xfed4087f flags 0x200] vs fed40080 out 06 16:02:20 etm kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed4-0xfed4087f flags 0x200] vs fed40080 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1721763 Title: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: I really do not know which package to assign this incident, please excuse me. Any way, the release candidates is near, and this problem continues to occur since linux kernel was updated from 4.11 to 4.12 ... and now with version 4.13 the problem continues. I noticed that this problem does not occur with my other two older notebooks (one Sony Vaio and the other a generic one integrated by me) both old notes use NVIDIA video card in versions of more than 5 years ago. My new Dell notebook has a GTX 1050 video card ... but I also do not know if the cause of this problem may be linked to the video card and the fact that Nouveau driver and linux Kernel have received recent implementations for compatibilities with this new NVIDIA technology. The fact is that Ubuntu 17.10 has potential to be distributed with this problem and I think this may not be interesting, so I am reporting this case. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.402 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 08:25:20 2017 InstallationDate: Installed on 2017-09-29 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1721763/+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 1721763] Re: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart
and this: out 06 16:02:20 etm kernel: ACPI: Core revision 20170531 out 06 16:02:20 etm kernel: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20170531/dswload-210) out 06 16:02:20 etm kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170531/psobject-252) out 06 16:02:20 etm kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_OEMBD) while loading table (20170531/tbxfload-228) out 06 16:02:20 etm kernel: ACPI Error: 1 table load failures, 10 successful (20170531/tbxfload-246) out 06 16:02:20 etm kernel: Security Framework initialized -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1721763 Title: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: I really do not know which package to assign this incident, please excuse me. Any way, the release candidates is near, and this problem continues to occur since linux kernel was updated from 4.11 to 4.12 ... and now with version 4.13 the problem continues. I noticed that this problem does not occur with my other two older notebooks (one Sony Vaio and the other a generic one integrated by me) both old notes use NVIDIA video card in versions of more than 5 years ago. My new Dell notebook has a GTX 1050 video card ... but I also do not know if the cause of this problem may be linked to the video card and the fact that Nouveau driver and linux Kernel have received recent implementations for compatibilities with this new NVIDIA technology. The fact is that Ubuntu 17.10 has potential to be distributed with this problem and I think this may not be interesting, so I am reporting this case. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.402 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 08:25:20 2017 InstallationDate: Installed on 2017-09-29 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1721763/+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 1721763] Re: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart
out 06 16:02:21 etm NetworkManager[884]: ((src/devices/nm- device.c:1452)): assertion '' failed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1721763 Title: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: I really do not know which package to assign this incident, please excuse me. Any way, the release candidates is near, and this problem continues to occur since linux kernel was updated from 4.11 to 4.12 ... and now with version 4.13 the problem continues. I noticed that this problem does not occur with my other two older notebooks (one Sony Vaio and the other a generic one integrated by me) both old notes use NVIDIA video card in versions of more than 5 years ago. My new Dell notebook has a GTX 1050 video card ... but I also do not know if the cause of this problem may be linked to the video card and the fact that Nouveau driver and linux Kernel have received recent implementations for compatibilities with this new NVIDIA technology. The fact is that Ubuntu 17.10 has potential to be distributed with this problem and I think this may not be interesting, so I am reporting this case. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.402 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 08:25:20 2017 InstallationDate: Installed on 2017-09-29 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1721763/+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 1721763] Re: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart
out 06 16:02:21 etm avahi-daemon[901]: chroot.c: open() failed: No such file or directory -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1721763 Title: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: I really do not know which package to assign this incident, please excuse me. Any way, the release candidates is near, and this problem continues to occur since linux kernel was updated from 4.11 to 4.12 ... and now with version 4.13 the problem continues. I noticed that this problem does not occur with my other two older notebooks (one Sony Vaio and the other a generic one integrated by me) both old notes use NVIDIA video card in versions of more than 5 years ago. My new Dell notebook has a GTX 1050 video card ... but I also do not know if the cause of this problem may be linked to the video card and the fact that Nouveau driver and linux Kernel have received recent implementations for compatibilities with this new NVIDIA technology. The fact is that Ubuntu 17.10 has potential to be distributed with this problem and I think this may not be interesting, so I am reporting this case. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.402 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 08:25:20 2017 InstallationDate: Installed on 2017-09-29 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1721763/+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 1721763] Re: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart
out 06 16:02:22 etm wpa_supplicant[1133]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none out 06 16:02:22 etm wpa_supplicant[1133]: dbus: Failed to construct signal out 06 16:02:22 etm wpa_supplicant[1133]: Could not read interface p2p-dev-wlp3s0 flags: No such device -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1721763 Title: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: I really do not know which package to assign this incident, please excuse me. Any way, the release candidates is near, and this problem continues to occur since linux kernel was updated from 4.11 to 4.12 ... and now with version 4.13 the problem continues. I noticed that this problem does not occur with my other two older notebooks (one Sony Vaio and the other a generic one integrated by me) both old notes use NVIDIA video card in versions of more than 5 years ago. My new Dell notebook has a GTX 1050 video card ... but I also do not know if the cause of this problem may be linked to the video card and the fact that Nouveau driver and linux Kernel have received recent implementations for compatibilities with this new NVIDIA technology. The fact is that Ubuntu 17.10 has potential to be distributed with this problem and I think this may not be interesting, so I am reporting this case. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.402 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 08:25:20 2017 InstallationDate: Installed on 2017-09-29 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1721763/+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 1721763] Re: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart
out 06 16:02:21 etm gnome-session-binary[1110]: Unrecoverable failure in required component org.gnome.Shell.desktop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1721763 Title: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: I really do not know which package to assign this incident, please excuse me. Any way, the release candidates is near, and this problem continues to occur since linux kernel was updated from 4.11 to 4.12 ... and now with version 4.13 the problem continues. I noticed that this problem does not occur with my other two older notebooks (one Sony Vaio and the other a generic one integrated by me) both old notes use NVIDIA video card in versions of more than 5 years ago. My new Dell notebook has a GTX 1050 video card ... but I also do not know if the cause of this problem may be linked to the video card and the fact that Nouveau driver and linux Kernel have received recent implementations for compatibilities with this new NVIDIA technology. The fact is that Ubuntu 17.10 has potential to be distributed with this problem and I think this may not be interesting, so I am reporting this case. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.402 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 08:25:20 2017 InstallationDate: Installed on 2017-09-29 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1721763/+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 1721763] Re: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart
out 06 16:02:21 etm gnome-session-binary[1110]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Erro ao chamar StartServiceByName para org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1721763 Title: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: I really do not know which package to assign this incident, please excuse me. Any way, the release candidates is near, and this problem continues to occur since linux kernel was updated from 4.11 to 4.12 ... and now with version 4.13 the problem continues. I noticed that this problem does not occur with my other two older notebooks (one Sony Vaio and the other a generic one integrated by me) both old notes use NVIDIA video card in versions of more than 5 years ago. My new Dell notebook has a GTX 1050 video card ... but I also do not know if the cause of this problem may be linked to the video card and the fact that Nouveau driver and linux Kernel have received recent implementations for compatibilities with this new NVIDIA technology. The fact is that Ubuntu 17.10 has potential to be distributed with this problem and I think this may not be interesting, so I am reporting this case. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.402 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 08:25:20 2017 InstallationDate: Installed on 2017-09-29 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1721763/+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 1721763] Re: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart
out 06 16:02:22 etm kernel: nouveau :01:00.0: gr: intr 0040 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1721763 Title: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: I really do not know which package to assign this incident, please excuse me. Any way, the release candidates is near, and this problem continues to occur since linux kernel was updated from 4.11 to 4.12 ... and now with version 4.13 the problem continues. I noticed that this problem does not occur with my other two older notebooks (one Sony Vaio and the other a generic one integrated by me) both old notes use NVIDIA video card in versions of more than 5 years ago. My new Dell notebook has a GTX 1050 video card ... but I also do not know if the cause of this problem may be linked to the video card and the fact that Nouveau driver and linux Kernel have received recent implementations for compatibilities with this new NVIDIA technology. The fact is that Ubuntu 17.10 has potential to be distributed with this problem and I think this may not be interesting, so I am reporting this case. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.402 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 08:25:20 2017 InstallationDate: Installed on 2017-09-29 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1721763/+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 1721763] Re: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart
And it's all. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1721763 Title: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: I really do not know which package to assign this incident, please excuse me. Any way, the release candidates is near, and this problem continues to occur since linux kernel was updated from 4.11 to 4.12 ... and now with version 4.13 the problem continues. I noticed that this problem does not occur with my other two older notebooks (one Sony Vaio and the other a generic one integrated by me) both old notes use NVIDIA video card in versions of more than 5 years ago. My new Dell notebook has a GTX 1050 video card ... but I also do not know if the cause of this problem may be linked to the video card and the fact that Nouveau driver and linux Kernel have received recent implementations for compatibilities with this new NVIDIA technology. The fact is that Ubuntu 17.10 has potential to be distributed with this problem and I think this may not be interesting, so I am reporting this case. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.402 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 08:25:20 2017 InstallationDate: Installed on 2017-09-29 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1721763/+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 1721763] Re: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart
out 06 16:02:47 etm kernel: nouveau :01:00.0: gr: intr 0040 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1721763 Title: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: I really do not know which package to assign this incident, please excuse me. Any way, the release candidates is near, and this problem continues to occur since linux kernel was updated from 4.11 to 4.12 ... and now with version 4.13 the problem continues. I noticed that this problem does not occur with my other two older notebooks (one Sony Vaio and the other a generic one integrated by me) both old notes use NVIDIA video card in versions of more than 5 years ago. My new Dell notebook has a GTX 1050 video card ... but I also do not know if the cause of this problem may be linked to the video card and the fact that Nouveau driver and linux Kernel have received recent implementations for compatibilities with this new NVIDIA technology. The fact is that Ubuntu 17.10 has potential to be distributed with this problem and I think this may not be interesting, so I am reporting this case. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.402 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 08:25:20 2017 InstallationDate: Installed on 2017-09-29 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1721763/+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 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)
** Changed in: maas
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
[2.3] resolv.conf is not set (during commissioning or testing)
Status in MAAS:
Fix Committed
Status in cloud-init package in Ubuntu:
Confirmed
Status in resolvconf package in Ubuntu:
In Progress
Bug description:
Using MAAS 2.3, during commissioning (and likely in the rest of the
ephemeral environment) we have noticed that resolv.conf is not set
with the DNS server.
That said, during the commissioning process, MAAS does not send any
metadata to cloud-init to configure the network, rather, we expect the
image to boot from the network via DHCP. So, cloud-init writes:
ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
auto lo
iface lo inet loopback
# control-manual ens3
iface ens3 inet dhcp
broadcast 192.168.122.255
dns-nameservers 192.168.122.2
gateway 192.168.122.1
netmask 255.255.255.0
Which correctly includes the DNS server. However:
ubuntu@manual:~$ ping google.com
ping: unknown host google.com
If restart the interfacE:
ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
ifdown: interface ens3 not configured
Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/ens3/52:54:00:ea:57:31
Sending on LPF/ens3/52:54:00:ea:57:31
Sending on Socket/fallback
DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67
(xid=0x5403eb14)
DHCPOFFER of 192.168.122.195 from 192.168.122.2
DHCPACK of 192.168.122.195 from 192.168.122.2
Restarting ntp (via systemctl): ntp.service.
bound to 192.168.122.195 -- renewal in 290 seconds.
ubuntu@manual:~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.122.2
search maas
ubuntu@manual:~$ ping google.com
PING google.com (216.58.192.46) 56(84) bytes of data.
64 bytes from mia07s46-in-f14.1e100.net (216.58.192.46): icmp_seq=1 ttl=52
time=7.47 ms
^C
--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 7.472/7.472/7.472/0.000 ms
As such, this either seems like a bug in Ubuntu, or caused by cloud-
init when writing e/n/i.d/50-cloud-init.cfg
ubuntu@manual:~$ dpkg -l | grep cloud-init
ii cloud-init 0.7.9-153-g16a7302f-0ubuntu1~16.04.2
all Init scripts for cloud instances
ii cloud-initramfs-copymods 0.27ubuntu1.4
all copy initramfs modules into root filesystem for later use
ii cloud-initramfs-dyn-netconf 0.27ubuntu1.4
all write a network interface file in /run for BOOTIF
ubuntu@manual:~$ uname -a
Linux manual 4.4.0-92-generic #115-Ubuntu SMP Thu Aug 10 09:04:33 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@manual:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename: xenial
ubuntu@manual:~$ pastebinit /var/log/cloud-init.log
http://paste.ubuntu.com/25342738/
ubuntu@manual:~$ pastebinit /var/log/cloud-init-output.log
http://paste.ubuntu.com/25342740/
Related bugs:
* bug 1714308: dns does not work in initramfs after configure_networking
* bug 1713803: replacement of resolvconf with systemd needs integration
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1711760/+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 1721880] [NEW] can't disable wi-fi and system hangs on shutdown
Public bug reported: If I try to turn off wi-fi the system freezes for few seconds and after that internet is not working and I can't open settings anymore, even if the wi-fi tray icon still shows a connection. When I shutdown the system it says that "A stop job for network-manager and wpa supplicant is running" and I have to wait for 10-11 minutes. Suspension doesn't work neither. Everything was working just fine on 17.10 daily builds. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 23:18:01 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-09-22 (14 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917) IpRoute: default via 192.168.1.254 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.105 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/3 Alice_BO2f15ab74-48df-437b-b0a1-83bf31708fea /org/freedesktop/NetworkManager/ActiveConnection/1 enp2s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- 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/1721880 Title: can't disable wi-fi and system hangs on shutdown Status in network-manager package in Ubuntu: New Bug description: If I try to turn off wi-fi the system freezes for few seconds and after that internet is not working and I can't open settings anymore, even if the wi-fi tray icon still shows a connection. When I shutdown the system it says that "A stop job for network-manager and wpa supplicant is running" and I have to wait for 10-11 minutes. Suspension doesn't work neither. Everything was working just fine on 17.10 daily builds. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 23:18:01 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-09-22 (14 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917) IpRoute: default via 192.168.1.254 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.105 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/3 Alice_BO2f15ab74-48df-437b-b0a1-83bf31708fea /org/freedesktop/NetworkManager/ActiveConnection/1 enp2s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled
[Touch-packages] [Bug 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault
ok, would you mind filing it upstream then? https://bugs.freedesktop.org -- Mesa, Drivers/Vulkan/radeon -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1720890 Title: vulkan-smoketest segfaults steam vulkan games segfault Status in mesa package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 $ apt-cache policy mesa-vulkan-drivers mesa-vulkan-drivers: Installed: 17.2.1-0ubuntu1 Candidate: 17.2.1-0ubuntu1 Version table: *** 17.2.1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages 100 /var/lib/dpkg/status Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install vulkan-utils Open a terminal type vulkan-smoketest instead of a glxgears type window it will segfault. message from kernel.log: Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in libvulkan_radeon.so[7fed619ab000+18b000] syslog: Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in libvulkan_radeon.so[7f627053b000+18b000] What should happen is a glxgears like window will open and render properly instead of segfaulting. It appears that the culprit is an old or broken libvulkan_radeon.so provided by mesa-vulkan-drivers. As a test I renamed the old lib and dropped in a newer version from oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad Max now work properly in Vulkan mode as well instead of segfaulting. This issue is also present on Zesty and fixed in both Oibaf's and Padoka's ppa's since April back when they were rolling 17.2 mesa. I have no idea if libvulkan_intel.so also needs updating no hardware to check. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1720890/+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 1682934] Re: python3 in /usr/local/bin can cause python3 packages to fail to install
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python2.7 (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1682934 Title: python3 in /usr/local/bin can cause python3 packages to fail to install Status in python2.7 package in Ubuntu: Fix Released Status in python3.5 package in Ubuntu: Fix Released Status in python2.7 source package in Xenial: Confirmed Status in python3.5 source package in Xenial: Fix Released Status in python2.7 source package in Zesty: Confirmed Status in python3.5 source package in Zesty: Fix Released Status in python3.5 package in Debian: Fix Released Bug description: [Impact] An upgrade of python3.5 will fail if someone has installed a different version of python3.5 in their path e.g. in /usr/local/bin. This is because the postinst scripts do not specify the complete path to python3.5. [Test Case] 1) Ensure the version of python3.5 from the release pocket is installed 2) Install python3 using the instructions at https://passingcuriosity.com/2015/installing-python-from-source/ 3) Confirm that python3.5 from /usr/local/bin/ is being used / the default 4) Upgrade to a newer version of python3.5 from -proposed Observe the following Traceback: Setting up python3.5-minimal (3.5.3-1) ... Traceback (most recent call last): File "/usr/lib/python3.5/py_compile.py", line 6, in import importlib._bootstrap_external File "/usr/lib/python3.5/importlib/__init__.py", line 57, in import types File "/usr/lib/python3.5/types.py", line 166, in import functools as _functools File "/usr/lib/python3.5/functools.py", line 23, in from weakref import WeakKeyDictionary File "/usr/lib/python3.5/weakref.py", line 12, in from _weakref import ( ImportError: cannot import name '_remove_dead_weakref' dpkg: error processing package python3.5-minimal (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of python3-minimal: python3-minimal depends on python3.5-minimal (>= 3.5.3-1~); however: Package python3.5-minimal is not configured yet. dpkg: error processing package python3-minimal (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: python3.5-minimal python3-minimal With the version of python3.5 from -proposed this Traceback will not be encountered. [Regression Potential] It's possible I missed a postinst script so other python3.5 binary packages should be installed to ensure they are all fixed e.g. python3.5-dbg. [Original Description] Got this error while using "Transmageddon Video Transcoder" and again while updating 16.10 to 17.04. Seems to have something to do with needing that Python3 version for Teletext decoding in media that is in transport stream format (.ts). ProblemType: PackageDistroRelease: Ubuntu 17.04 Package: python3 3.5.1-4 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Fri Apr 14 19:27:33 2017 ErrorMessage: pre-dependency problem - not installing python3 InstallationDate: Installed on 2015-05-01 (714 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4SourcePackage: python3-defaults Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3 UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1682934/+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 1682934] Re: python3 in /usr/local/bin can cause python3 packages to fail to install
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python2.7 (Ubuntu Zesty) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1682934 Title: python3 in /usr/local/bin can cause python3 packages to fail to install Status in python2.7 package in Ubuntu: Fix Released Status in python3.5 package in Ubuntu: Fix Released Status in python2.7 source package in Xenial: Confirmed Status in python3.5 source package in Xenial: Fix Released Status in python2.7 source package in Zesty: Confirmed Status in python3.5 source package in Zesty: Fix Released Status in python3.5 package in Debian: Fix Released Bug description: [Impact] An upgrade of python3.5 will fail if someone has installed a different version of python3.5 in their path e.g. in /usr/local/bin. This is because the postinst scripts do not specify the complete path to python3.5. [Test Case] 1) Ensure the version of python3.5 from the release pocket is installed 2) Install python3 using the instructions at https://passingcuriosity.com/2015/installing-python-from-source/ 3) Confirm that python3.5 from /usr/local/bin/ is being used / the default 4) Upgrade to a newer version of python3.5 from -proposed Observe the following Traceback: Setting up python3.5-minimal (3.5.3-1) ... Traceback (most recent call last): File "/usr/lib/python3.5/py_compile.py", line 6, in import importlib._bootstrap_external File "/usr/lib/python3.5/importlib/__init__.py", line 57, in import types File "/usr/lib/python3.5/types.py", line 166, in import functools as _functools File "/usr/lib/python3.5/functools.py", line 23, in from weakref import WeakKeyDictionary File "/usr/lib/python3.5/weakref.py", line 12, in from _weakref import ( ImportError: cannot import name '_remove_dead_weakref' dpkg: error processing package python3.5-minimal (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of python3-minimal: python3-minimal depends on python3.5-minimal (>= 3.5.3-1~); however: Package python3.5-minimal is not configured yet. dpkg: error processing package python3-minimal (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: python3.5-minimal python3-minimal With the version of python3.5 from -proposed this Traceback will not be encountered. [Regression Potential] It's possible I missed a postinst script so other python3.5 binary packages should be installed to ensure they are all fixed e.g. python3.5-dbg. [Original Description] Got this error while using "Transmageddon Video Transcoder" and again while updating 16.10 to 17.04. Seems to have something to do with needing that Python3 version for Teletext decoding in media that is in transport stream format (.ts). ProblemType: PackageDistroRelease: Ubuntu 17.04 Package: python3 3.5.1-4 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Fri Apr 14 19:27:33 2017 ErrorMessage: pre-dependency problem - not installing python3 InstallationDate: Installed on 2015-05-01 (714 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4SourcePackage: python3-defaults Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3 UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1682934/+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 1717471] Re: networkd does not accept / set advertised mtu
Hello Dimitri, or anyone else affected, Accepted nplan into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nplan/0.29~17.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: nplan (Ubuntu Zesty) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-zesty -- 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/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in nplan source package in Xenial: New Status in systemd source package in Xenial: New Status in nplan source package in Zesty: Fix Committed Bug description: [Impact] Hosts may require a specific MTU to be set as passed by DHCP options. We should honor these settings to ensure proper communication of the host with the rest of the network. [Test case] 1) Run netplan on a system that should receive MTU settings from DHCP. 2) Validate that the MTU configuration provided by DHCP is applied to the right interface. [Regression Potential] If DHCP settings specify an invalid MTU setting which is currently being ignored and letting the systems communicate correctly with the network, then these systems would regress. --- Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+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 1662031] Re: Switching language and format broken
/etc/pam.d/gdm-launch-environment is run as user gdm, so it's not what
we're interested in.
/etc/pam.d/gdm-password appears to be what sets the environment upon
user login.
When adding some logging to that module, I'm seeing the following:
pam_env(gdm-password:session): username=ubuntu
pam_env(gdm-password:session): user env path: /home/ubuntu/.pam_environment
pam_env(gdm-password:session): parsing config file
pam_env(gdm-password:session): remove variable "LANGUAGE=fr_FR:en_GB:en"
pam_env(gdm-password:session): remove variable "LANG=fr_FR.UTF-8"
It turns out, "VARIABLE=value" is not the correct syntax for
~/.pam_environment. The expected syntax is "VARIABLE [DEFAULT=[value]]
[OVERRIDE=[value]]" (man pam_env.conf).
And indeed if I modify ~/.pam_environment to conform to that syntax, I'm seeing
this instead:
pam_env(gdm-password:session): pam_putenv("LANGUAGE=fr_FR:en_GB:en")
pam_env(gdm-password:session): pam_putenv("LANG=fr_FR.UTF-8")
That doesn't seem to fix the overall issue though, as the values of
LANGUAGE and LANG are still those from /etc/default/locale after logging
in.
--
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/1662031
Title:
Switching language and format broken
Status in Ubuntu GNOME:
New
Status in accountsservice package in Ubuntu:
New
Status in gdm3 package in Ubuntu:
Confirmed
Status in gnome-control-center package in Ubuntu:
New
Status in accountsservice source package in Artful:
New
Status in gdm3 source package in Artful:
Confirmed
Status in gnome-control-center source package in Artful:
New
Bug description:
In Ubuntu GNOME 16.10 it doesn't matter what display language I select
- the effective language is still the one stated in
/etc/default/locale. ~/.pam_environment is changed as expected, but
the variables set in /etc/default/locale override ~/.pam_environment.
In Ubuntu GNOME 16.04 language switching takes effect, but the reason
for that seems to be that /etc/default/locale is changed as well, so
when a user changes the display language (or format), it changes it
for all users on the system.
The overriding by /etc/default/locale is probably caused by some other
package(s) but g-c-c.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1662031/+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 1709135] Re: add bond primary parameter
Hello Ryan, or anyone else affected, Accepted nplan into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nplan/0.29~17.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: nplan (Ubuntu Zesty) Status: Triaged => Fix Committed -- 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/1709135 Title: add bond primary parameter Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: Fix Committed Status in nplan source package in Zesty: Fix Committed Status in systemd source package in Zesty: Fix Committed Status in nplan source package in Artful: Fix Released Status in systemd source package in Artful: Fix Released Bug description: [Impact] Some complex bond configurations require setting a "primary" interface for the bond, or setting this greatly improves performance on the network bond. [Test case] See below for a configuration example. 1) Apply configuration on a system with netplan. 2) Run 'netplan apply' 3) Validate that netplan apply does not return with an error 4) Validate that netplan properly sets the "primary_slave" value on the bond. This can be verified by looking at /sys/class/net//bonding/primary_slave. 5) Validate that there are no parsing errors from systemd-networkd in the journalctl [Regression potential] If existing configuration fails to be parsed, or lack of primary interface breaks configuration for existing bonds, this would be a regression caused by this update. --- ifenslave/eni support a bond parameter: bond-primary which accepts an interface name that can be used to tell the kernel bonding driver which interface it should preferred in active-backup (and other modes). This config option is missing in netplan. % cat bond-primary.yaml network: version: 2 ethernets: eth0: match: driver: virtio ens4: match: driver: e1000 bonds: bond0: parameters: mode: active-backup mii-monitor-interval: 100 primary: e1000 dhcp4: true % ./generate -r `pwd`/target Error in network definition /home/rharper/work/git/netplan/target//etc/netplan/bond-primary.yaml line 12 column 8: unknown key primary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1709135/+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 1717471] Re: networkd does not accept / set advertised mtu
Hello Dimitri, or anyone else affected, Accepted nplan into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nplan/0.29~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: nplan (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-xenial -- 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/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: New Status in nplan source package in Zesty: Fix Committed Bug description: [Impact] Hosts may require a specific MTU to be set as passed by DHCP options. We should honor these settings to ensure proper communication of the host with the rest of the network. [Test case] 1) Run netplan on a system that should receive MTU settings from DHCP. 2) Validate that the MTU configuration provided by DHCP is applied to the right interface. [Regression Potential] If DHCP settings specify an invalid MTU setting which is currently being ignored and letting the systems communicate correctly with the network, then these systems would regress. --- Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+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 1709135] Re: add bond primary parameter
Hello Ryan, or anyone else affected, Accepted nplan into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nplan/0.29~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: nplan (Ubuntu Xenial) Status: Triaged => Fix Committed ** Tags removed: verification-done-xenial ** Tags added: verification-needed-xenial -- 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/1709135 Title: add bond primary parameter Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: Fix Committed Status in nplan source package in Zesty: Fix Committed Status in systemd source package in Zesty: Fix Committed Status in nplan source package in Artful: Fix Released Status in systemd source package in Artful: Fix Released Bug description: [Impact] Some complex bond configurations require setting a "primary" interface for the bond, or setting this greatly improves performance on the network bond. [Test case] See below for a configuration example. 1) Apply configuration on a system with netplan. 2) Run 'netplan apply' 3) Validate that netplan apply does not return with an error 4) Validate that netplan properly sets the "primary_slave" value on the bond. This can be verified by looking at /sys/class/net//bonding/primary_slave. 5) Validate that there are no parsing errors from systemd-networkd in the journalctl [Regression potential] If existing configuration fails to be parsed, or lack of primary interface breaks configuration for existing bonds, this would be a regression caused by this update. --- ifenslave/eni support a bond parameter: bond-primary which accepts an interface name that can be used to tell the kernel bonding driver which interface it should preferred in active-backup (and other modes). This config option is missing in netplan. % cat bond-primary.yaml network: version: 2 ethernets: eth0: match: driver: virtio ens4: match: driver: e1000 bonds: bond0: parameters: mode: active-backup mii-monitor-interval: 100 primary: e1000 dhcp4: true % ./generate -r `pwd`/target Error in network definition /home/rharper/work/git/netplan/target//etc/netplan/bond-primary.yaml line 12 column 8: unknown key primary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1709135/+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 1662031] Re: Switching language and format broken
/usr/share/language-tools/save-to-pam-env is the script that writes to ~/.pam_environment with an incorrect syntax. -- 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/1662031 Title: Switching language and format broken Status in Ubuntu GNOME: New Status in accountsservice package in Ubuntu: New Status in gdm3 package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: New Status in accountsservice source package in Artful: New Status in gdm3 source package in Artful: Confirmed Status in gnome-control-center source package in Artful: New Bug description: In Ubuntu GNOME 16.10 it doesn't matter what display language I select - the effective language is still the one stated in /etc/default/locale. ~/.pam_environment is changed as expected, but the variables set in /etc/default/locale override ~/.pam_environment. In Ubuntu GNOME 16.04 language switching takes effect, but the reason for that seems to be that /etc/default/locale is changed as well, so when a user changes the display language (or format), it changes it for all users on the system. The overriding by /etc/default/locale is probably caused by some other package(s) but g-c-c. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1662031/+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 1721204] Re: timesyncd has redundant condition conflict with ntp and others
This bug was fixed in the package systemd - 234-2ubuntu12 --- systemd (234-2ubuntu12) artful; urgency=medium [ Dimitri John Ledkov ] * debian/rules: do not strip test-copy. This insures test-copy is large enough for test-copy tests to pass. (LP: #1721203) [ Michael Biebl ] * Drop systemd-timesyncd.service.d/disable-with-time-daemon.conf. All major NTP implementations ship a native service file nowadays with a Conflicts=systemd-timesyncd.service so this drop-in is no longer necessary. (Closes: #873185) (LP: #1721204) -- Dimitri John Ledkov Wed, 04 Oct 2017 13:28:34 +0100 ** Changed in: systemd (Ubuntu Artful) Status: Fix Committed => Fix Released -- 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/1721204 Title: timesyncd has redundant condition conflict with ntp and others Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Artful: Fix Released Bug description: Cherrypick Drop systemd-timesyncd.service.d/disable-with-time-daemon.conf All major NTP implementations ship a native service file nowadays with a Conflicts=systemd-timesyncd.service so this drop-in is no longer necessary. Closes: #873185 This should resolve the current issue in Ubuntu, where when both ntpd and timesyncd are installed, both are enabled yet neither run. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721204/+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 1717471] Re: networkd does not accept / set advertised mtu
This bug was fixed in the package systemd - 234-2ubuntu12 --- systemd (234-2ubuntu12) artful; urgency=medium [ Dimitri John Ledkov ] * debian/rules: do not strip test-copy. This insures test-copy is large enough for test-copy tests to pass. (LP: #1721203) [ Michael Biebl ] * Drop systemd-timesyncd.service.d/disable-with-time-daemon.conf. All major NTP implementations ship a native service file nowadays with a Conflicts=systemd-timesyncd.service so this drop-in is no longer necessary. (Closes: #873185) (LP: #1721204) -- Dimitri John Ledkov Wed, 04 Oct 2017 13:28:34 +0100 ** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released -- 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/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: New Status in nplan source package in Zesty: Fix Committed Bug description: [Impact] Hosts may require a specific MTU to be set as passed by DHCP options. We should honor these settings to ensure proper communication of the host with the rest of the network. [Test case] 1) Run netplan on a system that should receive MTU settings from DHCP. 2) Validate that the MTU configuration provided by DHCP is applied to the right interface. [Regression Potential] If DHCP settings specify an invalid MTU setting which is currently being ignored and letting the systems communicate correctly with the network, then these systems would regress. --- Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+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
