I'm not sure if this makes any sense but when I booted with the
v4.1-rc3-unstable kernel it was as if the wireless card just wasn't
detected at all. No sign of it in the network manager and no option to
enable wi-fi.
There were some messages about iwlwifi firmware that appeared very
briefly during
I used to use the official supported LTS Ubuntu Trusty 3.13 kernel line.
With current updates.
I didn't noticed which subversion started to affect kernel panic after Totem
player. May be several months.
I tried to stress several times some kernels by Totem Player (play,
seek, switch playlist...):
It seems the following commit in vivid is also needed for the better
support for trusty and utopic.
Author: Seth Forshee
AuthorDate: Fri Mar 20 11:06:52 2015 -0500
Commit: Andy Whitcroft
CommitDate: Fri Mar 27 10:44:38 2015 +
HID: multitouch: Add support for button type usage
** Changed in: hwe-next
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1456881
Title:
Some touchpads' right button doesn't work under I2C mode, need sup
patch for trusty and utopic has been submitted to kernel-team@. vivid
has that commit already.
--
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/1456881
Title:
Some touchpads' right button
** Changed in: hwe-next
Assignee: Adam Lee (adam8157) => (unassigned)
** Changed in: hwe-next
Assignee: (unassigned) => Keng-Yu Lin (lexical)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpa
** Changed in: hwe-next
Importance: Undecided => High
** Changed in: hwe-next
Assignee: (unassigned) => Adam Lee (adam8157)
** Summary changed:
- Need support of clickpads
+ Some touchpads' right button doesn't work under I2C mode, need support of
clickpads
--
You received this bug no
Public bug reported:
We need to add this support, otherwise some touchpads' right button
doesn't work under I2C mode.
commit 015fdaa9f8edd89a456b3331088e1b77ebdad9d0 (patch)
HID: multitouch: add support of clickpads
Touchpads that have only one button are called clickpads and should
be advertise
[1] kvm psci v0.2 patchset
http://comments.gmane.org/gmane.linux.ubuntu.devel.kernel.general/56676
** Attachment added: "dmesg log after running 'reboot' & 'poweroff' on current
arm64 VM with the kvm psci v0.2 patchset"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455372/+attachmen
** Attachment added: "dmesg log after running 'reboot' & 'poweroff' on current
arm64 VM"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455372/+attachment/4400723/+files/dmesg-before-applying-patches.log
--
You received this bug notification because you are a member of Kernel
Packages
** Changed in: kernel-sru-workflow/verification-testing
Status: New => In Progress
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in: kernel-sru-workf
I'm attaching the two text files requested near the end of the
instructions. Apparently only one at a time can be attached.
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456873/+attachment/4400720/+files/lspci-vnvn.log
--
You received this bug n
Adding version .log.
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456873/+attachment/4400721/+files/version.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
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/1456873
Title:
3.13.0-53-generic breaks netwo
Public bug reported:
Description:Ubuntu 14.04.2 LTS
Release:14.04
I did the usual update with the graphical updater, it asked me to
reboot. I did, after logging back in things looked OK for a few short
minutes then networking completely stopped.
After several warm reboots and a cold
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad
(adconrad)
--
You received this bug notification because you are a
** Description changed:
This bug is for tracking the 3.19.0-18.18 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
kernel-stable-P
All builds are complete, packages in this bug can be copied to
-proposed.
Backport packages from packages here can be worked on, the following tracking
bugs were opened for them:
linux-lts-vivid (14.04.1) - bug 1456862
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Fix
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for tracking the 3.16.0-38.52 upload package. This bug will
contain status and testing results related to
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for tracking the 3.2.0-1650.70 upload package. This bug will
contain status and testing results related t
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for tracking the 3.2.0-84.121 upload package. This bug will
contain status and testing results related to
Remember similar stalling while booting in MacBook 2,1 issues predate the
ubuntu 3.19 kernel. They are in 3.16 and previous I think also, just not as
consistently or persistently as the in the 3.19. Would be nice for Ubuntu
to figure this out and backport all supported kernels.
On 20 May 2015 at
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for tracking the 3.13.0-53.87~precise1 upload package. This
bug will contain status and testing results r
** Changed in: hwe-next
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1448830
Title:
alsa daily dkms can't work well under ubuntu kernels (a
Wrong guess re 37ef01ab... , but there is a difference. After reaching the
usual "..Created slice..." message, instead of stalling on the message ,
the screen goes black then stalls. Still boots on recovery mode only. Must
be another or combination of commits. There are 4 or 5 i915 related ones
po
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for tracking the 3.13.0-53.88 upload package. This bug will
contain status and testing results related to
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for tracking the 3.16.0-38.52~14.04.1 upload package. This
bug will contain status and testing results re
Public bug reported:
I am seeing various USB drive errors while trying to use the drives.
For instance, I am unable to successfully create a new file system on
the drives. One example is parted which returns the following error:
Error fsyncing/closing /dev/sdc: Remote I/O error
dmesg shows the f
This bug was fixed in the package linux-firmware - 1.127.12
---
linux-firmware (1.127.12) trusty; urgency=medium
* Add new firmware files required by the lts-vivid 3.19 kernel as
described by the kernel MODULE_FIRMWARE statements, satisfied by the
following upstream commits:
This bug was fixed in the package linux-firmware - 1.127.12
---
linux-firmware (1.127.12) trusty; urgency=medium
* Add new firmware files required by the lts-vivid 3.19 kernel as
described by the kernel MODULE_FIRMWARE statements, satisfied by the
following upstream commits:
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/1456837
Title:
USB drive errors with kernel v
This likely won't be in vivid-backports, since there are many components
that depends on bluez and only work with bluez 4. (See also
https://blueprints.launchpad.net/ubuntu/+spec/desktop-v-bluez5)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
Hi Christopher,
Thank you for your quick response. I have submitted the new bug #1456837 and
have subscribed you to it.
I will be happy to provide additional information or run any experiments as
necessary.
Regards,
Gary
-- Original Message --
Subject: [Bug 1434764] Re: Ex
** Description changed:
This bug is for tracking the 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
kernel-stable-Prepare-packa
This bug was fixed in the package linux-armadaxp - 3.2.0-1650.70
---
linux-armadaxp (3.2.0-1650.70) precise; urgency=low
[ Ike Panhc ]
* Release Tracking Bug
- LP: #1452433
* Rebase to Ubuntu-3.2.0-84.121
[ Ubuntu: 3.2.0-84.121 ]
* Release Tracking Bug
- LP: #1451
This bug was fixed in the package linux-ti-omap4 - 3.2.0-1464.84
---
linux-ti-omap4 (3.2.0-1464.84) precise; urgency=low
* Release Tracking Bug
- LP: #1452432
[ Paolo Pisati ]
* rebased on Ubuntu-3.2.0-84.121
[ Ubuntu: 3.2.0-84.121 ]
* Release Tracking Bug
- LP:
This bug was fixed in the package linux - 3.2.0-84.121
---
linux (3.2.0-84.121) precise; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1451968
[ Upstream Kernel Changes ]
* netfilter: nf_conntrack: reserve two bytes for nf_ct_ext->len
- LP: #1442080
-
** Description changed:
This bug is for tracking the 3.2.0-84.121 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
kernel-stable-P
This bug was fixed in the package linux-armadaxp - 3.2.0-1650.70
---
linux-armadaxp (3.2.0-1650.70) precise; urgency=low
[ Ike Panhc ]
* Release Tracking Bug
- LP: #1452433
* Rebase to Ubuntu-3.2.0-84.121
[ Ubuntu: 3.2.0-84.121 ]
* Release Tracking Bug
- LP: #1451
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad
(adconrad)
** Changed in: kernel-sru-workflow/promote-to-updates
** Description changed:
This bug is for tracking the 3.2.0-1650.70 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
kernel-stable-
This bug was fixed in the package linux-lts-trusty -
3.13.0-53.87~precise1
---
linux-lts-trusty (3.13.0-53.87~precise1) precise; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1452900
[ dann frazier ]
* [Config] CONFIG_{EFI_PARAMS_FROM_FDT,GENERIC_EARLY_IO
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad
(adconrad)
** Changed in: kernel-sru-workflow/promote-to-updates
This bug was fixed in the package linux-armadaxp - 3.2.0-1650.70
---
linux-armadaxp (3.2.0-1650.70) precise; urgency=low
[ Ike Panhc ]
* Release Tracking Bug
- LP: #1452433
* Rebase to Ubuntu-3.2.0-84.121
[ Ubuntu: 3.2.0-84.121 ]
* Release Tracking Bug
- LP: #1451
** Changed in: kernel-sru-workflow/package-testing
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubu
** Description changed:
This bug is for tracking the 3.13.0-53.87~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
kernel
This bug was fixed in the package linux - 3.16.0-38.52
---
linux (3.16.0-38.52) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1452623
[ Stefan Bader ]
* SAUCE: vesafb: Set mtrr:3 (write-combining) as default
- LP: #1434581
[ Upstream Kernel
This bug was fixed in the package linux-lts-trusty -
3.13.0-53.87~precise1
---
linux-lts-trusty (3.13.0-53.87~precise1) precise; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1452900
[ dann frazier ]
* [Config] CONFIG_{EFI_PARAMS_FROM_FDT,GENERIC_EARLY_IO
This bug was fixed in the package linux-ti-omap4 - 3.2.0-1464.84
---
linux-ti-omap4 (3.2.0-1464.84) precise; urgency=low
* Release Tracking Bug
- LP: #1452432
[ Paolo Pisati ]
* rebased on Ubuntu-3.2.0-84.121
[ Ubuntu: 3.2.0-84.121 ]
* Release Tracking Bug
- LP:
This bug was fixed in the package linux - 3.16.0-38.52
---
linux (3.16.0-38.52) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1452623
[ Stefan Bader ]
* SAUCE: vesafb: Set mtrr:3 (write-combining) as default
- LP: #1434581
[ Upstream Kernel
This bug was fixed in the package linux - 3.2.0-84.121
---
linux (3.2.0-84.121) precise; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1451968
[ Upstream Kernel Changes ]
* netfilter: nf_conntrack: reserve two bytes for nf_ct_ext->len
- LP: #1442080
-
This bug was fixed in the package linux - 3.16.0-38.52
---
linux (3.16.0-38.52) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1452623
[ Stefan Bader ]
* SAUCE: vesafb: Set mtrr:3 (write-combining) as default
- LP: #1434581
[ Upstream Kernel
This bug was fixed in the package linux - 3.16.0-38.52
---
linux (3.16.0-38.52) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1452623
[ Stefan Bader ]
* SAUCE: vesafb: Set mtrr:3 (write-combining) as default
- LP: #1434581
[ Upstream Kernel
** Description changed:
This bug is for tracking the 3.16.0-38.52 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
kernel-stable-P
This bug was fixed in the package linux - 3.16.0-38.52
---
linux (3.16.0-38.52) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1452623
[ Stefan Bader ]
* SAUCE: vesafb: Set mtrr:3 (write-combining) as default
- LP: #1434581
[ Upstream Kernel
This bug was fixed in the package linux-ti-omap4 - 3.2.0-1464.84
---
linux-ti-omap4 (3.2.0-1464.84) precise; urgency=low
* Release Tracking Bug
- LP: #1452432
[ Paolo Pisati ]
* rebased on Ubuntu-3.2.0-84.121
[ Ubuntu: 3.2.0-84.121 ]
* Release Tracking Bug
- LP:
This bug was fixed in the package linux - 3.16.0-38.52
---
linux (3.16.0-38.52) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1452623
[ Stefan Bader ]
* SAUCE: vesafb: Set mtrr:3 (write-combining) as default
- LP: #1434581
[ Upstream Kernel
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad
(adconrad)
** Changed in: kernel-sru-workflow/promote-to-updates
This bug was fixed in the package linux - 3.13.0-53.88
---
linux (3.13.0-53.88) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1454785
[ Upstream Kernel Changes ]
* mmc: card: Don't access RPMB partitions for normal read/write
- LP: #1454013
linux
This bug was fixed in the package linux - 3.16.0-38.52
---
linux (3.16.0-38.52) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1452623
[ Stefan Bader ]
* SAUCE: vesafb: Set mtrr:3 (write-combining) as default
- LP: #1434581
[ Upstream Kernel
This bug was fixed in the package linux-ti-omap4 - 3.2.0-1464.84
---
linux-ti-omap4 (3.2.0-1464.84) precise; urgency=low
* Release Tracking Bug
- LP: #1452432
[ Paolo Pisati ]
* rebased on Ubuntu-3.2.0-84.121
[ Ubuntu: 3.2.0-84.121 ]
* Release Tracking Bug
- LP:
** Description changed:
This bug is for tracking the 3.13.0-53.88 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
kernel-stable-P
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad
(adconrad)
** Changed in: kernel-sru-workflow/promote-to-updates
This bug was fixed in the package linux - 3.2.0-84.121
---
linux (3.2.0-84.121) precise; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1451968
[ Upstream Kernel Changes ]
* netfilter: nf_conntrack: reserve two bytes for nf_ct_ext->len
- LP: #1442080
-
This bug was fixed in the package linux - 3.13.0-53.88
---
linux (3.13.0-53.88) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1454785
[ Upstream Kernel Changes ]
* mmc: card: Don't access RPMB partitions for normal read/write
- LP: #1454013
linux
This bug was fixed in the package linux - 3.16.0-38.52
---
linux (3.16.0-38.52) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1452623
[ Stefan Bader ]
* SAUCE: vesafb: Set mtrr:3 (write-combining) as default
- LP: #1434581
[ Upstream Kernel
Hello all, I've just started following this issue after updating to
vivid. First, would it be possible to get some sort of notion of how
this is coming along? Is it going to show up in vivid-backports, or is
it targeted for wily?
Also, is it possible to install the bluez version that packagers are
** Description changed:
This bug is for tracking the 3.16.0-38.52~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
kernel-
This bug was fixed in the package linux - 3.13.0-53.88
---
linux (3.13.0-53.88) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1454785
[ Upstream Kernel Changes ]
* mmc: card: Don't access RPMB partitions for normal read/write
- LP: #1454013
linux
*** This bug is a duplicate of bug 1454785 ***
https://bugs.launchpad.net/bugs/1454785
This bug was fixed in the package linux - 3.13.0-53.88
---
linux (3.13.0-53.88) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1454785
[ Upstream Kernel Changes ]
This bug was fixed in the package linux-lts-utopic -
3.16.0-38.52~14.04.1
---
linux-lts-utopic (3.16.0-38.52~14.04.1) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1452882
[ Stefan Bader ]
* SAUCE: vesafb: Set mtrr:3 (write-combining) as default
This bug was fixed in the package linux - 3.13.0-53.88
---
linux (3.13.0-53.88) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1454785
[ Upstream Kernel Changes ]
* mmc: card: Don't access RPMB partitions for normal read/write
- LP: #1454013
linux
This bug was fixed in the package linux - 3.13.0-53.88
---
linux (3.13.0-53.88) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1454785
[ Upstream Kernel Changes ]
* mmc: card: Don't access RPMB partitions for normal read/write
- LP: #1454013
linux
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad
(adconrad)
** Changed in: kernel-sru-workflow/promote-to-updates
This bug was fixed in the package linux - 3.13.0-53.88
---
linux (3.13.0-53.88) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1454785
[ Upstream Kernel Changes ]
* mmc: card: Don't access RPMB partitions for normal read/write
- LP: #1454013
linux
This bug was fixed in the package linux - 3.13.0-53.88
---
linux (3.13.0-53.88) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1454785
[ Upstream Kernel Changes ]
* mmc: card: Don't access RPMB partitions for normal read/write
- LP: #1454013
linux
This bug was fixed in the package linux - 3.13.0-53.88
---
linux (3.13.0-53.88) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1454785
[ Upstream Kernel Changes ]
* mmc: card: Don't access RPMB partitions for normal read/write
- LP: #1454013
linux
This bug was fixed in the package linux - 3.13.0-53.88
---
linux (3.13.0-53.88) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1454785
[ Upstream Kernel Changes ]
* mmc: card: Don't access RPMB partitions for normal read/write
- LP: #1454013
linux
This bug was fixed in the package linux - 3.13.0-53.88
---
linux (3.13.0-53.88) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1454785
[ Upstream Kernel Changes ]
* mmc: card: Don't access RPMB partitions for normal read/write
- LP: #1454013
linux
This bug was fixed in the package linux - 3.13.0-53.88
---
linux (3.13.0-53.88) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1454785
[ Upstream Kernel Changes ]
* mmc: card: Don't access RPMB partitions for normal read/write
- LP: #1454013
linux
This bug was fixed in the package linux - 3.13.0-53.88
---
linux (3.13.0-53.88) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1454785
[ Upstream Kernel Changes ]
* mmc: card: Don't access RPMB partitions for normal read/write
- LP: #1454013
linux
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad
(adconrad)
** Changed in: kernel-sru-workflow/promote-to-updates
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: New => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques
(henrix)
--
You received this bug notification because you are a
I just wanted to note that I was having the same problem in Ubuntu
15.04. I upgraded to the (currently) proposed 3.19.0-17-generic
(3.19.0-17.17) kernel and the Juniper SSL client is now working as
expected.
Thank you for getting this fixed. This would have been a serious issue
for me.
--
You
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => Chris J Arges (arges)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
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/1454843
Title:
Realtek RTL8723BE wireless card drops connection
Statu
I tested the patches earlier, so it should be good.
But just for the record:
I just pulled the trusty master-next branch, built and tested on the test vm.
The crash doesn't occur for me anymore in the reported scenario.
Atm, it looks like the fix will be in 3.13.0-54 but afaik we have to wait for
** 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/1454843
Title:
Realtek RTL8723BE wireless card drops connection
Statu
--- Comment From helle...@us.ibm.com 2015-05-19 20:54 EDT---
(In reply to comment #22)
> Reassigning to linux; this seems most likely to be a filesystem/ibmvfc
> driver issue.
Fine, but we are still waiting for answers to the above questions, see
comment 19. Like I said: there may in fact
I used to use the official supported LTS Ubuntu Trusty 3.13 kernel line.
With current updates.
I didn't noticed which subversion started to affect kernel panic after Totem
player. May be several months.
I tried to stress several times some kernels by Total Player (play,
seek, switch playlist..
** Description changed:
This bug will try to consolidate all HP Proliant Bugs related to kernel
panics. Please do not use this to attach cores and/or files. Just to
provide feedback on the cmdline and its explanations.
We had several talks (in the last 2 weeks) with HP ROM Engineering T
Hi, I've followed all the steps and bluetooth is still idle. I've set up
the second kernel. Any help? Thanks!
--
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/1394368
Title:
Bluet
I experienced the same issue on Mint 17.1 Cinnamon 64 after a power failure
during an update run.
Your methodology of booting a live cd, mounting the partitions, chroot, and
complete the updates worked for me and I was able to recover my system.
I posted my experience on the Mint forums here:-
h
** Changed in: linux (Ubuntu)
Status: Invalid => 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/1456732
Title:
linux: 3.19.0-18.18 -proposed tracker
Status in Kernel SRU Work
Hi,
I updated the bios and now I got the suspend-to-ram working with 3.19.0-16
kernel.
Here is the output of the requested command :
vincent@vincent-portable:~$ sudo dmidecode -s bios-version && sudo dmidecode -s
bios-release-date
[sudo] password for vincent:
05NS
07/03/2010
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/1456770
Title:
[System76, Inc. Gazelle Profes
** Tags removed: need-duplicate-check
--
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/1456770
Title:
[System76, Inc. Gazelle Professional] suspend/resume failure
Status in linux package
1 - 100 of 249 matches
Mail list logo
