Ticket #189 (assigned enhancement)

Opened 9 months ago

Last modified 3 months ago

Killing a stream with pavucontrol doesn't kill the client it belongs to

Reported by: jbglaw Assigned to: lennart (accepted)
Priority: normal Milestone:
Component: pavucontrol Severity: normal
Keywords: Cc:

Description

Just insalled a new version of pavucontrol that allows me to kill a client connection. Due to a misconfigured flash plugin, this looked quite helpful since the ~30 client connection limit is rapidly eaten up by it within some seconds... Since I almost always have pavucontrol opened, I tried to kill all those connections. They're removed from the stream list, but pulseaudio's file descriptors to the local socket aren't closed and (as before) further client connections are disallowed.

This is with SVN as of two days ago IIRC.

Change History

02/15/08 15:05:24 changed by lennart

  • status changed from new to assigned.
  • type changed from defect to enhancement.

Killing a stream will only do just that -- kill a stream. The connection is kept around. That's intended behaviour.

It might make sense to add another option for killing a client. OTOH having both is a bit confusing. Hmm, I have to think about it.

02/15/08 15:06:03 changed by lennart

  • component changed from daemon to pavucontrol.

06/10/08 23:50:10 changed by monreal

Isn't "killing" a bad word to use in a GUI? At least the GNOME HIG says not to use violent words like that.

06/21/08 17:33:10 changed by lennart

  • summary changed from Killing a client connection doesn't really kill it to Killing a stream with pavucontrol doesn't kill the client it.

06/21/08 17:33:26 changed by lennart

  • summary changed from Killing a stream with pavucontrol doesn't kill the client it to Killing a stream with pavucontrol doesn't kill the client it belongs to.