@suoko: could you retry with the current version from jammy (22.04)? The
Qt packages have been updated a couple of weeks ago with better OpenSSL
3 support, which hopefully fixes your issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is su
Hi Matt, thanks for taking the time to report this, as well as
investigating the different versions that might be affected.
I just checked, and both Impish and Jammy are affected as well (the
latter using OpenSSL 3.0).
--
You received this bug notification because you are a member of Ubuntu
Touc
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1947588
Title:
Infinite Loop in OpenSSL s_server
Status in openssl package in Ubuntu:
New
Status in openssl source package
** Also affects: openssl (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: openssl (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: openssl (Ubuntu Impish)
Importance: Undecided
Status: New
--
You received this bug notification beca
Disregard the (now deleted) comment regarding Focal, I got mixed up in
my terminals. Focal is affected, but Bionic is not.
I suspect this is caused by our patch that changes the semantics of
security level 2 to also drop support for (D)TLS < 1.2.
** Tags added: rls-ff-incoming rls-jj-incoming
**
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 Impish)
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.laun
To be clear, the root issue is that the server is using an outdated,
insecure protocol that has been deemed so for more than a decade, and
OpenSSL finally decided to disable it by default. The "proper" way to
fix this would be for them to upgrade.
Now, that being said, we live in the real world an
... And while looking for what exactly to suggest upstream, I realized
that GitHub search only prints out the first match in a given file,
which mean I missed the config options part of
https://www.openssl.org/docs/man3.0/man3/SSL_CONF_cmd_value_type.html
(search for UnsafeLegacyServerConnect), whi
any chance you could provide the journal log requested?
--
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/1962541
Title:
PEAP wifi can't connect (ubuntu live/installe
there were some recent fixes around owe on bug #1963906 but that's on a
GNOME session, unsure if that matches your issue?
** Changed in: network-manager (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
I would start by reinstalling libgail-common, restart and see if that
brings the issue back. I also think you can install the pending
upgrades, it shouldn't make a difference here
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lvm2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bug
this file is full log
beacause i dont want to try to upgrade and is not working
** Attachment added: "logfull.log"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1962541/+attachment/5567725/+files/logfull.log
--
You received this bug notification because you are a member of
** Bug watch added: Debian Bug tracker #923345
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923345
** Also affects: evince (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923345
Importance: Unknown
Status: Unknown
--
You received this bug notification because
This bug was fixed in the package expat - 2.4.1-2ubuntu0.3
---
expat (2.4.1-2ubuntu0.3) impish-security; urgency=medium
* SECURITY UPDATE: Stack exhaustion
- debian/patches/CVE-2022-25313.patch: prevent
stack exhaustion in build_model in expat/lib/xmlparse.c.
- debian/
This bug was fixed in the package expat - 2.2.5-3ubuntu0.7
---
expat (2.2.5-3ubuntu0.7) bionic-security; urgency=medium
* SECURITY UPDATE: Stack exhaustion
- debian/patches/CVE-2022-25313.patch: prevent
stack exhaustion in build_model in expat/lib/xmlparse.c.
- debian/
This bug was fixed in the package expat - 2.2.9-1ubuntu0.4
---
expat (2.2.9-1ubuntu0.4) focal-security; urgency=medium
* SECURITY UPDATE: Stack exhaustion
- debian/patches/CVE-2022-25313.patch: prevent
stack exhaustion in build_model in expat/lib/xmlparse.c.
- debian/p
I think we've concluded that we're not going to ship the configuration
file parts in the Impish and Focal uploads, so I'll reject them from the
queue now. The Bionic queue upload is ready now though.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, w
** Changed in: evince (Debian)
Status: Unknown => New
--
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 a hyperlink in a PDF fails to open it
Hello Utkarsh, or anyone else affected,
Accepted keyutils into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/keyutils/1.5.9-9.2ubuntu2.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
Public bug reported:
While mirrors listed on https://launchpad.net/ubuntu/+archivemirrors
support https, this is not reflected in software-properties-gtk ->
Download from -> other dialogue. Example: Charite Berlin supports https,
but only http is available from the "Protocol" dialogue.
Editing /e
I will take a stab at this later today.
Yesterday while searching a bit I may have encountered the reason these
particular packages have a problem. I was doing a search and it may be
that the packages having the problem I am seeing are all qt5 users.
Could there be a problem between qt5 and the l
** Tags removed: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1947588
Title:
Infinite Loop in OpenSSL s_server
Status in openssl package in Ubuntu:
Co
Thanks for the update, Robie.
I'll let you know how our testing goes with this soon.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to keyutils in Ubuntu.
https://bugs.launchpad.net/bugs/1962453
Title:
Apply default TTL to r
Public bug reported:
A customer reported network disconnections on their storage
servers when running 'netplan apply'. The culprit was that
they have link-local addresses configured and the Duplicate
Address Detection (DAD) mechanism was delaying the interfaces
from coming back up.
As a worka
** Changed in: packagekit (Ubuntu)
Status: New => Triaged
--
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/1963904
Title:
/usr/libexec/packagekitd:11:__strcmp_avx
> I think this commit [1] may be related (landed in systemd v249)
yeah, that commit seems to be intentionally forcing ACD on for
statically configured ipv4, i'm not sure quite why, it seems like a
user-configured setting should be honored; but possibly Yu was trying to
default it to on instead of
** Changed in: apport (Ubuntu)
Importance: Undecided => Low
** Changed in: errors
Status: New => Invalid
** Changed in: apport (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: packagekit (Ubuntu)
Status: New => Invalid
--
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 if
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu.
https://bugs.launchpad.net/bugs/1923052
Title:
screen reader does not read ubiquity w
I agree, a user-configured setting should be honored. Another thing to
consider is that according to the Jammy systemd.network man page, the
default should be 'ipv6' so one would expect that to be a global
default, but it gets overridden for link-local IPs due to this commit.
[1] https://manp
** Changed in: openssl (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: openssl (Ubuntu Impish)
Importance: Undecided => Medium
** Changed in: openssl (Ubuntu Focal)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
To
Public bug reported:
I don't know if the error reported is correct. The problem I have is
that the system freezes and becomes unresponsive, both the keyboard and
touchpad are unresponsive. It is not a single error of an isolated
program, but of the system. The only way to get it to work again is t
dropping the update-excuse tag, since this bug has nothing to do with
why the packages are or aren't migrating out of -proposed AFAIK
--
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.ne
oh correction, it does because of the added autopkgtest :)
--
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/1962038
Title:
wrong sysrq value in /usr/lib/sysctl.d/50-default.
How do I reinstall libgail-common? I used dpkg -i with
libgail-3-0_3.24.20-0ubuntu1_amd64.deb with no change in behavior. I
went back to
https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.20-0ubuntu1/+build/19437463
but I don't see a libgail-common file there.
--
You received this bug notificati
I just thought to look in synaptic and I see it there. Should I install
from there, or is there a reason to do so in another manner?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.ne
Public bug reported:
Problematic commit reverted upstream causing incorrect behavior in
Ubuntu Focal.
Discussion: https://github.com/iputils/iputils/issues/320
Fix: https://github.com/iputils/iputils/pull/321
Release: https://github.com/iputils/iputils/releases/tag/20210722
Could this patch be a
** Tags added: fr-2103
** Also affects: packagekit (Ubuntu Jammy)
Importance: High
Status: Triaged
** Tags removed: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs
I have found that the steps in this answer:
https://askubuntu.com/a/1367801
Fixed the problem for me
--
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/1929345
Title:
Pressin
yes, installing from synaptic is fine. The package comes from gtk2
that's why it's not on the gtk3 buildpage
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1962807
Title:
This bug was fixed in the package systemd - 249.10-0ubuntu2
---
systemd (249.10-0ubuntu2) jammy; urgency=medium
* Fix deadlock between pid1 and dbus-daemon (LP: #1871538)
File:
debian/patches/pid1-set-SYSTEMD_NSS_DYNAMIC_BYPASS-1-env-var-for-dbus-da.patch
https://git.launc
Thanks for taking your time to report this issue and help making Ubuntu
better.
Could you please attach the error message you get when running from the
console? I don't see any error message on my 20.04 test system, but
there might be some clue if it is caused by archive settings or
something else
This bug was fixed in the package systemd - 249.10-0ubuntu2
---
systemd (249.10-0ubuntu2) jammy; urgency=medium
* Fix deadlock between pid1 and dbus-daemon (LP: #1871538)
File:
debian/patches/pid1-set-SYSTEMD_NSS_DYNAMIC_BYPASS-1-env-var-for-dbus-da.patch
https://git.launc
Installed libgail-common via synaptic as requested and restarted the
system. The results are not what I expected:
dhdurgee@z560:~/Downloads$ fcl
Gtk-Message: 12:46:26.155: Failed to load module "gail"
** (fcl:2132): WARNING **: 12:46:26.238:
(../atk-adaptor/bridge.c:1018):atk_bridge_adaptor_ini
You have been subscribed to a public bug:
Steps:
1) Go to Settings->Bluetooth
2) Try to pair Honor freebuds 2
Expected result:
Device is succesfully connected
Actual result:
While pairing windows is freezes, then it closes
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+d
** 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/1964502
Title:
Settings->Bluetooth windows freezes while connecting b
the earlier experience of having the segfault not resolved after
removing it suggests that you might need to restart the session for the
change to be active, did you try to logout and log in again?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whi
I used synaptic to install the package and then did a restart of the
system after cleanly closing all running programs. That of course
required me to log back in when the system restarted. Is there more I
should do at this point?
--
You received this bug notification because you are a member of
This bug was fixed in the package procps - 2:3.3.17-6ubuntu2
---
procps (2:3.3.17-6ubuntu2) jammy; urgency=medium
* Add basic autopkgtest to validate sysctl-defaults (LP: #1962038)
-- Lukas Märdian Fri, 25 Feb 2022 12:57:56 +0100
** Changed in: procps (Ubuntu Jammy)
Stat
Public bug reported:
See https://lists.ubuntu.com/archives/kernel-team/2022-March/128565.html
NOTE: This config is enabled in other gcp kernels and in non-gcp
kernels.
** Affects: linux-gcp (Ubuntu)
Importance: Undecided
Assignee: Khaled El Mously (kmously)
Status: New
** Aff
Suddenly googled this bug report. I'm having the same problem with
networkmanager 1.36.2-1, but with ArchLinux
--
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
Public bug reported:
when the pc starts up or comes out of sleep mode the primary screen
remains black. To reactivate it I have to go through screen clone apply
and redo join the screens and apply.
Thanks
Ps: have done several research and attempt, without success, on the
internet including in
Hi Robie,
May we have your comment on this. Since we would like to have this
solution in the latest kernel, need you help to check on this. Thank
you.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https:/
You have been subscribed to a public bug:
Hi, I use Ubuntu 20.04 LTS version in my VivoBook 15_ASUS Laptop X507UF.
I live in a remote area where the only option for Internet is my cell
phones network data. I use this mobile internet via Wi-Fi connection.
The problem is, if I do not start the mobi
Thanks for the bug report.
Next time the problem happens please immediately run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
** Summary changed:
- monitor not recognized displayport
+ [nvidia] One monitor fails to wake after resuming from sleep
** Package changed:
** Package changed: ubuntu => network-manager (Ubuntu)
** Tags removed: bot-comment
** Tags added: network-manager
--
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/19
Thanks for the bug report. Next time the problem happens, please:
1. Wait 10 seconds.
2. Reboot.
3. Run:
journalctl -b-1 > prevboot.txt
4. Attach the resulting text file here.
5. Check for crashes by following:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.cras
Public bug reported:
I found this bug when I upgrade my ubuntu 20.04 LTS using command "apt-
get upgrade"
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libpam-runtime 1.3.1-5ubuntu4.3
ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_
Public bug reported:
Ubuntu 21.10 with wayland windowing system sits on completed file
transfers on and off usb and takes its time realising its finished and
closing the little transfer progress logo.
running an HP elitedesk 800 G1 SFF with 16gb ram, i5 4690 cpu and an HD
4600 onboard graphics ca
Flash drives are usually very slow devices. Next time a transfer has
trouble finishing please open a Terminal window and run:
sync
If the command returns immediately then this is a Nautilus bug. If the
command does not return until the file transfer finishes then this is
either a kernel bug or
** Changed in: zlib (Ubuntu Impish)
Importance: Undecided => High
** Changed in: zlib (Ubuntu Jammy)
Importance: Undecided => High
--
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.n
Can't someone just make a kernel build for ubuntu or some widely used
Linux version and put it on github? There is a lot of patching going on
here but no good documentation on how to do it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is su
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
65 matches
Mail list logo
