Small correction to my previous comment, on the A/B test method: the GTK_MODULES environment variable only adds modules on top of the gtk-modules line in settings.ini — it does not override it — so the removal side of the test was performed differently, with two methods:
1. Editing the gtk-modules line directly in settings.ini for the session (KDE regenerates the file at each login, so the edit only lasts until the next login — enough for the test). 2. As a cross-check, blocking the module for Chrome specifically through the module's own per-application blacklist: gsettings set org.appmenu.gtk-module blacklist "['google-chrome']" The results are unchanged: with the same binary, removing appmenu-gtk-module from the list -> starts fine; re-adding it -> crashes every launch; and testing each of the three modules individually, only appmenu-gtk-module triggers the crash. Worth noting for anyone exploring workarounds: since GTK_MODULES only adds modules, it cannot be used to exclude appmenu-gtk-module from the list. -- 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
