Re: [Touch-packages] [Bug 48734] Re: Home permissions too open
On 18/01/2021 12:46, Launchpad Bug Tracker wrote:
> This bug was fixed in the package adduser - 3.118ubuntu5
>
> ** Changed in: adduser (Ubuntu Hirsute)
>Status: Fix Committed => Fix Released
\o/
Well done and thank you to everyone who worked to make this happen.
I wonder if there will ever be another LP bug <50k that gets fix-
released?
Mark
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to adduser in Ubuntu.
https://bugs.launchpad.net/bugs/48734
Title:
Home permissions too open
Status in adduser package in Ubuntu:
Fix Released
Status in shadow package in Ubuntu:
Fix Released
Status in adduser source package in Hirsute:
Fix Released
Status in shadow source package in Hirsute:
Fix Released
Status in Ubuntu RTM:
Opinion
Bug description:
Binary package hint: debian-installer
On a fresh dapper install i noticed that the file permissons for the
home directory for the user created by the installer is set to 755,
giving read access to everyone on the system.
Surely this is a bad idea? If your set on the idea can we atleast have
a option during the boot proccess?
Also new files that are created via the console ('touch' etc.) are
done so with '644' permissons, is there anything that can be done
here? nautlius seems to create files at '600', which is a better
setting.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/48734/+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 1664844] Re: No distinction between link-up and link-down interfaces
Is there an updated target release for the ability to describe configuration for an interface (such as name) but leave the interface down at boot? -- 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/1664844 Title: No distinction between link-up and link-down interfaces Status in MAAS: Triaged Status in netplan: In Progress Status in netplan.io package in Ubuntu: In Progress Status in systemd package in Ubuntu: New Status in netplan.io source package in Xenial: Won't Fix Status in systemd source package in Xenial: Won't Fix Status in netplan.io source package in Zesty: Won't Fix Status in systemd source package in Zesty: Won't Fix Status in netplan.io source package in Artful: Won't Fix Bug description: [Impact] Users need to write valid configuration, especially for new features that are approved by not yet implemented, such as marking a link "optional". [Test case] Write a netplan configuration: network: version: 2 renderer: networkd ethernets: eth0: optional: yes dhcp4: yes And run 'netplan apply'. Netplan should write configuration for the link and not error out with a syntax error. [Regression potential] This has a minimal potential for regression: the new keyword was added to be supported already by consumers of netplan (users, cloud-init) so that they could start writing config with the new key and that configuration to be seen as valid by netplan before the backend is implemented. There is no functional change besides allowing for the value to exist in a netplan configuation. --- If I define an interface in netplan (even one which has no DHCP type and no addresses), it's not possible to determine if its adminStatus should be enabled (link up) or disabled (link down). I can completely exclude an interface from the netplan configuration, but I think that implies that not only its adminStatus is "disabled" by default, but also netplan will not be able to do anything "nice" for the interface, such as rename it to what the user specified in MAAS. If I include the interface but don't specify any addresses or DHCP, it isn't clear if it will be link up (my current assumption) or link down. There should be a way to allow an interface to be recognized by netplan (and even partially configured, waiting for the user to run something like 'ifup ' on a manual but not auto-started interface in ifupdown), but marked administratively disabled. (adminStatus down) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1664844/+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
Re: [Touch-packages] [Bug 1868706] Re: Snapd postinst script hangs
Pawel, this is great debugging, thank you. Agree it's an edge case. Mark -- 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/1868706 Title: Snapd postinst script hangs Status in snapd: Triaged Status in dpkg package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: On a machine which has been tracking upgrades for a while, I am unable to install new versions of snapd. The install process stalls indefinitely. Processes running suggest this is a hang in the postinst: ~$ ps ax | grep dpkg 2388 pts/1Ss+0:00 /usr/bin/dpkg --status-fd 25 --configure --pending 2389 pts/1S+ 0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8 2875 pts/2S+ 0:00 grep --color=auto dpkg ~$ pstree 2388 dpkg───snapd.postinst───systemctl───systemd-tty-ask ~$ ps ax | grep snapd 732 ?Ssl0:00 /usr/lib/snapd/snapd 2389 pts/1S+ 0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8 2452 pts/1S+ 0:00 /bin/systemctl start snapd.autoimport.service snapd.core-fixup.service snapd.recovery-chooser-trigger.service snapd.seeded.service snapd.service snapd.snap-repair.timer snapd.socket snapd.system-shutdown.service 2880 pts/2S+ 0:00 grep --color=auto snapd To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1868706/+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 1868706] Re: Snapd postinst script hangs
OK, so *now* the situation has cleared on that machine. And there are no snaps installed :/ -- 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/1868706 Title: Snapd postinst script hangs Status in snapd: Triaged Status in dpkg package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: On a machine which has been tracking upgrades for a while, I am unable to install new versions of snapd. The install process stalls indefinitely. Processes running suggest this is a hang in the postinst: ~$ ps ax | grep dpkg 2388 pts/1Ss+0:00 /usr/bin/dpkg --status-fd 25 --configure --pending 2389 pts/1S+ 0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8 2875 pts/2S+ 0:00 grep --color=auto dpkg ~$ pstree 2388 dpkg───snapd.postinst───systemctl───systemd-tty-ask ~$ ps ax | grep snapd 732 ?Ssl0:00 /usr/lib/snapd/snapd 2389 pts/1S+ 0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8 2452 pts/1S+ 0:00 /bin/systemctl start snapd.autoimport.service snapd.core-fixup.service snapd.recovery-chooser-trigger.service snapd.seeded.service snapd.service snapd.snap-repair.timer snapd.socket snapd.system-shutdown.service 2880 pts/2S+ 0:00 grep --color=auto snapd To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1868706/+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
Re: [Touch-packages] [Bug 1818340] Re: systemd-networkd core dumps in bionic-proposed
Confirmed that 3ubuntu10.15 fixes the core-dump in systemd-networkd. -- 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/1818340 Title: systemd-networkd core dumps in bionic-proposed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] during restart, systemd-networkd fails an assertion and aborts, leaving the system networking partially (if at all) configured. Further restarts continue to fail. [Test Case] Install a bionic system (cosmic affected also) with only systemd- networkd networking (i.e. uninstall or do not configure netplan). Ensure no networkd conf files are in /run/systemd/network. Stop networkd (sudo systemctl stop systemd-networkd). The interface to test with networkd (e.g. ens3) should have no address assigned and should be down. Create a file similar to below, adjusting for interface name: $ cat /etc/systemd/network/10-netplan-ens3.network [Match] Name=ens3 [Network] Address=192.168.122.68/24 Start networkd: ubuntu@lp1818340-b:~$ sudo systemctl start systemd-networkd ubuntu@lp1818340-b:~$ ip a show ens3 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:6e:8c:9f brd ff:ff:ff:ff:ff:ff inet 192.168.122.68/24 brd 192.168.122.255 scope global ens3 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe6e:8c9f/64 scope link valid_lft forever preferred_lft forever Stop networkd; ens3 should retain its address: ubuntu@lp1818340-b:~$ sudo systemctl stop systemd-networkd ubuntu@lp1818340-b:~$ ip a show ens3 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:6e:8c:9f brd ff:ff:ff:ff:ff:ff inet 192.168.122.68/24 brd 192.168.122.255 scope global ens3 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe6e:8c9f/64 scope link valid_lft forever preferred_lft forever Start networkd again; the bug is triggered: ubuntu@lp1818340-b:~$ sudo systemctl start systemd-networkd Job for systemd-networkd.service failed because a fatal signal was delivered causing the control process to dump core. See "systemctl status systemd-networkd.service" and "journalctl -xe" for details. Alternately, instead of separately stopping and then starting networkd, the failure can be reproduced with just a restart. Note the failure only happens with statically-assigned addresses; interfaces configured with dhcp do not trigger this bug. [Regression Potential] TBD [Other Info] This was introduced by the SRU for bug 1812760; both the new behavior of networkd not removing managed addresses/routes from managed interfaces, as well as the assertion failure bug. This does not fail in disco; I believe additional commit(s) from upstream need to be backported. Original description: --- I run a number of servers with -proposed enabled and have seen a bunch of this today: Mar 02 16:20:58 4-ridge-fw1 systemd[1]: systemd-networkd.service: Failed with result 'core-dump'. Mar 02 16:20:58 4-ridge-fw1 systemd[1]: Failed to start Network Service. These machines have numerous bonds, so I suspect that's a factor. So far I have only observed the issue on machines with -proposed enabled so I suspect it is a problem with systemd 237-3ubuntu10.14 Example netplan.yaml attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818340/+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
Re: [Touch-packages] [Bug 1818340] Re: systemd-networkd core dumps in bionic-proposed
Just to let you know, I still see 237-3ubuntu10.14 in -proposed and I think that's the one that has the issue. Mark -- 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/1818340 Title: systemd-networkd core dumps in bionic-proposed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: Fix Released Bug description: [Impact] during restart, systemd-networkd fails an assertion and aborts, leaving the system networking partially (if at all) configured. Further restarts continue to fail. [Test Case] Install a bionic system (cosmic affected also) with only systemd- networkd networking (i.e. uninstall or do not configure netplan). Ensure no networkd conf files are in /run/systemd/network. Stop networkd (sudo systemctl stop systemd-networkd). The interface to test with networkd (e.g. ens3) should have no address assigned and should be down. Create a file similar to below, adjusting for interface name: $ cat /etc/systemd/network/10-netplan-ens3.network [Match] Name=ens3 [Network] Address=192.168.122.68/24 Start networkd: ubuntu@lp1818340-b:~$ sudo systemctl start systemd-networkd ubuntu@lp1818340-b:~$ ip a show ens3 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:6e:8c:9f brd ff:ff:ff:ff:ff:ff inet 192.168.122.68/24 brd 192.168.122.255 scope global ens3 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe6e:8c9f/64 scope link valid_lft forever preferred_lft forever Stop networkd; ens3 should retain its address: ubuntu@lp1818340-b:~$ sudo systemctl stop systemd-networkd ubuntu@lp1818340-b:~$ ip a show ens3 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:6e:8c:9f brd ff:ff:ff:ff:ff:ff inet 192.168.122.68/24 brd 192.168.122.255 scope global ens3 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe6e:8c9f/64 scope link valid_lft forever preferred_lft forever Start networkd again; the bug is triggered: ubuntu@lp1818340-b:~$ sudo systemctl start systemd-networkd Job for systemd-networkd.service failed because a fatal signal was delivered causing the control process to dump core. See "systemctl status systemd-networkd.service" and "journalctl -xe" for details. Alternately, instead of separately stopping and then starting networkd, the failure can be reproduced with just a restart. Note the failure only happens with statically-assigned addresses; interfaces configured with dhcp do not trigger this bug. [Regression Potential] TBD [Other Info] This was introduced by the SRU for bug 1812760; both the new behavior of networkd not removing managed addresses/routes from managed interfaces, as well as the assertion failure bug. This does not fail in disco; I believe additional commit(s) from upstream need to be backported. Original description: --- I run a number of servers with -proposed enabled and have seen a bunch of this today: Mar 02 16:20:58 4-ridge-fw1 systemd[1]: systemd-networkd.service: Failed with result 'core-dump'. Mar 02 16:20:58 4-ridge-fw1 systemd[1]: Failed to start Network Service. These machines have numerous bonds, so I suspect that's a factor. So far I have only observed the issue on machines with -proposed enabled so I suspect it is a problem with systemd 237-3ubuntu10.14 Example netplan.yaml attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818340/+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 1818340] Re: systemd-networkd core dumps in bionic-proposed
Apport info from an affected system is in #1818487 -- 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/1818340 Title: systemd-networkd core dumps in bionic-proposed Status in systemd package in Ubuntu: New Bug description: I run a number of servers with -proposed enabled and have seen a bunch of this today: Mar 02 16:20:58 4-ridge-fw1 systemd[1]: systemd-networkd.service: Failed with result 'core-dump'. Mar 02 16:20:58 4-ridge-fw1 systemd[1]: Failed to start Network Service. These machines have numerous bonds, so I suspect that's a factor. So far I have only observed the issue on machines with -proposed enabled so I suspect it is a problem with systemd 237-3ubuntu10.14 Example netplan.yaml attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818340/+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 1818487] [NEW] systemd-networkd dumps core in bionic-proposed
*** This bug is a duplicate of bug 1818340 *** https://bugs.launchpad.net/bugs/1818340 Public bug reported: This is apport info for systemd related to #1818340 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.14 [modified: lib/systemd/system/systemd-networkd.service] ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Mon Mar 4 11:03:18 2019 MachineType: Supermicro X9DRL-3F/iF ProcEnviron: LANG=en_ZA.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=25ab7cee-0f78-4706-acc6-67bbc3d07908 ro console=tty0 console=ttyS1,115200 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X9DRL-3F/iF dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.3:bd07/12/2018:svnSupermicro:pnX9DRL-3F/iF:pvr0123456789:rvnSupermicro:rnX9DRL-3F/iF:rvr1.01:cvnSupermicro:ct3:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: X9DRL-3F/iF dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic package-from-proposed ** This bug has been marked a duplicate of bug 1818340 systemd-networkd core dumps in bionic-proposed -- 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/1818487 Title: systemd-networkd dumps core in bionic-proposed Status in systemd package in Ubuntu: New Bug description: This is apport info for systemd related to #1818340 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.14 [modified: lib/systemd/system/systemd-networkd.service] ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Mon Mar 4 11:03:18 2019 MachineType: Supermicro X9DRL-3F/iF ProcEnviron: LANG=en_ZA.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=25ab7cee-0f78-4706-acc6-67bbc3d07908 ro console=tty0 console=ttyS1,115200 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X9DRL-3F/iF dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.3:bd07/12/2018:svnSupermicro:pnX9DRL-3F/iF:pvr0123456789:rvnSupermicro:rnX9DRL-3F/iF:rvr1.01:cvnSupermicro:ct3:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: X9DRL-3F/iF dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818487/+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 1818340] Re: systemd-networkd core dumps in bionic-proposed
Taking the bond down and then bringing it back up again seemed to sort out the aggregation. I was able to assign an IP address to the bond and ping it. However, even with the bond sorted, restarting systemd-networkd dumps core. -- 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/1818340 Title: systemd-networkd core dumps in bionic-proposed Status in systemd package in Ubuntu: New Bug description: I run a number of servers with -proposed enabled and have seen a bunch of this today: Mar 02 16:20:58 4-ridge-fw1 systemd[1]: systemd-networkd.service: Failed with result 'core-dump'. Mar 02 16:20:58 4-ridge-fw1 systemd[1]: Failed to start Network Service. These machines have numerous bonds, so I suspect that's a factor. So far I have only observed the issue on machines with -proposed enabled so I suspect it is a problem with systemd 237-3ubuntu10.14 Example netplan.yaml attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818340/+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 1818340] Re: systemd-networkd core dumps in bionic-proposed
I found that the bond seems not to have come up properly: $ sudo cat /proc/net/bonding/bond-lan Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: IEEE 802.3ad Dynamic link aggregation Transmit Hash Policy: layer2+3 (2) MII Status: down MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 802.3ad info LACP rate: fast Min links: 0 Aggregator selection policy (ad_select): stable System priority: 65535 System MAC address: 5e:07:b7:b3:1d:bd bond bond-lan has no active aggregator Slave Interface: p3p4 MII Status: up Speed: 1 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 3c:fd:fe:77:32:cb Slave queue ID: 0 Aggregator ID: N/A Slave Interface: p3p3 MII Status: up Speed: 1 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 3c:fd:fe:77:32:ca Slave queue ID: 0 Aggregator ID: N/A -- 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/1818340 Title: systemd-networkd core dumps in bionic-proposed Status in systemd package in Ubuntu: New Bug description: I run a number of servers with -proposed enabled and have seen a bunch of this today: Mar 02 16:20:58 4-ridge-fw1 systemd[1]: systemd-networkd.service: Failed with result 'core-dump'. Mar 02 16:20:58 4-ridge-fw1 systemd[1]: Failed to start Network Service. These machines have numerous bonds, so I suspect that's a factor. So far I have only observed the issue on machines with -proposed enabled so I suspect it is a problem with systemd 237-3ubuntu10.14 Example netplan.yaml attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818340/+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 1818340] Re: systemd-networkd core dumps in bionic-proposed
Further digging in journalctl shows: -- Unit systemd-networkd.service has begun starting up. Mar 02 20:37:00 4-ridge-fw1 systemd-networkd[6851]: bond-lan: netdev ready Mar 02 20:37:00 4-ridge-fw1 systemd-networkd[6851]: bond-net: netdev ready Mar 02 20:37:00 4-ridge-fw1 systemd-networkd[6851]: bond-peer: netdev ready Mar 02 20:37:00 4-ridge-fw1 systemd-networkd[6851]: bond-plein: netdev ready Mar 02 20:37:00 4-ridge-fw1 systemd-networkd[6851]: bond-protea-2: netdev ready Mar 02 20:37:00 4-ridge-fw1 systemd-networkd[6851]: bond-protea: netdev ready Mar 02 20:37:00 4-ridge-fw1 systemd-networkd[6851]: bond-peer: Gained IPv6LL Mar 02 20:37:00 4-ridge-fw1 systemd-networkd[6851]: bond-plein: Gained IPv6LL Mar 02 20:37:00 4-ridge-fw1 systemd-networkd[6851]: bond-protea-2: Gained IPv6LL Mar 02 20:37:00 4-ridge-fw1 systemd-networkd[6851]: bond-protea: Gained IPv6LL Mar 02 20:37:00 4-ridge-fw1 systemd-networkd[6851]: Assertion 'link->state == LINK_STATE_SETTING_ADDRESSES' failed at ../src/network/networkd-link Mar 02 20:37:00 4-ridge-fw1 systemd[1]: systemd-networkd.service: Main process exited, code=dumped, status=6/ABRT Mar 02 20:37:00 4-ridge-fw1 systemd[1]: systemd-networkd.service: Failed with result 'core-dump'. Mar 02 20:37:00 4-ridge-fw1 systemd[1]: Failed to start Network Service. -- 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/1818340 Title: systemd-networkd core dumps in bionic-proposed Status in systemd package in Ubuntu: New Bug description: I run a number of servers with -proposed enabled and have seen a bunch of this today: Mar 02 16:20:58 4-ridge-fw1 systemd[1]: systemd-networkd.service: Failed with result 'core-dump'. Mar 02 16:20:58 4-ridge-fw1 systemd[1]: Failed to start Network Service. These machines have numerous bonds, so I suspect that's a factor. So far I have only observed the issue on machines with -proposed enabled so I suspect it is a problem with systemd 237-3ubuntu10.14 Example netplan.yaml attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818340/+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 1818340] [NEW] systemd-networkd core dumps in bionic-proposed
Public bug reported: I run a number of servers with -proposed enabled and have seen a bunch of this today: Mar 02 16:20:58 4-ridge-fw1 systemd[1]: systemd-networkd.service: Failed with result 'core-dump'. Mar 02 16:20:58 4-ridge-fw1 systemd[1]: Failed to start Network Service. These machines have numerous bonds, so I suspect that's a factor. So far I have only observed the issue on machines with -proposed enabled so I suspect it is a problem with systemd 237-3ubuntu10.14 Example netplan.yaml attached. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "npln.yml" https://bugs.launchpad.net/bugs/1818340/+attachment/5242832/+files/npln.yml -- 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/1818340 Title: systemd-networkd core dumps in bionic-proposed Status in systemd package in Ubuntu: New Bug description: I run a number of servers with -proposed enabled and have seen a bunch of this today: Mar 02 16:20:58 4-ridge-fw1 systemd[1]: systemd-networkd.service: Failed with result 'core-dump'. Mar 02 16:20:58 4-ridge-fw1 systemd[1]: Failed to start Network Service. These machines have numerous bonds, so I suspect that's a factor. So far I have only observed the issue on machines with -proposed enabled so I suspect it is a problem with systemd 237-3ubuntu10.14 Example netplan.yaml attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818340/+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 1818340] Re: systemd-networkd core dumps in bionic-proposed
Needless to say I suggest not promoting systemd from -proposed until this is figured out :) -- 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/1818340 Title: systemd-networkd core dumps in bionic-proposed Status in systemd package in Ubuntu: New Bug description: I run a number of servers with -proposed enabled and have seen a bunch of this today: Mar 02 16:20:58 4-ridge-fw1 systemd[1]: systemd-networkd.service: Failed with result 'core-dump'. Mar 02 16:20:58 4-ridge-fw1 systemd[1]: Failed to start Network Service. These machines have numerous bonds, so I suspect that's a factor. So far I have only observed the issue on machines with -proposed enabled so I suspect it is a problem with systemd 237-3ubuntu10.14 Example netplan.yaml attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818340/+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 1810578] Re: Set correct terminal size to improve login over serial port experience
&& works better :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1810578 Title: Set correct terminal size to improve login over serial port experience Status in base-files package in Ubuntu: New Bug description: For people who use ipmiconsole or other serial port access to servers a great deal it would be helpful to set LINES and COLUMNS correctly on login. There are a number of ways to do this. I found a small (10k) C application at: http://web.archive.org/web/20081224152013/http://www.davehylands.com /gumstix-wiki/resize/resize.c which works nicely. It appears to be a simplified version of the resize command in xterm (which has too many dependencies for comfortable server usage). It seems quite old (2006) so there may be a better, newer version of this. Perhaps it would be better named tty- resize. I added the following two lines to .profile which then invoke the resize command on login: # size the terminal for login over serial [[ $(tty) == /dev/ttyS* ]] & /usr/local/bin/resize I think remote serial usage is interesting for cloud and server farm use cases which are a big part of Ubuntu usage, so would like to improve experience in these cases across the board. This is a small part of that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1810578/+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 1810578] Re: Set correct terminal size to improve login over serial port experience
Hmm... that .profile causes this on SSH logins, so needs tweaking: Last login: Sat Jan 5 10:49:02 2019 from 192.168.4.70 [1]+ Exit 1 [[ $(tty) == /dev/ttyS* ]] john@xx:~$ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1810578 Title: Set correct terminal size to improve login over serial port experience Status in base-files package in Ubuntu: New Bug description: For people who use ipmiconsole or other serial port access to servers a great deal it would be helpful to set LINES and COLUMNS correctly on login. There are a number of ways to do this. I found a small (10k) C application at: http://web.archive.org/web/20081224152013/http://www.davehylands.com /gumstix-wiki/resize/resize.c which works nicely. It appears to be a simplified version of the resize command in xterm (which has too many dependencies for comfortable server usage). It seems quite old (2006) so there may be a better, newer version of this. Perhaps it would be better named tty- resize. I added the following two lines to .profile which then invoke the resize command on login: # size the terminal for login over serial [[ $(tty) == /dev/ttyS* ]] & /usr/local/bin/resize I think remote serial usage is interesting for cloud and server farm use cases which are a big part of Ubuntu usage, so would like to improve experience in these cases across the board. This is a small part of that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1810578/+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 1810578] [NEW] Set correct terminal size to improve login over serial port experience
Public bug reported: For people who use ipmiconsole or other serial port access to servers a great deal it would be helpful to set LINES and COLUMNS correctly on login. There are a number of ways to do this. I found a small (10k) C application at: http://web.archive.org/web/20081224152013/http://www.davehylands.com /gumstix-wiki/resize/resize.c which works nicely. It appears to be a simplified version of the resize command in xterm (which has too many dependencies for comfortable server usage). It seems quite old (2006) so there may be a better, newer version of this. Perhaps it would be better named tty-resize. I added the following two lines to .profile which then invoke the resize command on login: # size the terminal for login over serial [[ $(tty) == /dev/ttyS* ]] & /usr/local/bin/resize I think remote serial usage is interesting for cloud and server farm use cases which are a big part of Ubuntu usage, so would like to improve experience in these cases across the board. This is a small part of that. ** Affects: base-files (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1810578 Title: Set correct terminal size to improve login over serial port experience Status in base-files package in Ubuntu: New Bug description: For people who use ipmiconsole or other serial port access to servers a great deal it would be helpful to set LINES and COLUMNS correctly on login. There are a number of ways to do this. I found a small (10k) C application at: http://web.archive.org/web/20081224152013/http://www.davehylands.com /gumstix-wiki/resize/resize.c which works nicely. It appears to be a simplified version of the resize command in xterm (which has too many dependencies for comfortable server usage). It seems quite old (2006) so there may be a better, newer version of this. Perhaps it would be better named tty- resize. I added the following two lines to .profile which then invoke the resize command on login: # size the terminal for login over serial [[ $(tty) == /dev/ttyS* ]] & /usr/local/bin/resize I think remote serial usage is interesting for cloud and server farm use cases which are a big part of Ubuntu usage, so would like to improve experience in these cases across the board. This is a small part of that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1810578/+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
Re: [Touch-packages] [Bug 796588] Re: Fine-grained network mediation
Fine-grained network security for snaps is going to be fantastic, but it's also a rich area, and when networking policy stuff is done simplistically it becomes awkward more than useful. I'd suggest that we start now working up detailed design on the topic, so that when we are ready to start implementing we have confidence that the policy language is appropriate. I'm happy to participate in a discussion on this in Salt Lake City at the next roadmap review, would suggest the security team representatives bring a Discourse draft that's had some review by the snapd team for discussion. Mark -- 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/796588 Title: Fine-grained network mediation Status in AppArmor: In Progress Status in apparmor package in Ubuntu: Triaged Status in linux package in Ubuntu: Triaged Bug description: Binary package hint: apparmor This is a wishlist item / feature request. Increase the granularity of network restrictions to allow specification of which ports or ranges of ports can or can't be used by an application. This functionality is available in systrace if either the example or code would be of help: http://en.wikipedia.org/wiki/Systrace http://www.systrace.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/796588/+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
Re: [Touch-packages] [Bug 1791958] Re: iptables-restore is missing -w option
Seems like the point release would be a reasonable SRU. Mark -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1791958 Title: iptables-restore is missing -w option Status in iptables package in Ubuntu: Confirmed Bug description: For CRIU we need to have iptables version 1.6.2 which includes the '-w' option in iptables-restore. This is a request to update iptables to 1.6.2 in 18.10 and if possible backport the necessary changes to 18.04. The CRIU project gets right now many bug reports (mostly in the combination LXD + CRIU) due to the missing '-w' option in iptables- restore. Especially as 18.04 will be around for some time it would be good to have iptables-restore available with '-w'. This is one example bug report: https://github.com/checkpoint- restore/criu/issues/551 But not only CRIU would benefit from this change. It seems also problematic with Kubernetes: https://github.com/kubernetes/kubernetes/pull/60978 So if possible, please update iptables to 1.6.2 (or backport changes) to support -w in iptables-restore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1791958/+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 1751484] [NEW] Captive portal browser/device misreported
Public bug reported: The browser used in the captive portal system is reported as 'Desktop Safari Linux 64'. Could we change this to 'Ubuntu Desktop', please? ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1751484 Title: Captive portal browser/device misreported Status in network-manager package in Ubuntu: New Bug description: The browser used in the captive portal system is reported as 'Desktop Safari Linux 64'. Could we change this to 'Ubuntu Desktop', please? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1751484/+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
Re: [Touch-packages] [Bug 1734104] Re: 'upgrade' in bionic should by default autoremove as well
Perhaps we are talking at cross purposes. My expectation is that update would list the packages to be removed because they are no longer dependencies of packages that were consciously installed. On that basis, there should be no surprise to users. The messaging could point users to a handy document to understand how they can make a package stick around by flagging it as one they have manually / consciously installed. My point is that most users don't install 'linux-image-extra-4.13.0-15-generic' themselves, they have a system with 'linux-image-generic' installed, and it's dependencies change over time. AIUI, we already have a good way of holding back from autoremoval versions of the kernel which are currently in use, or which are the last-best-guess-good kernel, or which are the next-kernel-to-boot. All other kernels that were not explicitly installed by the user are simply ephemeral to that user, and for the vast majority of users, those ephemeral kernels build up over time taking large amounts of space and slowing down upgrades thanks to the initramfs generation mechanisms. Those kernels should go when they are deemed surplus; the user did not ask for them explicitly, and the user isn't going to boot them either. Here's what I have in mind, note the changes to text in the output of apt upgrade. The user is prompted, and told how to avoid autoremoval. $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done These packages were automatically installed and are no longer needed: libgweather-3-6, linux-image-extra-4.13.0-15-generic Cancel this operation and use 'sudo apt install ' to keep them from automatic removal. The following packages have been kept back: libreoffice-help-en-us The following packages will be upgraded: libio-socket-ssl-perl 1 upgraded, 0 newly installed, 2 to remove and 1 not upgraded. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1734104 Title: 'upgrade' in bionic should by default autoremove as well Status in apt package in Ubuntu: Triaged Bug description: In bionic, apt upgrade should also autoremove by default. I have a few bionic systems (upgrades from xenial mostly) which are not yet showing that behaviour, it may be we haven't implemented that yet so this is just a placeholder bug in that case :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1734104/+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 1748709] [NEW] Upgrade from xenial to bionic wants to replace moduli
Public bug reported: I see this on upgrade on one machine, which is unexpected. If this file is generated by each machine, why would we ship a default? Configuration file '/etc/ssh/moduli' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** moduli (Y/I/N/O/D/Z) [default=N] ? ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1748709 Title: Upgrade from xenial to bionic wants to replace moduli Status in openssh package in Ubuntu: New Bug description: I see this on upgrade on one machine, which is unexpected. If this file is generated by each machine, why would we ship a default? Configuration file '/etc/ssh/moduli' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** moduli (Y/I/N/O/D/Z) [default=N] ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1748709/+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
Re: [Touch-packages] [Bug 1727237] Re: systemd-resolved is not finding a domain
Thanks all, and Dimitri allow me to sponsor that Starbucks coffee :) -- 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/1727237 Title: systemd-resolved is not finding a domain Status in systemd package in Ubuntu: Triaged Bug description: I have an odd network situation that I have so far managed to narrow down to the inability to resolve a domain via systemd-resolved which is resolvable with nslookup. If I use nslookup against the two nameservers on this network I get answers for the domain, but ping says it is unable to resolve the same domain (as do browsers and crucially the captive portal mechanism). Here are details: NSLOOKUP: ~$ nslookup securelogin.arubanetworks.com 208.67.220.220 Server: 208.67.220.220 Address: 208.67.220.220#53 Non-authoritative answer: Name: securelogin.arubanetworks.com Address: 172.22.240.242 ~$ nslookup securelogin.arubanetworks.com 208.67.222.222 Server: 208.67.222.222 Address: 208.67.222.222#53 Non-authoritative answer: Name: securelogin.arubanetworks.com Address: 172.22.240.242 PING: ~$ ping securelogin.arubanetworks.com ping: securelogin.arubanetworks.com: Name or service not known mark@mark-X1Y2:~$ DIG: ~$ dig @208.67.222.222 securelogin.arubanetworks.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;securelogin.arubanetworks.com. IN A ;; AUTHORITY SECTION: arubanetworks.com.1991IN SOA dns5.arubanetworks.com. hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400 ;; Query time: 34 msec ;; SERVER: 208.67.222.222#53(208.67.222.222) ;; WHEN: Wed Oct 25 10:31:10 CEST 2017 ;; MSG SIZE rcvd: 144 MORE DIG: ~$ dig securelogin.arubanetworks.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;securelogin.arubanetworks.com. IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Oct 25 10:34:01 CEST 2017 ;; MSG SIZE rcvd: 58 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237/+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
Re: [Touch-packages] [Bug 1734104] Re: 'upgrade' in bionic should by default autoremove as well
The main reason to do this is kernel cruft. We have had kernels being flagged for removal for years now, and it's completely reliable. We really should garden that automatically. Mark -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1734104 Title: 'upgrade' in bionic should by default autoremove as well Status in apt package in Ubuntu: New Bug description: In bionic, apt upgrade should also autoremove by default. I have a few bionic systems (upgrades from xenial mostly) which are not yet showing that behaviour, it may be we haven't implemented that yet so this is just a placeholder bug in that case :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1734104/+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 1734104] [NEW] 'upgrade' in bionic should by default autoremove as well
Public bug reported: In bionic, apt upgrade should also autoremove by default. I have a few bionic systems (upgrades from xenial mostly) which are not yet showing that behaviour, it may be we haven't implemented that yet so this is just a placeholder bug in that case :) ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1734104 Title: 'upgrade' in bionic should by default autoremove as well Status in apt package in Ubuntu: New Bug description: In bionic, apt upgrade should also autoremove by default. I have a few bionic systems (upgrades from xenial mostly) which are not yet showing that behaviour, it may be we haven't implemented that yet so this is just a placeholder bug in that case :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1734104/+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
Re: [Touch-packages] [Bug 1512111] Re: "Ubuntu Light" font has heavier weight than "Ubuntu"
Confirmed, I am seeing this everywhere that local fonts are being used. I think it's a fontconfig or related regression. Mark -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-font-family-sources in Ubuntu. https://bugs.launchpad.net/bugs/1512111 Title: "Ubuntu Light" font has heavier weight than "Ubuntu" Status in One Hundred Papercuts: In Progress Status in Ubuntu Font Family: In Progress Status in ubuntu-font-family-sources package in Ubuntu: In Progress Status in ubuntu-font-family-sources source package in Wily: Triaged Bug description: After upgrading from Vivid to Wily, pages using the "Ubuntu light" font actually renders with a weight heavier than the regular one in web pages. This happens with Chrome/Chromium and also the Ubuntu browser. After manually reinstalling the 0.80-0ubuntu6 version from Vivid (in place of 0.83-0ubuntu1), the issue is fixed. See the attached screenshot showing the result seen browing https://www.google.com/fonts#UsePlace:use/Collection:Ubuntu ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ttf-ubuntu-font-family 0.83-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3 Uname: Linux 4.2.0-17-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 1 17:55:19 2015 Dependencies: InstallationDate: Installed on 2014-10-14 (382 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) PackageArchitecture: all SourcePackage: ubuntu-font-family-sources UpgradeStatus: Upgraded to wily on 2015-10-31 (0 days ago) IMPACT: Ubuntu Light font renders incorrectly for all 15.10 users which impacts the usability and visual design. The new version of font package (0.831) corrects the relationship between Light and Medium weight to follow the commonly used naming standards: Ubuntu Light Light Light Italic UbuntuRegular Italic BoldBold Italic Ubuntu Medium Medium Medium Italic Ubuntu Condensed Regular Ubuntu Mono Regular Italic BoldBold Italic TEST CASE: in 15.10, go to https://www.google.com/fonts#UsePlace:use/Collection:Ubuntu If the Light weight renders heavier than Normal weight, the bug is in place REGRESSION POTENTIAL 0.831 was tested by manually running in 15.10 and no regression was noticed, while the bug was fixed. The potential for regression is small. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1512111/+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 1727237] Re: systemd-resolved is not finding a domain
Yes, this is a captive portal situation on up-to-date 17.10. The captive portal popup fails with a DNS error looking for securelogin.arubanetworks.com and then hilarity ensues. Manually editing /etc/resolv.conf to use one of these DNS servers makes it all work. So the problem is systemd-resolved which is the default resolv.conf: ~$ cat /etc/resolv.conf # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search invitados It's all NM: ~$ cat /etc/netplan/01-network-manager-all.yaml # Let NetworkManager manage all devices on this system network: version: 2 renderer: NetworkManager Should /etc/resolv.conf be a symlink? libnss-resolve is not installed. systemd-resolve --status shows the two local DNS servers, as above. ~$ systemd-resolve --status | cat - 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 7 (wwp0s20f0u6i12) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 4 (wlp4s0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 208.67.222.222 208.67.220.220 DNS Domain: invitados Link 2 (enp0s31f6) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no -- 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/1727237 Title: systemd-resolved is not finding a domain Status in systemd package in Ubuntu: Incomplete Bug description: I have an odd network situation that I have so far managed to narrow down to the inability to resolve a domain via systemd-resolved which is resolvable with nslookup. If I use nslookup against the two nameservers on this network I get answers for the domain, but ping says it is unable to resolve the same domain (as do browsers and crucially the captive portal mechanism). Here are details: NSLOOKUP: ~$ nslookup securelogin.arubanetworks.com 208.67.220.220 Server: 208.67.220.220 Address: 208.67.220.220#53 Non-authoritative answer: Name: securelogin.arubanetworks.com Address: 172.22.240.242 ~$ nslookup securelogin.arubanetworks.com 208.67.222.222 Server: 208.67.222.222 Address: 208.67.222.222#53 Non-authoritative answer: Name: securelogin.arubanetworks.com Address: 172.22.240.242 PING: ~$ ping securelogin.arubanetworks.com ping: securelogin.arubanetworks.com: Name or service not known mark@mark-X1Y2:~$ DIG: ~$ dig @208.67.222.222 securelogin.arubanetworks.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;securelogin.arubanetworks.com. IN A ;; AUTHORITY SECTION: arubanetworks.com.1991IN SOA dns5.arubanetworks.com. hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400 ;; Query time: 34 msec ;; SERVER: 208.67.222.222#53(208.67.222.222) ;; WHEN: Wed Oct 25 10:31:10 CEST 2017 ;; MSG SIZE rcvd: 144 MORE DIG: ~$ dig securelogin.arubanetworks.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;;
[Touch-packages] [Bug 1727237] [NEW] systemd-resolved is not finding a domain
Public bug reported: I have an odd network situation that I have so far managed to narrow down to the inability to resolve a domain via systemd-resolved which is resolvable with nslookup. If I use nslookup against the two nameservers on this network I get answers for the domain, but ping says it is unable to resolve the same domain (as do browsers and crucially the captive portal mechanism). Here are details: NSLOOKUP: ~$ nslookup securelogin.arubanetworks.com 208.67.220.220 Server: 208.67.220.220 Address:208.67.220.220#53 Non-authoritative answer: Name: securelogin.arubanetworks.com Address: 172.22.240.242 ~$ nslookup securelogin.arubanetworks.com 208.67.222.222 Server: 208.67.222.222 Address:208.67.222.222#53 Non-authoritative answer: Name: securelogin.arubanetworks.com Address: 172.22.240.242 PING: ~$ ping securelogin.arubanetworks.com ping: securelogin.arubanetworks.com: Name or service not known mark@mark-X1Y2:~$ DIG: ~$ dig @208.67.222.222 securelogin.arubanetworks.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;securelogin.arubanetworks.com. IN A ;; AUTHORITY SECTION: arubanetworks.com. 1991IN SOA dns5.arubanetworks.com. hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400 ;; Query time: 34 msec ;; SERVER: 208.67.222.222#53(208.67.222.222) ;; WHEN: Wed Oct 25 10:31:10 CEST 2017 ;; MSG SIZE rcvd: 144 MORE DIG: ~$ dig securelogin.arubanetworks.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;securelogin.arubanetworks.com. IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Oct 25 10:34:01 CEST 2017 ;; MSG SIZE rcvd: 58 ** Affects: systemd (Ubuntu) Importance: Undecided 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://bugs.launchpad.net/bugs/1727237 Title: systemd-resolved is not finding a domain Status in systemd package in Ubuntu: New Bug description: I have an odd network situation that I have so far managed to narrow down to the inability to resolve a domain via systemd-resolved which is resolvable with nslookup. If I use nslookup against the two nameservers on this network I get answers for the domain, but ping says it is unable to resolve the same domain (as do browsers and crucially the captive portal mechanism). Here are details: NSLOOKUP: ~$ nslookup securelogin.arubanetworks.com 208.67.220.220 Server: 208.67.220.220 Address: 208.67.220.220#53 Non-authoritative answer: Name: securelogin.arubanetworks.com Address: 172.22.240.242 ~$ nslookup securelogin.arubanetworks.com 208.67.222.222 Server: 208.67.222.222 Address: 208.67.222.222#53 Non-authoritative answer: Name: securelogin.arubanetworks.com Address: 172.22.240.242 PING: ~$ ping securelogin.arubanetworks.com ping: securelogin.arubanetworks.com: Name or service not known mark@mark-X1Y2:~$ DIG: ~$ dig @208.67.222.222 securelogin.arubanetworks.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;securelogin.arubanetworks.com. IN A ;; AUTHORITY SECTION: arubanetworks.com.1991IN SOA dns5.arubanetworks.com. hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400 ;; Query time: 34 msec ;; SERVER: 208.67.222.222#53(208.67.222.222) ;; WHEN: Wed Oct 25 10:31:10 CEST 2017 ;; MSG SIZE rcvd: 144 MORE DIG: ~$ dig securelogin.arubanetworks.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;securelogin.arubanetworks.com. IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Oct 25 10:34:01 CEST 2017 ;; MSG SIZE rcvd: 58 To manage
Re: [Touch-packages] [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)
I think Andres has access to the GMAAS, would appreciate if he could
verify the fix there. If not, let me know and I can try it.
Thanks!
--
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:
=== Begin SRU Template ===
[Impact]
Without this fix applied, dns settings provided to the dhcp response
in the initramfs are not reflected in the "real root".
Thus dns resolution does not work. Of most interest was the MAAS use
case of the 'root=http://<>/squashfs' use case. MAAS 2.3 uses this for
the installation environment and also the rescue environment.
[Test Case]
There are two tests for this.
a.) local/non-MAAS test
Download the test case attached.
Run it and follow the instructions.
Login to the guest (ubuntu:password), and inspect /etc/resolv.conf
without the fix there would be no data in /etc/resolv.conf. With the
fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com'
b.) MAAS test.
For the full maas test, you need to build a image stream for maas
with the fix included in the squashfs image and then import that
stream to maas and use the rescue environment and verify dns.
This process is beyond the scope of the SRU template, but is
described partially in
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README
[Regression Potential]
Regression potential should be very low. There are gates in the code
to make sure that this code is inactive other than when it is explicitly
enabled.
net-interface-handler will exit without doing anything unless:
a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf
and these files have non-empty values for a variable mentioned above.
(These files are written by the initramfs code when 'ip=' is seen).
b.) this is not a container.
b.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
if open-iscsi has written this file due to open-iscsi root, then it
will handle this functionality. resolvconf will get out of the way.
c.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
This lowers the scope of changes in runtime to cases with where either the
new flag is seen or cloud-config-url is passed. The MAAS use case will
contain this flag.
[Other Info]
=== End SRU Template ===
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
[Touch-packages] [Bug 1723806] Re: 1.108ubuntu15.4 hangs on upgrade
I think it maybe that 15.3 had the issue, and 15.4 is OK. When I rebooted I was able to complete the 15.4 update, and another machine managed to do the 15.4 update without trouble. -- 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/1723806 Title: 1.108ubuntu15.4 hangs on upgrade Status in console-setup package in Ubuntu: New Bug description: There is an SRU for 1.108ubuntu15.4 in xenial-proposed that hangs for me on upgrade, causing updates to get stuck across the system. Haven't tracked it down further than that but wanted to report a bug quickly to prevent further promotion of the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1723806/+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
Re: [Touch-packages] [Bug 1650389] Re: Installing snapd on 14.04.5 desktop downgrades xorg et al.
On 15/12/16 17:25, Steve Langasek wrote:
> This was a known limitation when the SRU went through, and it was
> allowed because the understood target for snapd on 14.04 was
> server/cloud environments, not desktops. Has that changed?
It's unexpected for me, and will be substantially difficult to message
("install this but not on a desktop"). So I think we need to press on
this to understand it better. We do want snaps on 14.04, its a key part
of the value we're offering, but we can't make that a choice that
negatively impacts a desktop.
Mark
--
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/1650389
Title:
Installing snapd on 14.04.5 desktop downgrades xorg et al.
Status in Snappy:
Confirmed
Status in systemd package in Ubuntu:
Incomplete
Bug description:
When trying to install the latest snapd on a 14.04.5 desktop image,
the installation of systemd (as a dependency of snapd) triggers a
whole bunch of downgrades as systemd-shim is removed and replaced with
systemd.
We have to adjust the packaging such that installation of systemd does
not trigger such behavior for packages depending on systemd-shim in
trusty.
To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1650389/+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 1642966] [NEW] package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: This is in xenial-proposed, please block release to -updates accordingly :) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Fri Nov 18 11:13:15 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-05-02 (200 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: device for mallards-officejet-pro-8600: dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461 MachineType: Dell Inc. XPS 15 9550 Papersize: a4 PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check third-party-packages xenial -- 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/1642966 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: This is in xenial-proposed, please block release to -updates accordingly :) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Fri Nov 18 11:13:15 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-05-02 (200 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: device for mallards-officejet-pro-8600: dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461 MachineType: Dell Inc. XPS 15 9550 Papersize: a4 PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+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 1642932] [NEW] [2.1.3-4ubuntu0.1] package update failed from xenial-proposed
Public bug reported: Just saw this on update: Preparing to unpack .../cups-daemon_2.1.3-4ubuntu0.1_amd64.deb ... Job for cups.service canceled. invoke-rc.d: initscript cups, action "stop" failed. dpkg: warning: subprocess old pre-removal script returned error exit status 1 dpkg: trying script from the new package instead ... Job for cups.service canceled. invoke-rc.d: initscript cups, action "stop" failed. dpkg: error processing archive /var/cache/apt/archives/cups-daemon_2.1.3-4ubuntu0.1_amd64.deb (--unpack): subprocess new pre-removal script returned error exit status 1 ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- 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/1642932 Title: [2.1.3-4ubuntu0.1] package update failed from xenial-proposed Status in cups package in Ubuntu: New Bug description: Just saw this on update: Preparing to unpack .../cups-daemon_2.1.3-4ubuntu0.1_amd64.deb ... Job for cups.service canceled. invoke-rc.d: initscript cups, action "stop" failed. dpkg: warning: subprocess old pre-removal script returned error exit status 1 dpkg: trying script from the new package instead ... Job for cups.service canceled. invoke-rc.d: initscript cups, action "stop" failed. dpkg: error processing archive /var/cache/apt/archives/cups-daemon_2.1.3-4ubuntu0.1_amd64.deb (--unpack): subprocess new pre-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642932/+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
Re: [Touch-packages] [Bug 1611078] Re: Support snaps inside of lxd containers
Thanks guys, can't wait to see this in action :) Mark -- 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/1611078 Title: Support snaps inside of lxd containers Status in lxd: Unknown Status in Snappy: Fix Committed Status in apparmor package in Ubuntu: In Progress Status in linux package in Ubuntu: Fix Committed Status in lxd package in Ubuntu: Fix Committed Bug description: I tried following the instructions on snapcraft.io and got a failure. See the output below. I've also attached the relevant output from running "journalctl -xe". uname: Linux 3.19.0-65-generic x86_64 release: Ubuntu 16.04 package: snapd 2.11+0.16.04 Notably, I'm running this in an LXD container (version: 2.0.0.rc9). - $ sudo snap install hello-world 64.75 MB / 64.75 MB [==] 100.00 % 2.85 MB/s error: cannot perform the following tasks: - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See "systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for details. ) $ ls -la /snap total 4K drwxr-xr-x 3 root root 4096 Aug 8 17:49 ubuntu-core $ ls -la /snap/ubuntu-core/ total 4K drwxr-xr-x 2 root root 4096 Aug 8 17:49 122 $ ls -la /snap/ubuntu-core/122/ total 0K $ systemctl status "snap-ubuntu\\x2dcore-122.mount" ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min ago Where: /snap/ubuntu-core/122 What: /var/lib/snapd/snaps/ubuntu-core_122.snap Process: 31781 ExecMount=/bin/mount /var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs (code=exited, status=32) Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core... Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount failed: Unknown error -1 Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount process exited, code=exited status=32 Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for ubuntu-core. Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit entered failed state. To manage notifications about this bug go to: https://bugs.launchpad.net/lxd/+bug/1611078/+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
Re: [Touch-packages] [Bug 1624022] Re: Alias 'browse' to sensible-browser
Guys, the bug is to have the command "browse" DTRT. It sounds like xdg-open is TRT :) but please don't forget that the point is to get the command "browse" onto every ubuntu system. xdg-open is a lovely command for people who have a clue what xdg is. "browse " is what we want to tell our users to do. Mark -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sensible-utils in Ubuntu. https://bugs.launchpad.net/bugs/1624022 Title: Alias 'browse' to sensible-browser Status in sensible-utils package in Ubuntu: In Progress Bug description: The 'sensible-browser' command is very useful, but it's a bit unwieldy to use everywhere in docs. How about aliasing the simple 'browse' to sensible-browser, so I can recommend things like: sudo apt install foo; browse http://locahost:2022/ That would be crisp clean and friendly for current users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sensible-utils/+bug/1624022/+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 1624022] [NEW] Alias 'browse' to sensible-browser
Public bug reported: The 'sensible-browser' command is very useful, but it's a bit unwieldy to use everywhere in docs. How about aliasing the simple 'browse' to sensible-browser, so I can recommend things like: sudo apt install foo; browse http://locahost:2022/ That would be crisp clean and friendly for current users. ** Affects: sensible-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sensible-utils in Ubuntu. https://bugs.launchpad.net/bugs/1624022 Title: Alias 'browse' to sensible-browser Status in sensible-utils package in Ubuntu: New Bug description: The 'sensible-browser' command is very useful, but it's a bit unwieldy to use everywhere in docs. How about aliasing the simple 'browse' to sensible-browser, so I can recommend things like: sudo apt install foo; browse http://locahost:2022/ That would be crisp clean and friendly for current users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sensible-utils/+bug/1624022/+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 1594776] [NEW] add-apt-repository explodes on missing ppa
Public bug reported:
Just saw this on freshly updated Xenial. I think it's trying to be
helpful and tell me what PPAs a particular LP team has published, but in
the end it explodes:
$ sudo add-apt-repository ppa:juju/next
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 102, in
_get_https_content_py3
lp_page = urllib.request.urlopen(request, cafile=LAUNCHPAD_PPA_CERT)
File "/usr/lib/python3.5/urllib/request.py", line 162, in urlopen
return opener.open(url, data, timeout)
File "/usr/lib/python3.5/urllib/request.py", line 471, in open
response = meth(req, response)
File "/usr/lib/python3.5/urllib/request.py", line 581, in http_response
'http', request, response, code, msg, hdrs)
File "/usr/lib/python3.5/urllib/request.py", line 509, in error
return self._call_chain(*args)
File "/usr/lib/python3.5/urllib/request.py", line 443, in _call_chain
result = func(*args)
File "/usr/lib/python3.5/urllib/request.py", line 589, in http_error_default
raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 404: Not Found
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 327, in
get_ppa_info
ret = get_ppa_info_from_lp(user, ppa)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 92, in
get_ppa_info_from_lp
return get_info_from_lp(lp_url)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 88, in
get_info_from_lp
return _get_https_content_py3(lp_url)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 108, in
_get_https_content_py3
raise PPAException("Error reading %s: %s" % (lp_url, reason), e)
softwareproperties.ppa.PPAException: 'Error reading
https://launchpad.net/api/1.0/~juju/+archive/ubuntu/next: Not Found'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 393, in
shortcut_handler
return PPAShortcutHandler(shortcut)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 356, in
__init__
info = get_ppa_info(self.shortcut)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 339, in
get_ppa_info
_get_suggested_ppa_message(user, ppa))
softwareproperties.shortcuts.ShortcutException: Cannot add PPA:
'ppa:~juju/ubuntu/next'.
The team named '~juju' has no PPA named 'ubuntu/next'
Please choose from the following available PPAs:
* '1.22': 1.22 Updates
* '1.22-proposed': 1.22 Proposed
* '1.23': 1.23 Updates
* 'daily': Juju Daily
* 'devel': juju devel packages
* 'enablement': Juju Enablement
* 'experimental': juju experimental packages
* 'golang': juju-golang
* 'proposed': juju proposed packages
* 'stable': juju stable packages
Error: 'ppa:juju/next' invalid
** Affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1594776
Title:
add-apt-repository explodes on missing ppa
Status in software-properties package in Ubuntu:
New
Bug description:
Just saw this on freshly updated Xenial. I think it's trying to be
helpful and tell me what PPAs a particular LP team has published, but
in the end it explodes:
$ sudo add-apt-repository ppa:juju/next
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 102,
in _get_https_content_py3
lp_page = urllib.request.urlopen(request, cafile=LAUNCHPAD_PPA_CERT)
File "/usr/lib/python3.5/urllib/request.py", line 162, in urlopen
return opener.open(url, data, timeout)
File "/usr/lib/python3.5/urllib/request.py", line 471, in open
response = meth(req, response)
File "/usr/lib/python3.5/urllib/request.py", line 581, in http_response
'http', request, response, code, msg, hdrs)
File "/usr/lib/python3.5/urllib/request.py", line 509, in error
return self._call_chain(*args)
File "/usr/lib/python3.5/urllib/request.py", line 443, in _call_chain
result = func(*args)
File "/usr/lib/python3.5/urllib/request.py", line 589, in http_error_default
raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 404: Not Found
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 327,
in get_ppa_info
ret = get_ppa_info_from_lp(user, ppa)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 92,
in get_ppa_info_from_lp
return get_info_from_lp(lp_url)
File
Re: [Touch-packages] [Bug 762349] Update Released
Just wanted to say thanks for this fix, I will appreciate it every day :) Mark -- 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/762349 Title: [SRU] Difficult to distinguish which tab is selected Status in Ayatana Design: Fix Committed Status in Ubuntu theme: Fix Released Status in ubuntu-themes package in Ubuntu: Fix Released Status in ubuntu-themes source package in Xenial: Fix Released Bug description: [Impact] * When a user opens multiple tabs in GNOME terminal all tabs are styled in a *very* visually similar manner. This makes it very hard to distinguish between the current active tab and all the others and on a HiDPI screen pretty much impossible. * This fix has been ack'd by design and was targeted for X but didn't get reviewed and OK'd in time. Design team have approved this styling. * This bug is fixed by extending the CSS specifically for Terminal (i.e. no other applications are affected) giving the active tab a darker background colour (using only theme defined colours) and reworks the borders around the tabs to remove the graduated image borders that only look right on a light coloured background. Changes have been made for both Ambiance and Radiance. [Test Case] * On a stock 16.04 install open GNOME Terminal (ctrl-alt-t) * Open five new tabs (ctrl-shift-t) * Click on the tab in the middle * Note that it is hard to see at a glance which tab is currently selected * Close Terminal and all open tabs. * Install the patched theme * Open Terminal and open five new tabs * Click on the tab in the middle and note that it takes on a light grey background compared to the unselected tabs which are dark grey. [Regression Potential] * The patch only addresses tabs that are placed at the top of the window. However this is the only option in Terminal, so should not cause any problems. * There is a work-around to match the "actions bar" (the bit with the dropdown selector and + button). This bug is supposed to be fixed in v3.20 and could be removed. This is commented in the CSS. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/762349/+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
Re: [Touch-packages] [Bug 762349] Re: Difficult to distinguish which tab is selected
Oh god yes please! -- 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/762349 Title: Difficult to distinguish which tab is selected Status in Ayatana Design: New Status in Ubuntu theme: In Progress Status in ubuntu-themes package in Ubuntu: In Progress Status in ubuntu-themes source package in Xenial: In Progress Bug description: Binary package hint: unity In tabbed interfaces such as in gnome-terminal under unity it is difficult to visually distinguish the selected tab from the unselected ones. In the attached screenshot, gnome-terminal has three tabs open, and the third one is selected. If you look close you can see the text is slightly whiter than the other tabs, and the border is a little more prominent but to my old man eyes it's really hard to see it at a glance. Under metacity, the difference is more notable (or at least, the theme is different). My guess is this is a theme issue rather than unity, but I'm unsure. If it is just a theme issue please refile to the right project. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: unity 3.8.8-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2 Uname: Linux 2.6.38-8-generic-pae i686 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,scale,session,unityshell] Date: Fri Apr 15 17:41:12 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=C SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to natty on 2011-04-04 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/762349/+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 1577215] [NEW] Origin pattern is unexpected on dpkg-reconfigure
Public bug reported:
In testing out the new unattended-upgrades behaviour I was asked an
unexpected question about the "unattended-upgrades Origin-Pattern". This
is not a great experience, it doesn't match anything other than internal
code patterns.
For example, the default offered does NOT look like a sensible Ubuntu
default for Ubuntu users:
"origin=Debian,codename=${distro_codename},label=Debian-Security";___
Is that correct, or a mistake?
What I would expect is simply this:
Install security updates (Y/N)
Install performance and reliability updates (Y/N)
Install updates from unofficial archives (Y/N)
The latter would map to all PPAs etc.
** Affects: unattended-upgrades (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1577215
Title:
Origin pattern is unexpected on dpkg-reconfigure
Status in unattended-upgrades package in Ubuntu:
New
Bug description:
In testing out the new unattended-upgrades behaviour I was asked an
unexpected question about the "unattended-upgrades Origin-Pattern".
This is not a great experience, it doesn't match anything other than
internal code patterns.
For example, the default offered does NOT look like a sensible Ubuntu
default for Ubuntu users:
"origin=Debian,codename=${distro_codename},label=Debian-
Security";___
Is that correct, or a mistake?
What I would expect is simply this:
Install security updates (Y/N)
Install performance and reliability updates (Y/N)
Install updates from unofficial archives (Y/N)
The latter would map to all PPAs etc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1577215/+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
Re: [Touch-packages] [Bug 1564832] Re: Apparmor profile for NTPd needs to allow read/write access to /dev/ppsX
Hi Jamie - whatever you think is the best approach to have this work out of the box for other Ubuntu users installing NTP and setting up a PPS device. All I care about is that they don't have to edit apparmor profiles themselves. Mark -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1564832 Title: Apparmor profile for NTPd needs to allow read/write access to /dev/ppsX Status in ntp package in Ubuntu: Triaged Bug description: Am trying to get NTP to work with the kernel PPS subsystem, for high- accuracy GPS-based clocks. On startup of NTPd I see this: Apr 1 11:18:58 doorway kernel: [ 300.387443] audit: type=1400 audit(1459505938.042:9): apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" name="/dev/pps0" pid=1668 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 Adding this to the usr.sbin.ntpd apparmor profile eliminated the error: /dev/pps[0-9]* rw, I'm not sure why ntpd needs *write* access to ppsN though, perhaps that can be improved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1564832/+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 1564832] [NEW] Apparmor profile for NTPd needs to allow read/write access to /dev/ppsX
Public bug reported: Am trying to get NTP to work with the kernel PPS subsystem, for high- accuracy GPS-based clocks. On startup of NTPd I see this: Apr 1 11:18:58 doorway kernel: [ 300.387443] audit: type=1400 audit(1459505938.042:9): apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" name="/dev/pps0" pid=1668 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 Adding this to the usr.sbin.ntpd apparmor profile eliminated the error: /dev/pps[0-9]* rw, I'm not sure why ntpd needs *write* access to ppsN though, perhaps that can be improved. ** Affects: ntp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1564832 Title: Apparmor profile for NTPd needs to allow read/write access to /dev/ppsX Status in ntp package in Ubuntu: New Bug description: Am trying to get NTP to work with the kernel PPS subsystem, for high- accuracy GPS-based clocks. On startup of NTPd I see this: Apr 1 11:18:58 doorway kernel: [ 300.387443] audit: type=1400 audit(1459505938.042:9): apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" name="/dev/pps0" pid=1668 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 Adding this to the usr.sbin.ntpd apparmor profile eliminated the error: /dev/pps[0-9]* rw, I'm not sure why ntpd needs *write* access to ppsN though, perhaps that can be improved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1564832/+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
Re: [Touch-packages] [Bug 1512980] Re: Please enable PPS in the Ubuntu build of ntpd
Thanks Robie, excited to take it for a spin :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1512980 Title: Please enable PPS in the Ubuntu build of ntpd Status in ntp package in Ubuntu: Fix Committed Bug description: NTPD includes a reference clock driver called "pps" which uses a modern kernel mechanism for pulse-per-second devices for very accurate timekeeping. PPS is particularly useful for anybody building a stratum 0 GPS-disciplined time server. Please could we enable the PPS driver in Ubuntu's build of NTP? http://doc.ntp.org/4.2.6/drivers/driver22.html Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1512980/+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 1512980] Re: Please enable PPS in the Ubuntu build of ntpd
Thanks kick-d :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1512980 Title: Please enable PPS in the Ubuntu build of ntpd Status in ntp package in Ubuntu: In Progress Bug description: NTPD includes a reference clock driver called "pps" which uses a modern kernel mechanism for pulse-per-second devices for very accurate timekeeping. PPS is particularly useful for anybody building a stratum 0 GPS-disciplined time server. Please could we enable the PPS driver in Ubuntu's build of NTP? http://doc.ntp.org/4.2.6/drivers/driver22.html Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1512980/+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
Re: [Touch-packages] [Bug 861334] Re: [nc] Ship Ubuntu Mono .psf as default console font in Ubuntu 11.10
On 17/12/15 04:51, Christopher Kyle Horton wrote:
> Is there a chance this bug could be revisited for 16.04 LTS?
I just tried it and thought it didn't look very good at low resolutions,
perhaps I tried the wrong version (I am on Xenial). I don't think we had
the font specifically optimised for the sort so 8x13 - 8x18 resolutions
used by console fonts, and of course there is no such thing as hinting.
Can anybody else weigh on on the merits?
Mark
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-font-family-sources
in Ubuntu.
https://bugs.launchpad.net/bugs/861334
Title:
[nc] Ship Ubuntu Mono .psf as default console font in Ubuntu 11.10
Status in ubuntu-font-family-sources package in Ubuntu:
Confirmed
Bug description:
Further to bug #724022 ("Wishlist: Enable use of Ubuntu Mono as .psf
console-setup font"), Mark Shuttleworth requested that that Ubuntu
Mono bitmaps be used as the default Ubuntu Mono font for console use
in Ubuntu 11.10.
" fonts-ubuntu-font-family-console … needs to be a dep of
'ubuntu-standard', and the default mono font for 11.10 please"
Ubuntu 11.10 Hard Freeze is in 32 hours time. This would require:
1. Upstream release of Ubuntu Font Family 0.80. A release candidate has
been out for a couple of days with no reports of show stoppers
(https://launchpad.net/ubuntu-font-family/+milestone/0.80)
2. Distro upload of Ubutu Font Family 0.80 minus Medium for oneiric
3. Accepting 'fonts-ubuntu-font-family-console' binary (built from the same
source) into universe
4. Promoting 'fonts-ubuntu-font-family-console' to main
5. MIR for 'otf2bdf'
6. MIR for 'bdf2psf'
7. Adjusting of seeds to add 'fonts-ubuntu-font-family-console' to
'ubuntu-standard'
8. Increasing CD/Image size by 18 kB in all cases. (By not building
Italic/Bold Italic this would decrease to ~10 kB)
This would get 'consolefonts' installed, but would require users to
manually install it. This would not require changes to screenshots or
documentation adjusts as nothing in the default has changed. To
subsequently set as default would require:
9. '/var/lib/dpkg/info/console-setup.config' adjustments; the desired font
capacity is limited; this sets the particular subset for
Latin/Greek/Cyrillic/Arabic etc. We cannot replace all of these.
10. We don't have sufficient glyph coverage to replace all of these.
11. The snapshot of the hinted Ubuntu Mono fonts from Vincent
Connare/Dalton Maag on 2011-09-22 are a vast improvement, but are still a work
in progress.
12. Regenerating Ubuntu server screenshots
13. Adjusting documentation slightly, although likely minor
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/861334/+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
Re: [Touch-packages] [Bug 1512980] Re: Please enable PPS in the Ubuntu build of ntpd
Thank you Christian! Let's go with 4.2.8 for all the obvious reasons, get it done in Ubuntu and offer up the patch to Debian. Mark -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1512980 Title: Please enable PPS in the Ubuntu build of ntpd Status in ntp package in Ubuntu: New Bug description: NTPD includes a reference clock driver called "pps" which uses a modern kernel mechanism for pulse-per-second devices for very accurate timekeeping. PPS is particularly useful for anybody building a stratum 0 GPS-disciplined time server. Please could we enable the PPS driver in Ubuntu's build of NTP? http://doc.ntp.org/4.2.6/drivers/driver22.html Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1512980/+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
Re: [Touch-packages] [Bug 762349] Re: Difficult to distinguish which tab is selected
Man, this is a favourite bug of mine, would be DELIGHTED to see a fix in Wily ;) Mark -- 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/762349 Title: Difficult to distinguish which tab is selected Status in Ayatana Design: New Status in Ubuntu theme: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Binary package hint: unity In tabbed interfaces such as in gnome-terminal under unity it is difficult to visually distinguish the selected tab from the unselected ones. In the attached screenshot, gnome-terminal has three tabs open, and the third one is selected. If you look close you can see the text is slightly whiter than the other tabs, and the border is a little more prominent but to my old man eyes it's really hard to see it at a glance. Under metacity, the difference is more notable (or at least, the theme is different). My guess is this is a theme issue rather than unity, but I'm unsure. If it is just a theme issue please refile to the right project. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: unity 3.8.8-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2 Uname: Linux 2.6.38-8-generic-pae i686 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,scale,session,unityshell] Date: Fri Apr 15 17:41:12 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110202) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=C SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to natty on 2011-04-04 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/762349/+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 1446256] Re: Default out of the box menu option should be set to Global Menus
Ack, thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1446256
Title:
Default out of the box menu option should be set to Global Menus
Status in Unity:
In Progress
Status in unity package in Ubuntu:
New
Bug description:
Change request: the default out of the box menu option should be
global menus ('menus in the menu bar')
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1446256/+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 1355813] Re: Interface MTU management across MAAS/juju
Do we need to take into account any overhead being added by the protocol stack along the way? For example, if the underlying MAAS machine can be told to use 9000 byte MTUs and jumbo frames, then each layer up could adopt that, but might need to chop off some of that for protocol / tunnel / encapsulation overhead. I've seen cases where your internal interface needs to have, say 20 byte smaller MTUs than the host. Perhaps THAT's the bit that we should focus on specifying. So MAAS gets told just jumbo frames here and then everything else focuses on understanding and allowing for overhead, but maximising MTU subject to that overhead. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1355813 Title: Interface MTU management across MAAS/juju Status in juju-core: Fix Released Status in MAAS: Triaged Status in juju-core package in Ubuntu: Triaged Status in lxc package in Ubuntu: Invalid Bug description: Context: juju + MAAS deployed OpenStack environment, misc services deployed under LXC on the bootstrap node, interfaces configured for jumbo frames - note that I had to manually set the LXC container interfaces to mtu 9000 before the bridge would do the same. Action: Reboot one of the containers; MTU on br0 resets from 9000 - 1500. This feels like more of a 'we need a better way to orchestrate MTU configuration across different services' so raising tasks for MAAS and Juju as well. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.5-0ubuntu0.1 ProcVersionSignature: User Name 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Tue Aug 12 13:26:00 2014 KernLog: SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx lxcsyslog: To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+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 1419405] Re: indicator-location-service crashed with SIGABRT in internal::ToBackend::exit_module()
Hi folks, this is a crash on startup that creates a bad impression of the desktop. Is it a particularly complex fix? Mark -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1419405 Title: indicator-location-service crashed with SIGABRT in internal::ToBackend::exit_module() Status in indicator-location package in Ubuntu: Confirmed Bug description: :( ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-location 13.10.0+14.10.20141007-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4 Uname: Linux 3.18.0-12-generic x86_64 ApportVersion: 2.16-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Thu Feb 5 06:11:38 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-location/indicator-location-service InstallationDate: Installed on 2014-10-13 (117 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141012) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-location/indicator-location-service ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/false Signal: 6 SourcePackage: indicator-location StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ua_location_service_create_controller () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 UbuntuAppLocController::UbuntuAppLocController() () SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown Title: indicator-location-service crashed with SIGABRT in ua_location_service_create_controller() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1419405/+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 1419685] [NEW] indicator-location-service crashed with SIGABRT in ua_location_service_create_controller()
Public bug reported: Seems to happen very often. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-location 13.10.0+14.10.20141007-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4 Uname: Linux 3.18.0-12-generic x86_64 ApportVersion: 2.16-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sun Feb 8 09:58:30 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-location/indicator-location-service InstallationDate: Installed on 2013-11-27 (437 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131126) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-location/indicator-location-service ProcEnviron: PATH=(custom, no user) LANGUAGE=en_GB:en XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/false Signal: 6 SourcePackage: indicator-location StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ua_location_service_create_controller () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 UbuntuAppLocController::UbuntuAppLocController() () SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown Title: indicator-location-service crashed with SIGABRT in ua_location_service_create_controller() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: indicator-location (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace third-party-packages vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1419685 Title: indicator-location-service crashed with SIGABRT in ua_location_service_create_controller() Status in indicator-location package in Ubuntu: New Bug description: Seems to happen very often. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-location 13.10.0+14.10.20141007-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4 Uname: Linux 3.18.0-12-generic x86_64 ApportVersion: 2.16-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sun Feb 8 09:58:30 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-location/indicator-location-service InstallationDate: Installed on 2013-11-27 (437 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131126) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-location/indicator-location-service ProcEnviron: PATH=(custom, no user) LANGUAGE=en_GB:en XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/false Signal: 6 SourcePackage: indicator-location StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ua_location_service_create_controller () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 UbuntuAppLocController::UbuntuAppLocController() () SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown Title: indicator-location-service crashed with SIGABRT in ua_location_service_create_controller() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1419685/+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
Re: [Touch-packages] [Bug 1355284] Re: Switching swipe directions should reverse app spread
Thanks all! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1355284 Title: Switching swipe directions should reverse app spread Status in the base for Ubuntu mobile products: In Progress Status in Ubuntu UX bugs: Fix Committed Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: Fix Released Bug description: The new app spread is gorgeous, thank you! In general we try to ensure reversibility of transitions - if a user starts a gesture and changes their mind they should be able to reverse the gesture and exit the transition as long as they have not lifted their finger. In this case, a user swiping from the right who intends to toggle windows but overshoots (thereby entering the spread) should be able to change direction, move their finger back towards the right edge, returning to the toggle and then to the original app if they move their finger all the way off the right edge. --- Desired solution User should be in control through the whole the gesture. We want to have reversibility also after second commit point the same way we have for the first commit point in current implementation. This has now been captured also in the right edge documentation: https://docs.google.com/a/canonical.com/document/d/1FC_- 5yz5kPy_ZvTphaqxOgI5BPnALFbxRAO4eJkzlf8/edit# To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1355284/+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 1380044] [NEW] Welcome screen should be visible immediately when screen is activated
Public bug reported: When locking my device with the power button, and then activating it, I briefly see the previously-surfaced application before the welcome screen is drawn over that. What should happen is that activating the screen shows the welcome screen instantly. I suspect we need to draw the welcome screen when then button is pressed, and fade-out the screen to black. This way, the welcome screen is already in place when we turn the screen on again. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1380044 Title: Welcome screen should be visible immediately when screen is activated Status in “unity8” package in Ubuntu: New Bug description: When locking my device with the power button, and then activating it, I briefly see the previously-surfaced application before the welcome screen is drawn over that. What should happen is that activating the screen shows the welcome screen instantly. I suspect we need to draw the welcome screen when then button is pressed, and fade-out the screen to black. This way, the welcome screen is already in place when we turn the screen on again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380044/+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 1380100] [NEW] Screen should darken as launcher is revealed
Public bug reported: When the left edge launcher is revealed over an app or a scope other than the apps scope, the app should darken smoothly and proportionately to the revealing movement of the launcher. At the moment, the screen darkens after the launcher is fully committed. Instead the degree of darkening of the screen should be correlated to the extent of the launcher reveal. As the launcher is hinted, the screen should darken a little, and as it is revealed the rest of the darkening should happen, till the commit at which point the app / screen is at the final level of darkening. If the left edge swipe continues then we expect to reveal the app scope, which would be undimmed and hence contrast strongly with the app (or other scope) that was visible. This will serve to strengthen the hint / reveal of the launcher, and also to highlight the emergence of the app scope. It also matches the immediate dimming of the screen during a right-edge swipe. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1380100 Title: Screen should darken as launcher is revealed Status in “unity8” package in Ubuntu: New Bug description: When the left edge launcher is revealed over an app or a scope other than the apps scope, the app should darken smoothly and proportionately to the revealing movement of the launcher. At the moment, the screen darkens after the launcher is fully committed. Instead the degree of darkening of the screen should be correlated to the extent of the launcher reveal. As the launcher is hinted, the screen should darken a little, and as it is revealed the rest of the darkening should happen, till the commit at which point the app / screen is at the final level of darkening. If the left edge swipe continues then we expect to reveal the app scope, which would be undimmed and hence contrast strongly with the app (or other scope) that was visible. This will serve to strengthen the hint / reveal of the launcher, and also to highlight the emergence of the app scope. It also matches the immediate dimming of the screen during a right-edge swipe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380100/+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 1359590] Re: Getty's on serial consoles need to be consistent
Not sure if this should also be tracked against the cloud image builder. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1359590 Title: Getty's on serial consoles need to be consistent Status in Init scripts for use on cloud images: New Status in “util-linux” package in Ubuntu: New Bug description: In our cloud images today we launch a getty on ttyS0, as long as it's not in a container. We don't launch a getty on ttyS1-n even if they exist. In MAAS, which also uses cloud images, it would often be useful to put getty's on the serial port that is mapped to remote serial access, such as IPMI SOL. It is however difficult to know which is the correct getty. Broadly speaking I think we should have a consistent approach to getty's. That might mean: * launch a getty on each ttySn that passes an stty test (as per ttyS0 currently) * allow cloud-init to prevent some of those, via vendordata or userdata or default behaviour per-cloud or * launch no getty's on ttyS, but * allow cloud-init to create them based on vendordata or userdata or default behaviour per-cloud To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1359590/+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 1359590] [NEW] Getty's on serial consoles need to be consistent
Public bug reported: In our cloud images today we launch a getty on ttyS0, as long as it's not in a container. We don't launch a getty on ttyS1-n even if they exist. In MAAS, which also uses cloud images, it would often be useful to put getty's on the serial port that is mapped to remote serial access, such as IPMI SOL. It is however difficult to know which is the correct getty. Broadly speaking I think we should have a consistent approach to getty's. That might mean: * launch a getty on each ttySn that passes an stty test (as per ttyS0 currently) * allow cloud-init to prevent some of those, via vendordata or userdata or default behaviour per-cloud or * launch no getty's on ttyS, but * allow cloud-init to create them based on vendordata or userdata or default behaviour per-cloud ** Affects: cloud-init Importance: Undecided Status: New ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Also affects: cloud-init Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1359590 Title: Getty's on serial consoles need to be consistent Status in Init scripts for use on cloud images: New Status in “util-linux” package in Ubuntu: New Bug description: In our cloud images today we launch a getty on ttyS0, as long as it's not in a container. We don't launch a getty on ttyS1-n even if they exist. In MAAS, which also uses cloud images, it would often be useful to put getty's on the serial port that is mapped to remote serial access, such as IPMI SOL. It is however difficult to know which is the correct getty. Broadly speaking I think we should have a consistent approach to getty's. That might mean: * launch a getty on each ttySn that passes an stty test (as per ttyS0 currently) * allow cloud-init to prevent some of those, via vendordata or userdata or default behaviour per-cloud or * launch no getty's on ttyS, but * allow cloud-init to create them based on vendordata or userdata or default behaviour per-cloud To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1359590/+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
