--- Comment From pp...@de.ibm.com 2022-06-03 08:33 EDT---
I have already run the command do-release-upgrade. At the end of the upgrade I
could see "upgrade completed" but there were errors. Than I rebooted the system.
I attach the sources.list file an the output of the commands.
--- Comment (attachment only) From pp...@de.ibm.com 2022-06-03 08:34
EDT---
** Attachment added: "sources.list file"
https://bugs.launchpad.net/bugs/1977493/+attachment/5594615/+files/sources.list
--
You received this bug notification because you are a member of Ubuntu
Touch
I got a pair of new Precision 7760s, and by comparing their setups I
found that the on the one I hadn't used much yet the updates subscribed
to were "Security and Recommended" where the one I had used more the
updates were set to "Security Only". As I'm sure you are aware (though I
was not) this
Public bug reported:
Same issue as reported before for other versions.
Here 1.187.31
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-firmware 1.187.31
ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-40-generic x86_64
NonfreeKernelModules:
Well, it's a bit difficult to give remote recommendation for a system in this
state.
(Ideally I want to login to it by myself ...)
It would be good to know how many of the installed packages are still
packages from impish, and how many already from jammy.
One, may try to move forward to jammy
If there's any bug in Ubuntu here, it's that the release upgrader didn't
try harder to get the system into a consistent state before offering a
reboot. No bug in pam, which is simply one of the packages to be
upgraded.
libpam-modules refused to be upgraded because there were references to
*** This bug is a duplicate of bug 1958267 ***
https://bugs.launchpad.net/bugs/1958267
Same issue here:
the updated 2:2.10-6ubuntu1 version of wpasupplicant still gives
wpa_supplicant[33522]: SSL: SSL3 alert: write (local SSL3 detected an
error):fatal:internal error
wpa_supplicant[33522]:
#76 works here too
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1958267
Title:
wpa can't connect to servers using TLS 1.1 or older
Status in wpa package in Ubuntu:
Fix
Public bug reported:
spectrum@04397701017:/opt/swSpectrum/bin$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
default connected 1920x1080+0+0 0mm x 0mm
1920x1080 77.0*
Display setup
(In reply to Cameron Berkenpas from comment #429)
> Created attachment 298789 [details]
> linux-legion-sound-0.0.13.patch
>
> auto mute is now properly disabled as per Takashi's suggestion.
>
> This patch is against the latest Linus tree, but applies against 5.14.3 just
> fine.
>
> This patch
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
** Changed in: oem-priority
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1887910
Title:
[bionic]blutoothd segfault when you
** Changed in: kdesu (Ubuntu Jammy)
Status: Confirmed => In Progress
--
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/1965439
Title:
applications can no longer launch
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mawk in Ubuntu.
https://bugs.launchpad.net/bugs/1805115
Title:
problem with (ubuntu/cosmic)mawk /^[[:space:]]*http://archive.ubuntu.com/ubuntu
Since Xenial has reached its end of standard support period, I'm marking
this as Won't Fix.
** Changed in: cyrus-sasl2 (Ubuntu Xenial)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
This issue is now fixed upstream.
https://github.com/util-linux/util-linux/commit/304b4dc4936b115ca33af5325c3b04d0997c1353
https://github.com/util-linux/util-linux/commit/c9671a3cf7738bb81e1cbef2f56485a36c6e7623
--
You received this bug notification because you are a member of Ubuntu
Touch
** Package changed: linux (Ubuntu) => pam (Ubuntu)
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
--
You received this bug notification because you are a
Public bug reported:
After yesterdays upgrade (apt log attached) cupsd has stared to crash
again every other job. It is then restarted and the next job prints
fine.
This situation I recognize from the past. It's been like this for a
while in the past. Back then I didn't know the upgrade that
First of all I assume there was no previous attempt of doing a 'do-
release-upgrade' or even an attempt that was stopped/interrupted, or an
attempt to get the system updated in a different way, for example (in
the abs. not recommended way to) to change all 'impish' entries in
/etc/apt/sources.list
Going to wontfix for bionic since there doesn't seem to be a need for it
at this point
** Changed in: bluez (Ubuntu Bionic)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in
Thanks Olivier, I sponsored the change now
** Changed in: curl (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/1976619
Public bug reported:
I had recently upgraded from Ubuntu 22.04 LTS Jammy Jellyfish To Ubuntu 22.10
Kinetic Kudu (Development Branch) and i found 2 NEW Problems with it...
1) Audio does not work at all
2) Video playback is very laggy and not as smooth as before
When i played a video,The playback
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: snappy-hwe-snaps
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1973835
You have been subscribed to a public bug:
---Problem Description---
Upgrade from Ubuntu 21.10 to 22.4 fails
I run do-release-upgrade and I got a message upgrade completed with
errors. I rebooted the server and it is now in an undefined state
between 21.10 and 22.04. Not all packages have been
** Description changed:
This is a sync request for gettext 0.21-6.
These were the latest Ubuntu changes:
==> debian/changelog <==
gettext (0.21-4ubuntu4) jammy; urgency=medium
- * debian/patches/git-new-libunistring.patch:
- - cherry pick ah upstream change to fix the build
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apport (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apport (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
This even happened to me on Focal (latest update) when reporting the
gthumb CVE I found. I manually uploaded the crash dump, separated the
big apport file and put it up. Maybe a server issue
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
This issue was reported on IRC and we should probably fix it before
installing wireplumber by default so I'm setting the block-proposed tag.
https://i.imgur.com/L5VFZO8.png
wireplumber is apparently too forceful in how it enables PipeWire. Both
Arch Linux and Debian had to
** Changed in: pipewire-media-session (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1977564
Title:
wireplumber conflicts
ufw does not support rule removal. For a particular project (a task queue on a
cloud adhoc HPC cluster), I have had the occasion to test it in a relatively
massive parallel rate (20 concurrent uses). I have experienced:
- nice behaviour when adding rules,
- bad behaviour when removing rules.
I
I have declared also the bug in Ansible collection repo, however this is
clearly a UFW bug:
https://github.com/ansible-collections/community.general/issues/4769
** Bug watch added: github.com/ansible-collections/community.general/issues
#4769
Public bug reported:
This is a sync request for gettext 0.21-6.
These were the latest Ubuntu changes:
==> debian/changelog <==
gettext (0.21-4ubuntu4) jammy; urgency=medium
* debian/patches/git-new-libunistring.patch:
- cherry pick ah upstream change to fix the build with the new
** 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
Looking at the changelog of 1.38.0:
* Fix bug setting priority for IP addresses.
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-38/NEWS
So it looks like Ubuntu just introduced that bug by upgrading to 1.36.6.
Please either backport it from 1.38.0 or revert to 1.36.4.
Thanks for the testing and feedback, I've uploaded the fix in the SRU
reviews queue now
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1958267
Title:
wpa can't connect to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: vim (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
** Tags added: jammy
** 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
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619
--
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/1974428
Title:
Update to the current 1.36
No worry, thanks for following up. I will still check with our oem team
to make sure updates are enabled by default on those images
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
All of a sudden SLAAC addresses are preferred over DHCPv6 addresses,
which should not be happening. Setting ip6.privacy=0 no longer helps,
nor does setting net.ipv6.conf.all.use_tempaddr = 0 with sysctl.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
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=0 for the
Do you mean after this update? Could you do a new report and include
details on the step to trigger the issue?
--
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/1974428
** 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
Comparing the output of `ip -6 a`, you can see that the dynamic
addresses are no longer at the top of the list, where they should be.
Before (network-manager 1.36.4):
2: eno0: mtu 1500 state UP qlen 1000
inet6 2a10:3781:::bd0/128 scope global dynamic noprefixroute
valid_lft
I guess these commits are relevant:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/c631aa48f034ade2b5cb97ccc4462d56d80174e7
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/257221d1986b56cbb2e329fcc74a2daca145b7aa
Bottom line: addresses are now being
The problem still persist in Ubuntu 22.04. Should I file a new issue?
** Attachment added: "ubuntu_22.04_missing_glyphs."
https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1967009/+attachment/5594565/+files/ubuntu_22.04..png
--
You received this bug notification because you are a
Public bug reported:
There is a bug in systemd 249, where one can't pull any images. This was
fixed in version 250, and never got backported. (FIX:
https://github.com/systemd/systemd/commit/c40d82abf7b23803aa7394a7a7e24c40c32af851)
Hopefully this can be addressed.
ProblemType: Bug
Public bug reported:
[ Impact ]
* MRE for the latest stable OpenLDAP 2.5.x release, 2.5.12.
This update includes bugfixes only following the SRU policy exception
defined at https://wiki.ubuntu.com/StableReleaseUpdates/OpenLDAPUpdates.
[ Major Changes ]
* See the list of bugs fixed in this
** Changed in: openldap (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1977627
Title:
New upstream microrelease 2.5.12
Status in
50 matches
Mail list logo
