Attaching patch against Debian unstable. For ease of review, relevant commits
and tags have been pushed to the following repository:
https://code.launchpad.net/~waveform/ubuntu/+source/unattended-
upgrades/+git/unattended-upgrades
Specifically:
* logical/2.8ubuntu1 represents our split-out
Public bug reported:
Please merge unattended-upgrades 2.9.1+nmu2 from Debian unstable.
Updated changelog and diff against Debian unstable to be attached below.
** Affects: unattended-upgrades (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
Test package building in ppa:waveform/initramfs-tools
(https://launchpad.net/~waveform/+archive/ubuntu/initramfs-tools)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
Doh, let's try that again with the right series this time...
** Patch added: "3-1988418.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1988418/+attachment/5633182/+files/3-1988418.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch
Attaching amended debdiff addressing review comments
** Patch added: "2-1988418.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1988418/+attachment/5633181/+files/2-1988418.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
> My standard way of reviewing a merge is to do the merge myself and
> see what comes up different. Here are my observations:
>
> conf/initramfs.conf: the commented COMPRESSLEVEL setting should
> match the default, which for us is 1, not 3.
Good point! Slightly weird that it's set to 3 given that
atus: New => Confirmed
** Changed in: pulseaudio (Ubuntu Kinetic)
Assignee: Dave Jones (waveform) => (unassigned)
** Changed in: ubuntu-settings (Ubuntu)
Assignee: Dave Jones (waveform) => (unassigned)
** Changed in: ubuntu-settings (Ubuntu Kinetic)
Assignee: Da
Still a problem on jammy, and removing switch-on-connect does fix things
there.
The result of that change is that plugging in a new (never seen before)
USB device does *not* automatically switch to it, but once the device
has been selected as the output, it will subsequently be automatically
*** This bug is a duplicate of bug 1877194 ***
https://bugs.launchpad.net/bugs/1877194
This sounds like a duplicate of LP: #1877194 -- a workaround is
available in that report (see comment 2)
** This bug has been marked a duplicate of bug 1877194
switch-on-connect mistakes startup for USB
So where are we on this folks?
--
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/1991975
Title:
dev file system is mounted without nosuid or noexec
Status in linux package
** Changed in: netplan
Status: Incomplete => Triaged
--
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/1815101
Title:
[master] Restarting systemd-networkd breaks
Alright so that means we either need to push a change to remove noexec
from the kernel init code, or we go ahead with noexec, and give people
on option to remount with exec should they want sgx functionality. I do
think the nosuid flag does still provide some benefit even if we decide
not to
In case anyone is curious conversation is on-going on the kernel-team mailing
list
https://lists.ubuntu.com/archives/kernel-team/2022-October/133764.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
@juliank, is this an aws system? If not there's a good chance that you
are using an initramfs to mount the filesystems. That's definited in
either /etc/init.d/udev or directly out of the init that lives in the
initramfs.
--
You received this bug notification because you are a member of Ubuntu
Here is a workaround for this issue in case anyone finds this in the
future.
Copy remount_dev.service to /etc/systemd/system
sudo chown root:root /etc/systemd/system/remount_dev.service
sudo systemctl daemon-reload
sudo systemctl enable remount_dev.service
Still I think the kernel patch should
** Information type changed from Private Security to Public Security
** Summary changed:
- dev file system is mounted without nosuid
+ dev file system is mounted without nosuid or noexec
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Description changed:
+ [ SRU TEMPLATE ]
+ [ Impact ]
+
+ * nosuid, and noexec bits are not set on /dev
+ * This has the potential for nefarious actors to use this as an avenue for
attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more
discussion around this.
+ *
** Changed in: linux (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: systemd (Ubuntu Jammy)
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.
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Jammy)
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
Looks like Kees already found this years ago.
https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/
Looks like it was accepted as commit 28f0c335dd4a1 in 5.17. So I think
we should apply this patch and the corresponding set
CONFIG_DEVTMPFS_SAFE=y at least for the
I was hoping to work around this in /etc/init.d/udev, but it looks like that
gets redirected to systemctl via
. lib/lsb/init-functions
** Description changed:
This is similar to
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new.
I discovered that my ec2 instances
So far I've only tested focal AWS images, but this may likely exist
elsewhere as well.
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification
** Also affects: linux (Ubuntu)
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/1991975
Title:
dev file system is mounted
Public bug reported:
This is similar to
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new.
I discovered that my ec2 instances based off of Canonical supplied AMI
ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the
nosuid option.
It would probably be best to report the crash in the "Software and
Updates" tool separately against the software-properties package
(https://launchpad.net/ubuntu/+source/software-properties).
In the meantime you'll want to select "Pre-released Updates" on the
"Developer Options" tab at the end of
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1971901
Title:
dlltool uses non-unique temp filenames
Status in binutils:
Fix Released
Switching the dependency over to PyQt (or PySide?) sounds like something
for the desktop team to look at?
** Tags added: rls-kk-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
** Changed in: ubuntu-seeds
Status: New => Fix Committed
--
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"
** Changed in: ubuntu-seeds
Status: New => Fix Committed
--
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/1989807
Title:
Move raspi cloud-init configuration
** Also affects: ubuntu-settings (Ubuntu Jammy)
Importance: Undecided
Status: New
--
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/1989807
Title:
Move
Apparently rm_conffile is considerably more stubborn than I'd given it
credit for, when it comes to removing files previously unowned by
packages (i.e. /etc/cloud/cloud.cfg.d/99-fake_cloud.cfg). The only
successful method is to rm it in a postinst script unfortunately. The
attached patch remedies
Attaching debdiff for ubuntu-settings. This incorporates the diff for
this bug as well as the earlier (and vaguely related) LP: #1977764. In
addition to this, I've extended the merge proposal for the
aforementioned bug to update the necessary seed to include this package
in the Ubuntu Pi server
** Also affects: ubuntu-settings (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: ubuntu-seeds
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
Currently /etc/cloud/cloud.cfg.d/99-fake_cloud.cfg (which exists to
disable "real" cloud sources on the raspi images) is hacked into the
images from livecd-rootfs. It would be preferable to have this in a
server-specific variant of the ubuntu-raspi-settings package.
To avoid
Test packages are building in ppa:waveform/initramfs-tools at:
https://launchpad.net/~waveform/+archive/ubuntu/initramfs-tools
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
I would caution that there are some substantial changes in this merge.
Specifically:
* upstream has now moved to zstd by default (as in Ubuntu) resulting in
several bits of the delta changing
* upstream re-wrote a fair amount of logic around the "ip=" init
parameter; this is an area we already
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
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/1988418
Title:
Please merge initramfs-tools
Attaching patch against Debian unstable. For ease of review, relevant commits
and tags have been pushed to the following repository:
https://code.launchpad.net/~waveform/ubuntu/+source/initramfs-
tools/+git/initramfs-tools
Specifically:
* logical/0.140ubuntu17 represents our split-out delta on
Public bug reported:
Please merge initramfs-tools 0.142 from Debian unstable.
Updated changelog and diff against Debian unstable to be attached below.
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
It appears dbus is stuck in kinetic-proposed due to failures in
dependency resolution on i386; there are two new arch-indep packages in
the merged package which the dbus package depends on, but they lack
Multi-Arch tags in d/control.
I'm attaching (yet another :) debdiff which adds M-A: foreign
> I'll upload it using git-ubuntu style, too, so it will be easier to do
the next merge.
I must get Robie to remind me what I need to stuff in the .changes file
to make that automatic (I vaguely recall him mentioning there were some
extra tags that could/should be placed there).
> Using a
** Patch added: "manpage-is-wrong.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+attachment/5611101/+files/manpage-is-wrong.debdiff
** Tags added: rls-kk-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Patch added: "bash-is-wrong.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+attachment/5611100/+files/bash-is-wrong.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
I'm unsure what the "correct" solution is here; could be that bash's
behaviour is wrong, or it could be that the documentation is wrong.
Rather than decide, I'm taking the cowards way out and attaching patches
for both solutions, leaving it to the maintainer to decide which is
appropriate :)
--
Hmm, on the other hand --norc does indeed suppress both user and system-
wide bashrc files. So, the man-page is correct in that instance, and
apparently the intent of bash is to allow the system-wide bashrc file to
be suppressed in certain circumstances. Which sways me back toward the
notion that
I'm afraid the removal of colons in LP: entries of the changelog is a
deliberate tactic by maintainers to prevent launchpad from inadvertently
marking things closed when it shouldn't (theoretically, this shouldn't
happen if things are targetted correctly to the relevant releases, but
this isn't
This has apparently been an issue for some considerable time. I've just
now run into it while delving into a failure in pexpect's test-suite
(during work on LP: #1987420), which apparently assumes that using
--rcfile will suppress both the user *and* the system's bashrc (as the
man-page
** Summary changed:
- bash does not fulfill --bashrc option properly
+ bash does not fulfill --rcfile option properly
** Description changed:
I am starting a bash shell using
- $ bash --noprofile --bashrc my-custom-bash-rc-file
+ $ bash --noprofile --rcfile my-custom-bash-rc-file
Due
Attaching patch against Debian unstable. For ease of review, relevant commits
and tags have been pushed to the following repository:
https://code.launchpad.net/~waveform/ubuntu/+source/dbus/+git/dbus
Specifically:
* logical/1.12.20-2ubuntu4 represents our split-out delta on top of old/debian
Test builds will be available in ppa:waveform/dbus at the following URL:
https://launchpad.net/~waveform/+archive/ubuntu/dbus
** Tags added: fr-2624
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
** Summary changed:
- Please merge dbus 1.12.20-3 from Debian unstable
+ Please merge dbus 1.14.0-2 from Debian unstable.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
** Changed in: lvm2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1987340
Title:
Please merge lvm2 2.03.16-1 from Debian unstable.
Test builds are available from ppa:waveform/lvm2 at the following URL:
https://launchpad.net/~waveform/+archive/ubuntu/lvm2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
** Tags added: fr-2621
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1987340
Title:
Please merge lvm2 2.03.16-1 from Debian unstable.
Status in lvm2 package in Ubuntu:
Attaching patch against Debian unstable. For ease of review, relevant commits
and tags have been pushed to the following repository:
https://code.launchpad.net/~waveform/ubuntu/+source/lvm2/+git/lvm2
Specifically:
* logical/2.03.11-2.1ubuntu4 represents our split-out delta on top of
old/debian
Public bug reported:
Please merge lvm2 2.03.16-1 from Debian unstable.
Updated changelog and diff against Debian unstable to be attached below.
** Affects: lvm2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
As requested, here's what I managed to dig up on possible alternatives
to running unattended-upgrades-shutdown persistently:
There appear to be several methods by which systemd can be told to run
something at or near shutdown, but one has to be exceptionally careful
in the selection to cover all
** Description changed:
- On the hirsute Pi desktop, under a wayland session with the "full" KMS
- overlay enabled, and "kms-modifiers" present in the
- org.gnome.mutter/experimental-features, the body of a window containing
- an HTML renderer (e.g. help text or a login page) displays corruption.
To sponsors: let me know if the ubuntu-raspi-settings-desktop name is
not desirable; I'm happy to adjust this to (for example) ubuntu-desktop-
raspi-settings but it'll need adjusting in both this debdiff, and in the
MP for the corresponding seed.
--
You received this bug notification because you
Attaching debdiff for ubuntu-settings. This adds the ubuntu-raspi-
settings-desktop binary package which includes the necessary initramfs-
tools configuration to include the missing modules. In addition to this,
I'll file a merge proposal for the necessary seed to include this
package in the
** Also affects: ubuntu-seeds
Importance: Undecided
Status: New
** Changed in: ubuntu-seeds
Assignee: (unassigned) => Dave Jones (waveform)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-setti
** Patch added: "1-1814301-jammy.debdiff"
https://bugs.launchpad.net/ubuntu/jammy/+source/quassel/+bug/1814302/+attachment/5597063/+files/1-1814301-jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
** Patch added: "1-1814301-kinetic.debdiff"
https://bugs.launchpad.net/ubuntu/jammy/+source/quassel/+bug/1814302/+attachment/5596890/+files/1-1814301-kinetic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
ged in: quassel (Ubuntu Kinetic)
Status: Fix Released => Confirmed
** Changed in: quassel (Ubuntu Kinetic)
Assignee: Dan Streetman (ddstreet) => Dave Jones (waveform)
** Changed in: quassel (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: quassel (Ubuntu Jammy)
@seb128 tested with pipewire on kinetic with a Pi 4B and it correctly
selects the HDMI out by default both on initial setup and after a few
reboots. So, looks like this could be "invalid" on kinetic, at least for
the Raspberry Pi case. Would be useful to double-check that on PC
hardware too,
Oh, now I remember why this one was more complicated: it's for the pi
*desktop specifically*. Can't add this to ubuntu-raspi-settings directly
as that'll pull in zstd, z3fold, and all the zswap stuff on the server
images too, which increases the memory burden on the minimal Zero 2 and
3A+
** Changed in: initramfs-tools (Ubuntu Kinetic)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: initramfs-tools (Ubuntu Jammy)
Assignee: (unassigned) => Dave Jones (waveform)
** Also affects: ubuntu-settings (Ubuntu)
Importance: Undecided
Status: New
** No longer
Sure -- I'll try not to drown them in verbiage :)
--
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/1951586
Title:
Need option to specify wifi regulatory domain
> It could be maybe added to NetworkManager, if somebody sends a
> patch. But it's not actually clear to me that this is really
> NetworkManager's task. Maybe it is, but what are the arguments for
> that?
I could be glib, and say "because the kernel says so [1]". However, I
suspect that's not a
>> it's apparently never worked for me at home or at various friends
>> houses, and only once worked when I travelled to Germany for a
>> sprint.
> is that having a visible impact for users? like was your computer
> not able to connect to some access point?
Personally, I've never encountered
I'll take a shot at responding to @seb128's questions:
Why is this a rls issue in the LTS?
===
Prior to jammy, the crda database was in userland, and the crda package
provided a means (via editing /etc/default/crda) to persist the wireless
region across reboots.
> Should be part of the 'beacon' info.
https://howiwifi.com/2020/07/13/802-11-frame-types-and-formats/ has a
good overview. I discovered this exchange while observing 'on the wire'
with wireshark.
Thanks for the link; lots of useful stuff there!
> > I wondered if perhaps it this only works on
I'm not entirely convinced NetworkManager is working correctly this
regard? I *was* checking the wifi regulatory domain with "iw reg get"
which consistently shows UNSET both globally and for phy#0 under the
desktop for Pi images:
$ iw reg get
global
country 00: DFS-UNSET
(2402 - 2472 @
** Changed in: lvm2 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1928973
Title:
Please merge lvm2 2.03.11-2.1 from
** Changed in: ubuntu-settings (Ubuntu Impish)
Status: New => Won't Fix
--
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/1923672
Title:
[FFe] Provide access
*** This bug is a duplicate of bug 1969512 ***
https://bugs.launchpad.net/bugs/1969512
Sorry, I think this is a duplicate of 1969512 (marking as such) -- I
have found, in the course of investigating that one that we may either
need to switch the ISO test to use an OGG (or OGV) file instead
** Changed in: initramfs-tools (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1915966
Title:
Please merge
@jvonau I just came back to this while trawling through my still-open
bug list and had a look at what happens on the desktop. At least on our
Pi desktop images (using NetworkManager), no wifi regulatory domain gets
set at all (at least on my local network). Just in case it made any
difference, I
*** This bug is a duplicate of bug 1877194 ***
https://bugs.launchpad.net/bugs/1877194
** This bug is no longer a duplicate of bug 1899962
Wrong audio output device selected on Raspberry Pi Desktop
** This bug has been marked a duplicate of bug 1877194
switch-on-connect mistakes startup
*** This bug is a duplicate of bug 1877194 ***
https://bugs.launchpad.net/bugs/1877194
Looks like this fell off my radar, but looking at vanvugt's comment this
is indeed a duplicate of bug 1877194 (and still occurs in Jammy). I'll
mark it as such
** This bug has been marked a duplicate of
Another quick update: in recent days we've gone from "blank white space"
back to "incorrect stride corruption" in all documented cases (embedded
browsers, help windows, MiniBrowser, etc).
I note in the dpkg logs, libglx-mesa0 got updated a few days ago, but
unfortunately I'm unsure exactly when
** Changed in: ubuntu-meta (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-image (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
@noahod I've just tried this with the current
https://cdimage.ubuntu.com/ubuntu-server/daily-
preinstalled/current/jammy-preinstalled-server-arm64+raspi.img.xz image
(downloaded today) and with just your growpart config (I didn't try the
resize_rootfs key), the card booted without resizing the
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Fix Committed
--
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/1947311
Title:
Unexpected partition growth on
@seb128 interesting, I've just tried this on a fully updated jammy image
on a Pi 400 and /usr/lib/aarch64-linux-gnu/webkit2gtk-4.0/MiniBrowser
starts quite happily; browser window opens and ... nothing but blank
white space within the body of the window. All the controls in the
toolbar are fine
Attaching debdiff which I believe should prevent the service from being
stopped on upgrade. Test packages are currently building in
ppa:waveform/dbus (https://launchpad.net/~waveform/+archive/ubuntu/dbus)
but I've already built locally and verified that the offending portion
of the preinst
Some additional info:
"dh_installsystemd --no-start" on its own is *not* equivalent to "--no-
start --restart-after-upgrade" as one might imagine ("--restart-after-
upgrade" is *usually* the dh_installsystemd default). Instead "--no-
start" adjusts the restart default to
** Changed in: dbus (Ubuntu Jammy)
Assignee: (unassigned) => Dave Jones (waveform)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1962036
Title:
dbus was stopped dur
** Description changed:
+ NOTE: Resetting to new; do NOT merge (the current state of the merge
+ would also produce LP: #1962036 -- will update this merge once that is
+ fixed)
+
Please merge dbus 1.12.20-3 from Debian unstable.
Updated changelog and diff against Debian unstable to be
This still seems to be an issue on the current Ubuntu Pi Jammy images
although it presents in a different manner: instead of an incorrect-
stride corruption, the embedded browser (in the same places: help
windows, or the login entries for online accounts) simply appears blank
white.
However, if
** Tags added: fr-2147
--
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/1947311
Title:
Unexpected partition growth on first boot on impish for raspberry pi
Status in
Sorry, this slipped off my radar -- I'll get on with the required PRs
today
--
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/1947311
Title:
Unexpected partition growth
Closing as we're now using "full" KMS on all supported desktops
** Changed in: linux-raspi2 (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: linux-raspi (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch
** Changed in: debhelper (Ubuntu Jammy)
Assignee: Dave Jones (waveform) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
https://bugs.launchpad.net/bugs/1959054
Title:
debhel
** Patch added: "1-1961618.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1961618/+attachment/5562552/+files/1-1961618.debdiff
** Changed in: ubuntu-settings (Ubuntu)
Status: New => Confirmed
** Tags added: raspi-image rls-jj-incoming
--
You received this
Oh, and apparently ubuntu-settings FTBFS with the version of meson in
jammy (0.61.2-1); will add a patch for that too.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
Public bug reported:
The eth0 rename fix introduced in 20.10.1, and removed in 22.04.1
unfortunately causes problems on upgrade from impish to jammy as the
file (/etc/netplan/10-rpi-ethernet-eth0.yaml) still remains in place,
and the new netplan version on jammy chokes on the space-separated
1/+files/1-1959054.debdiff
** Changed in: debconf (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: debconf (Ubuntu Jammy)
Assignee: Dave Jones (waveform) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whi
** Changed in: dbus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1959211
Title:
Please merge dbus 1.12.20-3 from Debian unstable
@ahasenack Could you try the debconf version from [1]? I've patched that
with the same fix that I've proposed upstream [2]. I'll add the relevant
debian bug here too. I realize this is *technically* a separate issue,
but it's all so interconnected and related that I'd prefer to keep it
all in one
101 - 200 of 921 matches
Mail list logo
