The bt works on a cold 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/1777258
Title:
Qualcomm QCA6174 [168c:003e] (rev 32) on Ubuntu Bionic fresh install
has flakey wifi and no
Default Comment by Bridge
** Attachment added: "KDump kernel captures dump successfully using
regular/default initrd"
https://bugs.launchpad.net/bugs/1778844/+attachment/5157007/+files/kdump-success-with-default-initrd.log
** Changed in: ubuntu
Assignee: (unassigned) => Ubuntu on IBM
You have been subscribed to a public bug:
Problem Description:
===
After triggering crash ,kdump is not working & system enters into initramfs
state
Steps to re-create:
==
>. woo is installed ubuntu180401 kernel
root@woo:~# uname -a
Linux woo 4.15.0-23-generic
Thanks for your comment, Kai-Heng, but I did try the latest upstrem
kernel at the weekend. Please refer to my post #8.
Is there a good reason to try a kernel more recent than:-
linux-image-
unsigned-4.17.0-041700-lowlatency_4.17.0-041700.201806041953_amd64.deb
... along with its associated
I can see BT stuff when cold booting. Unable to test right now, but the
ability to see devices was not available before, so I think it probably
works. It must be a resume and warm boot issue?
On Tue, Jun 26, 2018 at 9:37 PM Joshua Freedman
wrote:
> [0.00] Linux version
[0.00] Linux version 4.18.0-041800rc1-generic (kernel@tangerine)
(gcc version 7.3.0 (Ubuntu 7.3.0-21ubuntu1)) #201806162031 SMP Sun Jun 17
00:34:22 UTC 2018
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.18.0-041800rc1-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash
[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.
[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.
[Expired for linux (Ubuntu Bionic) because there has been no activity
for 60 days.]
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I guess you warm booted instead of cold booted your system?
Please power off the system, and boot with v4.18-rc1 again.
--
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/1777258
Title:
** Changed in: linux (Ubuntu)
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/1720930
Title:
wlp3s0: failed to remove key (1,
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1773905
Title:
Support UVC1.5 Camera for Xenial
Status in linux
@Breno since the missing commits are only for improved reporting of
vulnerability status, does IBM consider them to be needed for Ubuntu
14.04's 3.13 kernel? (Ubuntu 17.10's 4.13 kernel will go EoL soon so it
probably won't receive the changes)
--
You received this bug notification because you
[0.00] Linux version 4.18.0-041800rc1-generic (kernel@tangerine) (gcc
version 7.3.0 (Ubuntu 7.3.0-21ubuntu1)) #201806162031 SMP Sun Jun 17 00:34:22
UTC 2018
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.18.0-041800rc1-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash
Anything specific I should be looking for? When I dmesg its a pretty
long list.
--
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/1777258
Title:
Qualcomm QCA6174 [168c:003e] (rev 32) on
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
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/1778511
Title:
PCI network card (r8169) UNCLAIMED at boot
Status in
Follow #22 and file a bug to let Intel iwlwifi developers know.
--
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/1772154
Title:
Unstable WiFi adapter Gigabyte GC-WB867D-I
Status in linux
Can you attach dmesg when BT failed to work?
--
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/1777258
Title:
Qualcomm QCA6174 [168c:003e] (rev 32) on Ubuntu Bionic fresh install
has
Please give #3 a try...
--
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/1776443
Title:
iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
Status in linux package in Ubuntu:
Sorry, I found the lsusb output you have already provided in:
http://paste.ubuntu.com/p/XC5PWRFywp/
Please just send us the output from 'journalctl' after the problem
occurs.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
Thanks.
It looks like some unusual things are happening in the kernel a couple
of times:
[ 81.158861] ath10k_pci :6b:00.0: Unknown eventid: 118809
[ 81.161868] ath10k_pci :6b:00.0: Unknown eventid: 90118
and
[ 9845.821302] ath10k_pci :6b:00.0: Unknown eventid: 118809
[
The Artful 4.13 kernel has already received some of these fixes in
4.13.0-43.48 and the same is true for the Trusty 3.13 kernel in
3.13.0-151.201.
They contain these patches:
- powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags
- powerpc: Add security feature flags for
The attachment "proposed-patch-1.debdiff" seems to be a debdiff. The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag,
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-xenial
** Tags added: block-proposed
** Description changed:
This bug is for tracking the 4.15.0-1010.10~16.04.1 upload package. This
bug will contain status and testing
The Xenial 4.4 kernel was fixed in 4.4.0-127.153:
https://launchpad.net/ubuntu/+source/linux/4.4.0-127.153
** Changed in: linux (Ubuntu Xenial)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri
(mhcerri)
** Description changed:
This bug is for tracking
** 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/1778555
Title:
My Webcam does not work with Cheese
Status in linux package in Ubuntu:
** Tags added: xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1778798
Title:
zedit doesn't open file in vm mode
Status in zfs-linux package in Ubuntu:
New
Bug
Indeed there was - in /etc/modprobe.d for r8168-dkms. I ran sudo apt-get
purge --auto-remove r8168-dkms
and all is working as it should.
Many thanks for your help.
On 26/06/18 16:02, Kai-Heng Feng wrote:
> Is there any entry in /etc/modprobe.conf or /etc/modprobe.d that is
> r8168/r8169?
>
--
It does not work with the upstream kernel.
(By the way, I realize that this is not a place to get support, but you
should help the bug reported to test: Is it good to run my production PC
with the upstream kernel from now on? or it it better to uninstall it
after finishing testing?)
Also: I told
precisely, its size is 0 and hence lsblk ignores it without option -a.
# lsblk -a
NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:00 0 loop
loop1 7:10 0 loop
loop2 7:20 0 loop
loop3 7:30 0 loop
loop4 7:40 0 loop
Nice catch. Thank you.
This indeed does seem to be a workaround. Forcing version 1.0 avoids the
issue. Its not a proper fix however. Seems to be bug in higher versions.
>From the man doc:
The default since v4.13.5 is for the client and server to negotiate the
highest possible version greater
On Tue, 2018-06-26 at 20:40 +, Joseph Salisbury wrote:
> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular
> problem?
The problem first appeared after an upgrade of Debian Linux (mixed
"frankendebian" distro).
[0.00] Linux version 4.18.0-041800rc1-generic (kernel@tangerine)
(gcc version 7.3.0 (Ubuntu 7.3.0-21ubuntu1)) #201806162031 SMP Sun Jun 17
00:34:22 UTC 2018
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.18.0-041800rc1-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash
Public bug reported:
fis-gtm installed in Ubuntu environment. zfs-zed package installed to
create and edit M routines. Using zed command doesn't open file.
--
Description:Ubuntu 16.04.4 LTS
Release:16.04
** Patch added: "proposed-patch-1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771783/+attachment/5156893/+files/proposed-patch-1.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber
Sacilotto de Souza (kleber-souza)
** Changed in:
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18 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
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18 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
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.18
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Changed
file a new bug, test mainline kernels starting from 4.8 and up
http://kernel.ubuntu.com/~kernel-ppa/mainline/
--
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/1770565
Title:
[i915_bpo]
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18 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
although, your issue can't be the result of this backport, because T440s
has a haswell (gen7.5) gpu, i915_bpo is used only on gen9 gpus
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I'm investigating this for Bionic. I'll post an update shortly.
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: Canonical Kernel Team
*** This bug is a duplicate of bug 1778772 ***
https://bugs.launchpad.net/bugs/1778772
** This bug has been marked a duplicate of bug 1778772
linux-gcp: 4.15.0-1010.10~16.04.1 -proposed tracker
--
You received this bug notification because you are a member of Kernel
Packages, which is
I can verify from IBM's standpoint, that we were able to use Volta gpu's
with POWER9. The Nvidia driver enabled correctly.
--
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/1772991
Title:
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Changed in: kernel-sru-workflow/snap-release-to-stable
Status: New => Invalid
** Description changed:
This bug is for tracking the 4.15.0-1010.10~16.04.1 upload package. This
bug will contain status
Public bug reported:
This bug is for tracking the 4.15.0-1010.10~16.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
Unable to run this command
** 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/1778765
Title:
Ubuntu 18.04 NVMe disks
There is a package on ppa:cascardo/ppa that should fix the problem. Can
you test it and report back?
Cascardo.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1765660
Title:
Ubuntu
There is a package on ppa:cascardo/ppa that should fix the problem. Can
you test it and report back?
Cascardo.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1746088
Title:
[Ubuntu
Could be related to something in here:
https://bugs.archlinux.org/task/57474
Adding vers=1.0 in the mount line seems to fix the issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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 1778765
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
Following the suggestion #12 on bug 1758205 to raise a new one
I have updated kernel to 4.15.0-23-generic and still see the problem reported
in 1758205:
root@localhost:/sys/block# nvme list
Node SN Model Namespace Usage Format FW Rev
I've used UKUU to get kernel version 4.17.3, but this issue remains on
my HP Pavilion 15-aw003nm
(http://www8.hp.com/h20195/v2/GetPDF.aspx/c05342156.pdf ) on kernel
version 4.15.0-23 from the repository as well as on the latest stable
kernel.
The exact error message copied from dmesg is as
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093554.html
--
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/1766055
Title:
Vcs-Git header on bionic linux
Is there any entry in /etc/modprobe.conf or /etc/modprobe.d that is
r8168/r8169?
--
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/1778511
Title:
PCI network card (r8169) UNCLAIMED at boot
Since installing this kernel, I see instant screen garbage or blanking
(everything but the cursor), when attaching / removing a second / third
screen on My Lenovo Thinkpad T440s.
Older kernels do not suffer these problems. A restart of lightdm makes
the problems go away and makes a second screen
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
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 1742488
and then change the status of the bug to 'Confirmed'.
If, due to the
Hi,
the own website [1] still calls it "should be considered a work in progress. As
such it is not a complete product nor should it be considered one. Extra care
should be taken when testing and configuring a system to use the KVMGT project".
That said I'm not sure what is expected here. I
Moving back to Confirmed state - since all the available logs are
already uploaded.
** 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.
* Also hit with 16.04.4 HWE kernel 4.13.0-45-generic.
* Not seen with LTS kernel 4.4 of Ubuntu 16.04
** Also affects: dellserver
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Attachment added: "screenshot-2"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778717/+attachment/5156771/+files/image-2018-06-22-14-48-57-801.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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 1778717
and then change the status of the bug to 'Confirmed'.
If, due to the
** Attachment added: "screenshot-1"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778717/+attachment/5156770/+files/image-2018-06-25-10-13-05-871.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Setup - A Dell EMC 14th Gen AMD server, with ESXi 6.7 as host and Ubuntu
18.04 (latest updates) guest.
Guest has 3 data disks apart from the boot disk. All these disks are exposed
through "ParaVirtual SCSI controller" from the host ESXi 6.7.
Run diskio stress on all the 3
** Package changed: linux-azure (Ubuntu) => null-and-void
** Information type changed from Public to Private
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1776284
Title:
@buy
** Package changed: linux-azure (Ubuntu) => null-and-void
** Information type changed from Public to Private
** Changed in: null-and-void
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in
kvm on z/vm is out of scope for Ubuntu on s390x.
one may still want to investigate none-the-less in case something
generic is uncovered.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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 1778705
and then change the status of the bug to 'Confirmed'.
If, due to the
Using a Logitech M310 from a KM520 bundle kit like Steven Karas (steven-
karas) and having exactly the same issue. His comment (comment #91)
makes my middle button magically start working as well.
--
You received this bug notification because you are a member of Kernel
Packages, which is
I'm praying intensely that the new AMD Epyc 3000 Embedded series (low
power e3000) don't have the same issues. Hoping to buy one in the next
few months when they finally put the damn things on some ITX boards.
--
You received this bug notification because you are a member of Kernel
Packages,
That doesn't seem to happen with 4.15.0-22-generic.
--
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/1777863
Title:
[drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI
(In reply to OptionalRealName from comment #375)
> Thread still ongoing with no response from AMD.
>
> Really shouldn't need to fiddle with custom bios options.
>
> What is big business / big iron or whatever it's called doing with Epyc and
> linux servers? Are those totally fine?
I am running
I just tried again to test if nvidia updates would fix this ugly bug. In
summary: no.
I also tried the graphics-drivers ppa mentioned (specifically tried the
340 and 390 drivers) with the same negative results.
The only working solution for my nvidia-prime laptop (nvidia+intel) is
using
Public bug reported:
TESTNAME=skey TIMEOUT=90s ACCEL= ./s390x/run s390x/skey.elf -smp 1
FAIL skey (2 tests)
This is the only failure in this test suite on Xenial zVM, need to run
it manually to see what's going on.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package:
I can't answer your question about battery life according to the
parameters, I did not test that.
If you're running RavenRidge on Ubuntu, you will have to fight the CPU
(Ryzen's CPU lock ups:
https://bugzilla.kernel.org/show_bug.cgi?id=196683 ) and also amdgpu,
because they're still working on
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 1778534
and then change the status of the bug to 'Confirmed'.
If, due to the
** Package changed: ubuntu => linux (Ubuntu)
--
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/1778534
Title:
Touchpad not working (Elantech ELAN0618)
Status in linux package in Ubuntu:
You have been subscribed to a public bug:
For a fresh installed Ubuntu 16 (and 18), touchpad doesn't work for
Elantech ELAN0618.
We have modified the struct elan_acpi_id, by adding ELAN0618 to the list
of the supported models (in the file drivers/input/mouse/elan_i2c_core.c
from the kernel
** Tags added: originate-from-1777105 somerville
--
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/1778658
Title:
Nvidia fails after switching its mode
Status in HWE Next:
New
Status in
Public bug reported:
[Impact]
Switch Nvidia mode requires rebooting the system. It's because of losing some
of its status while switching mode if runtime PM is enabled. It's a generic
issue that would happen on some other devices, too. This patch restores
devices' config space on runtime
The latest 13.0.151 kernel has the same issue, at least on this laptop.
This also means that whatever security updates are rolled into the
mainline kernels are in effect inaccessible to laptop users affected by
this issue. :-(
--
You received this bug notification because you are a member of
As this bug has been closed, could you raise a new bug (possibly
referencing this one) for this issue? Thanks.
--
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/1758205
Title:
Ubuntu 18.04
*** This bug is a duplicate of bug 1759628 ***
https://bugs.launchpad.net/bugs/1759628
Ah sorry. I did not catch that one. Yes the workaround is easy. Its one of
these two
sudo service bluetooth restart
or
sudo service network-manager restart
On Tue, Jun 26, 2018 at 4:10 AM Daniel van
Ack. Thanks for the update. Closing.
** Changed in: ubuntu-power-systems
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
It looks like the test has passed with Bionic Azure kernel + Xenial
(guest), I will remove the azure project.
** No longer affects: linux-azure (Ubuntu)
** Summary changed:
- Unable to boot Xenial cloud image on Bionic ARM64 ThunderX / Azure
+ Unable to boot Xenial cloud image on Bionic ARM64
** 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/1778584
Title:
linux-image-3.13.0-151-generic fails to boot
Status
Public bug reported:
It looks like the kernel module can be installed, but four tests have
failed:
== lttng smoke test of session create/destroy ==
Session test-kernel-session created.
Traces will be written in /tmp/lttng-kernel-trace-14716-session
PASSED (lttng create)
Session
92 matches
Mail list logo
