Public bug reported:
On the Ubuntu noble desktop for Raspberry Pi, the system journal has
numerous of the following entries:
May 23 10:30:29 kermit tracker-miner-f[11130]: Could not get landlock supported
ABI: Operation not supported
May 23 10:30:29 kermit tracker-miner-f[11130]: Refusing to
Public bug reported:
On the Ubuntu Desktop for Raspberry Pi (arm64) under noble, GIMP is
reliably crashing when closing the application with unsaved changes, and
selecting "Discard Changes".
Steps to reproduce:
* sudo apt install gimp
* Open GIMP with an image (right click image in Files, Open
Sorry, I should give a bit more context on this issue to clarify things.
The test for this issue comes from the ISO tests for the Ubuntu Desktop
for Raspberry Pi images. The test intends to check whether a fresh
install can play a video "out of the box". The video used in the test is
Failed to reproduce on noble beta images; marking invalid as that's two
failures now.
** Changed in: gnome-control-center (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Adding affects packagekit as I've no idea if this is totem's fault or
packagekit's.
** Also affects: packagekit (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
Public bug reported:
While attempting to play a video on Ubuntu noble desktop for raspberry
pi, totem attempts to locate a package for the H.264 codec but cannot
find a service providing org.freedesktop.PackageKit. This is strange
given that packagekit is installed, provides packagekit.service,
Public bug reported:
While testing the Ubuntu noble (24.04) desktop for Raspberry Pi beta, I
noticed that all GTK4 applications appear to be missing various icons.
All lack the minimize / maximize / close icons (which are left as three
empty circles on the window), and others lack icons within
Failed to reproduce this on the jammy .4 images during ISO testing.
Possibility it's either fixed or only occurs on later versions. Will
attempt to reproduce on mantic later, if I've got the time.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Public bug reported:
I'm unsure if this is a bug in quassel, or in the gnome dock itself.
Under Ubuntu 23.10 (mantic), running Quassel from a pinned icon on the
left bar results in the pinned icon appearing "idle" (not running), and
a second icon appearing below those that are pinned which
This has been fixed for a couple of releases now (since lunar I
believe), and if I recall correctly the issue was indeed the wpe backend
mentioned in comment 17. That would suggest this should be "invalid" for
gtk and yelp, and "fix released" for webkit2gtk.
--
You received this bug notification
This appears to be partially fixed under Ubuntu 23.10. While the
application (when running) still eats a few hundred meg of RAM, it does
release that when closed, as opposed to hanging around persistently.
Given apt usually eats over a hundred meg when processing the archive
index, it's probably
This looks to be working under mantic now; image properties pane appears
with resolution and (if present) EXIF details.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/2007160
Argh! During ISO testing I thought I'd just quickly check this still
didn't occur on a Pi 5... only to find it did, this time. I've still not
encountered a Pi 4 where it *didn't* occur, but I wonder if this is a
race-condition somewhere and just more prone to occurring on the slower
4.
--
You
Oh, one other note: no output in the journal during the hang; I'm afraid
the only info is from the backtrace.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2037017
Additional observation: I re-tested this on the Pi 4 and 5. The hang
only occurs on the Pi 4 and 400, but does *not* occur on the 5
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
Attaching backtrace from gdb with debug symbols
** Attachment added: "gdb.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037017/+attachment/5708243/+files/gdb.txt
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Confirmed
--
You received
With the correct video codecs installed (for the particular test video I
was using, I needed gstreamer1.0-plugins-bad which pulls in libav), this
now works on the mantic final images, under both the Pi 4 and 5.
** Changed in: totem (Ubuntu)
Status: Confirmed => Fix Released
--
You
Public bug reported:
On the Ubuntu Desktop for Raspberry Pi current Mantic beta images (with
gnome-control-center version 1.45.0-1ubuntu1), on a Raspberry Pi 4B,
switching to the "Sharing" tab hangs the application (presenting the
Force Quit / Wait overlay prompt).
Worse, re-launching the
Public bug reported:
Under the current Mantic beta, Firefox redundantly appears twice in the
Web and Photos drop-downs under the "Default Apps" tab of gnome-control-
center.
** Affects: gnome-control-center (Ubuntu)
Importance: Low
Status: New
** Changed in: gnome-control-center
*** This bug is a duplicate of bug 1794064 ***
https://bugs.launchpad.net/bugs/1794064
** This bug has been marked a duplicate of bug 1794064
Clicking a hyperlink in a PDF fails to open it if the default browser is a
snap
--
You received this bug notification because you are a member of
Also verified on a Pi 4 (mutter 44.1-0ubuntu1); video playback is smooth
again!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2017097
Title:
[raspi] GNOME Shell 44.0 runs at 30
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
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 Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/861493
Title:
evince doesn't print
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
Fails with this monitor: https://www.edid.tv/edid/2267/
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1998716
Title:
[raspi] Ubuntu 22.10 does not turn off monitor
To manage
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
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 Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
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
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
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1989615
Title:
gnome-shell crashed with SIGABRT in assertion
** 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.
@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
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
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’
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 Ubuntu
Desktop Bugs, which is subscribed to totem
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
@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 Ubuntu
Desktop Bugs, which is subscribed to totem in
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
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
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
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
@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
** Changed in: totem (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1969512
Title:
totem unable to play bbb mp4: "The specified movie
Hmm, some interesting updates here. Firstly, here's the output from
totem when run with "G_MESSAGES_DEBUG=all":
(totem:38425): GLib-GIO-DEBUG: 11:13:06.494: _g_io_module_get_default: Found
default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’
(totem:38425): dconf-DEBUG:
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
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
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
@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
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
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
Public bug reported:
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.
These
I've just test this can confirm the bug, same could not connect to
server message after about a minute of attempting to connect.
--
Totem BBC plugin cannot connect
https://bugs.launchpad.net/bugs/528728
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
54 matches
Mail list logo
