Comment 26 for bug 985788

> Mathieu: I’m worried that fixing nm-applet’s gnome-shell detection code, without first
> fixing gnome-shell’s location to look for NM plugins (which should be
> /usr/lib/network-manager instead of /usr/lib/gnome-shell), will cause this to break all
> the time, instead of just when gnome-shell doesn’t lose the startup race.

This appears to be exactly what happened with the upload of network-manager-applet 0.9.6.0~git201207161252.13c6db8-0ubuntu1. Now it’s _always_ impossible to connect to a VPN from gnome-shell, even when nm-applet is started first.

$ nm-applet &

** (nm-applet:29893): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-Uvn8AW90K7: Connection refused
** Message: applet now removed from the notification area
** Message: using fallback from indicator to GtkStatusIcon
$ gnome-shell &

** (gnome-shell:29899): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-Uvn8AW90K7: Connection refused
      JS LOG: Error: Requiring IBus, version none: Typelib file for namespace 'IBus' (any version) not found

** (gnome-shell-calendar-server:29910): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-Uvn8AW90K7: Connection refused
      JS LOG: GNOME Shell started at Wed Jul 18 2012 19:53:08 GMT-0400 (EDT)
** Message: applet now embedded in the notification area
** Message: Stopping applet secret agent because GNOME Shell appeared
$ [try to connect to a VPN]
      JS LOG: Error 'VPN plugin at /usr/lib/gnome-shell/nm-openconnect-auth-dialog is not executable' while processing VPN keyfile '/etc/NetworkManager/VPN/nm-openconnect-service.name'
      JS LOG: Error 'VPN plugin at /usr/lib/gnome-shell/nm-pptp-auth-dialog is not executable' while processing VPN keyfile '/etc/NetworkManager/VPN/nm-pptp-service.name'
      JS LOG: Invalid VPN service type (cannot find authentication binary)