Another result. When I tried the v18.04.3 system preview from the USB
FD, the background was "normal". I just finished installing the system,
and the background now has the transparent red raster overlay. I could
get to "Settings" though without locking up the system, so there was at
least a
Public bug reported:
Install failed grub would not install not boot.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.4
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
Uname: Linux 5.4.0-9-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Found a fix
https://www.andreagrandi.it/2013/06/22/how-to-make-subwoofer-work-in-
ubuntu/
thank me later :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553685
Title:
Lenovo Y700-17ISK
*** This bug is a duplicate of bug 1832701 ***
https://bugs.launchpad.net/bugs/1832701
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 #1832701, so is being marked as such.
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832701
Title:
kglobalaccel5 crashed with SIGABRT in raise()
To manage notifications about this bug go to:
** Changed in: mawk (Debian)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1332114
Title:
Please update mawk to latest upstream release
To manage notifications
** Changed in: mawk (Debian)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/490736
Title:
mawk 1.3.3-17ubuntu2 incorrectly handles "/" in "[ ]" expressions
To manage
Public bug reported:
Installer crashed during File Copy Process
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubiquity 19.10.21
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
andrei@HP-Laptop-15:~$ dmesg | grep 8723
[3.020266] rtl8723de: Using firmware rtlwifi/rtl8723defw.bin
[3.232218] rtl8723de :03:00.0 wlo1: renamed from wlan0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
andrei@HP-Laptop-15:~$ dmesg |grep -i firm
[0.581507] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[0.612749] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain [bus
00-7f] only partially covers this bridge
[2.926260] [drm] Found VCN firmware Version ENC: 1.9 DEC: 1
Public bug reported:
i install drivers from https://github.com/lwfinger/rtlwifi_new master and
extendet branches
not one version fixed my bluetooth
Uubntu 19.10
** Affects: linux-oem (Ubuntu)
Importance: Undecided
Status: Confirmed
** Changed in: linux-oem (Ubuntu)
** Changed in: mawk (Debian)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1074404
Title:
Segfault with mawk
To manage notifications about this bug go to:
judging by the log I have a slightly different device. rtl8723defw
andrei@HP-Laptop-15:~$ dmesg |grep -i firm
[0.574316] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[0.601064] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain [bus
00-7f] only partially covers this
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]
** Changed in: firefox (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: ubuntu-release-upgrader (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.
[Expired for dpkg (Ubuntu) because there has been no activity for 60
days.]
** Changed in: dpkg (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853725
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853701
[Expired for llvm-toolchain-9 (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: llvm-toolchain-9 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for unattended-upgrades (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: unattended-upgrades (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.
I can no longer reproduce it either. *shrug*
P.S. Hi Ted long time no see.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860676
Title:
apt-get dist-upgrade -y hangs during e2fsprogs update
To
Public bug reported:
1)
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
(2020/01/25 daily build)
2)
( https://wiki.ubuntu.com/Bugs/FindRightPackage. `locate -b` is not working... )
~/$ apt-cache policy xserver-xorg-input-wacom
xserver-xorg-input-wacom:
Hmm... I can't duplicate this on Debian testing, which is using a newer
version of e2fsprogs (1.45.5-2). The e2scrub_reap.service file is
identical with Ubuntu's 1.45.3-4ubuntu2.1, though. And looking at the
service file, I have no idea why systemctl would be trying to paskk for
a password,
Public bug reported:
Happened as soon as Firefox was updated to 72.0.1. I noticed sites could
not determine my location.
Troubleshooting page shows "missing" under Location service key.
I have another computer running Lubuntu 18.04LTS, which I rarely use.
Just for fun, I booted it up and as
Yes, this looks like the same thing. The root of the problem is that
/usr/bin/wodim is lacking the u+s (where user=root) permission.
Fixing it might just be a matter of changing the permissions of this
file in the .deb package. However, if upstream expects wodim to be
installed in the home
I think this is the same as
https://bugs.launchpad.net/ubuntu/+source/cdrkit/+bug/1769848
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811641
Title:
Wodim permissions error: /usr/bin/wodim:
APT forced me to stop using the DEB version and start using the Snap
version and I can confirm it is much slower to start on Ubuntu 19.10
(5.3.0-26)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi. Yes, I get the same crash with the 4.15.0-1054.58 proposed kernel.
Log attached.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860659
Title:
4.15.0-1053 contains fatal nilfs2 kernel bug
To
** Attachment added: "linux-raspi2 4.15.0-1054 (bionic-proposed) boot log.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1860659/+attachment/5322709/+files/linux-raspi2%204.15.0-1054%20%28bionic-proposed%29%20boot%20log.txt
--
You received this bug notification because you
Thank you for reporting this bug to Ubuntu.
Ubuntu 18.04 LTS has two upgrade paths
1: non-LTS path is to the next release which was 18.10, is now closed as
it's EOL. That is the only upgrade path tested & supported off LTS path
2. to the next LTS which won't open until the launch of Ubuntu
** 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 --
** 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/security-signoff
Status: In Progress => 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/1858588
Title:
xenial/linux-snapdragon: 4.4.0-1132.140
** 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/security-signoff
Status: In Progress => 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/1858586
Title:
xenial/linux-raspi2: 4.4.0-1128.137
** 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/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
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => 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/1859718
Title:
xenial/linux: 4.4.0-173.203 -proposed
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => 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/1858584
Title:
xenial/linux-kvm: 4.4.0-1065.72 -proposed
Hello, this appears to be working as designed.
In Linux, process tracing is tied with the process dumping flag. The
dumpable flag is cleared at execve(2) time when a setuid or setgid
application is executed. This flag persists to child processes created
by fork(2) and will only be reset when a
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/security-signoff
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: mawk (Debian)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1159933
Title:
mawk %d maxes out at 0x7FFF instead of 0x
To manage
OK I see now. I mistook Ubuntu 19.04 as the next LTS after 18.04. So my choices
will be:
1. Clean install of 18.04LTS
2. Upgrade to 19.10
3. Upgrade to 20.04 daily (after upgrade to 19.10)
--
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:
** Tags added: champagne
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860826
Title:
pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or
directory
To manage notifications about
*** This bug is a duplicate of bug 1860824 ***
https://bugs.launchpad.net/bugs/1860824
** This bug has been marked a duplicate of bug 1860824
IMAP with STARTTLS on port 143 is broken
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
All autopkgtests for the newly accepted poppler (0.80.0-0ubuntu1.1) for eoan
have finished running.
The following regressions have been reported in tests triggered by the package:
kopanocore/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
proceeding
Public bug reported:
Just upgraded to fossa. When clicking chromium-browser, title bar
switches to "Chromium Web Browser", spins for awhile and then disappears
nothing opens.
If it helps, running 'chromium-browser' at CLI is:
mark@zynxps:~$ chromium-browser
Failed to move to new namespace: PID
Public bug reported:
Hello, after upgrading to focal I found the following in my journalctl
output:
Jan 24 23:07:00 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open
/etc/securetty: No such file or directory
Jan 24 23:07:01 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open
Public bug reported:
can't get updates for ubuntu 19
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
Public bug reported:
Just upgraded from eoan -> fossa to test. Incoming mail is configured
to use STARTTLS over port 143 and works fine in eoan and bionic.
But in fossa, upon startup IMAP immediately fails with error message:
'The reported error was "Error performing TLS handshake: An
I went ahead and properly filed but 1860824 so this one can be closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860823
Title:
IMAP with STARTTLS is broken
To manage notifications about this
Bug still exists for me using version 6.0.7.3 on Ubuntu 18.04 opening
excel spreadsheet from smb mounted drive at
run/user/1000/doc/gvfs/smb...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1100190
Public bug reported:
Just upgraded from eoan -> fossa to test. Incoming mail is configured
to use STARTTLS over port 143 and works fine in eoan and bionic.
But in fossa, upon startup IMAP immediately fails with error message:
The reported error was “Error performing TLS handshake: An
Somehow this went the the wrong package; hopefully someone can reassign
it was intended to go to the 'evolution' package directly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860823
Title:
IMAP
** 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/security-signoff
Status: In Progress => 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/1860119
Title:
eoan/linux: 5.3.0-29.31 -proposed tracker
Public bug reported:
I cannot attach to a process with gdb despite setting ptrace_scope to 0.
The process has no capabilities, and is running under my uid & gid.
The process is a child, forked from a privileged program that has
divested itself of its parent's privileges. The parent is setgid
** 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 --
additional update kernel-5.3.0-26 after 10 min.
gui hung again.
I force power off PC, and restart again,
login and gui use again, but may be hung again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1860196/+attachment/5322677/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860196
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1860196/+attachment/5322672/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860196
Title:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1860196/+attachment/5322674/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
In safe graphics mode, the installation crashed while installing
packages. The only stranger thing i did was the manual partitioning:
/boot
/
/home
/efi
swap
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubiquity 19.10.21
ProcVersionSignature: Ubuntu
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1860196/+attachment/5322673/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860196
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1860196/+attachment/5322678/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860196
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1860196/+attachment/5322676/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860196
I found that restore backup file 2011-01-11,
and update to use software updater.
then gui not hung up.
but I do not know this backup can update normaly
I send informition apport-collect 1860196
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1860196/+attachment/5322670/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1860196/+attachment/5322671/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860196
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1860196/+attachment/5322675/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Description changed:
dear everyone.
I update ubuntu-18.04.3 to use software-updater,
then kernel update to 5.3.0-26.
Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up
fine.
but could not use applicaion, may be hung up.
could not
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1860196/+attachment/5322669/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860196
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1860196/+attachment/5322679/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860196
sorry I found that restore backup file 2020-01-11.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860196
Title:
kernel-5.3.0-26 could not use appliicatins on geforce 8600GTI
To manage
My machine did not reboot successfully; because I followed The Guide, my
system has a root password, and I was prompted for it at the systemd
emergency shell. (Which is super-confusing, because I forgot I had set a
password.)
The error message appeared to be along the lines of "bpool failed to
** Changed in: kernel-sru-workflow/verification-testing
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
** Changed in: kernel-sru-workflow/verification-testing
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
** Changed in: kernel-sru-workflow/verification-testing
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
** Changed in: kernel-sru-workflow/verification-testing
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
** Changed in: kernel-sru-workflow/verification-testing
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
** Changed in: kernel-sru-workflow/verification-testing
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
** Changed in: kernel-sru-workflow/verification-testing
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
** Changed in: kernel-sru-workflow/verification-testing
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
All autopkgtests for the newly accepted openssh (1:8.0p1-6ubuntu0.1) for eoan
have finished running.
The following regressions have been reported in tests triggered by the package:
libnet-scp-perl/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
** Changed in: kernel-sru-workflow/verification-testing
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
** Changed in: kernel-sru-workflow/verification-testing
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
** Changed in: kernel-sru-workflow/verification-testing
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
** Changed in: kernel-sru-workflow/verification-testing
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
** Changed in: kernel-sru-workflow/verification-testing
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
** Changed in: kernel-sru-workflow/verification-testing
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
** Changed in: kernel-sru-workflow/verification-testing
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
** Changed in: kernel-sru-workflow/verification-testing
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
** Changed in: kernel-sru-workflow/verification-testing
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
** Changed in: kernel-sru-workflow/verification-testing
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
Only one bug remains unverified for this kernel:
1858815 PAN is broken for execute-only user mappings on ARMv8
See this comment for information on verification of this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860123/comments/3
Manually setting the status of
** 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 --
1 - 100 of 637 matches
Mail list logo
