Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 695374 - sys-apps/audio-entropyd -d pulse leaves media-sound/pulseaudio open on Plasma logout
Summary: sys-apps/audio-entropyd -d pulse leaves media-sound/pulseaudio open on Plasma...
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal with 1 vote (vote)
Assignee: No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it
URL:
Whiteboard:
Keywords: NeedPatch
Depends on:
Blocks:
 
Reported: 2019-09-22 01:50 UTC by Red
Modified: 2022-06-18 07:40 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Red 2019-09-22 01:50:26 UTC
if you have run "sudo audio-entropyd -d pulse" while using Plasma, it leaves pulseaudio open when you log out.

Logging back in results in duplicate pulseaudio processes, and audio-entropyd crashes when you try and run it again.

Reproducible: Always

Steps to Reproduce:
1. Launch Plasma and open a terminal.
2. Run "pgrep -a pulseaudio" to make sure PulseAudio is running.
3. Run "sudo audio-entropyd -d pulse"
4. Log out of Plasma.
5. Type "pgrep -a audio-entropyd"
6. Type "pgrep -a pulseaudio"
7. Run "sudo audio-entropyd -d pulse"
Actual Results:  
5. audio-entropyd is not running.
6. Duplicate pulseaudio processes.
7. "audio-entropyd -d pulse" fails to run.

Expected Results:  
5. audio-entropyd should be running.
6. Only one pulseaudio process.
7. You shouldn't need to run audio-entropyd again, and if you do it shouldn't crash.

The duplicate processes will restart every time you attempt to kill them unless "autospawn: no" is temporarily added to /etc/pulse/client.conf.

Not sure what exactly this is a bug with: sys-apps/audio-entropyd, media-sound/pulseaudio, or something connected to Plasma.
Comment 1 Red 2019-09-27 19:55:03 UTC
Are you sure this should be marked no maintainer? It might be a media-sound/pulseaudio issue.
Comment 2 Igor V. Kovalenko 2022-06-18 07:40:57 UTC
(In reply to Red from comment #1)
> Are you sure this should be marked no maintainer? It might be a
> media-sound/pulseaudio issue.
This is not a pulseaudio issue since it is the consumer app which starts and keeps pulseaudio daemon alive. I suspect the app in question only works if pulsaudio access interface is shared to the user running the daemon. This is usually not done by default and requires manual configuration changes.