Tested with Upstream ModemManager, libmbim and libqmi. The WWAN function can be
turned on through gnome-control-center, and 5G function works correctly. The
upstream version get with "git rev-parse --short HEAD" listed as below:
ModemManager: eebdbc45
libmbim: add668b
libqmi: fa6c7a97
--
You
[Expired for apport (Ubuntu) because there has been no activity for 60
days.]
** Changed in: apport (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.
** Also affects: libmbim
Importance: Undecided
Status: New
** No longer affects: libmbim
** Also affects: libmbim
Importance: Undecided
Status: New
** Project changed: libmbim => libmbim (Ubuntu)
** Also affects: libqmi
Importance: Undecided
Status: New
** Project
** Tags added: oem-priority originate-from-1962525 somerville
** Changed in: oem-priority
Importance: Undecided => Critical
** Changed in: oem-priority
Assignee: (unassigned) => Dirk Su (dirksu)
** Changed in: oem-priority
Status: New => Confirmed
--
You received this bug notifi
Thanks for the bug report. I think we need proper debug symbols to get a
more accurate stack trace. So please just follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
2. If step 1 failed then look
You may need "nfit" module in the initrd too.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1981385
Title:
initrd lacks modules to mount boot image from http boot
** Merge proposal linked:
https://code.launchpad.net/~sergiodj/ubuntu/+source/openldap/+git/openldap/+merge/427967
--
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/1983618
YC is in the process of doing an SRU for a bunch of other bugs in fwupd
and the fix should come in that same SRU I expect.
** Changed in: fwupd (Ubuntu Jammy)
Assignee: (unassigned) => Yosu (yc)
** Changed in: fwupd (Ubuntu Jammy)
Assignee: Yosu (yc) => Yuan-Chen Cheng (ycheng-twn)
--
Deleted the apt task instead so comments don't go apt subscribers for
all eternity.
** No longer affects: apt (Ubuntu)
** No longer affects: apt (Ubuntu Focal)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
h
I think Eric has a good point. Why this fix is not ported back to Jammy?
Jammy is a LTS Version so this service won't work for the next two years
if the fix gets not back ported for all who stick to LTS for whatever
reason.
This is then from my point of view also a security issue, since if this se
** Also affects: apt (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: containerd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: containerd (Ubuntu Focal)
Importance: Undecided => Low
** Changed in: containerd (Ubuntu Focal)
Status:
Thanks for taking the time to report this bug and trying to make Ubuntu
better.
This seems to be a real issue, in the kubernetes documentation they tell
users to set this variable to true:
https://kubernetes.io/docs/setup/production-environment/container-
runtimes/#containerd-systemd
We are plan
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1820584
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
Good point: since this is the first bug I have ever actively pursued,
this is one of possibly many avenues I should follow.
> On 9 Aug 2022, at 19:30, Thorsten Glaser <1954...@bugs.launchpad.net> wrote:
>
> Have you considered informing klibc upstream? (Granted, save for hpa
> that’s basically t
Have you considered informing klibc upstream? (Granted, save for hpa
that’s basically the Debian maintainers, but they don’t necessarily get
Launchpad bugreports either.)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc i
** Changed in: systemd (Debian)
Status: Incomplete => Fix Released
--
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/1892798
Title:
systemd package missing resolvconf(
I encountered this crash after a fresh install of Ubuntu 22.04 LTS and
reported it to the Ubuntu Error Tracker. After doing so I was able to
find the following crash bucket with tens of thousands of incidents:
https://errors.ubuntu.com/bucket/?id=/usr/bin/seahorse%3Aseahorse%3A%20glib-
watch.c%3A1
This might actually be an issue/change in systemd-resolved between Focal
and Jammy.
On Focal the search domain is appended even to FQDNs.
On Jammy the search domain is only appended to single-label hostnames
(hostnames containing no dots), to make them FQDNs.
Would you mind sharing your output o
** Package changed: tracker (Ubuntu) => tracker-miners (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1983859
Title:
tracker-extract crashes with SIGSYS when upgr
This bug was fixed in the package qtbase-opensource-src - 5.15.4+dfsg-5
---
qtbase-opensource-src (5.15.4+dfsg-5) unstable; urgency=medium
* Add a patch to update signature of SSL_CTX_set_options for OpenSSL 3
(LP: #1981807). Thanks Michael Saxl!
-- Dmitry Shachnev Sun, 07 A
Hi Nick,
I cannot longer reproduce this. This was about 1 year ago in a VPS in
OVH that we no longer have.
--
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/1930482
Title:
n
Public bug reported:
If a printer preferrably prints through ipps, Cups will store the
printers (self signed) certificate in /etc/cups/ssl/
However, if this certificate becomes outdated or invalid, or if it
changes, it will *not be removed* and Cups only complains that the
"backend returned statu
*** This bug is a duplicate of bug 1976233 ***
https://bugs.launchpad.net/bugs/1976233
** This bug has been marked a duplicate of bug 1976233
"File has unexpected size" error on Focal ddebs repository
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
I will test the work-around, but I won’t get round to it before the end
of the week.
> On 9 Aug 2022, at 13:55, Juerg Haefliger <1954...@bugs.launchpad.net> wrote:
>
> Please do test the work-around. If indeed NFSv4 solves your overlayfs
> problem then that would be another reason for fixing nfs
Thanks for reporting the bug and providing an easy step to reproduce.
I could kind-of reproduce this behavior in a Ubuntu 20.04 (focal) VM:
Run "ubuntu-bug gnome-terminal" and then click directly on abort. The
windows froze for several seconds (but not mintues) until it closes. On
Ubuntu 22.04 it
** Attachment added: "xorg.1 file from crashed session"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1984067/+attachment/5607529/+files/Xorg.1.log.old
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Public bug reported:
All logs should be added automatically but the central issue is:
Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE)
Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Backtrace:
Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 0:
Please do test the work-around. If indeed NFSv4 solves your overlayfs
problem then that would be another reason for fixing nfsmount.
We can carry Ubuntu specific fixes if for some reason Debian doesn't
want them but the preferred way is obviously to fix it in Debian so that
it tickles down natural
** Changed in: gdk-pixbuf (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu.
https://bugs.launchpad.net/bugs/1982898
Title:
CVE-2021-46829: Buffer overw
Thanks Juerg, you’ve been very helpful.
Presumably there is no quick fix for this because of the klibc/glibc
thing, so it’s an architectural rather than a programming issue. And it
needs to be fixed in Debian rather than in Ubuntu.
I’d offer to help but I arrived here after drilling down from a
c
You should probably report it to Debian: https://bugs.debian.org/cgi-
bin/pkgreport.cgi?repeatmerged=no&src=zeromq3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zeromq3 in Ubuntu.
https://bugs.launchpad.net/bugs/1975383
Ti
** No longer affects: linux-raspi (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1977764
Title:
kernel modules "zstd" and "z3fold" missing.
Status in Ubu
I tried to produce a usable backtrace by copying the crash file back to
a VM that were in the state before the upgrade, but the backtrace there
has GDB warnings: Section `.reg-xstate/$number' in core file too small.
I assume that the crash happens when already some package were updated.
What I saw
Hello Erich!
May be it is really inappropriate project to report but i found that usbc not
working at all. I suspect usb power problems in kernel. Please help me to find
appropriate project on launchpad (i'm new here).
As i understand, device will not be disconnected in case of just not
complian
Public bug reported:
Steps to reproduce:
1. configured debug repo with vim into /etc/apt/source.list like:
deb http://ddebs.ubuntu.com/ubuntu/ focal-updates main
Did that in a docker container where the following is installed:
apt update; apt-get install -y ca-certificates; apt install curl -
It simply means that the ticket has been acknowledged as a bug/issue,
nothing more. As you might have noticed it's been reported in Debian in
2007, so it doesn't seem to be that important. I know that doesn't help
you but the fact that there's a work-around makes it even less
important. I'll take a
36 matches
Mail list logo
