After upgrade to Ubuntu14.04 the sound device is broken. There is only a
dummy output available. Ubuntu12.04 worked fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933209
Title:
No sound after s
I had the same issue. This solved it:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/908751/comments/4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933209
Title:
No sound after startup (
no audio
** Attachment added: "Screenshot from 2012-04-14 13:54:33.png"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/933209/+attachment/3096187/+files/Screenshot%20from%202012-04-14%2013%3A54%3A33.png
--
You received this bug notification because you are a member of Ubuntu
Bugs
I'm marking this as invalid (for alsa-driver, not for dbus) based on the
original reporter's feedback - if you're not having the same dbus
problems, please file a new bug instead. Thanks.
** Changed in: alsa-driver (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notificatio
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dbus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933209
Title:
No sou
** Package changed: ubuntu => dbus (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933209
Title:
No sound after startup (audio device shown as Dummy Output)
To manage notifications about thi
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dbus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933209
Title:
No sou
** Project changed: dbus => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933209
Title:
No sound after startup (audio device shown as Dummy Output)
To manage notifications about this bug go
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933209
Title:
No sound afte
** Project changed: null => dbus
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933209
Title:
No sound after startup (audio device shown as Dummy Output)
To manage notifications about this bug go to
Yes, that's helpful. This one seems to be the first sign of failure:
> dbus[625]: [system] Failed to activate service
'org.freedesktop.ConsoleKit': timed out
Without consolekit, PulseAudio won't have access to sound cards.
Second, this:
> pulseaudio[1075]: [pulseaudio] server-lookup.c: Unable t
If it matters, the lines below were added to /var/log/syslog after kill
pulseaudio (new process is 3404)
Apr 12 11:41:30 user-laptop rtkit-daemon[1077]: Successfully made thread 3397
of process 1758 (n/a) owned by '1000' RT at priority 5.
Apr 12 11:41:30 user-laptop rtkit-daemon[1077]: Supervisin
I noted that pulseaudio is started by 106 on startup, is this normal?
After the kill it is started by my userid:
user 3404 4.2 0.1 399304 5576 ?Shttps://bugs.launchpad.net/bugs/933209
Title:
No sound after startup (audio device shown as Dummy Output)
To manage notifications about
I also tried to hunt down the errant process (using the idea from
http://askubuntu.com/questions/25622/my-sound-stopped-working-today-how-
can-i-fix-it):
user@user-laptop:~/Desktop$ sudo fuser -f /dev/snd/*
/dev/snd/controlC0: 1075
/dev/snd/pcmC0D0p:1075m
user@user-laptop:~/Desktop$ ps aux |
This is what I see when I had to do a killall, I thought the pcm devices
are interfering but they seem to be started again after the killall,
with sound playing.
/dev/snd/controlC0: 11048
/dev/snd/pcmC0D0c: 11048m
/dev/snd/pcmC0D0p: 11048m
user@user-laptop:~/Desktop/Support/r8168-8.027.00$ su
Could you see if it's possible to run "sudo fuser -v /dev/snd/*" right
after startup, or maybe switch to a VT and execute it there? With some
luck we might catch the offending application.
** Changed in: alsa-driver (Ubuntu)
Status: Confirmed => Incomplete
** Project changed: pulseaudio =>
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: alsa-driver (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933209
Title:
nope, no sound in login session. I do hope this gets fixed (I agree it
is probably a matter of looking into the right places) even though the
crude workaround is available
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
My suspicion about this is that, at startup, some other program (i e,
not pulseaudio) is locking the sound card. As a result, pulseaudio does
not detect the card correctly.
Not sure how to figure this out in the best way though.
What about the login session (lightdm/gdm/etc) - does sound work the
** Description changed:
(testing from the ubuntu audio dev ppa)
-
- Running sudo alsa force-reload seems to be current workaround to get it
- to work
-
+ Running sudo alsa force-reload (or sudo killall pulseaudio) seems to be
+ current workaround to get it to work
hardware info (when s
recently discovered that `sudo killall pulseaudio` seems to get the
sound back somehow. Not sure if problem lies with pulseaudio or alsa-
driver
** Also affects: pulseaudio
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933209
Title:
No sound after startup (audio device shown as Dummy Output)
To manag
added pulseaudio log (following the steps to produce the log actually
got the sound working)
** Attachment added: "pulseverbose.log"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/933209/+attachment/2747510/+files/pulseverbose.log
--
You received this bug notification because you
apport information
** Tags added: apport-collected precise
** Description changed:
(testing from the ubuntu audio dev ppa)
Running sudo alsa force-reload seems to be current workaround to get it
to work
hardware info (when sound is working):
Code:
00:1b.0 Audio device: In
Please run apport-collect 933209 so we can get some information about
your hardware, preferably before you reload ALSA to get audio working
again.
Please also get a log from PulseAudio:
https://wiki.ubuntu.com/PulseAudio/Log.
** Changed in: alsa-driver (Ubuntu)
Status: New => Incomplete
-
25 matches
Mail list logo
