On Wed, 2015-04-29 at 07:09 +0200, Michael Biebl wrote: > Hi Dan! > > Am 27.04.2015 um 22:00 schrieb Dan Williams: > > On Mon, 2015-04-27 at 18:35 +0200, Michael Biebl wrote: > >> Am 12.04.2015 um 15:15 schrieb Jérémy Lal: > >> Afair, nm-applet was still autostarted for by gnome-shell to provide the > >> VPN auth dialogs/secrets. I don't think this is the case anymore today, > >> but I'm not totally sure. [1] indicates that it is no longer necessary. > > > > GNOME autostart was disabled by d6ffe34dc092926fb949449c182e8f27722b6b8b > > (2013-07-29) and then the shell watcher code was reworked and autostart > > was re-enabled by e192e83c1aa136512a9d4f026f81677799af8127 (2013-10-10). > > > > So yeah, it's re-autostarted now, and I guess that should be disabled. > > GNOME Shell has handled VPN auth dialogs since version 3.4 or something > > like that (almost 3 years old). I've committed a change to the applet's > > git master to disable autostart again. > > I see, that you added GNOME to NotShowIn= > I wonder if using > AutostartCondition=GNOME3 unless-session gnome > would be better, so it would still be run e.g. in GNOME flashback?
Do you mean the 'fallback' session? If so, that still runs the GNOME Shell network indicator. > > On the subject of splitting nm-connection-manager from nm-applet in > > packages, yes, I'd recommend that. I would have 3 packages generated > > from the network-manager-applet git repo: > > > > nm-applet > > That's currently called network-manager-gnome in Debian/Ubuntu > > > nm-connection-editor > > We don't split of nm-connection-editor (yet) in Debian. Is there a good > reason to do so? Is the nm-connection-editor binary called from within a > GNOME Shell session? It does get called from the gnome-control-center binary for some specific configuration cases still. Dan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
