@David:
can you please tell me why Phonon/Xine still depends on asoundrc.conf for the
plugin configuration? After the last update of KDE environment, Amarok
(phonon/xine) didn't recognize pulseaudio plugin/device any more and I had to
force its recognition adding these lines to the
can you please tell me why Phonon/Xine still depends on asoundrc.conf for the
plugin configuration? After the last update of KDE environment, Amarok
(phonon/xine) didn't recognize pulseaudio plugin/device any more and I had to
force its recognition adding these lines to the configuration
Yes, this is the point. And it seems to be difficult to have an ACER
ASPIRE 6920G properly configured out-of-the-box without doing some trick
and manually configuring them... Maybe it's only my problem (because as
you said I compiled last src version and I didn't rely on deb system),
but I can
If you compile your own PulseAudio, you get to handle all the bugs
associated with it. Please don't file bugs about default Ubuntu
systems unless you're actually using the versions of programs as
distributed from the Ubuntu repository. :-)
With Phonon, it is a well-known issue that because
Frankly, the way forward is for you to test the most current live cd
of Lucid to reproduce your issue:
http://cdimage.ubuntu.com/daily-live/current/
--
[regression] After Karmic Update integration ALSA+PULSEAUDIO is problematic
https://bugs.launchpad.net/bugs/478014
You received this bug
I'm running Karmic currently, and have youtube videos playing through
PulseAudio.
When I say properly configure alsa drivers I mean (with Karmic Koala):
1. Installing latest alsa drivers
2. Letting alsa recognize my audio card (adding proper option in alsa
configuration file)
3. Using
Does doing something basically mean not passing by DEB, but compiling
and installing files by myself? Could you tell me what's wrong in my
procedure? I think compiling/installing software should be supported as
well... I think I am pretty sure that also the backports installation
with cooked DEB
Could you tell me what's wrong in my procedure?
Any of the three points could have caused the error. All I'm saying is
that since this works properly for most people (if it didn't, we would
have seen many more bugs of this kind), so from what I know now, it is
not an Ubuntu bug.
I'm sorry I
I tried you scenario and, as expected, AMAROK (2.3) didn't play anything
because audio was stolen by the flash player. Once I close firefox amarok wakes
up and plays a short piece of the music, thus stopping. Afterthat i can
successfully play the song clicking on play button.
Now I rebooted
When I say properly configure alsa drivers I mean (with Karmic Koala):
1. Installing latest alsa drivers
2. Letting alsa recognize my audio card (adding proper option in alsa
configuration file)
3. Using Alsaconf to properly choose hda-intel audio card
this shall be enough to configure the
Just to verify that your assumption is correct, please do the following:
* Make sure you have no .asoundrc.asoundconf and no .asoundrc files in your
home directory (delete them or back them up)
* Logout and login again
* Reproduce the bug (by starting youtube first, then Amarok)
* enter this
Sorry to disturb you again and poll the status of this bug, but you said:
We removed asoundconf from alsa-utils precisely because it will create
alsa-lib configurations that cause the sorts of problems you're experiencing
with PulseAudio.
Now, if I PROPERLY configure ALSA DRIVERS and
so, any news from there?
--
[regression] After Karmic Update integration ALSA+PULSEAUDIO is problematic
https://bugs.launchpad.net/bugs/478014
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
@Daniel T Chen
Your ~/.asoundrc* is obsolete and actually conflict with PulseAudio. Please
remove it.
how can it be obsolete if I performed a fresh Koala Karmic install and a
fresh ALSA DRIVERS update? Is it maybe because I applied a workaround to
fix PulseAudio locking problem described in my
We removed asoundconf from alsa-utils precisely because it will create
alsa-lib configurations that cause the sorts of problems you're experiencing
with PulseAudio.
So, yes, in your haste to apply a dodgy workaround (instead of filing bugs
against the sound applications), you've created a
Ok, but right now issue is solved and my machine works flawlessly.Now,
what about solving the bug?
--
[regression] After Karmic Update integration ALSA+PULSEAUDIO is problematic
https://bugs.launchpad.net/bugs/478014
You received this bug notification because you are a member of Ubuntu
Bugs,
without my workaround:
if I just select 'Pulseaudio' as preferred in Gnome-Audio panel and
using alsaconf... SOME APPLICATION STILL USES ALSA AND NOT PULSEAUDIO.
For instance it happens for the flash codec, while I am watching a video on
youtube:
- I start youtube first: then any other
I'm using Ubuntu Karmic, and I have noticed some PulseAudio problems as
well. The latest issue being on every restart, the volume is reset down
too low and when you view the Sound Preferences, it says applications
are using ALSA instead of PulseAudio for some reason. Yet PulseAudio is
still
@Hephaestus Malleus
Please see https://wiki.ubuntu.com/PulseAudio/Log
--
[regression] After Karmic Update integration ALSA+PULSEAUDIO is problematic
https://bugs.launchpad.net/bugs/478014
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Daniel, I've attached the PulseAudio log. I hope the audio issues can
be resolved.
** Attachment added: pulseverbose.log
http://launchpadlibrarian.net/35390874/pulseverbose.log
--
[regression] After Karmic Update integration ALSA+PULSEAUDIO is problematic
@Hephaestus Malleus
In your case, it's fairly straightforward; some other applications has
grabbed the sound device:
...
I: (alsa-lib)setup.c: Cannot lock ctl elem
I: (alsa-lib)setup.c: Cannot lock ctl elem
I: (alsa-lib)setup.c: Cannot lock ctl elem
I: (alsa-lib)setup.c: Cannot lock ctl elem
D:
I've attached the results from this command 'sudo fuser -v /dev/dsp* /dev/snd/*
/dev/seq*'
But I'm still not sure what exactly is causing the conflict between ALSA and PA.
** Attachment added: fuser-results
http://launchpadlibrarian.net/35391663/fuser-results
--
[regression] After Karmic
@Hephaestus Malleus
Please just file a separate bug using ubuntu-bug alsa-base. Most
likely you have a misconfigured asoundrc and/or misconfigured ALSA
app.
--
[regression] After Karmic Update integration ALSA+PULSEAUDIO is problematic
https://bugs.launchpad.net/bugs/478014
You received this bug
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/35344246/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/35344247/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/35344248/ArecordDevices.txt
Your ~/.asoundrc* is obsolete and actually conflict with PulseAudio.
Please remove it.
--
[regression] After Karmic Update integration ALSA+PULSEAUDIO is problematic
https://bugs.launchpad.net/bugs/478014
You received this bug notification because you are a member of Ubuntu
Bugs, which is
25 matches
Mail list logo
