I can independently confirm this issue on a separate Ubuntu 22.04.5 system (KDE Plasma 5.24.7, X11). I hit the same crash and isolated appmenu-gtk-module via A/B testing before finding this report; adding my data points here since they extend the affected scope:
- google-chrome-stable 152.0.7977.75 -> SIGSEGV at startup - google-chrome-stable 153.0.8010.36 and 153.0.8010.52 -> SIGSEGV at startup - google-chrome-canary 156.0.8066.0 -> SIGSEGV at startup (regression still present in current Canary) - Chromium .deb 152.0.7977.82 (Linux Mint build for the Ubuntu 22.04 base) -> SIGSEGV at startup - google-chrome-stable 151.0.7922.75 -> works fine with the exact same configuration - Chromium 153.0.8010.36 (Snap) -> works fine with the exact same configuration - Firefox 156.0 (.deb) and 155.0.1 (Snap) -> works fine with the exact same configuration The failure mode is a crash at launch: from a terminal, "segmentation fault (core dumped)" within ~1 second, before any window is shown. A/B test with the same binary: launching with GTK_MODULES=colorreload-gtk-module:window-decorations-gtk-module (appmenu removed) starts fine; adding appmenu-gtk-module back crashes every launch. Testing each module in isolation, only appmenu-gtk-module triggers it. Environment (jammy): appmenu-gtk3-module 0.7.6-2, libgtk-3-0 3.24.33-1ubuntu2, kde-gtk-config writing the gtk-modules line into ~/.config/gtk-3.0/settings.ini. Additional data points from further testing: - Kubuntu 24.04 (noble) test install is also affected: appmenu-gtk3-module 0.7.6-2.1ubuntu2, libgtk-3-0t64 3.24.41-4ubuntu1, Plasma 5.27.11, X11, google-chrome-stable 153.0.8010.52 -> same SIGSEGV at startup with the same gtk-modules line (written by kde-config-gtk-style on that series). Both jammy and noble look affected, which may be relevant for the SRU scope. - It also reproduces on Debian 12 (bookworm, Plasma 5.27.5, X11, appmenu-gtk3-module 0.7.6-2.1, libgtk-3-0 3.24.37-2) with google-chrome-stable 153.0.8010.47 once the gtk-modules line is present, so this does not look specific to Ubuntu packaging. - Session differential on the same Debian machine, same binary, same config: under X11 the module is loaded at startup and then unloaded (captured with gdb "catch unload": chrome -> g_object_set -> libgtk-3 property handler -> g_module_close -> dlclose) and the browser SIGSEGVs on every launch; under Wayland the module never appears loaded and the browser runs fine. Chrome 151 shows no module unload at all under X11 on the same setup. - Chrome-side workaround: launching with --gtk-version=4 avoids the crash even with the module line present (GTK4 dropped gtk-modules). Workaround in use: removing appmenu-gtk-module from the gtk-modules list (KDE System Settings -> Global Theme -> "Use desktop layout from theme"). Note: the line is only dropped once no menu-integration element remains active. Besides the Global Menu widget (removed by the Global Theme step above), check the "Application menu" button under System Settings -> Appearance -> Window Decorations -> Titlebar Buttons and remove it there too if enabled; otherwise the line keeps being rewritten at every login. Happy to test the fixed package when it lands in -proposed (jammy and noble). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2166410 Title: appmenu-gtk3-module from the terminal pre-fills package versions and opens the same page in the browser. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-gtk-module/+bug/2166410/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
