Shotwell - menubar not updated when switching back to a category
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| AppMenu GTK+ |
Fix Released
|
Undecided
|
Unassigned | ||
| appmenu-gtk (Ubuntu) |
Fix Released
|
Low
|
Michael Terry | ||
Bug Description
Currently I am seeing three categories in the sidebar of shotwell, initially 'Photos' is selected. when I click on 'Events' category and come back to the menubar I see that menu items have changed but now If I click back on the 'Photos' category I wont get the same menubar it will remain the same as it was on events *but* if I click on a third category 'Trash' the menubar will change to trash related menus but clicking back on the first two categories won't switch to their menus.
Its like 'there is no going back'.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: libdbusmenu-gtk3 0.3.100-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-5-generic i686
Architecture: i386
Date: Fri Mar 4 22:01:54 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110226)
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: libdbusmenu
UpgradeStatus: No upgrade log present (probably fresh install)
Related branches
- Ted Gould (community): Approve
-
Diff: 161 lines (+61/-47)1 file modifiedsrc/bridge.c (+61/-47)
- Ken VanDine: Pending requested
-
Diff: 16203 lines (+5946/-3346)18 files modifiedMakefile.in (+3/-1)
aclocal.m4 (+8/-6)
build/Makefile.in (+3/-1)
build/autotools/Makefile.in (+3/-1)
build/autotools/libtool.m4 (+1256/-782)
build/autotools/ltoptions.m4 (+7/-6)
build/autotools/ltversion.m4 (+6/-6)
build/autotools/lt~obsolete.m4 (+9/-3)
config.guess (+120/-105)
config.sub (+101/-55)
configure (+1796/-966)
configure.ac (+1/-1)
debian/changelog (+10/-0)
debian/patches/01_remove_unused_variables.patch (+0/-19)
debian/patches/series (+0/-1)
ltmain.sh (+2619/-1390)
src/Makefile.in (+3/-1)
src/bridge.c (+1/-2)
| Omer Akram (om26er) wrote | #1 |
| Changed in libdbusmenu (Ubuntu): | |
| assignee: | nobody → Michael Terry (mterry) |
| importance: | Undecided → Low |
| Changed in libdbusmenu (Ubuntu): | |
| status: | New → Confirmed |
| Changed in libdbusmenu (Ubuntu): | |
| status: | Confirmed → In Progress |
| Michael Terry (mterry) wrote | #2 |
| affects: | dbusmenu → appmenu-gtk |
| affects: | libdbusmenu (Ubuntu) → appmenu-gtk (Ubuntu) |
| Changed in appmenu-gtk: | |
| status: | New → Fix Committed |
| Changed in appmenu-gtk: | |
| milestone: | none → 0.1.96 |
| status: | Fix Committed → Fix Released |
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in appmenu-gtk (Ubuntu): | |
| status: | In Progress → Fix Released |
OK, this so far appears to be a problem in appmenu-gtk, because it only re-examines the menubar when it sees new items inserted. So it correctly notices the first time any of these menus is created. But when just switching between menus that have already been created, it doesn't notice.
Probable fix is to make it watch when menubars are reparented.