libseccomp on bionic looks good from what I can see on
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#libseccomp - can this please
migrate now?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
similarly for xenial there is only one failure for libseccomp
autopkgtests which is systemd/i386 - https://people.canonical.com
/~ubuntu-archive/proposed-
migration/xenial/update_excuses.html#libseccomp - and this looks
reasonably flaky in recent history
https://autopkgtest.ubuntu.com/packages/s/sy
** Description changed:
on hirsute (21.04) software-properties-qt (software-properties-
qt/hirsute 0.99.8) (also callable as software-properties-kde) throws a
python exception when a package download source of "other" is selected.
+ the same error occurs when using software-properties-gtk.
Public bug reported:
on hirsute (21.04) software-properties-qt (software-properties-
qt/hirsute 0.99.8) (also callable as software-properties-kde) throws a
python exception when a package download source of "other" is selected.
this python traceback appears in the console:
Traceback (most recent
And finally after some fixups in the builders (thanks cjwatson!)
https://launchpad.net/ubuntu/+source/nss/2:3.55-1ubuntu3.1 also has built
riscv64.
All ready now
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
** Changed in: systemd
Status: Unknown => Fix Released
--
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/1921696
Title:
Failed to start Load/Save RF Kill Switch Status
Public bug reported:
I updated network-manger on hirsute:
network-manager-config-connectivity-ubuntu (1.30.0-1ubuntu3) over
(1.30.0-1ubuntu2)
During the postinst run, I get:
Setting up network-manager-config-connectivity-ubuntu (1.30.0-1ubuntu3) ...
Failed to restart network-manager.service: Un
[Expired for unattended-upgrades (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: unattended-upgrades (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unatt
Public bug reported:
Currently running 21.04, apport version is 2.20.11-0ubuntu62 .
When I try to fill a bug, I see:
$ ubuntu-bug network-manager
ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/repor
** Tags added: focal
** Package changed: xorg (Ubuntu) => xorg-server (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/1923513
Title:
xrandr --panning problem
Status
** Package changed: xorg (Ubuntu) => simple-scan (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/1923512
Title:
Simple Scan
Status in simple-scan package in Ubuntu:
It appears 2560x1440 was a fake mode created by the open source driver.
It's not a mode that is officially supported by the monitor itself,
whose data I have decoded below:
EDID version: 1.4
Manufacturer: GSM Model 23305 Serial Number 181370
Made in week 5 of 2016
Digital display
10 bits per prima
There was a suggestion in bug 1912940 that the latest hirsute updates
have fixed the problem. Please run:
sudo apt update
sudo apt full-upgrade
and tell us if the problem persists.
** This bug is no longer a duplicate of bug 1912940
Intel Wireless-AC 3165 [8086:3166] Subsystem [8086:4210]
Thank you for the time & effort shown in researching the issue you've
experienced.
Before the bug can really be accepted & worked on by Ubuntu, it'll need
to be confirmed that Linux Mint run-time adjustments are not-at-play,
ie. confirmation on a pure Ubuntu system (with logs provided).
Your logi
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Please execute the following command only once, as it will automatically
gather debugging information, in a terminal:
apport-collect 1923513
When reporting bugs in the future please use apport by using 'ubuntu-
b
Issues have been assigned numbers CVE-2021-30498、CVE-2021-30499
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-30498
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-30499
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
** Tags removed: need-amd64-retrace
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1923517
Title:
tracker-store crashed with signal 5
Status in tracker package in Ubuntu:
Public bug reported:
This happens with g_listenv
jpeisach@Joshua-PCTest ~/D/xreader-2.8.3 (master)>
addr2line -e /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6800.0 3F3A7 -fCi
g_listenv
??:?
ProblemType: Crash
DistroRelease: Ubuntu 21.04
Package: tracker 2.3.6-2
ProcVersionSignature: Ubuntu 5.11.
Public bug reported:
Non si avvia
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18
Uname: Linux 4.15.0-122-generic i686
.tmp.unity_support_test.0:
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: i386
Composi
Public bug reported:
Dear community
Recently I upgraded my old netbook from Linux from Linux Mint 18 to Linux Mint
20
Distribution:
cat /etc/upstream-release/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu Focal Fossa"
Netbook is with s
just tried to use netplan on a public facing server, discovered there's
no `ucarp` integration, and discovered this bug.
is there any ETA on these outstanding items? network HA is a nightmare
without CARP, this feels like essential server functionality.
--
You received this bug notification beca
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986836
Apparently I had not created the bug report correctly the first time.
** Bug watch added: Debian Bug tracker #986836
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986836
--
You received this bug notification because you are a membe
couldN’T, grr
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1921664
Title:
Recent update broke qemu-system-riscv64
Status in binutils package in Ubuntu:
New
Status in
That would explain why I could reproduce with personal builds. Glibc
looks very relevant here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1921664
Title:
Recent updat
Please note that upstream has indicated that this issue only affects the
xmllint binary, and not the shared library.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1895839
T
>From my test PPAs the version "1:5.2+dfsg-9ubuntu2~hirsuteppa3" which is
a no-change rebuild of the formerly working "1:5.2+dfsg-9ubuntu1" did in
three tries fail three times.
So we are not looking at anything that is in the qemu source or the
Ubuntu/Debian Delta applied to it. But at something
** Also affects: systemd via
https://github.com/systemd/systemd/issues/18677
Importance: Unknown
Status: Unknown
--
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/1
** Description changed:
+ [Impact]
+
+ If you enable the guest session feature on e.g. Ubuntu MATE, you are met
+ by an error message when trying to enter a guest session:
+
+ "Could not update file ICEauthority file /run/user/XXX/ICEauthority"
+
+ Even if it's not always a fatal error (the log
I'm marking this invalid for systemd (the patch there was reverted) and
fix released for plymouth, with the assumption this was fixed with the
patch for bug 1817738.
If anyone is able to reproduce the problem please add a comment.
--
You received this bug notification because you are a member of
A security update will be issue in next days to fix it on Ubuntu
releases.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to exiv2 in Ubuntu.
https://bugs.launchpad.net/bugs/1923479
Title:
out of buffer access and Integer ove
issued*
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to exiv2 in Ubuntu.
https://bugs.launchpad.net/bugs/1923479
Title:
out of buffer access and Integer overflow in Exiv2
Status in exiv2 package in Ubuntu:
In Progress
B
There are no CVEs for this issues so far.
** Changed in: exiv2 (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to exiv2 in Ubuntu.
https://bugs.launchpad.net/bugs/1923479
Title:
out
Public bug reported:
An out of buffer access:
https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d
and a Integer overflow :
https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0
affects Exiv2 in ubuntu releases
** Affects: exiv2 (Ubuntu)
Unfortunately I can't reproduce this bug, even with the
0.9.3-1ubuntu7.18.04.1 version of plymouth installed, so I can't say for
sure that it's fixed with plymouth 0.9.3-1ubuntu7.18.04.2.
Also note that the [test case] in the description is wrong, that would
be correct with the systemd change made
** Package changed: systemd (Ubuntu) => xdm (Ubuntu)
** Bug watch added: Debian Bug tracker #948346
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948346
** Also affects: xdm (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948346
Importance: Unknown
Status: Unkno
** Tags added: patch
--
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/1923432
Title:
apparmor-utils: missing CAP_CHECKPOINT_RESTORE in
/etc/apparmor/severity.db
Status i
New debdiff that contains a proper reference to the upstream patch.
Thanks!
** Patch added: "apparmor-utils-support-cap-checkpoint-restore.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1923432/+attachment/5486963/+files/apparmor-utils-support-cap-checkpoint-restore.debdiff
** Description changed:
+ [impact]
+
+ systemd-rfkill fails when running under kernel 5.10 or later due to
+ change in the kernel/userspace api
+
+ [test case]
+
+ on a system with kernel 5.10 or later, check systemd-rfkill status or
+ journal output, see comment 3 for specific failure text
+
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu.
https://bugs.launc
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: orca (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu.
https://bugs.launchpad
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: at-spi2-core (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu.
https://bugs.l
On Mon, Apr 12, 2021 at 03:07:45PM -, Andrea Righi wrote:
> @sbeattie sorry I didn't notice your comment, I can post another debdiff
> that includes the proper upstream commit.
Probably would be for the best for when we do a merge in the I
cycle, to make identifying which patches can be droppe
The status file seems fine, apt is happy with it, this is either a bug
in apt-listchanges or a specific FS corruption, but haven't seen that
before.
** Package changed: apt (Ubuntu) => apt-listchanges (Ubuntu)
** Changed in: apt-listchanges (Ubuntu)
Status: New => Triaged
--
You received
** Changed in: lightdm (Ubuntu Groovy)
Status: Triaged => Incomplete
--
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/1921655
Title:
lightdm-guest-session ICEauthorit
Public bug reported:
On the first login of the week, xdm (1.1.11-3ubuntu2) fails to start on
Ubuntu 20.04.
More correctly, it does start, but exits almost immediately on signal
12. It leaves /var/run/xdm.pid behind, and also a running X server with
no clients. This makes it hard to restart, for o
This bug was fixed in the package lightdm - 1.30.0-0ubuntu4
---
lightdm (1.30.0-0ubuntu4) hirsute; urgency=medium
* debian/patches/fix-guest-session-ICEauthority-error.patch:
- Fixes AppArmor issue which prevented access to the guest session
feature in e.g. MATE (LP: #1921
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: 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/1921696
Title:
Failed to start Load/Save
** Changed in: apt (Ubuntu)
Status: New => Triaged
** Changed in: apt (Ubuntu)
Importance: Undecided => Low
--
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/1918930
Tit
** Changed in: apt (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1918920
Title:
Harden test for no new acquires after tr
All the SRUs were released the same day, block tags were ignored :-(
** Changed in: apt (Ubuntu)
Status: In Progress => 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/
We set Acquire::Retries to 10 on autopkgtest.
** Changed in: apt (Ubuntu)
Status: New => Invalid
** Changed in: auto-package-testing
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Changed in: apt (Ubuntu)
Importance: Undecided => Medium
** Changed in: apt (Ubuntu)
Importance: Medium => Low
** Changed in: apt (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
@sbeattie sorry I didn't notice your comment, I can post another debdiff
that includes the proper upstream commit.
--
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/1923432
Ti
** Patch added: "apparmor-utils-support-cap-checkpoint-restore.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1923432/+attachment/5486955/+files/apparmor-utils-support-cap-checkpoint-restore.debdiff
--
You received this bug notification because you are a member of Ubuntu
Tou
Please report on the new GitHub of CUPS on OpenPrinting:
https://github.com/OpenPrinting/cups/issues
On Apple the CUPS project is dead and bug reports probably not read any
more.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Bug watch added: Red Hat Bugzilla #1858866
https://bugzilla.redhat.com/show_bug.cgi?id=1858866
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1923262
Title:
backup /e
** Changed in: shadow (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1923262
Title:
backup /etc/passwd- file should be mode
For some additional context, here is a related bug report for redhat:
https://bugzilla.redhat.com/show_bug.cgi?id=1858866 (they decided to
wont-fix, indicating the flaw is with the CIS benchmark).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whic
I largely agree but I'd like to point out a little bit of nuance. Even
on modern (e.g., 20.04) systems using shadow by default, global
read/write access to /etc/passwd{,-} _can_ (in some scenarios) still
problematic. A system will still function fine even if /etc/passwd has
000 permissions (+/- som
Public bug reported:
Ideally we should strive to boot rootfs from a matching hard drive.
I.e. if we are booting rootfs by UUID, we should try to find the one
that came from the same drive as where ESP (UEFI) came from, or u-boot
spl / u-boot got loaded from (loader1/loader2).
Such that for examp
Nothing to do for me. Ubuntu 20.10 HP spectre x360. 5.11.22 Kernel (no
microphone)
--
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/1840725
Title:
Microphone not working
This is https://gitlab.com/apparmor/apparmor/-/merge_requests/656
upstream, and was addressed in
https://gitlab.com/apparmor/apparmor/-/merge_requests/656/diffs?commit_id=2c2dbdc3a3012ce06371edc1e9be6f58711d8565
on the master branch and was cherrypicked to the apparmor 3.0 branch in
https://gitlab.
@Sebastien Sorry for the late reply.
I recall that the workaround consisted in adding a random delay to the
apt-daily task, so that it would not happen *right* at startup.
How exactly this was done, unfortunately, I did write it down :-/ but I
think it was adding or creating the file ./system/apt
Hi Sebastian,
the patch set the job state to backend error.
I don't think openprinting is the right error here. The problem is in
the backend (the USB backend) when it's not possible to communicate with
a USB printer. This usually means that the printer is not connected.
--
You received this bu
What's the status of the patch upstream? The cups reports mentioned
earlier got close asking to report to openprinting instead, did you do
that?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.laun
** Package changed: linux (Ubuntu) => e2fsprogs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1922909
Title:
Ubuntu 18.04 not detection SSD on SSD Samsung PM98
Sorry, providing a couple lines from the apt update history log isn't
enough for anyone to be able to analyze anything.
You can try attaching your full journal logs, and the full apt and dpkg
logs would help as well, but even the logs may not help and more
complete system configuration data may be
You have been subscribed to a public bug:
Hi Team,
Please be note Ubuntu ISO 18.04.5 not detecting the samsung PM981a SSD
drive upon installation
#nvme list
Node SN Model
Namespace Usage Format FW Re
Public bug reported:
Hello !
I have 2 monitors
1) one is 4K
2) another one is FULLHD,
when I installed lubuntu I had 4k monitor work at maximum 4k and another at
fullhd , I want to change that 4k monitor to 2560x1440(2k).
after install nvidia drivers there is no 2560x1440 resolution in
"mon
Didn't get the log message about rfkill after boot this morning.
After update today I have systemd 247.3-3ubuntu3 installed.
--
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/19
Although comment#2 is merged, this issue still needs PA corresponding
(https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290).
Therefore, we will deliver a special alsa-ucm-conf on our oem-archive as
short-term solution and leave it be replaced after this ticket gets the
merge.
Public bug reported:
It looks like /etc/apparmor/severity.db is missing the new capability
CAP_CHECKPOINT_RESTORE.
This causes the following regression test failure:
ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db
make: *** [Makefile:81: check_severity_db] Error 1
This new
** Package changed: systemd (Ubuntu) => sslh (Ubuntu)
--
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/1923406
Title:
sslh 1.18-1 high CPU load -> Fix available
Status in s
This bug was fixed in the package libseccomp - 2.5.1-1ubuntu1~20.04.1
---
libseccomp (2.5.1-1ubuntu1~20.04.1) focal; urgency=medium
* Updated to new upstream 2.5.1 version for updated syscalls support
(LP: #1891810)
- Removed the following patches that are now included in the
For bionic there's a few ADT regressions for libseccomp - I re-ran them,
let's see if they pass 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/1891810
Title:
Backport
@William, thanks, could you share the Debian bug url? I browsed
https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=yes&src=bluez
but I'm not finding it...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu
Public bug reported:
I have ImageMagick set as the default application for opening PDF. I am
trying to change the setting, but it doesn't work.
** Affects: ubuntu
Importance: Undecided
Status: New
** Package changed: xorg (Ubuntu) => ubuntu
--
You received this bug notification b
Public bug reported:
System: Ubuntu 18.04 LTS
Software: sslh v1.18-1
The Problem is that the sslh-daemon causes 100% load after a while.
The bug seems to be reported and fixed in december 2020 at the the ssl-project.
Should be fixed in v1.21b or newer. So please backport/update the
package acco
78 matches
Mail list logo
