It seems that simple
`ls -la /dev/disk/by-path`
freezes `ls` process.
However, /dev listing normally, as well as /dev/disk/{by-id,by-
label,etc} (except `by-path`).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in
ps axu | awk '$8 ~ /^D/'
** Attachment added: "stuck processes (D)"
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+attachment/5245990/+files/stucked_processes.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Attachment removed: "journalctl"
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+attachment/5245988/+files/journalctl-part.txt
** Attachment added: "journalctl"
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+attachment/5245989/+files/journalctl-part.txt
--
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware. I recommend
performing a back up and then investigating the situation. Measures you
might take include
** Changed in: unattended-upgrades (Ubuntu)
Importance: Undecided => High
** Changed in: unattended-upgrades (Ubuntu Artful)
Importance: Undecided => High
** Changed in: unattended-upgrades (Ubuntu Trusty)
Importance: Undecided => Low
--
You received this bug notification because you
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+attachment/5245981/+files/dmesg-part.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
** Attachment added: "lvs -"
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+attachment/5245983/+files/lvs_.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
** Attachment added: "vgcfgbackup -qq main"
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+attachment/5245982/+files/lvm-configuration.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
** Tags added: patch-accepted-upstream patch-forwarded-debian
--
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/1818282
Title:
systemd-networkd - RoutingPolicyRule does not
** Attachment added: "pvs -"
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+attachment/5245984/+files/pvs_.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
** Attachment added: "journalctl"
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+attachment/5245988/+files/journalctl-part.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
Public bug reported:
Hello
I am using lvm snapshots over sofware raid with 4 devices for rsync
backups.
Recently I found out that it is stuck and any operaton with lvm is stuck as
well.
This also causes 1000+ processes of systemd-udevd to be in interpretable sleep
and cannot be killed.
My
** Attachment added: "apt list --installed"
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+attachment/5245979/+files/apt_list_installed.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
** No longer affects: gnome-software (Ubuntu Artful)
** No longer affects: gnome-software (Ubuntu)
** Changed in: unattended-upgrades (Ubuntu Xenial)
Importance: Undecided => High
** No longer affects: apt (Ubuntu Artful)
** No longer affects: apt (Ubuntu)
--
You received this bug
You have been subscribed to a public bug:
Hello
I am using lvm snapshots over sofware raid with 4 devices for rsync
backups.
Recently I found out that it is stuck and any operaton with lvm is stuck as
well.
This also causes 1000+ processes of systemd-udevd to be in interpretable sleep
and
I have faced the same situation with my MacOS after so I contacted
https://applesupportnumber.net/ for the solution and they told me to
update the device but after updating the device the problem remains the
same.
--
You received this bug notification because you are a member of Ubuntu
Touch
** Tags removed: rls-z-incoming verification-needed wily
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1544942
Title:
Marks unneeded packages as manually
** Changed in: apt (Ubuntu Cosmic)
Importance: Undecided => Critical
** Changed in: apt (Ubuntu Bionic)
Importance: Undecided => Critical
** Changed in: apt (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: apt (Ubuntu Trusty)
Importance: Undecided => High
--
You
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1819996
Title:
package tzdata 2018i-0ubuntu0.18.10 failed to install/upgrade:
Public bug reported:
system error window appears when opening ubuntu
ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: tzdata 2018i-0ubuntu0.18.10
ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
It sounds like the XFCE window manager has crashed, but I'm not sure. It
might be a good idea to follow these steps:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
** Summary changed:
- Problem with windows
+ No border around windows, no resizing
** Tags removed: rls-aa-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1458204
Title:
removing kernels should not require a restart afterward
Status
I'm not sure how the Nvidia driver could be related.
Although this looks relevant to keyboard problems. This appears a few
times in your log (comment #22):
sty 27 21:03:24 br00net gnome-shell[2527]: JS ERROR: Exception in callback for
signal: activate: Error: Error invoking
Although ^^^ the above error ^^^ is already covered by bug 1812593.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1812014
Title:
keyboard not responding after suspend
Hmm...`cp` in xterm is a pretty clear indicator that this issue is
random and not triggered by a specific workload.
Lionel suggested that it would be good to have a feedback from the
kernel about what didn't pass validation.
There is a kernel option to generate debug traces for that but you have
(In reply to Mark Janes from comment #20)
> Yoshinori: Mesa i965 team is seeking a way to reproduce this bug, so we can
> analyze and fix it.
>
> How often does this occur in your product? If it is reproducible, then
> perhaps we can use an apitrace to investigate the root cause.
While I
This bug was fixed in the package busybox - 1:1.27.2-2ubuntu6
---
busybox (1:1.27.2-2ubuntu6) disco; urgency=medium
* debian/patches/handle-ip-valid_lft.patch: Don't choke on ip addr add
[...] valid_lft [...] preferred_lft. Closes LP: #1819747.
-- Steve Langasek Tue, 12
@ntyni excellent analysis! i like it a lot, and the patch is clean and
easy to understand.
Are you going to make a debian upload soon, or should I cherrypick that
for Ubuntu now?
** Also affects: perl (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924517
Importance: Unknown
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tiff in Ubuntu.
https://bugs.launchpad.net/bugs/1819983
Title:
package libtiffxx5 4.0.6-1ubuntu0.6 failed to install/upgrade: trying
Public bug reported:
installing from update manager, an apt problem?
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libtiffxx5 4.0.6-1ubuntu0.6
ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
Uname: Linux 4.4.0-142-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm
The CI Bug Log issue associated to this bug has been updated.
### New filters associated
* KBL: igt@perf_pmu@rc6 - fail - Failed assertion: (double)(idle - prev) =
(1.0 + (tolerance)) * (double)(ts[1] - ts[0]) (double)(idle - prev)
= (1.0 - (tol
-
** Description changed:
FFe paperwork still in progress
Feature Freeze exception for AppArmor 2.13.2
The security team is pushing to get AppArmor 2.13 into 19.04 since we
want AppArmor 3 (or higher) in 20.04 and we'd like to incrementally
update to it to test the new features that
** Attachment added: "upgrade.log"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1817799/+attachment/5245939/+files/upgrade.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
Here is the upgrade log. Note that these parser errors are unrelated to
apparmor 2.13 and an issue with the snapd packaging:
AppArmor parser error for /etc/apparmor.d in
/etc/apparmor.d/usr.lib.snapd.snap-confine.real at line 11: Could not open
'/var/lib/snapd/apparmor/snap-confine'
AppArmor
Here is the sbuild build log
** Attachment added: "apparmor_2.13.2-9ubuntu1_amd64-2019-03-13T21:48:49Z.build"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1817799/+attachment/5245940/+files/apparmor_2.13.2-9ubuntu1_amd64-2019-03-13T21%3A48%3A49Z.build
--
You received this bug
** Description changed:
- TODO
+ FFe paperwork still in progress
+
+ Feature Freeze exception for AppArmor 2.13.2
+
+ The security team is pushing to get AppArmor 2.13 into 19.04 since we
+ want AppArmor 3 (or higher) in 20.04 and we'd like to incrementally
+ update to it to test the new
@ddstreet:
> are you upstream nameservers not reachable from your system?
upstream servers have no clue about local LXC/LXD (linuxcontainers.org) DNS
names.
Configuration basically done via
systemd-resolve --interface lxdbr0 --set-dns 10.145.28.1 --set-domain
lxd
This gets broken by the
This bug was fixed in the package isc-dhcp - 4.4.1-2ubuntu4
---
isc-dhcp (4.4.1-2ubuntu4) disco; urgency=medium
* Write pidfile before informing parent of success. (LP: #1819747)
-- Michael Hudson-Doyle Wed, 13 Mar 2019
14:26:56 +1300
** Changed in: isc-dhcp (Ubuntu Disco)
The resolvconf SRU also introduces regressions (LP: #1819625) and is in
the process of being reverted.
** Changed in: resolvconf (Ubuntu Bionic)
Status: Fix Released => Triaged
** Changed in: resolvconf (Ubuntu Cosmic)
Status: Fix Released => Triaged
--
You received this bug
Hello Boris, or anyone else affected,
Accepted resolvconf into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/resolvconf/1.79ubuntu10.18.04.2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Boris, or anyone else affected,
Accepted resolvconf into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/resolvconf/1.79ubuntu10.18.10.2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package.
On a desktop system continuously upgraded from pre-xenial (through non-
LTS releases), I have the following before upgrade:
$ ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 27 Mar 29 2012 /etc/resolv.conf ->
/run/resolvconf/resolv.conf
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for
On Sat, Mar 09, 2019 at 03:59:22PM -, bugproxy wrote:
> This perl script will cause an error on Ubuntu 19.04:
>
> # perl test.pl
> Calling mblen with str=data
> perl: mbrtowc.c:105: __mbrtowc: Assertion `__mbsinit (data.__statep)' failed.
> Aborted
I've reported this bug upstream at
@bruno-42 are you upstream nameservers not reachable from your system?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1819625
Title:
Package
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1819625
Title:
Package resolvconf=1.79ubuntu10.18.04.1 broken
Status in resolvconf
Public bug reported:
This issue was recently fixed in Debian, but seems to have not been
pulled into Ubuntu: https://salsa.debian.org/gdb-
team/gdb/commit/e59e4e54af0fbe9086c40ab80a1000d5c50c7175
Description:Ubuntu Disco Dingo (development branch)
Release:19.04
gdb-multiarch:
Hi,
I have no unusual extensions installed and even though I disabled all gnom
extensions the problem remained.
After checking that, I did what I should have done at the beginning - I changed
display driver to X.Org X Server nouveau and since then I have got no problems
with the keyboard at
I recently installed a fresh system with 18.04 as well and have
experienced this exact issue when attempting to "apt dist-upgrade" from
ssh. In the two instances where systemd was being updated (a few weeks
ago and today), my ssh connection was dropped and I'm unable to re-
connect to the server.
** Description changed:
[Impact]
On Ubuntu Core we recently hit the a race in daemon-reload and systemctl
twice. This race is fixed in systemd upstream: "fix race between daemon-reload
and other commands #8803".
+
+ Note that this is a general problem in systemd with daemon-reload and
+
Public bug reported:
Due to following bug in binutils - gnu assembler
compiled code optimised for AVX512 will not work correctly.
binutils: Bug 23465 - wrongly scale non-8-bit x86 displacements
https://sourceware.org/bugzilla/show_bug.cgi?id=23465
it is fixed in binutils 2.31 but bug exist in
This bug was fixed in the package xorg - 1:7.7+19ubuntu10
---
xorg (1:7.7+19ubuntu10) disco; urgency=medium
* control: Add mesa-vulkan-drivers to xserver-xorg Recommends. (LP:
#1742714)
-- Timo Aaltonen Wed, 13 Mar 2019 13:54:57 +0200
** Changed in: xorg (Ubuntu)
Thank you so much for the solution.
Xubuntu 18.04.02. In the progress to install LAMP.
Decided to switch to MariaDB after install mysql-server/client with apt.
I forgot to purge mysql before "apt install mariadb-server/client", but it
seems to be fine.
Trying to run "mysel_secure_installation"
Tested with 1.1ubuntu1.18.04.7~16.04.2:
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ sudo apt autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
feh libid3tag0 libimlib2 libjpeg-progs libjpeg9
I installed the "ofono" package because it wasn't installed by default
on Linux Mint 19.1 XFCE. And now I don't see an error message anymore.
Thanks, Daniel van Vugt.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio
Tested with 1.1ubuntu1.18.04.7~16.04.2:
The crash does not seem to be occurring even in different form:
https://errors.ubuntu.com/?release=Ubuntu%2016.04=unattended-upgrades=year=1.1ubuntu1.18.04.7~16.04.2
** Tags removed: verification-needed verification-needed-xenial
** Tags added:
Tested with 1.1ubuntu1.18.04.7~16.04.2:
The crash does not seem to be occurring even in different form:
https://errors.ubuntu.com/?release=Ubuntu%2016.04=unattended-upgrades=year=1.1ubuntu1.18.04.7~16.04.2
** Tags removed: verification-needed verification-needed-xenial
** Tags added:
There were no relevant changes between .1 and .2 thus marking this bug
as verified on Xenial again.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Tested with 1.1ubuntu1.18.04.7~16.04.2 on Xenial:
root@x-uu-lp-1260041:~# dpkg -l unattended-upgrades | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name
Tested with 1.1ubuntu1.18.04.7~16.04.2 on Xenial:
root@x-uu-lp-1260041:~# apt-mark auto linux-image-extra-4.8.0-56-generic
linux-image-extra-4.8.0-58-generic linux-image-extra-4.8.0-54-generic
linux-image-extra-4.8.0-53-generic
linux-image-extra-4.8.0-56-generic set to automatically installed.
Tested with 1.1ubuntu1.18.04.7~16.04.2 on Xenial:
root@x-uu-lp-1260041:~# apt-mark auto linux-image-extra-4.8.0-56-generic
linux-image-extra-4.8.0-58-generic linux-image-extra-4.8.0-54-generic
linux-image-extra-4.8.0-53-generic
linux-image-extra-4.8.0-56-generic set to automatically installed.
Tested with 1.1ubuntu1.18.04.7~16.04.2 on Xenial:
root@x-uu-lp-1260041:~# unattended-upgrade --dry-run --debug
Unable to parse Unattended-Upgrade::Allowed-Origins.
Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1998, in
sys.exit(main(options))
File
Still seeing this issue with package and tracking FIFO on log in log out
lightdm.x86_64 1.25.0-1.el7
lightdm-gobject.x86_64 1.25.0-1.el7
lightdm-gtk.x86_64 1.8.5-19.el7
lightdm-gtk-common.noarch 1.8.5-19.el7
[root@caeusadm tmp]# lightdm -v
lightdm
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1776173
Title:
qt print
Verified with unattended-upgrades/1.1ubuntu1.18.04.7~16.04.2 on Xenial:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-xenial/xenial/amd64/u/unattended-
upgrades/20190228_150449_11313@/log.gz
...
Packages with upgradable origin but kept
*** This bug is a duplicate of bug 1260041 ***
https://bugs.launchpad.net/bugs/1260041
** This bug has been marked a duplicate of bug 1260041
Unattended-Upgrades crashes with a dpkg error
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
*** This bug is a duplicate of bug 1260041 ***
https://bugs.launchpad.net/bugs/1260041
** This bug is no longer a duplicate of bug 1602536
/usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin/unattended-upgrade@1468:main:do_auto_remove:cache_commit:commit:_fetch_archives
**
Tested 1.1ubuntu1.18.04.7~16.04.2 on Xenial.
root@x-uu-lp-1260041:~# yes no |apt-get autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
linux-image-4.8.0-53-generic
Verified with 1.1ubuntu1.18.04.7~16.04.2 on Xenial.
root@x-uu-lp-1260041:~# dpkg -l unattended-upgrades | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/
Ext4... the last two messages in that thread direct me to open a new
bug, so I have.
--
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/1815987
Title:
Systemd-tmpfiles-setup
@bhkolts: Yes, not sending an email when only kernel autoremovals took
place is a regression - or an incomplete part of the kernel autoremoval.
It is fixed in 19.04, but the fix is somewhat intrusive thus it may not
be back-ported.
--
You received this bug notification because you are a member
Tested with 1.1ubuntu1.18.04.7~16.04.2 on Xenial:
root@x-uu-lp-1260041:~# unattended-upgrade --dry-run --verbose --debug
Initial blacklisted packages:
Initial whitelisted packages:
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security,
I uploaded both the xenial and bionic version to -proposed now.
--
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/1819728
Title:
Please backport "fix race between
The version for xenial link in comment #9 did successfully run a full
spread run with UC16. This includes the regression test that systemctl
start is not hanging.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Thank you for your bug report, what filesystem do you use? There are
similar warnings in bug #1804603
--
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/1815987
Title:
Thank you for your bug report. Do you have a code example trigger the problem?
Also that should be reported upstream rather, can you send it to
https://gitlab.gnome.org/GNOME/gtk/issues ?
** Changed in: gtk+3.0 (Ubuntu)
Importance: Undecided => Low
** Changed in: gtk+3.0 (Ubuntu)
tested the ppa version (19.0 rc7) on AMD Ryzen / Vega Mobile now, works
fine (desktop, glxgears, vkcube)
--
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/1818516
Title:
FFe:
Verified with 1.1ubuntu1.18.04.7~16.04.2, measured times are similar to
.1, verified previously.
https://objectstorage.prodstack4-5.canonical.com
/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/u/unattended-upgrades/20190228_150449_11313@/log.gz
...
Allowed origins are:
** Also affects: systemd (Ubuntu Disco)
Importance: Low
Status: In Progress
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Bionic)
Exactly. I did the "verification-done-bionic" step for 18.2.2 in comment
#12 above; and unfortunately I don't have an affected school nearby,
where I could test 18.2.8 in cosmic, and installing cosmic in a remote
school would be hard.
Thanks a lot Timo!
--
You received this bug notification
Bump.
--
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/1815987
Title:
Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS
Status in systemd package in Ubuntu:
New
The / usr / lib / tracker / tracker-extract is using almost 100% CPU
resources see attached image
** Attachment added: "100% de recursos da CPU"
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1815089/+attachment/5245857/+files/Captura%20de%20tela%20de%202019-03-13%2011-16-25.png
--
Tested with 1.1ubuntu1.18.04.7~16.04.2:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-xenial/xenial/amd64/u/unattended-
upgrades/20190228_150449_11313@/log.gz
...
To: root@autopkgtest
Auto-Submitted: auto-generated
MIME-Version: 1.0
...
Tested 1.1ubuntu1.18.04.7~16.04.2 on Xenial.
root@x-uu-upgrade:~# unattended-upgrade --dry-run --verbose --debug
Initial blacklisted packages:
Initial whitelisted packages:
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security,
This version fixes a subtle bug added by me when de-conflicting the
diff.
** Patch removed: "Full debdiff for xenial systemd SRU (with correct changelog)"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+attachment/5245818/+files/systemd_229-4ubuntu21.18.debdiff
** Patch
No vpn - DNS resolver broken by update (on production server)
bug@test:~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub
The upstream release tracker probably helps showing that there's only
one identified bug on the list, which is triggered by Intel's CI. AMD
has something similar but not as comprehensive AIUI.
I've tested this on an Intel gen9 (coffee lake) gpu so far, AMD
Ryzen/Vega Mobile is soon done
--
You
bionic was already fixed earlier by 18.2.2-0ubuntu1~18.04.2 in time for
18.04.2 release
cosmic got the exact same oneliner in 18.2.8-0ubuntu0~blah, and then
that was backported to bionic which reopened this bug. Requiring Alkis
to test this on cosmic is too much IMO, as it would involve first to
** Description changed:
[Impact]
There are some new Intel GPU pci-id's that need to be added to several places:
0x3E98
0x87C0
and to make future additions easier, add platform definitions for
Whiskey Lake and Amber Lake too.
[Test case]
- Check that the user session uses
This was already fixed in bionic by 18.2.2-0ubuntu1~18.04.1, now the
same is included upstream in 18.2.8 which was upload to cosmic too as
well as to bionic via a new backport.
Again, I don't have the hardware (AML, WHL is broken atm), adding pci-
id's just allow the X driver to load the DRI
I can confirm the same issues with `systemd-networkd` in Xenial (and
Debian Stretch). Do you know if there is a patch from a modern `systemd`
that can be used to backport a fix to older versions?
When not using `systemd-networkd` (like older dists or "vanilla" Xenial)
it is possible to see when
Public bug reported:
No border around windows, no resizing buttons (max, min, close). Windows
cannot be moved or resized. Alt+tab and Alt+F4 have no effect, but some
other keyboard shortcuts, e.g. ctrl+alt+T and ctrl+Q, seem to work ok.
Only closing a window changes focus; even clicking with
The xenial version of this is NOT ready yet, a second run produced a
CRASH at startup on UC16 with the updated systemd.
** Patch removed: "debdiff with a port of the fix in PR#8803 for xenial"
What testing did you perform?
** Tags removed: verification-done verification-done-cosmic
** Tags added: verification-needed verification-needed-cosmic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
The xenial build of the updated systemd was tested using a full spread
run with no regressions and a new test was added in
https://github.com/snapcore/snapd/pull/6595 to test that the regression
is fixed
This test shows that core/edge is fixed but core/beta which does not yet
has the fix is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
moving back to the metapackage
** Package changed: xorg-server (Ubuntu) => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1742714
Title:
MIR:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
** Description changed:
[Impact]
On Ubuntu Core we recently hit the a race in daemon-reload and systemctl
twice. This race is fixed in systemd upstream: "fix race between daemon-reload
and other commands #8803".
[TEST CASE]
To reproduce its enough to run:
for i in $(seq 50); do
** Changed in: systemd (Debian)
Status: Unknown => New
--
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/1818282
Title:
systemd-networkd - RoutingPolicyRule does not
1 - 100 of 116 matches
Mail list logo
