GNOME Bugzilla – Bug 165010
User menu items lost after upgrade
Last modified: 2005-01-31 13:03:12 UTC
Distribution: Debian 3.1 Package: control-center Severity: normal Version: GNOME2.8.1 unspecified Gnome-Distributor: Debian Synopsis: User menu items lost after upgrade Bugzilla-Product: control-center Bugzilla-Component: general Bugzilla-Version: unspecified Description: Description of Problem: All user added menu items disappeared after upgrade Steps to reproduce the problem: 1. Use dselect to automatically upgrade all your packages. 2. Reboot your computer... 3. Actual Results: None of the user added menu items in the main menu are there. Seems like only the original items are there. A complete reset of the menus to scratch. Expected Results: I expected to have the same items in the menu as before the upgrade. How often does this happen? At least today... Additional Information: ------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-01-23 14:15 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "control-center". Setting to default milestone for this product, '---' Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
You mean menus items in the panel menu bar, right ? The menu system now uses the freedesktop menu specs, I'm not sure how user-added items fall into this plan. I'm reassigning to gnome-panel.
Thomas: are you using gnome 2.8.x or 2.9.x?
It is a Debing testing mix of 2.8.x (Some components are 2.8.0, some 2.8.1 and some 2.8.2) Any specific package you are after? BR /Thomas
And regarding the first question. Yes, it is the "menu bar". (I had to revert to English to figure out. Normally I run it localized to Swedish :-) /Thomas
I get this problem with gnome 2.8.2. It actually appears to be caused by glib- 2.6.1 since reverting to glib-2.6.0 returns all the user created items to the application menu. Cheers, James
There are two points here: + if James is right, there might be a glib bug. Thomas, can you confirm that downgrading glib helps? + user menu items will have bigger problems during the 2.8 => 2.10 transition since we now use the freedesktop menu spec. If point 1 is confirmed, then it'd be great to track down the problem. Point 2 is a bigger fish and we'll probably need to handle it soon...
Confirmed. Downgrading fixes it. It is even reproducable :-)
Is there some patches in the glib debian packages (for both 2.6.0 & 2.6.1 versions)? Looking at the ChangeLog, I don't see what could change the behaviour here... http://cvs.gnome.org/viewcvs/glib/ChangeLog?&only_with_tag=glib-2-6&view=auto It'd be great to track this regression.
Well, I have not been studying the code. But here is a link to the Debian diff-file: http://snapshot.debian.net/archive/2005/01/09/debian/pool/main/g/glib2.0/glib2.0_2.6.1-1.diff.gz If you search for glib2 on the following page in the package name pattern field http://snapshot.debian.net/ you will find the archive for the package. There you will have the all recent releases. Looking at the diff file it is mostly Makefile changes and some Debian specific items. Strangely enough I see no changes to the glib2 itself... There are a few intermediate version which I can give a try if you are interested? (One thing though: They are going to shutdown some of the Debian package sites this weekend due to a planned power interruption)
I went thru all of the intermediate packages and it is between 2.6.0 and 2.6.1-1 something happens.
Just thought I'd add that it isn't Debian specific since I'm using Gentoo. As far as I can see from the ebuild there's no patches to the gentoo version, just a straight compile from the source tarball.
cc'ing Matthias because he might know what have changed between glib 2.6.0 and glib 2.6.1 that can cause this Matthias: it seems a glib upgrade is breaking the menu editing in GNOME 2.8.x.
I have no idea; almost all changes between 2.6.0 and 2.6.1 are related to handling of filename encoding on win32. I think the first step would be to identify what glib interfaces are used when loading menus.
Ok, Debian people found the fix. It's because the behaviour of g_find_program_in_path was corrected for 2.6.1. *** This bug has been marked as a duplicate of 165799 ***