Yes it still happens even with recent Ubuntu and Linux Kernel (5.1).
I guess it's neither a Ubuntu nor a Linux Kernel problem but a bios problem of
the Dell Precision 5520 but unfortunately I have no Windows installed to
verify.
So you could close this ticket.
Thx, Matthias
--
You received t
Hello,it is a great post.It's been such a wonderful experience while reading
your blog.
If facing any problem related to printer please visit https://www.brotherprintersupport247.com/blog/resolve-konica-printer-error-code-c0202/";>
konica printer error c0202
and call us on toll free no. USA: +1-88
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
- backports: bug 1829171 (bionic/li
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
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.laun
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please f
** Changed in: gnome-bluetooth (Fedora)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1791405
Title:
bluetooth always in discoverable mode (securit
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains
Created attachment 144365
dmesg with constant_n forced true
Unfortunately not. Attached dmesg from using the newly compiled kernel
with the forced constant_n
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
Working (fastset at boot):
[3.494890] [drm:intel_dump_pipe_config [i915]] dp m_n: lanes: 4; gmch_m:
6213395, gmch_n: 8388608, link_m: 517782, link_n: 524288, tu: 64
Broken (modeset):
[ 192.531640] [drm:intel_dump_pipe_config [i915]] dp m_n: lanes: 4; gmch_m:
6213395, gmch_n: 8388608, link_m
Same thing happens to me, drops to the exact same wrong modeset after
changing the bool value.
(wrong modeset) dp m_n: lanes: 4; gmch_m: 24271, gmch_n: 32768, link_m:
32361, link_n: 32768, tu: 64
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
Created attachment 144358
dmesg from 5.1.4-arch1-1-ARCH with drm.debug=14
Adding a dmesg of my current kernel with fastboot enabled, 0-70s is the
correct behaviour, after that its me closing the lid, waiting a bit and
then opening it to a flickery display. Seems like the later part gets a
lot of h
@Stan/Maarten, can you help here? Any further suggestions?
--
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/1785912
Title:
Horizontal screen flicker Intel UHD graphics 620 (rev 07) Lenovo
** Changed in: ubuntu-z-systems
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/1829972
Title:
Require improved hypervisor detection patch in U
** Changed in: linux (Ubuntu Bionic)
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/1829972
Title:
Require improved hypervisor detection patch
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 1821269
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Package changed: alsa-driver (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/1821269
Title:
[Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-
You have been subscribed to a public bug:
I use realtek alc255 analog audio jack. External jack is 4 pole combo(apple
type. not europe type.).
When I plug 4 pole mic into jack, It doesn't detect.
So I can't my voice through external mic.
My laptop has internal mic. It belongs to Intel sound(HDA
I backported an i915 patch for glk machines, please remove the
workaround of "probe_mask=1" (#4) and test this kernel:
sudo dpkg -i linux-imgae-unsigned-xxx.deb
sudo dpkg -i linux-modules-xxx.deb
sudo dpkg -i linux-modules-extra-xxx.deb
reboot and choose the new installed kernel to boot, then red
Does this issue still happen?
--
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/1801359
Title:
Notebook lid blank after booting with lid closed
Status in linux package in Ubuntu:
Triaged
and?
not sure what you are trying to say (vanvugt).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu.
https://bugs.launchpad.net/bugs/1830582
Title:
nvidia-384 384.130-0ubuntu0.16.04.2: nvidia-384 k
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
Note: Missing test cases in s390x are caused by the test list in CKCT
--
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/1829203
Title:
linux-fips: 4.4.0-1011.14 -proposed tracker
Status in
** Summary changed:
- nvidia-384 384.130-0ubuntu0.16.04.2: nvidia-384 kernel module failed to build
+ nvidia-384 384.130-0ubuntu0.16.04.2: nvidia-384 kernel module failed to build
[arch/x86/Makefile:245: *** You are building kernel with non-retpoline
compiler, please update your compiler.. Stop
4.4.0-1011.14 - fips
Regression test CMPL, RTB.
52 / 54 tests were run, missing: ubuntu_boot, xfstests
Issue to note in amd64:
ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) debug (bug 1821906)
ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784)
fanotify07/fanotify08 t
** Merge proposal linked:
https://code.launchpad.net/~canonical-hwe-team/+git/iwlwifi-dkms/+merge/367972
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1830822
Title:
Killer 1650
This patch fixes the issue.
https://marc.info/?l=linux-wireless&m=155775442619906&w=2
Intel has a similar fix but doesn't public yet, so keep this patch as
sauce patch in ubuntu
** Description changed:
- Tried main line kernel v5.1-rc4, iwlwifi is looking for firmware named
- iwlwifi-QuQnj-b0-hr
(In reply to Moritz Naumann from comment #592)
> The latest firmware for X370 Taichi, v5.50 (2019/4/24), removes the "Power
> Supply Idle Control" option off the configuration UI; downgrading is not
> supported (but effectively possible at least from Windows). It is still
> possible to set "Power S
So Ryzen 3000 is coming, who will be the first guinea pig?
Curious to see if this problem is mysteriously, entirely fixed on the
3000 series.
(I damn well hope so)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
** Tags added: originate-from-1828147 somerville
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1830822
Title:
Killer 1650X Wifi/BT(2723:1654) fails to load correct firmware
Status
Also, the attached UdevDb.txt shows i2c bus support on DisplayPort (and
HDMI?) only.
If possible, please connect the monitor via DisplayPort or HDMI.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
This might be a driver bug or it might be a hardware problem.
In case it is a driver bug then I have assigned it to both the 'modeset'
Xorg driver and the kernel 'i915' driver. Can you please boot a newer
version of Ubuntu from USB and tell us if it has the same problem?
19.10: http://cdimages.
Public bug reported:
Tried main line kernel v5.1-rc4, iwlwifi is looking for firmware named
iwlwifi-QuQnj-b0-hr-b0-XX.ucode but those firmware files doesn't exist.
[ 4.252701] iwlwifi :03:00.0: enabling device ( -> 0002)
[ 4.263301] iwlwifi :03:00.0: Direct firmware load for
iwlwifi-
This is happening on two system with an Intel motherboard. Other systems
with a Silicon Mechanics motherboard and the same OS do not crash when
rsync is used.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
I backported a i915 patch, let us see if it can fix this problem on glk
machines, please test this kernel:
https://drive.google.com/drive/folders/1K7OrvkUTiub7vRaicen6smXR6TiDdBTM?usp=sharing
remove the workaround of #10
sudo dpkg -i linux-modules-.deb
sudo dpkg -i linux-image-unsigned-xxx.de
supplement for #8, don't forget to remove the module para in the #3
before testing the #8
--
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/1826868
Title:
Sound device not detected after re
This bug was fixed in the package debian-installer - 20101020ubuntu573
---
debian-installer (20101020ubuntu573) eoan; urgency=medium
* No-change rebuild to pick up new hw-detect and partman-iscsi.
(LP: #1817321)
-- Mauricio Faria de Oliveira Wed, 22 May 2019
10:30:55 -0300
I backported a i915 patch, let us see if it can fix this problem on glk
machines, please test this kernel:
https://drive.google.com/drive/folders/1K7OrvkUTiub7vRaicen6smXR6TiDdBTM?usp=sharing
sudo dpkg -i linux-modules-.deb
sudo dpkg -i linux-image-unsigned-xxx.deb
sudo dpkg -i linux-modules
Public bug reported:
[Impact]
TBD
[Test Case]
TBD
[Fix]
TBD
[Regression Risk]
TBD
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Disco)
Importance: Undecided
Assignee: dann frazier (dan
Somewhat different the second time around. This is with the 5.0.05-15
kernel.
[Tue May 28 17:36:56 2019] general protection fault: [#1] SMP PTI
[Tue May 28 17:36:56 2019] CPU: 23 PID: 0 Comm: swapper/23 Not tainted
5.0.0-15-generic #16~18.04.1-Ubuntu
[Tue May 28 17:36:56 2019] Hardware name
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
Sadly it died with this crash:
[Tue May 28 14:46:58 2019] ib0: enabling connected mode will cause multicast
packet drops
[Tue May 28 14:46:58 2019] ib0: mtu > 4092 will cause multicast packet drops.
[Tue May 28 14:46:58 2019] IPv6: ADDRCONF(NETDEV_CHANGE): ib0: link becomes
ready
[Tue May 28 14:
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow se
Known Bugs:
amd64:
ubuntu_kernel_selftests:(1812978) rtnetlink.sh in net from
ubuntu_kernel_selftests fails ,
ubuntu_kvm_unittests:(1821394) vmx tests fail in kvm_unit_tests, (1821390):
apic-split will fail in kvm_units_tests
ubuntu_ltp:(1819116): sync_file_range02 in ubuntu_ltp_syscalls fails
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 1830813
and then change the status of the bug to 'Confirmed'.
If, due to the nature
affects bionic, 4.15.0-1040.42 linux-aws
** Summary changed:
- sync_file_range02 in ubuntu_ltp_syscalls fails C/D
+ sync_file_range02 in ubuntu_ltp_syscalls fails
** Tags added: aws bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Patch added: "eoan_partman-iscsi.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817321/+attachment/5267258/+files/eoan_partman-iscsi.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
Hi Eric,
Nice catch. Sorry about that!
Sure, just attached the partman-iscsi debdiffs with the LP bug mentioned
in changelog.
Thanks,
Mauricio
--
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
** Patch added: "disco_partman-iscsi.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817321/+attachment/5267257/+files/disco_partman-iscsi.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Patch removed: "bionic_partman-iscsi.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817321/+attachment/5265733/+files/bionic_partman-iscsi.debdiff
** Patch removed: "cosmic_partman-iscsi.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817321/+attachment/52
** Tags added: regression-testing-passed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1829168
Title:
linux-gcp: 5.0.0-1007.7 -proposed tracker
Status in Kernel SRU Workflow:
In
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Patch added: "cosmic_partman-iscsi.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817321/+attachment/5267256/+files/cosmic_partman-iscsi.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow se
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
derivatives: bug 1829847 (linux-g
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow se
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1829196 (xenial/li
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1829192 (xenial/li
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1829208 (xenial/li
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1829213 (trusty/li
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
Public bug reported:
SRU Justification
Impact: WARN_ON messages casued by race condition between the close of
a TCP socket and another process inspecting the same socket.
The code of interest is the following; in tcp_close function :
...
release_sock(sk);
...
WARN_ON(sock_owned_by_user(sk));
..
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1829205 (trusty/li
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow se
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow se
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow se
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow se
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow se
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow se
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow se
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1829198
Title:
linux-raspi2: 4.4.0-11
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow se
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1829195
Title:
linux-kvm: 4.4.0-1047.53
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1829191
Title:
linux-oem: 4.15.0-1039.44
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1829187
Title:
linux-raspi2: 4.15.0-1
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1829200
Title:
linux-gcp: 4.15.0-1033.35
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-snapdragon in Ubuntu.
https://bugs.launchpad.net/bugs/1829189
Title:
linux-snapdragon:
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-snapdragon in Ubuntu.
https://bugs.launchpad.net/bugs/1829201
Title:
linux-snapdragon:
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow se
** Changed in: kernel-sru-workflow/security-signoff
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/1829209
Title:
linux: 4.4.0-149.175 -propose
Sponsored 'd-i' for Eoan, now that both hw-detect and partman-iscsi have
been built and land in release.
- Eric
** Changed in: debian-installer (Ubuntu Eoan)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is s
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1829214 (xenial/li
** Changed in: kernel-sru-workflow/security-signoff
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/1829219
Title:
linux: 4.15.0-51.55 -proposed
I apologise, I totally miss the fact that the second upload for partman-
iscsi didn't have the LP# mentioned in the changelog.
We are all human, mistake happens ;) So I did the LP modification
manually.
@mfo, could you produce a debdiff V2 for 'partman-iscsi' debdiff(s) and
make sure it contains
This bug was fixed in the package partman-iscsi - 40ubuntu4
---
partman-iscsi (40ubuntu4) eoan; urgency=medium
* Add support for different network interfaces and iscsi_auto for iBFT.
- debian/partman-iscsi.template: add partman-iscsi/iscsi_auto option.
- finish.d/iscsi_setti
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
derivatives: bug 1829178 (linux-a
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
I'm having similar problems with rsync killing a 18.04 head node that's
writing to a NFS share. It would die pretty quickly with rsync or
globus. We had a dozens of crashes, we originally thought it was a
hardware issue, but switching to a different server didn't help.
We tried:
```
$ apt instal
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1829176 (bionic/li
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1829182 (bionic/li
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1829179 (bionic/li
1 - 100 of 184 matches
Mail list logo
