Upstream seems replaced the comment#7 by
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/596
--
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/1902464
[Expired for initramfs-tools (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: initramfs-tools (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Package changed: ubuntu => alsa-driver (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1965215
Title:
[81FD, Realtek ALC236, Black Mic, Right] The external
** 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/1965219
Title:
gnome lock screen does not permit reentering password
Status in
You have been subscribed to a public bug:
Description:Ubuntu 20.04.4 LTS
Release:20.04
When inserted in the 3.5mm phone jack, the external microphone is not
detected, and thus the audio input doesn't auto-switch from the internal
microphone to the external microphone.
The problem
You have been subscribed to a public bug:
Initially, only the mouse works in the gnome lock screen, without any
way to get a password prompt. It's likely only happening when returning
from suspend with lid open.
It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and
login without
Yes, this remains an issues in ubuntu 20, nearly a fresh install. I'll
try to report what happens, but it's running for over an hour so far.
It's progress bar does slowly move however.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Thanks for the bug report. Next time a freeze happens please:
1. Wait 10 seconds.
2. Reboot.
3. Run:
journalctl -b-1 > prevboot.txt
lspci -k > lspci.txt
4. Attach the resulting text files here.
5. Run:
apport-collect 1965116
6. Look in /var/crash for crash files and if found run:
Ok, I did get my case to work by creating ~/ssl.conf containing:
openssl_conf = openssl_init
[openssl_init]
ssl_conf = ssl_sect
[ssl_sect]
system_default = system_default_sect
[system_default_sect]
Options = UnsafeLegacyRenegotiation
And then did OPENSSL_CONF=~/ssl.conf do-my-command
that
I can't speak for the SRU team, but it's entirely possible that if you
prepare and test a debdiff, and show that this can be fixed, you could
drive an SRU through to completion; see
https://wiki.ubuntu.com/StableReleaseUpdates for more information.
Thanks
--
You received this bug notification
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.
@Jernej Jakob: this is cited as 'released for 1.8.4'. There is a policy
for stable distros, never update the version. I asked for a backport,
did not get one. The 20.04 version is still at 1.8.2 and it does not has
this feature that was introduced after this version. It was released for
groovy,
The following PR should hopefully fix this:
https://github.com/canonical/ubuntu-advantage-desktop-daemon/pull/14
** Changed in: software-properties (Ubuntu)
Assignee: (unassigned) => Robert Ancell (robert-ancell)
** Changed in: software-properties (Ubuntu)
Importance: Undecided => High
Hello bs, or anyone else affected,
Accepted glibc into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/glibc/2.31-0ubuntu9.8
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Matthias, or anyone else affected,
Accepted glibc into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/glibc/2.31-0ubuntu9.8
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: glibc (Ubuntu Hirsute)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1892825
Title:
update-locale not perform correctly sanity
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: shared-mime-info (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shared-mime-info in
Ubuntu.
I tried also adding the following:
[openssl_init]
providers = provider_sect
ssl_conf = ssl_configuration
as I wasn't sure whether the [ssl_configuration] section would otherwise
get used for anything, but that didn't seem to make a difference.
The end of the file is
[ssl_configuration]
client
Public bug reported:
On Focal, in an automated environment (such as a launchpad builder), a
used can do the following workflow:
curl
"https://keyserver.ubuntu.com/pks/lookup?op=get=0x${FINGERPRINT};
--output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc
apt-add-repository "deb
FWIW I'm seeing this with the openconnect-sso
(https://github.com/vlaci/openconnect-sso) package on jammy. I just
tried adding the following to my /etc/ssl/openssl.cfg:
[ssl_configuration]
client = client_tls_config
[client_tls_config]
Options = UnsafeLegacyServerConnect
With no luck :(
--
Public bug reported:
Command `grep ^\s*\$FileCreateMode /etc/rsyslog.conf
/etc/rsyslog.d/*.conf` returns `/etc/rsyslog.conf:$FileCreateMode 0640`,
but logfiles are created with read permission for others.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: rsyslog 8.2001.0-1ubuntu1.1
Why is this marked as "fix released"? It's still broken on Ubuntu 20.04 LTS,
the fix has not been released into it.
At the very least, the behavior does not match what is described in the
sshd_config man page. Nowhere does it mention that Match blocks don't work
inside Include files. Not only
int with jammy 20220316, to a network printer
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: am
5112
Title:
cupsd crashed with SIGSEGV in __strcmp_evex()
Status in cups package in Ubuntu:
In Progress
Bug description:
trying to print with jammy 20220316, to a network printer
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu2
ProcVersionSign
vex()
Status in cups package in Ubuntu:
In Progress
Bug description:
trying to print with jammy 20220316, to a network printer
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.1
ation because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1965112
Title:
cupsd crashed with SIGSEGV in __strcmp_evex()
Status in cups package in Ubuntu:
New
Bug description:
trying to print with jammy 20220316,
New
Bug description:
trying to print with jammy 20220316, to a network printer
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11
*** This bug is a duplicate of bug 1951653 ***
https://bugs.launchpad.net/bugs/1951653
** This bug has been marked a duplicate of bug 1951653
can't use NM for ethernet device on 20.04 LTS because it is 'strictly
unmanaged'
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1664844 ***
https://bugs.launchpad.net/bugs/1664844
** This bug has been marked a duplicate of bug 1664844
No distinction between link-up and link-down interfaces
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
The fix was released with netplan v0.103.
** Changed in: netplan
Status: In Progress => Fix Released
** Changed in: netplan.io (Ubuntu Focal)
Status: New => Fix Released
** Changed in: netplan.io (Ubuntu Hirsute)
Status: New => Fix Released
** Changed in: netplan.io
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
** 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/bugs/1965008
Title:
'Software & Updates' crashes on tab
thanks, the journal has some error, did you edit the .service to add the
-d to the execstart as request? wpa doesn't seem to be in debug mode on
that log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in
Thanks for reporting it upstream!
** Package changed: libxml2 (Ubuntu) => xdg-desktop-portal (Ubuntu)
** Changed in: xdg-desktop-portal (Ubuntu)
Importance: Undecided => High
** Changed in: xdg-desktop-portal (Ubuntu)
Status: New => Triaged
** Bug watch added:
Public bug reported:
The latest bugfix release of the 3.0 branch is out, we should package it
for Jammy.
In the preliminary packaging I've done the test suite fails, i'm trying
to track down the cause ATM.
** Affects: openssl (Ubuntu)
Importance: Undecided
Status: New
** Tags:
Public bug reported:
Currently, it seems that software-properties is incorrectly assuming
that both ESM and Livepatch services can be enabled in a Jammy machine.
Those services are not yet available in Jammy and we are attaching an
image showing that the Desktop message is that we had an error
Moving it over to the netplan.io project, as nplan is deprecated.
I think we actually have an upstream way of matching Type=ether nowadays
(as of systemd v245+), so we should reconsider implementing a fix for
this.
:
cupsd crashed with SIGSEGV in __strcmp_evex()
Status in cups package in Ubuntu:
Incomplete
Bug description:
trying to print with jammy 20220316, to a network printer
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0
(In reply to Darin Miller from comment #563)
> *Ubuntu version:
>
> 1) install kernel build tools:
> (https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel):
>
> * sudo apt install libncurses-dev gawk flex bison openssl libssl-dev dkms
> libelf-dev libudev-dev libpci-dev libiberty-dev autoconf git
>
Thanks for your bug report.
I am reassigning this to the installer, but it seems more likely that
this is a result of user error, given that there have not been any
relevant changes in focal's installer. For user support, please use
askubuntu, discourse, the ubuntu-user mailing lists, or the
This was enabled in Debian's systemd v250.1-2
https://salsa.debian.org/systemd-team/systemd/-/commit/4a93ec2f56969e11c73ef346a342e7e552faae75
We're shipping the more stable systemd v249 in Ubuntu Jammy LTS, and are
already post feature freeze, so we cannot enable new features anymore.
This will
An update: I've noticed that my PE had the button "Global Bypass"
occasionally activated (somehow without my consent), and after
unpressing it the entire chain now works again. But the initial bug is
unfortunately there, that is PE does not get activated on sturtup
properly. So in 22.04 devel, the
No,I can't. I has no account on the gitlab.
--
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/1962093
Title:
network-manager can't connect to pppoe since version
OK, in devel 22.04 the sound restored after an update, though PE does
not actually perform any transformation from the chain... I just hope
that after all it will be fixed in the final release, and will work well
like it worked in 20.04... If not it seems we have to use the flatpak
version.
--
This has been enabled in Debian's systemd v250 via
https://salsa.debian.org/systemd-
team/systemd/-/commit/6b5e99f1d7f63c0c83007de9f98f7745f4a564f8
We're sticking with the more stable systemd v249 for Ubuntu Jammy LTS
and we're already post feature freeze, so we cannot enable those new
features
Public bug reported:
Right after clean install, "archive.ubuntu.com" was missing in
"/etc/apt/sources.list" as summary.
So, apt checked too small amount of servers for "apt update" or "apt install",
and all the fundamental and basic dev packages like libgtk-dev or gnome-builder
were not
Thank you for reporting this. I've forwarded it to the upstream
developers, as I think at very least this new behavior should be
documented in
https://systemd.network/systemd.network.html#DuplicateAddressDetection=
https://github.com/systemd/systemd/issues/22763
** Bug watch added:
Public bug reported:
I use Ubuntu 21.10 with Wayland and nvidia drivers. Sometimes, when
working, the desktop freezes.
Over ssh, I can see in the system logs many of those messages:
> gnome-shell[5615]: Key repeat discarded, Wayland compositor doesn't
seem to be processing events fast enough!
ion:
trying to print with jammy 20220316, to a network printer
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architect
in cups package in Ubuntu:
New
Bug description:
trying to print with jammy 20220316, to a network printer
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
A fix for this has been landed upstream (v250) for HP Omen 15 and
another fix for Omen 17:
https://github.com/systemd/systemd/commit/6f2353a2ce731afc8622a3d44679abc38105cded
https://github.com/systemd/systemd/commit/70920214b6a1c1825a2724793497e6be2ba3c0fc
It might be worth backporting those
** Attachment added: "syslog(success)"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+attachment/5569560/+files/syslog.7z
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
** Attachment added: "syslog(Failed)"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+attachment/5569534/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
It has recently been picked up by Foundations, and we should have the
capacity to start working on this next week.
--
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/1958284
I found the culprit, being a 0 byte "documents" file in the flatpak
database. I filed an issue in the flatpak github.
https://github.com/flatpak/xdg-desktop-
portal/issues/369#issuecomment-1068915444
I still don't know if this relates to libxml2, and if it is worth being
investigated how that
sergiojd: The problem I have reported happens using Packer to create
VirtualBox .ova images of Ubuntu Server guests. As I have said,
everything works OK using the Ubuntu Server 20.04 iso (released in
2020.04), but fails with the 20.04.1, 20.04.2, 20.04.3 or 20.04.4 isos.
I would say that something
I installed wpasupplicant_2.10-2_amd64.deb and libssl1.1_1.1.1m-1_amd64.deb
from debian sid. It works.
I attached the log from journalctl -b 0 with ubuntu's wpasupplicant package.
** Attachment added: "wpa_supplicant.log"
We can do both -- close it now and keep discussing and reopen it later
as required.
** Changed in: mesa (Ubuntu)
Status: New => Fix Released
** No longer affects: kwin (Ubuntu)
** No longer affects: meta-kde (Ubuntu)
--
You received this bug notification because you are a member of
Reverting back to the official repo fixed it. I guess that it was fixed
since I first reported this.
Please keep it open just in case the issue crops up again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
This bug was fixed in the package initramfs-tools - 0.140ubuntu13
---
initramfs-tools (0.140ubuntu13) jammy; urgency=medium
* Lower the compression levels for zstd and lz4 (LP: #1958148)
Following the discussion on the mailing list, we have reached
a conclusion to lower the
** Changed in: gnome-shell (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1962346
Title:
Ubuntu reboots instead of powering off
We would be able to at least tell if the problem is Mesa or KDE if you
could test regular Ubuntu (with GNOME).
--
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/1960403
Title:
If llvmpipe is working, that's just because it avoids using the GPU.
It's a slow workaround.
If going back to Mesa version 21.3.5-1ubuntu1 from Ubuntu reintroduces
freezes then I suggest that needs to be debugged by KDE/Plasma
developers.
** Also affects: kwin (Ubuntu)
Importance: Undecided
It sounds like the main problem is still Mesa.
The i7-640M is a "Gen5" Intel GPU apparently:
https://en.wikipedia.org/wiki/List_of_Intel_graphics_processing_units#Gen5
That means Mesa should select the "i965" Mesa driver for it:
/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
Make sure your build
64 matches
Mail list logo
