This bug was fixed in the package software-properties - 0.99.32
---
software-properties (0.99.32) lunar; urgency=medium
[ Nathan Pratta Teodosio ]
* Disable the Ubuntu Pro UI with an explanation when not connected
(lp: #2004634)
* Catch exceptions to wait (lp: #2003996)
*
This bug was fixed in the package software-properties - 0.99.32
---
software-properties (0.99.32) lunar; urgency=medium
[ Nathan Pratta Teodosio ]
* Disable the Ubuntu Pro UI with an explanation when not connected
(lp: #2004634)
* Catch exceptions to wait (lp: #2003996)
*
This bug was fixed in the package software-properties - 0.99.32
---
software-properties (0.99.32) lunar; urgency=medium
[ Nathan Pratta Teodosio ]
* Disable the Ubuntu Pro UI with an explanation when not connected
(lp: #2004634)
* Catch exceptions to wait (lp: #2003996)
*
Tested on machine with FM350 installed, with oem 6.0.0-1006 kernel,
modem manager 1.20.0-1~ubuntu22.04.1, libmbim-glib4 1.28.0-1~ubuntu20.04
and libqmi-glib5 1.32.0-1~ubuntu0.22.04.1. System can connect to 5g
network.
---
General | path: /org
Thanks for the links Peter. Looking at the upstream patch, it looks
straightforward enough, but can you also provide more detailed steps to
reproduce this issue?
I gather this would involve setting up a 20.04 host and 22.04 clients,
running Backuppc on the latter to pull data from the former. If
** Also affects: rsync (Ubuntu Jammy)
Importance: Undecided
Status: New
** Bug watch added: Debian Bug tracker #969463
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969463
** Also affects: rsync (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969463
Importanc
@Julian Andres Klode:
If I understand pull-lp-source's man page correctly, pull-lp-source is
not at all a substitute for apt-get build-dep. The latter will install
*and update* the relevant source code, so that your dependencies are as
secure as the rest of the repository. The former provides a o
The verification of the Stable Release Update for evince has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
This bug was fixed in the package evince - 43.0-1ubuntu1
---
evince (43.0-1ubuntu1) kinetic; urgency=medium
* debian/apparmor-profile:
- allow access to the libproxy helper pxgsettings which is needed on
some configuration to access remote printers (LP: #1915910)
-- Seba
Hi Bartłomiej, NSS is in the regular mozilla bugzilla at
https://bugzilla.mozilla.org/home. You can file or search for bugs
related to NSS by specifying "NSS" as the Product, e.g.:
https://bugzilla.mozilla.org/buglist.cgi?resolution=---&query_format=advanced&product=NSS&order=Importance&classific
I'm having similar issues. Following what Fabio mentioned, I think I had
a firewall issue but disabling the firewall was not enough, I needed to
restart the wifi after disabling the firewall. I guess that is the
sequence which addresses the problem for Fabio too.
--
You received this bug notifica
All tests succeeded, marking verification done.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.n
Jammy verification (continued), test (d)
d) It's now possible to have SCRAM and gssapi heimdal mechanisms
installed at the same time
Start with SCRAM available on jammy, by installing the gssapi-mit
package:
$ sudo apt install libsasl2-modules-gssapi-mit
...
$ ll /usr/lib/x86_64-linux-gnu/sasl2/
Jammy verification (continued), test (c)
c) A jammy system WITHOUT the SCRAM mechanism available (i.e.,
libsasl2-modules-gssapi-mit is NOT installed), will get SCRAM available
after the upgrade, but without installing any new package.
Starting on jammy with these installed:
$ dpkg -l | grep -E "^
Jammy verification (continued), test (b)
b) On the heels of the (a) test, release upgrade to kinetic
The summary two packages are going to be removed, not related to cyrus-sasl2.
At the end, 13 packages were going to be removed, also not related to
cyrus-sasl2:
13 packages are going to be remove
Jammy verification, test by test. First, (a):
a) SCRAM remains installed
Installed libsasl2-modules-gssapi-mit package from jammy, and confirmed scram
is part of it:
ubuntu@j-sasl-scram:~$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
lrwxrwxrwx 1 root root 18 Oct 19 21:06
/usr/lib/x86_64-lin
Thanks! New changelog looks good, I am uploading it now, with a slight
change to split one of the lines that was long and generating a lintian
error.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs
The detected regression looks like a false-positive caused by another
dependency. The reported error is `/bin/sh: 1: python: not found` which
does not seem to be caused by the changes in libunwind.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whi
Uploaded, thanks!
** Changed in: openssl (Ubuntu)
Status: New => Fix Committed
--
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/2006954
Title:
openssl: merge unstabl
Hi Marc, thanks a lot for taking a look at this. I misunderstood how the
changelog must be constructed.
I believe the Build-Conflicts can just be dropped as the problem with
fakeroot was fixed (LP: #1915250) and sudo doesn't require root to be
built anymore (and the file permissions seem to be cor
Also affects on 22.04.2, been encountering this bug for the 2 years I've
been having my Dell XPS 17.
--
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/1576844
Title:
Touchpad/Tr
Okay. I got some pcaps now. And apparently our apt-cacher-ng proxy
sometimes serves:
- an InRelease
- with a 200 OK
- and a non-zero Content-Length
- BUT, no content, but instead a TCP-FIN.
Under the right circumstances, this causes apt to stall forever.
The right circumstances seem to include:
It looks like you forgot to add the following to the changelog:
- debian/control:
+ Build-Conflicts on fakeroot (<< 1.25.3-1.1ubuntu1)
- debian/sudo[-ldap].manpages: install man/man8/sudo_root.8
- debian/sudo[-ldap].init: delete init scripts, as they are no longer
necessary
** Attachment added: "sudo autopkgtests"
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2007698/+attachment/5648890/+files/autopkgtests.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.l
** 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/2007912
Title:
PCI/internal sound card not detected
Status in alsa-d
You have been subscribed to a public bug:
The system cannot use the built-in mini-jack connections as output devices.
The device is not listed in the available sound devices.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.19.0-3
26 matches
Mail list logo
