[Expired for software-properties (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: software-properties (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: mir (Ubuntu)
Assignee: aalosman (aalosman) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1276322
Title:
[enhancement] Mir lacks relative
The Diagnostics option showed as "Automatic"... and then showed "Never"!
I flipped it to automatic, and now I see this:
systemctl status whoopsie.path
● whoopsie.path - Start whoopsie on modification of the /var/crash directory
Loaded: loaded (/lib/systemd/system/whoopsie.path; enabled;
ls /var/crash/
_opt_Signal_signal-desktop.1000.crash _usr_bin_gnome-shell.1000.crash
_usr_bin_gnome-shell.1000.uploaded _usr_libexec_goa-daemon.1000.upload
_opt_Signal_signal-desktop.1000.upload _usr_bin_gnome-shell.1000.upload
_usr_libexec_goa-daemon.1000.crash
** Changed in: mir (Ubuntu)
Assignee: (unassigned) => aalosman (aalosman)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1276322
Title:
[enhancement] Mir lacks relative
We're seeing the same behavior with Dell Precision 3600 series desktops and HID
Global OMNIKEY 3x21 Smart Card Readers
We did not encounter the issue with 18.04 or 20.04, only in 22.04.
sudo systemctl enable pcscd.socket
does not seem to resolve the issue for us
sudo systemctl start pcscd.service
This bug **is** the tracker bug for the issue we believe was triggered
by libcanberra.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not
Can you cite the bug report on the libcanberra package which relates to
this issue? There are LOTS of them.
FWIW, the only component of the several components of the evolution
suite which EXPLICITLY depends on libcanberra (ldd |grep canberra)
is
This bug was fixed in the package poppler - 0.62.0-2ubuntu2.14
---
poppler (0.62.0-2ubuntu2.14) bionic-security; urgency=medium
* SECURITY REGRESSION: Adding missing install header
- debian/patches/0001-Install-goo-GooCheckedOps.h.patch:
this add goo/GooCheckedOps.h to
Oh, I DO have sound in the speakers, BT high def (A2DP) audio too...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1988658
Title:
boot stops at black screen (blinking
$ lspci | grep -i audio
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
01:00.1 Audio device: NVIDIA Corporation TU116 High Definition Audio Controller
(rev a1)
*** Is there REALLY Realtek audio hardware in here too?
*** or just a partly initialized driver due to the
$ cat /sys/class/sound/hwC0D0/vendor_name
Realtek
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1988658
Title:
boot stops at black screen (blinking cursor in top left
Hmm...
$ cat /sys/class/sound/hwC0D0/chip_name
ALC294
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1988658
Title:
boot stops at black screen (blinking cursor in top
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that there was an error on your system when
trying to update the kernel on your system due to a lack of free space
in your boot partition. Please resolve this situation manually and try
the update again.
Public bug reported:
Feature Request:
When installing a system over the network using live installer
(subiquity), you can use the kernel cmdline option ip= [1] to provide
the network configuration.
In certain situations, it would be ideal to be able to configure a lacp
bond during this process.
** Changed in: apport (Ubuntu Bionic)
Status: Confirmed => Triaged
** Changed in: apport (Ubuntu Focal)
Status: Confirmed => Triaged
** Changed in: apport (Ubuntu Jammy)
Status: Confirmed => Triaged
** Changed in: apport (Ubuntu Bionic)
Importance: Undecided => High
**
** Changed in: initramfs-tools (Ubuntu Hirsute)
Status: Confirmed => Won't Fix
** Changed in: initramfs-tools (Ubuntu Focal)
Status: Confirmed => Triaged
** Changed in: initramfs-tools (Ubuntu Focal)
Importance: Undecided => Medium
--
You received this bug notification because
The failing autopkgtests have been re-run and everything passed.
--
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/1978129
Title:
Incomplete support for DT_RELR relocations
** Tags added: foundations-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1981385
Title:
initrd lacks modules to mount boot image from http boot
The fix for this bug has been awaiting testing feedback in the -proposed
repository for focal for more than 90 days. Please test this fix and
update the bug appropriately with the results. In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed
Can you check in the control panel under "Privacy" -> "Diagnostics"? If
"Send error reports to Canonical" is set to "Never" then the
whoopsie.path service will be disabled.
** Changed in: apport (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
All autopkgtests for the newly accepted openssh (1:8.2p1-4ubuntu0.6) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.44.1-1ubuntu1.1 (arm64, amd64, ppc64el)
Please visit the excuses page listed below and investigate the
Found that I can limit the package install to just:
apt install auditd audispd-plugins -y
with the changes to audit.rules and auditd.conf, and the /etc/default/grub file.
I get random launch failures with the service failure and "no rules".
--
You received this bug notification because you are
--- audio in the output of lshw ---
*-multimedia
description: Audio device
product: TU116 High Definition Audio Controller
vendor: NVIDIA Corporation
physical id: 0.1
bus info: pci@:01:00.1
--- seen in dmesg ---
[5.815777] Bluetooth: hci0: Firmware revision 0.1 build 26 week 11 2020
[5.881465] NET: Registered protocol family 38
[9.328954] wlo1: authenticate with 94:18:65:08:59:ae
[9.338666] wlo1: send auth to 94:18:65:08:59:ae (try 1/3)
[9.382307] wlo1:
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.
--
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/1897932
Title:
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.
--
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/1979952
Title:
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.
--
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/1981042
Title:
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.
--
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/1975667
Title:
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.
--
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/1979951
Title:
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.
--
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/1981622
Title:
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.
--
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/1988078
Title:
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.
--
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/1982462
Title:
** Attachment removed: "packages.txt"
https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1989599/+attachment/5615835/+files/packages.txt
** Attachment added: "packages.txt"
https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1989599/+attachment/5615864/+files/packages.txt
--
You
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.
--
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/1988994
Title:
** Description changed:
- All autopkgtest fail on Ubuntu 22.04 (jammy) and older:
- https://autopkgtest.ubuntu.com/packages/apport
+ [Impact]
+
+ All autopkgtest fail on Ubuntu 22.04 (jammy) and older:
https://autopkgtest.ubuntu.com/packages/apport
+ This leads to not detecting regressions from
Ok, i did find the issue -Thanks Security folks - and I'm issuing a
security regression update.
Thanks.
** Changed in: poppler (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
I am using a Lenovo ThinkPad Yoga 370, running Ubuntu 22.04 LTS.
When plugging in the charger, the current charge status in the top bar and
Settings shows 'Not Charging' for a few minutes and then shows that the system
is charging normally.
When unplugging the charger the
All autopkgtests for the newly accepted sudo (1.9.9-1ubuntu2.1) for jammy have
finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.48.2-0ubuntu1 (amd64)
Please visit the excuses page listed below and investigate the failures,
proceeding
Hi,
Could you please provide with any steps in how to reproduce it?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1989515
Title:
"goo/GooCheckedOps.h" is
** Attachment added: "packages.txt"
https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1989599/+attachment/5615835/+files/packages.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to audit in Ubuntu.
Fix committed upstream:
https://github.com/canonical/apport/commit/bb7cd6f08d16749c501ef893d5056a20a82346fd
** Changed in: apport
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in
** Attachment added: "auditconf.x86_64"
https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1989599/+attachment/5615836/+files/auditconf.x86_64
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to audit in Ubuntu.
Public bug reported:
Description:Ubuntu 20.04.5 LTS
Release:20.04
linux-image-aws 5.15.0.1019.23~20.04.11
auditd 1:2.8.5-2ubuntu6
I am having issues with auditd on Ubuntu 20.04 LTS Ubuntu official AMIs. I
have tested this with published AMIs ami-0123376e204addb71 and
** Attachment added: "auditrules.x86_64"
https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1989599/+attachment/5615834/+files/auditrules.x86_64
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to audit in Ubuntu.
I have verified that systemd-repart is available in jammy-proposed, and
that the upgrade path to kinetic works as expected:
root@jammy:~# apt-cache policy systemd-repart
systemd-repart:
Installed: 249.11-0ubuntu3.6
Candidate: 249.11-0ubuntu3.6
Version table:
*** 249.11-0ubuntu3.6 500
Hello iBug, or anyone else affected,
Accepted openssh into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:8.2p1-4ubuntu0.6 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: poppler (Ubuntu)
Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1989515
Title:
The description of the patch explains why the current behavior is buggy
and not just different in a way users would be relying on the difference
of behavior. It's not that it works differently, it is that it reports
wrong information.
The patch didn't apply directly so I've adapted it and
Proposed fix: https://github.com/canonical/apport/pull/4
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1989371
Title:
test_crash_setuid_unpackaged fails with
I'm not doubting that the revert was correct for upstream. But we have a
different context in a stable release, where users may be relying on
behaviours that upstream are at liberty to change in their main
development branch, but we are not in our stable releases. Further, we
can't just assume
Yeah, I was confused by this at first too. Here's a hint, try "apt-mark
showhold":
$ apt-mark showhold
$
If nothing is printed (as above), then the "issue" PRESUMABLY isn't
local to your system; ergo, the cause is PROBABLY at the server, such as
a phased update. Relax. It will probably
Hello Kangarooo, or anyone else affected,
Accepted sudo into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/sudo/1.9.9-1ubuntu2.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
@Robie, the patch description has details on the change. The github
report also discuss why the patch was broken and not just doing what is
intended and why the revert is right.
I'm not involved in iputils and will not be able to provide more
information that was in there. Note that the revert is
This is definitely a bug that we want to fix in Focal. But is this
particular code change the correct way to do it?
Won't reverting this commit regress the fix that was introduced by the
commit in the first place? I think this needs a proper analysis of the
possible implications for unaffected
I checked that jammy and later indeed has the same commit reverted.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iputils in Ubuntu.
https://bugs.launchpad.net/bugs/1964506
Title:
Ping: checks payloads incorrectly,
Upstream bug: https://github.com/iputils/iputils/pull/67
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iputils in Ubuntu.
https://bugs.launchpad.net/bugs/1551020
Title:
IpUtils Ping can be in wait forever
Status in
** Description changed:
All autopkgtest fail on Ubuntu 22.04 (jammy) and older:
https://autopkgtest.ubuntu.com/packages/apport
Following test cases fail:
* backend_apt_dpkg:
** test_get_dependencies (armhf)
** test_get_source_tree_sandbox (arm64, armhf, ppc64el)
**
** Description changed:
This maybe has to be reassigned to affect 'ddeb-retriever', but the web
form doesn't allow setting it as package for reporting.
'libglib2.0-0' was updated in the bionic-updates repository, but
'libglib2.0-0-dbgsym' was not correspondingly updated in the ddebs
*** Bug 53675 has been marked as a duplicate of this bug. ***
--
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/1971901
Title:
dlltool uses non-unique temp filenames
Public bug reported:
This maybe has to be reassigned to affect 'ddeb-retriever', but the web
form doesn't allow setting it as package for reporting.
'libglib2.0-0' was updated in the bionic-updates repository, but
'libglib2.0-0-dbgsym' was not correspondingly updated in the ddebs
repository:
Proposed fix: https://github.com/canonical/apport/pull/3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1989365
Title:
test_omit_all_processes_except_one is racy and fails
@enr0n and @brian-murray suggested that this change should go through
the feature freeze exception process.
**Description of the proposed changes**
With the change packages systemd-boot and systemd-boot-efi will be first
time built for the riscv64 architecture. No changes will occur for any
@seb128: Vivaldi is the spiritual successor of Opera. Opera _is_
included in /etc/apparmor.d/abstractions/ubuntu-browsers, so Vivaldi
should be as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
Public bug reported:
I'm running Ubuntu 20.04 on my desktop. I SSH into my laptop running
22.04:
desktop$ ssh laptop
laptop$ sudo -sE
laptop#
If I now run most any X11 client applications (e.g. xload, xterm)
using this laptop SSH command line, they correctly open windows on my
Thanks for the information, meanwhile this is resolved by
237-3ubuntu10.56.
--
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/1989433
Title:
Security patch only available
67 matches
Mail list logo
