Hello,
I have exactly the same problem with that Hardware (HP Pavilion X2
12-b003nf), with a live CD (I don't want to definitly install it until
I'm sure it works fine).
I tried the last Ubuntu 16.10 daily (the one from october, 8th with
Kernel 4.8.0.21.30) without success.
According to the kern
4.4.0-040400-generic #201601101930 SMP Mon Jan 11 00:32:41 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
Kernel 4.4 does not panic but shows the following message when `ls -al`:
[ 255.901591] BTRFS error (device loop0): parent transid verify failed on
30425088 wanted 120 found 119
[ 255.902458] BTRF
the commits are in 4.8 which is in yakkety, closing
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1619756
Title:
@mmifas,
Thank you for your testing result, and It looks like the headphone
(0x21) can't detect the plug/unplug. I have no idea why this happened.
I already asked for help from Realtek technical expert, he suggested we
turn on the hidden register (0x20), then generate an alsa-info.txt.
To do so,
** Changed in: linux-lts-xenial (Ubuntu Xenial)
Assignee: Eric Desrochers (slashd) => (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/1572630
Title:
boot-time kernel pan
Same here:
[ 8246.703778] usb 3-2: new full-speed USB device number 3 using ohci-pci
[ 8246.989449] usb 3-2: New USB device found, idVendor=046d, idProduct=0a29
[ 8246.989458] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 8246.989462] usb 3-2: Product: Logitech Wireless Heads
** Changed in: linux (Ubuntu)
Status: Incomplete => Opinion
** Changed in: linux (Ubuntu)
Status: Opinion => Confirmed
** Description changed:
Ubuntu 16.04 on 64 bit produces hissing sound (just by my - far from
being 'musical' - ear, it sounds like a sinus wave with frequency
I read this full issue report and replies and it seems I am experienced
an analogous problem. Should I report the details of my case here or
open a new issue?
Here are few initial information:
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
R
Marking this bug fix released as all the bits we wanted done here have
been done.
We still have a separate bug open for the dependency on squashfuse and
its SRU to xenial.
** Changed in: snappy
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
Hi Christopher,
I found the culprit and can confirm this is not a bug with the kernel
4.4.0.38. I attached a Sony PlayTV usb dvb tuner (dib0700) a little
while ago. I use it with TVHeadend which is installed as a background
service. After disconnecting it the system suspend/resume was working
perf
** Changed in: linux (Ubuntu Trusty)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Yakkety)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a m
hey guys,
I have the same problem with debian jessie and the current proxmox
kernel 4.4.x. I reported some things about the my problem here:
https://github.com/zfsonlinux/zfs/issues/4638
There is also another interesting bug report:
https://github.com/zfsonlinux/zfs/issues/3785
Greetings Hoppe
Public bug reported:
---Problem Description---
vios vfc unmap (vfcmap -vadapter vfchost0 -fcp) can result in no i/o being
retried nor device offline.
---uname output---
Linux ubuntu16 4.4.0-9136-generic #55-Ubuntu SMP Fri Aug 26 05:56:24 UTC 2016
ppc64le ppc64le ppc64le GNU/Linux
Machine Ty
You have been subscribed to a public bug:
---Problem Description---
vios vfc unmap (vfcmap -vadapter vfchost0 -fcp) can result in no i/o being
retried nor device offline.
---uname output---
Linux ubuntu16 4.4.0-9136-generic #55-Ubuntu SMP Fri Aug 26 05:56:24 UTC 2016
ppc64le ppc64le ppc64le G
** Changed in: kernel-sru-workflow
Status: In Progress => 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/1626604
Title:
linux: 3.13.0-97.144 -proposed tracker
Status
** Changed in: linux-armadaxp (Ubuntu Precise)
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubun
** Changed in: linux-lts-vivid (Ubuntu Trusty)
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubunt
** Changed in: kernel-sru-workflow
Status: In Progress => 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/1625788
Title:
linux: 3.19.0-70.78 -proposed tracker
Status
** Changed in: linux-ti-omap4 (Ubuntu Precise)
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-ti-omap4 in Ubuntu
** Changed in: linux-lts-trusty (Ubuntu Precise)
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in Ub
** Changed in: kernel-sru-workflow
Status: In Progress => 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/1628204
Title:
linux: 4.4.0-41.61 -proposed tracker
Status i
** Changed in: kernel-development-workflow
Status: In Progress => 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/1630279
Title:
linux: 4.8.0-21.23 -proposed tracker
** Information type changed from Private Security 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/1631287
Title:
CVE-2016-7039 and CVE-2016-
Status in linux packag
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/1632081
Title:
package linux-headers-4.4.0-42
Public bug reported:
Ubuntu 4.4.0-38.57-generic 4.4.19
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-headers-4.4.0-42-generic (not installed)
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architectur
https://lists.ubuntu.com/archives/kernel-team/2016-October/080298.html
** Also affects: linux (Ubuntu Yakkety)
Importance: Undecided
Assignee: Taco Screen team (taco-screen-team)
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Chan
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workfl
@tomposmiko, the official way is to 1) file a bug report, 2) get that
fixed in the current development branch, and then 3) follow the SRU
(stable release update) process to get it backported into the LTS
release.
The hole birth thing is a mess, and I've got bug #1600060 open for that
in Ubuntu. Ho
Running the xenial kernel on trusty seems like it would be pretty risky,
since presumably far fewer people have tested that combination.
--
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/15472
And also:
https://github.com/zfsonlinux/zfs/issues/4996
fix pending here:
https://github.com/zfsonlinux/zfs/pull/5061
Debian is shipping a patch to add an ignore_hole_birth tunable (and defaulting
to on). We should get that in Ubuntu, except that we also want to rename it as
per here:
https://gi
This bug was fixed in the package linux - 3.2.0-111.153
---
linux (3.2.0-111.153) precise; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1626151
* Altering use_tempaddr drops all IPv6 addresses (LP: #994931)
- Revert "UBUNTU: SAUCE: ipv6: make the net.ipv
This bug was fixed in the package linux - 3.2.0-111.153
---
linux (3.2.0-111.153) precise; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1626151
* Altering use_tempaddr drops all IPv6 addresses (LP: #994931)
- Revert "UBUNTU: SAUCE: ipv6: make the net.ipv
This bug was fixed in the package linux - 3.2.0-111.153
---
linux (3.2.0-111.153) precise; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1626151
* Altering use_tempaddr drops all IPv6 addresses (LP: #994931)
- Revert "UBUNTU: SAUCE: ipv6: make the net.ipv
Public bug reported:
---Problem Description---
The PSL data cache should be flushed before resetting a CAPI adapter.
If the PSL data cache holds dirty cache line when it is reset, the host trying
to access that memory when the link is down may face a Uncorrectable Error
(UE), forcing a reboot of
This bug was fixed in the package linux-lts-xenial - 4.4.0-42.62~14.04.1
---
linux-lts-xenial (4.4.0-42.62~14.04.1) trusty; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro:
This bug was fixed in the package linux-lts-xenial - 4.4.0-42.62~14.04.1
---
linux-lts-xenial (4.4.0-42.62~14.04.1) trusty; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro:
You have been subscribed to a public bug:
---Problem Description---
The PSL data cache should be flushed before resetting a CAPI adapter.
If the PSL data cache holds dirty cache line when it is reset, the host trying
to access that memory when the link is down may face a Uncorrectable Error
(UE)
This bug was fixed in the package linux - 3.13.0-98.145
---
linux (3.13.0-98.145) trusty; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
* CVE-2016-7039
- SAUCE: net: add recu
This bug was fixed in the package linux - 3.13.0-98.145
---
linux (3.13.0-98.145) trusty; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
* CVE-2016-7039
- SAUCE: net: add recu
This bug was fixed in the package linux - 3.13.0-98.145
---
linux (3.13.0-98.145) trusty; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
* CVE-2016-7039
- SAUCE: net: add recu
This bug was fixed in the package linux - 3.13.0-98.145
---
linux (3.13.0-98.145) trusty; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
* CVE-2016-7039
- SAUCE: net: add recu
This bug was fixed in the package linux - 3.19.0-71.79
---
linux (3.19.0-71.79) vivid; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of
This bug was fixed in the package linux - 3.19.0-71.79
---
linux (3.19.0-71.79) vivid; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of
This bug was fixed in the package linux - 3.13.0-98.145
---
linux (3.13.0-98.145) trusty; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
* CVE-2016-7039
- SAUCE: net: add recu
This bug was fixed in the package linux - 3.13.0-98.145
---
linux (3.13.0-98.145) trusty; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
* CVE-2016-7039
- SAUCE: net: add recu
This bug was fixed in the package linux - 3.19.0-71.79
---
linux (3.19.0-71.79) vivid; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of F
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of F
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of F
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of F
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of F
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of F
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of F
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of F
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of F
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of F
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of F
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of F
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of F
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of F
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of F
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of F
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of F
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of F
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of F
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of F
*** This bug is a duplicate of bug 1628204 ***
https://bugs.launchpad.net/bugs/1628204
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't appl
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of F
*** This bug is a duplicate of bug 1628204 ***
https://bugs.launchpad.net/bugs/1628204
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't appl
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of F
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of F
** No longer affects: ubuntu-mate
--
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/1564664
Title:
Peripheral Devices (keyboard and mouse) login delay
Status in linux package in Ubuntu:
The Trusty backport does not look like it would be suitable for an SRU.
Is running linux-generic-lts-xenial an option ?
--
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/1547231
Title:
/pro
These patches have already been released:
UBUNTU: SAUCE: Ibmvscsis: Fixed a bug reported by Dan Carpenter
UBUNTU: SAUCE: Ibmvscsis: Code cleanup of print statements
UBUNTU: SAUCE: Return TCMU-generated sense data to fabric module
UBUNTU: SAUCE: Ibmvscsis: Properly deregister target sessions
** A
Live patching for powerpc/ppc64el also requires CONFIG_MPROFILE_KERNEL=y
and CONFIG_DISABLE_MPROFILE_KERNEL=n
https://lists.ubuntu.com/archives/kernel-team/2016-October/080297.html
** Changed in: linux (Ubuntu Yakkety)
Status: Fix Committed => In Progress
--
You received this bug notific
** Also affects: linux (Ubuntu Yakkety)
Importance: High
Assignee: Canonical Kernel Team (canonical-kernel-team)
Status: Fix Released
** Changed in: linux (Ubuntu Yakkety)
Status: Fix Released => In Progress
** Changed in: linux (Ubuntu Yakkety)
Assignee: Canonical Kern
I've now also asked on #ubuntu-kernel if CONFIG_ARM64_VA_BITS=48 is here
to stay for the 4.4 kernel or not, pointing to this bug. It sounds like
no-one is currently considering going back to the 4.2 kernel on the
arm64 builders at least.
Meanwhile I'm collecting rebuilds of qtdeclarative-abi-5-6-1
I had 2 freezes in a months use. I suspect the bios update has lessen
the issue. But the hard crash happened.
1. Output of the terminal is as follows:
saif@saif-Aspire-E3-112:~$ sudo dmidecode -s bios-version && sudo dmidecode -s
bios-release-date
[sudo] password for saif:
V1.16
10/20/2015
saif
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team
(canonical-kernel-team)
--
You received this bug notification bec
** Tags removed: severity-critical
** Tags added: severity-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/1626983
Title:
[Ubuntu16.10]KV4.8: kernel livepatch config options are no
Otherwise "ok" so far regarding rebuilds but unmodified UITK starts to
fail two subtests on arm64: bug #1631941. Those did pass before the
builder kernel update, and it's now not sure where those new failures
come from. But they do happen on both xenial and yakkety:
https://launchpad.net/~ci-train-
** 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/1628694
Title:
Ubuntu 16.10 bluetooth doesn't work
Status in linux pa
I was wondering about your last question myself. I can't be sure, but
the last phrase of the commit note seems to say "Yes" - "so that the top
speaker works as is."
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
> Unfortunately the upstream fix seems to, while fixing arm64, cause
segfaults in Unity 8 on armhf and i386:
It seems we need rebuilds of everything that uses qtdeclarative-private
internal headers as those changed.
--
You received this bug notification because you are a member of Kernel
Package
I see this here, with the 4.7 kernel in Debian.
$ uname -a
Linux pallas 4.7.0-1-amd64 #1 SMP Debian 4.7.5-1 (2016-09-26) x86_64 GNU/Linux
[379781.198012] hid-generic 0005:05AC:3232.004F: unknown main item tag 0x0
[379781.198089] input: YHK-Mouse as
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1
--- Comment (attachment only) From bssrika...@in.ibm.com 2016-10-10 06:08
EDT---
** Attachment added: "syslog"
https://bugs.launchpad.net/bugs/1630304/+attachment/4758626/+files/syslog.gz
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
Just a note: 4.4.0-41.61 from xenial-proposed is still broken.
--
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/1629204
Title:
Autofs parameter substitution broken in kernel 4.4.0-38 and 4
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/1631892
Title:
Broadcom b43 Wifi no longer wo
I can confirm that the 0001-autofs4-Use-real_cred-for-uid-gid-in-
packets.patch fixes the problem.
I have tried the kernel located here:
http://people.canonical.com/~sforshee/lp1629204/
And I have also applied the patch an top of the 4.4.0-38 kernel (commit
be687e48ba9778ab2f28513bd50e1b274ba31f6
Public bug reported:
I've installed the new 16.04.1 (elementaryOS Loki) - removed `wl` wifi
driver [which for some reason was installed even though I did NOT choose
the option to install non-free software (mp3, etc..)].
I then connected via ethernet, installed b43 via its `firmware-
installer` pa
Btw I booted a livecd of Ubuntu 16.04.1 with kernel 4.4.0-31 and that
can sleep/resume fine. So the issue seems to be with 4.4.0-38, at least
with me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
This bug was fixed in the package linux-firmware - 1.157.4
---
linux-firmware (1.157.4) xenial; urgency=medium
* ath10k: QCA6174: update board files (LP: #1589905)
-- Seth Forshee Wed, 14 Sep 2016 08:19:44
-0500
** Changed in: linux-firmware (Ubuntu Xenial)
Status: Fix C
The verification of the Stable Release Update for linux-firmware 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 enco
On Tue, Oct 4, 2016 at 6:25 AM Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
No - it's a new machine on which I've installed Yakkety.
Would
94 matches
Mail list logo
