Bug 14995

Summary: Pulseaudio unable to contact D-Bus
Product: Mageia Reporter: Jüri Ivask <jyri2000>
Component: RPM PackagesAssignee: Colin Guthrie <mageia>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: Normal    
Version: Cauldron   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:

Description Jüri Ivask 2015-01-09 14:07:35 CET 
Description of problem: Pulseaudio unable to contact D-Bus


Version-Release number of selected component (if applicable):


How reproducible: After last dbus updates there is no audio in Plasma 5 desktop and in applicatlions like VLC or Skype etc - pulseaudio is not running.

Attempt to start it from command line gives:
W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Reproducible: 

Steps to Reproduce:
Comment 1 Colin Guthrie 2015-01-09 14:29:11 CET 
I think this has already been reported no?

I am aware of this and have been working on patches to other areas of the stack for some time, so this might be solved or reverted to previous behaviour depending on what seems best.

*** This bug has been marked as a duplicate of bug 14709 ***

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

Comment 2 Jüri Ivask 2015-01-09 14:53:39 CET 
No sure... It happened after last two dbus updates (1.8.14 (security hardening)) until that sound worked OK.
Comment 3 Colin Guthrie 2015-01-09 17:21:01 CET 
(In reply to Jüri Ivask from comment #2)
> No sure... It happened after last two dbus updates (1.8.14 (security
> hardening)) until that sound worked OK.

Hmm, it very much should have been in place for a long time now... basically back in October.

http://svnweb.mageia.org/packages?view=revision&revision=791791

Are you certain it only started happening recently? Or did you perhaps just not reboot for a long time?
Comment 4 Jüri Ivask 2015-01-10 08:03:17 CET 
Hmm... It's a laptop so the speakeres are always on and I shutdown/restart it at least daily. And I remember Skype (using exclusively pulseaudio) playing startup sound recently... Any chance to get the pre-security hardening dbus rpm for a test?
Comment 5 Jüri Ivask 2015-01-12 10:20:38 CET 
As of today morning I cannot reproduce it any more - pulseaudio seems to work ok now. Some anomaly in services initialisation? Sorry for a confusion...
Comment 6 Colin Guthrie 2015-01-12 10:26:51 CET 
It's definitely, 100% an issue. I know it is! Unless something else is starting your pulseaudio daemon outside of socket activation (which it certainly shouldn't) then PA should be started in an environment isolated from dbus and unable to connect to it.

If PA can talk to dbus on your system (and I mean the session dbus here, not the system dbus).

Anyway, I now see that you had bigger problems than just what's reported. Normally the dbus issue is actually non-fatal but I see it was indeed fatal to you.

So I don't think this actually is a duplicate of the other issue (sorry for not seeing it properly on first reading - I just saw "PA + DBus" and jumped to the known issue).

Anyway, I'll unmark it as a duplicate, but you'll find there are still dbus related issues :D

Status: RESOLVED => UNCONFIRMED
Resolution: DUPLICATE => (none)
Ever confirmed: 1 => 0

Comment 7 Colin Guthrie 2015-01-12 10:27:07 CET 
Resolving as WFM as per comment 5

Status: UNCONFIRMED => RESOLVED
Resolution: (none) => WORKSFORME

Comment 8 Colin Guthrie 2015-01-12 10:27:58 CET 
(comments above were poorly written - should have trimmed the first couple paragraphs as I re-read the bug properly! sorry for further confusion!)