I would suggest to ship at least Mesa 19.0.4, because of the bug
https://bugs.freedesktop.org/show_bug.cgi?id=110355 in some popular
programs.
** Bug watch added: freedesktop.org Bugzilla #110355
https://bugs.freedesktop.org/show_bug.cgi?id=110355
--
You received this bug notification
> LVM module is supposed to create PVs from devices using the links in
> /dev/disk/by-dname/
> folder that are created by udev.
Created by udev how? disk/by-dname is not part of the hierarchy that is
populated by the standard udev rules, nor is this created by lvm2. Is
there something in the
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oem-osp1 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mesa (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance:
@Peter,
Yes, we met the same issue.
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1828604
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1772844
Title:
we'll get the last update of 19.0.x series eventually
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1824111
Title:
Backport packages for 18.04.3 HWE stack
Status in libclc
** Description changed:
- Description:
+ [Impact]
+ Ice Lake (ICL) graphics needs to be enabled for OEM OSP1 image which is based
on 18.04.3 graphics stack with linux-oem-osp1 kernel.
+
+
+ [Test case]
+ The usual desktop usage, graphics tests etc.
+
+
+ [Regression potential]
+
I will take your opinion. Thank you.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1821269
Title:
[Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch
It is fixed from kernel driver, So all linux distros have this issue. We
plan to send the patch to upstream kernel and cc stable-kernel, after
this patch is merged to stable-kernel, I guess all linux distros will
have this fix automatically.
--
You received this bug notification because you are
Public bug reported:
I have dual-booted Ubuntu and Windows and I don't have sound at all.
Before when restart laptop sound back shortly but if I boot it again
there is no sound anymore. Interesting, when type alsamixer I get cannot
open mixer: No such file or directory. I'm noticing that I have
Verified 1.1.0~beta1ubuntu0.16.04.5 by running the attached script. It
does properly throw LockFailedException now. It does give you the cause
of the LockFailedException, which we might want to change eventually,
but um, that's just cosmetics, and might even be useful.
# python3 -c "import apt;
backported patches for mesa 19.0:
f8c3f408a6026f2 intel/genxml: Update MI_ATOMIC genxml definition.
11518384c465b9f i965: Re-enable fast color clears for GEN11.
9175c7058efb13d intel/blorp: Make blorp update the clear color in gen11.
232c0f64891e2f9 isl: Set ClearColorConversionEnable.
** Description changed:
[Impact]
ibus-libpinyin has proved to crash far too often. One or more files in
~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
directory allows the user to keep using ibus-libpinyin.
In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin
So generally, with my SRU hat on, after a longer discussion with Gunnar
I think we should give the backport a spin - but under specific
conditions. We would be keeping the SRU in -proposed for longer than 7
days and I'd appreciate some wider-testing during that time (maybe some
call for testing?).
An upload of libio-socket-ssl-perl to bionic-proposed has been rejected
from the upload queue for the following reason: "reupload required as
this version is known to introduce regressions".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
This bug was fixed in the package poppler - 0.74.0-0ubuntu1.1
---
poppler (0.74.0-0ubuntu1.1) disco; urgency=medium
* debian/patches/git_unicode_search.patch:
- backport a fix for a regression on case-insensitive search
(lp: #1829785)
-- Sebastien Bacher Tue, 21 May
udevadm info -e >/tmp/1828617-2.out
~# ls -l /var/lib/ceph/osd/ceph*
-rw--- 1 ceph ceph 69 May 21 08:44
/var/lib/ceph/osd/ceph.client.osd-upgrade.keyring
/var/lib/ceph/osd/ceph-11:
total 24
lrwxrwxrwx 1 ceph ceph 93 May 28 22:12 block ->
journalctl --no-pager -lu systemd-udevd.service >/tmp/1828617-1.out
Hostname obfusticated
lsblk:
NAME
MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0
*** This bug is a duplicate of bug 1248054 ***
https://bugs.launchpad.net/bugs/1248054
** This bug has been marked a duplicate of bug 1248054
[SRU] dlm package installation fails
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Andrey, I don't know if you saw James' comment as yours may have
coincided but if you can get the ceph-osd package version that would be
helpful. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Changed in: tar (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tar in Ubuntu.
https://bugs.launchpad.net/bugs/1554715
Title:
rmt and rmt-tar should not be autoinstalled
Status in
The attached debdiff to gdb fixes the issue. The patch was cleanly
applied from the upstream GDB git repo, and test results are as posted
to this bug report. No regression were found.
** Patch added: "Fix tagged pointer support."
Test package is available in PPA:
ppa:manjo/gdb-lp1830796
ubuntu@hotdog:~$ apt policy gdb
gdb:
Installed: 8.1-0ubuntu4
Candidate: 8.1-0ubuntu4
Version table:
*** 8.1-0ubuntu4 500
500 http://ppa.launchpad.net/manjo/gdb-lp1830796/ubuntu bionic/main
arm64 Packages
100
== Testing on PPC64EL ==
ubuntu@tiselius:~$ apt policy gdb
gdb:
Installed: 8.1-0ubuntu4
Candidate: 8.1-0ubuntu4
Version table:
*** 8.1-0ubuntu4 500
500 http://ppa.launchpad.net/manjo/gdb-lp1830796/ubuntu bionic/main
ppc64el Packages
100 /var/lib/dpkg/status
Thanks for keeping the bug updated
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
** Description changed:
[Impact]
- GDB fails to debug ARM64 vmlinux debug image with proc/kcore information. For
example it is unable to print values of variables like 'jiffies_64'.
+ GDB fails to debug ARM64 vmlinux debug image with proc/kcore information. For
example it is unable to print
Public bug reported:
[Impact]
GDB fails to debug ARM64 vmlinux debug image with proc/kcore information. For
example it is unable to print values of variables like 'jiffies_64'.
[Test]
# gdb /usr/lib/debug/boot/vmlinux-4.18.0-20-generic /proc/kcore
[New process 1]
Core was generated by
** Changed in: gdb (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1830796
Title:
[Bionic][ARM64]Failure debugging linux kernel
Can't do anything:
apt policy network-manager
network-manager:
Installed: 1.10.6-2ubuntu1.1
Candidate: 1.10.6-2ubuntu1.1
Version table:
*** 1.10.6-2ubuntu1.1 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu
What do you mean with "Can't do anything"? Does your problem now also
occur with the old version, too?
What I want to ask you to do is the following:
With network-manager and systemd updated the problem occurs for you. To
find a possible solution, install the updates, reboot, and do the
Public bug reported:
[Impact]
* As discussed in bug #1628745, the following kernel commit changes
AppArmor mediation behavior on exec transitions:
commit 9f834ec18defc369d73ccf9e87a2790bfa05bf46
Author: Linus Torvalds
Date: Mon Aug 22 16:41:46 2016 -0700
binfmt_elf: switch
** Summary changed:
- Itermittent testsuite failure on (at least) amd64
+ Intermittent testsuite failure on (at least) amd64
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tar in Ubuntu.
** Changed in: tar (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tar in Ubuntu.
https://bugs.launchpad.net/bugs/1189310
Title:
Broken markup in tar.1 manual page
Status in
Test suite got fixed in master too, all is good:
https://git.busybox.net/busybox/commit/?id=b2c123d484dbe261758f27ced213f4649173803b
Thanks a lot for the quick fixes! Included in Ubuntu devel series.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
The attachment "Fix tagged pointer support." seems to be a debdiff. The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch"
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1821269
Title:
[Aspire ES1-131, Realtek ALC255, Mic,
[Expired for openssh (Ubuntu) because there has been no activity for 60
days.]
** Changed in: openssh (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains
** Changed in: gnome-bluetooth (Fedora)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1791405
Title:
bluetooth always in discoverable
This might be a driver bug or it might be a hardware problem.
In case it is a driver bug then I have assigned it to both the 'modeset'
Xorg driver and the kernel 'i915' driver. Can you please boot a newer
version of Ubuntu from USB and tell us if it has the same problem?
19.10:
** No longer affects: cups (Ubuntu Xenial)
** No longer affects: cups (Ubuntu Bionic)
** No longer affects: cups (Ubuntu Cosmic)
** No longer affects: cups (Ubuntu Disco)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
Hey Support ,
I am not able to get resolution of my Monitor which is 1080P, I checked
with the cables and its all good. I think drivers are causing this
issue. Might need help with that.
Regards
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
The ceph-osd package provide udev rules which should switch the owner
for all ceph related LVM VG's to ceph:ceph.
# OSD LVM layout example
# VG prefix: ceph-
# LV prefix: osd-
ACTION=="add", SUBSYSTEM=="block", \
ENV{DEVTYPE}=="disk", \
ENV{DM_LV_NAME}=="osd-*", \
ENV{DM_VG_NAME}=="ceph-*",
by-dname udev rules are created by MAAS/curtin as part of the server
install I think.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1828617
Title:
Hosts randomly
** Tags removed: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1830022
Title:
DirtyCleanInterval should be 0 by default
Status in cups package in Ubuntu:
This feels similar to https://bugs.launchpad.net/charm-ceph-
osd/+bug/1812925. First question, are you running with the latest stable
charms which have the fix for that bug?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Please can you confirm which version of the ceph-osd package you have
installed; older versions rely on a charm shipped udev ruleset, rather
than it being provided by the packaging.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Sorry there was a part missing. Let us try again:
Please create the following files (and directories if needed for them):
1. /etc/systemd/journald.d/noratelimit.conf containing
RateLimitIntervalSec=0
RateLimitBurst=0
2. /etc/NetworkManager/conf.d/debug.conf
[logging]
level=TRACE
domains=ALL
Public bug reported:
See also https://discuss.linuxcontainers.org/t/limits-kernel-memlock-
cannot-exceed-16777216/4856/5
In containers, the limits.kernel.memlock cannot exceed 16777216 when the
container is bionic. The memlock setting is set to 16M in systemd and
cannot be bumped up in an
Sorry there was a part missing. Let us try again:
Please create the following files (and directories if needed for them):
1. /etc/systemd/journald.d/noratelimit.conf containing
RateLimitIntervalSec=0
RateLimitBurst=0
2. /etc/NetworkManager/conf.d/debug.conf
[logging]
level=TRACE
domains=ALL
Yes, it is latest - the cluster is being re-deployed as part of
Bootstack handover.
Corey,
The bug you point to is fixing the sequence of ceph/udev. Here however udev
can't create any devices as they don't exist at the moment of udev run seems so
- when the host boots and settles down - there
Sorry there was a part missing. Let us try again:
Please create the following files (and directories if needed for them):
1. /etc/systemd/journald.d/noratelimit.conf containing
RateLimitIntervalSec=0
RateLimitBurst=0
2. /etc/NetworkManager/conf.d/debug.conf
[logging]
level=TRACE
domains=ALL
This bug was fixed in the package mesa - 19.0.5-0ubuntu1
---
mesa (19.0.5-0ubuntu1) eoan; urgency=medium
* New upstream bugfix release.
* icl-backport.diff: Backport support for fast color clears and
bugfixes for Ice Lake (LP: #1825940).
-- Timo Aaltonen Tue, 28 May 2019
Steve,
This is MAAS who creates these udev rules. We requested this feature to be
implemented in order to be able to use persistent names in further services
configuration (using templating). We couldn't go with /dev/sdX names as they
may change after the reboot, and can't use wwn names as they
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1830022
Title:
DirtyCleanInterval should be 0 by default
Status in cups package in Ubuntu:
** Changed in: mesa (Ubuntu Bionic)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1825940
Title:
[graphics] Enable
** Changed in: network-manager (Ubuntu Bionic)
Assignee: (unassigned) => Till Kamppeter (till-kamppeter)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/942856
** Changed in: gnome-control-center (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1162475
Title:
[hostnamed] Changing hostname
Well I tried restarting AppArmor using `systemctl start apparmor` while
running `dmesg -w -k` and got the following log:
https://pastebin.ubuntu.com/p/98zXMsr6Sy/ I don't see a stack trace for
apparmor itself, just for chrome and pulseaudio.
Is there anyway to have apparmor.service show what
The attachment "fix-memlock-bump.patch" seems to be a patch. If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
Newer versions of NetworkManager, after upgrading from 17.04, have been
bundling the proper fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1695601
Title:
** Patch added: "fix-memlock-bump.patch"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830746/+attachment/5267179/+files/fix-memlock-bump.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Changed in: lvm2 (Ubuntu)
Assignee: Canonical Foundations Team (canonical-foundations) =>
(unassigned)
** Changed in: ubuntu-power-systems
Assignee: Canonical Foundations Team (canonical-foundations) => Canonical
Server Team (canonical-server)
--
You received this bug
I'm not aware of any way to get the apparmor.service to print out what
profile it is working on without actually modifying the service
however your dmesg does show the reason for the failure, it looks like
the apparmor_parser is being killed by the oom killer
[ 5986.338089] [13520] 0 13520
This bug was fixed in the package grilo-plugins - 0.3.8-2ubuntu1.1
---
grilo-plugins (0.3.8-2ubuntu1.1) cosmic; urgency=medium
* debian/patches/git_euronews_update.patch:
- euronews: Update for site changes (lp: #1820140)
-- Sebastien Bacher Fri, 15 Mar 2019 00:37:25
+0100
The verification of the Stable Release Update for grilo-plugins 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
How would you recommend I go about checking which profiles are actually
loaded and which profiles are reported as loaded? I have this from aa-
status: https://pastebin.ubuntu.com/p/c2FbrndDzs/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
The verification of the Stable Release Update for initramfs-tools 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 initramfs-tools - 0.130ubuntu3.8
---
initramfs-tools (0.130ubuntu3.8) bionic; urgency=medium
* Add modules for nvme path components on multipath nvme. LP: #1778844
-- Thadeu Lima de Souza Cascardo Tue, 16 Apr
2019 21:25:56 -0300
** Changed in:
This bug was fixed in the package busybox - 1:1.30.1-4ubuntu4
---
busybox (1:1.30.1-4ubuntu4) eoan; urgency=medium
* Revert previous upload, cherrypick upstream fix for the issue. LP:
#1828282
* Adjust testsuite expectations.
-- Dimitri John Ledkov Thu, 23 May 2019
This bug was fixed in the package e2fsprogs - 1.45.1-1ubuntu1
---
e2fsprogs (1.45.1-1ubuntu1) eoan; urgency=medium
* Use 4k blocksize in all ext4 mke2fs.conf such that lvm migration
between non-4k PVs and 4k PVs works irrespective of the volume
size. LP: #1817097
--
Updated package landed in release pocket - changing project entry to Fix
Released.
** Changed in: ubuntu-z-systems
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in
72 matches
Mail list logo
