Bug 16638

Summary:	pulseaudio killed on X11 logout & not restarted on login
Product:	Mageia	Reporter:	Marc Krämer <mageia>
Component:	RPM Packages	Assignee:	Colin Guthrie <mageia>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11
Version:	5	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	systemd-217-11.mga5 pulseaudio-5.0-6.mga5.x86_64	CVE:
Status comment:

Description Marc Krämer 2015-08-24 14:46:18 CEST

If you logout from your desktop session & relogin (e.g. LXDE) pulseaudio is not running anymore, so volumecontrol is missing.
You can also try to start "pactl" but it will state, no connection available.
It gets available again after starting "pulseaudio"

Reproducible: 

Steps to Reproduce:

Comment 1 Marja Van Waes 2015-08-24 19:49:37 CEST

@ M K

please test whether this bug is valid in text mode, too, like a similar (now fixed) cauldron bug was

See Jani's comments in bug 16345

16345#7:

> I can reproduce this even without X:
> 
> 1. Boot to text mode
> 2. Login as normal user
> 3. mplayer foo.mp3
> 4. Logout + re-login with same user
> 5. mplayer foo.mp3 and no sound.
> 
> After killing all leftover processes from previous session shown by
> 'loginctl session-status $ID' [1] (at least gpg-agent for me) and logging
> out + re-login, sound is working again.
> 
> [1] You can get $ID with 'loginctl' cmd.

Keywords: (none) => NEEDINFO
CC: (none) => marja11
Assignee: bugsquad => mageia
Summary: pulseaudio killed on X11 logout & restarted on login => pulseaudio killed on X11 logout & not restarted on login
Source RPM: pulseaudio-5.0-6.mga5.x86_64 => systemd-217-11.mga5 pulseaudio-5.0-6.mga5.x86_64

Comment 2 Marc Krämer 2015-08-25 12:32:47 CEST

if I boot to text mode I don't get any audio ever.
Sorry for asking, but what happens to start pulseaudio on text mode for you?

In X the startup process should start pulseaudio. On logout X is shutdown, so pulseaudio gets killed, but is not restarted on logon.

Comment 3 Marja Van Waes 2017-09-20 09:55:22 CEST

Is this bug still valid?

Comment 4 Marc Krämer 2018-01-04 19:26:58 CET

I'll close my bug. I haven't had this issue for some time.

Status: NEW => RESOLVED
Resolution: (none) => OLD