On Mon, May 23, 2016 at 9:32 AM, Brian <a...@cityscape.co.uk> wrote: > On Mon 23 May 2016 at 09:07:36 +0200, to...@tuxteam.de wrote: > >> On Sun, May 22, 2016 at 11:38:39PM +0100, Lisi Reisz wrote: >> > On Sunday 22 May 2016 22:56:36 Richard Owlett wrote: >> > > >> > > So what ever B**** says goes? >> > > Please *NO* !!!!! >> > >> > Richard - this snipping is very misleading. It was not Tomas whom Brian >> > was >> > calling incompetent - in fact, quite the opposite. I can't quite see why >> > Tomas has taken such fright, except that both the others were putting >> > things >> > rather strongly. But *nothing* that Brian said could reasonably have been >> > interpreted, as you appear to have done, as Brian telling Tomas to leave >> > the >> > thread. >> >> Exactly, Lisi. I'm too old to watch people slinging mud at each other >> ("asshole", "incompetent") like kids. I mean, I feel strongly about >> software, that's why I'm here, and I feel strongly about free software >> and its social value, but my time is just too precious for that nonsense. >> >> So you got it right. > > The OP deposited his FUD in -user (twice), completely ignored the > invitation to explore a technical solution using ifupdown and has now
Regardless of ifupdown, I want network-manager to work like it's supposed to, i.e. the same way in a dbus-launch-spawned session as under gnome. It doesn't. That a bug, not FUD. > taken himself off to -devel, which is not renowned for suffering the > spreading of misinformation. There's agreement on devel that it's not FUD. I posted a detailed description of the problem there. Go read it and send me something useful instead of more groundless claims that bug reports on network-manager are FUD. > One hopes his transition to there was not > due to anything *I* said and he gets a glimmer of clue, :) It was partly due to you, I'm hoping for more substantive responses there. Britton