netplan added support for configuring the regulatory domain in kinetic
and it works pretty nicely (it's one of the things I test before
release). However, that's relying on cloud-init to inject the netplan
configuration and that's only on the server images -- it's not a
solution for the preinstalle
Given there doesn't seem much interest in fixing this from the network
manager angle (and there's even a question as to whether that's the
right place to fix this), I'm going to take a leaf out of the RaspiOS
book, and see if I can persuade someone that the installer is the right
place to fix this
I'd say this is effectively "Fix Released" at this point in that on
lunar (and kinetic? Sorry, I forgot to re-test this before upgrading the
old drive), Totem now fails to play the video with "could not initialize
OpenGL support" which is the "fix" implemented upstream (and reflected
by the upstrea
** Also affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: livecd-rootfs (Ubuntu)
Milestone: None => ubuntu-23.04
** Changed in: livecd-rootfs (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
--
You received this bug notification b
This should only be merged once LP: #2004430 as it builds upon those
commits.
** Merge proposal linked:
https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/439835
** Merge proposal linked:
https://code.launchpad.net/~waveform/livecd-rootfs/+git/
andle calculating the resize
in early boot.
** Affects: ubuntu-settings (Ubuntu)
Importance: Undecided
Assignee: Dave Jones (waveform)
Status: New
** Changed in: ubuntu-settings (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: ubuntu-settings
Still an issue on the current LTS (jammy, 22.04), and the current devel
series (lunar, 23.04)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/861493
Title:
evince doesn't print duplex o
)
Importance: Undecided
Assignee: Dave Jones (waveform)
Status: In Progress
** Patch added: "fix-lto.patch"
https://bugs.launchpad.net/bugs/2009824/+attachment/5653167/+files/fix-lto.patch
** Changed in: libcamera (Ubuntu)
Assignee: (unassigned) => Dave Jo
FYI, in case anyone wants to add their monitor (and whether it succeeds
or fails at suspending with the Ubuntu raspi kernel) to this ticket:
$ cp /sys/devices/platform/gpu/drm/card1/card1-HDMI-A-1/edid hdmi0-monitor.edid
$ cp /sys/devices/platform/gpu/drm/card1/card1-HDMI-A-2/edid hdmi1-monitor.ed
Fails with this monitor: https://www.edid.tv/edid/2267/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1998716
Title:
[raspi] Ubuntu 22.10 does not turn off monitor
Status in linux-ra
I'm still seeing this behaviour (precisely as described at the top:
fades to black, switches off, then switches on to black a second or two
later) with the lunar daily image and the bootstrap 6.2 kernel, so it'll
likely be an issue in lunar.
I'll flash a jammy and kinetic image to a card in a bit
Public bug reported:
When testing the current lunar (23.04) pre-installed desktop image for
the Raspberry Pi, I attempted to retrieve the properties of a captured
JPEG from nautilus:
* Right click on a JPEG image
* Select "Properties" item at the bottom
* Click on the "Image Properties" link at t
I can confirm this bug remains even without Fractional Scaling is
enabled, and also while using Wayland not X11
In my case I set monitor 1 as primary monitor (primary display port),
monitor 3 (secondary display port) with orientation "Portrait Left",
after reboot/logout/system update that required
*** This bug is a duplicate of bug 1825593 ***
https://bugs.launchpad.net/bugs/1825593
I disagree that this is a Duplicate of bug #1825593, because this
happens for me without Fractional Scaling is enabled, and while using
Wayland not X11
In my case I set monitor 1 as primary monitor (primary
Looking at mesa git staging/23.0 it looks like 78a75e0d2 and 4c986c58b
may also be required.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2006669
Title:
Asynchronous wait on fence ...
The above referenced commits are committed into mesa 23.0.0. I see
references to backports of this onto stable, but I'm not familiar enough
with mesa as a project just yet.
** Also affects: mesa (Ubuntu Lunar)
Importance: Undecided
Assignee: Dave Chiluk (chiluk)
Status
** Tags added: indeed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2006669
Title:
Asynchronous wait on fence ... timed out
(hint:intel_atomic_commit_ready [i915])
Status in mesa pac
video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: mesa (Ubuntu)
Importance: Undecided
Assignee: Dave Chiluk (chi
Closing this ticket where I can as there's no update for 5 years. Plus
mir has been supplanted by wayland.
** Changed in: mesa (Ubuntu)
Status: New => Won't Fix
** Changed in: mir (Ubuntu)
Status: Triaged => Won't Fix
** Changed in: mir
Status: Triaged => Fix Released
--
** Changed in: livecd-rootfs (Ubuntu)
Milestone: None => ubuntu-23.04
** Changed in: ubuntu-settings (Ubuntu)
Milestone: None => ubuntu-23.04
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs
** Merge proposal linked:
https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/436647
** Merge proposal linked:
https://code.launchpad.net/~waveform/livecd-rootfs/+git/livecd-rootfs/+merge/436648
--
You received this bug notification because you
Affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Assignee: Dave Jones (waveform)
Status: New
** Affects: ubuntu-settings (Ubuntu)
Importance: Undecided
Assignee: Dave Jones (waveform)
Status: New
** Also affects: livecd-rootfs (Ubuntu)
Import
ux 5.19.0-29-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dave 7291 F wireplumber
/dev/snd/controlC1: dave 7291
PID ACCESS COMMAND
/dev/snd/controlC0: dave 7291 F wireplumber
/dev/snd/controlC1: dave 7291 F wireplumber
/dev/snd/seq: dave 7288 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Mon Jan 23 10:57:51 2023
InstallationDate: Installed on
Adding a trivial test PDF
** Attachment added: "test_pdf.pdf"
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2001904/+attachment/5639334/+files/test_pdf.pdf
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
htt
Public bug reported:
Opening a PDF under evince, then clicking an https: link within the PDF
fails to open the link in Firefox. On the command line, evince reports:
$ evince test.pdf
env: ‘/snap/bin/firefox’: Permission denied
In dmesg, the following message appears each time the link is clicked
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
selec
*** 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
I am running into something similar. I changing case in a filename
doesn't accept changes.
ie: renaming "text.txt" to "Test.txt" doesn't work. The only thing I can
do is rename "text.txt" to "test2.txt" then rename "test2.txt" to
"Test.txt"
--
You received this bug notification because you are a
Public bug reported:
When testing the Ubuntu 22.10 (kinetic) Desktop for Raspberry Pi on a
Raspberry Pi 4, the new pipewire stack selects the "Analogue Output -
Built-in Audio" by default when the system is first installed, when the
HDMI output probably ought to be selected by default (the analogu
Public bug reported:
When testing the Ubuntu 22.10 (kinetic) Desktop for Raspberry Pi on a
Raspberry Pi 400 (the keyboard-based model), the new pipewire stack
selects a non-existent audio output by default. Specifically, the output
device listed in the gnome control center is "Analogue Output - Bu
Public bug reported:
During testing of the kinetic desktop on a Raspberry Pi, I came across
an odd behaviour with the fractional scaling settings. I also replicated
the issue on the PC image (so it's not Pi specific), and on the jammy
desktop (so it's a fairly long-standing bug). Reproduction step
** Changed in: ubuntu-seeds
Status: New => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1977764
Title:
kernel modules "zstd" and "z3fold" missing.
Stat
** Changed in: ubuntu-seeds
Status: New => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1989807
Title:
Move raspi cloud-init configuration to ubuntu-set
** Also affects: ubuntu-settings (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1989807
Title:
Move raspi cloud-init
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 t
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 ima
** 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 Desktop
Packages, which is subscribed to ubuntu-settings in Ub
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
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1989615
Title:
gnome-shell crashed with SIGABRT in assertion
[libmutter:ERROR:../src
** 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.
*** This bug is a duplicate of bug 1924251 ***
https://bugs.launchpad.net/bugs/1924251
I'm afraid this is a long-standing issue under KMS; duplicate of LP:
#1924251
** This bug has been marked a duplicate of bug 1924251
Embedded browser display corruption under Wayland on Pi desktop
--
Y
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 Ubuntu
** 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 Desktop
Packages, which is subscribed to ubuntu-settings in Ubuntu.
ht
@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, obviou
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+ platforms
> I don't know what you mean when said that remote desktop is a recent
addition to the desktop...
I'll just address this point, but continue the discussion of what should
be included in the mandatory testing over on LP: #1978113.
What I specifically meant by "recent addition" is that, prior to im
> It is a pity Canonical is advertising super optimisations on
> Raspberry Pi 4 with 22.04 and this basic feature is totally broken
> as is: was never ever tested...
Graphical remote desktop is far from a "basic" feature, in my opinion
(an opinion bolstered by the fact it is only a recent addition
@seb128 yes, the following command line plays (for at least 20 seconds
-- I didn't watch the whole thing) happily under totem:
MESA_GL_VERSION_OVERRIDE=3.3 totem big_buck_bunny_720p_surround.mp4
So the issue is simply that the pi's GL driver only goes up to 2.1,
and/or that GTK doesn't accept GL<
Sorry, hadn't refreshed this page and didn't notice your comment 9
before posting mine! With the override in place it looks like things
work properly:
$ MESA_GL_VERSION_OVERRIDE=3.3 /usr/libexec/gnome-control-center-print-renderer
V3D 4.2
And looking at the upstream ticket you linked makes a lot
I've done a bit of debugging on this; wound up tweaking the code
mentioned in comment 8 above to return g_strdup("NULL context") instead
of return NULL and with this in place, gnome-control-center-print-
renderer (and indeed the "Graphics" field of the control center) both
return "NULL context" so
us: New
** 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
**
gnome-control-center-printer-renderer produces no output on the raspi.
The debug output from gnome-control-center is:
(gnome-control-center:3171): GLib-GIO-DEBUG: 14:47:50.015:
_g_io_module_get_default: Found default implementation dconf
(DConfSettingsBackend) for ‘gsettings-backend’
(gnome-cont
Sure -- I'll try not to drown them in verbiage :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1951586
Title:
Need option to specify wifi regulatory domain
Status in cloud-
> 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 gr
>> 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 issu
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. Fr
Reported issue with flatpak (under arm64) upstream:
https://gitlab.gnome.org/GNOME/totem/-/issues/509#note_1468424 (after
re-testing just to confirm that the issue still occurred).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in
I'm attaching the full outputs as a tarball (just in case they're
useful) but here's the pertinent bits too:
$ tail -n 13 /proc/cpuinfo
processor : 3
BogoMIPS: 108.00
Features: fp asimd evtstrm crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU p
@Samuel that fix is for PCs which is a different bug (LP: #1971463);
this bug is about totem on the Pi desktop images (or, I'm beginning to
suspect, arm64 more generally).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
h
An additional data point; I noted in the linked gitlab bug a couple of
messages noting that "it works with the flatpak". Out of curiosity (as
to whether this might be a well and truly arm64 specific problem), I
tried the flatpak on the pi desktop and: it's got exactly the same
problem (same behavio
Unfortunately we've tried "G_DEBUG=fatal_warnings" before (you suggested
it back in comment:4) but I did manage to figure out a couple of things
since last time:
The crash I originally observed (back in comment:6) only occurs on the
very first run of totem. All subsequent runs (even after a reboot
> 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 som
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 @ 40)
** Changed in: ubuntu-settings (Ubuntu Impish)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1923672
Title:
[FFe] Provide access to GPIO to de
*** 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 (or
It appears to take 250MB resident (according to top) on my Raspberry Pi
400 even when the software is "closed". On a machine with 4GB, this is
pretty significant. Even more so considering we now support the desktop
on Pis with as little as 2GB of RAM.
--
You received this bug notification because
I've now installed the -dbg packages in an attempt to get a proper
stacktrace (as requested by seb128); unfortunately try as I might I've
been unable to re-create the crash I experienced a couple of weeks ago.
Totem still fails to play anything (same message, same debug output as
previously reporte
@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 al
Workaround available here
https://askubuntu.com/questions/1403896/cant-add-cisco-compatible-vpn-vpnc-on-network-manager-ubuntu-22-04/1404609#1404609
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https:
** Tags added: indeed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1968588
Title:
Cannot create or add VPN in connection editor
Status in network-manager-applet pack
@floe -- thanks for the extra info! Unfortunately I'm not sure this is a
gstreamer issue (or more precisely, there may well be a gstreamer issue
on amd64, but it doesn't appear to be the case on arm64 with the Pi
Desktop image). gstreamer1.0-vaapi isn't seeded on the Pi Desktop
images, and indeed r
** Changed in: totem (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1969512
Title:
totem unable to play bbb mp4: "The specified movie cou
"/org/gnome/desktop/lockdown/" (establishing: 0, active: 1)
(totem:38425): Totem-DEBUG: 11:13:08.657: TotemGrilo: Pausing videos
thumbnailing
(totem:38425): Totem-DEBUG: 11:13:08.675: totem_playlist_add_one_mrl ():
big_buck_bunny_720p_surround.mp4 (null) (null) (null) 0 false
(totem:3842
We download and try to play locally (see item 12 in
http://iso.qa.ubuntu.com/qatracker/milestones/432/builds/247134/testcases/1747/results
for an example). I'll try and get some DEBUG output this morning (I can
state it's definitely not crashing though; the error message simply
appears and totem re
Public bug reported:
As part of our ISO testing for the Pi desktop, we attempt to play
https://archive.org/download/BigBuckBunny_124/Content/big_buck_bunny_720p_surround.mp4
with the shipped totem video player. Unfortunately, on the current Jammy
image, totem simply reports "The specified movie co
*** 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 bug
*** 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
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 th
** 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 Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launc
@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 root
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1947311
Title:
Unexpected partition growth on first boot 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 and
Public bug reported:
When testing firefox 98.0.2 from the snap on the Ubuntu for Raspberry Pi
pre-installed desktop image (using Wayland), I noted that I'm unable to
drag'n'drop tabs to re-order them, or detach them into separate windows.
I can re-order tabs with the Ctrl+Shift+Pg{Up,Dn} keyboard
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 th
** Tags added: fr-2147
--
You received this bug notification because you are a member of Desktop
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 cloud-init pac
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 Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1947311
Title:
Unexpected partition growth on first boot
Public bug reported:
At least according to gnome-control-center anyway.
Running the Ubuntu Desktop for Raspberry Pi image on a Pi 400 (or a Pi
4B), selecting Settings, then the "About" page shows that gnome-control-
center thinks the processor is "", the graphics are "unknown", and
apparently so
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 Desktop
Packa
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 Desktop
Packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1961618
Tit
** 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 bug
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
drive
@xnox Ah, that makes sense, thanks. I'll propose some seed updates in a
bit.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1947311
Title:
Unexpected partition growth on first boo
added to the desktop
seed specifically instead of the raspi-common seed.
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-meta (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: cloud-init (Ubuntu)
Assignee: Dave Jon
Just to clarify, while gzip may be preferable this shouldn't prevent the
lz4 fix from landing. It's a "good enough" workaround for a bug that
prevents people from running apt-upgrade (which is far more important
than "choice of compression algorithm").
--
You received this bug notification becaus
Some further research on this [1] suggests gzip may be a preferable
choice on the smaller platforms (lower memory usage, and better
compression anyway), plus this would alleviate the need for including
lz4 in the images.
I need to do some further analysis of the decompression to see if it is
still
** Changed in: ubuntu-settings (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: ubuntu-settings (Ubuntu Impish)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-settings in Ubuntu.
https
The attached debdiff fixes this issue in ubuntu-settings (and restores
the 21.04.3 changes that were previously missing). Packages have been
built and tested in the following PPA:
https://launchpad.net/~waveform/+archive/ubuntu/ubuntu-settings
** Patch added: "1-1950214.debdiff"
https://bug
101 - 200 of 2066 matches
Mail list logo
