My alsa info: http://alsa-
project.org/db/?f=9f087f5038e450cf77cdf21d21f86af763626d787
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850439
Title:
No sound on ASUS UX534FT
To manage notifications
This bug was fixed in the package apport - 2.20.9-0ubuntu7.11
---
apport (2.20.9-0ubuntu7.11) bionic; urgency=medium
* Create additional symlinks to the source_linux.py apport package hook for
many OEM kernels. Thanks to You-Sheng Yang for the patch. (LP: #1847967)
apport
Tried just now. After reboot "AuthInfoRequired username,password" still
there
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849859
Title:
smb printing fails
To manage notifications about this bug
This bug was fixed in the package apport - 2.20.9-0ubuntu7.11
---
apport (2.20.9-0ubuntu7.11) bionic; urgency=medium
* Create additional symlinks to the source_linux.py apport package hook for
many OEM kernels. Thanks to You-Sheng Yang for the patch. (LP: #1847967)
apport
** 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 --
The verification of the Stable Release Update for apport has completed
successfully and the package is now being 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
correct link: http://alsa-
project.org/db/?f=9f087f5038e450cf77cdf21d21f86af763626d78
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850439
Title:
No sound on ASUS UX534FT
To manage notifications
This bug was fixed in the package apport - 2.20.11-0ubuntu8.4
---
apport (2.20.11-0ubuntu8.4) eoan; urgency=medium
* Create additional symlinks to the source_linux.py apport package hook for
many OEM kernels. Thanks to You-Sheng Yang for the patch. (LP: #1847967)
apport
This bug was fixed in the package apport - 2.20.11-0ubuntu8.4
---
apport (2.20.11-0ubuntu8.4) eoan; urgency=medium
* Create additional symlinks to the source_linux.py apport package hook for
many OEM kernels. Thanks to You-Sheng Yang for the patch. (LP: #1847967)
apport
Public bug reported:
I don't have any idea
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.6
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CasperVersion: 1.394
Date: Tue
Does anyone know if there are a libxp for armhf? I only found for x86.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1517884
Title:
libxp6 not available in xenial
To manage notifications about
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-eoan
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
Public bug reported:
Playing with fence_scsi I have noticed that one of my images did not
have lvm2 package installed. With that, the following error ocurred:
$ sudo fence_scsi -n clufocal03 --action=status
2020-02-17 19:57:02,324 ERROR: Unable to run /sbin/vgs --noheadings --separator
: --sort
** 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) => Andy
Whitcroft (apw)
--
You received this bug notification because you are 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 --
** 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 --
This bug was fixed in the package masakari -
9.0.0~b2~git2020020609.8b122a8-0ubuntu2
---
masakari (9.0.0~b2~git2020020609.8b122a8-0ubuntu2) focal; urgency=medium
* d/p/allow-bare-hostnames.patch: Cherry pick inflight fix to allow use of
bare hostnames when adding hosts to
** Changed in: kernel-sru-workflow/promote-to-updates
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
** 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 --
** 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) => Andy
Whitcroft (apw)
--
You received this bug notification because you are a
This also effects Focal. Considering Focal is LTS and will run on
servers with RAID arrays it'd be a good idea to fix this before release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858342
Title:
I inspected perl code in /usr/bin/debsums...
The logic around catchink symlink loop is a bit flawed. Its in a
function resolve_path() and it is only called from method .check() which
intends to verify if the file can be opened. Since its goal is to find
any bad files, symlink loop should be
Public bug reported:
Playing with fence_scsi I have noticed that one of my images did not
have lvm2 package installed. With that, the following error ocurred:
$ sudo fence_scsi -n clufocal03 --action=status
2020-02-17 19:57:02,324 ERROR: Unable to run /sbin/vgs --noheadings --separator
: --sort
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-eoan
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
** 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 --
Strange results from the continued testing:
The Xubuntu iso file dated 2020-02-17 01:04 fails too (like the
Lubuntu iso filefrom Febr.16)
The Ubuntu iso file dated 2020-02-1707:50 succeeds (there is
persistence with this method)
Lubuntu is updated:
The Lubuntu iso file dated 2020-02-17
** 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) => Andy
Whitcroft (apw)
--
You received this bug notification because you are a
Just FYI there is now a new solution, no need for HPLIP nor proprietary
drivers with other manufacturers.
Most Multi-function scanners and now some stand alone scanners are
Airscan/eSCL compatible, which includes most HP multifunctions. Also
Kyocera, Cannon, Epson and more support eSCL/Airprint.
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** 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:
** Package changed: ubuntu => sane-backends (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862847
Title:
New Epson V19 scanner problems under Ubuntu 18.04.3
To manage notifications about
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** 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:
"Warning: Unable to find the persistent medium" is the message
indicating failure.
Do you know how to make changes to the initramfs? (I know it's not the
simplest procedure)
If you do, can you insert "ls -l /dev/disk/by-label/" just above the "if
[ ! -e "/dev/disk/by-label/${root_persistence}" ]
and a file corresponding to the file in comment #2
** Attachment added: "lubuntu-2020-02-17-18-40-46-00_label-writable_works.txt"
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1863672/+attachment/5329099/+files/lubuntu-2020-02-17-18-40-46-00_label-writable_works.txt
--
You received
Sorry for the misunderstanding alias careless reading of your
instructions. I got it now, and Lubuntu works, when I modified the label
to 'writable' (and kept the boot option persistent). To make things
complete I will give you the log file for this case too.
** Attachment added: "casper.log2"
So it seems to me that the problem for the community flavours is the
label. The are not accepting the old casper-rw. By the way, what about
home-rw. Will it be recognized by this new version?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** 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:
** 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:
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-lrm
Status: In Progress => Fix Committed
**
LiVES 3.0.2 is now in Ubuntu Focal
(https://bugs.launchpad.net/ubuntu/+source/lives/3.0.2-1)
** Changed in: lives (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: docker.io (Ubuntu)
Status: New => Fix Committed
** Changed in: runc (Ubuntu)
Status: New => Fix Committed
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-19921
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** 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 --
This bug was fixed in the package linux-azure-5.3 -
5.3.0-1013.14~18.04.1
---
linux-azure-5.3 (5.3.0-1013.14~18.04.1) bionic; urgency=medium
* bionic/linux-azure-5.3: 5.3.0-1013.14~18.04.1 -proposed tracker
(LP: #1862397)
[ Ubuntu: 5.3.0-1013.14 ]
* eoan/linux-azure:
Still no luck with 5.5.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860284
Title:
thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on
Yoga C940 unless plugged in before boot
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
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
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
Hello George, or anyone else affected,
Accepted containerd into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/containerd/1.3.3-0ubuntu1~18.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello George, or anyone else affected,
Accepted containerd into eoan-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/containerd/1.3.3-0ubuntu1~19.10.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
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
There is a further failure on s390x only:
cd /<>/obj-s390x-linux-gnu/plugins && /usr/bin/cmake -E
cmake_link_script CMakeFiles/check_nscp_api.dir/link.txt --verbose=1
/usr/bin/c++ -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
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 1863675
and then change the status of the bug to 'Confirmed'.
If, due to the
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863592
Title:
bionic/linux-oem: 4.15.0-1073.83
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
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
Public bug reported:
Hello everyone.
Recently I've bought a new laptop ASUS Zenbook 15 UX534FTC. I installed
Ubuntu 18.04 on it and everything works fine except sound. When music
plays - pavucontrol indicates that there is sound, but my speakers are
silent. No sound at all.
I googled that
** 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:
** 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 --
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
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
** 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:
** 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 --
+
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-eoan
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
Same issue (version 80.0.3987.87-0ubuntu0.16.04.1 on 16.04 Xenial),
although mine shows up as yellow-green. Downgrading to
79.0.3945.130-0ubuntu0.16.04.1 fixed the problem.
For others experiencing the problem, I was able to find the three needed
files (referenced in the bug description) here:
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-xenial
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-bionic
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-bionic
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
** Tags removed: verification-needed-bionic verification-needed-disco
verification-needed-eoan
** Tags added: verification-done-bionic verification-done-disco
verification-done-eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855685
Title:
change kconfig of the soundwire bus driver from y to m
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855666
Title:
alsa/sof: change to use hda hdmi codec driver to make
@ Rex,
If we apply the [1], it will make users easily reproduce the [2], that
is why kernel maintainer reverted the [1].
I thought I backport the [2] to the kernel first, then backport [1] to
the kernel, I tried to backport the [2] to the osp1 kernel myself, but
it didn't work at all, so I asked
You have been subscribed to a public bug:
Latest shim update on ubuntu 14.04LTS (shim-signed:amd64
1.33.1~14.04.2+13-0ubuntu2) deleted grubx64.efi boot option - resulting
the loss of boot capability.
The earlier shim update also resulted in loss of boot capability, but
then shim did not delete
*** This bug is a duplicate of bug 1861989 ***
https://bugs.launchpad.net/bugs/1861989
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1861989, so is being marked as such.
Please run 'top' to find out the name of the process(es) using the most
CPU and tell us what they are. Or just attach a screenshot of the top
window here.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification
** Changed in: mstflint (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863483
Title:
Mstflint package update to 4.13.3-2
To manage notifications
** 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 --
https://wiki.ubuntu.com/PhasedUpdates should explain what you're seeing.
** Changed in: update-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858961
This bug was fixed in the package linux-raspi2-5.3 -
5.3.0-1018.20~18.04.1
---
linux-raspi2-5.3 (5.3.0-1018.20~18.04.1) bionic; urgency=medium
* bionic/linux-raspi2-5.3: 5.3.0-1018.20~18.04.1 -proposed tracker
(LP: #1861196)
[ Ubuntu: 5.3.0-1018.20 ]
* eoan/linux-raspi2:
** 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 --
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
--
You received this bug notification because you are a
Thanks christian, you are right.
I opened this in rush thinking about not forgetting it when doing the
fixes after the freeze.
/usr/share/doc/tgt/examples/targets.conf.example <- here you go, as you
said!
Not sure I should worry about changing the man page about it or not. In
this case, for
Thanks christian, you are right.
I opened this in rush thinking about not forgetting it when doing the
fixes after the freeze.
/usr/share/doc/tgt/examples/targets.conf.example <- here you go, as you
said!
Not sure I should worry about changing the man page about it or not. In
this case, for
** Changed in: syslog-ng (Ubuntu)
Status: New => Invalid
** Changed in: octopussy (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861374
Title:
** Tags added: fixed-in-3.35.91 fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827751
Title:
Shield screen is displayed after blanking even when lock screen
disabled
To manage
I agree, but we're not the developers of PulseAudio and we have
thousands of software packages to get into Ubuntu... Polishing each one
to reduce log noise is not usually something we have time to do.
If you would like the issue fixed then please report it to the PulseAudio
developers at
*** This bug is a duplicate of bug 1855608 ***
https://bugs.launchpad.net/bugs/1855608
Thanks for the bug report. This sounds like a kernel bug but are you
able to provide additional photos of the bug under different conditions?
** Summary changed:
- Screen is scrambled/distored and
*** This bug is a duplicate of bug 1855608 ***
https://bugs.launchpad.net/bugs/1855608
Nevermind. It looks like bug 1855608 already describes the same issue so
let's use that.
** This bug has been marked a duplicate of bug 1855608
Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and
Yes, error report links are mostly anonymous. Except for your username
but in this case it is user 121 which is the built-in user 'gdm' (owner
of the login screen).
I think it's generally just Bug Control members who can view the page so
it is secure.
Please share the bug link here.
--
You
I can partially reproduce this on Ubuntu Mate 20.04 development release,
updated from 19.10. Hardware is a ThinkPad X230.
Steps to reproduce:
- mount an rclone remote drive
- do something which keeps the mountpoint busy (e.g. open the file manager and
navigate to a photos folder on the remote
Any chances of this landing in 20.04 ?
I really would like to have:
- python3-configshell-fb
- python3-rtslib-fb
- targetcli-fb
included in 20.04 [main] as the official - including the kernel side -
way to provide iSCSI targets
(https://www.kernel.org/doc/Documentation/target/tcmu-design.txt)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855608
Title:
Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** 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:
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** 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:
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** 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:
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** 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:
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** 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:
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** 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:
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** 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:
[Expired for gnome-control-center (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
301 - 400 of 1056 matches
Mail list logo
