Merge lp:~3v1n0/bamf/libbamf-sticky-proxy-keep-alive into lp:bamf/0.4
Status: | Merged |
---|---|
Approved by: | Łukasz Zemczak |
Approved revision: | 472 |
Merged at revision: | 470 |
Proposed branch: | lp:~3v1n0/bamf/libbamf-sticky-proxy-keep-alive |
Merge into: | lp:bamf/0.4 |
Diff against target: |
159 lines (+27/-30) 2 files modified
lib/libbamf/bamf-factory.c (+3/-2) lib/libbamf/bamf-view.c (+24/-28) |
To merge this branch: | bzr merge lp:~3v1n0/bamf/libbamf-sticky-proxy-keep-alive |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Jason Smith (community) | Approve | ||
Review via email: mp+109971@code.launchpad.net |
Commit message
libbamf, bamf-view: don't unset the proxy on closed sticky views
Also, don't reset the proxy if the current one is still valid.
Description of the change
When a sticky bamf view is closed, libbamf used to unset its dbus proxy; this is generally right, but in some tricky cases (hard to debug, mostly timing dependent) it caused that when the same application was opened again, the newly set proxy was not notified when a signal was emitted by the server.
This lead to bug #978401
To fix this, we don't unset the proxy of a sticky application when the related dbus object is closed, so that it will stay alive and will automatically reconnect to signals when the object will be exported again.
Also, now if we try to set the path of a view without changing it, we just ignore the request and we continue with the proxy that we already have.
Works fine