Your message dated Wed, 23 Apr 2014 09:57:47 -0300
with message-id 
<CAAfdZj-AFv_ng7eSuKX+-DPLsweAoBWv+1rpkvJ72tOmW=b...@mail.gmail.com>
and subject line Re: Bug#712959: Same here
has caused the Debian Bug report #712959,
regarding pulseaudio: No sound after upgrade on 20th June 2013
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
712959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712959
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: pulseaudio
Version: 4.0-3
Severity: normal

Dear Maintainer,

After upgrade to my sid system yesterday sound has stopped working.

If I type pulseaudio on a terminal it does say it is running - thus:-

alan@kanga:~$ pulseaudio
E: [pulseaudio] pid.c: Daemon already running.
E: [pulseaudio] main.c: pa_pid_file_create() failed.
alan@kanga:~$ 


I checked with alternative system (linux mint) and sound is working perfectly 
on that.

I have an standard intel motherboard with audio chip on the motherboard.  I am 
not sure precisely
which - alsamixer reports chip as Intel CougarPoint HDMI


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages pulseaudio depends on:
ii  adduser                       3.113+nmu3
ii  consolekit                    0.4.5-3.1
ii  libasound2                    1.0.27.1-1
ii  libasound2-plugins            1.0.27-2
ii  libc6                         2.17-5
ii  libcap2                       1:2.22-1.2
ii  libdbus-1-3                   1.6.12-1
ii  libfftw3-single3              3.3.3-5
ii  libgcc1                       1:4.8.1-3
ii  libice6                       2:1.0.8-2
ii  libltdl7                      2.4.2-1.2
ii  liborc-0.4-0                  1:0.4.17-2
ii  libpulse0                     4.0-3
ii  libsamplerate0                0.1.8-5
ii  libsm6                        2:1.2.1-2
ii  libsndfile1                   1.0.25-5
ii  libspeexdsp1                  1.2~rc1-7
ii  libstdc++6                    4.8.1-3
ii  libsystemd-login0             44-12
ii  libtdb1                       1.2.10-2
ii  libudev0                      175-7.2
ii  libwebrtc-audio-processing-0  0.1-2
ii  libx11-6                      2:1.6.0-1
ii  libx11-xcb1                   2:1.6.0-1
ii  libxcb1                       1.9.1-3
ii  libxtst6                      2:1.2.1-1+deb7u1
ii  lsb-base                      4.1+Debian12
ii  udev                          175-7.2

Versions of packages pulseaudio recommends:
ii  gstreamer0.10-pulseaudio  0.10.31-3+nmu1
ii  pulseaudio-module-x11     4.0-3
ii  rtkit                     0.10-2

Versions of packages pulseaudio suggests:
pn  paman             <none>
pn  paprefs           <none>
ii  pavucontrol       1.0-1
pn  pavumeter         <none>
ii  pulseaudio-utils  4.0-3

-- no debconf information

--- End Message ---
--- Begin Message ---
On Wed, Apr 23, 2014 at 3:43 AM, Alan Chandler
<[email protected]> wrote:
> On 23/04/14 00:12, Felipe Sateler wrote:
>>
>> 2014-04-21 6:20 GMT-03:00 Mario J. Barchéin Molina
>> <[email protected]>:
>>>
>>> Hello:
>>>
>>> I have uninstalled (purged) "speech-dispatcher" and everything is working
>>> fine now. If you want, I can reinstall it and run the test later.
>>
>> If everything is working fine then this would be a duplicate of bug
>> 521675. I'l wait for Alan to reply, otherwise I'm going to close this
>> issue because it is a duplicate.
>>
>>
>>
> Shortly after I submitted the bug, I downgraded my system to Debian stable
> as I needed more stability for my working environment, and sound has always
> worked fine for me after that.
>
> So don't wait on me

Thanks for your reply.

If you see issues when you upgrade again, please file a new bug report.

I'm closing this bug.


-- 

Saludos,
Felipe Sateler

--- End Message ---

Reply via email to