Ticket #189 (assigned enhancement)

Opened 3 years ago

Last modified 2 years ago

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

Reported by: jbglaw Owned by: lennart
Milestone: Component: pavucontrol
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

Changed 3 years ago 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.

Changed 3 years ago by lennart

  • component changed from daemon to pavucontrol

Changed 2 years ago 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.

Changed 2 years ago 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

Changed 2 years ago 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
Note: See TracTickets for help on using tickets.