| Summary: | alacarte doesn't start unless gnome-menus is installed | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Götz Waschk <goetz.waschk> |
| Component: | RPM Packages | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | critical | ||
| Priority: | Normal | CC: | davidwhodgins, girlando, isasalma2, lewyssmith, mageia, stormi-mageia, sysadmin-bugs, tmb, yann.cantin |
| Version: | 5 | Keywords: | Junior_job, Triaged, validated_update |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | MGA4TOO MGA5-64-OK MGA4-64-OK advisory | ||
| Source RPM: | alacarte-3.10.0-3.mga4.src.rpm | CVE: | |
| Status comment: | |||
| Attachments: | alacarte | ||
nothing new, cf bug 2911,10091, don't know upstream status Keywords:
(none) =>
Triaged Yes, but this is a different error.
Thierry Vignaud
2013-12-30 23:16:17 CET
Assignee:
bugsquad =>
olav Alacarte searches menu files from /etc/xdg/menus/, but gnome-applications.menu is located at /etc/xdg/gnome/menus/. You can test this by symlinking /etc/xdg/gnome/menus/gnome-applications.menu to /etc/xdg/menus/. CC:
(none) =>
jani.valimaa Another possible fix would be adding /etc/xdg/gnome/ to $XDG_CONFIG_DIRS when gnome is used. You can try this with: XDG_CONFIG_DIRS="/etc/xdg:/etc/xdg/gnome" alacarte (In reply to Jani Välimaa from comment #4) > Another possible fix would be adding /etc/xdg/gnome/ to $XDG_CONFIG_DIRS > when gnome is used. > Didn't dig further, but this should be already handled with gnome-session. See: http://svnweb.mageia.org/packages/cauldron/gnome-session/current/SOURCES/gnome-session-gnomerc?view=markup Is this bug still valid in latest cauldron? In Mageia 4? CC:
(none) =>
stormi I don't know about Cauldron, but it was not fixed in Mageia 4. Oh well, on Mageia 4 I just had to install gnome-menus which wasn't installed automatically. Now I'm able to start alacarte. So this could be a missing requires? Summary:
alacarte desn't start =>
alacarte doesn't start unless gnome-menus is installed It seems so. Tested on Mageia 5 RC. It works, once gnome-menus is installed (Comment 8). So it is just a problem of adjusting *.rpm packaging, so it install gnome-menus together with alacarte. CC:
(none) =>
girlando
Samuel Verschelde
2015-05-06 17:21:31 CEST
Whiteboard:
(none) =>
MGA4TOO
Jani Välimaa
2015-05-14 08:42:39 CEST
CC:
jani.valimaa =>
(none) Uploaded patched package for Mageia 5. The application should start now, please test. Advisory: ======================== Added missing Requires: gnome-menus ======================== Updated packages in core/updates_testing: ======================== alacarte-3.11.91-4.1.mga5.noarch.rpm From source RPMs: alacarte-3.11.91-4.1.mga5.src.rpm CC:
(none) =>
yann.cantin
Yann Cantin
2015-08-06 01:58:46 CEST
Version:
Cauldron =>
5 (In reply to Yann Cantin from comment #12) > Advisory: > ======================== > > Added missing Requires: gnome-menus That's typically the kidn of advisory that is useful to devs, but cryptic to end users. Something along those lines would be better: """ alacarte would not start in some desktop environments due to an unsatisfied dependency on the gnome-menus package. This update fixes it. """ BTW, an update for Mageia 4 would also be required IIUC. Uploaded patched package for Mageia 4, Mageia 5 and Cauldron. The application should start now, please test. Advisory: ======================== alacarte would not start in some desktop environments due to an unsatisfied dependency on the gnome-menus package. This update fixes it. ======================== Updated packages in core/updates_testing: ======================== alacarte-3.10.0-3.1.mga4.noarch.rpm alacarte-3.11.91-4.1.mga5.noarch.rpm alacarte-3.11.91-5.mga6.noarch.rpm From source RPMs: alacarte-3.10.0-3.1.mga4.src.rpm alacarte-3.11.91-4.1.mga5.src.rpm alacarte-3.11.91-5.mga6.src.rpm Testing Mageia 5 x64 using XFCE desktop - OK My system had all desktops installed. BEFORE: Removed gnome-menus, which took with it Cinnamon! Installed alacarte from normal repos: alacarte-3.11.91-4.mga5 Tried it: $ alacarte (alacarte:22919): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion 'gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed (alacarte:22919): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion 'gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed But its GUI appeared *and worked*. So it seems it can get by without gnome-menus sometimes. Sigh. AFTER: Updated alacarte from Updates Testing, which *did* pull in gnome-menus, which is the essential point of the update: alacarte-3.11.91-4.1.mga5 gnome-menus-3.13.3-4.mga5 Using it was just the same as before, same errors, but it worked. Whiteboard:
MGA4TOO advisory =>
MGA4TOO advisory MGA5-64-OK Testing Mageia 4 x64 using KDE desktop; OK The system had all desktops installed. BEFORE: Removed gnome-menus, which again took Cinnamon with it. Installed alacarte from normal repos: alacarte-3.10.0-3.mga4 Trying it: $ alacarte (alacarte:9769): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion 'gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed (alacarte:9769): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion 'gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed but it appeared and seemed to work (but I could not get 100% agreement on its menus and those of KDE; no matter). So much for gnome-menus. AFTER: Updated alacarte from Updates Testing, which *pulled in gnome-menus*, which is what this update is about: alacarte-3.10.0-3.1.mga4 gnome-menus-3.10.1-2.mga4 Running it was just the same as previously. Whiteboard:
MGA4TOO advisory MGA5-64-OK =>
MGA4TOO advisory MGA5-64-OK MGA4-64-OK (In reply to Lewis Smith from comment #16) > Removed gnome-menus, which again took Cinnamon with it. Note that you should be able to remove gnome-menus without removing packages that depend on it using: rpm -e --nodeps gnome-menus
Dave Hodgins
2015-08-10 05:52:23 CEST
CC:
(none) =>
davidwhodgins, sysadmin-bugs no advisory in svn CC:
(none) =>
tmb Advisory uploaded. Whiteboard:
MGA4TOO MGA5-64-OK MGA4-64-OK =>
MGA4TOO MGA5-64-OK MGA4-64-OK advisory An update for this issue has been pushed to Mageia Updates repository. http://advisories.mageia.org/MGAA-2015-0099.html Status:
NEW =>
RESOLVED Created attachment 13817 [details]
alacarte
(alacarte:403224): Gtk-CRITICAL **: 19:38:26.508: gtk_accel_label_set_accel_closure: assertion 'gtk_accel_group_from_accel_closure (accel_closure) != NULL' failedCC:
(none) =>
isasalma2 |
$ alacarte (alacarte:11090): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion 'gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed (alacarte:11090): Gtk-CRITICAL **: 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/python2.7/site-packages/Alacarte/MainWindow.py", line 454, in main app.setMenuBasename(basename) File "/usr/lib/python2.7/site-packages/Alacarte/MainWindow.py", line 65, in setMenuBasename self.editor = MenuEditor(menu_basename) File "/usr/lib/python2.7/site-packages/Alacarte/MenuEditor.py", line 36, in __init__ self.load() File "/usr/lib/python2.7/site-packages/Alacarte/MenuEditor.py", line 49, in load if not self.tree.load_sync(): gi._glib.GError: Failed to look up menu_file for "gnome-applications.menu" Reproducible: Steps to Reproduce: