libbamf: BamfView child cache not reloading
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bamf (Ubuntu) |
New
|
Undecided
|
Unassigned |
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:
tags: | added: trusty |
tags: | added: yakkety |
Did anyone look into this? If not, could you please take a look?
The attached patch provides an obvious and simple (one line) fix, and it would be great to see this fixed in bamf, to prevent "losing" application windows, because the corresponding Unity icon does not do anything and the windows also don't show up in the task switcher.
These basic window handling bugs can really be a pain, and it took me quite some time to find the root cause, so I would really appreciate it getting integrated into the upstream bamf code.
And it seems all versions from trusty up to yakkety are affected.
Thanks!