[Touch-packages] [Bug 1975865] Re: Hash and size mismatch with http://ddebs.ubuntu.com/dists/bionic-updates/main/binary-amd64/Packages.gz
This now happens for noble: ``` Err:12 http://ddebs.ubuntu.com noble/universe amd64 Packages File has unexpected size (5097972 != 5076444). Mirror sync in progress? [IP: 185.125.190.18 80] Hashes of expected file: - Filesize:5076444 [weak] - SHA512:4a12f4b6c12396bf02c70a1a1bd8933d2cf0b7a151c6f1efcd3feb0644392e8539a542499637d7981fd47e5f3dc922d878bb77630aaa47f9be169194e65fbe0c - SHA256:4b2177c1b5f6aa3772056116eb80630a6032445253b9248f06db30cd707bc910 - SHA1:3ba083c6ee31195a7d6851bb14a2c741083fe580 [weak] - MD5Sum:6845e2ee862b5570f928bbd4d2d7525e [weak] Release file created at: Sat, 13 Apr 2024 15:46:30 + Fetched 31.9 MB in 3s (10.4 MB/s) Reading package lists... Done E: Failed to fetch http://ddebs.ubuntu.com/dists/noble/universe/binary-amd64/Packages.xz File has unexpected size (5097972 != 5076444). Mirror sync in progress? [IP: 185.125.190.18 80] Hashes of expected file: - Filesize:5076444 [weak] - SHA512:4a12f4b6c12396bf02c70a1a1bd8933d2cf0b7a151c6f1efcd3feb0644392e8539a542499637d7981fd47e5f3dc922d878bb77630aaa47f9be169194e65fbe0c - SHA256:4b2177c1b5f6aa3772056116eb80630a6032445253b9248f06db30cd707bc910 - SHA1:3ba083c6ee31195a7d6851bb14a2c741083fe580 [weak] - MD5Sum:6845e2ee862b5570f928bbd4d2d7525e [weak] Release file created at: Sat, 13 Apr 2024 15:46:30 + E: Some index files failed to download. They have been ignored, or old ones used instead. ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1975865 Title: Hash and size mismatch with http://ddebs.ubuntu.com/dists/bionic- updates/main/binary-amd64/Packages.gz Status in apt package in Ubuntu: Fix Released Bug description: When adding the debug repos, I am getting: E: Failed to fetch http://ddebs.ubuntu.com/dists/bionic-updates/main/binary-amd64/Packages.gz File has unexpected size (795886 != 795487). Mirror sync in progress? [IP: 91.189.91.49 80] Hashes of expected file: - Filesize:795487 [weak] - SHA512:982169cbaaa6b0fe84e2cac755c140f52c578619beea451baa90234af2cfdaef90ac936eb7a7de24364ee860a6b021f852f11a87b7cd6dcb98923a248bc45a81 - SHA256:4a69b95e20ac09bb3de2d5e3c652b2c027bcfa4d6df9dea0a4aed16c805869e6 - SHA1:11dded397ab87e4fff81acf4aed6af18f8eee0b2 [weak] - MD5Sum:9045f9c8424cf15e897f682708f158b8 [weak] Release file created at: Thu, 26 May 2022 08:04:16 + E: Some index files failed to download. They have been ignored, or old ones used instead. When I manually go to the repositories... many (all?) of the hashes listed in http://ddebs.ubuntu.com/dists/bionic-updates/Release do not match the files (e.g. http://ddebs.ubuntu.com/dists/bionic- updates/main/binary-amd64/Packages.gz ) Note: I filed this against `apt` because `ubuntu-bug` forced me to specify a package and I didn't know any other way to file the bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.14 Uname: Linux 5.16.18-1rodete2-amd64 x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 Date: Thu May 26 18:36:21 2022 ProcEnviron: TERM=xterm PATH=(custom, no user) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1975865/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Bug 1975865] Re: Hash and size mismatch with http://ddebs.ubuntu.com/dists/bionic-updates/main/binary-amd64/Packages.gz
This now happens for noble: ``` Err:12 http://ddebs.ubuntu.com noble/universe amd64 Packages File has unexpected size (5097972 != 5076444). Mirror sync in progress? [IP: 185.125.190.18 80] Hashes of expected file: - Filesize:5076444 [weak] - SHA512:4a12f4b6c12396bf02c70a1a1bd8933d2cf0b7a151c6f1efcd3feb0644392e8539a542499637d7981fd47e5f3dc922d878bb77630aaa47f9be169194e65fbe0c - SHA256:4b2177c1b5f6aa3772056116eb80630a6032445253b9248f06db30cd707bc910 - SHA1:3ba083c6ee31195a7d6851bb14a2c741083fe580 [weak] - MD5Sum:6845e2ee862b5570f928bbd4d2d7525e [weak] Release file created at: Sat, 13 Apr 2024 15:46:30 + Fetched 31.9 MB in 3s (10.4 MB/s) Reading package lists... Done E: Failed to fetch http://ddebs.ubuntu.com/dists/noble/universe/binary-amd64/Packages.xz File has unexpected size (5097972 != 5076444). Mirror sync in progress? [IP: 185.125.190.18 80] Hashes of expected file: - Filesize:5076444 [weak] - SHA512:4a12f4b6c12396bf02c70a1a1bd8933d2cf0b7a151c6f1efcd3feb0644392e8539a542499637d7981fd47e5f3dc922d878bb77630aaa47f9be169194e65fbe0c - SHA256:4b2177c1b5f6aa3772056116eb80630a6032445253b9248f06db30cd707bc910 - SHA1:3ba083c6ee31195a7d6851bb14a2c741083fe580 [weak] - MD5Sum:6845e2ee862b5570f928bbd4d2d7525e [weak] Release file created at: Sat, 13 Apr 2024 15:46:30 + E: Some index files failed to download. They have been ignored, or old ones used instead. ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975865 Title: Hash and size mismatch with http://ddebs.ubuntu.com/dists/bionic- updates/main/binary-amd64/Packages.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1975865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Bug#1051946: libsdl2-dev: sdl2-config --static-libs will fail with clang-16 and above.
Package: libsdl2-dev Version: 2.28.3+dfsg-2 Justification: sdl2-config can fail to get the proper link flags. This used to work with both gcc and clang, but now when using clang, it fails: $ CC=clang-16 sdl2-config --static-libs clang: error: unsupported option '-print-multiarch' clang: error: no input files /usr/lib//libSDL2.a -lm -lasound -lm -ldl -lpthread -lpulse-simple -lpulse -pthread -lsamplerate -lX11 -lXext -lXcursor -lXi -lXfixes -lXrandr -lXss -ldrm -lgbm -lwayland-egl -lwayland-client -lwayland-cursor -lxkbcommon -ldecor-0 -lpthread The reason for this failure is the fact that clang has removed support for the -print-multiarch flag. See: https://github.com/llvm/llvm-project/commit/e05edb19adbfd1b24f58d583e4b5b4d742f982ee I first tried reporting this with Ubuntu, then with SDL2 upstream, but the source of this bug actually stems from a debian patch. See: debian/patches/no-libdir.patch The author of the patch states that: "a compiler for the host architecture that supports the -print-multiarch argument (which Debian's gcc and clang do)" This is no longer true, as clang will not take that flag. The SDL2 upstream will not execute the compiler to determine the library dir. This is debian-specific (and inherited by Ubuntu.) >From my testing, it seems that clang v 16 and above is affected. I have produced this bug on: Ubuntu 23.04 Lunar Lobster Ubuntu 23.10 Mantic Minotaur
[Desktop-packages] [Bug 2009739] Re: hwacc build crashes on direct scanout.
Does not crash when using AMD gpu, instead of Alderlake iGPU. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2009739 Title: hwacc build crashes on direct scanout. Status in chromium-browser package in Ubuntu: New Bug description: This pertains to the HWACC branches of the chromium snap. When launched full-screen on an Intel iGPU, the hardware overlay use will result in a core dump. This could be related to direct-scanout and overlay planes? To reproduce: $ chromium --start-fullscreen OS: Ubuntu 22.10 Chromium: 111.0.5563.19-hwacc GPU: Alderlake iGPU stolk@workpc:/snap/chromium/current/bin$ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/beta/hwacc refresh-date: yesterday at 08:52 PST channels: latest/stable:110.0.5481.177 2023-03-06 (2367) 156MB - latest/candidate: 111.0.5563.64 2023-03-08 (2381) 155MB - latest/beta: 111.0.5563.64 2023-03-07 (2380) 155MB - latest/edge: 112.0.5615.12 2023-03-03 (2375) 156MB - installed: 111.0.5563.19-hwacc(2376) 174MB - stolk@workpc:/snap/chromium/current/bin$ chromium --start-fullscreen [73039:73039:0308/101357.917887:WARNING:chrome_main_delegate.cc(618)] This is Chrome version 111.0.5563.19 (not a warning) [73039:73039:0308/101358.450380:WARNING:wayland_object.cc(152)] Binding to gtk_shell1 version 4 but version 5 is available. [73039:73039:0308/101358.450401:WARNING:wayland_object.cc(152)] Binding to zwp_pointer_gestures_v1 version 1 but version 3 is available. [73039:73039:0308/101358.450416:WARNING:wayland_object.cc(152)] Binding to zwp_linux_dmabuf_v1 version 3 but version 4 is available. Gtk-Message: 10:13:58.455: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. [73039:73039:0308/101358.611145:WARNING:account_consistency_mode_manager.cc(70)] Desktop Identity Consistency cannot be enabled as no OAuth client ID and client secret have been configured. [73039:73039:0308/101358.625559:WARNING:wayland_surface.cc(151)] Server doesn't support zcr_alpha_compositing_v1. [73039:73039:0308/101358.625573:WARNING:wayland_surface.cc(166)] Server doesn't support overlay_prioritizer. [73039:73039:0308/101358.625579:WARNING:wayland_surface.cc(180)] Server doesn't support surface_augmenter. [73039:73039:0308/101358.625583:WARNING:wayland_surface.cc(195)] Server doesn't support wp_content_type_v1 [73039:73039:0308/101358.625586:WARNING:wayland_surface.cc(214)] Server doesn't support zcr_color_management_surface. [73039:73039:0308/101358.625774:WARNING:cursor_loader.cc(123)] Failed to load a platform cursor of type kNull [73039:73039:0308/101358.626013:VERBOSE1:wayland_cursor.cc(151)] Failed to hide cursor. No mouse enter serial found. [73209:73209:0308/101358.654205:ERROR:gpu_init.cc(525)] Passthrough is not supported, GL is egl, ANGLE is [73209:73209:0308/101358.657517:WARNING:sandbox_linux.cc(393)] InitializeSandbox() called with multiple threads in process gpu-process. [73039:73039:0308/101358.692393:WARNING:bluez_dbus_manager.cc(247)] Floss manager not present, cannot set Floss enable/disable. [73039:73039:0308/101358.706280:VERBOSE1:wayland_cursor.cc(151)] Failed to hide cursor. No mouse enter serial found. [73039:73039:0308/101358.706292:VERBOSE1:wayland_cursor.cc(151)] Failed to hide cursor. No mouse enter serial found. [73039:73039:0308/101358.706371:VERBOSE1:wayland_cursor.cc(151)] Failed to hide cursor. No mouse enter serial found. [73039:73039:0308/101358.706375:VERBOSE1:wayland_cursor.cc(151)] Failed to hide cursor. No mouse enter serial found. [73209:73209:0308/101358.722161:ERROR:gbm_pixmap_wayland.cc(75)] Cannot create bo with format= RGBA_ and usage=SCANOUT [73209:73209:0308/101358.722276:ERROR:gbm_pixmap_wayland.cc(75)] Cannot create bo with format= RGBA_ and usage=GPU_READ [73209:73209:0308/101358.722320:ERROR:shared_image_factory.cc(661)] CreateSharedImage: could not create backing. [73209:73209:0308/101358.722375:ERROR:shared_image_factory.cc(516)] DestroySharedImage: Could not find shared image mailbox [73209:73209:0308/101358.722458:ERROR:raster_decoder.cc(1117)] RasterDecoderImpl: Context lost during MakeCurrent.
[Desktop-packages] [Bug 2009739] Re: hwacc build crashes on direct scanout.
Unfortunately, removing the --enable-hardware-overlays flag does not
help.
Still crashes when full screen:
Chromium111.0.5563.19 (Official Build) snap (64-bit)
Revision
378a38865270d286695aeb86f190564911ef7bc2-refs/branch-heads/5563@{#251}
OS Linux
JavaScript V8 11.1.277
User agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like
Gecko) Chrome/111.0.0.0 Safari/537.36
Command Line/snap/chromium/x13/usr/lib/chromium-browser/chrome
--password-store=basic --ozone-platform=wayland
--enable-features=VaapiVideoDecoder,VaapiVideoEncoder,VaapiVideoDecodeLinuxGL
--disable-features=UseChromeOSDirectVideoDecoder --use-gl=egl
--video-capture-use-external-dma-buffer
--disable-features=TFLiteLanguageDetectionEnabled
--vmodule=*/video/linux/*=3,*/ui/gl/*=3,*/platform/wayland/*=3 --v0
--enable-logging=stderr --flag-switches-begin --flag-switches-end
Executable Path /snap/chromium/x13/usr/lib/chromium-browser/chrome
Profile Path/home/stolk/snap/chromium/common/chromium/Default
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2009739
Title:
hwacc build crashes on direct scanout.
Status in chromium-browser package in Ubuntu:
New
Bug description:
This pertains to the HWACC branches of the chromium snap.
When launched full-screen on an Intel iGPU, the hardware overlay use
will result in a core dump.
This could be related to direct-scanout and overlay planes?
To reproduce:
$ chromium --start-fullscreen
OS: Ubuntu 22.10
Chromium: 111.0.5563.19-hwacc
GPU: Alderlake iGPU
stolk@workpc:/snap/chromium/current/bin$ snap info chromium
name: chromium
summary: Chromium web browser, open-source version of Chrome
publisher: Canonical✓
store-url: https://snapcraft.io/chromium
contact:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
license: unset
description: |
An open-source browser project that aims to build a safer, faster, and more
stable way for all Internet users to experience the web.
commands:
- chromium.chromedriver
- chromium
snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
tracking: latest/beta/hwacc
refresh-date: yesterday at 08:52 PST
channels:
latest/stable:110.0.5481.177 2023-03-06 (2367) 156MB -
latest/candidate: 111.0.5563.64 2023-03-08 (2381) 155MB -
latest/beta: 111.0.5563.64 2023-03-07 (2380) 155MB -
latest/edge: 112.0.5615.12 2023-03-03 (2375) 156MB -
installed: 111.0.5563.19-hwacc(2376) 174MB -
stolk@workpc:/snap/chromium/current/bin$ chromium --start-fullscreen
[73039:73039:0308/101357.917887:WARNING:chrome_main_delegate.cc(618)] This is
Chrome version 111.0.5563.19 (not a warning)
[73039:73039:0308/101358.450380:WARNING:wayland_object.cc(152)] Binding to
gtk_shell1 version 4 but version 5 is available.
[73039:73039:0308/101358.450401:WARNING:wayland_object.cc(152)] Binding to
zwp_pointer_gestures_v1 version 1 but version 3 is available.
[73039:73039:0308/101358.450416:WARNING:wayland_object.cc(152)] Binding to
zwp_linux_dmabuf_v1 version 3 but version 4 is available.
Gtk-Message: 10:13:58.455: Not loading module "atk-bridge": The functionality
is provided by GTK natively. Please try to not load it.
[73039:73039:0308/101358.611145:WARNING:account_consistency_mode_manager.cc(70)]
Desktop Identity Consistency cannot be enabled as no OAuth client ID and
client secret have been configured.
[73039:73039:0308/101358.625559:WARNING:wayland_surface.cc(151)] Server
doesn't support zcr_alpha_compositing_v1.
[73039:73039:0308/101358.625573:WARNING:wayland_surface.cc(166)] Server
doesn't support overlay_prioritizer.
[73039:73039:0308/101358.625579:WARNING:wayland_surface.cc(180)] Server
doesn't support surface_augmenter.
[73039:73039:0308/101358.625583:WARNING:wayland_surface.cc(195)] Server
doesn't support wp_content_type_v1
[73039:73039:0308/101358.625586:WARNING:wayland_surface.cc(214)] Server
doesn't support zcr_color_management_surface.
[73039:73039:0308/101358.625774:WARNING:cursor_loader.cc(123)] Failed to load
a platform cursor of type kNull
[73039:73039:0308/101358.626013:VERBOSE1:wayland_cursor.cc(151)] Failed to
hide cursor. No mouse enter serial found.
[73209:73209:0308/101358.654205:ERROR:gpu_init.cc(525)] Passthrough is not
supported, GL is egl, ANGLE is
[73209:73209:0308/101358.657517:WARNING:sandbox_linux.cc(393)]
InitializeSandbox() called with multiple threads in process gpu-process.
[73039:73039:0308/101358.692393:WARNING:bluez_dbus_manager.cc(247)] Floss
manager not present, cannot set Floss enable/disable.
[73039:73039:0308/101358.706280:VERBOSE1:wayland_cursor.cc(151)] Failed to
hide cursor. No mouse enter serial found.
[Desktop-packages] [Bug 2009739] [NEW] hwacc build crashes on direct scanout.
Public bug reported: This pertains to the HWACC branches of the chromium snap. When launched full-screen on an Intel iGPU, the hardware overlay use will result in a core dump. This could be related to direct-scanout and overlay planes? To reproduce: $ chromium --start-fullscreen OS: Ubuntu 22.10 Chromium: 111.0.5563.19-hwacc GPU: Alderlake iGPU stolk@workpc:/snap/chromium/current/bin$ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/beta/hwacc refresh-date: yesterday at 08:52 PST channels: latest/stable:110.0.5481.177 2023-03-06 (2367) 156MB - latest/candidate: 111.0.5563.64 2023-03-08 (2381) 155MB - latest/beta: 111.0.5563.64 2023-03-07 (2380) 155MB - latest/edge: 112.0.5615.12 2023-03-03 (2375) 156MB - installed: 111.0.5563.19-hwacc(2376) 174MB - stolk@workpc:/snap/chromium/current/bin$ chromium --start-fullscreen [73039:73039:0308/101357.917887:WARNING:chrome_main_delegate.cc(618)] This is Chrome version 111.0.5563.19 (not a warning) [73039:73039:0308/101358.450380:WARNING:wayland_object.cc(152)] Binding to gtk_shell1 version 4 but version 5 is available. [73039:73039:0308/101358.450401:WARNING:wayland_object.cc(152)] Binding to zwp_pointer_gestures_v1 version 1 but version 3 is available. [73039:73039:0308/101358.450416:WARNING:wayland_object.cc(152)] Binding to zwp_linux_dmabuf_v1 version 3 but version 4 is available. Gtk-Message: 10:13:58.455: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. [73039:73039:0308/101358.611145:WARNING:account_consistency_mode_manager.cc(70)] Desktop Identity Consistency cannot be enabled as no OAuth client ID and client secret have been configured. [73039:73039:0308/101358.625559:WARNING:wayland_surface.cc(151)] Server doesn't support zcr_alpha_compositing_v1. [73039:73039:0308/101358.625573:WARNING:wayland_surface.cc(166)] Server doesn't support overlay_prioritizer. [73039:73039:0308/101358.625579:WARNING:wayland_surface.cc(180)] Server doesn't support surface_augmenter. [73039:73039:0308/101358.625583:WARNING:wayland_surface.cc(195)] Server doesn't support wp_content_type_v1 [73039:73039:0308/101358.625586:WARNING:wayland_surface.cc(214)] Server doesn't support zcr_color_management_surface. [73039:73039:0308/101358.625774:WARNING:cursor_loader.cc(123)] Failed to load a platform cursor of type kNull [73039:73039:0308/101358.626013:VERBOSE1:wayland_cursor.cc(151)] Failed to hide cursor. No mouse enter serial found. [73209:73209:0308/101358.654205:ERROR:gpu_init.cc(525)] Passthrough is not supported, GL is egl, ANGLE is [73209:73209:0308/101358.657517:WARNING:sandbox_linux.cc(393)] InitializeSandbox() called with multiple threads in process gpu-process. [73039:73039:0308/101358.692393:WARNING:bluez_dbus_manager.cc(247)] Floss manager not present, cannot set Floss enable/disable. [73039:73039:0308/101358.706280:VERBOSE1:wayland_cursor.cc(151)] Failed to hide cursor. No mouse enter serial found. [73039:73039:0308/101358.706292:VERBOSE1:wayland_cursor.cc(151)] Failed to hide cursor. No mouse enter serial found. [73039:73039:0308/101358.706371:VERBOSE1:wayland_cursor.cc(151)] Failed to hide cursor. No mouse enter serial found. [73039:73039:0308/101358.706375:VERBOSE1:wayland_cursor.cc(151)] Failed to hide cursor. No mouse enter serial found. [73209:73209:0308/101358.722161:ERROR:gbm_pixmap_wayland.cc(75)] Cannot create bo with format= RGBA_ and usage=SCANOUT [73209:73209:0308/101358.722276:ERROR:gbm_pixmap_wayland.cc(75)] Cannot create bo with format= RGBA_ and usage=GPU_READ [73209:73209:0308/101358.722320:ERROR:shared_image_factory.cc(661)] CreateSharedImage: could not create backing. [73209:73209:0308/101358.722375:ERROR:shared_image_factory.cc(516)] DestroySharedImage: Could not find shared image mailbox [73209:73209:0308/101358.722458:ERROR:raster_decoder.cc(1117)] RasterDecoderImpl: Context lost during MakeCurrent. [73209:73209:0308/101358.722500:ERROR:gpu_service_impl.cc(980)] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly. [73039:73039:0308/101358.758383:ERROR:command_buffer_proxy_impl.cc(325)] GPU state invalid after WaitForGetOffsetInRange. [73039:73039:0308/101358.761718:ERROR:gpu_process_host.cc(952)] GPU process exited unexpectedly: exit_code=8704 [73039:73039:0308/101358.761733:WARNING:gpu_process_host.cc(1302)] The GPU process has crashed 1 time(s)
[Desktop-packages] [Bug 2004586] Re: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver.
Note that when logging into build VM after building the chromium-hwacc snap: multipass shell snapcraft-chromium I see: # pkg-config --variable=dridriverdir dri /usr/lib/x86_64-linux-gnu/dri And not the expected /snap/gnome-3-38-2004/current/usr/lib/x86_64-linux-gnu/dri this value is from here, btw: /usr/lib/x86_64-linux-gnu/pkgconfig/dri.pc Maybe we should just create a symbolic link, and also fix the escaped quotes? (Or fix amdgpu.c to not stringify) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2004586 Title: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver. Status in chromium-browser package in Ubuntu: In Progress Bug description: [NOTE] This is for the HWACC build of chromium, from snap channel latest/candidate/hwacc $ snap info chromium | grep installed installed: 107.0.5304.68-hwacc(2301) 172MB - This hwacc branch uses minigbm over the Ubuntu-supplied libgbm from Mesa origin. (Unlike the Mesa variant, the minigbm bundled by chromium can do YUV buffers, like NV12.) Regular builds of the chromium snap will not use minigbm, and thus not exhibit this behaviour! Something goes wrong with the expansion of the macro DRI_DRIVER_DIR $ strings /snap/chromium/current/usr/lib/chromium-browser/chrome | grep radeonsi_ /usr/lib64/dri/radeonsi_dri.so DRI_DRIVER_DIR/radeonsi_dri.so dlopen(radeonsi_dri.so) failed with error: The DRI_DRIVER_DIR was not properly expanded to /usr/lib/x86_64-linux- gnu here. I've also built current HEAD of chromium source code manually, and did the same test on that, and that version is unaffected: $ strings out/Default/chrome | grep radeonsi_ dlopen(radeonsi_dri.so) failed with error: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so /usr/lib64/dri/radeonsi_dri.so A partner found this change to third_party/minigbm/src/amdgpu.c:27 to be working: //#define DRI_PATH STRINGIZE(DRI_DRIVER_DIR/radeonsi_dri.so) #define DRI_PATH "/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so" But it is better to understand why this expansion failed. And it is possibly fixed in later chromium releases, if not, we should look how our snap building differs from the official Linux building instructions for chromium. In any case, we should track this. OS: Ubuntu 22.10 Package: chromium Snap version: 107.0.5304.68-hwacc Channel: latest/candidate/hwacc Expectations: correctly loading driver from correct location. Actual: using incorrect location. I will follow up by testing this on a machine with an AMD GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2004586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006646] Re: hwacc branch builds that use minigbm will switch to software compositor on amd.
Hard-coding the dri directory to point to the snap's dri dir fixes this, as I now see: Graphics Feature Status Canvas: Hardware accelerated Canvas out-of-process rasterization: Disabled Direct Rendering Display Compositor: Disabled Compositing: Hardware accelerated Multiple Raster Threads: Enabled OpenGL: Enabled Rasterization: Hardware accelerated Raw Draw: Disabled Video Decode: Hardware accelerated Video Encode: Software only. Hardware acceleration disabled Vulkan: Disabled WebGL: Hardware accelerated WebGL2: Hardware accelerated WebGPU: Disabled -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006646 Title: hwacc branch builds that use minigbm will switch to software compositor on amd. Status in chromium-browser package in Ubuntu: In Progress Bug description: This pertains to the hwacc branches of snap_from_source chromium builds. Following the guide-0.9.1, we switched from system gbm to minigbm. (These switches are in args.gn) use_system_minigbm = false use_intel_minigbm = true use_amdgpu_minigbm = true This enables us to better support intel hardware. However, there seems to be a regression on other gpus. Chromium will switch to software compositing on amd. When I revert back to system gbm, I get hardware compositing again. See attached screenshot. To reproduce: build chromium in two different ways, and compare the output from the chrome://gpu url. tested on: Radeon RX580 GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006646/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006646] Re: hwacc branch builds that use minigbm will switch to software compositor on amd.
I've added logging to third_party/minigbm/src/amdgpu.c third_party/minigbm/src/drv.c This yielded: drm_version->name: amdgpu backend_list[0] = amdgpu drv_get_backend(13) returned 0x55bf084e4338 dri_init() failed for path /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so driver radeonsi: No such file or directory backend init() failed: -19 [27925:27925:0221/111810.067118:WARNING:ozone_platform_wayland.cc(273)] Failed to find drm render node path. [27925:27925:0221/111810.068456:WARNING:wayland_buffer_manager_gpu.cc(437)] Failed to initialize drm render node handle. Checking with: sudo snap run --shell chromium ...it turns out that there is no /usr/lib/x86_64-linux-gnu/dri/ directory in the snap. NOTE: There is a /snap/chromium/current/usr/lib/x86_64-linux-gnu/dri directory, but that only contains video drivers, like radeonsi_drv_video.so ** Summary changed: - hwacc branch builds with minigbm switch to software compositor on amd. + hwacc branch builds that use minigbm will switch to software compositor on amd. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006646 Title: hwacc branch builds that use minigbm will switch to software compositor on amd. Status in chromium-browser package in Ubuntu: In Progress Bug description: This pertains to the hwacc branches of snap_from_source chromium builds. Following the guide-0.9.1, we switched from system gbm to minigbm. (These switches are in args.gn) use_system_minigbm = false use_intel_minigbm = true use_amdgpu_minigbm = true This enables us to better support intel hardware. However, there seems to be a regression on other gpus. Chromium will switch to software compositing on amd. When I revert back to system gbm, I get hardware compositing again. See attached screenshot. To reproduce: build chromium in two different ways, and compare the output from the chrome://gpu url. tested on: Radeon RX580 GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006646/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006646] Re: hwacc branch builds with minigbm switch to software compositor on amd.
I have reproduced this with a chromium that I built manually, from source, not going via snapcraft. So that rules out snap as the culprit, I think. reproduced with: 112.0.5572.0 Built with: use_system_minigbm = false use_intel_minigbm = true use_amdgpu_minigbm = true WARNING:ozone_platform_wayland.cc(273)] Failed to find drm render node path. WARNING:wayland_buffer_manager_gpu.cc(437)] Failed to initialize drm render node handle. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006646 Title: hwacc branch builds with minigbm switch to software compositor on amd. Status in chromium-browser package in Ubuntu: In Progress Bug description: This pertains to the hwacc branches of snap_from_source chromium builds. Following the guide-0.9.1, we switched from system gbm to minigbm. (These switches are in args.gn) use_system_minigbm = false use_intel_minigbm = true use_amdgpu_minigbm = true This enables us to better support intel hardware. However, there seems to be a regression on other gpus. Chromium will switch to software compositing on amd. When I revert back to system gbm, I get hardware compositing again. See attached screenshot. To reproduce: build chromium in two different ways, and compare the output from the chrome://gpu url. tested on: Radeon RX580 GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006646/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006646] Re: hwacc branch builds with minigbm switch to software compositor on amd.
With the DRI_DRIVER_DIR issue out of the way, I see: WARNING:ozone_platform_wayland.cc(273)] Failed to find drm render node path. WARNING:wayland_buffer_manager_gpu.cc(437)] Failed to initialize drm render node handle. render node is present: $ ls -al /dev/dri/ total 0 drwxr-xr-x 3 root root100 Feb 16 18:32 . drwxr-xr-x 22 root root 5800 Feb 17 08:00 .. drwxr-xr-x 2 root root 80 Feb 17 08:00 by-path crw-rw+ 1 root video 226, 0 Feb 17 08:00 card0 crw-rw+ 1 root render 226, 128 Feb 16 18:32 renderD128 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006646 Title: hwacc branch builds with minigbm switch to software compositor on amd. Status in chromium-browser package in Ubuntu: In Progress Bug description: This pertains to the hwacc branches of snap_from_source chromium builds. Following the guide-0.9.1, we switched from system gbm to minigbm. (These switches are in args.gn) use_system_minigbm = false use_intel_minigbm = true use_amdgpu_minigbm = true This enables us to better support intel hardware. However, there seems to be a regression on other gpus. Chromium will switch to software compositing on amd. When I revert back to system gbm, I get hardware compositing again. See attached screenshot. To reproduce: build chromium in two different ways, and compare the output from the chrome://gpu url. tested on: Radeon RX580 GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006646/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004586] Re: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver.
MR for snap-from-source is here: https://code.launchpad.net/~b-stolk/chromium-browser/+git/snap-from-source/+merge/437529 ** Changed in: chromium-browser (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2004586 Title: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver. Status in chromium-browser package in Ubuntu: In Progress Bug description: [NOTE] This is for the HWACC build of chromium, from snap channel latest/candidate/hwacc $ snap info chromium | grep installed installed: 107.0.5304.68-hwacc(2301) 172MB - This hwacc branch uses minigbm over the Ubuntu-supplied libgbm from Mesa origin. (Unlike the Mesa variant, the minigbm bundled by chromium can do YUV buffers, like NV12.) Regular builds of the chromium snap will not use minigbm, and thus not exhibit this behaviour! Something goes wrong with the expansion of the macro DRI_DRIVER_DIR $ strings /snap/chromium/current/usr/lib/chromium-browser/chrome | grep radeonsi_ /usr/lib64/dri/radeonsi_dri.so DRI_DRIVER_DIR/radeonsi_dri.so dlopen(radeonsi_dri.so) failed with error: The DRI_DRIVER_DIR was not properly expanded to /usr/lib/x86_64-linux- gnu here. I've also built current HEAD of chromium source code manually, and did the same test on that, and that version is unaffected: $ strings out/Default/chrome | grep radeonsi_ dlopen(radeonsi_dri.so) failed with error: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so /usr/lib64/dri/radeonsi_dri.so A partner found this change to third_party/minigbm/src/amdgpu.c:27 to be working: //#define DRI_PATH STRINGIZE(DRI_DRIVER_DIR/radeonsi_dri.so) #define DRI_PATH "/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so" But it is better to understand why this expansion failed. And it is possibly fixed in later chromium releases, if not, we should look how our snap building differs from the official Linux building instructions for chromium. In any case, we should track this. OS: Ubuntu 22.10 Package: chromium Snap version: 107.0.5304.68-hwacc Channel: latest/candidate/hwacc Expectations: correctly loading driver from correct location. Actual: using incorrect location. I will follow up by testing this on a machine with an AMD GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2004586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004586] Re: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver.
I've sent an up-stream fix to Gerrit: https://chromium-review.googlesource.com/c/chromiumos/platform/minigbm/+/4263398 Fix to snap-from-source will follow. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2004586 Title: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver. Status in chromium-browser package in Ubuntu: Triaged Bug description: [NOTE] This is for the HWACC build of chromium, from snap channel latest/candidate/hwacc $ snap info chromium | grep installed installed: 107.0.5304.68-hwacc(2301) 172MB - This hwacc branch uses minigbm over the Ubuntu-supplied libgbm from Mesa origin. (Unlike the Mesa variant, the minigbm bundled by chromium can do YUV buffers, like NV12.) Regular builds of the chromium snap will not use minigbm, and thus not exhibit this behaviour! Something goes wrong with the expansion of the macro DRI_DRIVER_DIR $ strings /snap/chromium/current/usr/lib/chromium-browser/chrome | grep radeonsi_ /usr/lib64/dri/radeonsi_dri.so DRI_DRIVER_DIR/radeonsi_dri.so dlopen(radeonsi_dri.so) failed with error: The DRI_DRIVER_DIR was not properly expanded to /usr/lib/x86_64-linux- gnu here. I've also built current HEAD of chromium source code manually, and did the same test on that, and that version is unaffected: $ strings out/Default/chrome | grep radeonsi_ dlopen(radeonsi_dri.so) failed with error: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so /usr/lib64/dri/radeonsi_dri.so A partner found this change to third_party/minigbm/src/amdgpu.c:27 to be working: //#define DRI_PATH STRINGIZE(DRI_DRIVER_DIR/radeonsi_dri.so) #define DRI_PATH "/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so" But it is better to understand why this expansion failed. And it is possibly fixed in later chromium releases, if not, we should look how our snap building differs from the official Linux building instructions for chromium. In any case, we should track this. OS: Ubuntu 22.10 Package: chromium Snap version: 107.0.5304.68-hwacc Channel: latest/candidate/hwacc Expectations: correctly loading driver from correct location. Actual: using incorrect location. I will follow up by testing this on a machine with an AMD GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2004586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004586] Re: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver.
This part is missing from the compiler command line -DDRI_DRIVER_DIR=\"/usr/lib/x86_64-linux-gnu/dri\" I've verified that this can be fixed by adding a configuration to minigbm's BUILD.gn I will create a patch that addresses this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2004586 Title: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver. Status in chromium-browser package in Ubuntu: Triaged Bug description: [NOTE] This is for the HWACC build of chromium, from snap channel latest/candidate/hwacc $ snap info chromium | grep installed installed: 107.0.5304.68-hwacc(2301) 172MB - This hwacc branch uses minigbm over the Ubuntu-supplied libgbm from Mesa origin. (Unlike the Mesa variant, the minigbm bundled by chromium can do YUV buffers, like NV12.) Regular builds of the chromium snap will not use minigbm, and thus not exhibit this behaviour! Something goes wrong with the expansion of the macro DRI_DRIVER_DIR $ strings /snap/chromium/current/usr/lib/chromium-browser/chrome | grep radeonsi_ /usr/lib64/dri/radeonsi_dri.so DRI_DRIVER_DIR/radeonsi_dri.so dlopen(radeonsi_dri.so) failed with error: The DRI_DRIVER_DIR was not properly expanded to /usr/lib/x86_64-linux- gnu here. I've also built current HEAD of chromium source code manually, and did the same test on that, and that version is unaffected: $ strings out/Default/chrome | grep radeonsi_ dlopen(radeonsi_dri.so) failed with error: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so /usr/lib64/dri/radeonsi_dri.so A partner found this change to third_party/minigbm/src/amdgpu.c:27 to be working: //#define DRI_PATH STRINGIZE(DRI_DRIVER_DIR/radeonsi_dri.so) #define DRI_PATH "/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so" But it is better to understand why this expansion failed. And it is possibly fixed in later chromium releases, if not, we should look how our snap building differs from the official Linux building instructions for chromium. In any case, we should track this. OS: Ubuntu 22.10 Package: chromium Snap version: 107.0.5304.68-hwacc Channel: latest/candidate/hwacc Expectations: correctly loading driver from correct location. Actual: using incorrect location. I will follow up by testing this on a machine with an AMD GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2004586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006646] Re: hwacc branch builds with minigbm switch to software compositor on amd.
This could be a hint on why: WARNING:ozone_platform_wayland.cc(273)] Failed to find drm render node path. WARNING:wayland_buffer_manager_gpu.cc(424)] Failed to initialize drm render node handle. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006646 Title: hwacc branch builds with minigbm switch to software compositor on amd. Status in chromium-browser package in Ubuntu: In Progress Bug description: This pertains to the hwacc branches of snap_from_source chromium builds. Following the guide-0.9.1, we switched from system gbm to minigbm. (These switches are in args.gn) use_system_minigbm = false use_intel_minigbm = true use_amdgpu_minigbm = true This enables us to better support intel hardware. However, there seems to be a regression on other gpus. Chromium will switch to software compositing on amd. When I revert back to system gbm, I get hardware compositing again. See attached screenshot. To reproduce: build chromium in two different ways, and compare the output from the chrome://gpu url. tested on: Radeon RX580 GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006646/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006966] Re: Missing flag causing lack of hardware encoding in hwacc build.
** Changed in: chromium-browser (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006966 Title: Missing flag causing lack of hardware encoding in hwacc build. Status in chromium-browser package in Ubuntu: In Progress Bug description: This is about the hwacc branch of snap-from-source package. The chromium 110 version of the build guide came with the instruction to add an additional flag when launching chromium: VaapiVideoDecodeLinuxGL This flag is not present in chromium.launcher of the beta branch of hwacc, causing hw acceleration to fail. This was caught by checkbox kivu run. I will make a merge request adding this flag. $ snap info chromium | grep installed installed: 110.0.5481.77-hwacc(2320) 174MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006966/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006966] [NEW] Missing flag causing lack of hardware encoding in hwacc build.
Public bug reported: This is about the hwacc branch of snap-from-source package. The chromium 110 version of the build guide came with the instruction to add an additional flag when launching chromium: VaapiVideoDecodeLinuxGL This flag is not present in chromium.launcher of the beta branch of hwacc, causing hw acceleration to fail. This was caught by checkbox kivu run. I will make a merge request adding this flag. $ snap info chromium | grep installed installed: 110.0.5481.77-hwacc(2320) 174MB - ** Affects: chromium-browser (Ubuntu) Importance: Undecided Assignee: Bram Stolk (b-stolk) Status: New ** Tags: kivu ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Bram Stolk (b-stolk) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006966 Title: Missing flag causing lack of hardware encoding in hwacc build. Status in chromium-browser package in Ubuntu: New Bug description: This is about the hwacc branch of snap-from-source package. The chromium 110 version of the build guide came with the instruction to add an additional flag when launching chromium: VaapiVideoDecodeLinuxGL This flag is not present in chromium.launcher of the beta branch of hwacc, causing hw acceleration to fail. This was caught by checkbox kivu run. I will make a merge request adding this flag. $ snap info chromium | grep installed installed: 110.0.5481.77-hwacc(2320) 174MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006966/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006641] Re: hwacc branches fail to build
>One-copy patch does not apply to 111. That is regrettable. I'll do a quick test to see if a higher --fuzz helps, by any chance. Which would be a trivial fix. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006641 Title: hwacc branches fail to build Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Currently the hwacc branches of snap_from_source fail to build. This is caused by the fact that the guide-0.9.1 patches are against 107 chromium, and no longer apply cleanly. build logs here: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006641/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006646] Re: hwacc branch builds with minigbm switch to software compositor on amd.
** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Bram Stolk (b-stolk) ** Changed in: chromium-browser (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006646 Title: hwacc branch builds with minigbm switch to software compositor on amd. Status in chromium-browser package in Ubuntu: In Progress Bug description: This pertains to the hwacc branches of snap_from_source chromium builds. Following the guide-0.9.1, we switched from system gbm to minigbm. (These switches are in args.gn) use_system_minigbm = false use_intel_minigbm = true use_amdgpu_minigbm = true This enables us to better support intel hardware. However, there seems to be a regression on other gpus. Chromium will switch to software compositing on amd. When I revert back to system gbm, I get hardware compositing again. See attached screenshot. To reproduce: build chromium in two different ways, and compare the output from the chrome://gpu url. tested on: Radeon RX580 GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006646/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006646] Re: hwacc branch builds with minigbm switch to software compositor on amd.
The previous test was on a chromium 107 build. I re-tested it on a chromium 110 build with minigbm, and it shows the same result on rx580 gpu: software compositing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006646 Title: hwacc branch builds with minigbm switch to software compositor on amd. Status in chromium-browser package in Ubuntu: New Bug description: This pertains to the hwacc branches of snap_from_source chromium builds. Following the guide-0.9.1, we switched from system gbm to minigbm. (These switches are in args.gn) use_system_minigbm = false use_intel_minigbm = true use_amdgpu_minigbm = true This enables us to better support intel hardware. However, there seems to be a regression on other gpus. Chromium will switch to software compositing on amd. When I revert back to system gbm, I get hardware compositing again. See attached screenshot. To reproduce: build chromium in two different ways, and compare the output from the chrome://gpu url. tested on: Radeon RX580 GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006646/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006646] [NEW] hwacc branch builds with minigbm switch to software compositor on amd.
Public bug reported: This pertains to the hwacc branches of snap_from_source chromium builds. Following the guide-0.9.1, we switched from system gbm to minigbm. (These switches are in args.gn) use_system_minigbm = false use_intel_minigbm = true use_amdgpu_minigbm = true This enables us to better support intel hardware. However, there seems to be a regression on other gpus. Chromium will switch to software compositing on amd. When I revert back to system gbm, I get hardware compositing again. See attached screenshot. To reproduce: build chromium in two different ways, and compare the output from the chrome://gpu url. tested on: Radeon RX580 GPU. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Attachment added: "comparision between minigbm and systemgbm" https://bugs.launchpad.net/bugs/2006646/+attachment/5645686/+files/chrome-gpu-comparision-minigbm-vs-systemgbm.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006646 Title: hwacc branch builds with minigbm switch to software compositor on amd. Status in chromium-browser package in Ubuntu: New Bug description: This pertains to the hwacc branches of snap_from_source chromium builds. Following the guide-0.9.1, we switched from system gbm to minigbm. (These switches are in args.gn) use_system_minigbm = false use_intel_minigbm = true use_amdgpu_minigbm = true This enables us to better support intel hardware. However, there seems to be a regression on other gpus. Chromium will switch to software compositing on amd. When I revert back to system gbm, I get hardware compositing again. See attached screenshot. To reproduce: build chromium in two different ways, and compare the output from the chrome://gpu url. tested on: Radeon RX580 GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006646/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006641] Re: hwacc branches fail to build
** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Bram Stolk (b-stolk) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006641 Title: hwacc branches fail to build Status in chromium-browser package in Ubuntu: New Bug description: Currently the hwacc branches of snap_from_source fail to build. This is caused by the fact that the guide-0.9.1 patches are against 107 chromium, and no longer apply cleanly. build logs here: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006641/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006641] [NEW] hwacc branches fail to build
Public bug reported: Currently the hwacc branches of snap_from_source fail to build. This is caused by the fact that the guide-0.9.1 patches are against 107 chromium, and no longer apply cleanly. build logs here: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-beta ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: kivu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006641 Title: hwacc branches fail to build Status in chromium-browser package in Ubuntu: New Bug description: Currently the hwacc branches of snap_from_source fail to build. This is caused by the fact that the guide-0.9.1 patches are against 107 chromium, and no longer apply cleanly. build logs here: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006641/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004586] Re: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver.
I confirmed that DRI_DRIVER_DIR never makes it to the compiler flags. I added an error pragma to catch an empty definition and no definition in attached patch. The result when building w that patch (on 107 chromium): FAILED: obj/third_party/minigbm/minigbm/amdgpu.o ../../third_party/llvm-build/Release+Asserts/bin/clang -MMD -MF obj/third_party/minigbm/minigbm/amdgpu.o.d -DUSE_UDEV -DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_OZONE=1 -DOFFICIAL_BUILD -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DNO_UNWIND_TABLES -D_GNU_SOURCE -DCR_CLANG_REVISION=\"llvmorg-16-init-4609-g025a5b22-2\" -D_LIBCPP_DISABLE_VISIBILITY_ANNOTATIONS -D_LIBCXXABI_DISABLE_VISIBILITY_ANNOTATIONS -DCR_LIBCXX_REVISION=e2f63a1a48a3cdcacbfc212236050ca5deeacc30 -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DDRV_AMDGPU -DDRV_I915 -I../.. -Igen -I../../buildtools/third_party/libc++ -I../../third_party/minigbm/src -fno-delete-null-pointer-checks -fno-ident -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -fno-unwind-tables -fno-asynchronous-unwind-tables -fPIC -pthread -fcolor-diagnostics -fmerge-all-constants -fcrash-diagnostics-dir=../../tools/clang/crashreports -mllvm -instcombine-lower-dbg-declare=0 -ffp-contract=off -flto=thin -fsplit-lto-unit -fw hole-program-vtables -fcomplete-member-pointers -m64 -msse3 -ffile-compilation-dir=. -no-canonical-prefixes -ftrivial-auto-var-init=pattern -O2 -fdata-sections -ffunction-sections -fno-unique-section-names -fno-omit-frame-pointer -g0 -fprofile-use=../../chrome/build/pgo_profiles/chrome-linux-5304-1666369430-50bfc04797db1acc0805fe1425e83d1bbe3b92f6.profdata -Wno-profile-instr-unprofiled -Wno-profile-instr-out-of-date -Wno-backend-plugin -fvisibility=hidden -Xclang -add-plugin -Xclang find-bad-constructs -Xclang -plugin-arg-find-bad-constructs -Xclang raw-ref-template-as-trivial-member -Xclang -plugin-arg-find-bad-constructs -Xclang check-ipc -Wheader-hygiene -Wstring-conversion -Wtautological-overlap-compare -Wall -Wno-unused-variable -Wno-c++11-narrowing -Wno-unused-but-set-variable -Wno-misleading-indentation -Wno-missing-field-initializers -Wno-unused-parameter -Wloop-analysis -Wno-unneeded-internal-declaration -Wenum-compare-conditional -Wno-psabi -Wno-ignored-pragma-optimize -Wn o-deprecated-builtins -Wno-bitfield-constant-conversion -I/usr/include/libdrm -std=c11 -c ../../third_party/minigbm/src/amdgpu.c -o obj/third_party/minigbm/minigbm/amdgpu.o ../../third_party/minigbm/src/amdgpu.c:27:3: error: "DRI_DRIVER_DIR is not defined." # error "DRI_DRIVER_DIR is not defined." ^ 1 error generated. [1511/54251] CXX obj/third_party/protobuf/protoc_lib/csharp_message.o ninja: build stopped: subcommand failed. Failed to run 'override-build': Exit code was 1. If will probably make sense to add a default path for that if the symbol has not been defined. I'll work on that. ** Patch added: "amdtest:check-for-empty-define.patch" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2004586/+attachment/5645635/+files/amdtest%3Acheck-for-empty-define.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2004586 Title: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver. Status in chromium-browser package in Ubuntu: In Progress Bug description: [NOTE] This is for the HWACC build of chromium, from snap channel latest/candidate/hwacc $ snap info chromium | grep installed installed: 107.0.5304.68-hwacc(2301) 172MB - This hwacc branch uses minigbm over the Ubuntu-supplied libgbm from Mesa origin. (Unlike the Mesa variant, the minigbm bundled by chromium can do YUV buffers, like NV12.) Regular builds of the chromium snap will not use minigbm, and thus not exhibit this behaviour! Something goes wrong with the expansion of the macro DRI_DRIVER_DIR $ strings /snap/chromium/current/usr/lib/chromium-browser/chrome | grep radeonsi_ /usr/lib64/dri/radeonsi_dri.so DRI_DRIVER_DIR/radeonsi_dri.so dlopen(radeonsi_dri.so) failed with error: The DRI_DRIVER_DIR was not properly expanded to /usr/lib/x86_64-linux- gnu here. I've also built current HEAD of chromium source code manually, and did the same test on that, and that version is unaffected: $ strings out/Default/chrome | grep radeonsi_ dlopen(radeonsi_dri.so) failed with error: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so /usr/lib64/dri/radeonsi_dri.so A partner found this change to third_party/minigbm/src/amdgpu.c:27 to be working: //#define DRI_PATH STRINGIZE(DRI_DRIVER_DIR/radeonsi_dri.so) #define DRI_PATH "/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so" But it is better to understand why this expansion failed. And it is possibly fixed in later chromium releases, if not, we should look how our snap building differs from the official
[Desktop-packages] [Bug 2004586] Re: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver.
Thanks for testing. So, your first log contains this error, though: ``` /build/chromium/parts/chromium/build ERROR at //build/config/linux/dri/BUILD.gn:11:20: Script returned non-zero exit code. dri_driver_dir = exec_script(pkg_config_script, ^-- Current dir: /build/chromium/parts/chromium/build/out/Release/ Command: python3 /build/chromium/parts/chromium/build/build/config/linux/pkg-config.py -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config --dridriverdir dri Returned 1 and printed out: Error from pkg-config. stderr: ``` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2004586 Title: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver. Status in chromium-browser package in Ubuntu: In Progress Bug description: [NOTE] This is for the HWACC build of chromium, from snap channel latest/candidate/hwacc $ snap info chromium | grep installed installed: 107.0.5304.68-hwacc(2301) 172MB - This hwacc branch uses minigbm over the Ubuntu-supplied libgbm from Mesa origin. (Unlike the Mesa variant, the minigbm bundled by chromium can do YUV buffers, like NV12.) Regular builds of the chromium snap will not use minigbm, and thus not exhibit this behaviour! Something goes wrong with the expansion of the macro DRI_DRIVER_DIR $ strings /snap/chromium/current/usr/lib/chromium-browser/chrome | grep radeonsi_ /usr/lib64/dri/radeonsi_dri.so DRI_DRIVER_DIR/radeonsi_dri.so dlopen(radeonsi_dri.so) failed with error: The DRI_DRIVER_DIR was not properly expanded to /usr/lib/x86_64-linux- gnu here. I've also built current HEAD of chromium source code manually, and did the same test on that, and that version is unaffected: $ strings out/Default/chrome | grep radeonsi_ dlopen(radeonsi_dri.so) failed with error: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so /usr/lib64/dri/radeonsi_dri.so A partner found this change to third_party/minigbm/src/amdgpu.c:27 to be working: //#define DRI_PATH STRINGIZE(DRI_DRIVER_DIR/radeonsi_dri.so) #define DRI_PATH "/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so" But it is better to understand why this expansion failed. And it is possibly fixed in later chromium releases, if not, we should look how our snap building differs from the official Linux building instructions for chromium. In any case, we should track this. OS: Ubuntu 22.10 Package: chromium Snap version: 107.0.5304.68-hwacc Channel: latest/candidate/hwacc Expectations: correctly loading driver from correct location. Actual: using incorrect location. I will follow up by testing this on a machine with an AMD GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2004586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004586] [NEW] Chromium's minigbm uses incorrect path for loading radeonsi_dri driver.
Public bug reported: [NOTE] This is for the HWACC build of chromium, from snap channel latest/candidate/hwacc $ snap info chromium | grep installed installed: 107.0.5304.68-hwacc(2301) 172MB - This hwacc branch uses minigbm over the Ubuntu-supplied libgbm from Mesa origin. (Unlike the Mesa variant, the minigbm bundled by chromium can do YUV buffers, like NV12.) Regular builds of the chromium snap will not use minigbm, and thus not exhibit this behaviour! Something goes wrong with the expansion of the macro DRI_DRIVER_DIR $ strings /snap/chromium/current/usr/lib/chromium-browser/chrome | grep radeonsi_ /usr/lib64/dri/radeonsi_dri.so DRI_DRIVER_DIR/radeonsi_dri.so dlopen(radeonsi_dri.so) failed with error: The DRI_DRIVER_DIR was not properly expanded to /usr/lib/x86_64-linux- gnu here. I've also built current HEAD of chromium source code manually, and did the same test on that, and that version is unaffected: $ strings out/Default/chrome | grep radeonsi_ dlopen(radeonsi_dri.so) failed with error: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so /usr/lib64/dri/radeonsi_dri.so A partner found this change to third_party/minigbm/src/amdgpu.c:27 to be working: //#define DRI_PATH STRINGIZE(DRI_DRIVER_DIR/radeonsi_dri.so) #define DRI_PATH "/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so" But it is better to understand why this expansion failed. And it is possibly fixed in later chromium releases, if not, we should look how our snap building differs from the official Linux building instructions for chromium. In any case, we should track this. OS: Ubuntu 22.10 Package: chromium Snap version: 107.0.5304.68-hwacc Channel: latest/candidate/hwacc Expectations: correctly loading driver from correct location. Actual: using incorrect location. I will follow up by testing this on a machine with an AMD GPU. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: kivu snap ** Tags added: kivu snap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2004586 Title: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver. Status in chromium-browser package in Ubuntu: New Bug description: [NOTE] This is for the HWACC build of chromium, from snap channel latest/candidate/hwacc $ snap info chromium | grep installed installed: 107.0.5304.68-hwacc(2301) 172MB - This hwacc branch uses minigbm over the Ubuntu-supplied libgbm from Mesa origin. (Unlike the Mesa variant, the minigbm bundled by chromium can do YUV buffers, like NV12.) Regular builds of the chromium snap will not use minigbm, and thus not exhibit this behaviour! Something goes wrong with the expansion of the macro DRI_DRIVER_DIR $ strings /snap/chromium/current/usr/lib/chromium-browser/chrome | grep radeonsi_ /usr/lib64/dri/radeonsi_dri.so DRI_DRIVER_DIR/radeonsi_dri.so dlopen(radeonsi_dri.so) failed with error: The DRI_DRIVER_DIR was not properly expanded to /usr/lib/x86_64-linux- gnu here. I've also built current HEAD of chromium source code manually, and did the same test on that, and that version is unaffected: $ strings out/Default/chrome | grep radeonsi_ dlopen(radeonsi_dri.so) failed with error: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so /usr/lib64/dri/radeonsi_dri.so A partner found this change to third_party/minigbm/src/amdgpu.c:27 to be working: //#define DRI_PATH STRINGIZE(DRI_DRIVER_DIR/radeonsi_dri.so) #define DRI_PATH "/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so" But it is better to understand why this expansion failed. And it is possibly fixed in later chromium releases, if not, we should look how our snap building differs from the official Linux building instructions for chromium. In any case, we should track this. OS: Ubuntu 22.10 Package: chromium Snap version: 107.0.5304.68-hwacc Channel: latest/candidate/hwacc Expectations: correctly loading driver from correct location. Actual: using incorrect location. I will follow up by testing this on a machine with an AMD GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2004586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968610] Re: Chromium snap doesn't launch correctly Ubuntu 22.04 on Wayland, Nvidia
I am hitting this too. Unlike OP, I am on 22.10 Like OP, I am on nvidia 510 proprietary drivers. Adding --ozone-platform=wayland fixes the issue for me. $ chromium Gtk-Message: 10:43:34.433: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to open nvidia-drm: /snap/chromium/2271/gnome-platform/usr/lib/x86_64-linux-gnu/dri/nvidia-drm_dri.so: cannot open shared object file: Permission denied (search paths /snap/chromium/2271/gnome-platform/usr/lib/x86_64-linux-gnu/dri, suffix _dri) failed to load driver: nvidia-drm chromium snap version: 109.0.5414.74 (latest/stable channel) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1968610 Title: Chromium snap doesn't launch correctly Ubuntu 22.04 on Wayland, Nvidia Status in chromium-browser package in Ubuntu: Confirmed Bug description: When launching Chromium as a snap on Ubuntu 22.04, it will not open properly and will open the browser with only the titlebar and a transparent window. I am using an Nvidia Graphics card with the 510.60.02 Nvidia proprietary drivers. Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Chromium Version: 100.0.4896.75 2022-04-07 When running "snap run chromium" in the terminal, the following output happens. Attached screenshot of result. nyaa@nyaa-desktop:~$ snap run chromium Gtk-Message: 13:42:20.777: Failed to load module "canberra-gtk-module" Gtk-Message: 13:42:20.778: Failed to load module "canberra-gtk-module" MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to open nvidia-drm: /snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri/nvidia-drm_dri.so: cannot open shared object file: Permission denied (search paths /snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri) failed to load driver: nvidia-drm MESA-LOADER: failed to open kms_swrast: /snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri/kms_swrast_dri.so: cannot open shared object file: Permission denied (search paths /snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri) failed to load driver: kms_swrast MESA-LOADER: failed to open swrast: /snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so: cannot open shared object file: Permission denied (search paths /snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri) failed to load swrast driver [9358:9478:0411/134223.111306:ERROR:udev_watcher.cc(98)] Failed to begin udev enumeration. Edit: I have recently tested this more, and I've isolated it to Wayland and the snap version of Chromium. On X, the chromium snap runs correctly. When I run Chromium as a direct download, the issue doesn't occur on Wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1968610/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003111] Re: ASAN catches bug in v4l kernel module.
lunar running on VM, kernel version 5.19.0-21-generic is not affected. kinetic running on HW, kernel version 5.19.0-29-generic is affected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003111 Title: ASAN catches bug in v4l kernel module. Status in linux package in Ubuntu: Confirmed Bug description: The package linux-modules-extra-5.19.0-29-generic has a kernel module named vivid.ko for artificial v4l streams. When I modprobe the vivid.ko module, an invalid operation is detected by ASAN, and the created of /dev/video0 device file fails. The offending call is v4l_querymenu The offending operation is shift-out-of-bounds I tried this in a virtual machine of lunar (23.04) where the modprobe succeeded. But it fails on the real machine, running kinetic (22.10) This is a kernel bug. ``` [ 6028.277644] vivid-000: using single planar format API [ 6028.278261] Registered IR keymap rc-cec [ 6028.278304] rc rc0: vivid-000-vid-cap0 as /devices/platform/vivid.0/rc/rc0 [ 6028.278329] input: vivid-000-vid-cap0 as /devices/platform/vivid.0/rc/rc0/input34 [ 6028.278395] vivid-000: CEC adapter cec0 registered for HDMI input 0 [ 6028.278420] vivid-000: V4L2 capture device registered as video3 [ 6028.278422] Registered IR keymap rc-cec [ 6028.278433] rc rc1: vivid-000-vid-out0 as /devices/platform/vivid.0/rc/rc1 [ 6028.278451] input: vivid-000-vid-out0 as /devices/platform/vivid.0/rc/rc1/input35 [ 6028.278491] vivid-000: CEC adapter cec1 registered for HDMI output 0 [ 6028.278512] vivid-000: V4L2 output device registered as video4 [ 6028.278531] vivid-000: V4L2 capture device registered as vbi0, supports raw and sliced VBI [ 6028.278550] vivid-000: V4L2 output device registered as vbi1, supports raw and sliced VBI [ 6028.278571] vivid-000: V4L2 capture device registered as swradio0 [ 6028.278590] vivid-000: V4L2 receiver device registered as radio0 [ 6028.278609] vivid-000: V4L2 transmitter device registered as radio1 [ 6028.278628] vivid-000: V4L2 metadata capture device registered as video5 [ 6028.278649] vivid-000: V4L2 metadata output device registered as video6 [ 6028.278669] vivid-000: V4L2 touch capture device registered as v4l-touch0 [ 6028.302648] [ 6028.302651] UBSAN: shift-out-of-bounds in /build/linux-qLbdtO/linux-5.19.0/drivers/media/v4l2-core/v4l2-ctrls-api.c:1102:35 [ 6028.302652] shift exponent 64 is too large for 64-bit type 'long long unsigned int' [ 6028.302654] CPU: 4 PID: 2138 Comm: pipewire Not tainted 5.19.0-29-generic #30-Ubuntu [ 6028.302656] Hardware name: ASUS System Product Name/PRIME Z690M-PLUS D4, BIOS 1008 01/13/2022 [ 6028.302656] Call Trace: [ 6028.302657] [ 6028.302659] show_stack+0x4e/0x61 [ 6028.302663] dump_stack_lvl+0x4a/0x6f [ 6028.302665] dump_stack+0x10/0x18 [ 6028.302666] ubsan_epilogue+0x9/0x43 [ 6028.302668] __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef [ 6028.302669] ? mutex_lock+0x12/0x50 [ 6028.302673] v4l2_querymenu.cold+0x24/0x39 [videodev] [ 6028.302681] v4l_querymenu+0x81/0xa0 [videodev] [ 6028.302686] __video_do_ioctl+0x1e7/0x590 [videodev] [ 6028.302691] video_usercopy+0x14b/0x730 [videodev] [ 6028.302696] ? video_get_user.constprop.0+0x1d0/0x1d0 [videodev] [ 6028.302700] video_ioctl2+0x15/0x30 [videodev] [ 6028.302705] v4l2_ioctl+0x69/0xb0 [videodev] [ 6028.302709] __x64_sys_ioctl+0x9d/0xe0 [ 6028.302711] do_syscall_64+0x58/0x90 [ 6028.302712] ? do_syscall_64+0x67/0x90 [ 6028.302712] ? do_syscall_64+0x67/0x90 [ 6028.302713] entry_SYSCALL_64_after_hwframe+0x63/0xcd [ 6028.302715] RIP: 0033:0x7f8631712d8f [ 6028.302717] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 [ 6028.302717] RSP: 002b:7ffd35484ed0 EFLAGS: 0246 ORIG_RAX: 0010 [ 6028.302719] RAX: ffda RBX: 0400 RCX: 7f8631712d8f [ 6028.302720] RDX: 7ffd35485050 RSI: c02c5625 RDI: 0032 [ 6028.302720] RBP: 000b R08: 0a58 R09: 000b [ 6028.302721] R10: 0008000c R11: 0246 R12: 7ffd35485058 [ 6028.302721] R13: 7ffd35485050 R14: 55959cc26a48 R15: 0032 [ 6028.302723] [ 6028.302724] ``` ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-modules-extra-5.19.0-29-generic 5.19.0-29.30 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse:
[Kernel-packages] [Bug 2003111] [NEW] ASAN catches bug in v4l kernel module.
Public bug reported: The package linux-modules-extra-5.19.0-29-generic has a kernel module named vivid.ko for artificial v4l streams. When I modprobe the vivid.ko module, an invalid operation is detected by ASAN, and the created of /dev/video0 device file fails. The offending call is v4l_querymenu The offending operation is shift-out-of-bounds I tried this in a virtual machine of lunar (23.04) where the modprobe succeeded. But it fails on the real machine, running kinetic (22.10) This is a kernel bug. ``` [ 6028.277644] vivid-000: using single planar format API [ 6028.278261] Registered IR keymap rc-cec [ 6028.278304] rc rc0: vivid-000-vid-cap0 as /devices/platform/vivid.0/rc/rc0 [ 6028.278329] input: vivid-000-vid-cap0 as /devices/platform/vivid.0/rc/rc0/input34 [ 6028.278395] vivid-000: CEC adapter cec0 registered for HDMI input 0 [ 6028.278420] vivid-000: V4L2 capture device registered as video3 [ 6028.278422] Registered IR keymap rc-cec [ 6028.278433] rc rc1: vivid-000-vid-out0 as /devices/platform/vivid.0/rc/rc1 [ 6028.278451] input: vivid-000-vid-out0 as /devices/platform/vivid.0/rc/rc1/input35 [ 6028.278491] vivid-000: CEC adapter cec1 registered for HDMI output 0 [ 6028.278512] vivid-000: V4L2 output device registered as video4 [ 6028.278531] vivid-000: V4L2 capture device registered as vbi0, supports raw and sliced VBI [ 6028.278550] vivid-000: V4L2 output device registered as vbi1, supports raw and sliced VBI [ 6028.278571] vivid-000: V4L2 capture device registered as swradio0 [ 6028.278590] vivid-000: V4L2 receiver device registered as radio0 [ 6028.278609] vivid-000: V4L2 transmitter device registered as radio1 [ 6028.278628] vivid-000: V4L2 metadata capture device registered as video5 [ 6028.278649] vivid-000: V4L2 metadata output device registered as video6 [ 6028.278669] vivid-000: V4L2 touch capture device registered as v4l-touch0 [ 6028.302648] [ 6028.302651] UBSAN: shift-out-of-bounds in /build/linux-qLbdtO/linux-5.19.0/drivers/media/v4l2-core/v4l2-ctrls-api.c:1102:35 [ 6028.302652] shift exponent 64 is too large for 64-bit type 'long long unsigned int' [ 6028.302654] CPU: 4 PID: 2138 Comm: pipewire Not tainted 5.19.0-29-generic #30-Ubuntu [ 6028.302656] Hardware name: ASUS System Product Name/PRIME Z690M-PLUS D4, BIOS 1008 01/13/2022 [ 6028.302656] Call Trace: [ 6028.302657] [ 6028.302659] show_stack+0x4e/0x61 [ 6028.302663] dump_stack_lvl+0x4a/0x6f [ 6028.302665] dump_stack+0x10/0x18 [ 6028.302666] ubsan_epilogue+0x9/0x43 [ 6028.302668] __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef [ 6028.302669] ? mutex_lock+0x12/0x50 [ 6028.302673] v4l2_querymenu.cold+0x24/0x39 [videodev] [ 6028.302681] v4l_querymenu+0x81/0xa0 [videodev] [ 6028.302686] __video_do_ioctl+0x1e7/0x590 [videodev] [ 6028.302691] video_usercopy+0x14b/0x730 [videodev] [ 6028.302696] ? video_get_user.constprop.0+0x1d0/0x1d0 [videodev] [ 6028.302700] video_ioctl2+0x15/0x30 [videodev] [ 6028.302705] v4l2_ioctl+0x69/0xb0 [videodev] [ 6028.302709] __x64_sys_ioctl+0x9d/0xe0 [ 6028.302711] do_syscall_64+0x58/0x90 [ 6028.302712] ? do_syscall_64+0x67/0x90 [ 6028.302712] ? do_syscall_64+0x67/0x90 [ 6028.302713] entry_SYSCALL_64_after_hwframe+0x63/0xcd [ 6028.302715] RIP: 0033:0x7f8631712d8f [ 6028.302717] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 [ 6028.302717] RSP: 002b:7ffd35484ed0 EFLAGS: 0246 ORIG_RAX: 0010 [ 6028.302719] RAX: ffda RBX: 0400 RCX: 7f8631712d8f [ 6028.302720] RDX: 7ffd35485050 RSI: c02c5625 RDI: 0032 [ 6028.302720] RBP: 000b R08: 0a58 R09: 000b [ 6028.302721] R10: 0008000c R11: 0246 R12: 7ffd35485058 [ 6028.302721] R13: 7ffd35485050 R14: 55959cc26a48 R15: 0032 [ 6028.302723] [ 6028.302724] ``` ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-modules-extra-5.19.0-29-generic 5.19.0-29.30 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stolk 2160 F wireplumber /dev/snd/controlC0: stolk 2160 F wireplumber /dev/snd/seq:stolk 2138 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 10:12:44 2023 Dependencies: linux-modules-5.19.0-29-generic 5.19.0-29.30 wireless-regdb 2022.06.06-0ubuntu1 InstallationDate: Installed on 2022-08-26 (144 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220825) MachineType: ASUS System Product Name
[Desktop-packages] [Bug 1999924] Re: Unsupported buffer format 842094158
Ugh, this may need revisiting. Even though it stops the crash, it also seems to stop hardware decode support for me. I would have sworn I tested with intel_gpu_top, but on the current edge build, I see no HW acceleration anymore. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/124 Title: Unsupported buffer format 842094158 Status in chromium-browser package in Ubuntu: Fix Committed Bug description: This is with 107.0.5304.121-hwacc from latest/candidate/hwacc on Ubuntu 22.10 Wayland. When playing a h264 video, or a youtube video, I get: ``` $ snap info chromium | grep installed installed: 107.0.5304.121-hwacc(2224) 171MB - $ chromium ~/sample.mp4 Gtk-Message: 09:25:06.701: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. [15876:15876:1216/092506.880657:ERROR:gpu_init.cc(537)] Passthrough is not supported, GL is egl, ANGLE is [15747:15837:1216/092506.908136:ERROR:top_sites_backend.cc(79)] Failed to initialize database. [15747:15747:1216/092507.059802:ERROR:wayland_event_watcher.cc(36)] libwayland: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 842094158 Trace/breakpoint trap (core dumped) ``` Test video: https://test- videos.co.uk/vids/bigbuckbunny/mp4/h264/1080/Big_Buck_Bunny_1080_10s_30MB.mp4 I will try other hwacc versions and a non-hwacc version to see if they behave differently. OS: Ubuntu 22.10 Desktop: Wayland GPU: Intel AlderLake-S GT1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000175] Re: [snap] latest/candidate/hwacc channel cause lots of Apparmor noise
I have made a Pull Request for upstream. https://github.com/intel/media-driver/pull/1588 Once this is merged and released, we should pick this up in our snap build. By setting GFX_FEATURE_FILE and GFX_FEATURE_FILE_NEXT we can then prevent access to /etc/ dir. ** Changed in: chromium-browser (Ubuntu) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2000175 Title: [snap] latest/candidate/hwacc channel cause lots of Apparmor noise Status in chromium-browser package in Ubuntu: Confirmed Bug description: # Issue description After installing chromium with hwacc (snap refresh chromium --channel latest/candidate/hwacc) I notice a lot of those new messages in dmesg: Dec 20 13:38:13 sdeziel-lemur kernel: audit: type=1400 audit(1671561493.126:3297): apparmor="DENIED" operation="mknod" profile="snap.chromium.chromium" name="/etc/igfx_user_feature.txt" pid=515408 comm="chrome" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 Dec 20 13:38:13 sdeziel-lemur kernel: audit: type=1400 audit(1671561493.126:3298): apparmor="DENIED" operation="mknod" profile="snap.chromium.chromium" name="/etc/igfx_user_feature_next.txt" pid=515408 comm="chrome" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 Those 2 files do not exist in the host's filesystem: $ ls /etc/igfx_user_feature.txt /etc/igfx_user_feature_next.txt ls: cannot access '/etc/igfx_user_feature.txt': No such file or directory ls: cannot access '/etc/igfx_user_feature_next.txt': No such file or directory # Additional information $ uname -a Linux sdeziel-lemur 5.15.0-56-generic #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ snap list chromium core20 snapd Name Version RevTrackingPublisher Notes chromium 107.0.5304.121-hwacc 2224 latest/candidate/… canonical✓ - core2020221123 1738 latest/stable canonical✓ base snapd 2.57.617883 latest/stable canonical✓ snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2000175/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc
Intel provided guidance on how to address this. I will make a merge
request.
** Changed in: chromium-browser (Ubuntu)
Assignee: Nathan Teodosio (nteodosio) => Bram Stolk (b-stolk)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1999487
Title:
Webcam does not work with v107.0.5304.121-hwacc
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
With the latest version of Chromium in the stable channel
(108.0.5359.94), I can access the webcam and the microphone in Google
Meet and Jitsi (using a framatalk.org instance).
However, with version 107.0.5304.121-hwacc (from
latest/candidate/hwacc branch), the same test does not work.
The only difference between the two in `snap connections chromium` is
content chromium:va-driver-non-free -
-
Test:
1. Install Chromium from the given channel
2. Go to https://framatalk.org/ and click on "Create a room"
3. Accept the permissions to access Microphone and Camera
Expected result:
Image from camera is displayed on screen
Actual result:
The webcam is turned on (the LED turns on), but no image is captured,
and after a few seconds, an error message is displayed ("We are unable
to access your camera").
In the settings, I can see the camera name ("UVC Camera (046d:0802)").
Attached are two logs:
- One retrieved by launching Chromium with `chromium
--enable-logging=stderr`, accessing framatalk.org and clicking on "Create a
room".
- One retrieved by launching Chromium with `chromium --enable-logging=stderr`
and accessing a Google Meet event.
Configuration information
=
- Desktop with AMD GPU RX580
- Ubuntu 20.04 (kernel 5.15.0-56-generic)
- Webcam: 046d:0802 Logitech, Inc. Webcam C200
- Headset: 046d:0a38 Logitech, Inc. Headset H340
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc
My current theory is that we broke video input for non Intel platforms.
On my machine with AMD GPU, I get:
ERROR:gpu_memory_buffer_support_x11.cc(134)] Can't create buffer -- gbm
device is missing
$ inxi -G
Graphics:
Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
driver: amdgpu v: kernel
Device-2: Logitech QuickCam Vision Pro type: USB
driver: snd-usb-audio,uvcvideo
Display: server: X.Org v: 1.22.1.3 driver: X: loaded: amdgpu,ati
unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu
resolution: 3840x2160~120Hz
OpenGL: renderer: llvmpipe (LLVM 13.0.1 256 bits) v: 4.5 Mesa 22.0.5
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1999487
Title:
Webcam does not work with v107.0.5304.121-hwacc
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
With the latest version of Chromium in the stable channel
(108.0.5359.94), I can access the webcam and the microphone in Google
Meet and Jitsi (using a framatalk.org instance).
However, with version 107.0.5304.121-hwacc (from
latest/candidate/hwacc branch), the same test does not work.
The only difference between the two in `snap connections chromium` is
content chromium:va-driver-non-free -
-
Test:
1. Install Chromium from the given channel
2. Go to https://framatalk.org/ and click on "Create a room"
3. Accept the permissions to access Microphone and Camera
Expected result:
Image from camera is displayed on screen
Actual result:
The webcam is turned on (the LED turns on), but no image is captured,
and after a few seconds, an error message is displayed ("We are unable
to access your camera").
In the settings, I can see the camera name ("UVC Camera (046d:0802)").
Attached are two logs:
- One retrieved by launching Chromium with `chromium
--enable-logging=stderr`, accessing framatalk.org and clicking on "Create a
room".
- One retrieved by launching Chromium with `chromium --enable-logging=stderr`
and accessing a Google Meet event.
Configuration information
=
- Desktop with AMD GPU RX580
- Ubuntu 20.04 (kernel 5.15.0-56-generic)
- Webcam: 046d:0802 Logitech, Inc. Webcam C200
- Headset: 046d:0a38 Logitech, Inc. Headset H340
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc
@ikepanhc Which GPU do you have? Intel, AMD or nVidia?
$ sudo apt install inxi
$ inxi -G
Thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1999487
Title:
Webcam does not work with v107.0.5304.121-hwacc
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
With the latest version of Chromium in the stable channel
(108.0.5359.94), I can access the webcam and the microphone in Google
Meet and Jitsi (using a framatalk.org instance).
However, with version 107.0.5304.121-hwacc (from
latest/candidate/hwacc branch), the same test does not work.
The only difference between the two in `snap connections chromium` is
content chromium:va-driver-non-free -
-
Test:
1. Install Chromium from the given channel
2. Go to https://framatalk.org/ and click on "Create a room"
3. Accept the permissions to access Microphone and Camera
Expected result:
Image from camera is displayed on screen
Actual result:
The webcam is turned on (the LED turns on), but no image is captured,
and after a few seconds, an error message is displayed ("We are unable
to access your camera").
In the settings, I can see the camera name ("UVC Camera (046d:0802)").
Attached are two logs:
- One retrieved by launching Chromium with `chromium
--enable-logging=stderr`, accessing framatalk.org and clicking on "Create a
room".
- One retrieved by launching Chromium with `chromium --enable-logging=stderr`
and accessing a Google Meet event.
Configuration information
=
- Desktop with AMD GPU RX580
- Ubuntu 20.04 (kernel 5.15.0-56-generic)
- Webcam: 046d:0802 Logitech, Inc. Webcam C200
- Headset: 046d:0a38 Logitech, Inc. Headset H340
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000175] Re: [snap] latest/candidate/hwacc channel cause lots of Apparmor noise
Just logging this here: I tried solving this with the `GFX_FEATURE_FILE` environment variable: `GFX_FEATURE_FILE=$SNAP_USER_COMMON/igfx_user_feature.txt` But unfortunately that did not prevent the media driver from using `/etc/` I think the file name override gets taken out by the precompiler. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2000175 Title: [snap] latest/candidate/hwacc channel cause lots of Apparmor noise Status in chromium-browser package in Ubuntu: Confirmed Bug description: # Issue description After installing chromium with hwacc (snap refresh chromium --channel latest/candidate/hwacc) I notice a lot of those new messages in dmesg: Dec 20 13:38:13 sdeziel-lemur kernel: audit: type=1400 audit(1671561493.126:3297): apparmor="DENIED" operation="mknod" profile="snap.chromium.chromium" name="/etc/igfx_user_feature.txt" pid=515408 comm="chrome" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 Dec 20 13:38:13 sdeziel-lemur kernel: audit: type=1400 audit(1671561493.126:3298): apparmor="DENIED" operation="mknod" profile="snap.chromium.chromium" name="/etc/igfx_user_feature_next.txt" pid=515408 comm="chrome" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 Those 2 files do not exist in the host's filesystem: $ ls /etc/igfx_user_feature.txt /etc/igfx_user_feature_next.txt ls: cannot access '/etc/igfx_user_feature.txt': No such file or directory ls: cannot access '/etc/igfx_user_feature_next.txt': No such file or directory # Additional information $ uname -a Linux sdeziel-lemur 5.15.0-56-generic #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ snap list chromium core20 snapd Name Version RevTrackingPublisher Notes chromium 107.0.5304.121-hwacc 2224 latest/candidate/… canonical✓ - core2020221123 1738 latest/stable canonical✓ base snapd 2.57.617883 latest/stable canonical✓ snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2000175/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc
Note: the `content chromium:va-driver-non-free` connection is completely
harmless.
We just added an extra path to get drivers from an alternate snap if so
required, in the future, for patent reasons.
This is a currently unused provision, and no free drivers are built or
used.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1999487
Title:
Webcam does not work with v107.0.5304.121-hwacc
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
With the latest version of Chromium in the stable channel
(108.0.5359.94), I can access the webcam and the microphone in Google
Meet and Jitsi (using a framatalk.org instance).
However, with version 107.0.5304.121-hwacc (from
latest/candidate/hwacc branch), the same test does not work.
The only difference between the two in `snap connections chromium` is
content chromium:va-driver-non-free -
-
Test:
1. Install Chromium from the given channel
2. Go to https://framatalk.org/ and click on "Create a room"
3. Accept the permissions to access Microphone and Camera
Expected result:
Image from camera is displayed on screen
Actual result:
The webcam is turned on (the LED turns on), but no image is captured,
and after a few seconds, an error message is displayed ("We are unable
to access your camera").
In the settings, I can see the camera name ("UVC Camera (046d:0802)").
Attached are two logs:
- One retrieved by launching Chromium with `chromium
--enable-logging=stderr`, accessing framatalk.org and clicking on "Create a
room".
- One retrieved by launching Chromium with `chromium --enable-logging=stderr`
and accessing a Google Meet event.
Configuration information
=
- Desktop with AMD GPU RX580
- Ubuntu 20.04 (kernel 5.15.0-56-generic)
- Webcam: 046d:0802 Logitech, Inc. Webcam C200
- Headset: 046d:0a38 Logitech, Inc. Headset H340
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000175] Re: [snap] latest/candidate/hwacc channel cause lots of Apparmor noise
I've traced it down to the Intel Media Driver's profiling: https://github.com/intel/media- driver/tree/master/Tools/MediaDriverTools/UMDPerfProfiler UMD Performance Profiler (I am pretty sure that here, UMD stands for User Mode Driver.) I will try to find a way to disable the profiling altogether, or at the very least make sure the media driver does not try to create these files in `/etc/` dir. It could possibly be a build flag we should toggle. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2000175 Title: [snap] latest/candidate/hwacc channel cause lots of Apparmor noise Status in chromium-browser package in Ubuntu: Confirmed Bug description: # Issue description After installing chromium with hwacc (snap refresh chromium --channel latest/candidate/hwacc) I notice a lot of those new messages in dmesg: Dec 20 13:38:13 sdeziel-lemur kernel: audit: type=1400 audit(1671561493.126:3297): apparmor="DENIED" operation="mknod" profile="snap.chromium.chromium" name="/etc/igfx_user_feature.txt" pid=515408 comm="chrome" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 Dec 20 13:38:13 sdeziel-lemur kernel: audit: type=1400 audit(1671561493.126:3298): apparmor="DENIED" operation="mknod" profile="snap.chromium.chromium" name="/etc/igfx_user_feature_next.txt" pid=515408 comm="chrome" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 Those 2 files do not exist in the host's filesystem: $ ls /etc/igfx_user_feature.txt /etc/igfx_user_feature_next.txt ls: cannot access '/etc/igfx_user_feature.txt': No such file or directory ls: cannot access '/etc/igfx_user_feature_next.txt': No such file or directory # Additional information $ uname -a Linux sdeziel-lemur 5.15.0-56-generic #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ snap list chromium core20 snapd Name Version RevTrackingPublisher Notes chromium 107.0.5304.121-hwacc 2224 latest/candidate/… canonical✓ - core2020221123 1738 latest/stable canonical✓ base snapd 2.57.617883 latest/stable canonical✓ snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2000175/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000175] Re: [snap] latest/candidate/hwacc channel cause lots of Apparmor noise
I confirm that I see the same. I will try a non-hwacc build to see if this is specific to hwacc. NOTE: It wants to create that file. It uses mknod() but to create a normal file, not a special file. On systems that have this file, it wants to open it for reading. We should find out what is going on, here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2000175 Title: [snap] latest/candidate/hwacc channel cause lots of Apparmor noise Status in chromium-browser package in Ubuntu: New Bug description: # Issue description After installing chromium with hwacc (snap refresh chromium --channel latest/candidate/hwacc) I notice a lot of those new messages in dmesg: Dec 20 13:38:13 sdeziel-lemur kernel: audit: type=1400 audit(1671561493.126:3297): apparmor="DENIED" operation="mknod" profile="snap.chromium.chromium" name="/etc/igfx_user_feature.txt" pid=515408 comm="chrome" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 Dec 20 13:38:13 sdeziel-lemur kernel: audit: type=1400 audit(1671561493.126:3298): apparmor="DENIED" operation="mknod" profile="snap.chromium.chromium" name="/etc/igfx_user_feature_next.txt" pid=515408 comm="chrome" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 Those 2 files do not exist in the host's filesystem: $ ls /etc/igfx_user_feature.txt /etc/igfx_user_feature_next.txt ls: cannot access '/etc/igfx_user_feature.txt': No such file or directory ls: cannot access '/etc/igfx_user_feature_next.txt': No such file or directory # Additional information $ uname -a Linux sdeziel-lemur 5.15.0-56-generic #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ snap list chromium core20 snapd Name Version RevTrackingPublisher Notes chromium 107.0.5304.121-hwacc 2224 latest/candidate/… canonical✓ - core2020221123 1738 latest/stable canonical✓ base snapd 2.57.617883 latest/stable canonical✓ snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2000175/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999924] Re: Unsupported buffer format 842094158
https://code.launchpad.net/~b-stolk/chromium-browser/+git/snap-from- source/+merge/435082 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/124 Title: Unsupported buffer format 842094158 Status in chromium-browser package in Ubuntu: New Bug description: This is with 107.0.5304.121-hwacc from latest/candidate/hwacc on Ubuntu 22.10 Wayland. When playing a h264 video, or a youtube video, I get: ``` $ snap info chromium | grep installed installed: 107.0.5304.121-hwacc(2224) 171MB - $ chromium ~/sample.mp4 Gtk-Message: 09:25:06.701: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. [15876:15876:1216/092506.880657:ERROR:gpu_init.cc(537)] Passthrough is not supported, GL is egl, ANGLE is [15747:15837:1216/092506.908136:ERROR:top_sites_backend.cc(79)] Failed to initialize database. [15747:15747:1216/092507.059802:ERROR:wayland_event_watcher.cc(36)] libwayland: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 842094158 Trace/breakpoint trap (core dumped) ``` Test video: https://test- videos.co.uk/vids/bigbuckbunny/mp4/h264/1080/Big_Buck_Bunny_1080_10s_30MB.mp4 I will try other hwacc versions and a non-hwacc version to see if they behave differently. OS: Ubuntu 22.10 Desktop: Wayland GPU: Intel AlderLake-S GT1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999924] Re: Unsupported buffer format 842094158
** Description changed: This is with 107.0.5304.121-hwacc from latest/candidate/hwacc on Ubuntu 22.10 Wayland. When playing a h264 video, or a youtube video, I get: ``` $ snap info chromium | grep installed installed: 107.0.5304.121-hwacc(2224) 171MB - $ chromium ~/sample.mp4 Gtk-Message: 09:25:06.701: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. - [15876:15876:1216/092506.880657:ERROR:gpu_init.cc(537)] Passthrough is not supported, GL is egl, ANGLE is + [15876:15876:1216/092506.880657:ERROR:gpu_init.cc(537)] Passthrough is not supported, GL is egl, ANGLE is [15747:15837:1216/092506.908136:ERROR:top_sites_backend.cc(79)] Failed to initialize database. [15747:15747:1216/092507.059802:ERROR:wayland_event_watcher.cc(36)] libwayland: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 842094158 Trace/breakpoint trap (core dumped) ``` Test video: https://test- videos.co.uk/vids/bigbuckbunny/mp4/h264/1080/Big_Buck_Bunny_1080_10s_30MB.mp4 I will try other hwacc versions and a non-hwacc version to see if they behave differently. + + OS: Ubuntu 22.10 + + Desktop: Wayland + + GPU: Intel AlderLake-S GT1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/124 Title: Unsupported buffer format 842094158 Status in chromium-browser package in Ubuntu: New Bug description: This is with 107.0.5304.121-hwacc from latest/candidate/hwacc on Ubuntu 22.10 Wayland. When playing a h264 video, or a youtube video, I get: ``` $ snap info chromium | grep installed installed: 107.0.5304.121-hwacc(2224) 171MB - $ chromium ~/sample.mp4 Gtk-Message: 09:25:06.701: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. [15876:15876:1216/092506.880657:ERROR:gpu_init.cc(537)] Passthrough is not supported, GL is egl, ANGLE is [15747:15837:1216/092506.908136:ERROR:top_sites_backend.cc(79)] Failed to initialize database. [15747:15747:1216/092507.059802:ERROR:wayland_event_watcher.cc(36)] libwayland: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 842094158 Trace/breakpoint trap (core dumped) ``` Test video: https://test- videos.co.uk/vids/bigbuckbunny/mp4/h264/1080/Big_Buck_Bunny_1080_10s_30MB.mp4 I will try other hwacc versions and a non-hwacc version to see if they behave differently. OS: Ubuntu 22.10 Desktop: Wayland GPU: Intel AlderLake-S GT1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999924] Re: Unsupported buffer format 842094158
108.0.5359.124 from latest/candidate plays video without crashing. 109.0.5414.36-hwacc from latest/beta/hwacc has the same crash. Adding --ozone-platform=x11 stops the crash. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/124 Title: Unsupported buffer format 842094158 Status in chromium-browser package in Ubuntu: New Bug description: This is with 107.0.5304.121-hwacc from latest/candidate/hwacc on Ubuntu 22.10 Wayland. When playing a h264 video, or a youtube video, I get: ``` $ snap info chromium | grep installed installed: 107.0.5304.121-hwacc(2224) 171MB - $ chromium ~/sample.mp4 Gtk-Message: 09:25:06.701: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. [15876:15876:1216/092506.880657:ERROR:gpu_init.cc(537)] Passthrough is not supported, GL is egl, ANGLE is [15747:15837:1216/092506.908136:ERROR:top_sites_backend.cc(79)] Failed to initialize database. [15747:15747:1216/092507.059802:ERROR:wayland_event_watcher.cc(36)] libwayland: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 842094158 Trace/breakpoint trap (core dumped) ``` Test video: https://test- videos.co.uk/vids/bigbuckbunny/mp4/h264/1080/Big_Buck_Bunny_1080_10s_30MB.mp4 I will try other hwacc versions and a non-hwacc version to see if they behave differently. OS: Ubuntu 22.10 Desktop: Wayland GPU: Intel AlderLake-S GT1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999924] [NEW] Unsupported buffer format 842094158
Public bug reported: This is with 107.0.5304.121-hwacc from latest/candidate/hwacc on Ubuntu 22.10 Wayland. When playing a h264 video, or a youtube video, I get: ``` $ snap info chromium | grep installed installed: 107.0.5304.121-hwacc(2224) 171MB - $ chromium ~/sample.mp4 Gtk-Message: 09:25:06.701: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. [15876:15876:1216/092506.880657:ERROR:gpu_init.cc(537)] Passthrough is not supported, GL is egl, ANGLE is [15747:15837:1216/092506.908136:ERROR:top_sites_backend.cc(79)] Failed to initialize database. [15747:15747:1216/092507.059802:ERROR:wayland_event_watcher.cc(36)] libwayland: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 842094158 Trace/breakpoint trap (core dumped) ``` Test video: https://test- videos.co.uk/vids/bigbuckbunny/mp4/h264/1080/Big_Buck_Bunny_1080_10s_30MB.mp4 I will try other hwacc versions and a non-hwacc version to see if they behave differently. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/124 Title: Unsupported buffer format 842094158 Status in chromium-browser package in Ubuntu: New Bug description: This is with 107.0.5304.121-hwacc from latest/candidate/hwacc on Ubuntu 22.10 Wayland. When playing a h264 video, or a youtube video, I get: ``` $ snap info chromium | grep installed installed: 107.0.5304.121-hwacc(2224) 171MB - $ chromium ~/sample.mp4 Gtk-Message: 09:25:06.701: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. [15876:15876:1216/092506.880657:ERROR:gpu_init.cc(537)] Passthrough is not supported, GL is egl, ANGLE is [15747:15837:1216/092506.908136:ERROR:top_sites_backend.cc(79)] Failed to initialize database. [15747:15747:1216/092507.059802:ERROR:wayland_event_watcher.cc(36)] libwayland: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 842094158 Trace/breakpoint trap (core dumped) ``` Test video: https://test- videos.co.uk/vids/bigbuckbunny/mp4/h264/1080/Big_Buck_Bunny_1080_10s_30MB.mp4 I will try other hwacc versions and a non-hwacc version to see if they behave differently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1999698] [NEW] Dodgy looking patch applied to our build.
Public bug reported: When building accountsservice we apply patches, among of which is `0010-set-language.patch` which raises concerns. It will not compile without warnings: At the very least contains misleading indentation. ``` [92/99] Compiling C object src/accounts-daemon.p/user.c.o ../src/user.c: In function ‘user_HOME_available’: ../src/user.c:1753:27: warning: this ‘else’ clause does not guard... [-Wmisleading-indentation] 1753 | } else | ^~~~ ../src/user.c:1755:33: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘else’ 1755 | break; | ^ ``` The code: ``` } else g_free (path_to_entry); break; ``` ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1999698 Title: Dodgy looking patch applied to our build. Status in accountsservice package in Ubuntu: New Bug description: When building accountsservice we apply patches, among of which is `0010-set-language.patch` which raises concerns. It will not compile without warnings: At the very least contains misleading indentation. ``` [92/99] Compiling C object src/accounts-daemon.p/user.c.o ../src/user.c: In function ‘user_HOME_available’: ../src/user.c:1753:27: warning: this ‘else’ clause does not guard... [-Wmisleading-indentation] 1753 | } else | ^~~~ ../src/user.c:1755:33: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘else’ 1755 | break; | ^ ``` The code: ``` } else g_free (path_to_entry); break; ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1999698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999698] [NEW] Dodgy looking patch applied to our build.
Public bug reported: When building accountsservice we apply patches, among of which is `0010-set-language.patch` which raises concerns. It will not compile without warnings: At the very least contains misleading indentation. ``` [92/99] Compiling C object src/accounts-daemon.p/user.c.o ../src/user.c: In function ‘user_HOME_available’: ../src/user.c:1753:27: warning: this ‘else’ clause does not guard... [-Wmisleading-indentation] 1753 | } else | ^~~~ ../src/user.c:1755:33: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘else’ 1755 | break; | ^ ``` The code: ``` } else g_free (path_to_entry); break; ``` ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1999698 Title: Dodgy looking patch applied to our build. Status in accountsservice package in Ubuntu: New Bug description: When building accountsservice we apply patches, among of which is `0010-set-language.patch` which raises concerns. It will not compile without warnings: At the very least contains misleading indentation. ``` [92/99] Compiling C object src/accounts-daemon.p/user.c.o ../src/user.c: In function ‘user_HOME_available’: ../src/user.c:1753:27: warning: this ‘else’ clause does not guard... [-Wmisleading-indentation] 1753 | } else | ^~~~ ../src/user.c:1755:33: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘else’ 1755 | break; | ^ ``` The code: ``` } else g_free (path_to_entry); break; ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1999698/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1999698] [NEW] Dodgy looking patch applied to our build.
Public bug reported: When building accountsservice we apply patches, among of which is `0010-set-language.patch` which raises concerns. It will not compile without warnings: At the very least contains misleading indentation. ``` [92/99] Compiling C object src/accounts-daemon.p/user.c.o ../src/user.c: In function ‘user_HOME_available’: ../src/user.c:1753:27: warning: this ‘else’ clause does not guard... [-Wmisleading-indentation] 1753 | } else | ^~~~ ../src/user.c:1755:33: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘else’ 1755 | break; | ^ ``` The code: ``` } else g_free (path_to_entry); break; ``` ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1999698 Title: Dodgy looking patch applied to our build. Status in accountsservice package in Ubuntu: New Bug description: When building accountsservice we apply patches, among of which is `0010-set-language.patch` which raises concerns. It will not compile without warnings: At the very least contains misleading indentation. ``` [92/99] Compiling C object src/accounts-daemon.p/user.c.o ../src/user.c: In function ‘user_HOME_available’: ../src/user.c:1753:27: warning: this ‘else’ clause does not guard... [-Wmisleading-indentation] 1753 | } else | ^~~~ ../src/user.c:1755:33: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘else’ 1755 | break; | ^ ``` The code: ``` } else g_free (path_to_entry); break; ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1999698/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Bug 1999698] [NEW] Dodgy looking patch applied to our build.
Public bug reported: When building accountsservice we apply patches, among of which is `0010-set-language.patch` which raises concerns. It will not compile without warnings: At the very least contains misleading indentation. ``` [92/99] Compiling C object src/accounts-daemon.p/user.c.o ../src/user.c: In function ‘user_HOME_available’: ../src/user.c:1753:27: warning: this ‘else’ clause does not guard... [-Wmisleading-indentation] 1753 | } else | ^~~~ ../src/user.c:1755:33: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘else’ 1755 | break; | ^ ``` The code: ``` } else g_free (path_to_entry); break; ``` ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1999698 Title: Dodgy looking patch applied to our build. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1999698/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Desktop-packages] [Bug 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc
I have tried to repro this.
chromium: 107.0.5304.121-hwacc on Ubuntu 22.10
Logitech, Inc. QuickCam Vision Pro [WORKS]
IMC Networks USB2.0 HD UVC WebCam [WORKS]
Could it be that this issue happens with MIPI cameras only? My tests
were with USB based cams.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1999487
Title:
Webcam does not work with v107.0.5304.121-hwacc
Status in chromium-browser package in Ubuntu:
New
Bug description:
With the latest version of Chromium in the stable channel
(108.0.5359.94), I can access the webcam and the microphone in Google
Meet and Jitsi (using a framatalk.org instance).
However, with version 107.0.5304.121-hwacc (from
latest/candidate/hwacc branch), the same test does not work.
The only difference between the two in `snap connections chromium` is
content chromium:va-driver-non-free -
-
Test:
1. Install Chromium from the given channel
2. Go to https://framatalk.org/ and click on "Create a room"
3. Accept the permissions to access Microphone and Camera
Expected result:
Image from camera is displayed on screen
Actual result:
The webcam is turned on (the LED turns on), but no image is captured,
and after a few seconds, an error message is displayed ("We are unable
to access your camera").
In the settings, I can see the camera name ("UVC Camera (046d:0802)").
Attached are two logs:
- One retrieved by launching Chromium with `chromium
--enable-logging=stderr`, accessing framatalk.org and clicking on "Create a
room".
- One retrieved by launching Chromium with `chromium --enable-logging=stderr`
and accessing a Google Meet event.
Configuration information
=
- Desktop with AMD GPU RX580
- Ubuntu 20.04 (kernel 5.15.0-56-generic)
- Webcam: 046d:0802 Logitech, Inc. Webcam C200
- Headset: 046d:0a38 Logitech, Inc. Headset H340
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc
@ikepanhc Thanks. What model webcam do you have?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1999487
Title:
Webcam does not work with v107.0.5304.121-hwacc
Status in chromium-browser package in Ubuntu:
New
Bug description:
With the latest version of Chromium in the stable channel
(108.0.5359.94), I can access the webcam and the microphone in Google
Meet and Jitsi (using a framatalk.org instance).
However, with version 107.0.5304.121-hwacc (from
latest/candidate/hwacc branch), the same test does not work.
The only difference between the two in `snap connections chromium` is
content chromium:va-driver-non-free -
-
Test:
1. Install Chromium from the given channel
2. Go to https://framatalk.org/ and click on "Create a room"
3. Accept the permissions to access Microphone and Camera
Expected result:
Image from camera is displayed on screen
Actual result:
The webcam is turned on (the LED turns on), but no image is captured,
and after a few seconds, an error message is displayed ("We are unable
to access your camera").
In the settings, I can see the camera name ("UVC Camera (046d:0802)").
Attached are two logs:
- One retrieved by launching Chromium with `chromium
--enable-logging=stderr`, accessing framatalk.org and clicking on "Create a
room".
- One retrieved by launching Chromium with `chromium --enable-logging=stderr`
and accessing a Google Meet event.
Configuration information
=
- Desktop with AMD GPU RX580
- Ubuntu 20.04 (kernel 5.15.0-56-generic)
- Webcam: 046d:0802 Logitech, Inc. Webcam C200
- Headset: 046d:0a38 Logitech, Inc. Headset H340
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837326] Re: platform eisa.0: EISA: Cannot allocate resource for mainboard
@thedoctar Add it to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub file. $ sudo dmesg | grep "Command line" [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic root=/dev/mapper/vgubuntu-root ro quiet splash intel_pstate=passive eisa_bus.disable_dev=1,2,3,4,5,6,7,8 vt.handoff=7 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837326 Title: platform eisa.0: EISA: Cannot allocate resource for mainboard Status in linux package in Ubuntu: Confirmed Bug description: dmesg: [0.889531] platform eisa.0: EISA: Cannot allocate resource for mainboard [0.889533] platform eisa.0: Cannot allocate resource for EISA slot 1 [0.889535] platform eisa.0: Cannot allocate resource for EISA slot 2 [0.889536] platform eisa.0: Cannot allocate resource for EISA slot 3 [0.889537] platform eisa.0: Cannot allocate resource for EISA slot 4 [0.889539] platform eisa.0: Cannot allocate resource for EISA slot 5 [0.889540] platform eisa.0: Cannot allocate resource for EISA slot 6 [0.889541] platform eisa.0: Cannot allocate resource for EISA slot 7 [0.889542] platform eisa.0: Cannot allocate resource for EISA slot 8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-8-generic 5.2.0-8.9 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 3028 F pulseaudio /dev/snd/pcmC0D0p: caravena 3028 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jul 21 12:16:07 2019 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (230 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-8-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2018-12-02 (230 days ago) dmi.bios.date: 04/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Linux-traipu] [Bug 1569601] Re: Audio/Video sync
Should be closed, as it pertains to a very old version. ** Changed in: openshot Status: New => Incomplete -- You received this bug notification because you are a member of UBUNTU - AL - BR, which is subscribed to OpenShot Video Editor. https://bugs.launchpad.net/bugs/1569601 Title: Audio/Video sync Status in OpenShot Video Editor: Incomplete Bug description: Either the audio is 0.2s early during editing, or it is 0.2s late after export to video file. I tried both mov av264 and mp4 av264. OpenShot 1.4.3 Linux ubuntu64 4.2.0-34-generic #39-Ubuntu SMP Thu Mar 10 22:13:01 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux installed with apt-get onto ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/openshot/+bug/1569601/+subscriptions -- Mailing list: https://launchpad.net/~linux-traipu Post to : linux-traipu@lists.launchpad.net Unsubscribe : https://launchpad.net/~linux-traipu More help : https://help.launchpad.net/ListHelp
[Openshot.bugs] [Bug 1569601] Re: Audio/Video sync
Should be closed, as it pertains to a very old version. ** Changed in: openshot Status: New => Incomplete -- You received this bug notification because you are a member of OpenShot Bugs, which is subscribed to OpenShot Video Editor. https://bugs.launchpad.net/bugs/1569601 Title: Audio/Video sync Status in OpenShot Video Editor: Incomplete Bug description: Either the audio is 0.2s early during editing, or it is 0.2s late after export to video file. I tried both mov av264 and mp4 av264. OpenShot 1.4.3 Linux ubuntu64 4.2.0-34-generic #39-Ubuntu SMP Thu Mar 10 22:13:01 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux installed with apt-get onto ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/openshot/+bug/1569601/+subscriptions -- Mailing list: https://launchpad.net/~openshot.bugs Post to : openshot.bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~openshot.bugs More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1998414] Re: libdrm-dev missing man pages
Debian also is missing the same pages: https://manpages.debian.org/bullseye/libdrm- dev/drmModeGetResources.3.en.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1998414 Title: libdrm-dev missing man pages Status in libdrm package in Ubuntu: New Bug description: When I access the man-page for drmModeGetResources I am referred to other pages in "SEE ALSO" ``` SEE ALSO drm(7), drm-kms(7), drmModeGetFB(3), drmModeAddFB(3), drmMod‐ eAddFB2(3), drmModeRmFB(3),drmModeDirtyFB(3),drmMod‐ eGetCrtc(3), drmModeSetCrtc (3), drmModeGetEncoder (3), drm‐ ModeGetConnector(3) ``` However, almost none of these other man-pages exist: ``` $ man drmModeGetEncoder No manual entry for drmModeGetEncoder ``` libdrm-dev is installed: 2.4.113-2 OS: Ubuntu 22.10 ``` $ dpkg -L libdrm-dev /. /usr /usr/include /usr/include/libdrm /usr/include/libdrm/amdgpu.h /usr/include/libdrm/amdgpu_drm.h /usr/include/libdrm/drm.h /usr/include/libdrm/drm_fourcc.h /usr/include/libdrm/drm_mode.h /usr/include/libdrm/drm_sarea.h /usr/include/libdrm/i915_drm.h /usr/include/libdrm/intel_aub.h /usr/include/libdrm/intel_bufmgr.h /usr/include/libdrm/intel_debug.h /usr/include/libdrm/mach64_drm.h /usr/include/libdrm/mga_drm.h /usr/include/libdrm/msm_drm.h /usr/include/libdrm/nouveau /usr/include/libdrm/nouveau/nouveau.h /usr/include/libdrm/nouveau/nvif /usr/include/libdrm/nouveau/nvif/cl0080.h /usr/include/libdrm/nouveau/nvif/cl9097.h /usr/include/libdrm/nouveau/nvif/class.h /usr/include/libdrm/nouveau/nvif/if0002.h /usr/include/libdrm/nouveau/nvif/if0003.h /usr/include/libdrm/nouveau/nvif/ioctl.h /usr/include/libdrm/nouveau/nvif/unpack.h /usr/include/libdrm/nouveau_drm.h /usr/include/libdrm/qxl_drm.h /usr/include/libdrm/r128_drm.h /usr/include/libdrm/r600_pci_ids.h /usr/include/libdrm/radeon_bo.h /usr/include/libdrm/radeon_bo_gem.h /usr/include/libdrm/radeon_bo_int.h /usr/include/libdrm/radeon_cs.h /usr/include/libdrm/radeon_cs_gem.h /usr/include/libdrm/radeon_cs_int.h /usr/include/libdrm/radeon_drm.h /usr/include/libdrm/radeon_surface.h /usr/include/libdrm/savage_drm.h /usr/include/libdrm/sis_drm.h /usr/include/libdrm/tegra_drm.h /usr/include/libdrm/vc4_drm.h /usr/include/libdrm/via_drm.h /usr/include/libdrm/virtgpu_drm.h /usr/include/libdrm/vmwgfx_drm.h /usr/include/libsync.h /usr/include/xf86drm.h /usr/include/xf86drmMode.h /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/libdrm.a /usr/lib/x86_64-linux-gnu/libdrm_amdgpu.a /usr/lib/x86_64-linux-gnu/libdrm_intel.a /usr/lib/x86_64-linux-gnu/libdrm_nouveau.a /usr/lib/x86_64-linux-gnu/libdrm_radeon.a /usr/lib/x86_64-linux-gnu/pkgconfig /usr/lib/x86_64-linux-gnu/pkgconfig/libdrm.pc /usr/lib/x86_64-linux-gnu/pkgconfig/libdrm_amdgpu.pc /usr/lib/x86_64-linux-gnu/pkgconfig/libdrm_intel.pc /usr/lib/x86_64-linux-gnu/pkgconfig/libdrm_nouveau.pc /usr/lib/x86_64-linux-gnu/pkgconfig/libdrm_radeon.pc /usr/share /usr/share/doc /usr/share/doc/libdrm-dev /usr/share/doc/libdrm-dev/copyright /usr/share/man /usr/share/man/man3 /usr/share/man/man3/drmAvailable.3.gz /usr/share/man/man3/drmHandleEvent.3.gz /usr/share/man/man3/drmModeGetResources.3.gz /usr/share/man/man7 /usr/share/man/man7/drm-kms.7.gz /usr/share/man/man7/drm-memory.7.gz /usr/share/man/man7/drm.7.gz /usr/lib/x86_64-linux-gnu/libdrm.so /usr/lib/x86_64-linux-gnu/libdrm_amdgpu.so /usr/lib/x86_64-linux-gnu/libdrm_intel.so /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so /usr/lib/x86_64-linux-gnu/libdrm_radeon.so /usr/share/doc/libdrm-dev/changelog.Debian.gz ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1998414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1998414] Re: libdrm-dev missing man pages
Debian also is missing the same pages: https://manpages.debian.org/bullseye/libdrm- dev/drmModeGetResources.3.en.html -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1998414 Title: libdrm-dev missing man pages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1998414/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1998414] [NEW] libdrm-dev missing man pages
Public bug reported: When I access the man-page for drmModeGetResources I am referred to other pages in "SEE ALSO" ``` SEE ALSO drm(7), drm-kms(7), drmModeGetFB(3), drmModeAddFB(3), drmMod‐ eAddFB2(3), drmModeRmFB(3),drmModeDirtyFB(3),drmMod‐ eGetCrtc(3), drmModeSetCrtc (3), drmModeGetEncoder (3), drm‐ ModeGetConnector(3) ``` However, almost none of these other man-pages exist: ``` $ man drmModeGetEncoder No manual entry for drmModeGetEncoder ``` libdrm-dev is installed: 2.4.113-2 OS: Ubuntu 22.10 ``` $ dpkg -L libdrm-dev /. /usr /usr/include /usr/include/libdrm /usr/include/libdrm/amdgpu.h /usr/include/libdrm/amdgpu_drm.h /usr/include/libdrm/drm.h /usr/include/libdrm/drm_fourcc.h /usr/include/libdrm/drm_mode.h /usr/include/libdrm/drm_sarea.h /usr/include/libdrm/i915_drm.h /usr/include/libdrm/intel_aub.h /usr/include/libdrm/intel_bufmgr.h /usr/include/libdrm/intel_debug.h /usr/include/libdrm/mach64_drm.h /usr/include/libdrm/mga_drm.h /usr/include/libdrm/msm_drm.h /usr/include/libdrm/nouveau /usr/include/libdrm/nouveau/nouveau.h /usr/include/libdrm/nouveau/nvif /usr/include/libdrm/nouveau/nvif/cl0080.h /usr/include/libdrm/nouveau/nvif/cl9097.h /usr/include/libdrm/nouveau/nvif/class.h /usr/include/libdrm/nouveau/nvif/if0002.h /usr/include/libdrm/nouveau/nvif/if0003.h /usr/include/libdrm/nouveau/nvif/ioctl.h /usr/include/libdrm/nouveau/nvif/unpack.h /usr/include/libdrm/nouveau_drm.h /usr/include/libdrm/qxl_drm.h /usr/include/libdrm/r128_drm.h /usr/include/libdrm/r600_pci_ids.h /usr/include/libdrm/radeon_bo.h /usr/include/libdrm/radeon_bo_gem.h /usr/include/libdrm/radeon_bo_int.h /usr/include/libdrm/radeon_cs.h /usr/include/libdrm/radeon_cs_gem.h /usr/include/libdrm/radeon_cs_int.h /usr/include/libdrm/radeon_drm.h /usr/include/libdrm/radeon_surface.h /usr/include/libdrm/savage_drm.h /usr/include/libdrm/sis_drm.h /usr/include/libdrm/tegra_drm.h /usr/include/libdrm/vc4_drm.h /usr/include/libdrm/via_drm.h /usr/include/libdrm/virtgpu_drm.h /usr/include/libdrm/vmwgfx_drm.h /usr/include/libsync.h /usr/include/xf86drm.h /usr/include/xf86drmMode.h /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/libdrm.a /usr/lib/x86_64-linux-gnu/libdrm_amdgpu.a /usr/lib/x86_64-linux-gnu/libdrm_intel.a /usr/lib/x86_64-linux-gnu/libdrm_nouveau.a /usr/lib/x86_64-linux-gnu/libdrm_radeon.a /usr/lib/x86_64-linux-gnu/pkgconfig /usr/lib/x86_64-linux-gnu/pkgconfig/libdrm.pc /usr/lib/x86_64-linux-gnu/pkgconfig/libdrm_amdgpu.pc /usr/lib/x86_64-linux-gnu/pkgconfig/libdrm_intel.pc /usr/lib/x86_64-linux-gnu/pkgconfig/libdrm_nouveau.pc /usr/lib/x86_64-linux-gnu/pkgconfig/libdrm_radeon.pc /usr/share /usr/share/doc /usr/share/doc/libdrm-dev /usr/share/doc/libdrm-dev/copyright /usr/share/man /usr/share/man/man3 /usr/share/man/man3/drmAvailable.3.gz /usr/share/man/man3/drmHandleEvent.3.gz /usr/share/man/man3/drmModeGetResources.3.gz /usr/share/man/man7 /usr/share/man/man7/drm-kms.7.gz /usr/share/man/man7/drm-memory.7.gz /usr/share/man/man7/drm.7.gz /usr/lib/x86_64-linux-gnu/libdrm.so /usr/lib/x86_64-linux-gnu/libdrm_amdgpu.so /usr/lib/x86_64-linux-gnu/libdrm_intel.so /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so /usr/lib/x86_64-linux-gnu/libdrm_radeon.so /usr/share/doc/libdrm-dev/changelog.Debian.gz ``` ** Affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Tags: manpage -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1998414 Title: libdrm-dev missing man pages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1998414/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1998414] [NEW] libdrm-dev missing man pages
Public bug reported: When I access the man-page for drmModeGetResources I am referred to other pages in "SEE ALSO" ``` SEE ALSO drm(7), drm-kms(7), drmModeGetFB(3), drmModeAddFB(3), drmMod‐ eAddFB2(3), drmModeRmFB(3),drmModeDirtyFB(3),drmMod‐ eGetCrtc(3), drmModeSetCrtc (3), drmModeGetEncoder (3), drm‐ ModeGetConnector(3) ``` However, almost none of these other man-pages exist: ``` $ man drmModeGetEncoder No manual entry for drmModeGetEncoder ``` libdrm-dev is installed: 2.4.113-2 OS: Ubuntu 22.10 ``` $ dpkg -L libdrm-dev /. /usr /usr/include /usr/include/libdrm /usr/include/libdrm/amdgpu.h /usr/include/libdrm/amdgpu_drm.h /usr/include/libdrm/drm.h /usr/include/libdrm/drm_fourcc.h /usr/include/libdrm/drm_mode.h /usr/include/libdrm/drm_sarea.h /usr/include/libdrm/i915_drm.h /usr/include/libdrm/intel_aub.h /usr/include/libdrm/intel_bufmgr.h /usr/include/libdrm/intel_debug.h /usr/include/libdrm/mach64_drm.h /usr/include/libdrm/mga_drm.h /usr/include/libdrm/msm_drm.h /usr/include/libdrm/nouveau /usr/include/libdrm/nouveau/nouveau.h /usr/include/libdrm/nouveau/nvif /usr/include/libdrm/nouveau/nvif/cl0080.h /usr/include/libdrm/nouveau/nvif/cl9097.h /usr/include/libdrm/nouveau/nvif/class.h /usr/include/libdrm/nouveau/nvif/if0002.h /usr/include/libdrm/nouveau/nvif/if0003.h /usr/include/libdrm/nouveau/nvif/ioctl.h /usr/include/libdrm/nouveau/nvif/unpack.h /usr/include/libdrm/nouveau_drm.h /usr/include/libdrm/qxl_drm.h /usr/include/libdrm/r128_drm.h /usr/include/libdrm/r600_pci_ids.h /usr/include/libdrm/radeon_bo.h /usr/include/libdrm/radeon_bo_gem.h /usr/include/libdrm/radeon_bo_int.h /usr/include/libdrm/radeon_cs.h /usr/include/libdrm/radeon_cs_gem.h /usr/include/libdrm/radeon_cs_int.h /usr/include/libdrm/radeon_drm.h /usr/include/libdrm/radeon_surface.h /usr/include/libdrm/savage_drm.h /usr/include/libdrm/sis_drm.h /usr/include/libdrm/tegra_drm.h /usr/include/libdrm/vc4_drm.h /usr/include/libdrm/via_drm.h /usr/include/libdrm/virtgpu_drm.h /usr/include/libdrm/vmwgfx_drm.h /usr/include/libsync.h /usr/include/xf86drm.h /usr/include/xf86drmMode.h /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/libdrm.a /usr/lib/x86_64-linux-gnu/libdrm_amdgpu.a /usr/lib/x86_64-linux-gnu/libdrm_intel.a /usr/lib/x86_64-linux-gnu/libdrm_nouveau.a /usr/lib/x86_64-linux-gnu/libdrm_radeon.a /usr/lib/x86_64-linux-gnu/pkgconfig /usr/lib/x86_64-linux-gnu/pkgconfig/libdrm.pc /usr/lib/x86_64-linux-gnu/pkgconfig/libdrm_amdgpu.pc /usr/lib/x86_64-linux-gnu/pkgconfig/libdrm_intel.pc /usr/lib/x86_64-linux-gnu/pkgconfig/libdrm_nouveau.pc /usr/lib/x86_64-linux-gnu/pkgconfig/libdrm_radeon.pc /usr/share /usr/share/doc /usr/share/doc/libdrm-dev /usr/share/doc/libdrm-dev/copyright /usr/share/man /usr/share/man/man3 /usr/share/man/man3/drmAvailable.3.gz /usr/share/man/man3/drmHandleEvent.3.gz /usr/share/man/man3/drmModeGetResources.3.gz /usr/share/man/man7 /usr/share/man/man7/drm-kms.7.gz /usr/share/man/man7/drm-memory.7.gz /usr/share/man/man7/drm.7.gz /usr/lib/x86_64-linux-gnu/libdrm.so /usr/lib/x86_64-linux-gnu/libdrm_amdgpu.so /usr/lib/x86_64-linux-gnu/libdrm_intel.so /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so /usr/lib/x86_64-linux-gnu/libdrm_radeon.so /usr/share/doc/libdrm-dev/changelog.Debian.gz ``` ** Affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Tags: manpage -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1998414 Title: libdrm-dev missing man pages Status in libdrm package in Ubuntu: New Bug description: When I access the man-page for drmModeGetResources I am referred to other pages in "SEE ALSO" ``` SEE ALSO drm(7), drm-kms(7), drmModeGetFB(3), drmModeAddFB(3), drmMod‐ eAddFB2(3), drmModeRmFB(3),drmModeDirtyFB(3),drmMod‐ eGetCrtc(3), drmModeSetCrtc (3), drmModeGetEncoder (3), drm‐ ModeGetConnector(3) ``` However, almost none of these other man-pages exist: ``` $ man drmModeGetEncoder No manual entry for drmModeGetEncoder ``` libdrm-dev is installed: 2.4.113-2 OS: Ubuntu 22.10 ``` $ dpkg -L libdrm-dev /. /usr /usr/include /usr/include/libdrm /usr/include/libdrm/amdgpu.h /usr/include/libdrm/amdgpu_drm.h /usr/include/libdrm/drm.h /usr/include/libdrm/drm_fourcc.h /usr/include/libdrm/drm_mode.h /usr/include/libdrm/drm_sarea.h /usr/include/libdrm/i915_drm.h /usr/include/libdrm/intel_aub.h /usr/include/libdrm/intel_bufmgr.h /usr/include/libdrm/intel_debug.h /usr/include/libdrm/mach64_drm.h /usr/include/libdrm/mga_drm.h /usr/include/libdrm/msm_drm.h /usr/include/libdrm/nouveau /usr/include/libdrm/nouveau/nouveau.h /usr/include/libdrm/nouveau/nvif /usr/include/libdrm/nouveau/nvif/cl0080.h /usr/include/libdrm/nouveau/nvif/cl9097.h /usr/include/libdrm/nouveau/nvif/class.h
[Ubuntu-x-swat] [Bug 1998001] [NEW] Missing tests from libdrm-tests
Public bug reported: It is advertised by the OS that kms-universal-planes can be installed via libdrm-tests but this is false: $ kms-universal-planes Command 'kms-universal-planes' not found, but can be installed with: sudo apt install libdrm-tests $ sudo apt install libdrm-tests [sudo] password for stolk: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: libdrm-tests 0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded. Need to get 47.5 kB of archives. After this operation, 193 kB of additional disk space will be used. Get:1 http://ca.archive.ubuntu.com/ubuntu kinetic/universe amd64 libdrm-tests amd64 2.4.113-2 [47.5 kB] Fetched 47.5 kB in 0s (142 kB/s) Selecting previously unselected package libdrm-tests. (Reading database ... 308766 files and directories currently installed.) Preparing to unpack .../libdrm-tests_2.4.113-2_amd64.deb ... Unpacking libdrm-tests (2.4.113-2) ... Setting up libdrm-tests (2.4.113-2) ... $ kms-universal-planes Command 'kms-universal-planes' not found, but can be installed with: sudo apt install libdrm-tests OS: Ubuntu 22.10 ** Affects: libdrm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1998001 Title: Missing tests from libdrm-tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1998001/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1998001] [NEW] Missing tests from libdrm-tests
Public bug reported: It is advertised by the OS that kms-universal-planes can be installed via libdrm-tests but this is false: $ kms-universal-planes Command 'kms-universal-planes' not found, but can be installed with: sudo apt install libdrm-tests $ sudo apt install libdrm-tests [sudo] password for stolk: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: libdrm-tests 0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded. Need to get 47.5 kB of archives. After this operation, 193 kB of additional disk space will be used. Get:1 http://ca.archive.ubuntu.com/ubuntu kinetic/universe amd64 libdrm-tests amd64 2.4.113-2 [47.5 kB] Fetched 47.5 kB in 0s (142 kB/s) Selecting previously unselected package libdrm-tests. (Reading database ... 308766 files and directories currently installed.) Preparing to unpack .../libdrm-tests_2.4.113-2_amd64.deb ... Unpacking libdrm-tests (2.4.113-2) ... Setting up libdrm-tests (2.4.113-2) ... $ kms-universal-planes Command 'kms-universal-planes' not found, but can be installed with: sudo apt install libdrm-tests OS: Ubuntu 22.10 ** Affects: libdrm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1998001 Title: Missing tests from libdrm-tests Status in libdrm package in Ubuntu: New Bug description: It is advertised by the OS that kms-universal-planes can be installed via libdrm-tests but this is false: $ kms-universal-planes Command 'kms-universal-planes' not found, but can be installed with: sudo apt install libdrm-tests $ sudo apt install libdrm-tests [sudo] password for stolk: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: libdrm-tests 0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded. Need to get 47.5 kB of archives. After this operation, 193 kB of additional disk space will be used. Get:1 http://ca.archive.ubuntu.com/ubuntu kinetic/universe amd64 libdrm-tests amd64 2.4.113-2 [47.5 kB] Fetched 47.5 kB in 0s (142 kB/s) Selecting previously unselected package libdrm-tests. (Reading database ... 308766 files and directories currently installed.) Preparing to unpack .../libdrm-tests_2.4.113-2_amd64.deb ... Unpacking libdrm-tests (2.4.113-2) ... Setting up libdrm-tests (2.4.113-2) ... $ kms-universal-planes Command 'kms-universal-planes' not found, but can be installed with: sudo apt install libdrm-tests OS: Ubuntu 22.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1998001/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1996217] acpidump.txt
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630407/+files/acpidump.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
[Desktop-packages] [Bug 1996217] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630403/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult:
[Desktop-packages] [Bug 1996217] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630406/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
[Desktop-packages] [Bug 1996217] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630405/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
[Desktop-packages] [Bug 1996217] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630404/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
[Kernel-packages] [Bug 1996217] acpidump.txt
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630407/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop:
[Kernel-packages] [Bug 1996217] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630400/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
[Kernel-packages] [Bug 1996217] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630402/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
[Kernel-packages] [Bug 1996217] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630399/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop:
[Kernel-packages] [Bug 1996217] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630397/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop:
[Kernel-packages] [Bug 1996217] Lsusb-t.txt
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630398/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop:
[Kernel-packages] [Bug 1996217] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630406/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop:
[Kernel-packages] [Bug 1996217] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630403/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
[Kernel-packages] [Bug 1996217] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630404/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
[Kernel-packages] [Bug 1996217] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630405/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop:
[Kernel-packages] [Bug 1996217] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630401/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
[Desktop-packages] [Bug 1996217] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630402/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
[Desktop-packages] [Bug 1996217] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630400/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
[Desktop-packages] [Bug 1996217] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630401/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
[Desktop-packages] [Bug 1996217] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630395/+files/Lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
[Desktop-packages] [Bug 1996217] Lspci-vt.txt
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630396/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
[Desktop-packages] [Bug 1996217] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630399/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
[Desktop-packages] [Bug 1996217] Lsusb-t.txt
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630398/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
[Desktop-packages] [Bug 1996217] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630397/+files/Lsusb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
[Kernel-packages] [Bug 1996217] Lspci-vt.txt
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630396/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop:
[Kernel-packages] [Bug 1996217] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630395/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop:
[Kernel-packages] [Bug 1996217] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630393/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
[Kernel-packages] [Bug 1996217] IwConfig.txt
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630394/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop:
[Desktop-packages] [Bug 1996217] IwConfig.txt
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630394/+files/IwConfig.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
[Desktop-packages] [Bug 1996217] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630393/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
[Kernel-packages] [Bug 1996217] Re: SIGTRAP on launch 109.0.5396.2-2184
apport information
** Description changed:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
-
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
-
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
+
+ SNAPPY DEBUG
+
+
+ $ snappy-debug
+ INFO: Following '/var/log/syslog'. If have dropped messages, use:
+ INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
+ = Seccomp =
+ Time: Nov 10 09:48:03
+ Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
+ Syscall: pkey_mprotect
+
+
+
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
** Tags added: apport-collected kinetic wayland-session
** Description changed:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
[Desktop-packages] [Bug 1996217] Re: SIGTRAP on launch 109.0.5396.2-2184
apport information
** Description changed:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
-
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
-
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
+
+ SNAPPY DEBUG
+
+
+ $ snappy-debug
+ INFO: Following '/var/log/syslog'. If have dropped messages, use:
+ INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
+ = Seccomp =
+ Time: Nov 10 09:48:03
+ Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
+ Syscall: pkey_mprotect
+
+
+
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
** Tags added: apport-collected kinetic wayland-session
** Description changed:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
[Desktop-packages] [Bug 1996217] [NEW] SIGTRAP on launch 109.0.5396.2-2184
Public bug reported:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818 launched
by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED" operation="capable"
class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED" operation="capable"
class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000 ses=2
subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
Re: [Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
Ah... that explains a lot!
Please send me the revised build guide! Mine is v0.5 from june!
Thanks!
On Thu, Oct 20, 2022 at 3:00 PM Qinling Wang <1990...@bugs.launchpad.net>
wrote:
> Which build guide do you have? Is that Revision 0.7? There are 7 patches
> rather than 3.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1990010
>
> Title:
> VA error: resource allocation failed
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+subscriptions
>
>
--
Owner/Director of Game Studio Abraham Stolk Inc.
Vancouver BC, Canada
b.st...@gmail.com
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1990010
Title:
VA error: resource allocation failed
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
https://github.com/intel/media-driver/issues/1498
---
When I play a H264/AAC video with HW decoding enabled on Alderlake
12600k, using Wayland I get the error:
vaCreateSurfaces (import mode) failed, VA error: resource allocation
failed
After which, chromium will proceed to play the video without HW
acceleration using ffmpeg.
This is both with using the pre-built snap from channel beta/hwacc and
a snap built from source.
(NOTE: HW decoding does work with same browser on X11 desktop, using
VDAVideoDecoder.)
To get more information on this VA error, I built the snap with debug
versions of gmmlib and media-driver (latest git) using the latest git
from valib as well.
The log output from chromium now mentions why the allocation fails:
[390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
[389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)]
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
[390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
[390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
[390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
[390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder
Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
modifier."
I am on wayland, and use these chromium flags:
export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist
--disable-gpu-driver-bug-workaround --ozone-platform=wayland"
The video that fails: the 1080p/60 version downloaded from here:
https://github.com/chthomos/video-media-samples/
I will figure out which is the "unsupported modifier" and report back,
here.
Note: currently gmmlib and media-driver have failing debug builds, but I have
created pull requests to both:
https://github.com/intel/media-driver/pull/1491
https://github.com/intel/gmmlib/pull/97
CPU: 12600k
GPU: Intel Alderlake_s (Gen12)
Snap built with: core20
Host OS: Ubuntu Kinetic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
Yes, your r105 debian package works on my machine, with HW-decode under
Wayland.
Are there any patches applied, other than the 3 mentioned in the
building guide?
** Attachment added: "Screenshot from 2022-10-20 11-11-45.png"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+attachment/5625584/+files/Screenshot%20from%202022-10-20%2011-11-45.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1990010
Title:
VA error: resource allocation failed
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
https://github.com/intel/media-driver/issues/1498
---
When I play a H264/AAC video with HW decoding enabled on Alderlake
12600k, using Wayland I get the error:
vaCreateSurfaces (import mode) failed, VA error: resource allocation
failed
After which, chromium will proceed to play the video without HW
acceleration using ffmpeg.
This is both with using the pre-built snap from channel beta/hwacc and
a snap built from source.
(NOTE: HW decoding does work with same browser on X11 desktop, using
VDAVideoDecoder.)
To get more information on this VA error, I built the snap with debug
versions of gmmlib and media-driver (latest git) using the latest git
from valib as well.
The log output from chromium now mentions why the allocation fails:
[390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
[389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)]
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
[390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
[390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
[390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
[390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder
Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
modifier."
I am on wayland, and use these chromium flags:
export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist
--disable-gpu-driver-bug-workaround --ozone-platform=wayland"
The video that fails: the 1080p/60 version downloaded from here:
https://github.com/chthomos/video-media-samples/
I will figure out which is the "unsupported modifier" and report back,
here.
Note: currently gmmlib and media-driver have failing debug builds, but I have
created pull requests to both:
https://github.com/intel/media-driver/pull/1491
https://github.com/intel/gmmlib/pull/97
CPU: 12600k
GPU: Intel Alderlake_s (Gen12)
Snap built with: core20
Host OS: Ubuntu Kinetic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
I tried building a snap with 104.0.5112.101 version of chromium, and
that gives me working HW-decode on Wayland.
A later change in chromium must have broken vaapi playback.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1990010
Title:
VA error: resource allocation failed
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
https://github.com/intel/media-driver/issues/1498
---
When I play a H264/AAC video with HW decoding enabled on Alderlake
12600k, using Wayland I get the error:
vaCreateSurfaces (import mode) failed, VA error: resource allocation
failed
After which, chromium will proceed to play the video without HW
acceleration using ffmpeg.
This is both with using the pre-built snap from channel beta/hwacc and
a snap built from source.
(NOTE: HW decoding does work with same browser on X11 desktop, using
VDAVideoDecoder.)
To get more information on this VA error, I built the snap with debug
versions of gmmlib and media-driver (latest git) using the latest git
from valib as well.
The log output from chromium now mentions why the allocation fails:
[390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
[389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)]
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
[390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
[390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
[390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
[390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder
Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
modifier."
I am on wayland, and use these chromium flags:
export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist
--disable-gpu-driver-bug-workaround --ozone-platform=wayland"
The video that fails: the 1080p/60 version downloaded from here:
https://github.com/chthomos/video-media-samples/
I will figure out which is the "unsupported modifier" and report back,
here.
Note: currently gmmlib and media-driver have failing debug builds, but I have
created pull requests to both:
https://github.com/intel/media-driver/pull/1491
https://github.com/intel/gmmlib/pull/97
CPU: 12600k
GPU: Intel Alderlake_s (Gen12)
Snap built with: core20
Host OS: Ubuntu Kinetic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
The deb does indeed vaapi hw decode for me on Alderlake.
$ LIBVA_TRACE=$HOME/va.log /usr/bin/chromium-browser-unstable --enable-
logging=stderr ~/Downloads/*mp4
** Attachment added: "va trace"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+attachment/5620150/+files/va.log.222000.thd-0x00032256
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1990010
Title:
VA error: resource allocation failed
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
https://github.com/intel/media-driver/issues/1498
---
When I play a H264/AAC video with HW decoding enabled on Alderlake
12600k, using Wayland I get the error:
vaCreateSurfaces (import mode) failed, VA error: resource allocation
failed
After which, chromium will proceed to play the video without HW
acceleration using ffmpeg.
This is both with using the pre-built snap from channel beta/hwacc and
a snap built from source.
(NOTE: HW decoding does work with same browser on X11 desktop, using
VDAVideoDecoder.)
To get more information on this VA error, I built the snap with debug
versions of gmmlib and media-driver (latest git) using the latest git
from valib as well.
The log output from chromium now mentions why the allocation fails:
[390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
[389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)]
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
[390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
[390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
[390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
[390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder
Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
modifier."
I am on wayland, and use these chromium flags:
export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist
--disable-gpu-driver-bug-workaround --ozone-platform=wayland"
The video that fails: the 1080p/60 version downloaded from here:
https://github.com/chthomos/video-media-samples/
I will figure out which is the "unsupported modifier" and report back,
here.
Note: currently gmmlib and media-driver have failing debug builds, but I have
created pull requests to both:
https://github.com/intel/media-driver/pull/1491
https://github.com/intel/gmmlib/pull/97
CPU: 12600k
GPU: Intel Alderlake_s (Gen12)
Snap built with: core20
Host OS: Ubuntu Kinetic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
@helainewang I can confirm that your .deb file indeed plays with HW
decoding on my Alderlake machine, but not via VAAPI.
If I pass:
```
--enable-logging=stderr
--enable-features=VaapiVideoDecoder,VaapiVideoEncoder
--disable-features=UseChromeOSDirectVideoDecoder
```
Then the decoding is in sofware, with the following error from chromium:
```
[188746:188746:0929/141918.619668:ERROR:vaapi_wrapper.cc(2128)] vaCreateContext
failed, VA error: unknown libva error
[188746:188746:0929/141918.619871:ERROR:vaapi_video_decode_accelerator.cc(726)]
Failed to create Context
```
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1990010
Title:
VA error: resource allocation failed
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
https://github.com/intel/media-driver/issues/1498
---
When I play a H264/AAC video with HW decoding enabled on Alderlake
12600k, using Wayland I get the error:
vaCreateSurfaces (import mode) failed, VA error: resource allocation
failed
After which, chromium will proceed to play the video without HW
acceleration using ffmpeg.
This is both with using the pre-built snap from channel beta/hwacc and
a snap built from source.
(NOTE: HW decoding does work with same browser on X11 desktop, using
VDAVideoDecoder.)
To get more information on this VA error, I built the snap with debug
versions of gmmlib and media-driver (latest git) using the latest git
from valib as well.
The log output from chromium now mentions why the allocation fails:
[390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
[389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)]
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
[390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
[390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
[390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
[390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder
Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
modifier."
I am on wayland, and use these chromium flags:
export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist
--disable-gpu-driver-bug-workaround --ozone-platform=wayland"
The video that fails: the 1080p/60 version downloaded from here:
https://github.com/chthomos/video-media-samples/
I will figure out which is the "unsupported modifier" and report back,
here.
Note: currently gmmlib and media-driver have failing debug builds, but I have
created pull requests to both:
https://github.com/intel/media-driver/pull/1491
https://github.com/intel/gmmlib/pull/97
CPU: 12600k
GPU: Intel Alderlake_s (Gen12)
Snap built with: core20
Host OS: Ubuntu Kinetic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
I get this both on dev, and edge-hwacc, and snaps I build myself.
It consistently gives me a VA error on wayland, but works on X11.
On Wed, Sep 28, 2022 at 2:30 PM Nathan Teodosio <1990...@bugs.launchpad.net>
wrote:
> > Which build guide did you follow to build your chromium browser? Could
> > you please provide us the version of your chromium browser and vainfo
> > output information? Thank you!
>
> Qinling, the snap against which we have been testing is built from [1].
> (Please correct me, Bram, if you tested a different build.)
>
> [1]: https://git.launchpad.net/~nteodosio/chromium-browser/tree/?h=dev
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1990010
>
> Title:
> VA error: resource allocation failed
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+subscriptions
>
>
--
Owner/Director of Game Studio Abraham Stolk Inc.
Vancouver BC, Canada
b.st...@gmail.com
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1990010
Title:
VA error: resource allocation failed
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
https://github.com/intel/media-driver/issues/1498
---
When I play a H264/AAC video with HW decoding enabled on Alderlake
12600k, using Wayland I get the error:
vaCreateSurfaces (import mode) failed, VA error: resource allocation
failed
After which, chromium will proceed to play the video without HW
acceleration using ffmpeg.
This is both with using the pre-built snap from channel beta/hwacc and
a snap built from source.
(NOTE: HW decoding does work with same browser on X11 desktop, using
VDAVideoDecoder.)
To get more information on this VA error, I built the snap with debug
versions of gmmlib and media-driver (latest git) using the latest git
from valib as well.
The log output from chromium now mentions why the allocation fails:
[390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
[389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)]
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
[390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
[390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
[390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
[390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder
Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
modifier."
I am on wayland, and use these chromium flags:
export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist
--disable-gpu-driver-bug-workaround --ozone-platform=wayland"
The video that fails: the 1080p/60 version downloaded from here:
https://github.com/chthomos/video-media-samples/
I will figure out which is the "unsupported modifier" and report back,
here.
Note: currently gmmlib and media-driver have failing debug builds, but I have
created pull requests to both:
https://github.com/intel/media-driver/pull/1491
https://github.com/intel/gmmlib/pull/97
CPU: 12600k
GPU: Intel Alderlake_s (Gen12)
Snap built with: core20
Host OS: Ubuntu Kinetic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
The chromium version and vainfo output are in the upstream issue:
https://github.com/intel/media-driver/issues/1498
The chromium build is via our snap, that integrates your patches.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1990010
Title:
VA error: resource allocation failed
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
https://github.com/intel/media-driver/issues/1498
---
When I play a H264/AAC video with HW decoding enabled on Alderlake
12600k, using Wayland I get the error:
vaCreateSurfaces (import mode) failed, VA error: resource allocation
failed
After which, chromium will proceed to play the video without HW
acceleration using ffmpeg.
This is both with using the pre-built snap from channel beta/hwacc and
a snap built from source.
(NOTE: HW decoding does work with same browser on X11 desktop, using
VDAVideoDecoder.)
To get more information on this VA error, I built the snap with debug
versions of gmmlib and media-driver (latest git) using the latest git
from valib as well.
The log output from chromium now mentions why the allocation fails:
[390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
[389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)]
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
[390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
[390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
[390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
[390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder
Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
modifier."
I am on wayland, and use these chromium flags:
export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist
--disable-gpu-driver-bug-workaround --ozone-platform=wayland"
The video that fails: the 1080p/60 version downloaded from here:
https://github.com/chthomos/video-media-samples/
I will figure out which is the "unsupported modifier" and report back,
here.
Note: currently gmmlib and media-driver have failing debug builds, but I have
created pull requests to both:
https://github.com/intel/media-driver/pull/1491
https://github.com/intel/gmmlib/pull/97
CPU: 12600k
GPU: Intel Alderlake_s (Gen12)
Snap built with: core20
Host OS: Ubuntu Kinetic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990677] Re: Update fonts-noto-color-emoji for Unicode 15
** Tags added: jammy ** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1990677 Title: Update fonts-noto-color-emoji for Unicode 15 Status in fonts-noto-color-emoji package in Ubuntu: Fix Released Status in fonts-noto-color-emoji source package in Jammy: Triaged Bug description: [Impact] Ubuntu has included Google's color emoji font by default for years. Annually, the Unicode Consortium releases a new Unicode standard with new emoji. Internet communication platforms quickly adopt the new emoji and it's important that those emoji also work on the latest Ubuntu release. Emojipedia provides a list of the emoji provided by this font. Click the Show new link to see the new emoji. Click the changed link to see other changes that were made in this release. https://emojipedia.org/google/15.0/ [Test Plan] The test plan is outlined on this wiki: https://wiki.ubuntu.com/DesktopTeam/TestPlans/EmojiFont [Where problems could occur] Sometimes there is an issue with the display of a particular font after the font has been updated. See Debian #788791 for instance. Perhaps this is a bug with font caching. To avoid this bug, it's recommended to restart your computer after applying the update. We are adding a postinst to tell Ubuntu's update-notifier to prompt the user to restart. This could technically be a User Interface Freeze change, but the new and changed emoji don't show in the Ubuntu docs or official screenshots. So there doesn't seem to be a need to notify the Docs team. There are no translations here so no need to notify the Translations team. [Other] This bug is fixed in the current development release. Fix is released: https://bugs.launchpad.net/ubuntu/+source/fonts-noto- color-emoji/+bug/1989626 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1990677/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990677] Re: Update fonts-noto-color-emoji for Unicode 15
** Description changed: - Ubuntu LTS should be capable of display all current color emojis. + [Impact] - For instance, these new emojis in unicode 15.0 + Ubuntu has included Google's color emoji font by default for years. + Annually, the Unicode Consortium releases a new Unicode standard with + new emoji. Internet communication platforms quickly adopt the new emoji + and it's important that those emoji also work on the latest Ubuntu + release. + Emojipedia provides a list of the emoji provided by this font. + + Click the Show new link to see the new emoji. Click the changed link to + see other changes that were made in this release. https://emojipedia.org/google/15.0/ + + [Test Plan] + + The test plan is outlined on this wiki: + https://wiki.ubuntu.com/DesktopTeam/TestPlans/EmojiFont + + [Where problems could occur] + + Sometimes there is an issue with the display of a particular font after + the font has been updated. See Debian #788791 for instance. Perhaps this + is a bug with font caching. To avoid this bug, it's recommended to + restart your computer after applying the update. + + We are adding a postinst to tell Ubuntu's update-notifier to prompt the + user to restart. + + This could technically be a User Interface Freeze change, but the new + and changed emoji don't show in the Ubuntu docs or official screenshots. + So there doesn't seem to be a need to notify the Docs team. There are no + translations here so no need to notify the Translations team. + + [Other] + + This bug is fixed in the current development release. + + Fix is released: https://bugs.launchpad.net/ubuntu/+source/fonts-noto- + color-emoji/+bug/1989626 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1990677 Title: Update fonts-noto-color-emoji for Unicode 15 Status in fonts-noto-color-emoji package in Ubuntu: Fix Released Status in fonts-noto-color-emoji source package in Jammy: Triaged Bug description: [Impact] Ubuntu has included Google's color emoji font by default for years. Annually, the Unicode Consortium releases a new Unicode standard with new emoji. Internet communication platforms quickly adopt the new emoji and it's important that those emoji also work on the latest Ubuntu release. Emojipedia provides a list of the emoji provided by this font. Click the Show new link to see the new emoji. Click the changed link to see other changes that were made in this release. https://emojipedia.org/google/15.0/ [Test Plan] The test plan is outlined on this wiki: https://wiki.ubuntu.com/DesktopTeam/TestPlans/EmojiFont [Where problems could occur] Sometimes there is an issue with the display of a particular font after the font has been updated. See Debian #788791 for instance. Perhaps this is a bug with font caching. To avoid this bug, it's recommended to restart your computer after applying the update. We are adding a postinst to tell Ubuntu's update-notifier to prompt the user to restart. This could technically be a User Interface Freeze change, but the new and changed emoji don't show in the Ubuntu docs or official screenshots. So there doesn't seem to be a need to notify the Docs team. There are no translations here so no need to notify the Translations team. [Other] This bug is fixed in the current development release. Fix is released: https://bugs.launchpad.net/ubuntu/+source/fonts-noto- color-emoji/+bug/1989626 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1990677/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990677] [NEW] Update fonts-noto-color-emoji for Unicode 15
Public bug reported: Ubuntu LTS should be capable of display all current color emojis. For instance, these new emojis in unicode 15.0 https://emojipedia.org/google/15.0/ ** Affects: fonts-noto-color-emoji (Ubuntu) Importance: Medium Status: Fix Released ** Affects: fonts-noto-color-emoji (Ubuntu Jammy) Importance: Medium Status: Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1990677 Title: Update fonts-noto-color-emoji for Unicode 15 Status in fonts-noto-color-emoji package in Ubuntu: Fix Released Status in fonts-noto-color-emoji source package in Jammy: Triaged Bug description: Ubuntu LTS should be capable of display all current color emojis. For instance, these new emojis in unicode 15.0 https://emojipedia.org/google/15.0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1990677/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
