diff options
author | Ryan Lortie <desrt@desrt.ca> | 2012-04-30 13:43:23 -0400 |
---|---|---|
committer | Ryan Lortie <desrt@desrt.ca> | 2012-04-30 17:50:45 -0400 |
commit | babd137e325931ee7b791dec8df825ad1262a320 (patch) | |
tree | c93ec0521c9d1ea68f977d1ea4574c667ba00715 /gtk/gtkapplicationprivate.h | |
parent | cdf473ec100d23ea6a9a8750ad301307a116b674 (diff) | |
download | gtk+-babd137e325931ee7b791dec8df825ad1262a320.tar.gz |
GtkApplication: fixes for NULL session bus
We currently have a couple of cases where GtkApplication assumes that
the session bus will be non-NULL causing critical error output or (in
the case of trying to publish menus) an infinite loop.
Three fixes:
- if the session bus is NULL due to not having registered the
GtkApplication yet then give a g_critical on the entry point to the
menu setters instead of going into an infinite loop. Document this.
- check for NULL session bus even when calling the menu setters at the
right time in order to prevent the infinite loop for
non-programer-error cases (ie: because we had trouble connecting to
the session bus)
- check for NULL session bus when publishing the X11 properties on the
GtkApplicationWindow and skip publishing them if we're not on the bus
https://bugzilla.gnome.org/show_bug.cgi?id=671249
Diffstat (limited to 'gtk/gtkapplicationprivate.h')
0 files changed, 0 insertions, 0 deletions