Public bug reported:
Description:Ubuntu 22.04 LTS
Release:22.04
xorg:
Installed: 1:7.7+23ubuntu2
Candidate: 1:7.7+23ubuntu2
Version table:
*** 1:7.7+23ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
1. Unco
** Summary changed:
- NetworkManager 1.36.6 orders IPv6 addresses incorrectly
+ NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
ht
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: software-properties (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
** Description changed:
Situation:
- My network has both DHCPv6 and SLAAC for IPv6. From a privacy
+ My network has both DHCPv6 and SLAAC (autoconf) for IPv6. From a privacy
perspective, for readability reasons and for network management
policies, DHCPv6 should *always* be preferred over
** Description changed:
Situation:
My network has both DHCPv6 and SLAAC for IPv6. From a privacy
perspective, for readability reasons and for network management
policies, DHCPv6 should *always* be preferred over SLAAC addresses when
available. And according to RFC 6724, the smaller /1
Public bug reported:
Ubuntu 22.04
logrotate 3.19.0-1ubuntu1.1
Every hour, I receive this wrong message:
Subject:Cron >cd / && run-parts --report
/etc/cron.hourly
/etc/cron.hourly/logrotate:
error: state file /var/lib/logrotate/status is world-readable and thus can be
locked from ot
** Description changed:
- My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
- perspective and readability reasons, DHCPv6 should *always* be preferred
- over SLAAC addresses when available. And according to RFC 6724 the
- smaller /128 scope of the DHCPv6 address should be chosen o
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available. And according to RFC 6724 the
smaller /128 scope of the DHCPv6 address should be chosen o
Speakers are working for me now after installing the BIOS update from
2022-06-02.
https://pcsupport.lenovo.com/de/en/products/laptops-and-netbooks/legion-
series/legion-7-16achg6/downloads/driver-list/component?name=BIOS%2FUEFI
I booted on windows, installed the update and after switching to Linu
Confirmed facing this bug. I managed to use the .desktop file workaround
for Discover, but it does not seem to work for Muon.
--
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/1965
Public bug reported:
I work with Ubuntu 22.04 but the Everest semiconductor Co Ltd ESSX8336\1 sound
card is not recognized. On the web a lot of people have the same problem.
It's an annoying problem. Could you please help us to solve this problem.
I have a Huawei Matebook D15 series Matebook D 15
This bug was fixed in the package wpa - 2:2.10-9ubuntu1
---
wpa (2:2.10-9ubuntu1) kinetic; urgency=medium
* debian/patches/lower_security_level_for_tls_1.patch:
- set the OpenSSL security level to 0 if that is the only option to
continue the TLS negotiation, i.e., when TLS
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Lubuntu has used sddm for all LXQt releases (ie. since Lubuntu 18.10),
and the upgrade from an release that used lightdm/LXDE is unsupported
due to breakage as was warned about in documentation, eg.
https://lubunt
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can
Public bug reported:
Hi,
I have updated several machines from Lubuntu 20.04 to Lubuntu 22.04 with
do-release-update -d
On all but one machine this worked well, but one machine, that formerly worked
without problems, now has no ssh-agent running after login, and the
~/.xsession-errors shows se
This bug was fixed in the package curl - 7.83.1-1ubuntu1
---
curl (7.83.1-1ubuntu1) kinetic; urgency=medium
* Apply upstream patch to fix multi-line header support (LP: #1976619)
-- Olivier Gayot Thu, 02 Jun 2022
13:44:50 +0200
** Changed in: curl (Ubuntu)
Status: Fix Co
Yeah, both the speaker and headphones work fine with correct channel.
And still work after resuming from suspend/hibernate.
Also fine after hotplug events, whatever it is playing or not.
Thanks for your patch a lot!
(In reply to Cameron Berkenpas from comment #627)
> Great!
>
> Some probably s
Great!
Some probably silly questions:
1) Do both speakers work? Do you get left channel sound out of the left
speaker and right channel sound out of the right speaker?
2) After resuming from suspend/hibernate, does your sound still work?
3) What if you insert headphones and remove them? Does so
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
- over SLAAC addresses when available.
+ over SLAAC addresses when available. And according to RFC 6724 the
+ smaller /128 scope o
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
ip6.privacy=
** Tags added: regression-update
--
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/1977619
Title:
NetworkManager 1.36.6 orders IPv6 addresses incorrectly
Status in n
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware. I recommend
performing a back up and then investigating the situation. Measures you
might take include check
Public bug reported:
Hello, I'm a user who installed Kubuntu 22.04 today, and trying to use
software-properties-qt package at Konsole(command line).
When I try to change software sources to the mirror that includes Ubuntu
Ports mirror service, software-properties-qt package change APT Sources
fil
Public bug reported:
package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade:
installed initramfs-tools package post-installation script subprocess
returned error exit status 1
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.7
ProcVersionSignature:
24 matches
Mail list logo
