Zesty is end of life.
** Changed in: procps (Ubuntu Zesty)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1717224
Title:
virsh start of virtual guest dom
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1584828
Title:
s390/pci: fix use after free in dma_init
Statu
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1739672
Title:
Regression in getaddri
** Changed in: systemd (Ubuntu Bionic)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1739672
Title:
Regression in getaddrinfo(): calls block for
** Changed in: chrony (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown w
Current kernel is 4.4.0-97-generic given we are blocked generating
initramfs, upgrading kernels is interesting...
We do not have any mdadm raids on this system, so I will try removing
mdadm; upgrading kernels; re-installing mdadm to reproduce the issue.
--
You received this bug notification beca
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1743638
Title:
Missing install-time driver for QLogic QED 25/40/100Gb Ethernet NIC
Status in debi
I believe this is third party source that you are trying to build, not
using Ubuntu package build procedures, with a non-default compiler.
This is out of scope to provide support for.
Why are you using clang, instead of gcc, btw? I believe you will have
more success if you use the default Ubuntu
** Changed in: systemd (Ubuntu Xenial)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/696435
Title:
wait-for-root fails to detect nbd root
Status
Hi, I do not believe canonical is committing to fix all the
upstream/mainline selftest failures. However, if there are additional
selftest regressions with the ubuntu kernel which are not seen with the
mainline build, those are worth looking into. If these selftests never
pass on POWER maybe it is
Are there patches that should be attached and synced to launchpad for
this bug report? Or have they been sent to the Ubuntu kernel team
mailing for review and inclusion?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
This is already fix released, as the commit mentioned is in the v4.13+
kernels.
Is this a request to backport this to some previous release? Because
this is an invalid request for 18.04.
** Changed in: ubuntu-z-systems
Status: Triaged => Invalid
** Changed in: linux (Ubuntu)
Status
Hi, if this is on bionic, you need to wait until 23rd Feb respin is
done, which I guess for you means Monday unfortunately. Since 4.15
landed in bionic now, but d-i was not rebuild correctly in time, thus
there was a missmatch of things temporarily.
--
You received this bug notification because y
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: linux (Ubuntu Xenial)
S
The bug is in progress, thus the fix for this issues is not yet available for
testing.
When it is available, there will be a comment on this bug report, calling for
testing and listing exact version number of the kernel which includes the fix.
--
You received this bug notification because you a
"as it will appear in kernel 4.17?"
Note, that 18.04 is currently targetting v4.15, thus above mentioned
commits, will need to be assessed by the kernel team for suitability to
be cherry-picked into v4.15 kernel. At least to me, the commits
mentioned, look mostly harmless.
--
You received this b
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1747639
Title:
[18.04 FEAT] Automatically detect layer2 setting in the qeth device
dri
On 27 February 2018 at 12:50, bugproxy wrote:
> --- Comment From naveed...@in.ibm.com 2018-02-27 07:41 EDT---
> since 4.15.0-11-generic is released, can we get dbgsym for
> linux-image-4.15.0-11-generic-dbgsym_4.15.0-11.xx_ppc64el.ddeb ?
This question is odd. How do you normally "get dbg
** Changed in: ubuntu-z-systems
Assignee: bugproxy (bugproxy) => (unassigned)
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1704929
Title:
Rep
** Changed in: linux (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1734691
Title:
Got disk i/o failur
** Changed in: linux (Ubuntu)
Assignee: bugproxy (bugproxy) => (unassigned)
** Changed in: ubuntu-z-systems
Assignee: bugproxy (bugproxy) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1751994
Title:
ppc64el: Support firmware disable of RFI flush
Status in The Ubu
Public bug reported:
bionic-proposed block to publish supported kernels in main
The following kernels should be available, installable, and in main, in
bionic.
linux-aws
linux-azure
linux-gke
linux-hwe
linux-kvm
Once all of these are published, with their metas, and are actually
installable, th
** Also affects: linux-meta-aws (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-meta-gke (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-meta-kvm (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-meta-azure (Ubuntu
Please also provide the upstream linus' tree commit ID, once merged /
when available.
** Changed in: linux (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel
(canonical-kernel)
--
You received this bug notification because you are a member of Kernel
Packages
grub2 is ready now.
livecd-rootfs is in-flight.
what's the update on this change landing?
** Changed in: linux (Ubuntu)
Importance: Medium => Critical
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Canonical Kernel (canonical-kernel)
--
You received this bug notification beca
@sofrshee / jsalisbury
I have now prepared, and sent an updated patch which does more.
Maybe seth was a bit trigger happy about this after lunch =)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
** Patch removed: "0001-UBUNTU-Config-CONFIG_EFI-y-on-armhf.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726362/+attachment/4987801/+files/0001-UBUNTU-Config-CONFIG_EFI-y-on-armhf.patch
** Patch added:
"0001-UBUNTU-Config-CONFIG_EFI-y-on-armhf-reconcile-secure.patch"
https
** Changed in: linux (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel
Team (canonical-kernel-team)
** Changed in: ubuntu-z-systems
Assignee: Canonical Kernel Team (canonical-kernel-team) => (unassigned)
** Changed in: linux (Ubuntu)
Status: New
@frank
10.04 LTS (Lucid Lynx) is end of life, and does not at all support s390x
=)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1755133
Title:
KVM: s390: diagnoses are instruction
@breno re: point release meaning vs updates
Please note point releases refer to installation media only, which is a
consistent snapshot of cloud images, container images, server ISO, d-i,
etc. Built from xenial-updates & xenial-security pockets as published at
the time of the respin. xenial-update
zfcpdump kernel is escalated to the kernel team.
** Also affects: zfcpdump-kernel (Ubuntu)
Importance: Undecided
Status: New
** Changed in: zfcpdump-kernel (Ubuntu Artful)
Status: New => Triaged
** Changed in: zfcpdump-kernel (Ubuntu Artful)
Importance: Undecided => High
**
** No longer affects: console-setup (Ubuntu Xenial)
** No longer affects: console-setup (Ubuntu Zesty)
** No longer affects: console-setup (Ubuntu Artful)
** Changed in: console-setup (Ubuntu)
Status: Confirmed => Incomplete
** Also affects: linux (Ubuntu)
Importance: Undecided
/dev/tty1 file exists on s390x ubuntu, however, one cannot open that
file doing that results in ENXIO.
console-setup is an architecture independent package which tries to
detect and configure all consoles. Ideally, I do not want to encode if
`uname -p` is s390x or some such to filter-out and skip
** Description changed:
- Enable non transparent hardware functions for KVM guests (crypto CPACF
- functions)
+ Kernel team, could you please consider cherrypicking the below commit
+ into the linux kernel for Artful?
+ commit b697e435aeee99b7f5b2d8f8dbb51f791be99b16
+ Author: Jason J. Herne
Then we defiantly want this patch in artful!
Because linux-hwe kernel will be used as is, on xenial, which may be
used with xenial GA qemu v2.5, or any of the cloud-archive backports of
qemu - 2.8 and 2.10.
--
You received this bug notification because you are a member of Kernel
Packages, which
v4.13 landed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1712724
Title:
s390 zKVM complains about "illegal operation" to s390/mm/pgalloc.c
Status in Ubuntu on IBM z Systems:
Triage
Do we need to escalate this back to IBM Kernel team to resolve upstream
/ stable?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1689240
Title:
scrashme failed to build on LPAR Ubuntu
S
Checking in on this stale bug report.
Which kernel drivers are missing from the main linux-image package, and
have we moved those in later releases and SRUed into xenial?
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a m
@hws @michael.holzheu @schwidefsky
It seems like schwidefsky updated s390 config upstream in v4.12 to
remove -CONFIG_DEBUG_FS=y for the zfcpdump_defconfig. Meaning any Linux
on Z systems using v4.12+ default zfcpdump_defconfig from upstream linux
source tree will get a bad configuration. It seems
The unit entered a failed state, and thus would not automatically started until
failed state clears.
Why does bouncing of the services result in the daemon exiting with an error
condition? Should that particular exit code result in a graceful shutdown of
the service, such that the unit can be re
Public bug reported:
ubuntu-regression-suite fails in xenial
autopkgtest [22:34:48]: test ubuntu-regression-suite: [---
Source Package Version: 4.4.0-1035.44
Running Kernel Version: 4.4.0-96.119
ERROR: running version does not match source package
Please note autopkgtests hav
The command ran is of this form:
autopkgtest [19:55:28]: host juju-prod-ues-proposed-migration-machine-3;
command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir
/tmp/autopkgtest-work.iw5t9p35/out --timeout-copy=6000 --setup-commands
/home/ubuntu/autopkgtest-cloud/worker-config-prod
This all for xenial ADT tests.
** Tags added: xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1721558
Title:
ubuntu-regression-suite fails in xenial
Status in linux-aws packa
That other bug was reverse-proxied as LTC-159968 please see that for
further discussion on upgrading Ubuntu's zfcpdump-kernel to 4.13.
** Changed in: ubuntu-z-systems
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which
> AFAIK you are the only official distribution that uses 4.13 for zfcpdump -
> therefore IMHO this should be sufficient.
That is not true. We do not use v4.13 kernel for zfcpdump-kernel package.
zfcpdump-kernel package is based on v4.9 and upgrading that to v4.10+ fails to
perform any dumps at a
Whilst we are waiting on upstream, can kernel team pick up the proposed
patches for power & s390 as patche sinto autotest-client-tests
framework?
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
--
You received this bug notification becau
@canonical kernel team
Is this issue now resolved with v4.13 kernels?
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
** Changed in: linux (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because y
Any updates? Have you been able to monitor fs.aio-nr exhaustion?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1717224
Title:
virsh start of virtual guest domain fails with internal err
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
** Summary changed:
- System fails to boot with nouveau
+ Ubuntu Desktop ISO fails to boot with nouveau
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
@jsalisbury that kernel is very nice, could you please cherrypick that
patch and include it in the next available/convenient src:linux SRU?
I have added the SRU template to the bug report.
** Description changed:
+ [Impact]
+ Kernel does not generate any events when ndb-client connects /dev/nbd0
yes, but I'm not uploading systemd until after the build-farm is open.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1739672
Title:
Regression in getaddrinfo(): calls block for much lon
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1744173
Title:
artful: rfi-flush: Switch to new linear fallback flush
Status in The Ubuntu-po
Public bug reported:
[Impact]
* Please enable CONFIG_EFI on the armhf generic kernels
* This may enable using armhf kernels with an armhf cloud-image and
qemu-efi-arm under qemu-system-arm
[Test Case]
* Kernel config has CONFIG_EFI=y
[Regression Potential]
* Kernel config/image/modules w
** Patch added: "0001-UBUNTU-Config-CONFIG_EFI-y-on-armhf.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726362/+attachment/4987801/+files/0001-UBUNTU-Config-CONFIG_EFI-y-on-armhf.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is s
So i think I will need to create livecd-rootfs and grub2 patches and
this too. So let's aim at landing this in bionic, and testing everything
works there before SRUing this config change. grub2 backports might be
too intrusive, and thus this might be a bionic+ thing only.
--
You received this bug
Once the kernel is fixed, are there any changes that are required to
systemd/udev?
** Changed in: systemd (Ubuntu Bionic)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
** Changed in: systemd (Ubuntu Artful)
Status: Confirmed => Fix Committed
** Changed in: systemd (Ubuntu Artful)
Status: Fix Committed => In Progress
** Changed in: systemd (Ubuntu Artful)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received
** Information type changed from Private to Public
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1734130
Title:
[18.04
Is this fix released in artful & bionic too?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730596
Title:
s390/mm: fix write access check in gup_huge_pmd()
Status in Ubuntu on IBM z Sy
$ time systemd-resolve -p dns not-a-real-hostname
not-a-real-hostname: resolve call failed: No appropriate name servers or
networks for name found
real0m0.003s
user0m0.000s
sys 0m0.004s
$ time systemd-resolve -p llmnr not-a-real-hostname
not-a-real-hostname: resolve call failed: All
avahi is zeroconf or IPv4LL, which is RFC 3927; whilst LLMNR is RFC
4795. In many aspects LLMNR is like mdns, yet the two are distinct and
resolve different things quite differently, when inspected closer.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Triaged
--
You received this
** Summary changed:
- Regression in getaddrinfo(): calls block for much longer on Bionic (compared
to Xenial)
+ Regression in getaddrinfo(): calls block for much longer on Bionic (compared
to Xenial), please disable LLMNR
--
You received this bug notification because you are a member of Kernel
On 3 November 2017 at 19:27, Jeff Lane wrote:
> On Fri, Nov 3, 2017 at 1:13 PM, Joseph Salisbury
> wrote:
>> Do you know which prior kernels did not exhibit this bug? Was it 4.12
>> or earlier?
>
> I "think" it happened with 4.10 as well, but I'm not positive, I ran
> some tests before realizing
Public bug reported:
Please enable CGROUP_BPF=y
Systemd has started to use that thing.
** Affects: linux (Ubuntu)
Importance: Wishlist
Status: Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
I am muppet
debian.master/config/annotations:CONFIG_CGROUP_BPF
policy<{'amd64': 'y', 'arm64': 'y', 'armhf': 'y', 'i386': 'y',
'ppc64el': 'y', 's390x': 'y'}>
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packa
https://launchpad.net/ubuntu/+source/linux/4.4.0-100.123
** Changed in: systemd (Ubuntu Xenial)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/69643
Should a fix for this be backported to 16.10 and 16.04?
Are there people who have the relevant hardware available, and are willing to
test the fix on both 16.10 and 16.04?
I do not have the hardware available, thus without available testers I would
not want to upload this fix.
--
You received t
** No longer affects: systemd (Ubuntu Xenial)
** No longer affects: systemd (Ubuntu Yakkety)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1590590
Title:
Touchpad not recognized on Del
This issues was rejected by Canonical, and closed as invalid on
2017-01-18.
This bug is incorrectly filed against src:linux, I will move it to
src:s390-tools shortly.
Further discussion is about upstream features. Canonical does not
participate in s390-tools upstream development.
It is absolutel
I do not believe I can land the systemd change, unless 4.4 kernel picks
up the above mentioned fix. As otherwise hwe kernels will work, and GA
kernel will not.
** Changed in: systemd (Ubuntu Xenial)
Status: New => Incomplete
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned)
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: systemd (Ubuntu Xenial)
Status: Confirmed => Incomplete
** No longer affects: linux (Ubuntu Xenial)
** No longer affects: systemd (Ubuntu Xenial)
--
You received this bug notification because you are a
Have patches to resolve this issue been created and contributed by IBM
to linux kernel upstream? Do you have commit ids please?
** Changed in: ubuntu-z-systems
Assignee: Canonical Kernel Team (canonical-kernel-team) => bugproxy
(bugproxy)
** Changed in: linux (Ubuntu)
Assignee: Skipper
Moving the ipr module from linux-image-extra to linux-image package
should resolve this issue as well, no? Essential modules for booting
should be kept in the linux-image package, whilst auxiliary can be kept
in the -extra package.
** Also affects: linux (Ubuntu)
Importance: Undecided
St
$ git tag --contains a521b048bc8c5d3c57a468c2cba70eb60e873616
v4.10-rc1
v4.10-rc2
and other commits since v4.9.
** Changed in: linux (Ubuntu)
Assignee: Canonical Kernel (canonical-kernel) => Canonical Kernel Team
(canonical-kernel-team)
** Changed in: linux (Ubuntu)
Importance: Wishlis
Tags: architecture-ppc64 -> seems to be the inconsistent tag.
** Tags removed: architecture-ppc64
** Tags added: architecture-ppc64le
** Also affects: linux (Ubuntu Zesty)
Importance: Medium
Assignee: Canonical Kernel Team (canonical-kernel-team)
Status: Triaged
** Also affects: l
All of the mentioned commits are in v4.6 and later, thus this is fix
released in yakkety and zesty.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1560482
Title:
perf: 24x7: Eliminate do
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: iucode-tool (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1423296
However, the message is mostly cosmetic in its nature.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1654068
Title:
Ubuntu 16.04.02: Error message "kernel version is not supporte
** Changed in: linux (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel
Team (canonical-kernel-team)
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Is there any progress on this issue?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1683587
Title:
LSI Harpoon support in megaraid_sas module
Status in linux package in Ubuntu:
Confir
@ bin tang
Could you please explain who you are and what are you doing? Are you an
employee of a partner? If so, you should not be using launchpad, and you
should only be using bugproxy mirror from internal bugzilla.
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: ubun
uname is not used to report point release version number.
The only authoritative files with point release details are: /etc/issue,
/etc/issue.net, /etc/lsb-release, /etc/os-release
These are updated via base-files package - see
https://launchpad.net/ubuntu/+source/base-files/9.4ubuntu4.5
base-fi
@abthla
This is not a forum.
This is not a place for discussions or support.
I do not understand your bug report :-(
I do not know how to help you. Or where you can seek help you require.
** No longer affects: ubuntu-z-systems
** No longer affects: ubuntu-power-systems
** Tags removed: archi
Please report this bug in Debian BTS at bugs.debian.org. You may find $
reportbug helpful.
Once fixed in Debian, we can sync the fix to ubuntu artful.
Fixing xenial is out of scope.
** Package changed: linux (Ubuntu) => rpm (Ubuntu)
--
You received this bug notification because you are a member
adt tests appear to pass quickly enough. A new bug will be opened if and
when any new adt issues arise.
** Tags removed: verification-needed-trusty verification-needed-xenial
verification-needed-zesty
** Tags added: verification-done-trusty verification-done-xenial
verification-done-zesty
--
Y
** Changed in: cloud-init
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1682871
Title:
attempts to rename vlans / vlans have addr_assign_type o
ticket closed.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
** Changed in: systemd (Ubuntu Xenial)
Status: New => Invalid
** Changed in: systemd (Ubuntu Yakkety)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packa
Please provide the installer logs from the running installer,
specifically /var/log/syslog
** Package changed: linux (Ubuntu) => debian-installer (Ubuntu)
** Changed in: debian-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
ubuntu@DEVAC02:~$ ethtool enc600
Settings for enc600:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supported pause frame
We currently believe our firmware is not up to date, as per comments
above. We will investigate our installs further, upgrade if necessory,
and retest. Setting to incomplete, and assigning to frank heimes to
coordinate this effort.
** Changed in: ubuntu-z-systems
Assignee: bugproxy (bugproxy)
We must support docker on cloud images which by default do not install
-extra- package.
Thus missing default drivers should be in the main kernel package.
** Changed in: linux (Ubuntu Yakkety)
Status: Invalid => Triaged
** Changed in: linux (Ubuntu)
Status: Invalid => Triaged
--
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
** Changed in: systemd (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu Xenial)
Importance: Undecided => Medium
--
You received th
*** This bug is a duplicate of bug 1557690 ***
https://bugs.launchpad.net/bugs/1557690
** This bug has been marked a duplicate of bug 1557690
s390/kconfig: CONFIG_NUMA without CONFIG_NUMA_EMU does not make any sense on
s390x
--
You received this bug notification because you are a member
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: systemd (Ubuntu)
Milestone: None =>
As far as I can tell the patch for hwdb sensitivity for Dell Latitude
E7470 is shipped in zesty now.
Is anything else required to have this resolved in zesty? Or hwdb update
is all that is needed here? If that is the case, then we can remove all
the other packages marked as affected and simply SRU
** Changed in: linux (Ubuntu Zesty)
Assignee: rahmadani (rahmadani) => (unassigned)
** Changed in: ubuntu-z-systems
Assignee: rahmadani (rahmadani) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The calls that fail are 'open()' calls. In ubuntu we do not have patches
to s390-tools for dasdfmt code path. Please seek help from s390-tools
upstream developers at IBM.
And call to 'open()' should not require user to have a default shell set
- e.g. it should not be resulting in e.g. system() cal
4.11.0-10.15 is now in artful, all requested commits are part of the
Ubuntu-4.11.0-10.15 tag.
** Information type changed from Private to Public
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: ubuntu-z-systems
Status: Incomplete => Fix Released
--
Public bug reported:
http://autopkgtest.ubuntu.com/packages/linux/artful/armhf
quite often the tests time out on armhf. Maybe this is due to running
inside a lxc container, rather than in a full VM.
Could you please consider disabling rebuild test on armhf? Or for
example lowering its parallelis
501 - 600 of 1816 matches
Mail list logo
