Description of problem: In GNOME Terminal (in wayland) [eduardo@ideafix ~]$ alacarte (alacarte:97122): Gtk-CRITICAL **: 21:11:21.812: gtk_accel_label_set_accel_closure: assertion 'gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed (alacarte:97122): Gtk-CRITICAL **: 21:11:21.812: gtk_accel_label_set_accel_closure: assertion 'gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed Traceback (most recent call last): File "/usr/bin/alacarte", line 24, in <module> main() File "/usr/lib/python3.10/site-packages/Alacarte/MainWindow.py", line 464, in main app.setMenuBasename(basename) File "/usr/lib/python3.10/site-packages/Alacarte/MainWindow.py", line 62, in setMenuBasename self.editor = MenuEditor(menu_basename) File "/usr/lib/python3.10/site-packages/Alacarte/MenuEditor.py", line 36, in __init__ self.load() File "/usr/lib/python3.10/site-packages/Alacarte/MenuEditor.py", line 49, in load if not self.tree.load_sync(): gi.repository.GLib.GError: g-io-error-quark: Failed to look up menu_file for "gnome-applications.menu" (0) [eduardo@ideafix ~]$ Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. sudo urpmi alacarte 2. alacarte 3.
CC: (none) => friSummary: Close with error => alacarte fail to launch
Unbelievable...the bug was already reported in 2019 *** This bug has been marked as a duplicate of bug 25361 ***
Resolution: (none) => DUPLICATEStatus: NEW => RESOLVED