twilightened
Posts: 157
Joined: Fri Sep 03, 2021 12:31 am

Re: STICKY: Bullseye - Comments and bug reports thread.

Sat Jun 04, 2022 7:14 pm

drmullins wrote:
Fri Jun 03, 2022 6:20 pm
Install chromium arm64 fron flatpak or snaps. Both work well.
Do they play drm content?

drmullins
Posts: 160
Joined: Fri Jun 23, 2017 9:22 pm
Location: Lambeth, London, UK

Re: STICKY: Bullseye - Comments and bug reports thread.

Sun Jun 05, 2022 8:21 am

I think you need to install chromium-ffmpeg to play drm in the snaps version but I haven't tried it.

twilightened
Posts: 157
Joined: Fri Sep 03, 2021 12:31 am

Re: STICKY: Bullseye - Comments and bug reports thread.

Sun Jun 05, 2022 12:20 pm

drmullins wrote:
Sun Jun 05, 2022 8:21 am
I think you need to install chromium-ffmpeg to play drm in the snaps version but I haven't tried it.
Bu what is the exact difference between these versions and the official RPI release? Why are you recommending me unofficial versions to install? Shouldn't the official release be the most compatible always?

drmullins
Posts: 160
Joined: Fri Jun 23, 2017 9:22 pm
Location: Lambeth, London, UK

Re: STICKY: Bullseye - Comments and bug reports thread.

Sun Jun 05, 2022 1:25 pm

Of course the official version should be best but the Ubuntu snaps version has substantial corporate backing from a commercial organisation which is proudly promoting snaps against the odds. I like the way it performs. If you are happy with the official version stick with it. I only suggested you try snaps version because you didn't seem to be happy with the official version.
If you identify specific problems with the official version you can report them on the chromium-browser repo of the github RPi-Distro repository.

twilightened
Posts: 157
Joined: Fri Sep 03, 2021 12:31 am

Re: STICKY: Bullseye - Comments and bug reports thread.

Mon Jun 06, 2022 9:47 pm

drmullins wrote:
Sun Jun 05, 2022 1:25 pm
Of course the official version should be best but the Ubuntu snaps version has substantial corporate backing from a commercial organisation which is proudly promoting snaps against the odds. I like the way it performs. If you are happy with the official version stick with it. I only suggested you try snaps version because you didn't seem to be happy with the official version.
If you identify specific problems with the official version you can report them on the chromium-browser repo of the github RPi-Distro repository.
OK i'll try installing snap version. Can i have it side by side with the official release? Or should i uninstall the official one first?

drmullins
Posts: 160
Joined: Fri Jun 23, 2017 9:22 pm
Location: Lambeth, London, UK

Re: STICKY: Bullseye - Comments and bug reports thread.

Tue Jun 07, 2022 9:36 am

I think you need to use the arm64 - 64 bit version of Raspberry Pi OS Bullseye. I don't suppose there are 32 bit versions in snaps or flatpak. You can leave the official one installed, provided you have plenty of spare disk space, and start the snaps version using 'snap run chromium' from terminal window. If you like the snaps version all you have to so is create a file named chromium in /home/pi/bin/ with the following content :

#!/bin/bash
snap run chromium $1 $2 $3

If needs be create /home/pi/bin directory first
Also set execute permission for the new file.

the command 'chromium' will now start the snaps version as executable commands in /home/pi/bin override the standard commands.

You may also want to try the Red Hat sponsored flatpak version (not sure how you run drm content though but there will likely be some way) which you would start with
'flatpak run org.chromium.Chromium' in a terminal window

I have all three installed

I'd be interested to know how you get on.

Actually I am running all these on the debian arm64 version of Bullseye on which Raspberry Pi OS arm64 version is based - and the standard debian version of chromium fails with 'stack smashing' which is why I tried the two alternatives. chromium-browser is specific to Raspberry Pi OS which is why I have installed chromium from the debian repository and can't install chromium-browser.

killiia
Posts: 7
Joined: Tue Dec 08, 2020 11:56 am

Re: STICKY: Bullseye - Comments and bug reports thread.

Thu Jun 23, 2022 11:11 am

Does anyone else experience these freezes (see below)?

This happens every ~3 hours of operation.

The system is unresponsive (headless), Application crashes, but ssh/dmesg still works. I have to hard-reset it.

Is somethin off with the Graphics Driver?

Code: Select all

[   48.246010] uart-pl011 fe201000.serial: no DMA platform data
[ 6905.208558] BUG: Bad rss-counter state mm:00000000d16954c6 type:MM_ANONPAGES val:32
[ 8275.798010] Unable to handle kernel paging request at virtual address 84807d7871706b7a
[ 8275.798040] Mem abort info:
[ 8275.798046]   ESR = 0x96000004
[ 8275.798053]   EC = 0x25: DABT (current EL), IL = 32 bits
[ 8275.798061]   SET = 0, FnV = 0
[ 8275.798067]   EA = 0, S1PTW = 0
[ 8275.798073]   FSC = 0x04: level 0 translation fault
[ 8275.798079] Data abort info:
[ 8275.798084]   ISV = 0, ISS = 0x00000004
[ 8275.798090]   CM = 0, WnR = 0
[ 8275.798096] [84807d7871706b7a] address between user and kernel address ranges
[ 8275.798105] Internal error: Oops: 96000004 [#1] PREEMPT SMP
[ 8275.798112] Modules linked in: rtc_pcf85063 regmap_i2c ov9281 brcmfmac brcmutil cfg80211 vc4 cec drm_kms_helper v3d rfkill gpu_sched snd_soc_core gpio_keys i2c_mux_pinctrl snd_compress bcm2835_unicam snd_pcm_dmaengine rpivid_hevc(C) v4l2_dv_timings raspberrypi_hwmon i2c_mux i2c_brcmstb v4l2_fwnode snd_pcm bcm2835_isp(C) v4l2_async bcm2835_codec(C) bcm2835_v4l2(C) bcm2835_mmal_vchiq(C) v4l2_mem2mem videobuf2_dma_contig videobuf2_vmalloc videobuf2_memops i2c_bcm2835 videobuf2_v4l2 videobuf2_common snd_timer vc_sm_cma(C) videodev snd mc syscopyarea sysfillrect sysimgblt fb_sys_fops nvmem_rmem uio_pdrv_genirq uio drm fuse drm_panel_orientation_quirks backlight ip_tables x_tables ipv6
[ 8275.798234] CPU: 0 PID: 568 Comm: Xorg Tainted: G         C        5.15.48-v8+ #1563
[ 8275.798241] Hardware name: Raspberry Pi Compute Module 4 Rev 1.0 (DT)
[ 8275.798246] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 8275.798253] pc : dma_resv_wait_timeout+0xec/0x3e0
[ 8275.798268] lr : dma_resv_wait_timeout+0x5c/0x3e0
[ 8275.798274] sp : ffffffc00924bb70
[ 8275.798278] x29: ffffffc00924bb70 x28: ffffff8001801040 x27: ffffff8001801078
[ 8275.798289] x26: ffffff8001a21900 x25: 0000000000000000 x24: ffffffc00924bd48
[ 8275.798298] x23: 0000000000000001 x22: 0000000000000001 x21: 0000000000000001
[ 8275.798307] x20: 00000000000391c4 x19: ffffff8001801078 x18: 0000000000000000
[ 8275.798316] x17: 0000000000000000 x16: ffffffe22a583fa0 x15: 0000007fe5a31b48
[ 8275.798326] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000
[ 8275.798334] x11: 0000000000000040 x10: ffffff804705c048 x9 : ffffffe22a583ffc
[ 8275.798344] x8 : ffffff800296c028 x7 : 0000000000000000 x6 : 0000000000000000
[ 8275.798352] x5 : ffffff800296c000 x4 : 000000006b656e6d x3 : 000000006b656e6c
[ 8275.798361] x2 : 0000000000000000 x1 : 000000006b656e6c x0 : 84807d7871706b5a
[ 8275.798370] Call trace:
[ 8275.798374]  dma_resv_wait_timeout+0xec/0x3e0
[ 8275.798380]  drm_gem_dma_resv_wait+0x74/0x128 [drm]
[ 8275.798487]  v3d_wait_bo_ioctl+0x5c/0xd0 [v3d]
[ 8275.798506]  drm_ioctl_kernel+0xc8/0x118 [drm]
[ 8275.798587]  drm_ioctl+0x21c/0x450 [drm]
[ 8275.798667]  __arm64_sys_ioctl+0xb0/0xf0
[ 8275.798674]  invoke_syscall+0x4c/0x110
[ 8275.798682]  el0_svc_common.constprop.3+0xfc/0x120
[ 8275.798689]  do_el0_svc+0x2c/0x90
[ 8275.798695]  el0_svc+0x24/0x60
[ 8275.798702]  el0t_64_sync_handler+0x90/0xb8
[ 8275.798708]  el0t_64_sync+0x1a0/0x1a4
[ 8275.798716] Code: f9401b80 12000019 37001180 f9400780 (f9401001)
[ 8275.798723] ---[ end trace 999ffbbaad0a6916 ]---

trljbrlj
Posts: 2
Joined: Thu Jun 23, 2022 6:32 pm

Re: STICKY: Bullseye - Comments and bug reports thread.

Thu Jun 23, 2022 6:42 pm

Calibre doesn't work.

schufti
Posts: 16
Joined: Mon Jun 25, 2012 9:30 pm

Bluetooth dead on 64bit ???

Fri Jun 24, 2022 9:48 am

I know that I had my BT speaker (Alexa) connected under 64bit bullseye back in march.
Now it nor anything else does show up in "add device" dialog (stays mostly empty in 64bit, sometimes my mobile shows up).
It is working under 32bit though.
bluetooth status seems to be the same in both cases.

64bit:
root@rPi400:/home/pi# /etc/init.d/bluetooth status
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2022-06-23 18:21:19 CEST; 1min 20s ago
Docs: man:bluetoothd(8)
Main PID: 761 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 4164)
CPU: 78ms
CGroup: /system.slice/bluetooth.service
└─761 /usr/libexec/bluetooth/bluetoothd

Jun 23 18:21:19 rPi400 systemd[1]: Starting Bluetooth service...
Jun 23 18:21:19 rPi400 bluetoothd[761]: Bluetooth daemon 5.55
Jun 23 18:21:19 rPi400 systemd[1]: Started Bluetooth service.
Jun 23 18:21:19 rPi400 bluetoothd[761]: Starting SDP server
Jun 23 18:21:19 rPi400 bluetoothd[761]: Bluetooth management interface 1.21 initialized
Jun 23 18:21:19 rPi400 bluetoothd[761]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Jun 23 18:21:19 rPi400 bluetoothd[761]: sap-server: Operation not permitted (1)
Jun 23 18:21:19 rPi400 bluetoothd[761]: Endpoint registered: sender=:1.23 path=/MediaEndpoint/A2DPSink/sbc
Jun 23 18:21:19 rPi400 bluetoothd[761]: Endpoint registered: sender=:1.23 path=/MediaEndpoint/A2DPSource/sbc
Jun 23 18:21:19 rPi400 bluetoothd[761]: Failed to set privacy: Rejected (0x0b)
root@rPi400:/home/pi#
32bit:
root@rPi400:/home/pi# /etc/init.d/bluetooth status
* bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2022-06-23 19:03:35 CEST; 13s ago
Docs: man:bluetoothd(8)
Main PID: 2634 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 4915)
CGroup: /system.slice/bluetooth.service
`-2634 /usr/lib/bluetooth/bluetoothd

Jun 23 19:03:35 rPi400 systemd[1]: Starting Bluetooth service...
Jun 23 19:03:35 rPi400 bluetoothd[2634]: Bluetooth daemon 5.50
Jun 23 19:03:35 rPi400 systemd[1]: Started Bluetooth service.
Jun 23 19:03:35 rPi400 bluetoothd[2634]: Starting SDP server
Jun 23 19:03:35 rPi400 bluetoothd[2634]: Bluetooth management interface 1.18 initialized
Jun 23 19:03:35 rPi400 bluetoothd[2634]: Sap driver initialization failed.
Jun 23 19:03:35 rPi400 bluetoothd[2634]: sap-server: Operation not permitted (1)
Jun 23 19:03:35 rPi400 bluetoothd[2634]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSource
Jun 23 19:03:35 rPi400 bluetoothd[2634]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSink
root@rPi400:/home/pi#
sb knows what is going on?
Any help appreciated,
schufti

schufti
Posts: 16
Joined: Mon Jun 25, 2012 9:30 pm

Re: STICKY: Bullseye - Comments and bug reports thread.

Fri Jun 24, 2022 3:12 pm

ok, so after full update on 32bit, it stopped working too.
In "Add Device..." it stopped showing all the BT devices with only mac addresses, only device visible is my mobile.
Connecting to Alexa works via "Make Discoverable" and start BT search on Alexa only.
After confirming the PIN request, I see "Echo Dot-DLM" connected but volume control claims that there are no audio devices found.

Edit: and after a reboot it doesn't reconnect. Has to be deleted and newly repaired to connect but not really work again...

WHY does nobody test images/updates before they are released on STABLE ???

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

Re: STICKY: Bullseye - Comments and bug reports thread.

Fri Jun 24, 2022 5:20 pm

Did you disable Bluetooth with the icon on taskbar and enable it again?

If you did this is a problem I've come up against check here

viewtopic.php?t=332688

This will also help restart Bluetooth and maybe help sort your issue.

schufti
Posts: 16
Joined: Mon Jun 25, 2012 9:30 pm

Re: STICKY: Bullseye - Comments and bug reports thread.

Fri Jun 24, 2022 9:04 pm

Hi,
thanks for your reply, but I found this thread allready.
I tried even with freshly installed images (via installer) to no avail.

Final: it is working BUT ....

a) not with the Alexa - what was defintely working on 64bit back in march.
as mentioned before, it does pair but fails to show up as audio device - and is in zombie state after reboot.
I still have a older 32bit image where it is working a treat.

b) the "add device" window seems to work different now, it only shows BT devices in pairing mode.

c) had to get another BT-speaker just to regain functionality that previously existed 8(

twilightened
Posts: 157
Joined: Fri Sep 03, 2021 12:31 am

Re: STICKY: Bullseye - Comments and bug reports thread.

Wed Jun 29, 2022 2:37 pm

Can't use Spotify web player under Chromium anymore. It brings the whole system to a halt unless you close the Spotify tab. It was perfectly fine yesterday. I didn't change anything (other than confirming system updates of the RPI OS).

UPDATE: I just installed a new set of updates. This problem seems to have been fixed now. It is nice to see the RPI team is really fast with the fixes.

Return to “Raspberry Pi OS”