Dec 10 04:58:52 m14 kernel: [4.864611] rtc-pl031 fff35000.rtc:
setting system clock to 2013-12-10 09:58:44 UTC (1386669524)
Thanks Paulo!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Err...Paolo. Sorry.
** Tags removed: verification-needed-saucy
** Tags added: verification-done-saucy
--
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/1252242
Title:
Stefan: I assigned you in the server team meeting. Please unassign if
you object. Thanks!
** Changed in: linux (Ubuntu Saucy)
Assignee: (unassigned) = Stefan Bader (smb)
** Changed in: qemu-kvm (Ubuntu Saucy)
Assignee: (unassigned) = Stefan Bader (smb)
--
You received this bug
** Description changed:
Currently there is no support for Arm support using kvm-ok. Currently
when I run kvm-ok I get the following output:
INFO: Your CPU does not support KVM extensions
KVM acceleration can NOT be used
[FFe]
We have ARM KVM support in the kernel, and now
Consider a debconf high priority notice on the final update (postinst?).
Or something else that will generate a root email, perhaps?
--
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/1244438
Public bug reported:
Working on MAAS, I see midway machines boot on Saucy with an incorrect
system time (close to epoch). I have tried various things, including
using MAAS to make sure that the hardware clock was set correctly before
installation. Despite this, I find that the hardware clock (as
** Changed in: linux (Ubuntu)
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/1252242
Title:
CONFIG_RTC_DRV_PL031=m stops the kernel from setting
** Also affects: cpu-checker
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to cpu-checker in Ubuntu.
https://bugs.launchpad.net/bugs/1194632
Title:
kvm-ok Support for ARM Architecture is
** Description changed:
Currently there is no support for Arm support using kvm-ok. Currently
when I run kvm-ok I get the following output:
INFO: Your CPU does not support KVM extensions
KVM acceleration can NOT be used
+
+ [FFe]
+
+ We have ARM KVM support in the kernel, and now
Oh, one other note. I was concerned about the external Internet
dependencies (ddebs.ubuntu.com and keyserver.ubuntu.com), but following
a discussion with jibel in #ubuntu-quality, we accepted that these
specific ones are OK. I see ddebs.ubuntu.com as an extension of test
dependencies, and
Three issues:
1) The shebang has a typo. It should be #!/bin/sh -x not #/bin/sh -x.
2) The heredoc end terminator needs leading whitespace removed; otherwise it
doesn't work.
3) Running /bin/sh -x writes output to stderr, which autopkgtest treats as a
failure by default. The easy fix is to add
Updated debdiff attached.
** Patch added: crash_autopkgtest_v2.debdiff
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1217474/+attachment/3825173/+files/crash_autopkgtest_v2.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Fixed in 6.1.6-1ubuntu2.
** Changed in: crash (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1217474
Title:
basic autopkgtest for
Marking as Confirmed to stop the linux bug bot, since we have the
details to reproduce based on the qemu image.
** Package changed: openldap (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New = Confirmed
** Tags added: ppc64el
--
You received this bug notification
Marking as Confirmed to stop the linux bug bot, since we have the
details to reproduce based on the qemu image.
** Package changed: openldap (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New = Confirmed
** Tags added: ppc64el
--
You received this bug notification
It might also be worth considering what users already use to monitor
their machines for updates, and to provide alerts by patching those
mechanisms. For example, we might SRU a patch to the check_apt nagios
plugin to pick up the EOL kernel state and present it as a warning or
failure.
What other
Looks like this was fixed in the 20140724 image (now 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/1313450
Title:
Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2 or Xen)
Reproduced with latest upstream kernel from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc4-vivid/
linux-image-4.0.0-04rc4-generic 4.0.0-04rc4.201503152135
Linux vivid-test 4.0.0-04rc4-generic #201503152135 SMP Mon Mar 16 01:36:37
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Workaround:
1. Install http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.13.11.11-trusty/linux-
image-3.13.11-0313-generic_3.13.11-0313.20141336_amd64.deb
2. Edit /etc/default/grub and set:
GRUB_DEFAULT=Advanced options for UbuntuUbuntu, with Linux
3.13.11-0313-generic
3. Run
Joseph, Stefan: I can give you access to the guest on lcy01 that
exhibits the problem if you need it.
--
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/1431473
Title:
kvm_intel (nested)
(the fix committed in Debian is at http://anonscm.debian.org/cgit
/collab-
maint/rpm.git/commit/?id=d246a0c7ed4853d1ec433fdc2ae999618f6837e2)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
It looks like the fix in rpm in Debian is to use bash instead of dash,
so the fallback from $HOME to ~ works if $HOME is not set.
I'm not sure if this particular fix is appropriate for Trusty as the rpm
package doesn't currently depend on bash. Incidentally, shouldn't the
fix in Debian have
@jjo
Please update the tags and change the status following peanlvch's
instructions in comment #10. I'm not sure exactly which version you
tested. Otherwise the bug may not reappear in the appropriate triage
queue and may get lost.
--
You received this bug notification because you are a member
@Christopher
Why did you mark this Incomplete? It does not look Incomplete. As far as
I can tell, all information requested has been provided.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This sounds like a kernel or X.org problem - certainly
not openssh - so reassigning.
** Package changed: openssh (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
I'm pretty sure this would need to be fixed in grub2 packaging, not in
the kernel.
** Package changed: linux (Ubuntu) = grub2 (Ubuntu)
** Changed in: grub2 (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Kernel
Packages, which is
In duplicate bug 1521086 the 14.04 kernel is implicated, so adding a
linux task.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Kernel memory leak introduced with recent 3.13 updates? Machine hangs with
out of memory after about 2 days.
+
** Changed in: libseccomp (Ubuntu)
Status: New => Triaged
--
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/1526358
Title:
adding seccomp rule for socket() fails on i386 since
It's at the bottom of the bug description.
** Tags added: kernel-bug-exists-upstream
--
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/1584042
Title:
Hyper-V NIC cannot pass IPv6 UDP
Please at least report your kernel version.
** Changed in: linux (Ubuntu)
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/1584042
Title:
Hyper-V
Frédéric,
Thank you. This is clear to me now. As it's a driver issue, I'm
reassigning to the kernel package. The kernel team will probably need
more information about your (virtual) hardware and will want you to test
the latest upstream kernel version or similar.
** Summary changed:
- IPV6
If this will take a while, then would it be possible to have ofono
default to a deterministic SIM for outbound calls as an interim
workaround? Eg. sort them by some key and take the lowest one, or use
the lowest numbered port or something. Then I could swap the SIM cards
around (if needed) to get
Hello Jim, or anyone else affected,
Accepted flash-kernel into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/flash-
kernel/3.0~rc.4ubuntu62.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Are there any other systems that use flash-kernel that need to be
considered in the test plan and regression potential sections?
>From a flash-kernel perspective, based on the patch it seems to me that
the decision to use a compressed kernel is outside the package, so I
don't see a regression
The current verification-done tag looks like it is intended for Yakkety
only, and the Xenial proposed package still needs verification.
** Tags removed: verification-done
** Tags added: verification-done-yakkety verification-needed
--
You received this bug notification because you are a member
I tried running tor in a Zesty container on a Xenial VM.
With 4.4.0.64.68 it fails as described (tor@default fails to start).
With 4.4.0.65.69 (following a reboot) it works correctly.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug
I tried running tor in a Zesty container on a Zesty VM.
With the current 4.10.0.8.10 it fails as described (tor@default fails to
start). AFAICT, the bug still exists on Zesty.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Yakkety)
I tried running tor in a Zesty container on a Yakkety VM.
With 4.8.0.39.50 it fails as described (tor@default fails to start).
With 4.8.0.40.51 (following a reboot) it *still* fails as described.
AFAICT, 4.8.0.40.51 does not fix the problem on Yakkety.
** Tags removed:
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since there isn't enough information in your report to differentiate
between a local configuration problem and a bug in Ubuntu, I'm marking
this bug as Incomplete.
If indeed this is a local configuration problem,
** Changed in: xen (Ubuntu)
Importance: Undecided => Wishlist
--
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/1460900
Title:
[Feature]Code/Data Prioritization (CDP) Enablment
Status
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since you say this was due to a change in the kernel version, it sounds
like is a kernel regression rather than a bug in the autofs package, so
reassigning.
** Package changed: autofs (Ubuntu) => linux (Ubuntu)
13:48 Hi SRU vanguard, could you please nominate LP: #1628279
affecting Xenial ?
13:48 Launchpad bug 1628279 in zfs-linux (Ubuntu) "python
utilities script suffix (.py) should be removed as per Policy 10.4"
[Low,Fix released] https://launchpad.net/bugs/1628279
13:48 slashd, done
13:49 apw,
** Tags added: regression-update
** Changed in: linux (Ubuntu)
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/1628735
Title:
Autofs variables do
** Package changed: drbd-utils (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/1629260
Title:
drdb kernal 4 crash
Status in linux package in Ubuntu:
Based on the investigation so far, it seems to me that this is entirely
a kernel bug, and there is nothing required in the bridge-utils package
in order to fix this issue. So I'm marking this bug as Invalid for
bridge-utils. The kernel tasks remain open. If this is incorrect, please
explain why
Setting Incomplete for qemu-kvm as well, pending the reporter's response
on whether this is still an issue.
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Also affects: linux (Ubuntu Yakkety)
Importance: Undecided
Status: New
--
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/1640786
Title:
netfilter regression introducing a
I happen to have come across this. I don't have the knowledge to help,
but it does sound like this is a kernel issue rather than a problem with
the intel-microcode package, so let's reassign it. Otherwise it won't
get attention from anyone who might know.
"Critical" importance is probably not
Thanks Tim!
Invalid for kbd then I guess, as the fix will be in the kernel.
** Changed in: kbd (Ubuntu Zesty)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
00:27 smb: is
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1648143/comments/26
correct? Wrong bug?
00:28 yeah, looked odd to me to, I don't see the link between that
security fix and this bug
00:29 Let's reopen for now. If it's wrong, smb can re-close it
perhaps?
** Changed in:
I have similar feelings to sil2100. I don't think it makes sense for
Ubuntu to do something special here. Until someone figures out what
upstream is doing I don't think it's appropriate to add a delta to
Ubuntu for this. So unsubscribing ~ubuntu-sponsors for now. Please
resubscribe
Kernel team,
This default appears to be set in drivers/tty/vt/vt.c to "10*60". Would
you be agreeable in changing the default to 0 for all of Ubuntu in the
next release (perhaps Zesty+1)? For example we could patch it, or we
could add a parameter to make it configurable (either defaulting to
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
Rejecting from the Xenial queue due to the lack of response.
If this still needs fixing in Xenial, please see
https://wiki.ubuntu.com/StableReleaseUpdates and follow
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure.
--
You received this bug notification because you are a member of Kernel
Sorry, you're right. "systemctl status tor@default" still shows the
service as not running, but now the reason is different.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu Yakkety)
Status: Confirmed => Fix Committed
** Tags removed:
So this particular bug is Invalid for the tor package in Ubuntu, since
the bug was in the kernel and we've verified that with fixes in
proposed. tor still doesn't work on Zesty, but I'll file a separate bug
for that.
** Changed in: tor (Ubuntu)
Status: New => Invalid
** Changed in: tor
I filed bug 1670408 to track the further issues in tor's AppArmor
profile that stop it from starting on 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/1648143
Title:
tor in lxd:
Public bug reported:
Using Ubuntu artful with linux-image-4.10.0-26-generic 4.10.0-26.30 and
sshfs 2.8-1. I use "sshfs -o reconnect" and often run gvim against a
file on an sshfs filesystem.
Sometimes when I suspend I get:
Jul 4 20:59:08 xps kernel: [46684.608740] PM: Syncing filesystems ...
apport information
** Tags added: apport-collected artful
** Description changed:
Using Ubuntu artful with linux-image-4.10.0-26-generic 4.10.0-26.30 and
sshfs 2.8-1. I use "sshfs -o reconnect" and often run gvim against a
file on an sshfs filesystem.
Sometimes when I suspend I get:
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1702368/+attachment/4909430/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1702368/+attachment/4909431/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1702368/+attachment/4909424/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1702368/+attachment/4909423/+files/CRDA.txt
--
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/1702368
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1702368/+attachment/4909427/+files/Lspci.txt
--
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/1702368
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1702368/+attachment/4909435/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1702368/+attachment/4909426/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1702368/+attachment/4909428/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1702368/+attachment/4909434/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1702368/+attachment/4909429/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1702368/+attachment/4909436/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1702368/+attachment/4909433/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1702368/+attachment/4909425/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1702368/+attachment/4909432/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
A workaround for my gvim-based hang is to not have gvim open on the
sshfs when I suspend. I don't have that option with gsd-housekeeping, so
I basically have to unmount sshfs before suspend, which breaks
everything else (eg. open bash prompts). Using "sshfs -o reconnect"
works fine except for
I'm also hitting this with:
Jul 6 08:19:25 xps kernel: [93020.924360] gsd-housekeepin D0 1729
1350 0
Creating a task against gnome-settings-daemon in case a workaround is
possible.
** Also affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
--
You
Hello Mike, or anyone else affected,
Accepted qemu into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:2.5+dfsg-
5ubuntu10.13 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
The current verification-done tag looks like it is intended for Zesty
only, and the Xenial proposed package still needs verification.
** Tags removed: verification-done
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Kernel
Packages,
Adding a task for Xenial as requested on IRC. But note that I haven't
looked into the details of the proposed fix - in particular checking for
and understanding any proposed change in behaviour for Xenial users. So
please don't take this as a +1 from ~ubuntu-sru. Before accepting this
SRU, please
*** This bug is a duplicate of bug 1452016 ***
https://bugs.launchpad.net/bugs/1452016
** This bug has been marked a duplicate of bug 1452016
uvtool-libvirt needs arch specific templates
--
You received this bug notification because you are a member of Kernel
Packages, which is
Could someone look at the autopkgtest failures listed against iproute2
in http://people.canonical.com/~ubuntu-archive/pending-sru.html please?
IIRC, firejail on s390x is a false positive? But there are some others,
too.
Also, has anyone done a quite smoke on amd64 to make sure the "ip"
command
*** This bug is a duplicate of bug 1452016 ***
https://bugs.launchpad.net/bugs/1452016
** This bug has been marked a duplicate of bug 1452016
uvtool-libvirt needs arch specific templates
--
You received this bug notification because you are a member of Kernel
Packages, which is
Blocked on:
* SRU paperwork
* Fixes for future stable releases
* Fix for Bionic
I understand that this was being treated as urgent. But it's been eight
days, and so if this were still the case I'd have expected the other
essential pieces to have been completed by now. I'm not sure it can be
12:58 apw: no SRU paperwork in bug 1737640? I don't know how to
check that the SRU verification minimises regression risk.
--
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/1737640
Thanks. That all looks fine then.
> Regarding amd64 smoke test, I've been using the updated package on my
machine (artful/amd64).
Does that actually exercise the ip command though? Or are you using
Network Manager, and does it speak to the kernel directly?
--
You received this bug notification
Thanks. That's useful information.
On Fri, Feb 02, 2018 at 10:17:37AM -, David JM Emmett wrote:
> "Warning failed to create cache: usr.sbin.sssd" before the instance
That sounds AppArmor related perhaps?
--
You received this bug notification because you are a member of Kernel
Packages,
If this problem comes and goes as you switch kernel, this points to a
possible kernel regression. In that case perhaps sssd is just the
trigger rather than the buggy package. So I'll add the kernel package to
this bug.
Or perhaps it's a latent bug in sssd that only triggers with the newer
kernel
The verification of the Stable Release Update for openvswitch has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This is in the SRU queue for Bionic. Does it need rejecting from there
if the bug is already fixed in Bionic? If not, then please could you
clarify and fix the bug statuses?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
Hello Po-Hsu, or anyone else affected,
Accepted lttng-modules into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/lttng-
modules/2.10.5-1ubuntu1.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Does this package work correctly against the equivalent kernels in
Bionic and Cosmic please? Obviously they'd be different versions, but
I'd like to ensure the spirit of the SRU rule about being fixed in the
development release to avoid a regression where a user uses a particular
kernel flavor,
Hello Ian, or anyone else affected,
Accepted bluez into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bluez/5.48-0ubuntu3.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
The verification of the Stable Release Update for iproute2 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
The verification of the Stable Release Update for iproute2 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
What version of makedumpfile was used for SRU verification please?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1658733
Title:
Ubuntu 16.04 KVM:kdump fails to mount root file
What version of makedumpfile was used for SRU verification please?
--
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/1635597
Title:
Ubuntu:talclp1: Kdump failed with multipath disk
Thank you for filing this report.
uvtool is just a wrapper for libvirt. Either we need libvirt support
first, or this is a wishlist item for uvtool to support some customised
libvirt configuration on this particular hardware, in which case please
provide details.
** Changed in: uvtool
It's not an issue for _uvtool itself_ until the hardware is enabled and
functional in libvirt directly, and the specific Ubuntu image you need
(Xenial) works against libvirt in the Ubuntu release you need. So please
leave the bug status for uvtool Incomplete until that is done.
> What detail I
Apparently not fixed (according to original reporter), so reopening.
** Changed in: linux (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: linux (Ubuntu Xenial)
Status: Fix Released => Confirmed
** Changed in: linux-aws (Ubuntu Xenial)
Status: Fix Released =>
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Reassigning to the kernel since rsync should never be able to crash the
system and if it crashes it's usually the kernel or bad hardware that's
responsible.
** Package changed: rsync (Ubuntu) => linux (Ubuntu)
Thank you for checking that this doesn't introduce a regression on
unaffected hardware.
Note that we don't currently have a verification for the actual reason
this is being SRU'd, which is "rfkill keyboard shortcuts not working as
intended on some Dell machines".
--
You received this bug
1 - 100 of 239 matches
Mail list logo
