Here's a perfect illustration how NOT to protect against MITM:
http://www.system-rescue-cd.org/Download/
Assumed, the attacker _can_ attack via MITM, then
1. the attacker can let the download link point somewhere else (e.g. to a
compromised download).
2. the attacker can _also_ show a checksum
Same issue here after this update, system won't boot after getting the
following two packages:
gnome-shell-common/disco-updates,disco-updates 3.32.1-1ubuntu1~19.04.1 all
[upgradable from: 3.32.0+git20190410-1ubuntu1]
gnome-shell/disco-updates 3.32.1-1ubuntu1~19.04.1 amd64 [upgradable from:
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-shell (Ubuntu)
Status: New => In Progress
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues
** Changed in: epiphany-extensions (Debian)
Status: New => 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/285119
Title:
[packaging] The README file is uninteresting to the end
This bug was fixed in the package ipvsadm - 1:1.28-3ubuntu0.18.04.1
---
ipvsadm (1:1.28-3ubuntu0.18.04.1) bionic; urgency=medium
* d/ipvsadm.init: remove duplicate syncid on daemon invocation (LP:
#1830033)
-- Christian Ehrhardt Fri, 24 May
2019 09:51:59 +0200
** Changed in:
In respect to the above discussion TJ posted:
Please be aware that https-securing mirrors does in fact not necessarily
increase the trustworthyness of the download. Reason:
An attacker could compromise a mirror's downloads (e.g. via stolen
credentials or via MITM while the mirror downloads via
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
pcmanfm. This problem was most recently seen with package version 1.3.1-1, the
problem page at
https://errors.ubuntu.com/problem/a3e3c3a40d821379ae25c46324a3f9259ffb0bb4
contains more details,
** Summary changed:
- disco 19.04 doesn't shutdown
+ disco 19.04 doesn't shutdown on an Asrock 970 Extreme 4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829077
Title:
disco 19.04 doesn't
I forgot to verify this for 4.15 in addition to 5.0. The package in
-proposed (0.10.0-1ubuntu1.1) installs correctly without any compilation
errors for 4.15 and 5.0.
I've attached the log of the installation while running a 4.15 kernel.
The 5.0 kernel is also installed on this VM so it similarly
Public bug reported:
core18 snap missing from bionic desktop, snaps fail to seed offline
yet gnome-logs etc depend on core18
Note the livecd-rootfs in bionic does not have snap-tool and is not
using it.
Possibly we need to force seed core18 manually somehow
** Affects: livecd-rootfs
This bug was fixed in the package v4l2loopback - 0.10.0-1ubuntu1.1
---
v4l2loopback (0.10.0-1ubuntu1.1) bionic; urgency=medium
* Fix build for kernel 5.0 (LP: #1828615)
- debian/patches/0002-Replace-do_gettimeofday-with-v4l2_get_timestamp.patch
-- Connor Kuehl Fri, 10 May
The verification of the Stable Release Update for v4l2loopback 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 lexicon 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 lexicon - 2.2.1-2ubuntu0.1
---
lexicon (2.2.1-2ubuntu0.1) bionic; urgency=medium
[ Adrien Ferrand ]
* Fix dnsimple provider to create records (LP: #1825049).
-- Robie Basak Mon, 29 Apr 2019 10:22:26
+0100
** Changed in: lexicon (Ubuntu
The verification of the Stable Release Update for hexchat 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 looks like the following error bucket and the version in -proposed
doesn't appear in it.
https://errors.ubuntu.com/problem/24d8d665e8b301554c9bb5720df6d262eeb4ddf7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The pvscan issue is likely something different, just wanted to make sure
folks are aware of it for completeness.
The logs /var/log/ceph/ceph-volume-systemd.log and ceph-volume.log are
empty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: qtbase-opensource-src (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831505
Title:
Qt5 incorrectly interpret keypresses from remote
Hello Sahid, or anyone else affected,
Accepted neutron into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/neutron/2:12.0.6-0ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello James, or anyone else affected,
Accepted neutron into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/neutron/2:12.0.6-0ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1831670
and then change the status of the bug to 'Confirmed'.
If, due to the
Hello James, or anyone else affected,
Accepted neutron into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/neutron/2:13.0.2-0ubuntu3.3 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1827330
Title:
[block layer] please pull below upstream patch to Ubuntu 19.04
** Tags added: block-proposed 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/1823429
Title:
linux-oracle ftbfs in disco
To manage notifications about this bug go to:
Public bug reported:
Whether one press trackpoint button (left, right or middle), release
event occurs immediately after press event, not at the moment when it
actually released
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
** 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 --
We will be investigation this situation ASAP but it is pending
submission for SRU for other azure work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830740
Title:
[linux-azure] Delay during boot
> Are you linux-oracle maintainer?
I only play one on TV.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823429
Title:
linux-oracle ftbfs in disco
To manage notifications about this bug go to:
This bug was fixed in the package gost-crypto - 0.3-1ubuntu2
---
gost-crypto (0.3-1ubuntu2) eoan; urgency=medium
* Add Linux 5.1+ fix for deprecated CRYPTO_TFM_REQ_WEAK_KEY (LP: #1830045)
- This adds a compat fix for the deprecated CRYPTO_TFM_REQ_WEAK_KEY, from
5.1 onwards
this bug is platform dependent
or maybe also from hardware?
I am helped by adding options in grub / kernel
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=nomsi,noaer"
--
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: 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:
It's up to the kernel team to manage kernel bugs.
Are you linux-oracle maintainer?
On Tue, 4 Jun 2019, 21:35 Dan Streetman,
wrote:
> This is difficult because security/selinux/ doesn't use the *actual*
> kernel headers for the kernel being built to get the AF_MAX/PF_MAX defines;
> those are
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829202
Title:
linux-gke-4.15: 4.15.0-1033.35 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829202
Title:
linux-gke-4.15: 4.15.0-1033.35 -proposed tracker
** 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 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: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829202
Title:
linux-gke-4.15: 4.15.0-1033.35 -proposed tracker
** 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 --
** 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/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.
** 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
derivatives: bug 1829215
** 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 --
** Description changed:
[Impact]
We enabled CONFIG_DMA_CMA to fix bug 1803206, but that led to a regression
on other arm64 systems that began spewing these messages on boot - sometimes
> 10K of them:
[ 19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
[
** 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 --
** 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 --
** 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 --
** 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
** 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 1829182
** 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
backports: bug 1829192
** 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
backports: bug 1829196
** 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
** 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
Hello James, or anyone else affected,
Accepted neutron into disco-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/neutron/2:14.0.0-0ubuntu1.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** 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 1829171
Note that the updates and upgrades on the test machine are not current.
Obviously.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831514
Title:
Ubuntu 19.04 system update causes boot failure
To
Prior to submitting this bug, this discussion started:
https://answers.launchpad.net/ubuntu/+question/681215
There may be some details that might help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
>Try to force reboot/power down earlier during the boot
Not possible.
This is the boot process:
1. push power button
2. type in decryption password
3. hit enter
4. you immediately receive the Ubuntu splash screen
5. more and more (but not all) red dots appear
6. system hangs at 3 or 4 red dots
** No longer affects: qttools-opensource-src (Ubuntu)
** No longer affects: tightvnc (Ubuntu)
** Also affects: qtbase-opensource-src (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: qtbase-opensource-src (Ubuntu)
Status: New => Fix Released
--
You received
** Changed in: ubuntustudio-meta
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/1830271
Title:
Add obs-studio to ubuntustudio-meta seed
To manage
Public bug reported:
lsp-plugins (https://launchpad.net/ubuntu/+source/lsp-plugins) has been
added to the Universe repository for Eoan. Please update Ubuntu Studio's
seed to include this package.
** Affects: ubuntustudio-meta
Importance: Undecided
Status: New
** Affects:
--- Comment From youh...@us.ibm.com 2019-06-04 16:47 EDT---
is there issue associate with this problem?
How does one recreate this problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected uec-images
** Description changed:
This error is being reproduced on i386 arch when using the pc-kernel
snap from beta or candidate.
> sudo snap install test-snapd-tools
> dmesg
[15131.806107] audit: type=1400
As the error is happening in ubuntu core 16 on i386, I couldn't install
the apport snap due to is is not available for this arch (just for
amd64). So I installed classic and generated the report from there, but
I am not sure this information is the one you want.
--
You received this bug
Hello bugproxy, or anyone else affected,
Accepted lvm2 into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lvm2/2.02.176-4.1ubuntu3.18.10.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1831490/+attachment/5268850/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831490
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1831490/+attachment/5268848/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1831490/+attachment/5268849/+files/ProcCpuinfoMinimal.txt
--
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 1829205
** Description changed:
- On some arm64 systems[*] we are seeing a spew of messages on the
- console:
+ [Impact]
+ We enabled CONFIG_DMA_CMA to fix bug 1803206, but that led to a regression
+ where other systems began spewing on the order of 10K of these messages on
boot:
[ 19.534097]
This is difficult because security/selinux/ doesn't use the *actual* kernel
headers for the kernel being built to get the AF_MAX/PF_MAX defines; those are
not included in the kernel uapi headers. Instead, those defines come from
/usr/include/x86_64-linux-gnu/bits/socket.h which is provided by:
Hi everyone,
It looks like the commit described here, "block: Revert v5.0
blk_mq_request_issue_directly() changes", made it in during our SRU sync
with upstream stable. [1]
It should be included with the 5.0.0-16 Disco kernel that just recently
went out into the "updates" repository. [2]
If you
Hello bugproxy, or anyone else affected,
Accepted lvm2 into disco-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lvm2/2.02.176-4.1ubuntu4.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
You are right, bug is fixed in Ubuntu 18.10 (cosmic) and 19.04 (disco).
I can type text in Kate even without XKB.
** Tags added: cosmic
** Tags removed: cosmic
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
+1
As a workaround, you can compile my fork of the official Gthumb Github
repo:
https://github.com/antongulenko/gthumb
I changed the following keyboard bindings:
- Left/Right keys for switching images
- Scrolling up/down for zooming the current image
The changes are hacked in and not intended
An upload of mesa to disco-proposed has been rejected from the upload
queue for the following reason: "Comet Lake support was dropped without
explanation.".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fix proposed to branch: master
Review: https://review.opendev.org/663133
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831181
Title:
[aodh.notifier] Not setting user_domain_id raises keystone
*** This bug is a duplicate of bug 1823429 ***
https://bugs.launchpad.net/bugs/1823429
** This bug has been marked a duplicate of bug 1823429
linux-oracle ftbfs in disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
the same 4.15 kernel is getting built on b/c/d/e, and
scripts/selinux/genheaders/genheaders.c includes the local header files,
specifically :
#include
which define PF_MAX (via AF_MAX) as 45 for cosmic and later. however
genheaders.c also:
#include "classmap.h"
which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-oracle (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/1823429
*** This bug is a duplicate of bug 1823429 ***
https://bugs.launchpad.net/bugs/1823429
i marked this as dup as i already commented in the other bug explaining
the failure, and that bug is lower numbered. feel free to un-dup if you
disagree.
** This bug has been marked a duplicate of bug
The "Regression Potential" portion of the SRU template is to indicate
how things might go wrong to improve testing of the Stable Release
Update. Can you please update the regression potential with something
that meets that criteria?
** Changed in: modem-manager-gui (Ubuntu Disco)
Status:
In gnome-shell itself, in overview mode and either as favorite or not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831384
Title:
.desktop files not working in Ubuntu 19.04 Gnome
To manage
Khurshid, could you have a look, it seems like you are the one who
rebased the patch for the new nautilus
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820859
Title:
101 - 200 of 756 matches
Mail list logo
