** Changed in: gnome-online-accounts (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/1811596
Title:
Ubuntu Single
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1821863
Title:
Need to add Intel CML
Thank you Timo!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1795857
Title:
enable CONFIG_DRM_BOCHS
Status in kmod package in Ubuntu:
Fix Released
Status in linux
Change introduced in Ubuntu-meta in 1.431 [1]
But since that usually only reflects the seeds that must be from there somehow.
[1]: https://launchpad.net/ubuntu/+source/ubuntu-meta/1.431
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Yes, I'm SRUing that, but I also extend the fix first with
https://github.com/mvo5/unattended-upgrades/pull/187 to not hold qemu
needlessly back.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
@rbalint I've collect logs from both u-u packages. Latest u-u stucks in
a loop. Please see zip attached.
I have hold packages
$ apt-mark showhold
linux-generic
linux-headers-generic
linux-image-generic
linux-libc-dev
papirus-icon-theme
** Attachment added: "uu.zip"
** Changed in: apt (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1785778
Title:
Hash Sum mismatch Ubuntu Server 18.04.1 LTS
Could you add your journalctl log to the bug at the time of the issue?
** Changed in: tracker (Ubuntu)
Importance: Undecided => High
** Changed in: tracker (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Thank you for your bug report. Could youa dd your journalctl log after getting
the issue?
Could you also open the settings -> sound -> application tab and see if there
is a slider added there when the sound is heard?
** Changed in: alsa-driver (Ubuntu)
Importance: Undecided => Low
**
Thanks, I didn't notice the :i386 first time I read the description,
looks like a multiarch issue
** Changed in: libxkbcommon (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Thank you for your bug report, that sounds like an upstream issue and
probably worth reporting on https://lists.gnu.org/archive/html/bug-
coreutils/
** Changed in: coreutils (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch
Thanks Rbalint for fixing that.
Since a triggering change in qemu is in at least >=Bionic and was reported to
even affect continuous unattended upgrades there would you considering SRUing
your changes as needed?
I added tasks for all releases, but set >=Bionic to high to to that being an
issue
I think we can go with a simple catch all of linux-.* as in
https://salsa.debian.org/apt-team/apt/merge_requests/59
For explanation as to why this works: apt takes the listed patterns,
then appends the kernel versions to it, and then anchors it. So, with
linux-.* you end up with patterns:
*** This bug is a duplicate of bug 1823093 ***
https://bugs.launchpad.net/bugs/1823093
** This bug has been marked a duplicate of bug 1823093
cannot be installed in containers
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
@spvkgn Could you please collect the logs of the upgrade where u-u
1.1ubuntu1.18.04.10 got stuck?
Did you have any special origin or local package configured?
If you could downgrade the packages which got upgraded could you please run
1.1ubuntu1.18.04.10 with --debug --verbose --download-only to
Germinate [2] clearly points at the seeds.
bin:multipath-tools src:multipath-tools why:Ubuntu.Disco server seed
bin:multipath-tools-boot src:multipath-tools why:Ubuntu.Disco
server-ship-live seed
The second I saw before in the seeds [1], but where exactly is the first
line listed here within
*** This bug is a duplicate of bug 1817317 ***
https://bugs.launchpad.net/bugs/1817317
bug #1817317 is about a similar issue in the init script, best to
comment on that bug rather than use a new one?
** Changed in: openssh (Ubuntu)
Importance: Undecided => Low
** This bug has been marked
Inhibitor support:
https://salsa.debian.org/apt-team/apt/merge_requests/60
** Changed in: apt (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
root@d-upgr:~# apt remove multipath-tools -s
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
ibverbs-providers kpartx libaio1 libfreetype6 libibverbs1 libnl-3-200
Now that we know that we can drop all bug ubuntu-meta task, marking the
others invalid.
** Changed in: multipath-tools (Ubuntu)
Status: New => Invalid
** Changed in: multipath-tools (Ubuntu)
Status: Invalid => Triaged
** Changed in: multipath-tools (Ubuntu)
Importance:
Yep, once checking the right and up to date branches it seems clear.
I found [1], subscribing xnox here as well.
This change was on late February, there was no ubuntu-meta update since
then so the issue wasn't triggered.
I think we'd want to undo the seed change, but in a fashion so that what
*** This bug is a duplicate of bug 1823093 ***
https://bugs.launchpad.net/bugs/1823093
This was initially triggered by:
https://code.launchpad.net/~xnox/ubuntu-seeds/+git/ubuntu-seeds/+merge/363541
Which was matching cleanups we did earlier this year and again in Malta.
But that there was
Public bug reported:
Since upgrade direct from start video resolutio borked.
Starting with 5.0.0.7 works fine - 5.0.0.11.12 has problem
could be - as hard to see - other programmas also unusable. Setting /
Tweaktools etc can't be used
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg
Public bug reported:
use host uuid on kvm on power too
On power, the qemu uuid is exposed as
/sys/firmware/devicetree/base/vm,uuid and should be used like
/sys/class/dmi/id/product_uuid is used on x86.
** Affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
** Affects:
Ack. Also DPM mode has LPAR UUID we should be using.
--
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/1824810
Title:
use host uuid on kvm on power too
Status in libvirt
On s390x it only uses sysinfo for systemd-detect-virt,
src/basic/virt.c:306:r = get_proc_field("/proc/sysinfo", "VM00
Control Program",
WHITESPACE, );
but there also the Host UUID is exposed:
$ cat /proc/sysinfo
VM00 UUID:0804001f-c45f-4345-994f-9fec048e822e
There
Public bug reported:
attempting to find tool and solution to error msg displayed when booting
ubuntu, nooby so attempting to climb learning mountain
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
In that container that has no profiles at all I can explicitly load them.
$ sudo apparmor_parser -r /etc/apparmor.d/usr.sbin.libvirtd
$ systemctl restart libvirtd
makes it show up correctly
1 processes are in enforce mode.
/usr/sbin/libvirtd (1146)
But why is it missing in the first place
*** This bug is a duplicate of bug 1806961 ***
https://bugs.launchpad.net/bugs/1806961
** This bug has been marked a duplicate of bug 1806961
Lock can be circumvented by switching tty when using lightdm
** Information type changed from Private Security to Public Security
--
You received
Since I started seeing this in libvirt There might be reasons that is done that
way but this affects me and probably other use cases e.g. if I install libvirt:
$ apt install libvirt-daemon-system
$ aa-status | grep libvirt
On my test systems the containers do not get any profile loaded:
$
This bug was fixed in the package ubuntu-meta - 1.425.1
---
ubuntu-meta (1.425.1) cosmic; urgency=medium
* Added ubuntu-wsl metapackage from the wsl seed (LP: #1822341)
* Added wslu to ubuntu-wsl
-- Balint Reczey Sat, 30 Mar 2019 15:59:08 +0100
** Changed in: ubuntu-meta
Perhaps because of bug 1823379, which broke some code's dynamic
detection of apparmor being enabled via
/sys/module/apparmor/parameters/enabled?
The fix is working its way through the queue and is currently in
proposed.
--
You received this bug notification because you are a member of Ubuntu
Sorry, no. Ignore comment #10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1824812
Title:
apparmor no more starting in Disco LXD containers
Status in apparmor package
@spvkgn Thanks!
>From the log it seems this is not a loop, just applying the very high cost
>fallback for each held package:
...
Checking: linux-generic ([,
])
package linux-generic upgradable but fails to be marked for upgrade (E:Unable
to correct problems, you have held broken packages.)
https://www.redhat.com/archives/libvir-list/2019-April/msg00987.html
--
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/1824810
Title:
use host uuid on kvm on power too
Apparmor is disabled in LXD containers now !?!
Compare aa-status after spawning a new container.
root@d-testapparmor:~# aa-status
apparmor module is loaded.
15 profiles are loaded.
15 profiles are in enforce mode.
/snap/core/6673/usr/lib/snapd/snap-confine
** Changed in: util-linux (Ubuntu)
Assignee: Manoj Iyer (manjo) => Canonical Foundations Team
(canonical-foundations)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
In Cosmic /lib/systemd/system/apparmor.service pointed to "/etc/init.d/apparmor
start"
This had some code, but it was not triggered:
if [ -x /usr/bin/systemd-detect-virt ] && \
systemd-detect-virt --quiet --container && \
!
*** This bug is a duplicate of bug 1806961 ***
https://bugs.launchpad.net/bugs/1806961
** Summary changed:
- Security breach with CRTL+ALT+F7
+ CRTL+ALT+F7 bypasses the lock-screen with lightdm
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Tags added: regression-update
--
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/1824804
Title:
Unattended upgrades falls back to adjust all upgradable
** Changed in: libvirt (Ubuntu)
Status: New => Invalid
** Changed in: apparmor (Ubuntu)
Status: New => Triaged
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
** Changed in: apparmor (Ubuntu)
Importance: Undecided => High
--
You
This is affecting radosgw's civetweb (embedded webserver) when SSL is in
used for Bionic which doesn't yet support OpenSSL 1.1 in civetweb v1.8
-> LP: #1822872 .
The support of OpenSSL 1.1 start only with civetweb v1.10 and later.
- Eric
--
You received this bug notification because you are a
Public bug reported:
The fix for LP: #1821101 allowed installing packages for which APT's
resolver could not find solution for without adjusting other packages,
but also tries to adjust many packages to install packages which are
held back.
See:
bug is still present in disco xubuntu iso "final" 04-13.1-2019
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1821609
Title:
lightdm login screen briefly appears and then
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtsvg-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1824678
Title:
package libqt5svg5:amd64 5.11.1-2 failed to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
Public bug reported:
I have four 18.04 servers that are regularly updated and have a
bond/bridge configured via netplan. Every so often the interfaces
themselves will have "speed changed to 0" and the server will be
unresponsive over network. The servers are still usable via the console,
though.
The new bug: LP: #1824804
--
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/1396787
Title:
checking trust of archives eats a lot of cpu
Status in
This bug was fixed in the package systemd - 239-7ubuntu10.13
---
systemd (239-7ubuntu10.13) cosmic; urgency=medium
[ Ioanna Alifieraki ]
* d/p/backport_network-fix-return-value-of-routing_policy_rule_get.patch,
This bug was fixed in the package systemd - 239-7ubuntu10.13
---
systemd (239-7ubuntu10.13) cosmic; urgency=medium
[ Ioanna Alifieraki ]
* d/p/backport_network-fix-return-value-of-routing_policy_rule_get.patch,
This bug was fixed in the package systemd - 237-3ubuntu10.20
---
systemd (237-3ubuntu10.20) bionic; urgency=medium
[ Ioanna Alifieraki ]
* d/p/backport_network-fix-return-value-of-routing_policy_rule_get.patch,
The verification of the Stable Release Update for systemd 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 systemd - 237-3ubuntu10.20
---
systemd (237-3ubuntu10.20) bionic; urgency=medium
[ Ioanna Alifieraki ]
* d/p/backport_network-fix-return-value-of-routing_policy_rule_get.patch,
The verification of the Stable Release Update for systemd 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
Yep, adding
Environment=SFS_MOUNTPOINT=/sys/kernel/security/apparmor/
to
/lib/systemd/system/apparmor.service
Fixes the bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
The verification of the Stable Release Update for ubuntu-meta 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
** Description changed:
+ The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-control-center. This problem was most recently seen with package version
1:3.30.0-0ubuntu1, the problem page at
https://github.com/systemd/systemd/pull/12321
--
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/1824810
Title:
use host uuid on kvm on power too
Status in libvirt package
Thanks for the autopkgtest check! Looks good. For cosmic (and partially
bionic too), I will not be hinting the test failures that we think LP:
#182423 is responsible for. Since apparently those should go away with
the new snapd - if not, we'll at least know what's up.
Few others I will hint
Adding set -x and calling this directly:
Cosmic:
. /lib/apparmor/functions
is_container_with_internal_policy
+ local ns_stacked_path=/sys/kernel/security/apparmor/.ns_stacked
+ local ns_name_path=/sys/kernel/security/apparmor/.ns_name
+ local ns_stacked
+ local ns_name
+ '[' -f
Once again today I couldn't connect to the SSID I normally use, I tried
something in network manager, through the drop down menu ( accessible through
left click on the network icon/indicator located on the upper panel, all the
way down the menu, select "modifications des connexions" ( don't
I got a reply to my bug report on gnu.org which says:
"
From:
Paul Eggert
It works for me with coreutils 8.31 on RHEL 7 x86-64:
$ date +%-Y -d "- 2010 years"
9
Most likely you are running on a 32-bit machine, and dates in the year 9
cannot be represented in a 32-bit timestamp. So a simple fix
*** This bug is a duplicate of bug 1824677 ***
https://bugs.launchpad.net/bugs/1824677
** This bug has been marked a duplicate of bug 1824677
Display only has 640x480
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Once again today I couldn't connect to the SSID I normally use, I tried
something in network manager, through the drop down menu ( accessible through
left click on the network icon/indicator located on the upper panel, all the
way down the menu, select "modifications des connexions" ( don't
** Also affects: apparmor
Importance: Undecided
Status: New
** Changed in: apparmor
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
Ok, it is now reported upstream:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=35289
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1824688
Title:
date+%-Y -d "- N
There are only a couple of reports in the Error Tracker bucket about
this happening with version 2.20.10-0ubuntu13.3 and those are likely
showing that version due to apport's late package version collection.
Setting to verification-done.
** Tags removed: verification-needed-cosmic
** Tags added:
** Summary changed:
- apparmor no more starting in Disco LXD containers
+ apparmor does not start in Disco LXD containers
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
This is due to a bug in upstream parser/rc.apparmor.functions because
SFS_MOUNTPOINT is only set after is_apparmor_loaded() is called, but
is_container_with_internal_policy() doesn't call it.
/lib/apparmor/apparmor.systemd calls is_container_with_internal_policy()
prior to apparmor_start() and it
Public bug reported:
It seems to randomly lockup.
Often, I am able to scroll the mouse pointer without being able to
interact with the desktop itself.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
Uname:
Nope, glib fix is enough for nautilus.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1760569
Title:
Nautilus crashes in g_free -> g_bookmark_file_move_item ->
This bug was fixed in the package ubuntu-meta - 1.417.1
---
ubuntu-meta (1.417.1) bionic; urgency=medium
* Added ubuntu-wsl metapackage from the wsl seed (LP: #1822341)
* Added wslu to ubuntu-wsl
-- Balint Reczey Sat, 30 Mar 2019 15:59:08 +0100
** Changed in: ubuntu-meta
This bug was fixed in the package ubuntu-meta - 1.361.3
---
ubuntu-meta (1.361.3) xenial; urgency=medium
* Added ubuntu-wsl metapackage from the wsl seed (LP: #1822341)
* Added wslu and ubuntu-minimal's dependencies and recommends to ubuntu-wsl
-- Balint Reczey Sat, 30 Mar
Only Line Out works
--
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/1824205
Title:
[MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front]
Playback
do you notice similar (problematic) behavior when just restarting
networkd, e.g.:
$ sudo systemctl restart systemd-networkd
or, stopping systemd-networkd, e.g.:
$ sudo systemctl stop systemd-networkd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I have ran a few tests on 16.04, 18.04, 18.10, and 19.04 (all X86_64):
16.04:
root@u1604:~# date +%-Y -d '- 2010 years'
9
root@u1604:~# date --version
date (GNU coreutils) 8.25
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
Thanks for the testing C de-Avillez.
Here's the output of debug:
$ date +%-Y -d "- 112 years" --debug
date: parsed relative part: -112 year(s)
date: input timezone: system default
date: using current time as starting value: '20:47:40'
date: using current date as starting value: '(Y-M-D)
Uploaded 2.13.2-9ubuntu6 with the SFS_MOUNTPOINT change.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1824812
Title:
apparmor does not start in Disco LXD containers
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.2
---
netplan.io (0.96-0ubuntu0.18.10.2) cosmic; urgency=medium
* d/p/0001-Partially-revert-the-change-for-enabling-systemd-net.patch:
Partially revert changes to networkd jobs ordering: leave systemd-networkd
The verification of the Stable Release Update for netplan.io 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 netplan.io - 0.96-0ubuntu0.18.10.2
---
netplan.io (0.96-0ubuntu0.18.10.2) cosmic; urgency=medium
* d/p/0001-Partially-revert-the-change-for-enabling-systemd-net.patch:
Partially revert changes to networkd jobs ordering: leave systemd-networkd
Public bug reported:
In disco, when policykit prompted me for a password in order for update-
manager to dispatch instructions to aptdaemon to perform package
updates, the password dialog remained on the screen after I clicked
'authenticate'.
The window is not clickable, it appears not to even
Restarting polkit.service does not cause the window to disappear.
** Changed in: policykit-1 (Ubuntu)
Importance: Undecided => High
** Tags added: rls-dd-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Since the apparmor SFS_MOUNTPOINT change is small, I'll prepare an
upload for that immediately. We may need another parser update for the
other issue.
** Changed in: apparmor (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
I noticed that confinement inside of LXD containers works fine when
shiftfs is disabled:
$ sudo rmmod shiftfs
$ sudo mv /lib/modules/5.0.0-11-generic/kernel/fs/shiftfs.ko .
$ sudo systemctl restart snap.lxd.daemon
$ lxc launch ubuntu-daily:d noshift
Creating noshift
Starting
*** This bug is a duplicate of bug 1504897 ***
https://bugs.launchpad.net/bugs/1504897
** This bug has been marked a duplicate of bug 1504897
packages with only upstart+systemd without sysvinit fail to upgrade with
do-release-upgrade: upgrade tarballs ship obsolete invoke-rc.d
--
You
@Thapelo, seems the back port is not yet in Cosmic (18.10). Follow the
steps recommended by Mikhail Shevtsov to resolve the issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
There are two bugs that are causing trouble for apparmor policy in LXD
containers:
1. the rc.apparmor.functions bug (easy fix: define SFS_MOUNTPOINT at the right
time
2. there is some sort of an interaction with the 5.0.0 kernel that is causing
problems
I'll give complete instructions on how
Assaf Gordon reports that he did not reproduce the problem on Ubuntu
Live amd64 dated 2019-04-13 22:28; see:
https://debbugs.gnu.org/35289#25
Perhaps the output of 'env' and 'strace' will help the original reporter
diagnose the problem.
--
You received this bug notification because you are a
Here's the strace output.
** Attachment added: "straceout"
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1824688/+attachment/5256046/+files/straceout
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils
The following will reproduce the issue in a disco VM with disco LXD
container:
Initial setup:
1. have an up to date disco vm
$ cat /proc/version_signature
Ubuntu 5.0.0-11.12-generic 5.0.6
2. sudo snap install lxd
3. sudo adduser `id -un` lxd
4. newgrp lxd
5. sudo lxd init # use defaults
6. .
> $ dig phspi05 @192.168.2.1
> ;; Warning: Message parser reports malformed message packet.
that's generally not good...
> phspi05. 69314 IN A 192.168.2.35
ok, this is resolving the "single label" name. systemd-resolved never
forwards lookups of single-label names (except
There are several issues that need fixing here:
https://github.com/mvo5/unattended-upgrades/pull/191
https://github.com/mvo5/unattended-upgrades/pull/189
** Changed in: unattended-upgrades (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member
Okay, I have a fix for the shiftfs side I think. Attached here.
** Patch added: "UBUNTU: SAUCE: shiftfs: use correct llseek method for"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1824812/+attachment/5256074/+files/0001-UBUNTU-SAUCE-shiftfs-use-correct-llseek-method-for-d.patch
--
Hello Anderson, or anyone else affected,
Accepted unattended-upgrades into disco-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/unattended-
upgrades/1.10ubuntu4 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello errors.ubuntu.com, or anyone else affected,
Accepted unattended-upgrades into disco-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/unattended-
upgrades/1.10ubuntu4 in a few hours, and then in the -proposed
repository.
Please help us by testing
*** This bug is a duplicate of bug 1504897 ***
https://bugs.launchpad.net/bugs/1504897
** This bug has been marked a duplicate of bug 1504897
packages with only upstart+systemd without sysvinit fail to upgrade with
do-release-upgrade: upgrade tarballs ship obsolete invoke-rc.d
--
You
** Package changed: policykit-1 (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1824874
Title:
undismissable, unclickable
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
unattended-upgrades. This problem was most recently seen with package version
1.10ubuntu3, the problem page at
https://errors.ubuntu.com/problem/dbb18e4c8f3777ec91c18aefd3a429f661227655
1 - 100 of 124 matches
Mail list logo
