This bug was fixed in the package libidn - 1.38-4ubuntu1
---
libidn (1.38-4ubuntu1) jammy; urgency=medium
* debian/patches/initialise_langinfo_codeset.patch:
- Fix handling of non-ASCII characters (LP: #1971715)
-- Christopher James Halse Rogers Tue, 01 Nov 2022
16:40:24 +01
The verification of the Stable Release Update for libidn has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
This bug was fixed in the package ubuntu-meta - 1.481.1
---
ubuntu-meta (1.481.1) jammy; urgency=medium
* Refreshed dependencies
* Added firefox to desktop-minimal-recommends [amd64 arm64 armhf],
desktop-recommends [amd64 arm64 armhf] as it provides dpkg alternatives
for x
The verification of the Stable Release Update for ubuntu-meta has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encount
** Information type changed from Public to Public Security
--
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/2025695
Title:
systemd-resolved: manually dhclient ethx，dns names
** No longer affects: command-not-found (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/2025965
Title:
aptsources deb822 Section constructor fails on valid .sou
Public bug reported:
I have Logitech wireless keyboard and wireless mouse, coonnected to the same
Unifying receiver.
battery level of these devices is reported correctly, but both are listed in
power settings as a keyboard, making me a bit confusing, which device is run
out of power, when I ge
Public bug reported:
The new version displays that warning which makes the gtk autopkgtest
red
Upstream https://gitlab.freedesktop.org/mesa/mesa/-/issues/9199
Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039922
** Affects: mesa
Importance: Unknown
Status: Unknown
**
Note this is still an issue, we just marked the given test case as
ignored on s390x going forward.
The https://launchpad.net/ubuntu/+source/iptables/1.8.7-1ubuntu6 upload:
* disabled 0002-ebtables-save-restore_0 on x86
* disabled 0009-needless-bitwise_0 on s390x
See the diff at
http://launchpadli
Thank you for your bug report. Which mouse model do you have? It looks
similar to https://gitlab.freedesktop.org/upower/upower/-/issues/215
** Bug watch added: gitlab.freedesktop.org/upower/upower/-/issues #215
https://gitlab.freedesktop.org/upower/upower/-/issues/215
** Changed in: upower (Ub
Thank you, Lucas. I split that merge commit.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu.
https://bugs.launchpad.net/bugs/2025666
Title:
Please merge 1.225-1 into mantic
Status in netcat-openbs
Do we need evince to be reuploaded for jammy there since the previous
upload was rejected by Steve?
--
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/1794064
Title:
Clicking
** Summary changed:
- System program problem
+ kde frontend crashed
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net
On 04/07/23 08:23, Gunnar Hjalmarsson wrote:
> My first upload to the PPA proved to not be complete. Corrected now.
> (Wait for the builds to finish and the packages to be published before
> updating).
I have installed the new proposed version, but I have a regression with
deadkeys: pressing altgr
** Merge proposal linked:
https://code.launchpad.net/~danilogondolfo/ubuntu/+source/sudo/+git/sudo/+merge/446052
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/2025655
Titl
I made a comment in the Debian bug above expressing interest in working
on this if Simon gives his approval, since it is more critical as the
package is synced with Debian at the moment.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subsc
I'll unsubscribe ~ubuntu-sponsors for now. Please re-subscribe once the
merge is ready again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/2025363
Title:
Merge con
Hi Pedro,
Can you please try this with the latest version of systemd? We have
249.11-0ubuntu3.9 which has a patch for a similar sounding bug (I don't
*think* it's the same thing, but just to be sure).
Assuming that does not resolve the issue, can you please provide debug-
level logs from systemd-
dhclient is not part of the systemd package, so I will re-assign this
bug.
** Package changed: systemd (Ubuntu) => isc-dhcp (Ubuntu)
** Summary changed:
- systemd-resolved: manually dhclient ethx，dns nameserver in the
/etc/resolve.conf will be written duplicate
+ manually dhclient ethx，dns name
** Changed in: mesa
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2025982
Title:
Warning 'failed to get driver name for fd 0' fails gtk tests
device models are listed in the log above:
model: K800 (this is keyboard)
model: Performance MX (mouse)
their product codes are 046D:2010 and 046D:101A
it really seems similar to the issue #215, but that fix didn't help me.
I cloned git version of upower, compiled and installed.
now I see:
U
** Changed in: mesa (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2025982
Title:
Warning 'failed to get driver name for fd 0' fails gt
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
** Bug watch added: github.com/systemd/systemd/issues #13432
https://github.com/systemd/systemd/issues/13432
** Also affects: systemd via
https://github.com/systemd/systemd/issues/13432
Importance: Unknown
Status: Unk
** Changed in: systemd
Status: Unknown => 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/1997542
Title:
DNS fails with "Using degraded feature set" in logs unti
Thanks. Uploaded netcat-openbsd 1.225-1ubuntu1.
** Changed in: netcat-openbsd (Ubuntu)
Assignee: (unassigned) => Benjamin Drung (bdrung)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu.
https://b
** Changed in: netcat-openbsd (Ubuntu)
Assignee: Benjamin Drung (bdrung) => (unassigned)
** Changed in: netcat-openbsd (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: netcat-openbsd (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you
Is this actually causing you problems somewhere? Or do you just disagree
with this concept? Please see
https://www.freedesktop.org/software/systemd/man/systemd.unit.html#String%20Escaping%20for%20Inclusion%20in%20Unit%20Names
for an explanation of this naming.
** Changed in: systemd (Ubuntu)
@Federico: Thanks for testing and reporting that observation!
I can't reproduce it (on mantic), though. Dead keys work as expected for
me, also with the keyboard layout you mentioned.
Are you sure that the issue is related to the proposed ibus version?
Does the issue go away if you downgrade to t
** Description changed:
- [placeholder]
+
+ PPA: https://launchpad.net/~danilogondolfo/+archive/ubuntu/sudo2
+
+ Autopkgtests https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-
+ danilogondolfo-sudo2/mantic/s390x/s/sudo/20230705_144943_c8ec0@/log.gz
+
+ This merge includes a workaround
** Changed in: keepalived (Ubuntu Xenial)
Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro)
** Changed in: keepalived (Ubuntu Bionic)
Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro)
** No longer affects: keepalived (Ubuntu Xenial)
** Changed in: keepalived (Ubuntu Focal)
** Also affects: ubuntu-pro
Importance: Undecided
Status: New
** Changed in: ubuntu-pro
Assignee: (unassigned) => Tom Moyer (tom-tom)
** Also affects: ubuntu-pro/18.04
Importance: Undecided
Assignee: Tom Moyer (tom-tom)
Status: New
** Changed in: ubuntu-pro/18.04
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
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/2023401
Title:
[Dell XPS 17 9700] Upon shutdown, shutdown proc
** Also affects: mesa-amber (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2019212
Title:
Backport packages for 22.04.3 H
probably it's due to the single path for both devices?..
udevadm info /dev/input/event3
P:
/devices/pci:00/:00:14.0/usb3/3-6/3-6:1.2/0003:046D:C52B.0004/0003:046D:2010.0007/input/input18/event3
M: event3
R: 3
U: input
D: c 13:67
N: input/event3
L: 0
S: input/by-id/usb-Logitech_USB_Receiv
** Description changed:
[Impact]
The graphics HWE stack from lunar needs to be backported to jammy for 22.04.3
mesa
- new major release (23.0.4)
+ mesa-amber
+ - a minor update from upstream mesa (21.3.7 -> 21.3.9), though there were no
+ changes to the classic dri drivers
+ - dro
I tested this on Lunar and saw the same behavior.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
could you check if the backport from lunar in jammy-proposed fixes this?
** Also affects: mesa (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: mesa (Ubuntu Jammy)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
I see that this looks like a kernel problem. One of my computers was
without sound in the last 5 months, so I had to use a small screen
laptop to watch movies or listen audio, but I lost patience in the
process. Is there any GUI centric Linux distro, which fixes this
problem?
--
You received this
--- Comment From wint...@de.ibm.com 2023-07-05 12:00 EDT---
Is this a new testcase, or did it work before?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1974056
Ti
** Description changed:
- I have Logitech wireless keyboard and wireless mouse, coonnected to the same
Unifying receiver.
- battery level of these devices is reported correctly, but both are listed in
power settings as a keyboard, making me a bit confusing, which device is run
out of power, wh
also FYI: solaar detects my mouse properly
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/2025980
Title:
can not configure keyboard and mouse separately
Status in upower p
Public bug reported:
The upstream version 3.137 should be merged into mantic. The current
version is 3.134ubuntu1.
Note: this is a tracking bug
** Affects: adduser (Ubuntu)
Importance: Undecided
Assignee: Mateus Rodrigues de Morais (mateus-morais)
Status: In Progress
** Chang
Thanks, Danilo.
I am removing ubuntu-sponsors to avoid duplication in the sponsoring
queue. Your MP is already being tracked there.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bu
Hi Cyrus, thanks for the patch!
As per the SRU guidelines in
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template, regarding
the "[ Where problems could occur ]" section,
> * This must '''never''' be "None" or "Low", or entirely an argument as to why
your upload is low risk.
Describ
** Description changed:
The upstream version 3.137 should be merged into mantic. The current
version is 3.134ubuntu1.
Note: this is a tracking bug
+
+ PPA for review: https://launchpad.net/~mateus-
+ morais/+archive/ubuntu/adduser-merge-lp2026199
--
You received this bug notification b
** Description changed:
The upstream version 3.137 should be merged into mantic. The current
version is 3.134ubuntu1.
+ * PPA for review:
https://launchpad.net/~mateus-morais/+archive/ubuntu/adduser-merge-lp2026199
+ * Git rebase of Ubuntu delta available at:
https://code.launchpad.net/~m
Is this still an issue for you? If so, what release are you running now?
We would also need some logs to investigate further. This sounds like a
kernel issue rather than systemd, but it would be helpful if you
provided some logs. Specifically:
1. Enable debug logging in systemd-logind:
$ mkdir -p
Re-assigning since it sounds like this is not a systemd issue.
** Package changed: systemd (Ubuntu) => linux (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/1988023
Looking at a recent build log, this seems to be set already in newer
releases https://launchpadlibrarian.net/656923986/buildlog_ubuntu-lunar-
amd64.systemd_252.5-2ubuntu3_BUILDING.txt.gz. Notably, it does not
appear to be set in Jammy. Is this needed there?
** Changed in: systemd (Ubuntu)
S
Can you share the generated networkd files from /run/systemd/network?
Also, 99-default.link is not the correct place to change these values -
you should set MACAddressPolicy in specific link files, e.g.
10-eth0.link. I am not sure off the top of my head of netplan.io has a
config option that maps t
The patch for this is indeed present in Jammy and newer. I don't
currently see a strong enough reason to SRU this to Focal, but if you or
someone else thinks it's important, feel free to explain here.
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug not
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
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/1961418
Title:
snap failed to run with '/usr/bin/snap wait sy
Sorry this was not looked at sooner. Is this still using the latest
systemd on your re-installed system?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
udev restricts this sort of thing for security reasons, so this is
working as expected.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://
** Changed in: mesa (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2025982
Title:
Warning 'failed to get driver name for
I also got this error when I tried to upgrade. Upon trying 'apt
reinstall linux-firmware' I get the following:
# apt reinstall linux-firmware
The following packages will be REINSTALLED:
linux-firmware
0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 3 not
upgraded.
Need t
Public bug reported:
To support the use of AppArmor policies that specify features like
userns, add the new 4.0 ABI from upstream
https://gitlab.com/apparmor/apparmor/-/merge_requests/1061.
Note this should not be enabled by default (as the existing AppArmor
profiles have not been updated to acco
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2026230
Title:
error when setting up after upgrading
Status in n
** Tags removed: need-amd64-retrace
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2026230
Title:
error when setting up after upgrading
Status in network-manager
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
--
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/1922414
Title:
ssh-agent fails to start (has_opti
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lightdm (Ubuntu)
Status: New => Confirmed
--
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/
You mention snap update in the title. What specific snap are you
referring to, Chromium, Cups or Snapd? The output of "snap changes"
could be useful. If you roll it back with "snap revert ",
does it work again?
> Launching chrome from menu shortcut that is managed by the snap works
> and it u
** Changed in: mesa-amber (Ubuntu Jammy)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2019212
Title:
Backport packages for 22.04.3 HWE sta
Could you refer to some documentation on this restriction (especially -
what actions are allowed/restricted)?
In addition - what was the reason of DROP behaviour? All known to me
system restrictions behave as REJECT - i.e. restricted action gets an
immediate result instead on being stuck until the
Hi Athos,
Thanks for the review.
Please pause this SRU. There are currently issues that need clarification from
Intel. I will reopen it and update the "[ Where problems could occur ]" section
once the issue is clarified. Thank you.
** Changed in: oem-priority
Status: In Progress => Inval
65 matches
Mail list logo
