[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-bugs-dist
Subject: [plasmashell] [Bug 348123] Some processes are left running after exiting KDE
From: John Stanley via KDE Bugzilla <bugzilla_noreply () kde ! org>
Date: 2015-11-03 7:08:13
Message-ID: bug-348123-17878-m7xgpzByN3 () http ! bugs ! kde ! org/
[Download RAW message or body]
https://bugs.kde.org/show_bug.cgi?id=348123
--- Comment #21 from John Stanley <jpsinthemix@verizon.net> ---
(In reply to John Stanley from comment #20)
> (In reply to Rex Dieter from comment #19)
> > If you could provide any technical details on the pulseaudio problem, I'd be
> > happy to facilitate pushing it back to pulseaudio upstream devs.
>
> I'll look into it a bit in the next few days.. but now I'm trying to finish
> a fix for the session management issue
> https://bugs.kde.org/show_bug.cgi?id=346768 (I have a tentative fix for
> 346768 which is probably good enough for me, but I'm not completely happy
> with it, so I need to play with it a bit more).
Here's a summary of the issue along with a resolution (looks like its not
really a bug after all):
For a vanilla pulseaudio-7.1 installation, the pulse daemon remains running for
some time after user session logout (after logout, the user processes
pulseaudio and sd-pam(systemd) remain. The processes do in fact terminate some
15+ seconds later.
You can see this in the (loglevel info) logs, eg,
Nov 02 18:23:23 b-movie pulseaudio[4185]: [pulseaudio] client.c: Freed 10
"KMix"
Nov 02 18:23:23 b-movie pulseaudio[4185]: [pulseaudio] protocol-native.c:
Connection died.
Nov 02 18:23:23 b-movie pulseaudio[4185]: [pulseaudio] client.c: Freed 0 "Login
Session c2"
Nov 02 18:23:43 b-movie pulseaudio[4185]: [pulseaudio] core.c: We are idle,
quitting...
Nov 02 18:23:43 b-movie pulseaudio[4185]: [pulseaudio] main.c: Daemon shutdown
initiated.
I thought about fixing this with a simple patch, eg,
--- pulseaudio-7.1.old/src/modules/module-systemd-login.c 2015-09-10
00:51:41.000000000 -0400
+++ pulseaudio-7.1.new/src/modules/module-systemd-login.c 2015-11-02
20:53:55.338622526 -0500
@@ -94,6 +94,9 @@
pa_log_debug("Removing session %s", session->id);
+ /* Presumably a logout; no need for idle waits */
+ session->client->core->exit_idle_time = 0;
+
pa_client_free(session->client);
pa_xfree(session->id);
pa_xfree(session);
but then (stupid me) I had a look at the pulse-daemon.conf manpage, which
contains:
IDLE TIMES
exit-idle-time= Terminate the daemon after the last client quit and this time
in
seconds passed. Use a negative value to disable this feature. Defaults to 20.
The
--exit-idle-time command line option takes precedence.
So, in /etc/pulse/daemon.conf, setting exit-idle-time = 0 solves the problem.
Note that setting it to a negative value effectively sets the idle wait to
infinity (the daemon never terminates on its own).
So, this is not really a bug after all, but I am curious about the intended
purpose of this idle wait time and whether there are negative repercussions to
setting it to zero.
--
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic