On Mon, Apr 21, 2014 at 8:08 AM, Kevin Martin <ktmdms(a)gmail.com> wrote:
On 04/19/2014 12:02 PM, Tom London wrote:
> On Sat, Apr 19, 2014 at 9:49 AM, Tom London <selinux(a)gmail.com <mailto:
selinux(a)gmail.com>> wrote:
>
> On Sat, Apr 19, 2014 at 9:47 AM, Clyde E. Kunkel <
clydekunkel7734(a)verizon.net <mailto:clydekunkel7734@verizon.net>> wrote:
>
> On Sat, 19 Apr 2014 12:45:10 -0400
> "Clyde E. Kunkel" <clydekunkel7734(a)verizon.net <mailto:
clydekunkel7734(a)verizon.net>> wrote:
>
> > On Sat, 19 Apr 2014 09:32:00 -0700
> > Tom London <selinux(a)gmail.com <mailto:selinux@gmail.com>>
wrote:
> > <snip>>
> > May be a red herring.  The file does not exist on  my
machine booted
> > with kernel-3.14.
>
> Apologies for not deleting majority of msg in my previous reply.
> --
>
>
> Not sure I understand: which file? My report was about a deadlock
triggered by pulseaudio process causing a "hung process".
>
>
>
> BZ'ed here:
https://bugzilla.redhat.com/show_bug.cgi?id=1089488
>
>
>
> --
> Tom London
>
>
Tom,
You could try *not having pulseaudio installed. I finally gave up on
pulseaudio and run as close to a strict alsa setup as I can
and don't have many of the issues that I once had. My installed "audio"
rpms are:
pulseaudio-libs-glib2-5.0-3.fc21.x86_64
pulseaudio-libs-5.0-3.fc21.x86_64
pulseaudio-libs-devel-5.0-3.fc21.x86_64
python-alsa-1.0.26-3.fc20.x86_64
alsa-utils-1.0.27.2-5.fc21.x86_64
alsa-lib-devel-1.0.27.2-2.fc21.x86_64
alsa-oss-1.0.17-9.fc20.x86_64
alsa-oss-libs-1.0.17-9.fc20.x86_64
alsamixergui-0.9.0-0.16.rc2.fc20.x86_64
alsa-lib-1.0.27.2-2.fc21.x86_64
alsa-firmware-1.0.27-2.fc20.noarch
alsa-tools-firmware-1.0.27-3.fc21.x86_64
alsa-lib-debuginfo-1.0.27.2-2.fc21.x86_64
alsa-tools-1.0.27-3.fc21.x86_64
And I've only got the pulseaudio-libs stuff installed because of
dependencies from other packages.
Kevin
--
The tt (and the liked lkml thread) describes a simpler solution.
The issue appears to be not with pulseaudio per se, but with the handling
of USB audio devices.
Since my only USB audio device is a Logiteck webcam (per the ticket), all I
had to do is unplug it and the system now boots to gdm/Gnome just fine.
tom
--
Tom London