The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of m
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Importance: Undecided => High
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
--
You received this bug notifi
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of m
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Ike Panhc (ikepanhc)
** Changed in: linux (Ubuntu)
Status: Triaged => 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.
Hello friend,
Perhaps you have seen that reports already? You are going to be
pleasantly surprised, read it here please
http://www.airparks.ru/pioneer.php?UE8yNjQ3ODlAYnVncy5sYXVuY2hwYWQubmV0
Mario Piccoli
-
>From time to time this website may also include links to other websites.
These l
I have a device with rtl8723bs, the message should be completely
harmless.
--
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/1720580
Title:
RTL8723bs bug: ERROR sd_recv_rxfifo: alloc recvbu
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of m
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of m
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of m
But "blacklist=nouveau modprobe.blacklist=nouveau" can boot, right?
13a86519202c5d119d83640d6f781f3181205d2c drm/nouveau/i2c/gf119-: add support
for address-only transactions:
http://people.canonical.com/~khfeng/lp1723619-2/
--
You received this bug notification because you are a member of Kern
dmesg1, dmesg2, which are the same as LP: #1678477:
[7.388222] usb 3-14: can't read configurations, error -110
dmesg3:
[ 40.156098] usbhid 3-14:1.1: can't add hid device: -110
[ 40.156314] usbhid: probe of 3-14:1.1 failed with error -110
So the original issue is solved, but now you hit an
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of m
Thanks.
It looks like there's also an out-of-tree driver available, if people
want to go that direction. (For example, it's available from Dell at
https://downloads.dell.com/FOLDER04588242M/1/UnifiedDriver_7.700.52.00_SLES12.tar.gz
, found on the drivers and downloads page for the R640 or R740 aft
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 1723644
and then change the status of the bug to 'Confirmed'.
If, due to the nature
So it's more likely to be a driver issue.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: 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/1723644
Title:
Netwo
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of m
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of m
Hi,
It turns out that support for this driver would require a very large
backport with several series of patches, involving significant
refactoring, code movement and other code change. This makes it very
hard for us to be sure that our backport is correct, and that it's not
going to fail unexpect
Are the patches for 4.4 (Xenial) available somewhere? We'd like patches
so we can build the kernel ourselves. We can immediately do basic
testing against H730/830 (Invader, previously supported) and H840
(Harpoon, new, probably same as H740 except with external connectors
instead of internal). With
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of m
Please look in /var/crash for a relevant crash file and when found
upload it using this command:
ubuntu-bug /PATH/TO/WHATEVER.crash
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
That's just the same BS Asus support always try to push on people. I can
tell you have updated every driver, to no avail. And even if it did
work, it wouldn't make a difference in Windows. It is most certainly a
firmware bug. That said, there still hasn't been any explanation as to
why this thread
Wouldn't make a difference in Linux I meant.
--
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/1653456
Title:
ASUS G752VS: Touchpad and Fn keys not working (Ubuntu
16.04.1/16.10/17.04)
S
Public bug reported:
Issue:
Call traces occurs when memory-hotplug script is run with 16Gb hugepages
configured.
Environment:
ppc64le PowerVM Lpar
root@ltctuleta-lp1:~# uname -r
4.4.0-34-generic
root@ltctuleta-lp1:~# cat /proc/meminfo | grep -i huge
AnonHugePages: 0 kB
HugePages_Total:
You have been subscribed to a public bug:
Issue:
Call traces occurs when memory-hotplug script is run with 16Gb hugepages
configured.
Environment:
ppc64le PowerVM Lpar
root@ltctuleta-lp1:~# uname -r
4.4.0-34-generic
root@ltctuleta-lp1:~# cat /proc/meminfo | grep -i huge
AnonHugePages:
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of m
Public bug reported:
[Impact]
Early ThunderX silicon may hang when initializing the SATA controller.
[Test Case]
This was found in a reboot loop.
The latest ThunderX2 firmware (3.1) enables hardware error interrupts and
when the reset fix fails, we get a hang with the print:
[ 14.839308] sd 1:
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of m
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of m
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of m
Did this issue start happening after an update/upgrade?
It started after upgrading to 17.10 artful aardvark.
Was there a prior kernel version where you were not having this particular
problem?
It worked/works with 4.10.0-35 (still in grub boot list)
Would it be possible for you to tes
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of m
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of m
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of m
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of m
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of m
Reproes with the v4.14 kernel.
Power usage on idle is
4.14:~8W
4.13:~10W
4.10:~7W
There appears to have been a significant regression in power use from
4.10 to 4.13 that has been partially addressed in 4.14.
I got curious, and I get the same 100% busy report if I boot with the
legacy 4.10.37 ker
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of m
** Changed in: kernel-sru-workflow/automated-testing
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/1722335
Title:
linux: 3.13.0-134.183 -proposed
Now I cannot do it.
I will do it tomorrow around this time, having access to the hardware
involved.
Thanks
On Mon, 16 Oct 2017 at 21:41 Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> It looks like the bisect failed. All of the kernels I posted were
> reported as good and resolved th
Public bug reported:
ubuntu 17.10
bluez 5.46-0ubuntu3
after failing to search for bluetooth mouse, bluetooth applet crashes.
restarting bluetooth.service yields "adapter not found" message upon trying to
turn on bluetooth.
** Affects: bluez (Ubuntu)
Importance: Undecided
Status:
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of m
I did the same with:
$ uname -rv
4.13.7-041307-generic #201710141430 SMP Sat Oct 14 14:31:12 UTC 2017
and also this kernel works for me and touchpad works after resume. What
is also nice, Wi-Fi works after resume.
--
You received this bug notification because you are a member of Kernel
Packages
The kernel at #14 fails to boot.
--
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/1723619
Title:
Ubuntu Desktop ISO fails to boot with nouveau on a displayport
Status in Release Notes for
This was presumed fixed in the upstream bug report [1] and hasn't been a
problem for a couple of years now. Closing this report.
[1] https://bugzilla.kernel.org/show_bug.cgi?id=102161
** Bug watch added: Linux Kernel Bug Tracker #102161
https://bugzilla.kernel.org/show_bug.cgi?id=102161
** C
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of m
Sorry for the delay. I will try the new kernel, thanks!
On Wed, Oct 11, 2017 at 3:01 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
>
Hello Joseph,
thanks for your email. I'm trying to install the Kernel 4.14 from this
link: http://sourcedigit.com/22814-install-linux-kernel-4-14-rc5/ but it
doesn't work. After the two first commands all other show the message "not
found".
I'll try to answer your questions. This problem started
Public bug reported:
Add and update firmware files as necessary to support a 4.12 based
kernel in the xenial linux-hwe-edge package.
** Affects: linux-firmware (Ubuntu)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: In Progress
--
You received this bug notificat
I've applied the above mentioned patch, and rebuilt the rtl8723bs
module, but the same problem persists. Also tested kernel 4.14, and, as
expected, the same bug is there too.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you ar
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of m
Could you also give the latest upstream stable 3.13 kernel a try? It is
available here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13.7/
--
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
Disabling Thunderbolt support in the BIOS (F2 during boot) worked for
me.
Suspend works.
Don't know when/if I'll need the Thunderbolt. This works for now.
Thanks!
Can I provide any additional info to help you debug/fix this properly?
Cheers,
Walter
Before disabling Thunderbolt:
[ 4694.66762
Let me know do you need anything else. Will be possible to backport
fixes from 4.14 to final release of Ubuntu 17.10, so touchpad works
after resume on default Artful Aardvark install?
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification beca
I did following:
dpkg -i \
linux-headers-4.14.0-041400rc5_4.14.0-041400rc5.201710152230_all.deb \
linux-headers-4.14.0-041400rc5-generic_4.14.0-041400rc5.201710152230_amd64.deb
\
linux-image-4.14.0-041400rc5-generic_4.14.0-041400rc5.201710152230_amd64.deb
and rebooted the system to new kernel
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of m
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: linux (Ubuntu Zesty)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: lin
It looks like the bisect failed. All of the kernels I posted were
reported as good and resolved the bug. One or more of them should have
been bad and exhibited the bug.
I copied all of the test kernels back to
http://kernel.ubuntu.com/~jsalisbury/lp1723174. The test kernels for a
specific SH
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: Incomplete
** Also affects: linux (Ubuntu Bb-series)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of m
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 1724044
and then change the status of the bug to 'Confirmed'.
If, due to the nature
note the commit mentioned in the description is for trusty, but there
are similar commits for x/y/z/a that make autopkgtest fail for those
releases as well in the same way.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
Public bug reported:
commit 7a4e330a7f82869d161462b6f4b47f7d8ff963f2 (for trusty kernel)
changed autopkgtest to only build the first 'flavour'. However, this
causes failure on armhf because the 'lpae' flavour is still expected,
e.g.:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2a
I can confirm that Kernel 4.13 in ubuntu 17.10 beta 2 fixes this
problem. No work around is needed to boot into the system or live media.
--
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/1683
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of m
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of m
linux-image-4.10.0-37-generic Commit
b1943b80d393d40a75c7fd0679f51d6f998d28d5 fixed the problem. Wifi not
working again though.
--
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/1723174
Title
** Description changed:
the autopkgtests for the kernel include 'ubuntu-regression-suite' which
contains this test:
sver=`dpkg-parsechangelog -SVersion`
read x rver x &2
- exit 1
+ echo "ERROR: running version does not match source package" 1>&2
+ exit 1
fi
-
- However
This bug was fixed in the package dkms - 2.2.0.3-2ubuntu11.5
---
dkms (2.2.0.3-2ubuntu11.5) xenial; urgency=medium
* 0014-remove-initrd-backup.patch: When removing a kernel also remove
related .old-dkms file from /boot after its been created not before.
(LP: #1515513)
-- B
This bug was fixed in the package dkms - 2.3-3ubuntu1.2
---
dkms (2.3-3ubuntu1.2) zesty; urgency=medium
* 0014-remove-initrd-backup.patch: When removing a kernel also remove
related .old-dkms file from /boot after its been created not before.
(LP: #1515513)
-- Brian Murray
The verification of the Stable Release Update for dkms 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 encounter a reg
The fault is mine. Didn't take out-of-tree proprietary modules into
account. Please try artful kernel here:
http://people.canonical.com/~khfeng/lp1705748-artful/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
Please try Linux kernel here:
http://people.canonical.com/~khfeng/lp1723736/
--
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/1723736
Title:
Touchpad not detected - Lenovo ideapad 320-15IK
I built the next test kernel, up to the following commit:
b1943b80d393d40a75c7fd0679f51d6f998d28d5
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1723174
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on y
It looks like you may have already tested 4.12 final per comment #6. If
so, we just need to figure out which 4.13 release candidate introduced
the fix. So if v4.13-rc1 is still bad, we would next test -rc2, -rc3,
etc until we find the good version.
--
You received this bug notification because
To perform a bisect, we need to identify linear versions. Can you test
the following two kernels:
v4.12 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12/
v4.13-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc1/
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Jos
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
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is su
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
If the bug still exists in mainline, we can perform a kernel bisect to
identify the commit that introduced this regression.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
--
You received this bug notification because you are a member of Kernel
Packages
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[
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
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 1721880
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
We would like to see if this bug is already fixed upstream, so please
test the latest upstream kernel. Refer to
https://wiki.ubuntu.com/KernelMainlineBuilds
To see if this bug is fixed upstream, please 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 d
This problem persists on Ubuntu 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/362075
Title:
session logout after suspend
Status in NULL Project:
Invalid
Status in linux packag
The upstream kernel 4.14-rc5 contains a patch for this ALSA: usb-audio:
Add sample rate quirk for Plantronics P610
https://patchwork.kernel.org/patch/9987737/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
Yea, all ath10k devices are affected. Linux kernel based on 4.13.6
should land in Artful soon.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: network-manager (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Pack
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1722302
Title:
linux-aws: 4.4.0-1002
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => 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/1722335
Title:
linux: 3.13.0-134.183 -pr
--- Comment From cls...@us.ibm.com 2017-10-16 12:32 EDT---
(In reply to comment #30)
> Hi Carol,
>
> Could you please do one last check and let us know if we can close this bug?
>
> Thanks
> Victor
Verified with 4.10.0-37-generic.
--
You received this bug notification because you are a m
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
--
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/1722336
Title:
linux-lts-trus
I can confirm that linux-image-4.10.0-37-generic Commit
8b1a7b0607a840e73e9b6fd15cc01d800742fe43 fixed the problem. Wifi not
working though.
--
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/1
@Dimitri, yes I'll submit an SRU request.
--
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/696435
Title:
wait-for-root fails to detect nbd root
Status in linux package in Ubuntu:
Fix Re
Hi - I tested the libseccomp SRU in Zesty using the following libseccomp
package version:
- libseccomp2 2.3.1-2.1ubuntu2~17.04.1
I tested it with the following kernels:
- linux-image-4.10.0-37-generic 4.10.0-37.41
+ does not contain seccomp logging patches
- linux-image-4.10.0-38-generic 4
No. I don't feel comfortable installing that patch. Firstly, because it is
quite suspicious. Secondly, I will completely wipe out Windows from my machine
in coming days, so even if the patch eventually works correctly - I think that
without Windows the effect will most probably disappear.
By the
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
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/1646277
Title:
Xenial server 16.04.x will have a black screen after PXE installati
1 - 100 of 179 matches
Mail list logo
