Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bzip2 (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/1834494
Title:
Since it's fixed in cosmic and later, marking the main task as fix
released.
** Changed in: sssd (Ubuntu Bionic)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: livecd-rootfs (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Workaround to be able to install in the meantime?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820617
Title:
subiquity install fails: kernel modules not found
To manage notifications about this
** Changed in: sssd (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: sssd (Ubuntu Bionic)
Status: New => 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/1834507
** Changed in: systemd (Ubuntu Disco)
Status: New => Incomplete
** Changed in: systemd (Ubuntu Bionic)
Status: New => Incomplete
** Changed in: systemd (Ubuntu Cosmic)
Status: New => Incomplete
** Changed in: systemd (Ubuntu Eoan)
Importance: Medium => Undecided
--
You
Since it's fixed in cosmic and later, marking the main task as fix
released.
** Changed in: sssd (Ubuntu Bionic)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to sssd in Ubuntu.
cosmic->disco testing, same as last comment (with no lxd installed), has
the same result; do-release-upgrade tries to install snaps after
upgrade, while do-release-upgrade -p does not.
** Tags removed: verification-needed verification-needed-disco
** Tags added: verification-done
Quick test case, to be used in the sru template later on:
sudo apt update
sudo apt install sssd winbind
create this /etc/samba/smb.conf:
[global]
log file = /var/log/samba/log.%m
map to guest = Bad User
max log size = 1000
panic action =
Quick test case, to be used in the sru template later on:
sudo apt update
sudo apt install sssd winbind
create this /etc/samba/smb.conf:
[global]
log file = /var/log/samba/log.%m
map to guest = Bad User
max log size = 1000
panic action =
Hi, Oliver. I have no clue how to comply with your request, below,
unfortunately.
Also, please run the following command in a terminal to attach
additional information to the bug report:
apport-collect 1834375
Bob James
On Thursday, June 27, 2019, 4:30:47 AM EDT, Olivier Tilloy
I to want to thank you for your hard work. It is appreciated.
For an update. I was able to get a workaround, which is not ideal and
one that puts my system at risk. The server setup was two drives
mirrored, RAID1, via software RAID. This was for the Operating System
only. I have the
All autopkgtests for the newly accepted systemd (229-4ubuntu21.22) for xenial
have finished running.
There have been regressions in tests triggered by the package. Please visit the
sru report page and investigate the failures.
https://people.canonical.com/~ubuntu-archive/pending-sru.html#xenial
** 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 --
Ok, reproduced:
[2019/06/27 17:35:46.930548, 0]
../source3/winbindd/idmap.c:328(smb_register_idmap)
Failed to register idmap module.
The module was compiled against SMB_IDMAP_INTERFACE_VERSION 5,
current SMB_IDMAP_INTERFACE_VERSION is 6.
Please recompile against the current version of
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/security-signoff
Status: New => Fix Released
** Changed in:
All autopkgtests for the newly accepted systemd (229-4ubuntu21.22) for xenial
have finished running.
There have been regressions in tests triggered by the package. Please visit the
sru report page and investigate the failures.
https://people.canonical.com/~ubuntu-archive/pending-sru.html#xenial
All autopkgtests for the newly accepted systemd (229-4ubuntu21.22) for xenial
have finished running.
There have been regressions in tests triggered by the package. Please visit the
sru report page and investigate the failures.
https://people.canonical.com/~ubuntu-archive/pending-sru.html#xenial
All autopkgtests for the newly accepted systemd (229-4ubuntu21.22) for xenial
have finished running.
There have been regressions in tests triggered by the package. Please visit the
sru report page and investigate the failures.
https://people.canonical.com/~ubuntu-archive/pending-sru.html#xenial
In the updates tab, I keep all three boxes checked under "Install
updates from:", because I like to manually run `sudo apt-get update &&
sudo apt-get upgrade` whenever I have a good stable release of software
and feel like stomaching a raft of system changes.
In past versions of ubuntu going back
Ok, reproduced:
[2019/06/27 17:35:46.930548, 0]
../source3/winbindd/idmap.c:328(smb_register_idmap)
Failed to register idmap module.
The module was compiled against SMB_IDMAP_INTERFACE_VERSION 5,
current SMB_IDMAP_INTERFACE_VERSION is 6.
Please recompile against the current version of
Thanks for filing this bug in Ubuntu.
While I try to reproduce this, it would speed things up if you had a
sample config that shows the problem. We could then also use this as a
test case to verify the fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for your work. Please leave a comment when the fix lands in
Linus' tree.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777586
Title:
Ubuntu Server 18.04 LTS aacraid error
To manage
Thanks for filing this bug in Ubuntu.
While I try to reproduce this, it would speed things up if you had a
sample config that shows the problem. We could then also use this as a
test case to verify the fix.
--
You received this bug notification because you are a member of Ubuntu
Server, which
Does any of older 5.0.0-* kernel ever work?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829497
Title:
Bluetooth not work
To manage notifications about this bug go to:
New release of DOSBox happened today (0.74-3).
It contains some security fixes CVE-2019-7165 CVE-2019-12594 and some
important OpenGL-related fixes.
Official note about release is on https://www.dosbox.com/
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-12594
** CVE added:
Seems like a known bug already fix upstream in sssd-1_16_2.
https://pagure.io/SSSD/sssd/issue/3741
https://github.com/SSSD/sssd/pull/572
** Tags added: sts
** Also affects: sssd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: sssd (Ubuntu)
Status: New =>
A bit of necromancy on an old bug report, but in case someone else is
seeing this:
Yes, this is an SDL issue, but DOSBox could instruct SDL to work
correctly.
To *work around* it, you can use environment variable:
SDL_VIDEO_FULLSCREEN_DISPLAY= AND use dosbox settings:
sdl.fullresolution= (do not
This bug was fixed in the package mutter - 3.32.2+git20190626-1ubuntu1
---
mutter (3.32.2+git20190626-1ubuntu1) eoan; urgency=medium
* Merge with debian (LP: #1834493). Remaining changes:
+ debian/control:
- Update VCS flags to point to launchpad
- Update maintainer
** 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
This bug was fixed in the package mutter - 3.32.2+git20190626-1ubuntu1
---
mutter (3.32.2+git20190626-1ubuntu1) eoan; urgency=medium
* Merge with debian (LP: #1834493). Remaining changes:
+ debian/control:
- Update VCS flags to point to launchpad
- Update maintainer
This bug was fixed in the package mutter - 3.32.2+git20190626-1ubuntu1
---
mutter (3.32.2+git20190626-1ubuntu1) eoan; urgency=medium
* Merge with debian (LP: #1834493). Remaining changes:
+ debian/control:
- Update VCS flags to point to launchpad
- Update maintainer
UPDATE: I've installed Kubuntu 19.10 on a separate drive in the same
system and I've found that this bug still persists irregardless of
options. It doesn't matter if I choose encryption or not, nor lvm or
not. Out of curiosity, I booted a thumb drive with the latest live build
on UEFI and escaping
** 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 --
Hello.
It is still unclear whether this is still an issue in apt-xapian-index
or the underlying python apt bindings. I am marking this as Incomplete
for apt-xapian-index as this is still marked as affecting it and has
been since 2015, and the Trusty that was affected is End of Life.
Please
It is unclear if this issue still remains. Please verify that this
issue still exists in supported releases of apt-xapian-index, and if so
please mark this as "Confirmed". I am marking this as Incomplete for
now.
** Changed in: apt-xapian-index (Ubuntu)
Status: Triaged => Incomplete
**
** Changed in: software-properties (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/1834226
Title:
update-notifier doesn't respect "automatically check for
Public bug reported:
package version: 2.3.10-1ubuntu2.1
Crash logs:
Jun 27 10:51:28 ubuntu-xenial ovpn-client[1182]: Preserving previous TUN/TAP
instance: tun0
Jun 27 10:51:28 ubuntu-xenial ovpn-client[1182]: NOTE: Pulled options changed
on restart, will need to close and reopen TUN/TAP
Dash to Dock works for me but pretty much nothing else does, including
the apparently "officially supported" classic applications menu.
Intentional breakage eh, nice of the GNOME team to confuse all the users
and provide a super helpful "Error." message long as things are
easier for the devs,
** Summary changed:
- update-notifier ignores update-manager's settings
+ update-notifier ignores software-properties's settings
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817559
Title:
Public bug reported:
MARCOCOCO
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: gnome-shell (Ubuntu Disco)
Importance: Undecided
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: In Progress
** Also affects: gnome-shell
Trusty is End of LIfe and not going to get an update for this.
It is unclear if this crash is able to be reproduced in later versions
of the software/package. If it is, please mark this bug as "Confirmed"
and tag it with the release tested on. Until that time, however, I am
marking this as
** Changed in: curl (Ubuntu)
Status: Confirmed => Fix Released
** Tags removed: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832882
Title:
libcurl-gnutls segfaults spotify
bionic->cosmic testing, after doing:
$ sudo apt purge lxd lxd-client
testing using 'do-release-upgrade' prompts that the snapstore isn't
reachable, and then after upgrade still tries to install snaps.
testing using 'do-release-upgrade -p' prompts that snapstore isn't
reachable, and then does
** 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
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
** 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 --
This very much needs to be fixed and has not been. It's impossible to
enable OMEMO or other plugins, making Gajim pretty much useless.
Screenshots attached; there needs to be a "Plugins" menu _somewhere_ and
there is not. I got bounced from the Gajim repo when I tried to report
this, Ubuntu needs
** 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
I tested this on an virtual machine running Eoan and did not notice
vgcfgbackup taking as much time as it doesn in an schroot.
bdmurray@clean-eoan-amd64:~$ sudo time vgcfgbackup
0.00user 0.00system 0:00.02elapsed 37%CPU (0avgtext+0avgdata 10848maxresident)k
3584inputs+0outputs
This bug was fixed in the package virt-manager - 1:2.2.0-0ubuntu1
---
virt-manager (1:2.2.0-0ubuntu1) eoan; urgency=medium
* Merge with new upstream release v2.2
Amonth other fixes and improvements this fixes
LP: #1826856 - KVM: Boot Configuration Override
- update
** 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
Good to know! Thank you!
Would it also be possible to mark the "upstream" test
(https://salsa.debian.org/systemd-
team/systemd/blob/master/debian/tests/control#L113) "flaky" or turn it
off altogether? We run it on CentOS and Arch anyway so it should be
safe. On Ubuntu CI it's particularly flaky
** 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
** 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
** 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
Public bug reported:
I got this in my error logs:
Jun 25 22:49:13 mail policyd-spf[7946]: Traceback (most recent call last):
Jun 25 22:49:13 mail policyd-spf[7946]: File "/usr/bin/policyd-spf", line
708, in
Jun 25 22:49:13 mail policyd-spf[7946]: sys.stdout.write('action=550
%s\n\n' %
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: python-libmaas (Ubuntu Cosmic)
Status: New => Confirmed
--
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: 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
** 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
** 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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: python-libmaas (Ubuntu Bionic)
Status: New => Confirmed
--
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-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-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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: python-libmaas (Ubuntu Disco)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package snapd - 2.39.2ubuntu0.2
---
snapd (2.39.2ubuntu0.2) xenial; urgency=medium
* Cherry-pick pull-request 7040 fixing build-time unit-tests that started
failing recently.
snapd (2.39.2ubuntu0.1) xenial; urgency=medium
* Cherry-pick pull-request
Hi guys, we've faced the same issue you are talking about,
i've found the guilty patch:
395e5df79a95 ("scsi: aacraid: Remove reference to Series-9")
and made a fix which helps me.
i've sent the patch to LKML:
https://marc.info/?l=linux-kernel=156165206304641=2
Public bug reported:
1. The release of Ubuntu is Ubuntu 18.04.2 LTS
2. The package version is 1:3.26.4-0
3. I expected to ask if I want to replace the image or not.
4. What happened is that the app crashed.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.4-0~ubuntu18.04.4
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => In Progress
--
You received this bug notification because you are a
** 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
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => In Progress
--
You received this bug notification because you are a
The verification of the Stable Release Update for golang-1.8 has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for snapd-glib has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package linux-meta-raspi2 - 5.0.0.1012.9
---
linux-meta-raspi2 (5.0.0.1012.9) disco; urgency=medium
* Bump ABI 5.0.0-1012
-- Stefan Bader Mon, 24 Jun 2019 19:06:46
+0200
** Changed in: linux-meta-raspi2 (Ubuntu Disco)
Status: Fix Committed =>
This bug was fixed in the package snapd-glib - 1.48-0ubuntu0.19.04.0
---
snapd-glib (1.48-0ubuntu0.19.04.0) disco; urgency=medium
* New upstream release (LP: #1831827)
-- Robert Ancell Tue, 18 Jun 2019
14:03:15 +1200
** Changed in: snapd-glib (Ubuntu Disco)
Status: Fix
** 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-raspi2 - 5.0.0-1012.12
---
linux-raspi2 (5.0.0-1012.12) disco; urgency=medium
* linux-raspi2: 5.0.0-1012.12 -proposed tracker (LP: #1833921)
[ Ubuntu: 5.0.0-20.21 ]
* linux: 5.0.0-20.21 -proposed tracker (LP: #1833934)
*
This bug was fixed in the package golang-1.8 - 1.8.3-2ubuntu1.18.04.1
---
golang-1.8 (1.8.3-2ubuntu1.18.04.1) bionic; urgency=medium
* Fix FTBFS (LP: #1815396):
- On ppc64el by converting some tests that ran with unsupported linker
flags to run with supported ones.
-
** 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-aws - 5.0.0-1010.11
---
linux-aws (5.0.0-1010.11) disco; urgency=medium
* linux-aws: 5.0.0-1010.11 -proposed tracker (LP: #1833922)
[ Ubuntu: 5.0.0-20.21 ]
* linux: 5.0.0-20.21 -proposed tracker (LP: #1833934)
* CVE-2019-11479
-
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => In Progress
--
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 --
** Also affects: netplan.io (Ubuntu Eoan)
Importance: High
Status: New
** Changed in: netplan.io (Ubuntu Eoan)
Status: New => Confirmed
** Tags removed: rls-ee-incoming
** Tags added: eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => In Progress
--
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 --
This bug was fixed in the package linux-gcp - 5.0.0-1010.10
---
linux-gcp (5.0.0-1010.10) disco; urgency=medium
* linux-gcp: 5.0.0-1010.10 -proposed tracker (LP: #1833927)
[ Ubuntu: 5.0.0-20.21 ]
* linux: 5.0.0-20.21 -proposed tracker (LP: #1833934)
* CVE-2019-11479
-
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => In Progress
--
You received this bug notification because you are a
This bug was fixed in the package linux-kvm - 5.0.0-1010.11
---
linux-kvm (5.0.0-1010.11) disco; urgency=medium
* linux-kvm: 5.0.0-1010.11 -proposed tracker (LP: #1833928)
[ Ubuntu: 5.0.0-20.21 ]
* linux: 5.0.0-20.21 -proposed tracker (LP: #1833934)
* CVE-2019-11479
-
This bug was fixed in the package linux-snapdragon - 5.0.0-1016.17
---
linux-snapdragon (5.0.0-1016.17) disco; urgency=medium
* linux-snapdragon: 5.0.0-1016.17 -proposed tracker (LP: #1833929)
[ Ubuntu: 5.0.0-20.21 ]
* linux: 5.0.0-20.21 -proposed tracker (LP: #1833934)
*
** 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 1833930
This bug was fixed in the package linux - 5.0.0-20.21
---
linux (5.0.0-20.21) disco; urgency=medium
* linux: 5.0.0-20.21 -proposed tracker (LP: #1833934)
* CVE-2019-11479
- SAUCE: tcp: add tcp_min_snd_mss sysctl
- SAUCE: tcp: enforce tcp_min_snd_mss in tcp_mtu_probing()
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => In Progress
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => In Progress
--
You received this bug notification because you are a
** 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
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => In Progress
--
You received this bug notification because you are a
Thanks for the response, Oliver.
Today, the results are different. There is no error message, but the Gaia
videos will not start. That is, there is no response to a left click on the
little GUI in the center of the video display image.
Also, I would like to comply with your request but have
There was a problem contacting the mirror of the Ubuntu archive that
your system is configured to use. Please resolve your network issue or
try switching mirrors of the Ubuntu archive. From
VarLogDistupgradeMainLog:
2019-06-26 21:56:14,851 DEBUG examining: 'deb
Public bug reported:
When attempting to load the sss.so module, on a Bionic box running
samba-* on 4.7 and sssd-* 1.16.1, one sees the following in syslog:
winbindd[13099]: load_module_absolute_path: Module
'/usr/lib/x86_64-linux-gnu/samba/idmap/sss.so' loaded
winbindd[13099]: Failed to
This bug was fixed in the package octavia - 4.0.0-0ubuntu1.1
---
octavia (4.0.0-0ubuntu1.1) disco; urgency=medium
[ Corey Bryant ]
* d/gbp.conf: Create stable/stein branch.
[ Sahid Orentino Ferdjaoui ]
* d/p/0001-db-add-missing-primary-key-in-spares_pool-table.patch:
201 - 300 of 862 matches
Mail list logo
