Interesting, when fixing the script I relied on the mode the USB ports
are in (which they should always be in source mode for a desktop machine
but apparently each vendor does things differently).
The USB port being in sink mode means that it is configured to power the
system and not power periphe
The workaround mentioned by Monica and Andreas is viable. A possible
implementation can be found in Apache Impala at
https://github.com/apache/impala/commit/8dd935a98f1ee758bd8f2a03f9bd778a8a2f433e
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whi
> when the new changelog entry contains an old bug number reference
[...] we remove the ":".
Interesting, cause lintian complains about that 😅 (or at least it does
with debian bug tags, i haven't verified that it also does for lp bug
tags)
--
You received this bug notification because you are a
I got this issue in Ubuntu Jammy Arm architecture. But this workaround
not work.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2089071
Title:
tarfile.py regression: "Re
Hi Jay,
On second thought, I'll include the fix in Plucky to proceed with the
SRUs as fast as possible. Later, when the fix arrives in Debian, we can
manually resync dnsmasq. This way, we unlock this.
I hope this helps you and the Ironic community. Sorry for the comings
and goings.
--
You recei
I got the same issue with Ubuntu Jammy arm.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2089071
Title:
tarfile.py regression: "ReadError: invalid header"
Status in p
*** This bug is a duplicate of bug 2089071 ***
https://bugs.launchpad.net/bugs/2089071
>This is a working version of /usr/lib/python2.7/tarfile.py
I got the same issue with Ubuntu Jammy arm architecture, does this
workaround work?
--
You received this bug notification because you are a memb
** Changed in: dnsmasq (Ubuntu Jammy)
Status: Incomplete => Confirmed
** Also affects: dnsmasq (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: dnsmasq (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: dnsmasq (Ubuntu Plucky)
Impo
I can reproduce the issue, this patch
https://pastebin.canonical.com/p/J5jzyFkbcT/ can resolve the issue, we're
working on releasing the fixed version asap. I will update this thread once it
is done
thank you for the patience
** Changed in: python2.7 (Ubuntu Focal)
Assignee: (unassigned) =
This log shows the tests-in-lxd test passing now:
https://autopkgtest.ubuntu.com/results/autopkgtest-
jammy/jammy/amd64/s/systemd/20241120_155239_e1b7a@/log.gz.
The autopkgtest run overall fails due an existing failure in networkd-
test.py, but that is unrelated. Unfortunately that test comes and
Thank you for the report @gordon-lack.
Could you run the systemd-ac-power command with SYSTEMD_LOG_LEVEL=debug?
$ SYSTEMD_LOG_LEVEL=debug systemd-ac-power
And share the logs printed on screen.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packag
Public bug reported:
After installing the latest Python2.7 (2.7.18-13ubuntu1.3) there is a
problem installing packages with PIP.
```
pip install cryptography
DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020.
Please upgrade your Python as Python 2.7 is no longer maintained
** Description changed:
- After installing the latest Python2.7 (2.7.18-13ubuntu1.3) there is a
- problem installing packages with PIP.
+ After installing the latest Python2.7 (2.7.18-13ubuntu1.3) there is a problem
installing packages with PIP.
+ The new release has changes "Remove backtracking
** Changed in: openssh (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2088207
Title:
cloud-init enables ssh password auth
Adding a jammy task for systemd because I see the error there now. At
the very least I want to just skip the test in jammy to get a green
baseline again.
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Jammy)
Importance: Undeci
*** This bug is a duplicate of bug 2080216 ***
https://bugs.launchpad.net/bugs/2080216
Thanks for this bug report. This is effectively a duplicate of bug
2080216 (same root cause, same fix).
The patch for this is currently available in noble-proposed, and should
hopefully land in noble-update
Invert the logic?
Perhaps just look for any /sys/class/power_supply/BAT?/current_now that is
non-zero?
If any found, it's running on battery.
Else it must be on a mains-supply.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: pam (Ubuntu Noble)
Status: In Progress => Fix Released
** Also affects: pam (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: pam (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: pam (Ubuntu Plucky)
Importance: Unde
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: python2.7 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchp
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: python2.7 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchp
I've cherry picked the patch to Plucky now which is a pre-require for
SRUing, once it migrates to the release pocket and I will continue with
uploading to Oracular and Noble
** Changed in: policykit-1 (Ubuntu)
Importance: Undecided => Low
** Changed in: policykit-1 (Ubuntu)
Status: New
** Changed in: openssh (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2089049
Title:
systemd-socket-activation test can be fla
Public bug reported:
While testing an application I'm working on, I noticed it fails with
Ubuntu's version of GStreamer but not with Debian's.
My application tries to use decodebin to decode some JPEGs. It needs
this bug in jpegparse fixing:
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/m
** Patch added: "cups_2.4.10-2ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2089041/+attachment/5839145/+files/cups_2.4.10-2ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubu
[ganuc]: SYSTEMD_LOG_LEVEL=debug systemd-ac-power
port0: The USB type-C port is in power sink mode.
port1: The USB type-C port is in power sink mode.
ucsi-source-psy-USBC000:001: The USB type-C device has at least one port in
power sink mode.
ucsi-source-psy-USBC000:001: The power supply is curren
The attachment "cups_2.4.10-2ubuntu1.debdiff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff. If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch" tag
All of my Intel NUcs report the type-C port being in sink mode.
None of them can be powered by a USB-C port.
Even plugging in an external drive leaves the system reporting them all
in sink mode.
According to https://www.ti.com/lit/wp/slyy109b/slyy109b.pdf that is correct.
A sink is a port that wi
This bug was fixed in the package python2.7 - 2.7.18-1~20.04.6
---
python2.7 (2.7.18-1~20.04.6) focal-security; urgency=medium
* SECURITY REGRESSION: regression for CVE-2024-6232
- d/p/fix-regression-lp2089071.patch: fix incomplete update for
CVE-2024-6232 (LP: #2089071)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
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.n
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launc
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cloud-init (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.la
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: netplan.io (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.la
Uploaded plucky:
Uploading to ubuntu (via ftp to upload.ubuntu.com):
Uploading bash_5.2.32-1ubuntu2.dsc: done.
Uploading bash_5.2.32-1ubuntu2.debian.tar.xz: done.
Uploading bash_5.2.32-1ubuntu2_source.buildinfo: done.
Uploading bash_5.2.32-1ubuntu2_source.changes: done.
Successfully uploa
** Package changed: ubuntu => xorg (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/2089319
Title:
System is unresponsive after wakeup from suspend
Status in xorg pac
** Package changed: ubuntu => pulseaudio (Ubuntu)
--
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/2089301
Title:
After last system update reboots no mor audio device
St
*** This bug is a duplicate of bug 2089071 ***
https://bugs.launchpad.net/bugs/2089071
it is also fixed in jammy
https://ubuntu.com/security/notices/USN-7015-6
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in
** Also affects: python2.7 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: python2.7 (Ubuntu Jammy)
Status: New => Fix Released
** Changed in: python2.7 (Ubuntu Jammy)
Assignee: (unassigned) => Nishit Majithia (0xnishit)
--
You received this bug notificatio
*** This bug is a duplicate of bug 2089071 ***
https://bugs.launchpad.net/bugs/2089071
fix has been released: https://ubuntu.com/security/notices/USN-7015-6
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-defaults
Public bug reported:
Don't know what this is but it happened during upgrade. Maybe i386 and
AMD64 package conflicts if both installed?
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: libgdk-pixbuf-2.0-0:i386 2.42.10+dfsg-3ubuntu3.1
ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19
** Description changed:
- [ Impact ]
+ [Impact]
Programs relying on the builtin printf function of bash stop working
correctly when trying to format numbers with %f.
- [ Test Plan ]
+ [Test Plan]
- Run the following command, which currently returns "-nan" while it should
return 52.12
*** This bug is a duplicate of bug 2089071 ***
https://bugs.launchpad.net/bugs/2089071
I think the bug #2089071 addressed to Ubuntu focal. While we also have
the bug in Jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
This bug was fixed in the package python2.7 - 2.7.18-13ubuntu1.4
---
python2.7 (2.7.18-13ubuntu1.4) jammy-security; urgency=medium
* SECURITY REGRESSION: regression for CVE-2024-6232
- d/p/fix-regression-lp2089071.patch: fix incomplete update for
CVE-2024-6232 (LP: #208907
You have been subscribed to a public bug:
After resuming my PC from suspend it displays either cursor on a black
screen or glitched image of my desktop. Mouse is not responding and
system needs hardware reboot. The issue is probably connected with
NVIDIA drivers, see attached kernel log (nvidiabug
You have been subscribed to a public bug:
Hello
Yesterday 20.11.2024 I got 2 new update from the "Software Updater". The
first one messed up the Wifi device - of course the second one somehow
fixed it...
After that the audio devices worked until next day (21.11.2024) I was
booted. No audio devic
Public bug reported:
I have a VPS upgraded to Ubuntu 22.04 with a rather peculiar network
setup. My /etc/netplan/90-vz-ens3.yaml is
network:
ethernets:
ens3:
addresses:
- 80.209.x.y/32
- 10.209.x.y/8
- 2a02:7b40:x:y::1/128
dhcp4
This bug was fixed in the package openssh - 1:9.9p1-3ubuntu2
---
openssh (1:9.9p1-3ubuntu2) plucky; urgency=medium
* document /etc/ssh/sshd_config.d/*.conf better in sshd_config
(LP: #2088207)
- d/p/debian-config.patch: expand comment about configuration options
and pr
This bug was fixed in the package openssh - 1:9.9p1-3ubuntu2
---
openssh (1:9.9p1-3ubuntu2) plucky; urgency=medium
* document /etc/ssh/sshd_config.d/*.conf better in sshd_config
(LP: #2088207)
- d/p/debian-config.patch: expand comment about configuration options
and pr
*** This bug is a duplicate of bug 2089071 ***
https://bugs.launchpad.net/bugs/2089071
** This bug has been marked a duplicate of bug 2089071
tarfile.py regression: "ReadError: invalid header"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Changed in: ubuntu-keyring (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Tags removed: rls-pp-incoming
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyri
Also, can you all try to restore socket activation, and see if the
problem persists? You can restore socket activation by running:
# This removes the symlink to mask the generator, if needed.
$ rm -f /etc/systemd/system-generators/sshd-socket-generator
$ systemctl daemon-reload
$ systemctl disable
*** This bug is a duplicate of bug 2089071 ***
https://bugs.launchpad.net/bugs/2089071
** This bug has been marked a duplicate of bug 2089071
tarfile.py regression: "ReadError: invalid header"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
I will make sure to update the on_ac_power script to fulfill such
scenarios similar to systemd ;)
I am just waiting for feedback from @racb first before working on it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powermgmt
From the definition of the TI documentation page 3:
- A sink is a port that when attached consumes power from VBUS and a
sink is most often a device. A sink could include USB peripherals such
as a USB powered light or fan.
- A source is a port that when attached provides power over VBUS. Common
s
** Changed in: colord-gtk
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to colord in Ubuntu.
https://bugs.launchpad.net/bugs/2088294
Title:
colord-sane prevents connection to USB scanner
S
I don't see anything fixed.
The service colord, or more precisely colord-sane, should never send commands
to the scanner that lead to the cancellation of USB communication. If
necessary, there needs to be a blacklist of devices that fail due to such
commands.
An average Ubuntu user has no knowl
The version shipped with 24.04 did not have this problem.
So a work around, if you are live booting off USB (as I was), is to use a 24.04
image for this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https:/
Public bug reported:
The issue was
[reported](https://gitlab.gnome.org/GNOME/glib/-/issues/3516) in the
glib repo. It was found that the fix had already been implemented, so
I'm asking for a backport of the fix from
https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3714 (and by
extension,
https
Chris, Kevin, John, or anyone else affected:
Is it possible that you changed your sshd_config without actually
reloading and restarting ssh.socket, a while (hours, days, etc.) before
the upgrade occurred? I am wondering if it's possible that the
configuration was already broken by a local change,
58 matches
Mail list logo
