Bug#998125: libasound2-plugins: Config file for a52 plugin (60-a52-encoder.conf) produces no/garbled sound via optical digital out (S/PDIF)
On Tue, 2 Nov 2021 10:14:51 +0100 Jens Schmidt wrote: > Reported upstream as > https://github.com/alsa-project/alsa-plugins/issues/38 > > Thanks for reporting upstream. I'm also experiencing non-working a52 encoding with the libasound2-plugins package shipped with debian (1.2.5-2). On my system, the plugin outputs a digital 2-channel signal without any sound instead of the expected 6-channel AC3 encoded stream. After some researching I found that the main problem is not the configuration files, but changes in the libavcodec encode API that were not handled correctly by the a52 plugin. There were multiple commits in upstream alsa already to fix the issue (see for example here: https://alsa-project.org/wiki/Changes_v1.2.5.1_v1.2.6 ). So I assume that the current version (1.2.5) is just broken with respect to the a52 plugin. I'm looking forward to a new release of 1.2.6 (or newer) to be included in debian, which should hopefully fix the issues again. It would be great if a maintainer could upgrade the debian alsa packages to latest upstream (see also this request https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001697 ) Best regards, Stefan
Bug#977956: Bug#977870: fixed in chromium 87.0.4280.88-0.4
related upstream thread (confirming the issue and the fix for versions >87; just found it in the other thread about https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979017, sorry, didn't see that one earlier) https://bugs.chromium.org/p/chromium/issues/detail?id=1141354 I guess it's best to wait for a newer release of chromium (>87) then, if you plan to use the intel drivers on some systems. Otherwise you could work-around by using the --disable-gpu flag (at the cost of hw accel, though)
Bug#977956: Bug#977870: fixed in chromium 87.0.4280.88-0.4
Hello, some additional info that might be useful: I have a 2nd old box with a SandyBridge processor (core i3-2105). Behavior is similar there (chromium-87 not working properly in fullscreen when intel DDX is running, but working fine with modesetting driver) I also had a look at newer versions of chrome (from http://dl.google.com/linux/chrome/deb/ repository): google-chrome-stable (v87): same full-screen issues as chromium v87 google-chrome-beta (v88): no issues when switching to full-screen google-chrome-unstable (v89): no issues when switching to full-screen When I compare the output of chrome://gpu for the different builds of google-chrome it seems to me that there are quite a lot of changes ongoing. Logs attached, in case you're interested. 87 88 89 Compositing Hardware acceleratedSoftware only. Hardware acceleration disabledHardware accelerated Out-of-process RasterizationDisabledHardware acceleratedDisabled Hardware Protected Video Decode Hardware acceleratedUnavailable Unavailable Rasterization Software only. Hardware acceleration disabled Hardware accelerated Software only. Hardware acceleration disabled Vulkan DisabledEnabled Disabled WebGL Hardware acceleratedHardware accelerated but at reduced performance Hardware accelerated WebGL2 Hardware acceleratedHardware accelerated but at reduced performance Hardware accelerated Graphics Feature Status Canvas: Hardware accelerated Compositing: Hardware accelerated Multiple Raster Threads: Enabled Out-of-process Rasterization: Disabled OpenGL: Enabled Hardware Protected Video Decode: Hardware accelerated Rasterization: Software only. Hardware acceleration disabled Skia Renderer: Enabled Video Decode: Software only. Hardware acceleration disabled Vulkan: Disabled WebGL: Hardware accelerated WebGL2: Hardware accelerated Driver Bug Workarounds adjust_src_dst_region_for_blitframebuffer clear_uniforms_before_first_program_use decode_encode_srgb_for_generatemipmap disable_chromium_framebuffer_multisample exit_on_context_lost msaa_is_slow scalarize_vec_and_mat_constructor_args disabled_extension_GL_KHR_blend_equation_advanced disabled_extension_GL_KHR_blend_equation_advanced_coherent Problems Detected Clear uniforms before first program use on all platforms: 124764, 349137 Applied Workarounds: clear_uniforms_before_first_program_use Multisampling is buggy in Intel IvyBridge: 116370 Applied Workarounds: disable_chromium_framebuffer_multisample Always rewrite vec/mat constructors to be consistent: 398694 Applied Workarounds: scalarize_vec_and_mat_constructor_args On Intel GPUs MSAA performance is not acceptable for GPU rasterization: 527565 Applied Workarounds: msaa_is_slow adjust src/dst region if blitting pixels outside framebuffer on Linux Intel: 664740 Applied Workarounds: adjust_src_dst_region_for_blitframebuffer Disable KHR_blend_equation_advanced until cc shaders are updated: 661715 Applied Workarounds: disable(GL_KHR_blend_equation_advanced), disable(GL_KHR_blend_equation_advanced_coherent) Decode and Encode before generateMipmap for srgb format textures on Linux Mesa ANGLE path: 634519 Applied Workarounds: decode_encode_srgb_for_generatemipmap Some drivers can't recover after OUT_OF_MEM and context lost: 893177 Applied Workarounds: exit_on_context_lost Accelerated video decode has been disabled, either via blocklist, about:flags or the command line. Disabled Features: video_decode ANGLE Features allow_compressed_formats (Frontend workarounds): Enabled: true Allow compressed formats disable_anisotropic_filtering (Frontend workarounds): Disabled Disable support for anisotropic filtering disable_program_binary (Frontend features) anglebug:5007: Disabled Disable support for GL_OES_get_program_binary disable_program_caching_for_transform_feedback (Frontend workarounds): Disabled: IsAndroid() && isQualcomm On some GPUs, program binaries don't contain transform feedback varyings lose_context_on_out_of_memory (Frontend workarounds): Enabled: true Some users rely on a lost context notification if a GL_OUT_OF_MEMORY error occurs scalarize_vec_and_mat_constructor_args (Frontend workarounds) 398694: Enabled: true Always rewrite vec/mat constructors to be consistent sync_framebuffer_bindings_on_tex_image (Frontend workarounds): Disabled: IsWindows() && isIntel On some drivers TexImage sometimes seems to interact with the Framebuffer add_and_true_to_loop_condition (OpenGL workarounds): Disabled: IsApple() && isIntel Calculation of loop conditions in for and while loop has bug adjust_src_dst_region_for_blitframebuffer (OpenGL workarounds) 830046: Enabled: IsLinux() || (IsAndroid() && isNvidia) || (IsWindows() && isNvidia) Many platforms have issues with blitFramebuffer when the parameters are large. allow_clear_for_robust_resource_init (OpenGL workarounds) 883276: Disabled: IsApple() Using glClear for robust resource initialization is buggy on
Bug#977956: Bug#977870: fixed in chromium 87.0.4280.88-0.4
On Sat, 02 Jan 2021 13:46:46 +0100 Michel Le Bihan wrote: > Hello, > > I also have an IvyBridge laptop with the i5-3210M and can't reproduce > your issue. Could you please list the graphic related packages that you > have installed and any config changes you have made? > > Michel Le Bihan > Hello, thanks for your support. First of all as a disclaimer: my system is quite the opposite of a "clean" install, rather an old system dist-upgraded continuously from debian/unstable over several years, so there may well be something wrong somewhere. I would fully understand if you can't be bothered with this kind of report, no hard feelings at all in that case. I did some more tests: First I removed /etc/chromium.d/default-flags to make sure that there are now entries that might interfere. Also, I started chromium with --temp-profile Then tried again: 1) using intel driver (custom config /usr/share/X11/xorg.conf.d/20-intel.conf; file attached) starting "chromium --temp-profile" -> seems to work OK, but pressing "F11" causes blinking/unresponsiveness output of "chrome://gpu" is attached starting "chromium --temp-profile --use-gl=desktop" -> becomes unresponsive, even directly or after short use 2) using modesetting driver starting "chromium --temp-profile" -> seems to work OK, pressing "F11" works as expected output of "chrome://gpu" is attached I hope this will be helpful, if you decide to follow up and need more info, please let me know and I'll try to look deeper. Thanks, Stefan Below please find some additional info, as requested: cat /proc/cpuinfo | grep i5 model name : Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz output gathered using "reportbug --template -T none -s none -S normal -b --list-cc none -q chromium" see below -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages chromium depends on: ii chromium-common 87.0.4280.88-0.4 ii libasound2 1.2.4-1 ii libatk-bridge2.0-0 2.38.0-1 ii libatk1.0-0 2.36.0-2 ii libatomic1 10.2.1-3 ii libatspi2.0-0 2.38.0-2 ii libavcodec58 7:4.3.1-5 ii libavformat58 7:4.3.1-5 ii libavutil56 7:4.3.1-5 ii libc6 2.31-6 ii libcairo2 1.16.0-5 ii libcups2 2.3.3op1-4 ii libdbus-1-3 1.12.20-1 ii libdrm2 2.4.103-2 ii libevent-2.1-7 2.1.12-stable-1 ii libexpat1 2.2.10-1 ii libflac8 1.3.3-2 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.10.4+dfsg-1 ii libgbm1 20.2.6-1 ii libgcc-s1 10.2.1-3 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1 ii libglib2.0-0 2.66.4-1 ii libgtk-3-0 3.24.24-1 ii libharfbuzz0b 2.6.7-1 ii libicu67 67.1-5 ii libjpeg62-turbo 1:2.0.5-2 ii libjsoncpp24 1.9.4-4 ii liblcms2-2 2.9-4+b1 ii libminizip1 1.1-8+b1 ii libnspr4 2:4.29-1 ii libnss3 2:3.60-1 ii libopenjp2-7 2.3.1-1 ii libopus0 1.3.1-0.1 ii libpango-1.0-0 1.46.2-3 ii libpangocairo-1.0-0 1.46.2-3 ii libpng16-16 1.6.37-3 ii libpulse0 13.0-5 ii libre2-9 20201101+dfsg-2 ii libsnappy1v5 1.1.8-1 ii libstdc++6 10.2.1-3 ii libwebp6 0.6.1-2+b1 ii libwebpdemux2 0.6.1-2+b1 ii libwebpmux3 0.6.1-2+b1 ii libx11-6 2:1.6.12-1 ii libx11-xcb1 2:1.6.12-1 ii libxcb1 1.14-2.1 ii libxcomposite1 1:0.4.5-1 ii libxdamage1 1:1.1.5-2 ii libxext6 2:1.3.3-1.1 ii libxfixes3 1:5.0.3-2 ii libxml2 2.9.10+dfsg-6.3+b1 ii libxrandr2 2:1.5.1-1 ii libxslt1.1 1.1.34-4 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages chromium recommends: ii chromium-sandbox 87.0.4280.88-0.4 Versions of packages chromium suggests: pn chromium-driver pn chromium-l10n pn chromium-shell Versions of packages chromium-common depends on: ii libc6 2.31-6 ii libstdc++6 10.2.1-3 ii libx11-6 2:1.6.12-1 ii libxext6 2:1.3.3-1.1 ii x11-utils 7.7+5 ii xdg-utils 1.1.3-2 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages chromium-common recommends: ii chromium-sandbox 87.0.4280.88-0.4 ii fonts-liberation 1:1.07.4-11 ii gnome-flashback [notification-daemon] 3.38.0-1 ii gnome-shell [notification-daemon] 3.38.2-1 ii libgl1-mesa-dri
Bug#977956: Bug#977870: fixed in chromium 87.0.4280.88-0.4
On Wed, 30 Dec 2020 17:04:08 + Debian FTP Masters wrote: > Source: chromium > Source-Version: 87.0.4280.88-0.4 > Done: Michel Le Bihan > > We believe that the bug you reported is fixed in the latest version of > chromium, which is due to be installed in the Debian FTP archive. > > [...] Thanks for looking into this issue. On my system (old IvyBridge desktop with intel Gen7 GPU), the latest chromium version is/was still broken when combined with the "intel" DDX driver: without "--use-gl=desktop", chromium starts fine, but the browser UI hangs/freezes when switching to full screen mode (triggered by e.g. pressing F11 or full-screen video) with "--use-gl=desktop" the chromium UI immediately freezes I think chromium around 84 was still fine, with later builds it started breaking. I did some digging and found that the reason for the issue on my system is most likely is a bug in the "intel" DDX driver (and/or) SNA acceleration, which I had manually enabled a long time ago. I switched to "modesetting" driver now, and things look fine now again. Not blaming the chromium developers here, as it looks more like an intel DDX bug* to me. But maybe this info will be helpful for other users. *additional reason why I think its an intel DDX bug: firefox also freezes when enabling GL and WEBRENDER when using intel DDX, but seems to work fine with modesetting/glamoregl
