@khurshid-alam Sorry for responding so late.
As far as I can see, the patch wasn't applied to the bionic tree of bamf, so I think this should still be a problem in 18.04, but I haven't tested this. I have only experience with Unity and bamf in 16.04 and it seems that there were some Unity changes which mask the problem, or at least make it harder to reproduce. But that doesn't change, that I think that the cache reloading logic is wrong, and that it can lead to problems as described in my initial bug report. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1609303 Title: libbamf: BamfView child cache not reloading Status in bamf package in Ubuntu: New Bug description: When applications close and re-open their window and BamfView changed its path, the child cache of BamfView does not reload its children and continues to work with the old cache, which does not contain any children. The application icon in Unity then does not do anything (cannot raise the application window, activate a minimized window or Alt-Tab to the window). This problem shows up for us mainly when using the Citrix Receiver, but other applications can trigger this too. This problem exists in Trusty and Yaketty (maybe older versions too, I haven't checked those), and the attached patch fixes the problem (fixes the handling of the reload_children boolean). I think the following bug report might be the same problem: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1326903 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1609303/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
