It missed the 45.0 tag and gnome-45 branch so currently only exists in
future release 46. Hopefully it will get cherry picked into 45.
** Tags added: fixed-upstream
** Tags added: fixed-in-gsettings-desktop-schemas-46
--
You received this bug notification because you are a member of Ubuntu
** Changed in: apparmor (Ubuntu)
Status: Incomplete => 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/2036128
Title:
[FFe] enable unprivileged user namespace
@vorlon - the FFe you approved was to upload a whole new release
apparmor-4.0.0~alpha2 with supporting infrastructure for this feature,
but crucially it did not enable it at that time (as we wanted more time
to add additional profiles for all the packages in the archive so that
when then feature
** Changed in: gsettings-desktop-schemas
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gsettings-desktop-schemas
in Ubuntu.
https://bugs.launchpad.net/bugs/1956102
Title:
Time for the
tu:
New
Status in gnome-shell package in Ubuntu:
Incomplete
Bug description:
I was booting up a daily-legacy image from 20230918 and received a
crash report after choosing "Try Ubuntu".
ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45~rc-0ubuntu3
Un
** No longer affects: subiquity (Ubuntu)
** No longer affects: hundredpapercuts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gsettings-desktop-schemas
in Ubuntu.
https://bugs.launchpad.net/bugs/1956102
Title:
Time for
Public bug reported:
The audio on my laptop, specifically when booting on ubuntu, is not working
properly.
The volume slider either turns my audio off or it turns it up to 100%.
Anything else than muted is 100% on the volume slider.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package:
Public bug reported:
Hi,
We run ext4 on EBS volumes on EC2. During provisioning, cloud-init will
occasionally report that resize2fs has failed due to a superblock checksum
mismatch. We debugged this internally, and were able to come up with the
following reproducer:
#!/usr/bin/bash
I am confused because I thought I had already approved an FFe for this
feature. Did I imagine this? Did that FFe not cover the whole scope?
The hour is getting late now.
** Changed in: apparmor (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
> If you are using NetworkManager, then systemd-networkd.service (and
associated units like systemd-networkd-wait-online.service) should NOT
be enabled. With the caveat that I am not sure why you have systemd-
networkd enabled in the first place, I would recommend that you simply
disable it:
> $
>> On Ubuntu 22.04 desktop system using network-manager
> To be clear, does this mean you have no network interfaces that are
configured to use networkd?
Hey Steve :)
So, this system is quite old. I think the first install was 16.04 and it
went through a bunch of upgrades (mostly interim until
Could we have a justification for why this is important for SRU, please?
As written, the Impact statement describes a bug, but doesn't present
any explanation of why it is important for Ubuntu to fix it in its
stable releases. If it is just that the output might be wrong and we'd
like it to be
** Summary changed:
- signon-ui no longer works for Goolge authentication
+ signon-ui no longer works for Google authentication
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to signon-ui in Ubuntu.
(unsubscribing ~ubuntu-sponsors as given my previous comment there is
now nothing remaining to sponsor)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/2035061
Title:
buntu" on daily-legacy image produced a crash
Status in apport package in Ubuntu:
New
Status in gnome-shell package in Ubuntu:
Invalid
Bug description:
I was booting up a daily-legacy image from 20230918 and received a
crash report after choosing "Try Ubuntu".
** Changed in: gsettings-desktop-schemas (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gsettings-desktop-schemas
in Ubuntu.
https://bugs.launchpad.net/bugs/1956102
marking resolved for the devel series, per description.
** Changed in: procps (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
I'm also affected by this: I'm on Ubuntu 22.04.3 for Raspberry Pi and
after updating to 249.11-0ubuntu3.10 on boot I get:
Sep 18 19:16:33 pi4-ubuntu systemd[1]: Starting Wait for Network to be
Configured...
Sep 18 19:19:29 pi4-ubuntu systemd-networkd-wait-online[1319]: Timeout occurred
image from 20230918 and received a
crash report after choosing "Try Ubuntu".
ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45~rc-0ubuntu3
Uname: Linux 6.5.0-5-generic x86_64
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 18 15:20:58 2
:42] Unable to parse report
(/var/crash/_usr_lib_ubiquity_bin_ubiquity.0.crash):
/var/crash/_usr_lib_ubiquity_bin_ubiquity.0.crash could not be opened.
Sep 18 15:28:42 ubuntu systemd[1]: whoopsie.service: Deactivated successfully.
This was on an Ubuntu daily-legacy image dated 20230918.
ProblemT
ption:
I was booting up a daily-legacy image from 20230918 and received a
crash report after choosing "Try Ubuntu".
ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45~rc-0ubuntu3
Uname: Linux 6.5.0-5-generic x86_64
Architecture: amd64
CurrentDesktop: ubun
quot;Try Ubuntu" on daily-legacy image produced a crash
Status in apport package in Ubuntu:
New
Status in gnome-shell package in Ubuntu:
Invalid
Bug description:
I was booting up a daily-legacy image from 20230918 and received a
crash report after choosing "Try Ubuntu".
Prob
I tested this again today with an Ubuntu desktop legacy image dated
20230918 and encountered the same bug where the screenreader works with
ubiquity if you do not choose "Try Ubuntu" and launch the installer
again.
If this isn't going to be fixed or isn't fixable then I suggest we clos
This bug was fixed in the package linux-raspi - 6.5.0-1002.2
---
linux-raspi (6.5.0-1002.2) mantic; urgency=medium
* mantic/linux-raspi: 6.5.0-1002.2 -proposed tracker (LP: #2033637)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
* Miscellaneous Ubuntu
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.
It is not a desktop system.
Disabling systemd-networkd seems to fix that problem, modemmanager still does
not find the Huawei modem but the interface wwan0 is available and after a
minute of waiting it gets an ip address and is working again.
Thank You!
--
You received this bug notification
systemd[1]: whoopsie.service: Deactivated successfully.
This was on an Ubuntu daily-legacy image dated 20230918.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: whoopsie 0.2.77
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
):
/var/crash/_usr_lib_ubiquity_bin_ubiquity.0.crash could not be opened.
Sep 18 15:28:42 ubuntu systemd[1]: whoopsie.service: Deactivated successfully.
This was on an Ubuntu daily-legacy image dated 20230918.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: whoopsie 0.2.77
** Changed in: lxc (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/2036302
Title:
apparmor 4.0.0~alpha2-0ubuntu3 ships same
Also appears to be affecting the Pi server images (which have no network
manager and only use networkd for networking); I've only checked lunar
so far.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Thanks a lot for taking the time to test and provide feedback.
I'll continue with the SRU process which should take a few more weeks
(I'd say between two and four but that's a very rough guess).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Thanks a lot for taking the time to test and provide feedback.
--
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/1994165
Title:
CMS_final: do not ignore CMS_dataFinal result
Thanks a lot for taking the time to test and provide feedback. I'll
continue with the SRU process; landing will probably take a few weeks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
This bug was fixed in the package lxc - 1:5.0.1-0ubuntu7
---
lxc (1:5.0.1-0ubuntu7) mantic; urgency=medium
* Update apparmor profile to support new userns feature (LP: #2035315)
- d/p/apparmor-userns.patch: Add userns permission to
start-container abstraction and declare
I am guessing this system is running Ubuntu Desktop? If so, systemd-
networkd should not be enabled (and therefore neither should systemd-
networkd-wait-online.service). If I am correct that this is a desktop,
and that you expect NetworkManager to manage the interfaces (along with
ModemManager for
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.
** Description changed:
Description: Ubuntu 22.04.3 LTS
Release: 22.04
- After the latest upgrade our Huawei LTE modem is not working anymore.
+ After the latest upgrade our Huawei LTE modem is not working anymore.
We can see the modem wie lsusb, but no interfaces gets activated
this bug affects us too
--
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/2036427
Title:
Upgrade to version 249.11-0ubuntu3.10 breaks 12d1:15c1 Huawei ME906s
LTE M.2
Public bug reported:
Description:Ubuntu 22.04.3 LTS
Release:22.04
After the latest upgrade our Huawei LTE modem is not working anymore.
We can see the modem wie lsusb, but no interfaces gets activated and
systemd-networkd-wait-online gets a timeout.
The following packages have
If you are using NetworkManager, then systemd-networkd.service (and
associated units like systemd-networkd-wait-online.service) should NOT
be enabled. With the caveat that I am not sure why you have systemd-
networkd enabled in the first place, I would recommend that you simply
disable it:
$
FYI I redid this change again on top of the fix from
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2036302 and have
uploaded it to the aforementioned PPA (debdiff is almost identical,
except for the different context in debian/changelog)
** Patch added:
** Summary changed:
- Printing Ubuntu Bold font - strange symbol
+ Cyrillic characters not spaced correctly when printing with Ubuntu Bold font
** Changed in: fonts-ubuntu (Ubuntu)
Status: Incomplete => New
** Also affects: cups (Ubuntu)
Importance: Undecided
Status: New
--
Hi Andreas,
Regarding output,
non-human-readable output of uptime is not modified.
I had to modify code flow a little bit to not change upminutes and uphours
after initial calculation in case of "-p", thus I hid it under
if(!human_readable).
Code flow for !human_readable should stay exactly as
** Changed in: mesa (Ubuntu)
Status: In Progress => Fix Committed
** Tags added: fixed-in-mesa-23.3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2034672
Title:
** Changed in: apparmor (Ubuntu)
Status: New => Invalid
** Converted to question:
https://answers.launchpad.net/ubuntu/+source/apparmor/+question/707965
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
45 matches
Mail list logo
