Thanks, that explain, and I think we have an understanding of each of
the disks/graphics/cpu causes now!
** Changed in: gnome-control-center (Ubuntu)
Status: Confirmed => Triaged
** Summary changed:
- I have no processor!
+ incorrect cpu/graphics/disks information on raspi
--
You
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
Is the renderer result different if MESA_GL_VERSION_OVERRIDE=3.3 is
exported? It could be similar to
https://gitlab.gnome.org/GNOME/gtk/-/issues/2619
** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #2619
https://gitlab.gnome.org/GNOME/gtk/-/issues/2619
--
You received this bug
> gnome-control-center-printer-renderer produces no output on the raspi.
the code basically does
context = gdk_window_create_gl_context (gtk_widget_get_window (win),
NULL);
if (!context)
return NULL;
gdk_gl_context_make_current (context);
renderer
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’
What's the output of /usr/libexec/gnome-control-center-print-renderer on the
raspi?
and
$ G_MESSAGES_DEBUG=all gnome-control-center info-overview
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
On the disk issue, there are some related discussion on
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/633
but basically gnome-control-center currently ignore removable devices
because it shouldn't account for a connected usb stick or sdcard as
system capacity
one suggested
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Confirmed
--
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/1964601
Title:
I have no processor!
Thanks for the details.
I've added the cpuinfo to the libgtop report. It does somehow sound like
a kernel issue though that the cpu details are not provided.
I can try to upstream the other problems, it seems they are each worth a
report on gnome-control-center, but if you want to do it directly
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
Thank you for your bug report.
The CPU missing has been reported upstream on
https://gitlab.gnome.org/GNOME/libgtop/-/issues/60
Could you provide the content of /proc/cpuinfo on the raspi?
And what is the output of
$ glxinfo | grep 'OpenGL renderer string'
And could you add the log generated
12 matches
Mail list logo
