When trying to add a submenu as a menu button to the panel (via the context menu of a menu entry) an error message is written into ~/.xsession-errors: ** (gnome-panel:10887): WARNING **: Failed to find menu scheme for gnome-applications.menu Since applications.menu was renamed, gnome-panel need to be patched with the new name of that file. The following attached patch fix the problem. References: http://bugs.gentoo.org/256614 http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg343712.html Reproducible: Always Steps to Reproduce: 1 - Go to Applications menu, then a submenu. 2 - Right clic on an icon, the context menu appear 3 - Hilight 'all the menu', and clic on 'add this as a menu on the panel'
Created attachment 208840 [details, diff] gnome-panel-2.26.3-menu-button.patch
This is completely wrong. Please read gnome 2.28 migration guide and/or gnome-menus elog informations.
Reference: http://www.gentoo.org/proj/en/desktop/gnome/howtos/gnome-2.26-upgrade.xml
Sorry, I have already read the gnome migration 2.26 guide. I login with gdm. > $ export | grep XDG_MENU > declare -x XDG_MENU_PREFIX="gnome-" You should try to reproduce before closing the bug. I'm on a stable system with gnome 2.26.
(In reply to comment #2) > This is completely wrong. Please read gnome 2.28 migration guide and/or > gnome-menus elog informations. > +1 Then please read the lastest entry in my blog http://blogs.gentoo.org/mrpouet
and it works just fine on my laptop (amd64 stable system)
Created attachment 208883 [details] emerge --info (In reply to comment #5) > Then please read the lastest entry in my blog http://blogs.gentoo.org/mrpouet > I read elog messages. I receive them in my mailbox.(In reply to comment #6) > and it works just fine on my laptop (amd64 stable system) > It doesn't works here until I patched gnome-panel-2.26.3. And I'm not the only one that this happens, there's some peoples on the forum who patched gnome-panel to have the same result.
(In reply to comment #4) > Sorry, I have already read the gnome migration 2.26 guide. I login with gdm. > > > $ export | grep XDG_MENU > > declare -x XDG_MENU_PREFIX="gnome-" > > You should try to reproduce before closing the bug. > I'm on a stable system with gnome 2.26. What do you think I'm using, KDE ? I wrote the code and migration guide and users helped me iron it out so I'm pretty sure it covers all cases. Anyway if you have some surprising corner case, please attach your .xsession-errors and the result of the "env" command.
Created attachment 208944 [details] output of env > What do you think I'm using, KDE ? No, but I quote you : > This is completely wrong. In 4 words, you are saying that I'm lying and you close the bug instantly. It is not already obvious to try to explain the problem when english is not your native language, but also whether to fight every time to justify everything... This is really frustrating. Do you think that I will lose my time to open a bug just for fun ? No luck, I read elogs and guides, I know gentoo, and it still seems that something is wrong. This is at least 3 months that I am under gnome 2.26, I can reproduce the bug as many times as you want on 3 differents x86 systems. My system is clean and up-to-date. Maybe something is wong, but in this case, the upgrade guide is not enough. The attached file is the output of the env command just after I login with gdm.
Created attachment 208946 [details] xsessions-errors
Ok I see it now that's a new issue. gnome-panel does not respect XDG_MENU_PREFIX and that's where the real problem is. My initial "this is completely wrong" message was about the supposed fix. The proposed fix is simply not the solution. It is just a workaround, just like telling users to remove ~/.local when upgrading shared-mime-info.
Created attachment 209019 [details, diff] gmenu-simple-editor.patch I just noticed that running /usr/bin/gnome-simple-editor is fine, but making changes on the menu does not work : the changes are not saved, and the next time I run the gnome-simple-editor, all the checkbox are checked. See the attached patched, obviously it fixed the problem. Strange.
so that confirms that gnome-panel is clueless about XDG_MENU_PREFIX, wonderful.
And again, I'm not alone with this bug, see the following forum thread : http://forums.gentoo.org/viewtopic-p-6039506.html Something is wrong.
There are two issues in this bug: 1) gnome-panel does not respect XDG_MENU_PREFIX 2) gmenu-simple-editor does not respect XDG_MENU_PREFIX while editing menus I suspect alacarte is also broken in a similar way. Question is, do we want these apps to respect XDG_MENU_PREFIX (ie, gnome- or kde- etc) or we want them to only use "gnome-" ? Note that other distros seem to have opted to hard-code the value.
hardcoding the value is the most idiotic option obviously. gnome apps are supposed to be XDG compliant when the cost of implementation is worth it (not in evolution 2.* for example). gnome-panel and it's utilities should respect it. alacarte works just fine as far as I know (it had a couple of open bugs about that in the past).
other distro opted to hard-coded it, which is pretty ugly :) in the worst case, we could use XDG_MENU_PREFIX directly in gnome-panel (but properly using g_getenv() and so on...) Normally gmenu should use it.. (and does in 2.26... I'm not sure.. that's why I don't understand why it does not work... well)
(In reply to comment #15) > There are two issues in this bug: > > 1) gnome-panel does not respect XDG_MENU_PREFIX > 2) gmenu-simple-editor does not respect XDG_MENU_PREFIX while editing menus > Bugs still present in gnome-panel-2.28.0 and gnome-menus-2.28.0.1. I must patch them in the same way to solve the problem and got them working as expected. (In reply to comment #16) > hardcoding the value is the most idiotic option obviously. This is not an option : it's already hardcoded by upstream. Is this still the case in gnome 2.30 ?
(In reply to comment #15) > 2) gmenu-simple-editor does not respect XDG_MENU_PREFIX while editing menus Will be fixed in next gnome-menus-2.30.3 by commit 2054996af842e6df1726e58d81a569f03e30d75f on http://git.gnome.org/browse/gnome-menus/
(In reply to comment #18) > (In reply to comment #15) > > There are two issues in this bug: > > > > 1) gnome-panel does not respect XDG_MENU_PREFIX Is gnome-panel upstream aware of this problem?
(In reply to comment #20) > Is gnome-panel upstream aware of this problem? Upstream bug 623221.
Thanks
(In reply to comment #19) > (In reply to comment #15) > > 2) gmenu-simple-editor does not respect XDG_MENU_PREFIX while editing menus > > Will be fixed in next gnome-menus-2.30.3 by commit > 2054996af842e6df1726e58d81a569f03e30d75f > on http://git.gnome.org/browse/gnome-menus/ > Included in gnome-menus-2.30.2-r1
Created attachment 260425 [details, diff] gnome-panel-prefix.patch Looks like openbsd people are using this one :-/, but I haven't tested it
And more in http://www.openbsd.org/cgi-bin/cvsweb/ports/x11/gnome/panel/patches/
*** Bug 291131 has been marked as a duplicate of this bug. ***
OK Looks like http://bugzilla-attachments.gnome.org/attachment.cgi?id=179461 is the only one needed just now. Upstream (vuntz) is aware of the problem but I am not sure about when he will have time to look at this. I would vote for using that patch as, even hardcoding the value, it's still better than current situation (at least on a "default" setup with XDG_MENU_PREFIX=gnome-
(In reply to comment #27) > OK > > Looks like http://bugzilla-attachments.gnome.org/attachment.cgi?id=179461 is > the only one needed just now. Upstream (vuntz) is aware of the problem but I am > not sure about when he will have time to look at this. I would vote for using > that patch as, even hardcoding the value, it's still better than current > situation (at least on a "default" setup with XDG_MENU_PREFIX=gnome- I will go for this solution if nobody disagrees
+*gnome-panel-2.32.1-r2 (03 Apr 2011) + + 03 Apr 2011; Pacho Ramos <pacho@gentoo.org> -gnome-panel-2.30.2.ebuild, + -gnome-panel-2.32.1.ebuild, +gnome-panel-2.32.1-r2.ebuild: + Revision bump including multiple fixes from 2.32 and master upstream branches + (including upstream fix for bug #357197 by Alessandro Surace and using + gnome-applications.menu instead of applications.menu as it's our default + value until upstream resolve their bug #623221 in a better way). Also drops + --with-in-process-applets configure option to prevent annoying error messages + about applets disappearing 'unexpectedly' when removing wncklet, clock or + notification-area applets (upstream default value for this is 'none'). Remove + old. +
*** Bug 367523 has been marked as a duplicate of this bug. ***