This bug was fixed in the package linux - 4.4.0-150.176
---
linux (4.4.0-150.176) xenial; urgency=medium
* linux: 4.4.0-150.176 -proposed tracker (LP: #1830941)
* glibc 2.23-0ubuntu11 ADT test failure with linux 4.4.0-149.175
(LP: #1830890)
- x86/vdso: Pass
This bug was fixed in the package linux - 4.4.0-150.176
---
linux (4.4.0-150.176) xenial; urgency=medium
* linux: 4.4.0-150.176 -proposed tracker (LP: #1830941)
* glibc 2.23-0ubuntu11 ADT test failure with linux 4.4.0-149.175
(LP: #1830890)
- x86/vdso: Pass
This bug was fixed in the package linux - 4.4.0-150.176
---
linux (4.4.0-150.176) xenial; urgency=medium
* linux: 4.4.0-150.176 -proposed tracker (LP: #1830941)
* glibc 2.23-0ubuntu11 ADT test failure with linux 4.4.0-149.175
(LP: #1830890)
- x86/vdso: Pass
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
This bug was fixed in the package linux - 4.4.0-150.176
---
linux (4.4.0-150.176) xenial; urgency=medium
* linux: 4.4.0-150.176 -proposed tracker (LP: #1830941)
* glibc 2.23-0ubuntu11 ADT test failure with linux 4.4.0-149.175
(LP: #1830890)
- x86/vdso: Pass
This bug was fixed in the package linux - 4.4.0-150.176
---
linux (4.4.0-150.176) xenial; urgency=medium
* linux: 4.4.0-150.176 -proposed tracker (LP: #1830941)
* glibc 2.23-0ubuntu11 ADT test failure with linux 4.4.0-149.175
(LP: #1830890)
- x86/vdso: Pass
This bug was fixed in the package linux - 4.15.0-51.55
---
linux (4.15.0-51.55) bionic; urgency=medium
* linux: 4.15.0-51.55 -proposed tracker (LP: #1829219)
* disable a.out support (LP: #1818552)
- [Config] Disable a.out support
* [UBUNTU] qdio: clear intparm during
This bug was fixed in the package linux - 5.0.0-16.17
---
linux (5.0.0-16.17) disco; urgency=medium
* linux: 5.0.0-16.17 -proposed tracker (LP: #1829173)
* shiftfs: lock security sensitive superblock flags (LP: #1827122)
- SAUCE: shiftfs: lock down certain superblock flags
This bug was fixed in the package linux - 5.0.0-16.17
---
linux (5.0.0-16.17) disco; urgency=medium
* linux: 5.0.0-16.17 -proposed tracker (LP: #1829173)
* shiftfs: lock security sensitive superblock flags (LP: #1827122)
- SAUCE: shiftfs: lock down certain superblock flags
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
This bug was fixed in the package linux - 4.18.0-21.22
---
linux (4.18.0-21.22) cosmic; urgency=medium
* linux: 4.18.0-21.22 -proposed tracker (LP: #1829186)
* disable a.out support (LP: #1818552)
- [Config] Turn off a.out support
* ftrace in ubuntu_kernel_selftests hang
This bug was fixed in the package linux - 4.18.0-21.22
---
linux (4.18.0-21.22) cosmic; urgency=medium
* linux: 4.18.0-21.22 -proposed tracker (LP: #1829186)
* disable a.out support (LP: #1818552)
- [Config] Turn off a.out support
* ftrace in ubuntu_kernel_selftests hang
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
Nautilus saves photo from Evince. But this process is some long.
I have one question. Should I report about this bug to GNOME project or you
will do it yourself? I understand that Evince is part of GNOME Project, but
it is part of Ubuntu too. So Ubuntu team can modify source code of Evince
and
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
This bug was fixed in the package linux-raspi2 - 4.18.0-1015.17
---
linux-raspi2 (4.18.0-1015.17) cosmic; urgency=medium
* linux-raspi2: 4.18.0-1015.17 -proposed tracker (LP: #1829174)
[ Ubuntu: 4.18.0-21.22 ]
* linux: 4.18.0-21.22 -proposed tracker (LP: #1829186)
* disable
Public bug reported:
Since a few weeks, my displays won't wake up from display powersave. The
machine stays responsive via SSH.
This first occurred on Ubuntu 18.04, and keeps happening on 18.10 (which
I had updated to in the hopes of fixing the issue that way).
The only escape I've found from
This bug was fixed in the package linux-gcp - 4.18.0-1012.13
---
linux-gcp (4.18.0-1012.13) cosmic; urgency=medium
* linux-gcp: 4.18.0-1012.13 -proposed tracker (LP: #1829183)
[ Ubuntu: 4.18.0-21.22 ]
* linux: 4.18.0-21.22 -proposed tracker (LP: #1829186)
* disable a.out
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831587
Title:
brightness control not work with OLED panel
To
This bug was fixed in the package linux-gcp-edge -
4.18.0-1012.13~18.04.1
---
linux-gcp-edge (4.18.0-1012.13~18.04.1) bionic; urgency=medium
* linux-gcp-edge: 4.18.0-1012.13~18.04.1 -proposed tracker (LP:
#1829182)
[ Ubuntu: 4.18.0-1012.13 ]
* linux-gcp: 4.18.0-1012.13
Followed up on this today. No joy. IRC log from #ubuntu-hardened:
12:37 Could we revisit Bug #1359836 ? At the very least the checksum
files should require HTTPS because most new users have no idea (nor sometimes,
facility) to verify using GPG - think Windows users coming to Ubuntu. This
This bug was fixed in the package linux - 4.4.0-150.176
---
linux (4.4.0-150.176) xenial; urgency=medium
* linux: 4.4.0-150.176 -proposed tracker (LP: #1830941)
* glibc 2.23-0ubuntu11 ADT test failure with linux 4.4.0-149.175
(LP: #1830890)
- x86/vdso: Pass
Verified for cosmic:
apt-cache policy cups-daemon
cups-daemon:
Installed: 2.2.8-5ubuntu1.4
lp -d PDF /usr/share/cups/data/default.pdf
PreserveJobHistory 30:
I [04/Jun/2019:09:12:13 +] [Job 1] Job completed.
D [04/Jun/2019:09:12:44 +] [Job 1] Removing from history.
PreserveJobHistory
This bug was fixed in the package linux-raspi2 - 5.0.0-1009.9
---
linux-raspi2 (5.0.0-1009.9) disco; urgency=medium
* linux-raspi2: 5.0.0-1009.9 -proposed tracker (LP: #1829164)
* Disco update: 5.0.8 upstream stable release (LP: #1828415)
- [Config]: add
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => 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
This bug was fixed in the package linux-gcp - 4.15.0-1033.35
---
linux-gcp (4.15.0-1033.35) bionic; urgency=medium
* linux-gcp: 4.15.0-1033.35 -proposed tracker (LP: #1829200)
[ Ubuntu: 4.15.0-51.55 ]
* linux: 4.15.0-51.55 -proposed tracker (LP: #1829219)
* disable a.out
This bug was fixed in the package linux-gcp - 5.0.0-1007.7
---
linux-gcp (5.0.0-1007.7) disco; urgency=medium
* linux-gcp: 5.0.0-1007.7 -proposed tracker (LP: #1829168)
* Disco update: 5.0.8 upstream stable release (LP: #1828415)
- [Config]: add CONFIG_LDISC_AUTOLOAD=y
-
Do you have access to the /var/log/ceph/ceph-volume-systemd.log after
the latest reboot? That should give us some details such as:
"[2019-05-31 20:43:44,334][systemd][WARNING] failed to find db volume,
retries left: 17"
or similar for wal volume.
If you see that the retries have been exceeded
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub-installer (Ubuntu)
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/1811205
Additional, more positive, discussion.
12:59 or just relax the policy and let us get LE certs outselves, just
like for all the other names
13:00 maybe we could do that if we registered a new domain name
13:01 I'll bring it up again soon
13:03 the problem is we round robin mirrors under
This bug was fixed in the package linux - 5.0.0-16.17
---
linux (5.0.0-16.17) disco; urgency=medium
* linux: 5.0.0-16.17 -proposed tracker (LP: #1829173)
* shiftfs: lock security sensitive superblock flags (LP: #1827122)
- SAUCE: shiftfs: lock down certain superblock flags
This bug was fixed in the package linux - 5.0.0-16.17
---
linux (5.0.0-16.17) disco; urgency=medium
* linux: 5.0.0-16.17 -proposed tracker (LP: #1829173)
* shiftfs: lock security sensitive superblock flags (LP: #1827122)
- SAUCE: shiftfs: lock down certain superblock flags
This bug was fixed in the package linux-hwe-edge - 5.0.0-16.17~18.04.1
---
linux-hwe-edge (5.0.0-16.17~18.04.1) bionic; urgency=medium
* linux-hwe-edge: 5.0.0-16.17~18.04.1 -proposed tracker (LP: #1829171)
* Disco update: 5.0.8 upstream stable release (LP: #1828415)
-
This bug was fixed in the package linux - 5.0.0-16.17
---
linux (5.0.0-16.17) disco; urgency=medium
* linux: 5.0.0-16.17 -proposed tracker (LP: #1829173)
* shiftfs: lock security sensitive superblock flags (LP: #1827122)
- SAUCE: shiftfs: lock down certain superblock flags
This bug was fixed in the package linux - 5.0.0-16.17
---
linux (5.0.0-16.17) disco; urgency=medium
* linux: 5.0.0-16.17 -proposed tracker (LP: #1829173)
* shiftfs: lock security sensitive superblock flags (LP: #1827122)
- SAUCE: shiftfs: lock down certain superblock flags
This bug was fixed in the package linux-raspi2 - 4.4.0-1110.118
---
linux-raspi2 (4.4.0-1110.118) xenial; urgency=medium
* linux-raspi2: 4.4.0-1110.118 -proposed tracker (LP: #1829198)
* Xenial update: 4.4.179 upstream stable release (LP: #1828420)
- [Config]: add
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/snap-release-to-stable
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or
** 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 --
Public bug reported:
Steps to reproduce:
Configure ssmtp to send through gmail following these instructions:
mailhub=smtp.gmail.com:587
AuthUser=myemailaddr...@gmail.com
AuthPass=MyPassword
UseTLS=YES
UseSTARTTLS=YES
rewriteDomain=gmail.com
hostname=localhost
FromLineOverride=YES
>From the
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/snap-release-to-stable
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or
Please attach output from networkd on boot prior to / without the extra
dhclient unit if you can.
$ networkctl | pastebinit
$ journalctl -b -u systemd-networkd | pastebinit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/snap-release-to-stable
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => 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/promote-to-updates
Status: Fix Committed => 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
** 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 --
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc2/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830116
Title:
linux-generic: missing module
** 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 1829215
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => 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/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-xenial
** Tags removed: 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-updates
Status: Fix Committed => 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
** Tags added: originate-from-1829985
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831587
Title:
brightness control not work with OLED panel
To manage notifications about this bug go to:
Verified livecd-rootfs/2.578.5 on Disco:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/l/livecd-rootfs/20190604_011227_29089@/log.gz
:
...
16K livecd.ubuntu-cpc.wsl.rootfs.manifest
363M
--- Comment From sthou...@in.ibm.com 2019-06-04 06:30 EDT---
Thiru , please verify now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766201
Title:
CTAUTO:DevOps:860.50:devops4fp1:Error
** Tags added: regression-release
** Tags added: cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831144
Title:
GNOME control center UI does not update dconf setting for magnifier
mouse
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-bionic
** Tags removed: block-proposed
** Description changed:
This bug will
Public bug reported:
Reproduce rate: 100%
Steps:
1. git clone --depth=1 https://github.com/linux-test-project/ltp.git
2. cd ltp; make autotools; ./configure; make; sudo make install
3. Run the block_dev test:
cd /opt/ltp/testcases/bin
sudo ./block_dev
All 7 test cases will pass,
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/snap-release-to-stable
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
** 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
backports: bug 1829208
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => 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
The cause looks like to be the block_dev from kenrel_misc
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831595
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830011
Title:
cve-2017-17053
>Do you mean that after applying those updates you don't get to the login
>screen anymore?
correct
>Can you reproduce after a new install and upgrading again?
The boot failure occurs on step 5. This is reproducible.
>Can you boot to a command line using the recovery option
I tried to boot
** 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-signing-to-proposed
Assignee: (unassigned) => Andy Whitcroft (apw)
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Thanks for the report. We've landed a couple of hours ago. Details are
also provided in RHBZ:
https://bugzilla.redhat.com/show_bug.cgi?id=1708991
** Changed in: snapd (Ubuntu)
Status: New => Fix Committed
** Bug watch added: Red Hat Bugzilla #1708991
** Attachment added: "debdiff with fix"
https://bugs.launchpad.net/ubuntu/+source/v4l2loopback/+bug/1830060/+attachment/5268781/+files/v4l2loopback_0.12.1-1_0.12.1-1ubuntu1.diff.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
backports: bug 1829213
Ok, so it's a new feature in samba 4.10. That's unlikely to get
backported to bionic, which has 4.7.x.
** Changed in: samba (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: samba (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-xenial
** Tags removed: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
This bug also affects MaaS when commissioning is done with Bionic 18.04
and an external proxy is set.
Commissioning fails at the step inside the script when trying to install packages for the test itself.
Error message:
Temporary failure resolving
--
You received this bug notification
No, it is a bug.
The Attribute-Editor is an essential part of an active directoy.
Take a look here:
https://wiki.samba.org/index.php/Maintaining_Unix_Attributes_in_AD_using_ADUC
This screenshot is pretty old since the "Unix-Attributes" next to the
"Attribute Editor" has been deprecated with
Source package with fix: https://kernel.ubuntu.com/~cking/lp-1830060
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830060
Title:
v4l2loopback 0.12.1-1 ADT test failure with linux 5.2.0-0.1
To
Ok, so it's a new feature in samba 4.10. That's unlikely to get
backported to bionic, which has 4.7.x.
** Changed in: samba (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: samba (Ubuntu)
Status: Incomplete => Triaged
--
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 --
That's great news, thanks Maciek.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831605
Title:
snapd-2.39-1 Makes Fedora 30 Unresponsive
To manage notifications about this bug go to:
I browsed the WHATSNEW.txt file looking for something to indicate how
and when this was addressed, but didn't find it. Would you be able to
take a look, since you are more familiar with this feature?
Here are some links:
https://github.com/samba-team/samba/blob/v4-7-test/WHATSNEW.txt
This bug was fixed in the package linux - 4.15.0-51.55
---
linux (4.15.0-51.55) bionic; urgency=medium
* linux: 4.15.0-51.55 -proposed tracker (LP: #1829219)
* disable a.out support (LP: #1818552)
- [Config] Disable a.out support
* [UBUNTU] qdio: clear intparm during
This bug was fixed in the package linux - 4.15.0-51.55
---
linux (4.15.0-51.55) bionic; urgency=medium
* linux: 4.15.0-51.55 -proposed tracker (LP: #1829219)
* disable a.out support (LP: #1818552)
- [Config] Disable a.out support
* [UBUNTU] qdio: clear intparm during
This bug was fixed in the package linux - 4.15.0-51.55
---
linux (4.15.0-51.55) bionic; urgency=medium
* linux: 4.15.0-51.55 -proposed tracker (LP: #1829219)
* disable a.out support (LP: #1818552)
- [Config] Disable a.out support
* [UBUNTU] qdio: clear intparm during
This bug was fixed in the package linux - 4.15.0-51.55
---
linux (4.15.0-51.55) bionic; urgency=medium
* linux: 4.15.0-51.55 -proposed tracker (LP: #1829219)
* disable a.out support (LP: #1818552)
- [Config] Disable a.out support
* [UBUNTU] qdio: clear intparm during
This bug was fixed in the package linux - 4.18.0-21.22
---
linux (4.18.0-21.22) cosmic; urgency=medium
* linux: 4.18.0-21.22 -proposed tracker (LP: #1829186)
* disable a.out support (LP: #1818552)
- [Config] Turn off a.out support
* ftrace in ubuntu_kernel_selftests hang
This bug was fixed in the package linux - 4.15.0-51.55
---
linux (4.15.0-51.55) bionic; urgency=medium
* linux: 4.15.0-51.55 -proposed tracker (LP: #1829219)
* disable a.out support (LP: #1818552)
- [Config] Disable a.out support
* [UBUNTU] qdio: clear intparm during
This bug was fixed in the package linux - 5.0.0-16.17
---
linux (5.0.0-16.17) disco; urgency=medium
* linux: 5.0.0-16.17 -proposed tracker (LP: #1829173)
* shiftfs: lock security sensitive superblock flags (LP: #1827122)
- SAUCE: shiftfs: lock down certain superblock flags
This bug was fixed in the package linux - 5.0.0-16.17
---
linux (5.0.0-16.17) disco; urgency=medium
* linux: 5.0.0-16.17 -proposed tracker (LP: #1829173)
* shiftfs: lock security sensitive superblock flags (LP: #1827122)
- SAUCE: shiftfs: lock down certain superblock flags
This bug was fixed in the package linux - 4.15.0-51.55
---
linux (4.15.0-51.55) bionic; urgency=medium
* linux: 4.15.0-51.55 -proposed tracker (LP: #1829219)
* disable a.out support (LP: #1818552)
- [Config] Disable a.out support
* [UBUNTU] qdio: clear intparm during
This bug was fixed in the package linux - 4.15.0-51.55
---
linux (4.15.0-51.55) bionic; urgency=medium
* linux: 4.15.0-51.55 -proposed tracker (LP: #1829219)
* disable a.out support (LP: #1818552)
- [Config] Disable a.out support
* [UBUNTU] qdio: clear intparm during
This bug was fixed in the package linux - 4.15.0-51.55
---
linux (4.15.0-51.55) bionic; urgency=medium
* linux: 4.15.0-51.55 -proposed tracker (LP: #1829219)
* disable a.out support (LP: #1818552)
- [Config] Disable a.out support
* [UBUNTU] qdio: clear intparm during
This bug was fixed in the package linux - 5.0.0-16.17
---
linux (5.0.0-16.17) disco; urgency=medium
* linux: 5.0.0-16.17 -proposed tracker (LP: #1829173)
* shiftfs: lock security sensitive superblock flags (LP: #1827122)
- SAUCE: shiftfs: lock down certain superblock flags
This bug was fixed in the package linux - 4.15.0-51.55
---
linux (4.15.0-51.55) bionic; urgency=medium
* linux: 4.15.0-51.55 -proposed tracker (LP: #1829219)
* disable a.out support (LP: #1818552)
- [Config] Disable a.out support
* [UBUNTU] qdio: clear intparm during
This bug was fixed in the package linux-signed-hwe-edge -
5.0.0-16.17~18.04.1
---
linux-signed-hwe-edge (5.0.0-16.17~18.04.1) bionic; urgency=medium
* Master version: 5.0.0-16.17~18.04.1
* Built-Using incorrect (LP: #1824016)
- Rename "VERSION" template string to more
This bug was fixed in the package linux - 4.18.0-21.22
---
linux (4.18.0-21.22) cosmic; urgency=medium
* linux: 4.18.0-21.22 -proposed tracker (LP: #1829186)
* disable a.out support (LP: #1818552)
- [Config] Turn off a.out support
* ftrace in ubuntu_kernel_selftests hang
1 - 100 of 756 matches
Mail list logo
