Not sure I should chime in, since it's already been confirmed but, I'm
seeing this as well.
Says it's 100c in Disks and in Freon too.
$ sudo hddtemp /dev/sdb
/dev/sdb: KINGSTON SA400S37240G: 26°C
I'm a bit too tired at this point to try and figure out how to address
the issue. I'll read the t
--- Comment From pavsu...@in.ibm.com 2019-02-15 01:11 EDT---
I have installed all the packages as mentioned.
root@ltc-zz10:~# dpkg -i
linux-modules-4.15.0-45-generic_4.15.0-45.48~16.04.1_ppc64el.deb
(Reading database ... 129194 files and directories currently installed.)
Preparing to unpa
Any chance this could be added? I know the last message is from 2017,
but there commercial products such as the Yamaha MD-BT01 Bluetooth
Wireless MIDI Adaptor that rely on this being enabled.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
please find attached file.
In dmesg it does shows some error regading (Broadcom network).
** Attachment added: "lsusb-v.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815925/+attachment/5238829/+files/lsusb-v.txt
--
You received this bug notification because you are a member of
I can't find any wireless device in your PCI bus, perhaps it's on USB.
Can you attach the output of 'lsusb -v' here?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
** 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/1815808
Title:
Thunderbolt Ethernet high-traffic exception
Status in
[Expired for nftables (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nftables (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.
[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
A recent driver contributor has made the blobs available here:
https://www.reddit.com/r/SoundBlasterOfficial/comments/9mm5ad/sound_blaster_r3dr3dizzxrae5_linux_driver/
No idea on the licensing situation.
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => In Progress
** 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
** 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
-- swm properties --
boot
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Fix Released
--
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/1814733
Title:
linux-azure: 4.18.0-100
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.77-0ubuntu0.18.04.2
---
nvidia-graphics-drivers-390 (390.77-0ubuntu0.18.04.2) bionic; urgency=medium
* debian/rules.defs:
- Add support for xserver-xorg-core-hwe-18.04 (LP: #1815579).
-- Alberto Milone Thu,
This bug was fixed in the package nvidia-graphics-drivers-340 -
340.107-0ubuntu0.18.04.2
---
nvidia-graphics-drivers-340 (340.107-0ubuntu0.18.04.2) bionic; urgency=medium
* Add support for xserver-xorg-core-hwe-18.04 (LP: #1815579).
-- Alberto Milone Thu, 14 Feb 2019
16:48:59 +0
The verification of the Stable Release Update for nvidia-graphics-
drivers-340 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
On Thu, Feb 14, 2019 at 10:44:34PM -, Marek Hák wrote:
> The output of 'efibootmgr -v' showed me where the EFI partition is, but
> I have no idea where it's mounted or how to get to it.
> Boot0004* ubuntuHD(2,GPT,83484852-541d-401e-
> 84e7-6e6e8549496a,0x1f4800,0x82000)/File(\EFI\ubunt
The output of 'efibootmgr -v' showed me where the EFI partition is, but
I have no idea where it's mounted or how to get to it.
Boot0004* ubuntuHD(2,GPT,83484852-541d-401e-
84e7-6e6e8549496a,0x1f4800,0x82000)/File(\EFI\ubuntu\shimx64.efi)
Some info that may help:
I do not have the current
Launchpad has imported 2 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=202581.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
This happens for me with 18.04, kernel 4.15.0-45-generic.
It does not happen with 4.15.0-43-generic.
Running on xterm (as opposed to terminator) it still happens, but much
later in the build.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
@lazamarius1: Just to clarify, the fix is scheduled to go in the 4.15
kernel in Bionic which is the same kernel as the Xenial HWE kernel. So
there's no need to add anything to the Affects section. You will see a
new linux-hwe 4.15 kernel in xenial-proposed once this is ready to test.
Thanks!
--
Y
Ok.
My first patch for the linux kernel:
https://github.com/caravena/linux/commit/c540283416a7756dedaa72aa66a00c897517b113#diff-f52b6863505adc3b972c64d4a22195cc
I would like to have credits for this patch (:
--
You received this bug notification because you are a member of Kernel
Packages, whic
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
$ lspci
-> Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71]
(rev 21)?
Add line(?):
+ SND_PCI_QUIRK(0x103c, 0x8086, "HP Pavilion x360", CXT_FIXUP_MUTE_LED_GPIO),
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Marek, Secure Boot is a UEFI feature. It is not possible for you to
have Secure Boot blocking a kernel boot if you do not have UEFI.
It is possible that your EFI System Partition is not mounted at
/boot/efi, if you have modified your /etc/fstab since installation. For
the system to boot at all u
This bug was fixed in the package dkms - 2.2.0.3-2ubuntu11.6
---
dkms (2.2.0.3-2ubuntu11.6) xenial; urgency=medium
* debian/patches/shim_secureboot_support.patch:
- Move to signing just after module build to ensure it correctly applies
at kernel update times. (LP: #1772950
This bug was fixed in the package dkms - 2.2.0.3-2ubuntu11.6
---
dkms (2.2.0.3-2ubuntu11.6) xenial; urgency=medium
* debian/patches/shim_secureboot_support.patch:
- Move to signing just after module build to ensure it correctly applies
at kernel update times. (LP: #1772950
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/pci/hda/patch_conexant.c?id=v5.0-rc6#n934
SND_PCI_QUIRK(0x103c, 0x837f, "HP ProBook 470 G5",
CXT_FIXUP_MUTE_LED_GPIO),
What values are those that replace "0x837f"?
Where does that information come from?
--
You receive
Sounds like broken record here, oh no broken shutdown here actually.
Bodhi Linux 4.2 on old hardare Aspire 5000 laptop, was wooring fine till a day
or two ago.
Hangs at shutting down several things says all stopped down to hardware clock
something or another.
can hit Esc a couple times and it pro
Thanks for the help Mathieu, however, it sadly did not solve the issue.
There was no /efi direcory in my /boot. I still tried to create the
directories you told me to copy it into, but that didn't work. Is it
possible I have a non-UEFI version of ubuntu?
--
You received this bug notification beca
This happens on kernel 5.0.0-05rc6-generic
** 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/1815952
Title:
Mute key LED does not work on HP P
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
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/1795453
Title:
[SRU] IO's are issued with incorrect Sca
** Bug watch added: Linux Kernel Bug Tracker #202581
https://bugzilla.kernel.org/show_bug.cgi?id=202581
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=202581
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
Public bug reported:
Description of problem:
The F6/mute key on the keyboard of HP notebooks often has a built in LED
indicator to show if the sound is muted. The LED state is never toggled. It
will just retain its state, even though the audio is succesfully muted/unmuted.
Tested with HP Pavili
If you can still boot to Ubuntu with an older kernel (one that is
signed), here's what you can do:
1) Download http://archive.ubuntu.com/ubuntu/dists/xenial-
updates/main/uefi/grub2-amd64/2.02~beta2-36ubuntu3.20/grubx64.efi.signed.
2) Copy grubx64.efi.signed over /boot/efi/EFI/ubuntu/grubx64.efi:
Public bug reported:
SRU Justification:
Impact:
This feature is going to be a popular request for users of Intel's next gen
CPUs. It
is enabled by two small commits that went into the upstream 4.20 kernel.
Please
backport the two commits indicated in Fix: and investigate the effort
** Description changed:
- Kernel has the "reset_devices" parameter that drivers can opt-in, and
- perform special activity in case this parameter is parsed from command-
- line. For example, in kdump kernels it hints the drivers that they
- (maybe) are booting from a non-healthy condition and need
** Changed in: kernel-sru-workflow/snap-release-to-candidate
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 w
** 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
-- swm properties --
boot
I wasn't able to reproduce it in hyper-v or in azure using the 4.15.0-45
generic kernel.
--
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/1779640
Title:
[Hyper-V] KVP daemon crashes at sta
I can't reproduce the problem any more with 340 either:
~$ apt-cache policy nvidia-340
nvidia-340:
Installed: 340.107-0ubuntu0.18.04.2
Candidate: 340.107-0ubuntu0.18.04.2
Version table:
*** 340.107-0ubuntu0.18.04.2 400
400 http://archive.ubuntu.com/ubuntu bionic-proposed/restricted
** Changed in: kernel-sru-workflow/snap-release-to-candidate
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 w
Snap beta testing complete, no regressions found. Ready for promotion.
Results here: https://trello.com/c/plDdBsnS/749-pc-kernel-440-143169-188
** Changed in: kernel-sru-workflow/snap-certification-testing
Status: Confirmed => Fix Released
--
You received this bug notification because you
Snap beta testing complete, no regressions found. Ready for promotion.
Results here:
https://trello.com/c/rY5iUjvX/750-pi2-kernel-440-1104112-83
** Changed in: kernel-sru-workflow/snap-certification-testing
Status: Confirmed => Fix Released
--
You received this bug notification because yo
Still actual for me.
Please, can someone answer on the bug?
--
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/1808886
Title:
Microcode SW error detected. Restarting 0x0.
Status in linux pa
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
Just correcting a wrong comment (#2) I made:
> It happens on both 32bit and 64bit installations.
I asked the school that reported the issue on 64bit to check again, and
they said they have a 32bit installation after all.
So the problem has only been reported in 32bit installations; I don't
know i
** Changed in: kernel-sru-workflow/snap-release-to-beta
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/snap-release-to-edge
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/snap-certification-testing
Status: New => Confirmed
** Descr
Does it also happen with the lastest generic bionic kernel (4.15.0-45)?
--
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/1779640
Title:
[Hyper-V] KVP daemon crashes at startup
Status in l
Tested `sudo apt install xserver-xorg-hwe-18.04` after activating
proposed in the affected machine. Now working as intended. Rebooted,
checked Xorg version with `sudo X -version` (X.Org X Server 1.20.1) and
run `nvidia-smi` showing driver 390.77 version and installed cards
without any issues.
So,
That's the expected result. Only multiqueue io schedulers will be
available for multiqueue block devices.
--
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/1813211
Title:
Allow I/O sc
This bug was fixed in the package shim-signed - 1.33.1~14.04.4
---
shim-signed (1.33.1~14.04.4) trusty; urgency=medium
* update-secureboot-policy: (LP: #1748983)
- Backport update-secureboot-policy changes to generate a MOK and guide
users through re-enabling validation an
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic
--
You received this bug notificat
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic
--
You received this bug notificat
This bug was fixed in the package dkms - 2.2.0.3-1.1ubuntu5.14.04.10
---
dkms (2.2.0.3-1.1ubuntu5.14.04.10) trusty; urgency=medium
* debian/patches/shim_secureboot_support.patch:
- Move to signing just after module build to ensure it correctly applies
at kernel update time
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic
--
You received this bug notificat
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic
--
You received this bug notificat
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic
--
You received this bug notificat
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic
--
You received this bug notificat
Hello:
I'm an ex-Ubuntu user and thought I'd add some information which may be
useful.
I came across this thread while looking for answers to problems posed by
the e1000e driver for my Sun Microsystems Ultra 24 on-board ethernet
controller.
It's an Intel Corporation 82566DM-2 Gigabit Network Con
This bug was fixed in the package dkms - 2.2.0.3-1.1ubuntu5.14.04.10
---
dkms (2.2.0.3-1.1ubuntu5.14.04.10) trusty; urgency=medium
* debian/patches/shim_secureboot_support.patch:
- Move to signing just after module build to ensure it correctly applies
at kernel update time
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic
--
You received this bug notificat
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic
--
You received this bug notificat
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic
--
You received this bug notificat
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic
--
You received this bug notificat
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic
--
You received this bug notificat
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic
--
You received this bug notificat
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic
--
You received this bug notificat
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic
--
You received this bug notificat
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic
--
You received this bug notificat
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic
--
You received this bug notificat
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic
--
You received this bug notificat
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic
--
You received this bug notificat
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic
--
You received this bug notificat
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic
--
You received this bug notificat
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic
--
You received this bug notificat
** Description changed:
- Since kernel v4.5, the correct parameter to disable USB subsystem
- initialization is "usbcore.nousb" always (instead of "nousb" in case the
- subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb:
- make "nousb" a clear module parameter").
+ [Impact]
+ Cra
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic
--
You received this bug notificat
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic
--
You received this bug notificat
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic
--
You received this bug notificat
This bug was fixed in the package shim-signed - 1.33.1~16.04.4
---
shim-signed (1.33.1~16.04.4) xenial; urgency=medium
* update-secureboot-policy: (LP: #1748983)
- Backport update-secureboot-policy changes to generate a MOK and guide
users through re-enabling validation an
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic
--
You received this bug notificat
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic
--
You received this bug notificat
The verification of the Stable Release Update for shim-signed 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 encount
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic
--
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/1775217
Title:
bluetooth controller fail
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
** Changed in: kernel-sru-workflow/snap-release-to-beta
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/snap-release-to-edge
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/snap-certification-testing
Status: New => Confirmed
** Descr
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
Sorry for the delay. That might be a dependency problem on the KVP
systemd service. I will run some tests locally. Can you confirm if the
problem also happens with the linux-azure kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
1 - 100 of 485 matches
Mail list logo
