You are not logged in.

#1 2024-03-27 17:40:53

MattWylde
Member
Registered: 2014-11-28
Posts: 9

[SOLVED] Segfault with ozone platform (Wayland) since Gnome 46

Chromium or any electron app segfaults under Wayland since Gnome 46. I must not be the only one with this setup? I can't find any info about the problem:

chromium --enable-logging=stderr --enable-features=UseOzonePlatform --ozone-platform=wayland
[6191:6191:0327/133934.295829:WARNING:chrome_main_delegate.cc(740)] This is Chrome version 123.0.6312.86 (not a warning)
[6191:6191:0327/133934.343198:INFO:policy_logger.cc(145)] :components/policy/core/common/config_dir_policy_loader.cc(118) Skipping mandatory platform policies because no policy file was found at: /etc/chromium/policies/managed
[6191:6191:0327/133934.343229:INFO:policy_logger.cc(145)] :components/policy/core/common/config_dir_policy_loader.cc(118) Skipping recommended platform policies because no policy file was found at: /etc/chromium/policies/recommended
[6191:6191:0327/133934.368330:WARNING:wayland_object.cc(164)] Binding to gtk_shell1 version 4 but version 5 is available.
[6191:6191:0327/133934.368356:WARNING:wayland_object.cc(164)] Binding to zwp_pointer_gestures_v1 version 1 but version 3 is available.
[6191:6191:0327/133934.368384:WARNING:wayland_object.cc(164)] Binding to zwp_linux_dmabuf_v1 version 3 but version 5 is available.
[6230:6230:0327/133934.541534:WARNING:sandbox_linux.cc(418)] InitializeSandbox() called with multiple threads in process gpu-process.
[6191:6191:0327/133936.141102:WARNING:key_storage_libsecret.cc(55)] the encryption key has been modified since it was created.
[6191:6191:0327/133936.141529:ERROR:policy_logger.cc(157)] :components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(161) Cloud management controller initialization aborted as CBCM is not enabled. Please use the `--enable-chrome-browser-cloud-management` command line flag to enable it if you are not using the official Google Chrome build.
[6191:6191:0327/133936.157573:WARNING:wayland_surface.cc(183)] Server doesn't support zcr_alpha_compositing_v1.
[6191:6191:0327/133936.157585:WARNING:wayland_surface.cc(198)] Server doesn't support overlay_prioritizer.
[6191:6191:0327/133936.157588:WARNING:wayland_surface.cc(212)] Server doesn't support surface_augmenter.
[6191:6191:0327/133936.157591:WARNING:wayland_surface.cc(227)] Server doesn't support wp_content_type_v1
[6191:6191:0327/133936.157593:WARNING:wayland_surface.cc(246)] Server doesn't support zcr_color_management_surface.
[6191:6191:0327/133936.160541:WARNING:account_consistency_mode_manager.cc(77)] Desktop Identity Consistency cannot be enabled as no OAuth client ID and client secret have been configured.
[6279:1:0327/133936.164860:WARNING:runtime_features.cc(728)] AttributionReportingCrossAppWeb cannot be enabled in this configuration. Use --enable-features=ConversionMeasurement,AttributionReportingCrossAppWeb in addition.
[6280:1:0327/133936.166005:WARNING:runtime_features.cc(728)] AttributionReportingCrossAppWeb cannot be enabled in this configuration. Use --enable-features=ConversionMeasurement,AttributionReportingCrossAppWeb in addition.
[6191:6191:0327/133936.177819:WARNING:bluez_dbus_manager.cc(248)] Floss manager not present, cannot set Floss enable/disable.
[6191:6227:0327/133936.292405:WARNING:backend_impl.cc(1759)] Destroying invalid entry.
[6191:6191:0327/133936.427463:ERROR:wayland_event_watcher.cc(43)] libwayland: wl_surface@32: error 2: Buffer size (64x64) must be an integer multiple of the buffer_scale (3).

[0327/133936.433394:ERROR:elf_dynamic_array_reader.h(64)] tag not found
Trace/breakpoint trap (core dumped)

Last edited by MattWylde (2024-03-28 13:30:27)

Offline

#2 2024-03-27 20:20:10

MattWylde
Member
Registered: 2014-11-28
Posts: 9

Re: [SOLVED] Segfault with ozone platform (Wayland) since Gnome 46

Strack trace:

Core was generated by `/usr/lib/chromium/chromium --enable-logging=stderr --enable-features=UseOzonePl'.
Program terminated with signal SIGTRAP, Trace/breakpoint trap.
#0  0x00006359af9ce19b in ui::WaylandEventWatcher::WlDisplayCheckForErrors() ()
[Current thread is 1 (Thread 0x7e82319454c0 (LWP 6191))]
(gdb) bt
#0  0x00006359af9ce19b in ui::WaylandEventWatcher::WlDisplayCheckForErrors() ()
#1  0x00006359af9ce84e in ui::(anonymous namespace)::WatchSourceDispatch(_GSource*, int (*)(void*), void*) [clone .a82fcc63155f75de0613745cb5c3e93e] [clone .cfi] ()
#2  0x00007e82369ae199 in g_main_dispatch (context=0xf6400274540) at ../glib/glib/gmain.c:3344
#3  0x00007e8236a0d3bf in g_main_context_dispatch_unlocked (context=0xf6400274540) at ../glib/glib/gmain.c:4152
#4  g_main_context_iterate_unlocked.isra.0 (context=context@entry=0xf6400274540, block=block@entry=0, dispatch=dispatch@entry=1, self=<optimized out>)
    at ../glib/glib/gmain.c:4217
#5  0x00007e82369ad712 in g_main_context_iteration (context=0xf6400274540, may_block=0) at ../glib/glib/gmain.c:4282
#6  0x00006359b4673d7f in base::MessagePumpGlib::Run(base::MessagePump::Delegate*) ()
#7  0x00006359b45f84df in base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run(bool, base::TimeDelta) ()
#8  0x00006359b45b3996 in base::RunLoop::Run(base::Location const&) ()
#9  0x00006359b19afc3e in content::BrowserMainLoop::RunMainMessageLoop() ()
#10 0x00006359b19b1bd3 in content::BrowserMainRunnerImpl::Run() ()
#11 0x00006359b19abe5e in content::BrowserMain(content::MainFunctionParams) ()
#12 0x00006359b369df5c in content::ContentMainRunnerImpl::Run() ()
#13 0x00006359b369ae4c in content::ContentMain(content::ContentMainParams) ()
#14 0x00006359aef00dca in ChromeMain ()
#15 0x00007e8234980cd0 in __libc_start_call_main (main=main@entry=0x6359aef009f0 <main>, argc=argc@entry=4, argv=0x7ffcd79fbb08, argv@entry=0x7ffcd79fb960)
    at ../sysdeps/nptl/libc_start_call_main.h:58
#16 0x00007e8234980d8a in __libc_start_main_impl
    (main=0x6359aef009f0 <main>, argc=4, argv=0x7ffcd79fb960, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffcd79fbaf8)
    at ../csu/libc-start.c:360
#17 0x00006359aeaaa025 in _start ()

Last edited by MattWylde (2024-03-28 13:16:49)

Offline

#3 2024-03-27 22:38:39

seth
Member
Registered: 2012-09-03
Posts: 51,608

Re: [SOLVED] Segfault with ozone platform (Wayland) since Gnome 46

[6191:6191:0327/133936.427463:ERROR:wayland_event_watcher.cc(43)] libwayland: wl_surface@32: error 2: Buffer size (64x64) must be an integer multiple of the buffer_scale (3).

https://gitlab.gnome.org/GNOME/mutter/-/issues/2428
https://gitlab.gnome.org/GNOME/mutter/-/issues/2603
https://github.com/kovidgoyal/kitty/issues/4878

For 64x64 my money is on the cursor (theme) regardless, do you use adwaita?
Better results w/ Vanilla-DMZ-AA? (They're virtually the same)

Are you deliberately running gnome on 300% scaling?

Offline

#4 2024-03-27 23:22:42

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,896
Website

Re: [SOLVED] Segfault with ozone platform (Wayland) since Gnome 46

Please edit your posts to make use of code tags.

https://wiki.archlinux.org/title/Genera … s_and_code


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#5 2024-03-28 13:17:37

MattWylde
Member
Registered: 2014-11-28
Posts: 9

Re: [SOLVED] Segfault with ozone platform (Wayland) since Gnome 46

seth wrote:

[6191:6191:0327/133936.427463:ERROR:wayland_event_watcher.cc(43)] libwayland: wl_surface@32: error 2: Buffer size (64x64) must be an integer multiple of the buffer_scale (3).

https://gitlab.gnome.org/GNOME/mutter/-/issues/2428
https://gitlab.gnome.org/GNOME/mutter/-/issues/2603
https://github.com/kovidgoyal/kitty/issues/4878

For 64x64 my money is on the cursor (theme) regardless, do you use adwaita?
Better results w/ Vanilla-DMZ-AA? (They're virtually the same)

Are you deliberately running gnome on 300% scaling?

250%, but the segfault also happens at 100%. Not relevant to the crash it seems.

Last edited by MattWylde (2024-03-28 13:18:29)

Offline

#6 2024-03-28 13:23:55

MattWylde
Member
Registered: 2014-11-28
Posts: 9

Re: [SOLVED] Segfault with ozone platform (Wayland) since Gnome 46

Update: it seems to work this morning with integer fractional scale (100, 200, 300). 250% was always working until now however.

Offline

#7 2024-03-28 13:26:32

seth
Member
Registered: 2012-09-03
Posts: 51,608

Re: [SOLVED] Segfault with ozone platform (Wayland) since Gnome 46

Do you still get the buffer size/scale mismatch warning w/ those values?

Offline

#8 2024-03-28 13:29:15

MattWylde
Member
Registered: 2014-11-28
Posts: 9

Re: [SOLVED] Segfault with ozone platform (Wayland) since Gnome 46

seth wrote:

[6191:6191:0327/133936.427463:ERROR:wayland_event_watcher.cc(43)] libwayland: wl_surface@32: error 2: Buffer size (64x64) must be an integer multiple of the buffer_scale (3).

https://gitlab.gnome.org/GNOME/mutter/-/issues/2428
https://gitlab.gnome.org/GNOME/mutter/-/issues/2603
https://github.com/kovidgoyal/kitty/issues/4878

For 64x64 my money is on the cursor (theme) regardless, do you use adwaita?
Better results w/ Vanilla-DMZ-AA? (They're virtually the same)

Are you deliberately running gnome on 300% scaling?

Thank you so much. Vanilla-DMZ-AA fixed it!

Offline

#9 2024-03-28 13:36:17

seth
Member
Registered: 2012-09-03
Posts: 51,608

Re: [SOLVED] Segfault with ozone platform (Wayland) since Gnome 46

Offline

Board footer

Powered by FluxBB