Bug 32902 - alacarte fail to launch
Summary: alacarte fail to launch
Status: RESOLVED DUPLICATE of bug 25361
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 9
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-02-26 21:23 CET by Eduardo Mestre
Modified: 2024-02-27 15:50 CET (History)
1 user (show)

See Also:
Source RPM: alacarte-3.44.2-1.mga9.src.rpm
CVE:
Status comment:


Attachments

Description Eduardo Mestre 2024-02-26 21:23:55 CET
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.
Morgan Leijström 2024-02-26 22:54:34 CET

CC: (none) => fri
Summary: Close with error => alacarte fail to launch

Comment 1 sturmvogel 2024-02-27 15:50:28 CET
Unbelievable...the bug was already reported in 2019

*** This bug has been marked as a duplicate of bug 25361 ***

Resolution: (none) => DUPLICATE
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.