Public bug reported:
in the setting,when i set a refresh rate>60Hz, there will be a black
screen for about half a minute and the refresh rate is automatically
reset to 60Hz.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu
Onuh and David - Please share the output from the following commands:
$ apt-cache policy systemd
$ systemctl list-dependencies systemd-pstore.service
$ systemctl list-dependencies --reverse modprobe@mtdpstore.service
$ systemd-analyze unit-files systemd-pstore.service
--
You received this bug
@mwhudson yes, I am working on the debdiffs and once ready I'll attach
them here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lsb in Ubuntu.
https://bugs.launchpad.net/bugs/1761341
Title:
lsb_release crashed with
This bug was fixed in the package vim - 2:8.1.2269-1ubuntu5.9
---
vim (2:8.1.2269-1ubuntu5.9) focal-security; urgency=medium
* No-change rebuild to republish missing architecture binaries in the
security pocket (LP: #1989973)
-- Nishit Majithia Mon, 19 Sep 2022
10:29:57
Reverified for 1.6.17 as per #23
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
** Changed in: apport (Ubuntu Focal)
Status: Fix Committed => Confirmed
--
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/1867204
Title:
** No longer affects: google-chrome-beta (Ubuntu)
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
** Description changed:
[Impact]
Oops pages show wrong time window in JournalErrors. For example, I just
experienced a crash at:
Feb 28 17:31:12
And the JournalErrors entries are:
Feb 28 17:31:30 - Feb 28 17:31:41
So don't relate to the crash.
[Test Plan]
Tested and verified. Note that there is no original TEST CASE, but the
original issue is clearly reproducible. Used the following TEST CASE to
verify:
1. Installed 22.04 in WSL2 (for performance reasons until everything is updated)
2. sudo apt update && sudo apt upgrade -y
3. Installed my
I cannot verify that.
BROWSER=chromium sensible-browser a &
BROWSER=chromium sensible-browser b &
gives me two tabs in one Chromium window.
Since the report is old, I'm marking it as invalid, but please bump it
if still reproducible for you.
** Also affects: sensible-utils (Ubuntu)
** Description changed:
+ [Impact]
+
The Ubuntu Error Tracker has been receiving reports about a problem regarding
apport. This problem was most recently seen with package version
2.20.11-0ubuntu19, the problem page at
** Description changed:
[Impact]
Apport will write an empty core dump file inside of containers.
[Test plan]
Run following testcase script inside a LXC container:
```
rm -f /var/lib/apport/coredump/*
ulimit -c 100
sleep 86400 &
killall -3 sleep
```
Apport
** Description changed:
[Impact]
Apport will fail for processes with dump mode 2 inside of containers.
[Test plan]
Run following testcase script inside a LXC container:
```
#!/bin/sh
sudo rm -rf /var/crash/* /var/log/apport.log
sudo -u mail sh -c "ping 127.0.0.1 >
** Description changed:
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
** Description changed:
[Impact]
All autopkgtest fail on Ubuntu 22.04 (jammy) and older:
https://autopkgtest.ubuntu.com/packages/apport
This leads to not detecting regressions from security updates.
[Test Plan]
Check that the autopkgtest succeed all architectures (except for
Public bug reported:
In kinetic, systemd-resolved now Recommends: libnss-resolve, pulling it
into the ubuntu-minimal seed.
In the past we briefly had libnss-resolve seeded (between xenial and
bionic LTSes but not in any LTS) but it was removed because:
- it was redundant; /etc/resolv.conf was
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.
(I've opened LP:#1990216 to request that the fix for upstream "OpenSSL 3
cannot decrypt data encrypted with OpenSSL 1.1 with blowfish in OFB or
CFB modes #18359" be backported to libssl3 in Jammy.)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
[Expired for python2.7 (Ubuntu) because there has been no activity for
60 days.]
** Changed in: python2.7 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
There is a regression introduced in the 2.72.3 update so we're going to
prepare 2.72.4 for Jammy when it's released.
https://gitlab.gnome.org/GNOME/glib/-/issues/2687
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
** Tags
On Fri, Aug 05, 2022 at 00:35:32 -, Don wrote:
> It appears the issue is resolved in libssl3 3.0.4-1ubuntu1 from kinetic
> (in addition to enabling the legacy providers)
I installed a Kinetic test environment, and confirmed that I was able to
connect to my Xenial tinc (1.0.26-1) instance
On Wed, May 18, 2022 at 15:36:30 -, Nathan Stratton Treadway wrote:
> On Wed, May 18, 2022 at 13:37:46 -, Simon Chopin wrote:
> > Could you give more details about what happens when using the legacy
> > providers?
>
> The short version is that by enabling the legacy provider and setting
>
Nick
#apt-cache policy systemd
systemd:
Installed: 249.11-0ubuntu3.6
Candidate: 249.11-0ubuntu3.6
Version table:
*** 249.11-0ubuntu3.6 500
500 http://ci.archive.ubuntu.com/ubuntu jammy-proposed/main amd64
Packages
100 /var/lib/dpkg/status
249.11-0ubuntu3.4 500
PipeWire is not supported in 22.04, but it will be supported in 22.10.
Do you still experience this bug without PipeWire in 22.04?
** Tags added: jammy
** Package changed: bluez (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
** Tags added: a2dp
--
You received
Thanks for the bug report.
This appears to be either a hardware problem or a bug in the Nvidia
driver. I think most likely it's due to insufficient HDMI cable
bandwidth. Please ensure you are using an HDMI 2.1 certified cable
capable of at least 40 Gbit/s. An HDMI 2.0 cable will not be good
Public bug reported:
OpenSSL upstream implemented a fix for their issue #18359 "OpenSSL 3 cannot
decrypt data encrypted with OpenSSL 1.1 with blowfish in OFB or CFB modes"
https://github.com/openssl/openssl/issues/18359
as of libssl3 3.0.4 (and thus it is included in recent libssl3 versions
Thanks for the bug report. I can't yet see anything wrong with the
machine. Can you describe the problem in more detail, maybe with a
video?
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are
Sponsored for kinetic-proposed. Please make sure systemd migrates into
the release pocket.
** Changed in: systemd (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: systemd (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member
Public bug reported:
The doc-check test fails on RISC-V because it is a very slow
architecture: fix this by increasing the timeout on this specific test.
** Affects: json-glib (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
As this is indeed an FFe from previous cycles, I'll close it down as
Invalid.
** Changed in: base-files (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
The package built successfully here:
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13962373/+listing-
archive-extra
** Attachment added: "debdiff"
https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1990113/+attachment/5616956/+files/debdiff
--
You received this
31 matches
Mail list logo
