Bug 16345 - pulseaudio may become inoperational after a series of steps involving login/logout.
Summary: pulseaudio may become inoperational after a series of steps involving login/l...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2015-07-11 11:54 CEST by Shlomi Fish
Modified: 2015-08-08 20:21 CEST (History)
4 users (show)

See Also:
Source RPM: systemd
CVE:
Status comment:


Attachments

Description Shlomi Fish 2015-07-11 11:54:12 CEST
Description of problem:

pulseaudio may become inoperational and unusable after a series of the following steps:

#. Enable PulseAudio in draksound.

#. Reboot while making sure that a display manager does not start by default. 

#. After reboot login from the virtual terminal (VT) as a normal user.

#. Play a sound file using mplayer (possibly while using -novideo).

#. Login as root from a different VT and play a sound file using mplayer.

#. Keep the root VT running.

#. As the normal user, start X and XFCE (one can put "startxfce4" in XFCE for that)

#. On XFCE, play a file using VLC.

#. Exit XFCE.

#. Exit the normal user.

# Login back as the normal user from the VT.

#. Try playing a file using mplayer - it no longer works.

============

Regards,

-- Shlomi Fish

Reproducible: 

Steps to Reproduce:
Comment 1 Marja Van Waes 2015-07-11 20:49:15 CEST
Hi Shlomi :-)

Today's corner case award goes to you ;-)

However, I would very much like to know why this happens, too!

Please read https://wiki.mageia.org/en/Support:DebuggingSoundProblems
for a lot of information on how to debug sound issues and do anything that seems applicable.

I don't know what XFCE all does, when it's being closed, CC'ing wally in case he knows why this happens, even without getting more information.

Keywords: (none) => NEEDINFO
CC: (none) => jani.valimaa, mageia, marja11

Comment 2 Shlomi Fish 2015-07-11 21:46:42 CEST
Hi Marja!

(In reply to Marja van Waes from comment #1)
> Hi Shlomi :-)
> 
> Today's corner case award goes to you ;-)
> 

It makes me very proud. :-).

> However, I would very much like to know why this happens, too!
> 
> Please read https://wiki.mageia.org/en/Support:DebuggingSoundProblems
> for a lot of information on how to debug sound issues and do anything that
> seems applicable.
>

There's quite a lot of text (and some links) there. What am I looking for exactly there?

Regards,

-- Shlomi Fish

 
> I don't know what XFCE all does, when it's being closed, CC'ing wally in
> case he knows why this happens, even without getting more information.
Comment 3 Marja Van Waes 2015-07-11 23:09:00 CEST
(In reply to Shlomi Fish from comment #2)

> 
> It makes me very proud. :-).

\o/

> 
> > However, I would very much like to know why this happens, too!
> > 
> > Please read https://wiki.mageia.org/en/Support:DebuggingSoundProblems
> > for a lot of information on how to debug sound issues and do anything that
> > seems applicable.
> >
> 
> There's quite a lot of text (and some links) there. What am I looking for
> exactly there?
> 

I don't know, I know near to nothing about sound. However, Colin is smart and a sound expert and all information in that page comes from him.

Maybe running (from  
https://wiki.mageia.org/en/Support:DebuggingSoundProblems#Useful_tools_and_commands ):
2. "ps aux | grep pulseaudio" will check that PulseAudio is running. 
3. "pactl stat" will check that you can connect to the PulseAudio daemon correctly. 
6 "pacmd ls" will give you a LOT of debug information about the current state of your audio. 
7. "/usr/sbin/lsmod | grep snd" will enable you to check which sound related kernel modules (drivers) are loaded. 

and seeing whether there's something different between when sound works and when it doesn't.
Comment 4 Jani Välimaa 2015-07-12 08:50:32 CEST
This is happening most probably because of new systemd 222 + lightdm combo. However, it would be nice to hear if this is happening also with other DMs.

There's this thread in systemd-devel ml:
http://lists.freedesktop.org/archives/systemd-devel/2015-July/033464.html

It was also cross-posted to lightdm ml:
http://lists.freedesktop.org/archives/lightdm/2015-July/000813.html
Jani Välimaa 2015-07-12 08:51:08 CEST

Source RPM: task-pulseaudio-2011.0-6.mga5.src.rpm => systemd or lightdm

Comment 5 Jani Välimaa 2015-07-12 09:06:48 CEST
I can reproduce this with xfce + lightdm. Simple login + re-login is enough, no need to play any sound.

If you check 'loginctl session-status' output after the second login, you'll see that the state of the session is "Closing" and it's not right. IIUC it's happening because of the leftover processes from the previous login/session.

If you kill all leftovers before new session, then everything works OK.
Comment 6 Shlomi Fish 2015-07-12 11:25:33 CEST
(In reply to Jani Välimaa from comment #5)
> I can reproduce this with xfce + lightdm. Simple login + re-login is enough,
> no need to play any sound.
> 
> If you check 'loginctl session-status' output after the second login, you'll
> see that the state of the session is "Closing" and it's not right. IIUC it's
> happening because of the leftover processes from the previous login/session.
> 
> If you kill all leftovers before new session, then everything works OK.

Jani, I'm not running lightdm or any other display manager. I'm using startx to start XFCE.
Comment 7 Jani Välimaa 2015-07-12 12:23:39 CEST
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.

Source RPM: systemd or lightdm => systemd

Florian Hubold 2015-07-12 16:31:43 CEST

CC: (none) => doktor5000

Comment 8 Jani Välimaa 2015-08-08 17:16:43 CEST
I can't reproduce this anymore with systemd 224.
Comment 9 Shlomi Fish 2015-08-08 20:21:22 CEST
(In reply to Jani Välimaa from comment #8)
> I can't reproduce this anymore with systemd 224.

Yes. Seems to be OK - RESOLVEing as FIXED.

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


Note You need to log in before you can comment on or make changes to this bug.