User avatar
raymate
Posts: 178
Joined: Sat Sep 28, 2013 3:56 pm
Location: Canada / UK

Re: Bullseye - Comments and bug reports thread.

Fri Nov 12, 2021 8:16 pm

AkulaMD wrote:
Tue Nov 09, 2021 10:36 am
jamesh wrote:
Tue Nov 09, 2021 10:09 am
AkulaMD wrote:
Tue Nov 09, 2021 9:45 am
The "CPUFreq frontend" Panel Applet no longer appear on the taskbar (after added) with "Bullseye". It used to work just fine with "Buster".
I think that is the one that doesn't like GTK3. There is another applet for CPU that does work.
I'm using all 3 of them (including the CPU Usage and CPU Temperature) with Buster. Hope the missing of the "CPUFreq frontend" applet in Bullseye would just be a temporary hiccup.
2nd that, I use all three its my default setup on every Pi I have, its good to see what the clock speed is when your using the Pi's, its also a great quick way to make sure your overclock has taken. Wonder who created the Applet? perhaps someone could contact them to update or create a new version. The new OS needs time to work out the bugs, its not a snappy thats for sure.. but with time it should be good.
___________________________________________________________________
Pi model B / Pi 2 / Pi 3 / Pi 4 / Pi 400 / Pi Zero W / Pi Zero 2 W / Pico

RonR
Posts: 3037
Joined: Tue Apr 12, 2016 10:29 pm
Location: US

Re: Bullseye - Comments and bug reports thread.

Fri Nov 12, 2021 8:23 pm

2021-10-30-raspios Bullseye 32-bit/64-bit fully updated on Raspberry Pi 4B/4G:

Keyboard input to Chromium address bar lags by 5 seconds when VNC is being used. No lag when monitor+USB keyboard used instead of VNC.

No other applications (Terminal, Text Editor, etc.) have any keyboard input lag when VNC is being used.

User avatar
billybangleballs
Posts: 191
Joined: Fri May 18, 2012 11:28 pm

Re: Bullseye - Comments and bug reports thread.

Fri Nov 12, 2021 8:33 pm

Youtube playback is a joke, the video stops and starts constantly.
There is a general, noticeable, lag between clicking/typing before anything happens.
I've gone back to using buster, because bullseye is unusable in its present state.

Given the choice between 'open sauce' and 'usable', I'd go with usable every time.
Keep working on it, I'm sure you'll get there eventually.
Last edited by billybangleballs on Fri Nov 12, 2021 8:50 pm, edited 1 time in total.
Grumpy old man.
Ex-G0KAP - I'd rather be doing it than talking about it.
"When found, make a note of." - Captain Cuttle

DarkElvenAngel
Posts: 2495
Joined: Tue Mar 20, 2018 9:53 pm

Re: Bullseye - Comments and bug reports thread.

Fri Nov 12, 2021 8:34 pm

I was looking at the setting for the Updater Applet, it would be nice if we could set a time for each check rather than in hours. I would suggest making the check on boot optional and having the ability to set either a check every x hour(s) or to do the check at some time.

I like the feature of the updater however I've gotten updates twice today due to reboots for one or two packages.

User avatar
raymate
Posts: 178
Joined: Sat Sep 28, 2013 3:56 pm
Location: Canada / UK

Re: Bullseye - Comments and bug reports thread.

Fri Nov 12, 2021 8:46 pm

billybangleballs wrote:
Fri Nov 12, 2021 8:33 pm
Youtube playback is a joke, the video stops and starts constantly.
There is a general, noticeable, lag between clicking/typing before anything happens.
I've gone back to using buster, because bullseye is unusable in its present state.
Agreed im not upgrading any of my in use PI's that run 24/7 doing stuff.
___________________________________________________________________
Pi model B / Pi 2 / Pi 3 / Pi 4 / Pi 400 / Pi Zero W / Pi Zero 2 W / Pico

pidd
Posts: 4429
Joined: Fri May 29, 2020 8:29 pm
Location: Wirral, UK

Re: Bullseye - Comments and bug reports thread.

Sat Nov 13, 2021 2:16 am

Biggest disappointment so far is the loss of the "Always on Top" option for windows (especially LXTerminal).

LTolledo
Posts: 6657
Joined: Sat Mar 17, 2018 7:29 am
Location: Anime Heartland

Re: Bullseye - Comments and bug reports thread.

Sat Nov 13, 2021 2:30 am

I tried installing RPiOS32 Bullseye Desktop in a RPi3B+ using a 16GB Sandisk A1 microSD
the install completed fine without problems
then added some of my fave app (that I know will have no problems)
boot up was quite good

then transferred that same microSD to my BreadboardPi (RPi1B+)
boot up to desktop....
took nearly 2 hrs to show desktop log-in screen (and it was supposed to be auto-login as setup in RPi3B+)
30 minutes after logging in the screen blanked
the green LED is still showing some sort of activity...
tried moving the mouse
returned me to the log-in screen
aborted..

moving the microSD back to RPi3B+
it booted normally to desktop in less than a minute
"Don't come to me with 'issues' for I don't know how to deal with those
Come to me with 'problems' and I'll help you find solutions"

Some people be like:
"Help me! Am drowning! But dont you dare touch me nor come near me!"

DarkElvenAngel
Posts: 2495
Joined: Tue Mar 20, 2018 9:53 pm

Re: Bullseye - Comments and bug reports thread.

Sat Nov 13, 2021 3:08 am

pidd wrote:
Sat Nov 13, 2021 2:16 am
Biggest disappointment so far is the loss of the "Always on Top" option for windows (especially LXTerminal).
I second this! I just found this out myself, doing some tasks I'll keep a terminal or MousePad over the other windows. I hope there is a work around for this

thirose
Posts: 9
Joined: Tue Mar 16, 2021 10:35 pm

Re: Bullseye - Comments and bug reports thread.

Sat Nov 13, 2021 8:51 am

So, has anyone tried switching keyboard languages with shift+capslock or by clicking the keyboard handler flag icon?
Does it work for anyone?
I use "fcitx-mozc" package which gets automatically installed if I choose one of CJK locales on the initial installation wizard. In Fcitx configuation, I choose "Alt+`" as my key combo for triggering input method, but this combo is not recognized when I want to activate input method. It's strange because the combo is recognised in the fcitx global config screen, but when I actually want to use it to activate it is not recognised.

User avatar
pasman1
Posts: 245
Joined: Mon Aug 10, 2020 3:01 pm
Location: Poland

Re: Bullseye - Comments and bug reports thread.

Sat Nov 13, 2021 10:07 am

Hi.
There is error when opening youtube.com in chromium:

Code: Select all

$ chromium-browser 
[12012:12012:1113/110232.055748:ERROR:gpu_init.cc(441)] Passthrough is not supported, GL is egl
[1113/110246.159479:ERROR:elf_dynamic_array_reader.h(61)] tag not found
Segmentation fault

$ chromium-browser --version
Chromium 92.0.4515.98 Built on Raspbian , running on Raspbian 11

Pi4-4G RaspiOS 32 BuLlSeYe

User avatar
kerry_s
Posts: 4924
Joined: Thu Jan 30, 2020 7:14 pm

Re: Bullseye - Comments and bug reports thread.

Sat Nov 13, 2021 10:42 am

pasman1 wrote:
Sat Nov 13, 2021 10:07 am
Hi.
There is error when opening youtube.com in chromium:

Code: Select all

$ chromium-browser 
[12012:12012:1113/110232.055748:ERROR:gpu_init.cc(441)] Passthrough is not supported, GL is egl
[1113/110246.159479:ERROR:elf_dynamic_array_reader.h(61)] tag not found
Segmentation fault

$ chromium-browser --version
Chromium 92.0.4515.98 Built on Raspbian , running on Raspbian 11

delete this cookie & you can get in. You'll need to delete it every time you leave youtube.
Attachments
2021-11-12-233209_689x70_scrot.png
2021-11-12-233209_689x70_scrot.png (7.8 KiB) Viewed 3389 times

talraash
Posts: 27
Joined: Wed Apr 29, 2020 10:03 pm

Re: Bullseye - Comments and bug reports thread.

Sat Nov 13, 2021 11:22 am

pidd wrote:
Sat Nov 13, 2021 2:16 am
Biggest disappointment so far is the loss of the "Always on Top" option for windows (especially LXTerminal).
Just change wm to openbox

Code: Select all

sudo nano /etc/xdg/lxsession/LXDE-pi/desktop.conf
comment mutter #window_manager=mutter
and add
window_manager=openbox
restart display manager or just reboot pi.
It's a mystery for me why mutter is used by default not as experimental feature. Smooth windows animations and effects vs huge resource utilization and lot of bugs.
Last edited by talraash on Sat Nov 13, 2021 11:37 am, edited 2 times in total.

User avatar
pasman1
Posts: 245
Joined: Mon Aug 10, 2020 3:01 pm
Location: Poland

Re: Bullseye - Comments and bug reports thread.

Sat Nov 13, 2021 11:29 am

kerry_s wrote:
Sat Nov 13, 2021 10:42 am
delete this cookie & you can get in. You'll need to delete it every time you leave youtube.
This works, but I need to be log in youtube.
I installed firefox-esr.
Pi4-4G RaspiOS 32 BuLlSeYe

User avatar
kerry_s
Posts: 4924
Joined: Thu Jan 30, 2020 7:14 pm

Re: Bullseye - Comments and bug reports thread.

Sat Nov 13, 2021 11:42 am

pasman1 wrote:
Sat Nov 13, 2021 11:29 am
kerry_s wrote:
Sat Nov 13, 2021 10:42 am
delete this cookie & you can get in. You'll need to delete it every time you leave youtube.
This works, but I need to be log in youtube.
I installed firefox-esr.
yeah, i been taking a break from firefox, may end up doing the same.

pidd
Posts: 4429
Joined: Fri May 29, 2020 8:29 pm
Location: Wirral, UK

Re: Bullseye - Comments and bug reports thread.

Sat Nov 13, 2021 1:24 pm

talraash wrote:
Sat Nov 13, 2021 11:22 am
pidd wrote:
Sat Nov 13, 2021 2:16 am
Biggest disappointment so far is the loss of the "Always on Top" option for windows (especially LXTerminal).
Just change wm to openbox

Code: Select all

sudo nano /etc/xdg/lxsession/LXDE-pi/desktop.conf
comment mutter #window_manager=mutter
and add
window_manager=openbox
restart display manager or just reboot pi.
It's a mystery for me why mutter is used by default not as experimental feature. Smooth windows animations and effects vs huge resource utilization and lot of bugs.
Thanks, I can understand them being a bit twitchy on something that hasn't been updated in 7 years but sometimes there's a good reason for that - it works. I'd prefer to stay relatively stock but in this instance mutter is a backward step. I really needed "always on top" to cut and paste settings when putting my system back together last night, I felt handcuffed .... openbox reunion coming up shortly.

Chimneyfactory
Posts: 93
Joined: Sun May 19, 2019 1:30 pm

Re: Bullseye - Comments and bug reports thread.

Sat Nov 13, 2021 2:12 pm

Hi,

I've noticed two issues since a fresh install of Bullseye compared to Buster :

I am tallying some data from 13 web pages into a spreadsheet. I open 13 tabs in Chrome, and open a Libre Office spreadsheet. I then look at each tab in chrome, press alt tab to go back to the spreadsheet, key in a value, alt tab back to Chrome and move to the next Chrome tab. Repeat.

In Buster, once everything is loaded, this is remarkably fast, and you can quickly key the data, alt tabbing between windows quickly and smoothly.

In Bullseye, after Alt Tab to a different window there seems to be a 3-5 second pause where everything is VERY sluggish. Keypresses don't appear, the mouse is very stuttery so that accurate movement is impossible.

Reading in the previous comments about reverting to Openbox, I edited desktop.conf to change mutter to openbox, and I find this problem is resolved. Everything is back to being fast and speedy switching between windows, no keyboard or mouse lag.

(For info, once the pages are loaded, htop shows the cpu load of between 1-6% per core, and memory as 1.33G/3.75G and swapfile usage at 0 so it's not overloaded or swapping.)

Also : Alt Tab behaviour has changed. Previously, Alt Tab would tab between all windows on each press of tab. Now it only toggles between current and previous windows.

Switching back to openbox has restored this behaviour.

Pi is 4b 4GB , Raspberry PI OS installed on an SSD, overclocked to 1900Mhz (stable). Nice and quick and very usable as a daily machine. Sadly and frustratingly, less so with mutter at the present.

Thanks

Ian

pfharlock
Posts: 30
Joined: Sat Oct 08, 2016 1:30 pm

Re: "Screen Configuration" tool does not work on RPi4B

Sat Nov 13, 2021 2:22 pm

beta-tester wrote:
Tue Nov 09, 2021 10:46 am
"Screen Configuration" tool does not work.
i have tried the images 2021-10-30-raspios-bullseye-armhf.zip and 2021-10-30-raspios-bullseye-armhf-full.zip on my RPi4B(4GB).
they are connected to a 4k TV (3840x2160).
out of the box the RaspiOS drives the RPi4B at 4096x2160. because the native resolution of the TV is 3840x2160 and the TV is scaling proportional i have a black bar at the top and bottom (left and right there are no black borders).
i tried to change the resolution in the Screen Configuration tool to 3840x2160 and answered the question to reboot to apply the changes with yes.
but after the reboot nothing changed in the screen resolution. then i tried 1920x1080 and the same happens. after reboot the screen resolution did not changed on the TV. it was still at 4096x2160. in the Screen Configuration tool the current resolution was shown as 1960x1080 that is definitely wrong what was displayed there.

so Screen Configuration tool isn't working for me at all.

for the moment i turned off / comment out in /boot/config.txt
# dtoverlay=vc4-kms-v3d
to have the old display resolution settings in Raspberry Pi Configuration to manage the resolution there - and there the resolution is changing the screen resolution on TV
I can confirm that the "screen configuration" tool is completely broken. It will not save any screen resolution changes which effectively makes my pi useless when running the latest version of raspberry pi OS.

EDIT - update, once I rearranged the screens the settings took effect on reboot. So the bug is, just setting the resolution won't trigger a setting change until you rearrange the windows.

SalsaCrave
Posts: 1
Joined: Sat Nov 13, 2021 1:37 pm

Re: Bullseye - Comments and bug reports thread.

Sat Nov 13, 2021 4:28 pm

Chimneyfactory wrote:
Sat Nov 13, 2021 2:12 pm
Also : Alt Tab behaviour has changed. Previously, Alt Tab would tab between all windows on each press of tab. Now it only toggles between current and previous windows.
Yes, this is so frustrating.

IIRC ctrl+esc could be used to open the main menu in Buster, but it doesn't work in Bullseye.
I had to manually add the keybinding as it only accepts the Super key by default.

Another issue is auto hiding the desktop taskbar does not work properly if a size greater than 0 pixels is set to stay visible when minimized.
One time it leaves behind a black bar that hides windows behind it, the other time it does work like it should.
Basically you need to leave the taskbar twice to succesfully hide it.

Changing the taskbar appearance background color using transparency only makes the taskbar black, not transparent.

And using a widget theme other than the default from lxappearance cuts off the top of the icons on the taskbar.

User avatar
jordana
Posts: 69
Joined: Thu Jan 02, 2020 3:26 pm

Re: Bullseye - Comments and bug reports thread.

Sat Nov 13, 2021 5:27 pm

System clock is not synchronized for me with latest Bullseye image:

Code: Select all

pi@pi02w:~ $ timedatectl status
               Local time: Sat 2021-11-13 16:40:42 GMT
           Universal time: Sat 2021-11-13 16:40:42 UTC
                 RTC time: n/a
                Time zone: Europe/London (GMT, +0000)
System clock synchronized: no
              NTP service: active
          RTC in local TZ: no
pi@pi02w:~ $ timedatectl timesync-status
       Server: fd52:a81c:df85:1:960b:19ff:fe89:7c43 (fd52:a81c:df85:1:960b:19ff:fe89:7c43)
Poll interval: 17min 4s (min: 32s; max 34min 8s)
 Packet count: 0
pi@pi02w:~ $ timedatectl show-timesync
SystemNTPServers=fd52:a81c:df85:1:960b:19ff:fe89:7c43
FallbackNTPServers=0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org
ServerName=fd52:a81c:df85:1:960b:19ff:fe89:7c43
ServerAddress=fd52:a81c:df85:1:960b:19ff:fe89:7c43
RootDistanceMaxUSec=5s
PollIntervalMinUSec=32s
PollIntervalMaxUSec=34min 8s
PollIntervalUSec=17min 4s
Frequency=0
I have no idea where IPv6 NTP server address have come from yet but it does not come from timesyncd.conf...

Code: Select all

pi@pi02w:~ $ cat /etc/systemd/timesyncd.conf 
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See timesyncd.conf(5) for details.

[Time]
#NTP=
FallbackNTP=0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org
#RootDistanceMaxSec=5
#PollIntervalMinSec=32
#PollIntervalMaxSec=2048

User avatar
QBall1977
Posts: 101
Joined: Thu Aug 09, 2012 10:06 am
Location: Hull, East Yorkshire

Re: Bullseye - Comments and bug reports thread.

Sat Nov 13, 2021 10:19 pm

jonwitts wrote:
Wed Nov 10, 2021 11:32 am
jamesh wrote:
Wed Nov 10, 2021 11:10 am
jonwitts wrote:
Wed Nov 10, 2021 10:55 am
Hi, have just installed Bullseye on a PI4 4Gb on an SSD and have started to test out software which we use on our school Raspberry Pis to check if we are good to upgrade to Bullseye.

First off; blender is no longer working... It installs fine but when running from the CLI you get the following error:

"Error! Unsupported graphics card or driver.
A graphics card and driver with support for OpenGL 3.3 or higher is required.
The program will now close."

Is it going to be possible to have the old version of Blender available through Bullseye so we can at least still run it on the Pi?

Jon
Try

LIBGL_ALWAYS_SOFTWARE=1 blender

No idea if it is usable, but it does start up.
Thanks; that gets it running; but it is laggy as hell! The 2.79 version on Buster ran with no lag at all... I will keep testing it, but I don't think that this version is usable from my initial tests... I certainly wouldn't want to try and teach 3D modelling to a room of 30 students with this much lag in the software...
I can confirm this behaviour to. Version 2.79b was fine for a little 3D modelling for 3D Printing, I didn't need rendering. Bullseye installs version 2.8x which the Pi can't run without OpenGL using the above switch. I tried rolling back to version 2.79b, but this does not exist in the RPi software library just version 2.8x. I also thought backports might be a good idea. However this is only from the Debian Stable Branch not the RPI software library and is still version 2.82 (I think) anyone know ANY way of getting Blender 2.79b back on Bullseye for ARMHF without building from source?
____________________________________________
Looking for where to start - try Kernel Panic - http://goo.gl/EEQ5J

kopfsalat
Posts: 10
Joined: Fri Oct 15, 2021 5:06 pm

Re: Bullseye - Comments and bug reports thread.

Sat Nov 13, 2021 10:53 pm

vlc does not use hardare acceleration by default, »MMAL X11 splitter« setting does.

Alt-Tab does only switch between two most recent windows.

edit: +Alt-LeftMouse to move windows does not work +Alt-RightMouse does not resize windows.
Last edited by kopfsalat on Sun Nov 14, 2021 10:01 am, edited 1 time in total.

klricks
Posts: 8595
Joined: Sat Jan 12, 2013 3:01 am
Location: Grants Pass, OR, USA

Re: Bullseye - Comments and bug reports thread.

Sat Nov 13, 2021 11:03 pm

When a desktop icon is moved to new position it will disappear and will not reappear until you mouse click anywhere on the screen.
Unless specified otherwise my response is based on the latest and fully updated RPi OS Bullseye w/ Desktop OS.

SirFico
Posts: 28
Joined: Sat Nov 13, 2021 11:17 pm
Location: UK

Re: Bullseye - Comments and bug reports thread.

Sat Nov 13, 2021 11:35 pm

Silly me I just posted this under a sticky buster thread and I meant to put in the here in the bullseye thread.

Bullseye bug. - if the menu bar is on the top of the screen my pyqt5 program treats the top of the screen as being under the menu bar meaning I don't see the pyqt5's window tittle bar, thus I can get to the minimise or close buttons. On buster the top of the screen is treated as starting from below the title bar (if the title bar is placed on the top of the screen of course) and works OK.

User avatar
QBall1977
Posts: 101
Joined: Thu Aug 09, 2012 10:06 am
Location: Hull, East Yorkshire

Re: Bullseye - Comments and bug reports thread.

Sun Nov 14, 2021 12:22 am

QBall1977 wrote:
Sat Nov 13, 2021 10:19 pm
jonwitts wrote:
Wed Nov 10, 2021 11:32 am
jamesh wrote:
Wed Nov 10, 2021 11:10 am


Try

LIBGL_ALWAYS_SOFTWARE=1 blender

No idea if it is usable, but it does start up.
Thanks; that gets it running; but it is laggy as hell! The 2.79 version on Buster ran with no lag at all... I will keep testing it, but I don't think that this version is usable from my initial tests... I certainly wouldn't want to try and teach 3D modelling to a room of 30 students with this much lag in the software...
I can confirm this behaviour to. Version 2.79b was fine for a little 3D modelling for 3D Printing, I didn't need rendering. Bullseye installs version 2.8x which the Pi can't run without OpenGL using the above switch. I tried rolling back to version 2.79b, but this does not exist in the RPi software library just version 2.8x. I also thought backports might be a good idea. However this is only from the Debian Stable Branch not the RPI software library and is still version 2.82 (I think) anyone know ANY way of getting Blender 2.79b back on Bullseye for ARMHF without building from source?
If anyone has a spare hour here is how to get Blender 2.79b working on Bullseye! - viewtopic.php?t=323796
____________________________________________
Looking for where to start - try Kernel Panic - http://goo.gl/EEQ5J

User avatar
jordana
Posts: 69
Joined: Thu Jan 02, 2020 3:26 pm

Re: Bullseye - Comments and bug reports thread.

Sun Nov 14, 2021 7:39 am

jordana wrote:
Sat Nov 13, 2021 5:27 pm
System clock is not synchronized for me with latest Bullseye image:

Code: Select all

pi@pi02w:~ $ timedatectl status
               Local time: Sat 2021-11-13 16:40:42 GMT
           Universal time: Sat 2021-11-13 16:40:42 UTC
                 RTC time: n/a
                Time zone: Europe/London (GMT, +0000)
System clock synchronized: no
              NTP service: active
          RTC in local TZ: no
pi@pi02w:~ $ timedatectl timesync-status
       Server: fd52:a81c:df85:1:960b:19ff:fe89:7c43 (fd52:a81c:df85:1:960b:19ff:fe89:7c43)
Poll interval: 17min 4s (min: 32s; max 34min 8s)
 Packet count: 0
pi@pi02w:~ $ timedatectl show-timesync
SystemNTPServers=fd52:a81c:df85:1:960b:19ff:fe89:7c43
FallbackNTPServers=0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org
ServerName=fd52:a81c:df85:1:960b:19ff:fe89:7c43
ServerAddress=fd52:a81c:df85:1:960b:19ff:fe89:7c43
RootDistanceMaxUSec=5s
PollIntervalMinUSec=32s
PollIntervalMaxUSec=34min 8s
PollIntervalUSec=17min 4s
Frequency=0
I have no idea where IPv6 NTP server address have come from yet but it does not come from timesyncd.conf...

Code: Select all

pi@pi02w:~ $ cat /etc/systemd/timesyncd.conf 
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See timesyncd.conf(5) for details.

[Time]
#NTP=
FallbackNTP=0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org
#RootDistanceMaxSec=5
#PollIntervalMinSec=32
#PollIntervalMaxSec=2048
I realised that a leftover Vodafone router without a working uplink that I tried to use as a 4 port LAN switch have provided a non-functional IP6 NTP server. So from Bullseye POV this is a feature not a bug :)

Return to “Raspberry Pi OS”