** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee
(sforshee)
** Changed in: kernel-sru-workflow/prepare-package-meta
The patch has just been applied to the kernel.org git.
--
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/1605974
Title:
usbduxsigma_firmware.bin: old version causes driver crash
Hi again,
Still same problem, wakeup from hibernation freezes at some time, with latest
kernel (4.4.0-31),
that is to say the system becomes totally unresponsive, the screen may go black
or not.
It seems that the system is not always able to write something in logs when
this occurs :
in
Public bug reported:
Servers periodically became unresponsive, and report the following
problem:
Jul 28 01:26:36 osd1-05 kernel: [1644406.270794] kworker/12:2D
88085fcd3180 0 25000 2 0x
Jul 28 01:26:36 osd1-05 kernel: [1644406.270813] Workqueue: dio/bdev
I have an E4.5 and with OTA-12 I can't pair to C4 Citroen.
Time ago I did some tests. When the phone detect a car tried to match it. Now
their names still appear. This is very strange.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
As a non-LTS release, 15.10 has a 9-month month support cycle and, as
such, the support period is now nearing its end and Ubuntu 15.10 will
reach end of life on Thursday, July 28th. At that time, Ubuntu Security
Notices will no longer include information or updated packages for
Ubuntu 15.10.
**
This also affects our environment running on Ubuntu 14.04 /
3.13.0-65-generic. During an unattended upgrade os-prober scans all
filesystems. After this the upgrade hangs on modprobe btrfs, resulting
in a stalled upgrade.
Because of this automatic security updates/upgrades will not take place.
--
This change was made by a bot.
** 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.
https://bugs.launchpad.net/bugs/1607239
Title:
mdadm raid gets frozen
Hi,
I can't tell you whether the issue started after an update/upgrade sorry
- I've only noticed it recently.
I've installed the 4.7 upstream kernel and the bug is still exhibited:
eddie@codey:~$ uname -a
Linux codey 4.7.0-040700-generic #201607241632 SMP Sun Jul 24 20:34:30 UTC 2016
x86_64
As a non-LTS release, 15.10 has a 9-month month support cycle and, as
such, the support period is now nearing its end and Ubuntu 15.10 will
reach end of life on Thursday, July 28th. At that time, Ubuntu Security
Notices will no longer include information or updated packages for
Ubuntu 15.10.
**
Hey,
I'll try to help a bit here.
First as for the unknown or unwanted entries on the paired devices lists
[and such] you can try to remove them from the bluetoothctl level.
) enable developers mode & connect it via usb cable
) login with adb shell to the deivce
) type $ bluetoothctl
) then
As a non-LTS release, 15.10 has a 9-month month support cycle and, as
such, the support period is now nearing its end and Ubuntu 15.10 will
reach end of life on Thursday, July 28th. At that time, Ubuntu Security
Notices will no longer include information or updated packages for
Ubuntu 15.10.
**
As a non-LTS release, 15.10 has a 9-month month support cycle and, as
such, the support period is now nearing its end and Ubuntu 15.10 will
reach end of life on Thursday, July 28th. At that time, Ubuntu Security
Notices will no longer include information or updated packages for
Ubuntu 15.10.
**
http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-
firmware.git/log/usbduxsigma_firmware.bin
--
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/1605974
Title:
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
--
You received this bug notification because you are a
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1607356
Title:
package linux-image-3.5.0-54-generic 3.5.0-54.81~precise1 failed to
install/upgrade:
** Patch added:
"0001-UBUNTU-SAUCE-namespace-fuse-Permit-requests-from-oth.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605344/+attachment/4708792/+files/0001-UBUNTU-SAUCE-namespace-fuse-Permit-requests-from-oth.patch
--
You received this bug notification because you are a
** Description changed:
+ SRU Justification
+
+ Impact: The pid namespace support in fuse refuses requests from any
+ process whose pid does not map into the pid namespace of the fuse
+ userspace process. This has caused a regression for at least one user.
+
+ Fix: Permit requests from
You have been subscribed to a public bug:
== Comment: #17 - Guilherme Guaglianoni Piccoli - 2016-07-27 18:49:08 ==
Temperature and fan information from hardware are normally available to
userspace through hwmon sysfs abstraction. In case of be2net driver, all PCI
devices "managed" by this
Public bug reported:
== Comment: #17 - Guilherme Guaglianoni Piccoli - 2016-07-27 18:49:08 ==
Temperature and fan information from hardware are normally available to
userspace through hwmon sysfs abstraction. In case of be2net driver, all PCI
devices "managed" by this driver have hwmon entries,
Public bug reported:
... someone replaced my init-functions with an HTML file :-o
Waht an a..hole !
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: linux-image-3.5.0-54-generic 3.5.0-54.81~precise1
ProcVersionSignature: Ubuntu 3.5.0-54.81~precise1-generic 3.5.7.33
Uname: Linux
Public bug reported:
SRU Justification
Impact: The xenfs filesystem is traditionally mounted at /proc/xen in
xen guests. This directory doesn't use the special "create proc
mountpoint" interface and thus fails the permanently empty test in
fs_fully_visible(). This causes mounting of proc to fail
** Summary changed:
- [LTCTest][Opal][FW860] Ubuntu: lm-sensors is throwing "ERROR: Can't get value
of subfeature temp1_input: I/O error" for be2net driver
+ lm-sensors is throwing "ERROR: Can't get value of subfeature temp1_input: I/O
error" for be2net driver
--
You received this bug
I've uploaded the patch to xenial-proposed too. Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1548009
Title:
ZFS pools should be automatically scrubbed
Status in
Public bug reported:
I've recently installed ubuntu 16.04 LTS twice -and i discovered that
the problem was from the tool katoolin so i didn't install it- after i
installed ubuntu the bluetooth didn't work for me.
P.S:the bluetooth was working when my laptop was ubuntu 15.04
when i turn
Using my simpler testing I found that the problem first started
occurring in 15.10
I also noticed this is also when the "Disable while typing" option was
removed.
I hope this helps, I will be able to test any new upstream releases pretty
quickly
(Now that I have done it once :) )
** Tags
Public bug reported:
I was able to reproduce this 2 or 3 times last 2 days. I have the
following setup:
Containers for Trusty/kilo service machines:
inaddy@workstation:~$ lxc-ls | grep tk
tkcephmon01 RUNNING 0 - 192.168.65.52 -
tkcephmon02 RUNNING 0 -
Hi,
I have the Lenovo T440p with integrated intel and nvidia, and I encounter the
same symptoms than deb2014.
The log is also with symbols.
It's ramdomly crashed with a black screen or works after hibernating no more
than 2-3 times.
Moreover, it crashs every time I plug in to the
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1607355
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
Thanks for the help. After a while modprobe btrfs hangs again,
specifically on "insmod
/lib/modules/3.13.0-88-generic/kernel/lib/raid6/raid6_pq.ko" and "insmod
/lib/modules/3.13.0-88-generic/kernel/fs/btrfs/btrfs.ko". Even after
installing btrfs-tools.
--
You received this bug notification
I think the fix for this crash is this upstream commit:
8329e818f14926a6040df86b2668568bde342ebf
--
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/1605843
Title:
Kernel crashes from time
Original report of the exact same issue:
https://lkml.org/lkml/2016/5/13/327
--
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/1605843
Title:
Kernel crashes from time to time when using
** Patch added:
"0001-UBUNTU-SAUCE-xenbus-Use-proc_create_mount_point-to-c.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607374/+attachment/4708767/+files/0001-UBUNTU-SAUCE-xenbus-Use-proc_create_mount_point-to-c.patch
** Changed in: linux (Ubuntu Xenial)
Importance:
Hi guys. I am happy about finding this page. I had the same issue with
my new Dell Bluetooth Mouse WM615 but after using your suggestions, it's
working well now.
What I did are
- editing /etc/bluetooth/main.conf as it is said in #25
- editing /lib/udev/rules.d/50-bluetooth-hci-auto-poweron.rules
Default Comment by Bridge
** Attachment added: "dmesg output"
https://bugs.launchpad.net/bugs/1607325/+attachment/4708674/+files/system_log.txt
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Package changed: ubuntu => linux (Ubuntu)
--
Thanks Foppe. A few questions:
Does blacklisting the btrfs module work around the problem?
What does the output of `blkid` return for this machine?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
blkid gives me /dev/vda1: LABEL="cloudimg-rootfs" UUID="1ff353c2-3fed-
48fb-acc0-6d18086d030b" TYPE="ext4"
After blacklisting btrfs and restarting it gives me the message "[1]
1360 segmentation fault modprobe btrfs" after running "modprobe btrfs".
But it does not hang anymore.
--
You received
Hi,
I have installed these packages, but I still observer this issue:
kamil@host:~$ sudo lspci | grep Volatile
[sudo] password for kamil:
03:00.0 Non-Volatile memory controller: Intel Corporation PCIe Data Center SSD
(rev 01)
04:00.0 Non-Volatile memory controller: Intel Corporation PCIe Data
** Also affects: zfs-linux (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1548009
Title:
ZFS pools should be
Hey,
the procedure is not very difficult and once all the tools are installed it
is straightforward however if you do not feel confident, given that it is
not certain that it will help for issues with cars, I would recommend
waiting till OTA-13.
Best,
Konrad
On Thu, Jul 28, 2016 at 1:05 PM,
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin16041
--
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/1607325
Title:
Ubuntu 16.04 running on z13 hardware is
Public bug reported:
got this error by making a "sudo apt-get update && sudo apt-get dist-
upgrade"
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-firmware 1.157
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion:
Hi Konrad,
thank you for your answer, I will try to apply the procedure that you
have described during this weekend.
I never installed a silos, so maybe it's better to wait the OTA-13 that
incude bluez 5.41.
Thank you,
Marco
Il 28/07/2016 10:54, Konrad Zapałowicz ha scritto:
> Hey,
>
> I'll
You have been subscribed to a public bug:
Problem Description
===
system Z Ubuntu 16.04 LTS can not correctly configured DS8870 2107 LUNs.
---uname output---
Linux ilabg3 4.4.0-33-generic #52-Ubuntu SMP Fri Jul 22 19:17:00 UTC 2016 s390x
s390x s390x GNU/Linux
Hi Kamil,
It looks like the kernel issue is resolved. Your drive just appears to
be in a bad state and the driver reacts accordingly.
I think this launchpad's issue is resolved and should request the fix go
forward.
--
You received this bug notification because you are a member of Kernel
This patch adds /usr/local/bin and /usr/local/sbin to the path. Given
the utilities in use are all official binaries this seems unexpected and
a potential security risk.
** Changed in: zfs-linux (Ubuntu Xenial)
Status: New => Incomplete
--
You received this bug notification because you
Kamil,
For your issue, this is potentially a bug specific to the 4.5 driver. We
used to poll once a second, which would hide legacy irq issues during
initialization, but 4.5 removed it. A patch[*] to 4.6 removed all use of
legacy interrupts, and should have been applied to 4.5 stable (they were
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
*** This bug is a duplicate of bug 1588946 ***
https://bugs.launchpad.net/bugs/1588946
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
precise' to 'verification-done-precise'.
If verification is not done by 5 working days
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
Hello Richard, or anyone else affected,
Accepted zfs-linux into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/0.6.5.6-0ubuntu11 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
This should be rejected for Xenial and reverted for Yakkety and a more
minimal path used.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1548009
Title:
ZFS pools should be
Just happened two days ago on Trusty 14.04.4 with Linux 4.4.0-31 on one
of Ceph Jewel OSD server. It ran fine for 8 days though and suddenly the
CPU load spiked to 600.
The server is from SuperMicro SuperStorage Server SSG-6048R-E1CR36L with these
following specs:
2x Intel Xeon E5-2630 v3 @
I get not wanting unnecessary PATHs... But is /usr/local really
considered a security issue? It's in /usr...
It's part of the standard PATH for the root user. And if an admin has
installed tools in /usr/local, wouldn't they expect them to be used?
--
You received this bug notification
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (inaddy)
--
You received this bug notification because you are a member of
Ok, comparing this to other users of /etc/cron.d it does seem to be a
common idiom used there. To update the path to exactly the above form.
So this is not making things any worse. I am inclined to let this go on
that basis given it is already in yakkety.
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
FYI, this is a requirement for snapd, but it was deprioritized in favor
of namespace stacking in support of LXD, upstreaming and other work in
support of snappy (eg, gsettings mediation). A lot of work was done to
support this, but the soonest it would be delivered given current
priorities is
Maybe this will help, Bugzilla Gnome-Shell memory leak bugs:
Bug 735705 Summary -Memory usage of gnome-shell increasing to X GiB (heap)
https://bugzilla.gnome.org/show_bug.cgi?id=735705
Bug 709451 -gnome-shell memory leaks
https://bugzilla.gnome.org/show_bug.cgi?id=709451
Bug 701230 - Summary:
Would it not make more sense to have /usr/lib/zfs-linux/scrub set the
PATH that it requires in order to find the zpool command?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1548009
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
/usr/local/bin and /usr/local/sbin are not required for anything zfs
specific, so given that they are redundant they should not be added to
the PATH. Plus the security issue as mentioned above.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
precise' to 'verification-done-precise'.
If verification is not done by 5 working days
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
precise' to 'verification-done-precise'.
If verification is not done by 5 working days
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
Could /usr/lib/zfs-linux/scrub not just give the full path to zpool
instead? Then PATH wouldn't need modifying at all.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1548009
Title:
The (1) onexec test problem is tracked in bug #1528230. Please use this
bug to track the (2) exec_qual test failure or problem.
--
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/1543461
Debdiff for Yakkety (16.10)
** Patch added: "Debdiff for Yakkety (16.10)"
https://bugs.launchpad.net/ubuntu/xenial/+source/zfs-linux/+bug/1574342/+attachment/4708820/+files/lp1574342_yakkety.debdiff
** Tags added: patch sts
--
You received this bug notification because you are a member of
Acknowledged, we will verify and revert.
--
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/1590655
Title:
[Hyper-V] storvsc messages for CD-ROM medium not present tray closed
Status in
I just tested the suspend to ram (sorry I misunderstood this option in my own
language), it works.
The tip is that if the laptop is on the dockstation and I suspend it to ram,
after wakeup I have to unplug and replug it, to bypass the black screen.
--
You received this bug notification because
Acknowledged, we will verify and revert.
--
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/1583357
Title:
[Hyper-V] Rebase Hyper-V to 4.6 kernel
Status in linux package in Ubuntu:
Fix
1 - 100 of 228 matches
Mail list logo
