*** This bug is a duplicate of bug 320875 ***
https://bugs.launchpad.net/bugs/320875
On Ubuntu 12.04.3, I'm seeing
[alsa-source] alsa-source.c: ALSA woke us up to read new data from the device,
but there was actually nothing to read!
[alsa-source] alsa-source.c: Most likely this is a bug
*** This bug is a duplicate of bug 320875 ***
https://bugs.launchpad.net/bugs/320875
Hi
This bug is there in Ubuntu 11.04 . So let's celebrate 2 year
Anniversary
Regards,
Vipin Balakrishnan.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 320875 ***
https://bugs.launchpad.net/bugs/320875
Hi All,
This Bug is there very badly in Ubuntu 10.04 LTS. I dont know why
nobody is intereseted to fix.
Regards,
Vipin Balakrishnan.
--
ALSA woke us up to write new data to the device, but there was
*** This bug is a duplicate of bug 320875 ***
https://bugs.launchpad.net/bugs/320875
I am also receiving these mesages in syslog. My alsa-info.sh output is
locate at http://www.alsa-
project.org/db/?f=3cc84abd1b4be1ec90a385aa93c4c010cccf43fc . I already
have load-module module-hal-detect
*** This bug is a duplicate of bug 320875 ***
https://bugs.launchpad.net/bugs/320875
** This bug has been marked a duplicate of bug 320875
pulseaudio produces lots of log messages
--
ALSA woke us up to write new data to the device, but there was actually nothing
to write.
This appeared in my pc after upgrading to 9.04 alpha 5.
LOTS of identical entries in my syslog.
Is there some progress?
Can I help somehow?
My result of alsa debugging script: http://tinyurl.com/asc8mz
--
ALSA woke us up to write new data to the device, but there was actually nothing
to write.
I'm getting the same problem in 9.04 and floods of logs about it.
ALSA woke us up to write new data to the device, but there was actually
nothing to write! Most likely this is a Linux bug. Please report this
issue to the ALSA developers. We were woken up with POLLOUT set --
however a subsequent
Try adding tsched = 0 to /etc/pulse/default.pa under the hal-detect
module. More info at the end of this article:
http://fedoraproject.org/wiki/Features/GlitchFreeAudio
It fixed my audio problems and the messages. Clearly it's exposing a
bug somewhere.
--
ALSA woke us up to write new data to
** Attachment added: user.log
http://launchpadlibrarian.net/22640876/user.log
** Description changed:
Hello everyone,
I was going over my log messages and found out this entry appears a few
times in the user.log file:
Feb 14 19:08:05 LaptopLinux pulseaudio[21013]:
** Description changed:
Hello everyone,
I was going over my log messages and found out this entry appears a few
times in the user.log file:
Feb 14 19:08:05 LaptopLinux pulseaudio[21013]: module-alsa-sink.c: ALSA woke
us up to write new data to the device, but there was actually
Please run the alsa-info.sh debugging script from http://www.alsa-
project.org/alsa-info.sh
** Changed in: linux (Ubuntu)
Sourcepackagename: alsa-driver = linux
Status: New = Incomplete
--
ALSA woke us up to write new data to the device, but there was actually nothing
to write.
Here it is
** Attachment added: alsa-info.txt
http://launchpadlibrarian.net/22641238/alsa-info.txt
--
ALSA woke us up to write new data to the device, but there was actually nothing
to write.
https://bugs.launchpad.net/bugs/329620
You received this bug notification because you are a member
I think I am hittingBug #326693
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/326693). I too
realized that I can not get sound when glxgears is running.
--
ALSA woke us up to write new data to the device, but there was actually nothing
to write.
https://bugs.launchpad.net/bugs/329620
Forget what I just said about glxgears
--
ALSA woke us up to write new data to the device, but there was actually nothing
to write.
https://bugs.launchpad.net/bugs/329620
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
14 matches
Mail list logo
