** Also affects: tzdata (Ubuntu Lunar)
Importance: Critical
Status: New
--
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/1995209
Title:
tzdata 2022f release
Status
All autopkgtests for the newly accepted apt (2.5.3ubuntu0.1) for kinetic have
finished running.
The following regressions have been reported in tests triggered by the package:
sbuild/0.83.1ubuntu1 (ppc64el, arm64, s390x, amd64)
Please visit the excuses page listed below and investigate the fail
Same behavior with an Entroware laptop on 5.15.0-52-generic (both
touchpad and internal keyboard, function keys work)
Hard to tell who's the culprit among the kernel, libusb, udev and gdm
One weird thing in the context of resuming : The Xorg.log generated by
gdm shows:
(II) UnloadModule: "libi
All autopkgtests for the newly accepted openssh (1:9.0p1-1ubuntu7.1) for
kinetic have finished running.
The following regressions have been reported in tests triggered by the package:
dropbear/2022.82-4 (armhf)
gvfs/1.50.2-2 (amd64, arm64)
sbuild/0.83.1ubuntu1 (s390x, amd64, arm64, ppc64el)
piupa
All autopkgtests for the newly accepted openssh (1:9.0p1-1ubuntu7.1) for
kinetic have finished running.
The following regressions have been reported in tests triggered by the package:
dropbear/2022.82-4 (armhf)
gvfs/1.50.2-2 (amd64, arm64)
sbuild/0.83.1ubuntu1 (s390x, amd64, arm64, ppc64el)
piupa
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: s-tui (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-psutil in Ubuntu.
https://bugs.launchp
Hello Julian, or anyone else affected,
Accepted apt into kinetic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.5.3ubuntu0.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubu
Hello msaxl, or anyone else affected,
Accepted openssh into kinetic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/openssh/1:9.0p1-1ubuntu7.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
Hello Nick, or anyone else affected,
Accepted openssh into kinetic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/openssh/1:9.0p1-1ubuntu7.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
Personally, I'd like to see this implemented so that we get crash
reports from more systems so I've tagged it foundations-triage-discuss
in the hopes it'll move to foundations-todo.
** Tags added: foundations-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
I think there should also be an informational message about how to
report the crash(es) as is done with messages in the motd. Example:
1 device has a firmware upgrade available.
Run `fwupdmgr get-upgrades` for more information.
0 updates can be applied immediately.
New release '22.04.1 LTS' ava
Public bug reported:
To make users more aware of existing crashes that should/could be
reported, please mention the number of crashes in the motd (if there are
any).
** Affects: apport (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are
** Changed in: ubuntu-settings (Ubuntu)
Status: Confirmed => Invalid
** Changed in: ubuntu-settings (Ubuntu Jammy)
Status: New => Invalid
** Changed in: ubuntu-settings (Ubuntu Kinetic)
Status: Confirmed => Invalid
** Changed in: pulseaudio (Ubuntu Jammy)
Status: New
Thanks for the reproducer, Maximilian.
I added this to the server team backlog so someone can work on this one
soon.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1995260
** Changed in: dnsmasq (Ubuntu Focal)
Status: New => Triaged
** Tags added: bitesize server-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1995260
Title:
dnsm
Folded into the LP #1990379 uploads to Jammy, Kinetic and Lunar.
** Also affects: zlib (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: zlib (Ubuntu Kinetic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
See https://github.com/canonical/cloud-init/pull/1034 and
https://github.com/canonical/cloud-init/pull/1153
** Changed in: cloud-init
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to a
Uploaded to Lunar, Kinetic, Jammy and Focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1990379
Title:
[UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC
** Tags removed: foundations-triage-discuss
--
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/1992979
Title:
kinetic ppc64le reporting Failed to send WATCHDOG=1 notification
Still a problem on jammy, and removing switch-on-connect does fix things
there.
The result of that change is that plugging in a new (never seen before)
USB device does *not* automatically switch to it, but once the device
has been selected as the output, it will subsequently be automatically
selec
*** This bug is a duplicate of bug 1877194 ***
https://bugs.launchpad.net/bugs/1877194
This sounds like a duplicate of LP: #1877194 -- a workaround is
available in that report (see comment 2)
** This bug has been marked a duplicate of bug 1877194
switch-on-connect mistakes startup for USB
Public bug reported:
System sound output setting always defaults to headphones instead of
hdmi at startup and login and must be reset every time. No headphones
are connected; only hdmi from pi 4 to TV and from TV to sound system via
hdmi-arc.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package:
22 matches
Mail list logo
