This bug was fixed in the package linux - 4.4.0-36.55
---
linux (4.4.0-36.55) xenial; urgency=low
[ Stefan Bader ]
* Release Tracking Bug
- LP: #1612305
* I2C touchpad does not work on AMD platform (LP: #1612006)
- SAUCE: pinctrl/amd: Remove the default de-bounce time
This bug was fixed in the package linux - 3.19.0-68.76
---
linux (3.19.0-68.76) vivid; urgency=low
[ Stefan Bader ]
* Release Tracking Bug
- LP: #1612550
* CVE-2016-5696
- tcp: make challenge acks less predictable
linux (3.19.0-67.75) vivid; urgency=low
[ Stefan Ba
** Changed in: kernel-sru-workflow/promote-to-security
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.
https://bugs.launchpad.net/bugs/1612738
Title:
linux-ti-omap4: 3
--- Comment From gbert...@br.ibm.com 2016-08-29 10:30 EDT---
(In reply to comment #55)
> This bug was fixed in the package linux - 4.4.0-36.55
--- Comment From gbert...@br.ibm.com 2016-08-29 10:30 EDT---
(In reply to comment #56)
> (In reply to comment #55)
> > This bug was fixed i
This bug was fixed in the package linux - 4.4.0-36.55
---
linux (4.4.0-36.55) xenial; urgency=low
[ Stefan Bader ]
* Release Tracking Bug
- LP: #1612305
* I2C touchpad does not work on AMD platform (LP: #1612006)
- SAUCE: pinctrl/amd: Remove the default de-bounce time
Public bug reported:
This bug is for tracking the 3.13.0-96.143~precise1 upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties
This bug was fixed in the package linux - 3.2.0-109.150
---
linux (3.2.0-109.150) precise; urgency=low
[ Stefan Bader ]
* Release Tracking Bug
- LP: #1612732
* CVE-2016-5696
- tcp: make challenge acks less predictable
linux (3.2.0-108.149) precise; urgency=low
[ St
** Changed in: kernel-sru-workflow/promote-to-security
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/1612715
Title:
linux: 3.13.0-95.142 -prop
** Changed in: kernel-sru-workflow/promote-to-security
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 Ubuntu.
https://bugs.launchpad.net/bugs/1612740
Title:
linux-armadaxp: 3
** Changed in: kernel-sru-workflow/promote-to-security
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/1612550
Title:
linux: 3.19.0-68.76 -propo
Derivative packages from packages here can be worked on, the following tracking
bugs were opened for them:
linux-keystone - bug 1618090
Backport packages from packages here can be worked on, the following tracking
bugs were opened for them:
linux-lts-trusty (precise1) - bug 1618093
** Changed i
This bug was fixed in the package linux - 4.4.0-36.55
---
linux (4.4.0-36.55) xenial; urgency=low
[ Stefan Bader ]
* Release Tracking Bug
- LP: #1612305
* I2C touchpad does not work on AMD platform (LP: #1612006)
- SAUCE: pinctrl/amd: Remove the default de-bounce time
This bug was fixed in the package linux - 4.4.0-36.55
---
linux (4.4.0-36.55) xenial; urgency=low
[ Stefan Bader ]
* Release Tracking Bug
- LP: #1612305
* I2C touchpad does not work on AMD platform (LP: #1612006)
- SAUCE: pinctrl/amd: Remove the default de-bounce time
Public bug reported:
On waking up from suspend, the display stays black. I cannot switch to
the console, nor kill the x server. After a while the laptop reboots
itself, or alternatively, I power it off.
It does not happen on every suspend, but very often. I happens most of
the times when the lapt
This bug was fixed in the package linux - 4.4.0-36.55
---
linux (4.4.0-36.55) xenial; urgency=low
[ Stefan Bader ]
* Release Tracking Bug
- LP: #1612305
* I2C touchpad does not work on AMD platform (LP: #1612006)
- SAUCE: pinctrl/amd: Remove the default de-bounce time
This bug was fixed in the package linux - 4.4.0-36.55
---
linux (4.4.0-36.55) xenial; urgency=low
[ Stefan Bader ]
* Release Tracking Bug
- LP: #1612305
* I2C touchpad does not work on AMD platform (LP: #1612006)
- SAUCE: pinctrl/amd: Remove the default de-bounce time
This bug was fixed in the package linux - 3.13.0-95.142
---
linux (3.13.0-95.142) trusty; urgency=low
[ Stefan Bader ]
* Release Tracking Bug
- LP: #1612715
* CVE-2016-5696
- tcp: make challenge acks less predictable
linux (3.13.0-94.141) trusty; urgency=low
[ Stef
This bug was fixed in the package linux - 3.2.0-109.150
---
linux (3.2.0-109.150) precise; urgency=low
[ Stefan Bader ]
* Release Tracking Bug
- LP: #1612732
* CVE-2016-5696
- tcp: make challenge acks less predictable
linux (3.2.0-108.149) precise; urgency=low
[ St
This bug was fixed in the package linux - 4.4.0-36.55
---
linux (4.4.0-36.55) xenial; urgency=low
[ Stefan Bader ]
* Release Tracking Bug
- LP: #1612305
* I2C touchpad does not work on AMD platform (LP: #1612006)
- SAUCE: pinctrl/amd: Remove the default de-bounce time
This bug was fixed in the package linux - 4.4.0-36.55
---
linux (4.4.0-36.55) xenial; urgency=low
[ Stefan Bader ]
* Release Tracking Bug
- LP: #1612305
* I2C touchpad does not work on AMD platform (LP: #1612006)
- SAUCE: pinctrl/amd: Remove the default de-bounce time
This bug was fixed in the package linux - 4.4.0-36.55
---
linux (4.4.0-36.55) xenial; urgency=low
[ Stefan Bader ]
* Release Tracking Bug
- LP: #1612305
* I2C touchpad does not work on AMD platform (LP: #1612006)
- SAUCE: pinctrl/amd: Remove the default de-bounce time
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 kernel[0
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
**
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 kernel[0
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 kernel[0
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => Confirmed
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: New => Confirmed
--
You received this bug notificat
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 kernel[0
** Changed in: kernel-sru-workflow/promote-to-security
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 Ubuntu.
https://bugs.launchpad.net/bugs/1612564
Title:
linux-lts-vivid:
** Changed in: kernel-sru-workflow/promote-to-security
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 Ubuntu.
https://bugs.launchpad.net/bugs/1612718
Title:
linux-lts-trust
Derivative packages from packages here can be worked on, the following tracking
bugs were opened for them:
linux-raspi2 - bug 1618099
linux-snapdragon - bug 1618100
Backport packages from packages here can be worked on, the following tracking
bugs were opened for them:
linux-lts-xenial (14.04.1)
Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel d
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 kernel[0
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 kernel[0
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 kernel[0
** 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/1617599
Title:
Resume from suspend causes reboot, except if USB key is plu
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Tags added: kernel-dakye
** Tags removed: kernel-dakye
** Tags added: kernel-da-key
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Kernel
Pac
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
**
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
**
** Changed in: kernel-sru-workflow/promote-to-security
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/1612732
Title:
linux: 3.2.0-109.150 -prop
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 kernel[0
We can perform a kernel bisect to identify the commit that introduced
this bug. Can you first test the latest upstream stable 4.4 kernel to
see if this bug is already fixed? It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.19/
It might also be good to test the latest
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1607153
Title:
Mic mute key does not work for Ideapad laptops
Stat
Can you see if this issue also happens with the latest daily image? It can be
downloaded from:
http://cdimage.ubuntu.com/daily-live/current/
Also, can you see if this happens with the 16.04.1 image:
http://www.ubuntu.com/download/server
** Changed in: linux (Ubuntu)
Importance: Undecided =>
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 kernel[0
Thanks. So we now know 4.4.0-22 is good and 4.4.0-25 is bad. Can you
next try 4.4.0-23 and 4.4.0-24:
4.4.0-23: https://launchpad.net/ubuntu/+source/linux/4.4.0-8.23/+build/9059173
4.4.0-24: https://launchpad.net/ubuntu/+source/linux/4.4.0-9.24/+build/9279168
--
You received this bug notificat
Quoting Joseph Salisbury :
> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular problem?
It was a fresh install of xenial, I just got the laptop a short while
ago and installed ubuntu in virtualbox, but now I wa
linux| 3.13.0-93.140 | trusty-updates | source
linux-meta | 3.13.0.93.100 | trusty-updates | source
linux-signed | 3.13.0-93.140 | trusty-updates | source
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progress => Fix Committed
--
You received this bug
linux| 3.19.0-66.74 | vivid-updates| source
linux-meta | 3.19.0.66.64 | vivid-updates| source
linux-signed | 3.19.0-66.74 | vivid-updates| source
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
linux-lts-vivid| 3.19.0-66.74~14.04.1 | trusty-updates | source
linux-meta-lts-vivid | 3.19.0.66.48 | trusty-updates | source
linux-signed-lts-vivid | 3.19.0-66.74~14.04.1 | trusty-updates | source
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progr
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for track
Danilo Silva, it will help immensely if you filed a new report with the Ubuntu
repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.
--
You received t
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => Confirmed
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: New => Confirmed
** Description changed:
This bug
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for track
linux | 3.2.0-107.148 | precise-updates | source
linux-meta| 3.2.0.107.123 | precise-updates | source
linux-backports-modules-3.2.0 | 3.2.0-107.99 | precise-updates | source
--
You received this bug notification because you are a member of Kernel
I tested on kernel 4.4.19-040419 and the bug seems to be gone.
** Tags added: kernel-fixed-upstream
** 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.
htt
linux-lts-trusty| 3.13.0-93.140~precise1 | precise-updates | source
linux-meta-lts-trusty | 3.13.0.93.84 | precise-updates | source
linux-signed-lts-trusty | 3.13.0-93.140~precise1 | precise-updates | source
** Changed in: kernel-sru-workflow/promote-to-updates
Stat
linux-armadaxp | 3.2.0-1670.96 | precise-updates | source
linux-meta-armadaxp | 3.2.0.1670.86 | precise-updates | source
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ker
linux-ti-omap4 | 3.2.0-1485.112 | precise-updates | source
linux-meta-ti-omap4 | 3.2.0.1485.80 | precise-updates | source
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of K
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for tra
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for tra
Saif Taifur Anwar, as per http://www.acer.com/ac/en/US/content/drivers
an update to your computer's buggy, insecure, and outdated BIOS is
available (1.16). When you update to this following
https://help.ubuntu.com/community/BIOSUpdate how does this improve the
situation?
For more on BIOS updates a
L'Africain, it will help immensely if you filed a new report with the Ubuntu
repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.
--
You received thi
linux| 4.4.0-34.53 | xenial-updates | source
linux-meta | 4.4.0.34.36 | xenial-updates | source
linux-signed | 4.4.0-34.53 | xenial-updates | source
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progress => Fix Committed
** Changed in: kernel-sru-
manitou, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603397/comments/23
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line
Can you also give the latest 4.4 upstream stable kernel a test? It is
available from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.19/
--
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bcmwl (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1618033
** Changed in: bcmwl (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1618033
Title:
fails to build on 4.6 kernel
Status in bcmwl package
Lars Peter Thomsen, to clarify, did this issue not occur in a release
prior to 16.04?
--
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/1600624
Title:
MacBook wifi doesn't work (brcmfmac)
I'm pretty sure this is related to copy up. For some reason, when
unlinking a file in the lowerdir that isn't in the upperdir overlayfs
first copies up the file from the lowerdir, then replaces it with a
whiteout. There are a couple of problems with letting the user create
the inode in the upperdir
V B, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1567237/comments/39
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and
** Tags added: bios-outdated-f9
--
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/1618001
Title:
My computer reboots instead of shutting down
Status in linux package in Ubuntu:
Incomplet
Chris J Arges, the issue you are reporting is an upstream one. Could you
please report this problem following the instructions verbatim at
https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing
list (TO Dmitry Torokhov CC linux-input)?
Please provide a direct URL to your post to t
EvilWayz, to keep this relevant to upstream, one will want to test the
latest mainline kernel (now 4.8-rc3) as they are released.
Could you please advise?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
Thor H. Johansen, it will help immensely if you filed a new report with the
Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.
--
You receiv
The problem started happening as soon as I did the (fresh) Ubuntu 16.04
install.
Previously, the computer had been running 14.04, and the computer would
properly shut down as long as no USB medium (stick or disk) was
connected when I initiated the shutdown. I got into the habit of
disconnecting al
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for tra
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for tra
I spent some time investigating our issue further.
As far as I can tell, the main issue is that ioctl(FIFREEZE) can take a long
time when running VSS backups, and the default timeout is 10s.
This is very noticeable under load, with rare peaks of >5s seen, so 10s seem
plausible
If the timeout is
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for tra
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for tra
@faulpletz Do you mean with "and the guest systems continue to work
normally" that the guest does not have any read-only problems any more
with your patch?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
You have been subscribed to a public bug:
monklp3 is installed with ubuntu 14.04.4. System crashed and dropped
into xmon at pcibios_release_device+0x5c/0x80 during running dlpar
test(CPU, MEM and SLOT).
The output from vterm:
[ 1333.379900] lpfc 0005:a0:00.1: 2:1303 Link Up Event x1 received Dat
Default Comment by Bridge
** Attachment added: "xmon log"
https://bugs.launchpad.net/bugs/1618151/+attachment/4730172/+files/136402.log
** Changed in: ubuntu
Assignee: (unassigned) => Taco Screen team (taco-screen-team)
** Package changed: ubuntu => linux (Ubuntu)
--
You received this
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xfce4-power-manager (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/
@Frederik: yes, as far as I have seen. The file systems are still frozen
between FREEZE and THAW, which in the case of timeouts, is >10s, I have seen
about 30s in some of our error cases. But they do recover.
I only tried the patched 4.4.0-34 version for now, though
Some testing would be apprecia
Christopher what would you to know?
It's difficult for me to do a report because when the "freeze" happens I can do
anything?? Maybe I can try with this file /var/log/kern.log?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
I no longer use Cinnamon, I still use Blueberry, and it works with
4.7rc3. However, I must switch each pulseaudio stream manually to the
bluetooth device after it has connected, it doesn't switch
automatically.
--
You received this bug notification because you are a member of Kernel
Packages, wh
Public bug reported:
This bug is for tracking the 3.19.0-69.77 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
** Affects: kernel-sru-workf
Just tested with v4.8-rc3:
$ uname -a
Linux wkst1 4.8.0-040800rc3-generic #201608212032 SMP Mon Aug 22 00:34:39 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux
The problem persists.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you
Thank you for the detailed explanation.
Since the underlying problem is that overlayfs is not (yet very)
namespace aware, this issue may be intractable.
Naive question regarding copy-up: Do the files in the upperdir and
lowerdir need to have the same owner? If not, could copy-up be amended
so t
Public bug reported:
This bug is for tracking the 3.19.0-69.77~14.04.1 upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Backport packages from packages here can be worked on, the following tracking
bugs were opened for them:
linux-lts-vivid (14.04.1) - bug 1618176
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Changed in: kernel-sru-workflow/prepare-package-meta
Statu
On Mon, Aug 29, 2016 at 06:26:54PM -, oleg wrote:
> Naive question regarding copy-up: Do the files in the upperdir and
> lowerdir need to have the same owner? If not, could copy-up be amended
> so that it behaves similarly to the copying of a root-owned file by a
> non-root user? Ie the owne
@timg-tpi, the commits mentioned by Adrian above are actually to the
ixgbevf driver, updating that VF driver for Hyper-V, not Hyper-V itself.
It is a driver we can update as part of this process or should I file a
separate LP? The commits have been upstream since April.
--
You received this bug n
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => Confirmed
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: New => Confirmed
** Description changed:
This bug
Recently I've tried to use this instruction -
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511019/comments/8
If it will be unuseful, I capture it after a new freeze.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
You have been subscribed to a public bug:
== Comment: #0 - Ofer Baruch - 2016-08-28 07:41:53 ==
When you set the memory size of a Ubuntu Guest to a number which is not a
multiple of the memory block size (in our case 256MB) there are missing memory
slots at /sys/bus/memory/devices.
for example
Default Comment by Bridge
** Attachment added: "bdginfo from the Ubuntu guest"
https://bugs.launchpad.net/bugs/1618203/+attachment/4730220/+files/DBGINFO-2016-08-28-06-32-42-UBU9LT1-0A73E6.tgz
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
**
** Tags added: patch
--
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/1470250
Title:
[Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
Backups
Status in linux package i
It looks it's fixed in mainline kernel, now it's not happening. Note
that I tried v4.8 rc3
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
101 - 200 of 258 matches
Mail list logo
