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"
https://bugs.launchpad.net/ubuntu/+source/gcc-6/+bug/1594452/+attachment
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 no
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
rearra
** 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
** 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 b
** 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
** 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.
https://bugs.launchpad.net/bugs/15467
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 f
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 i
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
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 could
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: li
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 receiv
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 rec
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:
** 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 d
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 U
** 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 i
** 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
Stat
** 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
ht
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]:
github.com_juju_cmd.Defa
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
** 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
** 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 Wily
** Also affects: gccgo-4.9 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: gcc-4.8 (Ubuntu)
** No longer affects: gcc-4.9 (Ubuntu)
** Changed in: gccgo-4.9 (Ubuntu Trusty)
Status: New => Confirmed
** Also affects: gccgo-5 (Ubuntu)
Importance: Undecided
** 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 b
** 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
** Summary changed:
- Ubuntu 14.04 cannnot ssh into Chassis Manager
+ Ubuntu 14.04 cannot ssh into Chassis Manager
--
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/1311250
Public bug reported:
Similar to the m800 case in LP: #1347776, udev/systemd also needs to
know how to trigger a graceful shutdown on ProLiant m400 cartridges.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a mem
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
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 m400 cartr
** 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 ProLi
** Patch added: "patch for utopic's systemd"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1354306/+attachment/4172769/+files/utopic.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https:/
** 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 membe
** 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 membe
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 recei
** 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.
https://b
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+="pow
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+="pow
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 s
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 s
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 pressing,
** 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 m400
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 thi
On Mon, Jul 28, 2014 at 3:46 PM, Steve Langasek
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,
> systemd notwithstanding.
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 multi
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 this
201 - 246 of 246 matches
Mail list logo
