https://bugs.kde.org/show_bug.cgi?id=363851
--- Comment #10 from Me <sno...@icloud.com> --- I’m running KDE neon in an Oracle VirtualBox VM. I keep it fully apt-get dist-upgraded. If I leave #KillUserProcesses=no, then the shutdown process ‘hangs’ once the KDE neon 5.6.90 logo screen appears for a full 1min 30s. I’ve screen-captured this: Where is this second session of ‘me’ coming from? It’s this second session that is hung (I believe it’s actually dead — a zombie?) and causes systemd to delay the shutdown; it waits for the second session to terminate “on it’s own”, and when, after the default time of 1min 30s, it hasn’t, systemd then kills it and the shutdown finishes as it should. Paul Loughman sno...@icloud.com > On Jun 10, 2016, at 1:49 PM, Thomas Pfeiffer via KDE Bugzilla > <bugzilla_nore...@kde.org> wrote: > > https://bugs.kde.org/show_bug.cgi?id=363851 > > --- Comment #9 from Thomas Pfeiffer <thomas.pfeif...@kde.org> --- > (In reply to Martin Steigerwald from comment #8) >> Entirely your choice and in the end I don´t care, cause I do not intend to >> use Neon. Yet, you mask bugs this way. > > Sure, I'm all for fixing the misbehaving applications, but "Let's expose other > people's fuck-ups so they'll fix them" has not been a very successful approach > for us in the past. > Usually what happens is that those who fucked up don't do anything about it, > and our users blame _us_ for the problems. > > -- > You are receiving this mail because: > You are the assignee for the bug. > _______________________________________________ > neon mailing list > n...@kde.org > https://mail.kde.org/mailman/listinfo/neon -- You are receiving this mail because: You are watching all bug changes.
