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 Desktop
Packages,
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 Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
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
>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 Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
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.
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 Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1828136
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
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
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
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 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
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,
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262477/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262473/+files/CRDA.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262480/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262481/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262478/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
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 Desktop
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262475/+files/Lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262479/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262476/+files/Lsusb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in 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
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262482/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Attachment added: "AudioDevicesInUse.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262472/+files/AudioDevicesInUse.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262474/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
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
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
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
Public bug reported:
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 persists now in 19.04.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
I have updated the BIOS. After this update the problem no longer
occurs.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in
Public bug reported:
I recently updated my Ubuntu version. Before it was working generally
(though I did experience a sporadic crash---don't know if that was
related).
Now after updates the log in display appears but when I attempt to
actually log in the screen clears to black, and then the
I get the same error when running the trackballs program, which might
be easier to investigate since it's freely available.
Is there anything else I can do to shed light on this? Additional
tests I could run? Problem is 100% repeatable.
--
You received this bug notification because you are a
root# dpkg -S gs_fonts.ps
libgs9-common: /usr/share/ghostscript/9.10/Resource/Init/gs_fonts.ps
root# dpkg -l | grep libgs9-common
ii libgs9-common9.10~dfsg-0ubun all interpreter for the
PostScript language and f
root# dpkg -l | grep libgs9-common
ii libgs9-common
Why wouldn't sudo apt-get install package install all of the package's
dependencies? I didn't want to potentially install a bunch of extra
stuff from -proposed. I vaguely recall that when I upgraded ghostscript
that it did in fact install some other things.
--
You received this bug
I'm a little confused. I reverted my patch to
/usr/share/ghostscript/9.10/Resource/Init/gs_fonts.ps and then I
installed the proposed package, I think.
[code]
% dpkg -l | grep ghost
ii ghostscript 9.10~dfsg-0ubuntu10.1 amd64
interpreter for the
Public bug reported:
When searching for fonts ghostscript issues the error Error: /typecheck
in /findfont: and aborts.
This appears to be a bug in ghostscript having to do with .woff files.
http://bugs.ghostscript.com/show_bug.cgi?id=695031
I applied the patch given above and it fixed the
Public bug reported:
I'm trying to run a game called braid. I previously ran this game
successfully under 12.04 with my nVidia card using the proprietary
drivers, and I have also run it under 13.10 on a different box with a
different nVidia card. Now with 14.04 intel graphics finally actually
When I tried to create the requested log, the sound wasn't working at
all. I rebooted...and then X wasn't working. The dust has settled now
and the sound bug seems to be fixed (after persisting through several
reboots and lasting for a couple months) so I guess the bug should be
closed.
--
You
Public bug reported:
I have used this USB mic (part of a webcam) for years under linux and it
has worked fine. Some recent changes seem to have broken it, and it has
never worked under 13.04.
Note also that today when I decided to try to report the bug the
behavior was a little different than
42 matches
Mail list logo
