*** This bug is a duplicate of bug 1793640 ***
https://bugs.launchpad.net/bugs/1793640
** This bug has been marked a duplicate of bug 1793640
Pulseaudio fails to detect sound card, while timidity is installed
--
You received this bug notification because you are a member of Ubuntu
Touch
I finally posted on the pulseaudio list and someone referred me to this
bug:
https://bugs.launchpad.net/ubuntu/+source/timidity/+bug/1793640
I uninstalled timidity and that seems to have fixed the problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Yes, and it looks like you need to be a list member first.
you could register this list from:
https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in
So is the next step that I should post this to pulseaudio-
disc...@lists.freedesktop.org? Do I need to be a list member to post
there?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
User 'gdm' is normal and not a bug. That's the user which runs the login
screen.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1828136
Title:
[Intel DH67CL, Realtek
On my ubuntu 18.04 system I only have
/usr/bin/pulseaudio --start --log-target=syslog
owned by me. On my 19.04 system
/usr/bin/pulseaudio --daemonize=no
also owned by me. Note gdm is not running. I assume lightdm, which is
running, is the alternative.
--
You received this bug notification
my system is ubuntu 18.04. And from log ps:
The user of "/usr/bin/pulseaudio --daemonize=no" is gdm
The user of "/usr/bin/pulseaudio --start --log-target=syslog" is my
account.
If the user is differnt, I have no idea, maybe we should report the problem to
>From ps I see that "/usr/bin/pulseaudio --daemonize=no" is running with
user "adrian" and also my home directory is owned by "adrian".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
E: [autospawn] core-util.c: Home directory not accessible: Permission
denied
I printed out the "Home directory" on my computer, it is
/home/$my_account, and the USER of pulseaudio is $my_account too
(through ps -aux"), then there is no "Permission denied" problem.
In the pulseaudio, it will
I already posted the log file a.txt in its entirety. Here it is again:
D: [pulseaudio] conf-parser.c: Parsing configuration file '/etc/pulse/client.con
f'
E: [autospawn] core-util.c: Home directory not accessible: Permission denied
W: [autospawn] lock-autospawn.c: Cannot access autospawn lock.
On my machine, this is the log the pulseaudio find the sound card via
udev, could you find similar info in your a.txt?
D: [pulseaudio] module.c: Checking for existence of
'/usr/lib/pulse-11.1/modules/module-udev-detect.so': success
D: [pulseaudio] module-udev-detect.c: /dev/snd/controlC0 is
I forgot to mention that dpkg -S says:
libpulse0:amd64, libpulse0:i386: /etc/pulse/client.conf.d/00-disable-
autospawn.conf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
I looked around a bit and found ~/.config/pulse, a directory with
permission 700. Changed it to 777. That didn't make a difference.
Also found ~/.pulse with this contents:
12 -rw-r--r-- 1 adrian adrian 12288 Oct 7 2013
11597e2b32f1c4cb56501b9c0008-card-database.tdb
4 -rw-r--r-- 1 adrian
I removed the 00-disable-autospawn.conf file and rebooted. Then I get
a.txt containing this:
D: [pulseaudio] conf-parser.c: Parsing configuration file '/etc/pulse/client.con
f'
E: [autospawn] core-util.c: Home directory not accessible: Permission denied
W: [autospawn] lock-autospawn.c: Cannot
there is no client.conf.d/00-disable-autospawn.conf on my computer too.
And the pulseaudio usually sets "autospawn=yes" or "Restart=on-failure"
in the systemd.
Maybe you could delete 00-disable-autospawn.conf temporarily and do a
test, if it does not work, restore it.
And you could run "dpkg -S
I believe that I upgraded incrementally as new releases came out from
14.04. (Hard to recall for sure back that far.) But definitely I got to
18.10 from 18.04 to 18.04 from 17.10. And 18.04, I didn't have this
problem. In fact, I have a second machine that I'm "scared" to upgrade
that's still
This is something I never met before, this is the content of my
/etc/pulse/client.conf, and I can find the /tmp/a.txt after booting up.
Maybe this is the root cause of the problem you report, the pulseaudio
doesn't start as the 18.10 or 19.04, the pulseaudio still act as the
14.04. Did you upgrade
I followed the instructions but no log file was created.
I noticed in the man page for pulse-client.conf it says
extra-arguments= Extra arguments to pass to the PulseAudio daemon when
autospawning.
and in /etc/pulse/client.conf.d I see
autospan=no
I tried playing sound, running "alsa
Then edit /etc/pulse/client.conf, change the line "; extra-arguments =
--log-target=syslog" to "extra-arguments = - --log-
target=file:/tmp/a.txt".
reboot.
you will find the /tmp/a.txt, this is the pulseaaudio log, let us try to
find some clues from the log.
--
You received this bug
The before file was attached to the last comment. Here's the after file
from pactl.
** Attachment added: "postforce"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+attachment/5263010/+files/postforce
--
You received this bug notification because you are a member of
I rebooted, ran pactl list cards, ran alsa force reload, then re-ran the
pactl command. Results was as you predicted. The pactl outputs before
and after appear below.
Here's the before output:
Card #0
Name: alsa_card.pci-_01_00.1
Driver: module-alsa-card.c
Owner
I guess you alsa driver works after booing up, but the pulseaudio fails
to get your built in sound card via alsa-lib.
To check it, after booing up, run pactl list cards, I guess you could
only see one dummy card and one nvidia hdmi audio card; after sudo alsa
force-reload and run pactl list
I rebooted and went into the "Ubuntu" desktop and looked at the sound
settings. It shows an output tab and said "dummy". I clicked and was
able to switch it to the nvidia card. I think maybe the nvidia card was
off, which it should be since there's no output device connected.
I went back into
If I look at the sound settings using pavucontrol (I don't normally use
gnome and don't seem to have a program called gnome-sound-setting
installed) then under the configuration tab I see the nvidia hardware
but not the built in audio. (The nvidia card has only HDMI and my
speakers don't have
According to the log of ls and aply -l, your audio hardware is
recognized by the driver after booting up.
And alsa is ready to work, I can't find any problem here. I guess you
could run 'aplay test.wav' to play sound after booting up without "sudo
alsa force-reload"
you wrote "After rebooting I
Summary: looks to me like aplay -l is showing the intel hardware. No
adrian> ls -la /dev/snd
total 0
0 drwxr-xr-x 3 root root 320 May 9 18:07 ./
0 drwxr-xr-x 20 root root 5080 May 9 18:07 ../
0 drwxr-xr-x 2 root root 80 May 9 18:07 by-path/
0 crw-rw+ 1 root audio 116,
After booting up, please run:
ls -la /dev/snd/ #could you see some dev nodes
aplay -l # could you see some audio devices
sudo chmod a+rw /dev/snd/*
aplay -l # could you see some different output from the 1st time.
--
You received this bug notification because you are a member of Ubuntu
Yeah, kernel bugs have a slightly different process regarding
"Confirmed".
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I ran the "apport-collect 1828136" command as directed by the automated
script. A little puzzled that it gave the message
dpkg-query: no packages found matching alsa-driver
dpkg-query: no packages found matching linux
--
You received this bug notification because you are a member of Ubuntu
The automated script said I should change the status to "confirmed" even
though I am the reporter.
When 18.10 came out some other people reported similar issues:
https://ubuntuforums.org/showthread.php?t=2403077
https://ubuntuforums.org/showthread.php?t=2405764
--
You received this bug
apport information
** Tags added: apport-collected
** Description changed:
After rebooting I have no sound. My sound device doesn't show up at all
in the mixer.
Running "sudo alsa force-reload" corrects the problem, until the next
reboot.
This problem started in 18.10 and
Sorry, yes, while that problem is shown in the attached files it does
sound irrelevant now.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
Added a kernel task because our kernel engineers are experts at such
ALSA issues. And often the solution lies in the kernel.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
I repeat, immediately after a reboot, audacity is not running. Are you
saying that audacity can prevent the system from recognizing my sound
hardware at boot just from being installed?
At the moment, sound works despite the audacity's configuration because
I ran "alsa force-reload'.
--
You
The attached file AudioDevicesInUse.txt suggests that 'audacity' is
stealing the hardware device from pulseaudio -- bypassing it.
If that is the issue then it's unfortunately not a bug. You need to be
sure that all audio software (including audacity) is configured to use
PulseAudio only, and not
I'm a little confused here. What does audacity have to do with the fact
that there is no sound after a reboot? Audacity happens to be running
now...perhaps that's why it's the only program using ALSA. (Is ALSA
deprecated?) But audacity does not start automatically at boot, so it
is irrelevant
It appears 'audacity' is the exclusive user of /dev/snd/seq according to
your AudioDevicesInUse.txt.
Please try:
1. Reconfiguring Audacity to use PulseAudio and not ALSA or OSS.
2. Uninstalling 'audacity'.
** Summary changed:
- [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
+
37 matches
Mail list logo
