I've tested 0.96.24.32.20 on 18.04, activating ubuntu pro through the
magic workflow, detachig and activating again using the manual token
one, it works as expected, marked as verified on B
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal
** Tags added: ve
** No longer affects: pam (Ubuntu)
--
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/1977493
Title:
Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam-
modul
** Summary changed:
- re-add s390x vectorized crc32 support to zlib in lunar
+ [23.04] re-add s390x vectorized crc32 support to zlib in lunar
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Tou
└─$ sudo apt --fix-broken install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
libpam-modules
The following packages will be upgraded:
libpam-modules
1 upgrad
** Also affects: pam (Ubuntu)
Importance: Undecided
Status: New
--
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/1977493
Title:
Upgrade from Ubuntu 21.10 to 22.04 fail
# journalctl -b 0 --grep eno1 | cut -c22-
kernel: igb :02:00.0 eno1: renamed from eth1
systemd-networkd[763]: eno1: Link UP
kernel: igb :02:00.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex,
Flow Control: RX
systemd-networkd[763]: eno1: Gained carrier
kernel: IPv6: ADDRCONF(NE
Launchpad has imported 30 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1941170.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://he
Sounds like a mirror issue.
** Changed in: python3-defaults (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2003644
Title:
Hello Sebastien, or anyone else affected,
Accepted software-properties into bionic-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/software-properties/0.96.24.32.20
in a few hours, and then in the -proposed repository.
Please help us by testing this n
** Changed in: software-properties (Ubuntu)
Status: Fix Released => Fix Committed
** Tags added: verification-needed verification-needed-kinetic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ub
This bug was fixed in the package sysvinit - 3.05-7ubuntu2
---
sysvinit (3.05-7ubuntu2) lunar; urgency=medium
* d/rules: fix installation of 50-ubuntu-logging when building on Ubuntu
(LP: #2002789)
-- Olivier Gayot Fri, 13 Jan 2023
11:33:36 +0100
** Changed in: sysvinit (Ub
This bug was fixed in the package sysvinit - 3.05-7ubuntu2
---
sysvinit (3.05-7ubuntu2) lunar; urgency=medium
* d/rules: fix installation of 50-ubuntu-logging when building on Ubuntu
(LP: #2002789)
-- Olivier Gayot Fri, 13 Jan 2023
11:33:36 +0100
** Changed in: sysvinit (Ub
This bug was fixed in the package zlib - 1:1.2.13.dfsg-1ubuntu4
---
zlib (1:1.2.13.dfsg-1ubuntu4) lunar; urgency=medium
* Add d/p/1390.patch to not update strm.adler for raw streams on s390x
(DFLTCC), otherwise libxml2 gets broken on s390x. LP: #2002511
-- Frank Heimes Wed,
This bug was fixed in the package zlib - 1:1.2.13.dfsg-1ubuntu4
---
zlib (1:1.2.13.dfsg-1ubuntu4) lunar; urgency=medium
* Add d/p/1390.patch to not update strm.adler for raw streams on s390x
(DFLTCC), otherwise libxml2 gets broken on s390x. LP: #2002511
-- Frank Heimes Wed,
Are there any errors in your journal about the config? Check journalctl
-b 0 --grep eno1 for starters. Also just to double check, you are
running the latest version of systemd in jammy, right? It should be
249.11-0ubuntu3.6.
--
You received this bug notification because you are a member of Ubuntu
Thomas and Marc, thanks for the guidance and time spent here. :)
I'll look into the SRU process.
--
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/2003903
Title:
[BPO] opens
I've discussed this with mapreri who is another person on the
backporters team.
Given the API/ABI changes that happen during OpenSSL microreleases that
break packages integrations AND that this will add a security delta
(-backports doesn't receive Security Team support so if they change and
patch
Minor OpenSSL releases have historically introduced a whole lot of
behaviour and API changes that required fixing dozens of other packages
in the archive. I don't recommend putting 3.0.5 in backports.
What I suggest is to actually SRU the 3-4 commits that fix
SSL_OP_LEGACY_SERVER_CONNECT to the ve
Mark, are you asking this to be backported in -backports or in -updates
and -security? This is one of the packages that if we do this in
-backports any security patches applied by the Security team for OpenSSL
in -security and -updates would be ignored with the higher version of
this in -backports
OpenSSL is one of those tricky things out there I would like to get a
Security insight for before we do any kind of backporting of it.
There's other things this could impact, backports or not.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
It shows
# resolvectl mdns
Global: yes
Link 2 (enp1s0): no
Link 3 (eno1): no
Link 4 (lan): no
Link 5 (finnland): no
Link 6 (docker0): no
Link 8 (veth21cf34c5): no
In other words: No.
--
You received this bug notification because you are a member of
Public bug reported:
Humbly requesting backporting OpenSSL 3.0.5-2ubuntu2 from kinetic to
jammy.
[Impact]
>From the OpenSSL 3.0 migration guide:
(https://www.openssl.org/docs/man3.0/man7/migration_guide.html)
"Secure renegotiation is now required by default for TLS connections
Support for RFC
Can we reopen this and potentially backport OpenSSL 3.0.5 from kinetic
to jammy?
The "UnsafeLegacyServerConnect" option was mentioned above in #3.
Unfortunately, that option was documented but not implemented in the
3.0.2 OpenSSL release available in the jammy repos. (See
https://github.com/openss
The option doesn't literally get appended to the original file, but when
the settings are applied it will use the drop-in conf as well. What does
resolvectl mdns show? The rest of your output looks expected (networkctl
status won't mention the use of the drop-in config). I have tested this
on 22.04
** Merge proposal linked:
https://code.launchpad.net/~danilogondolfo/ubuntu/+source/libcap2/+git/libcap2/+merge/436344
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcap2 in Ubuntu.
https://bugs.launchpad.net/bugs/2003
** Summary changed:
- Pleae merge wpa 2.10-10 from Debian
+ Please merge wpa 2.10-10 from Debian
--
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/2003889
Title:
Please merge wp
Cross-reference, among others:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1988299
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1355026
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1360556
--
You received this bug notification because y
Hey Simon! Thanks for your quick response.
Apparently this changelog bug has already been released in the ubuntu1
version[1], sorry I didn't notice it.
Yes let me forward that to Debian, thanks for the reminder.
[1]:
http://launchpadlibrarian.net/604422811/wpa_2%3A2.10-9_2%3A2.10-9ubuntu1.diff.g
PPD file from 18.04. The MD5 does not match the other one so it is
definitely different somehow. Note that the name is nearly identical but
has an extra underscore at the end for some reason.
Also there are two print queues for this printer on the old machine. I
didn't try the other one. It's PPD
Error log from 18.04.
The command I ran was:
lp -d HP_LaserJet_100_colorMFP_M175nw_61F41D_ -o print-scaling=none
170x230.pdf
I also previously tried it without the print-scaling option (not
logged), and result was the same. Very close to the correct size both
times.
** Attachment added: "error
More cases where the same linker flags caused issues
https://bugs.launchpad.net/ubuntu/+source/openblas/+bug/1860601
https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1898006
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
The bionic upload failed to include a recent fix and failed
verification, I uploaded 0.96.24.32.20 to address the problem now
--
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.launchpa
Hi Nathan!
I have no problem with the patch, given the author. That being said, it
would be useful to send this delta up to Debian if at all possible.
Please consider it. :)
Also, it's best not to modify changelog entries that exist in Debian.
I'm dropping this before uploading:
wpa (2:2.10-9)
Note: when testing this package with autopkgtest (or sbuild) locally,
you need to remove the .git directory (if there is one) or the build
will fail. One of the make files will detect the directory exists and
set the environment variable DYNAMIC to no. Because of that, static
binaries will be gener
I'm currently away from this particular network for some time, I'm
currently jumping between different countries.
If this just merges these settings into the systemd file generated by
netplan without the need of netplan to be able to deal with mdns, this
should do the job.
But I wasn't aware that
Public bug reported:
Ubuntu will include -Wl,-Bsymbolic-functions in the build flags by
default. This option seems to break libcap2.
One of the autopkgtests that is supposed to prevent an exploitation
instance using capabilities fails:
https://autopkgtest.ubuntu.com/results/autopkgtest-
lunar/lun
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: orc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to orc in Ubuntu.
https://bugs.launchpad.net/bugs/
Thanks. Please attach the PPD and error_log from that 18.04 computer.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1998917
Title:
Everything prints approximately 2% too sma
You can use a drop-in configuration to achieve this:
$ cat /etc/systemd/network/10-netplan-eth0.network.d/mdns.conf
[Match]
Name=eth0
[Network]
MulticastDNS=yes
This will basically append the MulticastDNS option to the existing
netplan-generated network configuration. Does that solve your probl
** Patch added: "resulting debdiff between debian and ubuntu"
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/2003889/+attachment/5643439/+files/10-10--10-10ubuntu1.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to w
** Patch added: "resulting debdiff between current and proposed ubuntu"
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/2003889/+attachment/5643440/+files/10-9ubuntu1--10-10ubuntu1.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
I built it successfully in Lunar.
** Affects: wpa (Ubuntu)
Importance: Wishlist
Assignee: Nathan Teodosio (nteodosio)
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Also I just tried printing the test document on another computer which
still has Ubuntu 18.04 installed. The output rectangle was undersized by
less than 1mm, which seems okay. I can attach the ppd file and error log
from there if it would help.
--
You received this bug notification because you a
** Summary changed:
- Merge Debian unstable's 0.24.1-2
+ Merge Debian unstable's p11-kit 0.24.1-2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to p11-kit in Ubuntu.
https://bugs.launchpad.net/bugs/2003548
Title:
Merge Debi
### VERIFICATION DONE JAMMY ###
sudo apt-get update
sudo apt install qemu-kvm libvirt-clients libvirt-daemon-system virtinst
bridge-utils -y
sudo systemctl enable libvirtd
sudo systemctl status libvirtd
wget https://releases.ubuntu.com/jammy/ubuntu-22.04.1-live-server-
amd64.iso
sudo chown ub
Note that both of the print commands failed to print anything at all,
but the testipp printer does know that my printer is low on toner. Also
I tried deleting the testipp printer and recreating it but still
nothing.
--
You received this bug notification because you are a member of Ubuntu
Touch se
ppd file
** Attachment added: "testipp.ppd"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+attachment/5643436/+files/testipp.ppd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.l
error log
** Attachment added: "error_log"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+attachment/5643437/+files/error_log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.laun
I've tested 0.99.9.10 on 20.04, activating ubuntu pro through the magic
workflow, detachig and activating again using the manual token one, it
works as expected, marked as verified on F
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
I've tested 0.99.22.5 on 22.04, activating ubuntu pro through the magic
workflow, detachig and activating again using the manual token one, it
works as expected, marked as verified on J
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug no
### VERIFICATION DONE KINETIC ###
sudo apt-get update
sudo apt install qemu-kvm libvirt-clients libvirt-daemon-system virtinst
bridge-utils -y
sudo systemctl enable libvirtd
sudo systemctl status libvirtd
wget https://releases.ubuntu.com/kinetic/ubuntu-22.10-live-server-
amd64.iso
virsh list
I think the "Failed to connect system bus: No such file or directory"
stderr output rather comes from networkctl [1] than from "netplan-dbus"
(Netplan's output would be "... connect TO system bus..."). netplan-dbus
is not involved at all AFAICS, as cloud-init is calling into the
"netplan apply" CLI
** Changed in: six (Ubuntu)
Milestone: later => ubuntu-22.11
** Changed in: six (Ubuntu)
Milestone: ubuntu-22.11 => kinetic-updates
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to six in Ubuntu.
https://bugs.launchpad
A new Debian version for bridge-utils is available. There is also a new
upstream release but it's not yet packaged by Debian.
bridge-utils (1.7-2) unstable; urgency=medium
* Add BRIDGE_DISABLE_LINKLOCAL_IPV6_ALSO_PHYS to /etc/default/bridge-utils
to stop disabling IPv6 on physical interfac
Right, I understand why it would be needed in a ping. But since the DNS
server config in systemd-resolved applies to a specific link, the scope
ID is implied.
As far as your desktop vs server systems, maybe it's the difference
between the interfaces available on each system? If you only have one
n
** Description changed:
Scheduled-For: ubuntu-22.12
- Upstream: tbd
- Debian: 1.7-1
+ Upstream: 1.7.1
+ Debian: 1.7-2
Ubuntu: 1.7-1ubuntu3
-
-
### New Debian Changes ###
- bridge-utils (1.7-1) unstable; urgency=medium
+ bridge-utils (1.7-2) unstable; urgency=medium
- *
** Package changed: ubuntu => nss (Ubuntu)
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/2003845
Title:
updating NSS on 18.04
Status in nss package in
You have been subscribed to a public bug:
Ubuntu 18.04 uses older version of NSS (version 3.35) by which the
latest root certificates distributed by NSS are not trusted in Ubuntu
18.04. Hence, please update it to latest version of NSS. For example,
Mozilla Firefox uses version 3.86 of NSS in Ubunt
We are suspecting issues in the ppc64el toolchain. The problem is only
reproducible on Ubuntu ppc, and not on other distributions. The
backtrace show some borken pointers that can't be explained. The
upstream issue has all the details. None of us speak ppc assembly so we
can't really check the bina
** Tags added: ppc64el reverse-proxy-bugzilla
** Changed in: ubuntu-power-systems
Importance: Undecided => Medium
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => bugproxy (bugproxy)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: 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/1992178
Title:
autopkgtest: upstream tests
This annoying bug rears its ugly head since I upgraded my own and my
wifes computer to Ubuntu 22.04. This does not happen on my 18.04 laptop
or 20.04 workbox.
When using the Save As dialog, focus switches to the filter/search field
in the dialog when we start typing a name for the file. The focus
I think it's better to ship slightly wrong documentation in the wrong
place than to ship the right documentation in a language users don't
understand, so that's why they don#t get updated in stable releases.
I do not think the apt.conf manual page is a good idea in the first
place. These options b
As David wrote, the behavior here is correct. linux-lowlatency is a
binary package provided by linux-meta-lowlatency, for which you are
requesting the source code.
** Changed in: apt (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
T
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: python3-defaults (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https:
Thanks for the reply. Julian.
Let's assume that the problem is indeed latency/dropped packets/whatever
on our side. IMO, an (occasionally) broken network should not cause apt-
get to hang indefinitely. Do you think it should?
Also, it doesn't address that the behaviour seems recent. We have not
o
Patches are welcome but unfortunately there isn't much we can do
otherwise, this highly depends on network specifics like latency and
mtus and is never reliably reproducible.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt
Public bug reported:
Hi!
Yesterday I spotted several machines of ours where a period `apt-get
update` was stalled. The `http` children were hanging in `WaitFd`
(waiting for parent instructions/queue). The parent was looping in
`AcquireUpdate` every 500ms.
We have a cronjob that runs every few h
** Description changed:
tzdata 2021b says in NEWS: "Merge more location-based Zones whose
timestamps agree since 1970, as pre-1970 timestamps are out of scope.
This is part of a process that has been ongoing since 2013. This does
not affect post-1970 timestamps, and timezone historians wh
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: python3-defaults (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https:
I'm on Ubuntu 22.04 LTS. I always need to provide the interface
specification when using link-local IPv6-addresses, e.g. a simple 'ping
fe80::2a0:57ff:fe24' doesn't work but 'ping fe80::2a0:57ff:fe24%2' does
the trick. I couldn't figure out why this is required on my desktop
Ubuntu system. In contr
71 matches
Mail list logo