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 pac
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.
https://bugs.launch
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 Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launch
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.
E:
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.
https://bugs.launchpad.net/bug
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 acc
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 ru
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 Ubun
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 Modu
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 m
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 that
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,
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
Touc
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 Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https:/
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 Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchp
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 Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubu
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 Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubunt
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 Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bug
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 notific
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 Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://b
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 Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad
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 Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad
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 Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
htt
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 Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://b
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 Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.n
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 persis
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 rece
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 t
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
Package
I'm also seeing this artifact again in Ubuntu 16.04, libgtk-3-0
3.18.9-1ubuntu3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1508357
Title:
Tooltips have a black squares
-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mariano1348 F pulseaudio
Date: Sat Feb 27 21:28:51 2016
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with
return code 2
HibernationDevice: RESUME=UUID=7d444ceb-3f27-45df
Sending files from notebook (Ubuntu 14.04) to smartphone (SG2, Android
4.1.2) worked yesterdays, does not today. Sending files now produces the
error message in the subject. Nothing on the system was changed.
Running the command bluez-simple-agent produces this:
> user@box:~$ bluez-simple-agent
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 logi
36 matches
Mail list logo
