The verification of the Stable Release Update for libreoffice 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
Ok, I find out what happens.
While standard SATA setup, chain of functions is called: ... ->
ata_eh_recover -> ata_eh_reset. If SATA is not initialized, then hard
reset is performed (function ata_do_reset() ).
In both drivers I have, function ata_do_reset() returns 0, even if after
this reset
This bug was fixed in the package libreoffice-l10n -
1:6.2.3-0ubuntu0.19.04.1
---
libreoffice-l10n (1:6.2.3-0ubuntu0.19.04.1) disco; urgency=medium
[ Olivier Tilloy ]
* debian/patches/java.vendor-Ubuntu.patch: update to also recognize
"Private Build" as java.vendor (for
Public bug reported:
[impact]
systemd autopkgtest fails
[test case]
run systemd autopkgtest, check for output like:
LUKS device with "tmp" option ... rmmod: ERROR: Module scsi_debug is in use
FAIL
==
FAIL: test_luks_tmp
Patch upstream accepted, bundling with the coming libvirt upload which
was focused on these vhost fixes anyway.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829223
Title:
vhost-scsi triggers
This bug was fixed in the package libreoffice - 1:6.2.3-0ubuntu0.19.04.1
---
libreoffice (1:6.2.3-0ubuntu0.19.04.1) disco; urgency=medium
[ Olivier Tilloy ]
* debian/patches/java.vendor-Ubuntu.patch: update to also recognize
"Private Build" as java.vendor (for custom PPA
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
Maybe this conversation should be moved to Linux linux-ide mailing list.
There is some technical decisions to make and may it's better to consult
it with other developers.
--
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 libreoffice-l10n -
1:6.2.3-0ubuntu0.19.04.1
---
libreoffice-l10n (1:6.2.3-0ubuntu0.19.04.1) disco; urgency=medium
[ Olivier Tilloy ]
* debian/patches/java.vendor-Ubuntu.patch: update to also recognize
"Private Build" as java.vendor (for
** Changed in: kernel-sru-workflow/prepare-package
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:
The verification of the Stable Release Update for libreoffice 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
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Stefan Bader (smb) => Canonical Kernel Team
(canonical-kernel-team)
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Stefan Bader (smb) => Canonical Kernel Team
(canonical-kernel-team)
** 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
derivatives: bug 1829215
Public bug reported:
When the screen locks or blanks I can type the password on the keyboard,
hit enter and it returns me to the desktop without issue. However, when
the screen is locked or blanked, the fingerprint scanner is deactivated.
I have to FIRST press a key on the keyboard such as enter.
** 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 --
@sw0x2a can you try the qemu from this ppa:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1829245
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829245
Title:
Networking issues after upgrade to
>From whoopsie I got nothing, from ubuntu-bug I got the image attached,
hope it helps. Today I'll try the workaround in the 3rd step.
Cheers
** Attachment added: "ubuntu-bug.png"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1829160/+attachment/5264195/+files/ubuntu-bug.png
--
Great, thanks.
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1829256
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
backports: bug 1829171
The verification of the Stable Release Update for bash 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 encounter a
This bug was fixed in the package bash - 5.0-3ubuntu1.1
---
bash (5.0-3ubuntu1.1) disco; urgency=medium
* Resurrect "Set the default path to comply with Debian policy" in
deb-bash-config.diff which went missing since 4.2+dfsg-1 or so.
LP: #1792004 LP: #1614080 Closes:
Adaptec/Microsemi support recommends to replace the RAID card for ubuntu
18.04..
Answer from support:
Unfortunately, this card has no drivers for Ubunto 18.
See it's product page here
https://storage.microsemi.com/en-us/support/raid/sas_raid/sas-6405e/
Replacement card is
the output is intel_backlight
It appers, that ist fixed. I booted it up on the machine to run command and the
slider is there. Did not change any settings. just did apt autoremove before
last shutdown. I guess it changed the default jernel executable to the newest
--
You received this bug
** Summary changed:
- linux-hwe: 4.15.0-50.54~16.04.2 -proposed tracker
+ linux-hwe: 4.15.0-51.55~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of
@otto, sorry it's not clear to me from your comment, is there something
wrong with this upload?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824335
Title:
autopkgtest always fails with "I can't
The verification of the Stable Release Update for bash 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 encounter a
This bug was fixed in the package bash - 5.0-3ubuntu1.1
---
bash (5.0-3ubuntu1.1) disco; urgency=medium
* Resurrect "Set the default path to comply with Debian policy" in
deb-bash-config.diff which went missing since 4.2+dfsg-1 or so.
LP: #1792004 LP: #1614080 Closes:
** 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) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
Hello Simone,
sorry for the delay, was working on something else for the last SRU
cycle.
While preparing a cover letter for patching this into our 4.18 Cosmic
kernel, I am a bit hesitated as the diff in this commit [1] is
relatively big for fixing a (well, several models actually) touchpad
This bug was fixed in the package linux-aws - 4.4.0-1044.47
---
linux-aws (4.4.0-1044.47) trusty; urgency=medium
[ Ubuntu: 4.4.0-148.174 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- perf/x86/intel: Add model
This bug was fixed in the package linux-raspi2 - 5.0.0-1008.8
---
linux-raspi2 (5.0.0-1008.8) disco; urgency=medium
[ Ubuntu: 5.0.0-15.16 ]
* CVE-2019-11683
- udp: fix GRO reception in case of length mismatch
- udp: fix GRO packet of death
* CVE-2018-12126 //
This bug was fixed in the package linux-lts-xenial -
4.4.0-148.174~14.04.1
---
linux-lts-xenial (4.4.0-148.174~14.04.1) trusty; urgency=medium
[ Ubuntu: 4.4.0-148.174 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
-
This bug was fixed in the package linux-gcp - 5.0.0-1006.6
---
linux-gcp (5.0.0-1006.6) disco; urgency=medium
[ Ubuntu: 5.0.0-15.16 ]
* CVE-2019-11683
- udp: fix GRO reception in case of length mismatch
- udp: fix GRO packet of death
* CVE-2018-12126 // CVE-2018-12127
This bug was fixed in the package linux-aws - 5.0.0-1006.6
---
linux-aws (5.0.0-1006.6) disco; urgency=medium
[ Ubuntu: 5.0.0-15.16 ]
* CVE-2019-11683
- udp: fix GRO reception in case of length mismatch
- udp: fix GRO packet of death
* CVE-2018-12126 // CVE-2018-12127
This bug was fixed in the package linux-azure - 5.0.0-1006.6
---
linux-azure (5.0.0-1006.6) disco; urgency=medium
[ Ubuntu: 5.0.0-15.16 ]
* CVE-2019-11683
- udp: fix GRO reception in case of length mismatch
- udp: fix GRO packet of death
* CVE-2018-12126 //
This bug was fixed in the package linux-snapdragon - 5.0.0-1012.12
---
linux-snapdragon (5.0.0-1012.12) disco; urgency=medium
[ Ubuntu: 5.0.0-15.16 ]
* CVE-2019-11683
- udp: fix GRO reception in case of length mismatch
- udp: fix GRO packet of death
* CVE-2018-12126 //
This bug was fixed in the package linux - 5.0.0-15.16
---
linux (5.0.0-15.16) disco; urgency=medium
* CVE-2019-11683
- udp: fix GRO reception in case of length mismatch
- udp: fix GRO packet of death
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
-
This bug was fixed in the package linux-kvm - 5.0.0-1006.6
---
linux-kvm (5.0.0-1006.6) disco; urgency=medium
[ Ubuntu: 5.0.0-15.16 ]
* CVE-2019-11683
- udp: fix GRO reception in case of length mismatch
- udp: fix GRO packet of death
* CVE-2018-12126 // CVE-2018-12127
This bug was fixed in the package linux-gcp - 4.18.0-1011.12
---
linux-gcp (4.18.0-1011.12) cosmic; urgency=medium
[ Ubuntu: 4.18.0-20.21 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu: Sanitize FAM6_ATOM
This bug was fixed in the package linux-kvm - 4.18.0-1012.12
---
linux-kvm (4.18.0-1012.12) cosmic; urgency=medium
[ Ubuntu: 4.18.0-20.21 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu: Sanitize FAM6_ATOM
This bug was fixed in the package linux-raspi2 - 4.18.0-1014.16
---
linux-raspi2 (4.18.0-1014.16) cosmic; urgency=medium
[ Ubuntu: 4.18.0-20.21 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu: Sanitize
This bug was fixed in the package linux - 4.18.0-20.21
---
linux (4.18.0-20.21) cosmic; urgency=medium
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu: Sanitize FAM6_ATOM naming
- kvm: x86: Report STIBP on
This bug was fixed in the package linux-aws - 4.18.0-1016.18
---
linux-aws (4.18.0-1016.18) cosmic; urgency=medium
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
[ Ubuntu: 4.18.0-20.21 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
-
This bug was fixed in the package linux-azure - 4.18.0-1018.18
---
linux-azure (4.18.0-1018.18) cosmic; urgency=medium
[ Ubuntu: 4.18.0-20.21 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu: Sanitize
This bug was fixed in the package linux-azure - 4.15.0-1045.49~14.04.1
---
linux-azure (4.15.0-1045.49~14.04.1) trusty; urgency=medium
[ Ubuntu: 4.15.0-1045.49 ]
* [linux-azure] Storage performance drop on RAID (LP: #1828248)
- Revert "blk-mq: remove the request_list usage"
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Jesse Sung (wenchien) => Stefan Bader (smb)
**
This bug was fixed in the package linux-azure - 4.15.0-1045.49~14.04.1
---
linux-azure (4.15.0-1045.49~14.04.1) trusty; urgency=medium
[ Ubuntu: 4.15.0-1045.49 ]
* [linux-azure] Storage performance drop on RAID (LP: #1828248)
- Revert "blk-mq: remove the request_list usage"
** Changed in: kernel-sru-workflow/prepare-package-meta
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
Whether you are shopping online or in store, using coupon sites can save
you money. Here are the best coupon websites to save the most forever 21
coupons https://www.couponmall.net/store/forever-21/
--
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
backports: bug 1829176
** Changed in: duplicity
Status: Fix Committed => 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/1770929
Title:
Duplicity fails with UnicodeDecodeError in uexc function
To
** Description changed:
Hi!
+ Ubnuntu 19.04
+ sshfs -V
+ SSHFS version 2.10.0
+ FUSE library version: 2.9.9
+ fusermount version: 2.9.9
+ using FUSE kernel interface version 7.19
Try to mount through sshfs and I got
fusermount: mounting over filesystem type 0xfe534d42 is forbidden
i
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-cosmic
** 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.
Version 1:2.5+dfsg-5ubuntu10.38 doesn't fix it entirely but works better
than ...10.37. It seem to lose network connectivity only on reboots of a
VM. Poweroff/resume (killing and restarting the kvm process) fixes it
again.
Still no error messages or something. Willing to provide more
information
** 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.
** Summary changed:
- linux-gke-4.15: -proposed tracker
+ linux-gke-4.15: 4.15.0-1032.34 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
** 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-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.
Public bug reported:
Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network
Connection (rev 0)
PCIID: 8086:10fb subsystem 103c:17d0
I have tried to install Ubuntu 16.04 with default kernel v4.4 and backported
kernel from 18.04 v4.15. PXE boot process works well till the
** Summary changed:
- linux-kvm: -proposed tracker
+ linux-kvm: 4.4.0-1047.53 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
@Naegling23 So I'm running Fedora 29 myself. And just like you, it at
first worked, then just stayed there trying to login. Any subsequent
attempt to start the program crashed like before. Until I did the
following:
sudo chmod 444 libnode.so
Basically, I made the file read-only. At that point, I
See original bug report
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1757107 and
in particular commit
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1757107/comments/11
This problem was introduced by sloppy maintainer work, pushing in 10.2
to Debian repos without prior
Seems to fix Slack for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827302
Title:
18.10 → 19.04 Alt-Tab cycling no longer includes Slack window
To manage notifications about this bug go to:
** Summary changed:
- linux-aws: -proposed tracker
+ linux-aws: 4.18.0-1017.19 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
Ubuntu-Studio 19.10 qa-test; Same issue, so I'm changing to new. QA-test
comments paste :-
hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
change display so display2 is below display1, and 2 is primary; moved main
panel to bottom of display2
firefox; start streaming of local (au) news and
** Summary changed:
- linux-hwe: -proposed tracker
+ linux-hwe: 4.15.0-50.54~16.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
Olivier Fourdan referenced this bugreport in commit
22fe30cdd99d111f043b3282a02f39df468c7ac2
netwm: Fix window type for broken clients
https://git.xfce.org/xfce/xfwm4/commit?id=22fe30cdd99d111f043b3282a02f39df468c7ac2
--
You received this bug notification because you are a member 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
backports: bug 1829185
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1829214
For #44 Aaron's suggested patch, it seems patch have been included after
4.15.0-46. The testing 18.04.2 iso with 4.15.0-48 kernel seems the
system would be hang on language selection after select install server
of grub screen. So it seems this hibmc_drm would caused another this
hang issues too.
(In reply to Philip Rosvall from comment #593)
> Since 5.0.10, and this commit ...:
>
> (https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.0.10)
> "commit 205c53cbe553c9e5a9fe93f63e398da7e59124b6
> Author: Thomas Gleixner
> Date: Sun Apr 14 19:51:06 2019 +0200
>
> x86/speculation:
(In reply to Moritz Naumann from comment #592)
> The latest firmware for X370 Taichi, v5.50 (2019/4/24), removes the "Power
> Supply Idle Control" option off the configuration UI; downgrading is not
> supported (but effectively possible at least from Windows). It is still
> possible to set "Power
The latest firmware for X370 Taichi, v5.50 (2019/4/24), removes the "Power
Supply Idle Control" option off the configuration UI; downgrading is not
supported (but effectively possible at least from Windows). It is still
possible to set "Power Supply Idle Control" (C6 package) via MSR using e.g.
Hello Leon, or anyone else affected,
Accepted lexicon into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lexicon/2.2.1-2ubuntu0.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Thanks for the clarification.
Next please run:
ls /sys/class/backlight/
and tell us what output you see.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829256
Title:
[Dell Vostro 5568] Cannot
Also, you seem to be running an old kernel (v4.18) from Ubuntu 18.10.
Please try booting the newer kernel (v5.0) from Ubuntu 19.04:
1. Reboot.
2. As soon as the purple screen appears tap Escape.
3. Look through the menus to find a newer kernel to boot.
--
You received this bug notification
I'm wondering as 1:2.5+dfsg-5ubuntu10.37 never existed in the wild.
The archive should have went from .36 to .38 I'd think.
There is a single upload [1] covering both.
.37 only existed in proposed I'd think.
Never the less it contained a few changes to networking.
One to slirp (not your case),
Ah sorry for imprecision, I was indeed only referring to the apt bits.
On Thu, 16 May 2019, 18:25 Christian Ehrhardt , <1829...@bugs.launchpad.net>
wrote:
> FYI: /usr/share/locales have 7MB in ubuntu:latest as of 15th of May
>
> --
> You received this bug notification because you are a member
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1829179
This issue was fixed in the openstack/oslo.cache 1.30.4 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812672
Title:
impossible to create nova instances after upgrading to rocky
To manage
OK, for ubuntu-19.04-live-server-amd64.iso booting in secure boot mode, I found
more commands are not working, at least including:
lspci
probe
md5sum
play
sha1sum
tr
usb
videoinfo
While the following are working:
ls
cat
echo
help
reboot
I am wondering is this due to some purpose about
Public bug reported:
I command ceph-deploy mgr create node1
cluster: id: cb144140-f41a-464a-a834-d7817785e149 health: HEALTH_WARN 3
modules have failed dependencies
services: mon: 1 daemons, quorum monitor mgr: monitor(active) osd: 0
osds: 0 up, 0 in
data: pools: 0 pools, 0 pgs objects: 0
I repeated the above steps for ubuntu-18.04.2-live-server-amd64.iso, and
got the same result. The regexp command in the grub shell does not work
in secure boot mode. However, it does work in non-secure boot mode.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
FYI: /usr/share/locales have 7MB in ubuntu:latest as of 15th of May
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829333
Title:
please filter /usr/share/locales when creating minimized images
To
Would you mind testing an older oem kernel from bionic? Install 'linux-
image-4.15.0-1034-oem' and remember to select it from the boot menu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826125
Public bug reported:
In a discussion around image sizes it came up that our images still have
locales in
/usr/share/locales
Since my words seem to be misleading I'm quoting Steve on this:
"ok, now I see what you mean about locales. yes, since we do not support
non-English locales in the
** Changed in: kernel-sru-workflow/prepare-package-lrm
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags
** Summary changed:
- linux-azure: -proposed tracker
+ linux-azure: 4.18.0-1019.19 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
** Attachment added: "Grub command regexp works in the non-secure boot mode"
https://bugs.launchpad.net/ubuntu/+source/grub-efi-amd64-signed/+bug/1829331/+attachment/5264191/+files/grub-working.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Dear maintainer,
The grub command "regexp" on Ubuntu 19.04 does not work in the secure boot
mode, yet it works in the non-secure boot mode.
Attached please find the screenshots about that.
How to reproduce it?
1. Download Ubuntu 19.04 sever ISO file:
601 - 690 of 690 matches
Mail list logo
