After the update, I started to have this weird issue, that I’m not sure how to troubleshoot.
When loading a YouTube video in firefox, the page loads fine, but there is no player or video.
Video playback works fine on other devices and when using mpv+ytdl.
So it’s not network issue.
Running in safe mode profile results in the same issue.
Not sure if this is the place to report it, but I guess it has something to do with mesa driver since I’m using hardware accelerated decoding.
EDIT:
Yup, switching to SW decoding solve it.
Not sure if anyone else is having the same issue.
chromium-112.0.5615.49-1-x86_64 89.0 MiB 576 KiB/s 02:38 [####################################################] 100%
Total ( 7/65) 406.4 MiB 2.56 MiB/s 02:39 [####################################################] 100%
error: failed retrieving file 'lib32-mesa-23.0.1-2.1-x86_64.pkg.tar.zst.sig' from mirror.alpix.eu : Operation too slow. Less than 1 bytes/sec transferred the last 10 seconds
error: failed retrieving file 'noto-fonts-20230401-1-any.pkg.tar.zst.sig' from mirror.alpix.eu : Operation too slow. Less than 1 bytes/sec transferred the last 10 seconds
warning: failed to retrieve some files
Hey @philm, I’m one of the users who are facing the no such cryptodisk found issue that doesn’t actually prevent boot (so pressing a key/waiting will trigger boot), I was wondering a couple things, sorry if I’m being thick:
Should I apply the 20230406 update if I’m still facing the issue, or am I supposed to have solved the issue first?
When you say check grub.cfg for entries like cryptomount -u 3722dfb2-... and try to remove the dash separators: does this advice apply to those who are still able to boot? I’m worried that doing this will cause the full-on boot-blocking issue in my case. I have tried the other solutions suggested (short of sudo grub-install) to no avail.
Chromium HW acceleration appears to be broken for me, but hopefully it will come back in a future update. No worries, I can wait for the fix from upstream.
Same issue here, Chromium does not manage to initialize graphics acceleration:
[42307:42307:0406/151139.659447:ERROR:angle_platform_impl.cc(43)] Display.cpp:1019 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1654.
ERR: Display.cpp:1019 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1654.
[42307:42307:0406/151139.659593:ERROR:gl_display.cc(504)] EGL Driver message (Critical) eglInitialize: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1654.
[42307:42307:0406/151139.659643:ERROR:gl_display.cc(793)] eglInitialize SwANGLE failed with error EGL_NOT_INITIALIZED
[42307:42307:0406/151139.659684:ERROR:gl_display.cc(819)] Initialization of all EGL display types failed.
[42307:42307:0406/151139.659721:ERROR:gl_ozone_egl.cc(26)] GLDisplayEGL::Initialize failed.
[42307:42307:0406/151139.660053:ERROR:angle_platform_impl.cc(43)] Display.cpp:1019 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1654.
ERR: Display.cpp:1019 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1654.
[42307:42307:0406/151139.660116:ERROR:gl_display.cc(504)] EGL Driver message (Critical) eglInitialize: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1654.
[42307:42307:0406/151139.660158:ERROR:gl_display.cc(793)] eglInitialize SwANGLE failed with error EGL_NOT_INITIALIZED
[42307:42307:0406/151139.660196:ERROR:gl_display.cc(819)] Initialization of all EGL display types failed.
[42307:42307:0406/151139.660234:ERROR:gl_ozone_egl.cc(26)] GLDisplayEGL::Initialize failed.
[42307:42307:0406/151139.661750:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
For now, downgrading back to Chromium 111 from the last release works just fine for me.
In my case I still have the isue with grub (…press any key). I tried a solution posted but that did not work for me. In fact I did a fresh install a few days ago and made the update. So today I made this update (april 6) and it worked well.
There are multiple things which can cause that issue. cryptsetup package had changes for systemd 253. However we still ship 252, which doesn’t have that. Hence I reverted those changes on the cryptsetup package to match our systemd series. So yes, apply the update and see if that magically solves your issue. Take part at the discussion we have about that topic and report back your finding: Can't boot LUKS encrypted install after 2023-03-31 stable update
If someone can still boot, we call it a nag screen. Since we don’t know what the actual issue is, those community suggestions helped some of our users. As soon as there is a solution or guideline we will update the information. So far it is partly guessing. You can read my take on it to have more info about it.
I’m also getting this not such cryptodisk found line (but booting with no problem for now). In my case is most probably triggered for I’m keeping the systemd 251 till 252 is out (I don’t want to loose the timed suspend-then-hibernate option that was removed with 252, and is planned again for 253). So, I guess that 252 is coming not much later, and I can live with that for now.
Just, I saw the information about not using dashes for the UUID for LUKS devices in grub… Should then everyone change that line yet, wait if it’s working (with just the line showed), or what is the recommended procedure? Perhaps just try to modify the line directly in grub when booting, to check if it makes any difference, before changing anything permanently?
Thanks!
EDIT: after trying changing manually from grub menu to confirm it works properly, just taking out (manually) the dashes from the cryptomount -u lines in /boot/grub/grub.config , as suggested, avoids the (no so) annoying prompt. So, by now it’s an easy solution, to be applied whenever grub is updated; and probably future upgrades will solve it completely. Thanks again!
After this update, it might have even been the 23.03.31 one, Gwenview hangs when playing an .mp4 file and after it finishes, you go to the next item, be that a pic or vid. You see the little wheel spinning in the center and can not but force the application quit.
There is no such bug when the video is still playing or when you move backwards. Also, changing to the Browse overview in Gwenview once the video has finished playing hangs the application.
There was a similar bug some years ago, fixed without confirmation, which might have been Qt related: show_bug.cgi?id=344809
The bug didn’t exist before the 2 most recent update cycles.
Reinstalling Gwenview, rebooting, to no avail.
I applied the update, but the nag screen persists unfortunately. I’ll post an update on the main thread.
Thanks for the explanations!
UPDATE: @brn is reporting here that removing the dash separators in grub.cfg has removed the nag screen issue: applying this fix solved the issue in my case too!