[Touch-packages] [Bug 1349566] [NEW] systemd-logind triggered poweroffs ignore upstart services

Public bug reported: systemd-logind has a facility to detect non-ACPI power-off events (e.g. a power button push) and initiate a system shutdown. This facility works in Ubuntu - it manages to shutdown the sysvinit services, but upstart services do not appear to be cleanly shutdown. Among other

Re: [Touch-packages] [Bug 1349566] Re: systemd-logind triggered poweroffs ignore upstart services

On Mon, Jul 28, 2014 at 3:46 PM, Steve Langasek steve.langa...@canonical.com wrote: Dann, what upstart services fail to be shut down? The last messages shown in your log are from /etc/init.d/sendsigs and /etc/init.d/reboot, which on an upstart system are only ever called via /etc/init/rc.conf,

[Touch-packages] [Bug 1349566] Re: systemd-logind triggered poweroffs ignore upstart services

You're right, it is calling /sbin/poweroff, I made a wrapper to see what was going on there as you suggested. While using the wrapper (to prevent an actual poweroff), I noticed: - 'udevadm monitor -e' logs no events - No arguments are supplied to /sbin/poweroff - '/sbin/poweroff' gets called

[Touch-packages] [Bug 1349566] Re: systemd-logind triggered poweroffs ignore upstart services

As you mentioned in IRC, this is probably just documented behavior. From reboot(8): When called with --force or when in runlevel 0 or 6, this tool invokes the reboot(2) system call itself (with REBOOTCOMMAND argument passed) and directly reboots the system. Otherwise

[Touch-packages] [Bug 1354306] Re: gpio shutdown trigger for ProLiant m400 cartridges

** Patch added: patch for trusty's systemd https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1354306/+attachment/4172770/+files/trusty.patch ** Description changed: Similar to the m800 case in LP: #1347776, udev/systemd also needs to know how to trigger a graceful shutdown on

[Touch-packages] [Bug 1354306] Re: gpio shutdown trigger for ProLiant m400 cartridges

** Bug watch added: freedesktop.org Bugzilla #82347 https://bugs.freedesktop.org/show_bug.cgi?id=82347 ** Also affects: systemd via https://bugs.freedesktop.org/show_bug.cgi?id=82347 Importance: Unknown Status: Unknown -- You received this bug notification because you are a

[Touch-packages] [Bug 1347776] Re: shutdown trigger on gpio_keys.X for armhf hardware

** Bug watch added: freedesktop.org Bugzilla #82347 https://bugs.freedesktop.org/show_bug.cgi?id=82347 ** Also affects: systemd via https://bugs.freedesktop.org/show_bug.cgi?id=82347 Importance: Unknown Status: Unknown -- You received this bug notification because you are a

[Touch-packages] [Bug 1354306] Re: gpio shutdown trigger for ProLiant m400 cartridges

The vendor has requested we use the string gpio_keys instead of gpio- keys to match current convention. Updated patches attached. ** Patch added: updated patch for utopic https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1354306/+attachment/4174681/+files/utopic.patch -- You received

[Touch-packages] [Bug 1354306] Re: gpio shutdown trigger for ProLiant m400 cartridges

** Patch added: updated patch for trusty https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1354306/+attachment/4174680/+files/trusty.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1354306]

Note that, due to a firmware change, the m400 rule should use gpio_keys instead of gpio-keys. Here is the new rule: SUBSYSTEM==input, KERNEL==event*, SUBSYSTEMS==platform, KERNELS==gpio_keys.6, PROGRAM=/bin/grep '^HP ProLiant m400 Server Cartridge$' /proc/device-tree/model, TAG+=power-switch --

[Touch-packages] [Bug 1347776]

Right, that wasn't intended to be an upstream patch submittal, just a description of the problem. My best guess at a good solution would be something like this: SUBSYSTEM==input, KERNEL==event*, SUBSYSTEMS==platform, ATTRS{keys}==116, TAG+=power-switch Which would obviously require some new

[Touch-packages] [Bug 1354306]

Right, that wasn't intended to be an upstream patch submittal, just a description of the problem. My best guess at a good solution would be something like this: SUBSYSTEM==input, KERNEL==event*, SUBSYSTEMS==platform, ATTRS{keys}==116, TAG+=power-switch Which would obviously require some new

[Touch-packages] [Bug 1354306] Re: gpio shutdown trigger for ProLiant m400 cartridges

Martin, Thanks for the review. This squashes the proliant support patches into one and uses the RESULT== format consistently. This patch is against trusty, but you should be able to use the included ProLiant-power-button.patch patch directly in utopic. It is true that trusty is more

[Touch-packages] [Bug 1354306] Re: gpio shutdown trigger for ProLiant m400 cartridges

** Tags removed: verification-needed ** Tags added: verification-done -- 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/1354306 Title: gpio shutdown trigger for ProLiant

[Touch-packages] [Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

** No longer affects: gccgo-5 (Ubuntu Trusty) ** Also affects: gcc-5 (Ubuntu) Importance: Undecided Status: New ** No longer affects: gccgo-5 (Ubuntu Wily) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gccgo-4.9

[Touch-packages] [Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

** Summary changed: - [arm64] lxd crashes on startup + [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4 ** Package changed: lxd (Ubuntu) = gcc-4.9 (Ubuntu) ** Changed in: gcc-4.9 (Ubuntu) Status: New = Confirmed ** Also affects: gcc-4.8 (Ubuntu) Importance: Undecided

[Touch-packages] [Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

** Also affects: gcc-4.8 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: gcc-4.9 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: gcc-4.8 (Ubuntu Wily) Importance: Undecided Status: Confirmed ** Also affects: gcc-4.9 (Ubuntu

[Touch-packages] [Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

** No longer affects: gcc-4.8 (Ubuntu Trusty) ** No longer affects: gcc-4.8 (Ubuntu Wily) ** No longer affects: gcc-4.8 (Ubuntu Vivid) ** No longer affects: gcc-4.9 (Ubuntu Trusty) ** No longer affects: gcc-4.9 (Ubuntu Vivid) ** No longer affects: gcc-4.9 (Ubuntu Wily) -- You received this

[Touch-packages] [Bug 1353729] Re: [4.9 Regression] ICE in final_scan_insn, at final.c:2952 (aarch64-linux-gnu)

The gcc-4.8 SRU in trusty from 4.8.2-19ubuntu1 - 4.8.4-2ubuntu1~14.04 has introduced this regression, causing mysql-5.6 to now FTBFS. I've confirmed that this bug also persists in gcc-4.8 in wily today (4.8.4-3ubuntu1). ** Also affects: gcc-4.8 (Ubuntu) Importance: Undecided Status: New

[Touch-packages] [Bug 1508577] Re: [wily] installing juju-local on ARM64 failed. broken apt dependency

fwiw, this isn't a general arm64 problem. I can install juju-local on a mustang running wily w/o a problem. I suspect it maybe due to using a custom kernel, possibly with some networking features disabled in the config. I've asked Manoj to set -x /usr/lib/aarch64-linux-gnu/lxc/lxc- net to see if

[Touch-packages] [Bug 1513958] Re: arm64: failure with small objects passed on stack

** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libffi in Ubuntu. https://bugs.launchpad.net/bugs/1513958 Title: arm64: failure with small objects

[Touch-packages] [Bug 1513958] [NEW] arm64: failure with small objects passed on stack

en triaged to libffi in those releases. ** Affects: libffi (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: libffi (Ubuntu Trusty) Importance: Medium Assignee: dann frazier (dannf) Status: In Progress ** Also affects: libffi (Ubuntu Trusty)

[Touch-packages] [Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

** Also affects: gcc via https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67508 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gccgo-4.9 in Ubuntu.

[Touch-packages] [Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

** Changed in: gccgo-4.9 (Ubuntu Vivid) Status: New => In Progress ** Changed in: gccgo-4.9 (Ubuntu Trusty) Status: Confirmed => Invalid ** Changed in: gccgo-4.9 (Ubuntu Trusty) Status: Invalid => In Progress ** Changed in: gccgo-4.9 (Ubuntu Vivid) Status: In

[Touch-packages] [Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

** Description changed: - lxd 0.12-0ubuntu2 - libgo7/5.1.1-12ubuntu1 + [Impact] + Various go-based packages crash on startup on arm64 when booted with a kernel where CONFIG_ARM64_PGTABLE_LEVELS=4. LXD, docker and juju are examples. - Jul 08 00:11:16 vital-beggar systemd[1]: Starting Container

[Touch-packages] [Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

= vivid verification = # My kernel has the problematic config ubuntu@cvm1:~$ grep CONFIG_ARM64_PGTABLE_LEVELS /boot/config-$(uname -r) CONFIG_ARM64_PGTABLE_LEVELS=4 # Build a clean vivid chroot ubuntu@cvm1:~$ mkdir lp1472650 ubuntu@cvm1:~$ sudo debootstrap --components 'main,universe' --include

[Touch-packages] [Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

Verified: ubuntu@cvm2s:~$ juju help p=0xa6947000 fatal error: runtime_lfstackpush: invalid pointer runtime stack: :0 :0 :0 :0 :0 :0 :0 :0 :0 :0 goroutine 1 [garbage collection]:

[Touch-packages] [Bug 1588946] [NEW] Support booting from ehci-msm attached storage

and reboot. Booting will fail because it will be unable to find the root file system. [Regression Risk] This driver is only available on ARM platforms, minimizing the impact to all other architectures. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf

[Touch-packages] [Bug 1588946] Re: Support booting from ehci-msm attached storage

ned) => Manoj Iyer (manjo) ** Changed in: initramfs-tools (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bug

[Touch-packages] [Bug 1588946] Re: Support root on ehci-msm attached storage

** Summary changed: - Support booting from ehci-msm attached storage + Support root on ehci-msm attached storage -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.

[Touch-packages] [Bug 1588020] Re: package linux-image-4.4.0-22-generic 4.4.0-22.40 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

You appear to have run out of disk space: gzip: stdout: No space left on device Can you free up some space and retry? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.

[Touch-packages] [Bug 1588946] Re: Support root on ehci-msm attached storage

** Changed in: initramfs-tools (Ubuntu Xenial) Status: Confirmed => In Progress ** Changed in: initramfs-tools (Ubuntu Xenial) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages,

[Touch-packages] [Bug 1594452] Re: Add vulcan support

** Project changed: gcc => gcc-6 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1594452 Title: Add vulcan support Status in binutils package in Ubuntu:

[Touch-packages] [Bug 1594452] Re: Add vulcan support

GCC support is upstream now; backport attached. ** Changed in: gcc-6 (Ubuntu) Status: New => Confirmed ** Changed in: gcc-6 (Ubuntu) Importance: Undecided => Medium ** Patch added: "gcc-6-vulcan-support.patch"

[Touch-packages] [Bug 1594452] [NEW] Add vulcan support

Public bug reported: Vulcan support has recently landed upstream. Please include this backport in Ubuntu. ** Affects: binutils (Ubuntu) Importance: Medium Status: Confirmed ** Tags: arm64 ** Attachment added: "binutils-vulcan-support.patch"

[Touch-packages] [Bug 1542080] Re: Needs tar/xattr support to build docker

** Changed in: gccgo-4.9 (Ubuntu Trusty) Status: New => Triaged ** Patch added: "libgo-add-tar-xattr-support.debdiff" https://bugs.launchpad.net/ubuntu/+source/gccgo-4.9/+bug/1542080/+attachment/4564171/+files/libgo-add-tar-xattr-support.debdiff -- You received this bug notification

[Touch-packages] [Bug 1542080] Re: Needs tar/xattr support to build docker

** Attachment added: "failed build log" https://bugs.launchpad.net/ubuntu/+source/gccgo-4.9/+bug/1542080/+attachment/4564170/+files/docker.io.buildlog.FAILED.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gccgo-4.9 in

[Touch-packages] [Bug 1542080] [NEW] Needs tar/xattr support to build docker

Public bug reported: [Impact] docker.io does not build on archs that require gccgo. [Test Case] Build docker.io in trusty on an arch that requires gccgo. I used arm64. (Also need patch in LP: #1510288) [Regression Risk] This is an upstream patch that applies cleanly (other than file tree

[Touch-packages] [Bug 1542080] Re: Needs tar/xattr support to build docker

** Changed in: gccgo-4.9 (Ubuntu Trusty) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: gccgo-4.9 (Ubuntu Trusty) Importance: Undecided => Critical ** Changed in: gccgo-4.9 (Ubuntu Trusty) Importance: Critical => High ** Changed in: gccgo-4.9 (Ubun

[Touch-packages] [Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

Marking as impacting juju-core/trusty. This is easily reproduced by attempting to bootstrap a juju-local environment in trusty with juju- core 1.24.7-0ubuntu1~14.04.1 when using a kernel w/ 4 level page tables. This will be a supported config once the xenial-lts kernel is available in trusty. A

[Touch-packages] [Bug 1546714] Re: System not booting when /home is on separate LUKS-encrypted partition

** Changed in: systemd (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1542080] Re: Needs tar/xattr support to build docker

I prepared a docker PPA with this update and asked our QA team to run some tests on it. Even though the binary builds and runs, we're still seeing docker crashes based on the older version of gccgo in trusty, so it still doesn't make sense to enable docker for gccgo in trusty at this time. A fix

[Touch-packages] [Bug 1554098] Re: Update s390x syscall tables

Thanks - I've updated the title of the bug to be about the syscall tables - I'll leave it to the Ubuntu dev to figure out if it makes sense to fix this w/ a new upstream or a backport. ** Summary changed: - Rebase libseccomp from (2.2.3-3) -> 2.3.0 + Update s390x syscall tables ** Changed in:

[Touch-packages] [Bug 1556140] Re: Restart Network service no Ip address was set on interface

The interface enccw0.0.f5f0 is not set to "auto". If you add the line "auto enccw0.0.f5f0" before the interface definition in /etc/network/interfaces, does it work as expected? See interfaces(5) for more information. ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You

[Touch-packages] [Bug 1546714] Re: System not booting when /home is on separate LUKS-encrypted partition

** Also affects: ubuntu-z-systems 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/1546714 Title: System not booting when /home

[Touch-packages] [Bug 1520162] Re: compiled binaries don't work on arm64 64k pages kernel due to alignment

I cannot reproduce this issue in xenial: dannf@mustang:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Xenial Xerus (development branch) Release:16.04 Codename: xenial dannf@mustang:~$ getconf PAGE_SIZE 65536 dannf@mustang:~$ -- You

[Touch-packages] [Bug 1560545] Re: Some or all OSA devices may be unavailable after boot if too many are visible

Marking systemd and sysconfig-hardware as affected due to these messages in syslog: systemd-udevd[4387]: Process '/sbin/hwup -A -D /devices/css0/0.0.0600/0.0.2f17 ccw 0.0.2f17' failed with exit code 9. ** Package changed: ubuntu => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Assignee:

[Touch-packages] [Bug 1560545] Re: Some or all OSA devices may be unavailable after boot if too many are visible

** Changed in: sysconfig (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- 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/1560545 Title: Some or all OSA

Re: [Touch-packages] [Bug 1542080] Re: Needs tar/xattr support to build docker

On Wed, Mar 23, 2016 at 6:01 AM, Chris J Arges <1542...@bugs.launchpad.net> wrote: > Are you wanting gccgo-4.9 4.9.3-0ubuntu5 rejected from the trusty queue? Yes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gccgo-4.9 in

[Touch-packages] [Bug 1552939] Re: arm64 build doesn't use asm and is 4x-16x slower than it could be

** Changed in: openssl (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: openssl (Ubuntu) Importance: Undecided => High ** Also affects: openssl (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794326 Importance: Unknown Status: U

[Touch-packages] [Bug 1552939] Re: arm64 build doesn't use asm and is 4x-16x slower than it could be

Thanks for the patch Ali! I uploaded a test package to ppa:dannf/test, and I've attempted to reproduce the improvement on a couple of different systems. On a ThunderX system, I am observing a significant performance improvement. However, on an X-Gene system, the performance actually seems to be

[Touch-packages] [Bug 1552939] Re: arm64 build doesn't use asm and is 4x-16x slower than it could be

Oops - I mean thanks Yangzheng! Confused the bug reporter w/ the patch submitter, sorry! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1552939 Title: arm64 build doesn't

[Touch-packages] [Bug 1552939] Re: arm64 build doesn't use asm and is 4x-16x slower than it could be

This is a change to a Debian-specific targets, so marking it Invalid for the upstream OpenSSL project. ** Changed in: openssl Status: New => Invalid ** Changed in: openssl (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member

[Touch-packages] [Bug 1552939] Re: arm64 build doesn't use asm and is 4x-16x slower than it could be

fyi, this is now available in xenial-proposed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1552939 Title: arm64 build doesn't use asm and is 4x-16x slower than it

[Touch-packages] [Bug 1554098] Re: Rebase libseccomp from (2.2.3-3) -> 2.3.0

s390x support has been backported to Ubuntu 2.2.3 packages. Is there some bug fix or additional functionality missing from that backport? If so, I suggest we reframe/retitle this bug to be about that functionality - that'll be more actionable than a new upstream version at this stage. ** Changed

[Touch-packages] [Bug 1552939] Re: arm64 build doesn't use asm and is 4x-16x slower than it could be

** Changed in: openssl (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1552939 Title: arm64 build doesn't use asm and is

[Touch-packages] [Bug 1574832] Re: iptraf-ng display issue

** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Importance: Undecided => Medium ** Bug watch added: Debian Bug tracker #819928 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819928 ** Also affects: iptraf-ng (Debian) via

[Touch-packages] [Bug 427775] Re: ntpdate.dhcp always ignored

** Also affects: ntp (Ubuntu Trusty) 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/427775 Title: ntpdate.dhcp always ignored

[Touch-packages] [Bug 1603137] Re: libbfd changed name without transition

** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu.

[Touch-packages] [Bug 1608948] Re: support hw watchpoints/breakpoints on ARMv8.{1, 2}

** Patch added: "armv8.1,2-hw-watch,breakpoints.diff" https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1608948/+attachment/4712374/+files/armv8.1%2C2-hw-watch%2Cbreakpoints.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1594452] Re: Add vulcan support

gcc-5 5.4.0-5ubuntu1~16.04 from ppa:ubuntu-toolchain-r/ppa does accept vulcan as an -mcpu option, and it does pass the correct -march settings down to the assembler: $ gcc -v hello.c -o hello 2>&1 | grep ' as ' as -v -EL -mabi=lp64 -o /tmp/ccgyMnhl.o /tmp/cchw8EFH.s $ gcc -mcpu=vulcan -v hello.c

[Touch-packages] [Bug 1637026] [NEW] kill incorrectly parses negative PIDs

** Affects: procps (Ubuntu Xenial) Importance: High Assignee: dann frazier (dannf) Status: In Progress ** Also affects: procps (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: procps (Ubuntu) Status: New => Fix Released ** Changed in: pro

[Touch-packages] [Bug 1610499] Re: hadoop crash: /bin/kill in ubuntu16.04 has bug in killing process group

*** This bug is a duplicate of bug 1637026 *** https://bugs.launchpad.net/bugs/1637026 ** This bug has been marked a duplicate of bug 1637026 kill incorrectly parses negative PIDs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1637300] Re: procps upgrades fail in a LXD container

** Patch added: "proposed debdiff for xenial" https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1637300/+attachment/4768378/+files/procps-no-init-on-upgrade.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps

[Touch-packages] [Bug 1637300] [NEW] procps upgrades fail in a LXD container

nce: Undecided Status: Fix Released ** Affects: procps (Ubuntu Xenial) Importance: High Assignee: dann frazier (dannf) Status: In Progress ** Also affects: procps (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: procps (Ubuntu)

[Touch-packages] [Bug 1178140] Re: top reports 9999% process CPU utilization

*** This bug is a duplicate of bug 531310 *** https://bugs.launchpad.net/bugs/531310 ** This bug has been marked a duplicate of bug 531310 Top showing % CPU usage -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1637300] Re: procps upgrades fail in a LXD container

Note that, though procps itself is patched to ignore errors when writing to /proc/sys, the problem here is that the initscript causes the systemd-sysctl service to get triggered, and that does not fail gracefully: ubuntu@procps:~$ sudo /lib/systemd/systemd-sysctl Couldn't write '1' to

[Touch-packages] [Bug 1637026] Re: kill incorrectly parses negative PIDs

** Tags removed: verification-needed ** Tags added: verification-failed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1637026 Title: kill incorrectly parses negative PIDs

[Touch-packages] [Bug 1637300] Re: procps upgrades fail in a LXD container

** Bug watch added: Debian Bug tracker #827423 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827423 ** Also affects: procps (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827423 Importance: Unknown Status: Unknown -- You received this bug notification because

[Touch-packages] [Bug 1643474] Re: sysrq k(kill) always kill the Xorg under Desktop

** Package changed: procps (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1643474 Title: sysrq k(kill) always kill the Xorg under Desktop

[Touch-packages] [Bug 1643084] Re: [REGRESSION] kill segfaults w/ single, negative PID

** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1643084 Title: [REGRESSION] kill segfaults w/ single,

[Touch-packages] [Bug 1643084] Re: [REGRESSION] kill segfaults w/ single, negative PID

Addresses: https://errors.ubuntu.com/problem/ca3851bccaed9924746cc8551188f9039c162093 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1643084 Title: [REGRESSION] kill

[Touch-packages] [Bug 1577297] Re: echo | xargs kill -15 kills running window session

*** This bug is a duplicate of bug 1637026 *** https://bugs.launchpad.net/bugs/1637026 ** This bug has been marked a duplicate of bug 1637026 kill incorrectly parses negative PIDs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1643084] [NEW] [REGRESSION] kill segfaults w/ single, negative PID

LP: #1637026. [Test Case] $ /bin/kill -9 Segmentation fault (core dumped) [Regression Risk] This fix will now make our optparsing almost identical to current yakkety, for which I see no obvious regressions filed. ** Affects: procps (Ubuntu) Importance: High Assignee: dann frazier (da

[Touch-packages] [Bug 1637026] Re: kill incorrectly parses negative PIDs

I've verified the fix for this issue, but it appears to have exposed a bug with updating procps in an LXD container. Below I'll show the verification, followed by the update issue. root@procps:~# apt-cache policy procps | grep Installed Installed: 2:3.3.10-4ubuntu2 root@procps:~# strace -f -o

[Touch-packages] [Bug 1637026] Re: kill incorrectly parses negative PIDs

root@procpstest:~# strace -f -o /tmp/strace.out su dannf -c '/bin/kill -12' root@procpstest:~# grep kill /tmp/strace.out 2623 execve("/bin/su", ["su", "dannf", "-c", "/bin/kill -12"], [/* 11 vars */]) = 0 2628 execve("/bin/bash", ["bash", "-c", "/bin/kill -12"], [/* 17 vars */]) = 0 2628

[Touch-packages] [Bug 1637300] Re: procps upgrades fail in a LXD container

root@procpstest:~# apt install procps -y Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: procps 1 upgraded, 0 newly installed, 0 to remove and 46 not upgraded. Need to get 208 kB of archives. After this

[Touch-packages] [Bug 1649213] Re: Support rootfs on xhci-plat-hcd attached storage

** Also affects: initramfs-tools (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux

[Touch-packages] [Bug 1649213] Re: Support rootfs on xhci-plat-hcd attached storage

** No longer affects: linux (Ubuntu Zesty) ** No longer affects: linux (Ubuntu Xenial) ** No longer affects: linux (Ubuntu Trusty) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.

Re: [Touch-packages] [Bug 1649213] Re: Support rootfs on xhci-plat-hcd attached storage

On Thu, Jan 5, 2017 at 2:46 PM, Brian Murray wrote: > Is the Trusty task valid? I don't see an upload in its SRU queue. It is - I think Ike maybe waiting for the current trusty-proposed version to migrate before rebasing. -dann -- You received this bug notification because

[Touch-packages] [Bug 1700826] Re: please include numactl on the ubuntu-server iso

** Changed in: ubuntu-meta (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-meta (Ubuntu Xenial) Status: New => In Progress ** Changed in: ubuntu-meta (Ubuntu Zesty) Status: New => In Progress -- You received this bug notification because you are a member of

[Touch-packages] [Bug 1686784] Re: no predictable names for platform (non-PCI) NICs

I upgraded systemd to 229-4ubuntu18 and removed /etc/udev/rules.d/70 -persistent-net.rules, and found that my onboard NICs are now using predictable names: ubuntu@d05-2:~$ ls /sys/class/net/ enahisic2i0 enahisic2i3 enP2p233s0f0 enP2p233s0f3 lo enahisic2i1 enP10p17s0f0 enP2p233s0f1

[Touch-packages] [Bug 1686784] Re: no predictable names for platform (non-PCI) NICs

Verified w/ 229-4ubuntu19. I rebuilt d-i against this update and verified that the enahisi style names were used at boot. I also upgraded a system with 229-4ubuntu18 to 229-4ubuntu19 where the non-PCI platform NIC is my primary NIC. After reboot, everything came back up as expected. ** Tags

[Touch-packages] [Bug 1700826] Re: please include numactl on the ubuntu-server iso

The MIR has been approved, so please go ahead and add numactl to the server seed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1700826 Title: please include numactl

[Touch-packages] [Bug 1700826] [NEW] please include numactl on the ubuntu-server iso

Public bug reported: I've submitted an MIR for the numactl binary package at: LP: #1700824. Assuming that is approved, please also include this on the server seed, which I believe is necessary for it to appear on the ubuntu-server ISOs. ** Affects: ubuntu-meta (Ubuntu) Importance:

[Touch-packages] [Bug 1686784] [NEW] no predictable names for platform (non-PCI) NICs

Public bug reported: [Impact] Systems may have NICs attached to the "platform" bus. These are NICs that are onboard, but not attached to a PCI(-like) bus. Rather, they are described by firmware directly. None of the naming policies enabled by Ubuntu by default matches these NICs, so they end

[Touch-packages] [Bug 1674258] Re: lscpu crashs when /dev/mem is not stable to read

** Also affects: util-linux (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: util-linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: util-linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug

[Touch-packages] [Bug 1686784] Re: no predictable names for platform (non-PCI) NICs

I built a d-i image against zesty-proposed, and verified that the installer showed predictable names for the onboard interfaces on a HiSilicon D05 server (see enahisi* in the attached screenshot). I used one of these interfaces for the install, and the system retained the configuration upon

[Touch-packages] [Bug 1686784] Re: no predictable names for platform (non-PCI) NICs

I also tested this on a Qualcomm QDF2400 server, and the onboard platform device was renamed to "enaqcom8070i0". -- 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/1686784

Re: [Touch-packages] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

On Thu, Jun 1, 2017 at 7:27 AM, Zhanglei Mao wrote: > Daniel, > > It is really good. For patch driver and new kernel buiding, I cc Dann on the > mail too, he is our engineer for this enablement project with Hisilicon. > This is pearl kernel was build by him too. > >

[Touch-packages] [Bug 1722313] Re: [SRU][xenial] Add "--with-audit" config option so that the hwclock command creates an audit record when the hardware clock is altered.

** Also affects: util-linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: util-linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: util-linux (Ubuntu Zesty) Importance: Undecided Status: New -- You received this bug

[Touch-packages] [Bug 1714431] Re: Can not login after switch to runlevel 3 from 1

** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of

[Touch-packages] [Bug 1700826] Re: please include numactl on the ubuntu-server iso

Yeah - I verified it on the arm64 ISOs, and it was good. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1700826 Title: please include numactl on the ubuntu-server iso

[Touch-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names

** Description changed: - On a HiSilicon D06 system we noticed that interfaces provided by a plug- - in "HINIC" network card are not getting assigned predictable names. - We're getting "ethX" names instead of the expected "enPblah" names. + [Impact] + Interfaces associated with Huawei "hinic" PCI

[Touch-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names

** Description changed: [Impact] Interfaces associated with Huawei "hinic" PCI adapters will not be assigned predictable names[*] and instead remain using the kernel names (e.g. eth0). This can lead to races where the interface names are not the same on every boot. For example, in a system

[Touch-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names

Verification: ubuntu@d06-3:~$ cat /proc/version Linux version 4.15.0-34-generic (buildd@bos02-arm64-002) (gcc version 7.3.0 (Ubuntu/Linaro 7.3.0-16ubuntu3)) #37-Ubuntu SMP Mon Aug 27 15:22:18 UTC 2018 ubuntu@d06-3:~$ lsmod | grep hinic hinic 94208 0 ubuntu@d06-3:~$ grep eth

[Touch-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device

I prepared a ppa build of d-i (ppa:dannf/test) and booted w/ apt- setup/proposed=true. It resolves the issue I was seeing on a HiSilicon D05 system w/ disks attached to an mpt3sas controller. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received

[Touch-packages] [Bug 1782835] Re: d-i step "Configure the keyboard" fails

I rebuilt bionic d-i against proposed and the problem is now gone. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names

fyi, this appears to fix the problem for me. ** Patch added: "0001-hinic-Link-the-logical-network-device-to-the-pci-dev.patch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783138/+attachment/5166848/+files/0001-hinic-Link-the-logical-network-device-to-the-pci-dev.patch ** Also

[Touch-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names

** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

  1   2   3   >