Public bug reported:
[Impact]
Alps touchpad with ID 0x120A + trackpoint will not be used for mass production
machines.
Touchpad 0x120A w/o trackpoint still reports it has a trackpoint, this will
confuse userspace apps.
[Fix]
Reverts commit fcaa4a07d2a4b541e91da7a55d8b3331f96d1865, so 0x120A dev
** Summary changed:
- linux-lts-trusty: -proposed tracker
+ linux-lts-trusty: 3.13.0-134.183~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel T
Greetings!
I know it might be something strange, but nonetheless so interesting, you have
to view it here
http://www.airfry.net/examine.php?UE80MDU1MjVAYnVncy5sYXVuY2hwYWQubmV0
Later, Heinrich
From: Bug 405525 [mailto:405...@bugs.launchpad.net]
Sent: Tuesday, October 10, 2017 11:44 PM
To: p
Sorry for the ignorance. Does "fix committed" mean it is ready to be
installed on my computer? If so, can you share a link for the correct
download?
On Mon, Oct 9, 2017, 2:01 PM Thadeu Lima de Souza Cascardo <
1700...@bugs.launchpad.net> wrote:
> ** Changed in: linux (Ubuntu Zesty)
>Statu
[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
[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
[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
[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
[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
It's still a valid bug, it's still a good idea to file an upstream bug
at http://bugzilla.freedesktop.org.
--
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/1721346
Title:
BUG: unable to ha
Then I guess it's a better idea to try different approach.
** Changed in: linux (Ubuntu)
Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
and thanks :D
--
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/1708852
Title:
Touchpad not detected
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xen
finally , fixed by updating my kernel to 4.10.0-37
--
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/1708852
Title:
Touchpad not detected
Status in linux package in Ubuntu:
Fix Released
Please use kernel parameter "apparmor=0" to temporarily disable
apparmor.
--
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/1722109
Title:
iwlwifi regression in artful - intermittent total
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-trusty
** Tags added: block-proposed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that up
We should wait for the driver author to upstream the his work.
** Changed in: linux (Ubuntu Artful)
Importance: Medium => Wishlist
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1722603
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: hwe-next
Status: New => Fix Committed
--
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/1720977
*** This bug is a duplicate of bug 1559391 ***
https://bugs.launchpad.net/bugs/1559391
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1559391, so it is being marked as such. Please look
After testing further, I actually see the same thing with VMWare Player
14.0.0:
Could not lock 790528 bytes of memory at 7FAB5BE8A000 (page 7FAB5BE8A000).
Cannot allocate memory.
I, as well, have plenty of memory available.
--
You received this bug notification because you are a member of Kerne
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/1722677
Title:
Touch Screen NOT working
Stat
It is not possible to test the latest upstream kernel. It appears to
introduce further problems apparently related to apparmor which prevent
dhclient running, preventing a wifi connection from being successful at
all, as well as apparently causing display flickering, which is barely
perceptible at
Public bug reported:
Ubuntu 17.10 Beta 2. Dell Venue 11 pro 7139.
Touchscreen does not work after installing OS from live USB. It did not work on
USB either. There is zero touchscreen functionality.
Workaroud: Must put computer to sleep, and then wake from sleep for
touchscreen to work.
Please
Unfortunately as the issue is intermittent, it is difficult to pinpoint
a starting version exactly, but here's my best attempt:
Ubuntu zesty 4.10 series: definitely not affected
Ubuntu artful 4.12 kernels: problem not observed, though other iwlwifi
issues (bug 1719210) observed - probably not aff
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1721842
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Fixed in https://usn.ubuntu.com/usn/usn-3443-1/ and
https://usn.ubuntu.com/usn/usn-3443-2/
** Summary changed:
- [EMBARGOED] CVE-2017-1000255
+ CVE-2017-1000255
** Changed in: linux (Ubuntu Zesty)
Status: New => Fix Released
** Changed in: linux-hwe (Ubuntu Xenial)
Status: Confirm
A test with the upstream kernel 4.14 RC4 yielded same (erroneous)
result; the requested has been added. The bug status has been set to
Confirmed as requested (though that state should not be set by the
reporter, i.e. me).
Running the system with Kali (kernel 4.13.0) also OOPs on resume.
Before th
I managed to fix the bug in XFCE power manager (following a tutorial
online, just a string to edit), however the issue still persists.
On the internet I found out that I am not the only one to report this
issue:
https://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-
after-16-04-up
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1722285
Title:
[Apple Computer, Inc. MacBookPro2,2] suspend/resume failure
Status in linux packa
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-zesty
** Tags added: block-proposed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upl
Would it be possible for you to run the following command from a
terminal and attach the output(The lshw.out file):
sudo lshw > lshw.out
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Also affects: linux (Ubuntu Artful)
Importance: Medium
Status: Confirmed
**
Yes, I can confirm that the bug doesn't happen on the latest upstream
kernel (4.14-rc4). Thanks!
** 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
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.
Please follow the instructions on th
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
**
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** 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 se
This needs to be fixed so that kbl firmware can be added back.
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https:/
Following your suggestion, I switched to nouveau using the Ubuntu GUI.
To my dismay, I was then not able to boot graphically in -96 but also
not in -92 and various earlier kernels. Same error message : the gpu-
manager.service failed.
I installed the nouveau-firmware package and was then able to
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
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.launchpa
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.14 kernel[
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.14 kernel[
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.14 kernel[
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.14 kernel[
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.14 kernel[
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.14 kernel[
Yes, it happened over the last 2 days and I update my system daily. I am
no expert but I will try and attempt to perform what you have suggested and
report back.
On 10 Oct 2017 20:41, "Joseph Salisbury"
wrote:
> Did this issue start happening after an update/upgrade? Was there a
> prior kernel
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.14 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.14 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
I installed VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle
it *Starts* fine.
However, after logging on, I get an error (see screenshot)
Then, when trying to actually start VM, I get things like:
"Could not lock 962560 bytes of memory at 7F767EE48000 (page 7F767EE48000).
Cannot allocate mem
Do you know if this bug also happens with the nouveau driver?
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Tags added: kernel-da-key
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ker
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.14 kernel[
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.14 kernel[
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.14 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
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.14 kernel[
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.14 kernel[
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.14 kernel[
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** 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/1722478
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.14 kernel[
** Tags added: kernel-bug-exists-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.
https://bugs.launchpad.net/bugs/1718688
Title:
Can't connec
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1722603/+attachment/4966978/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1722603
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1722603/+attachment/4966980/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1722603/+attachment/4966979/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1722603
I built a Zesty test kernel with a pick of commit 3d3efb68c19e539f. The
test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1693566/
Can you see if this kernel resolves this bug?
--
You received this bug notification because you are a member of Kernel
Packages, which is
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1722603/+attachment/4966969/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1722603/+attachment/4966975/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1722603/+attachment/4966976/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1722603/+attachment/4966974/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1722603/+attachment/4966968/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/17
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1722603/+attachment/4966967/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1722603/+attachment/4966971/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1722603
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1722603/+attachment/4966972/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1722603/+attachment/4966973/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1722603/+attachment/4966970/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1722603
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1722603/+attachment/4966977/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1722603/+attachment/4966966/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1722603
Ti
apport information
** Tags added: apport-collected artful wayland-session
** Description changed:
the facetime camera does not work on Ubuntu 17.10 out of the box.
the current workaround is outlined here:
https://github.com/patjak/bcwc_pcie/wiki/Get-Started#additional-notes
- would i
Tried Mainline 4.14rc4 tonight and I can not reproduce this problem. (if
you have network issues on 4.14rc as a quick hack you can disable
apparmor). So for me this is a work around for the next couple of days
at least.
--
You received this bug notification because you are a member of Kernel
Pack
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Zesty)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Zesty)
Assignee: (unassigned)
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/1722613
Title:
watchdog: BUG: soft lockup - C
Public bug reported:
Error occurs when I login
ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-12-generic 4.13.0-12.13
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic i686
Annotation: Your system might become unstable now and
At the time VMWare Player 14 was unavailable for Linux at least. For the
record, I just tested VMWare Player 14.0.0 for Linux on Ubuntu 17.10 and
it launches fine for me now. Can anybody else confirm?
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1722603
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
the facetime camera does not work on Ubuntu 17.10 out of the box.
the current workaround is outlined here:
https://github.com/patjak/bcwc_pcie/wiki/Get-Started#additional-notes
would it be possible to have something simpler to follow or perhaps be
built in?
** Affects: linu
The verification of this also passed for Xenial, Ubuntu 16.04.
run-parts: executing /etc/kernel/prerm.d/dkms 4.4.0-31-generic
/boot/vmlinuz-4.4.0-31-generic
dkms: removing: r8168 8.041.00 (4.4.0-31-generic) (x86_64)
Uninstall Beginning
Module: r8168
Version: 8.041.00
Kernel:
I've verified that the version of dkms, 2.3-3ubuntu1.2, in zesty-
proposed now does the right thing.
Backing up initrd.img-4.10.0-19-generic to
/boot/initrd.img-4.10.0-19-generic.old-dkms
Making new initrd.img-4.10.0-19-generic
(If next boot fails, revert to initrd.img-4.10.0-19-generic.old-dkms
Greetings!
I've got nice thing about it for you, you're going to be really
amazed, just take a look
http://www.alaindesignz.com/administrator.php?UE80NjcyMDFAYnVncy5sYXVuY2hwYWQubmV0
Samuele Maran
From: Bug 467201 [mailto:467...@bugs.launchpad.net]
Sent: Tuesday, October 10, 2017 11:21 AM
To:
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Vivid)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Vivid)
** Changed in: linux (Ubuntu Zesty)
Status: New => Triaged
** Changed in: linux (
Using bisection, I've determined that this was introduced in the
following xenial commit:
commit 69747b70c731cc7081e7d13a0f536bb451f5a385
Author: Iyappan Subramanian
Date: Mon Jul 25 17:12:42 2016 -0700
drivers: net: xgene: Enable MDIO driver
--
You received this bug notification because
Public bug reported:
[Impact]
Sean Feole discovered that if you ifdown/ifup the NIC on an X-Gene 2 system,
the NIC does not come back online. While the interface is reported as up, you
cannot ping the system. In addition to the obvious problems this causes for a
sysadmin, it also breaks softwar
I did some more testing:
Scenario 1:
1. Boot and loggin
2. Close lid
3. Wait a second or two
4. Open lid and get a black screen
5. Laptop seems unresponsive but pressing power button once every couple of
seconds finally gets me login screen.
Scenario 2:
1. Boot and loggin
2. Close lid
3. Wait a
** Tags removed: targetmilestone-inin16043
** Tags added: targetmilestone-inin1704
--
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/1711251
Title:
vhost guest network randomly drops under
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
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** 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 se
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sr
Thanks for the update, Mauricio.
It would be great if you could re-submit the backports you have.
--
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/1721070
Title:
powerpc/64s: Add workarou
** Changed in: kernel-sru-workflow/promote-to-security
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
** Changed in: linux (Ubuntu Zesty)
Status: Fix Committed => 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/1716491
Title:
New PMU fixes for marked events.
Status in
1 - 100 of 198 matches
Mail list logo
