<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Apr 21, 2014 at 10:42 AM, Clyde E. Kunkel <span dir="ltr"><<a href="mailto:clydekunkel7734@verizon.net" target="_blank">clydekunkel7734@verizon.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, 21 Apr 2014 09:12:09 -0700<br>
<div class="">Tom London <<a href="mailto:selinux@gmail.com">selinux@gmail.com</a>> wrote:<br>
<br>
><br>
><br>
> ><snip><br>
><br>
</div><div class="">> The tt (and the liked lkml thread) describes a simpler solution.<br>
><br>
> The issue appears to be not with pulseaudio per se, but with the<br>
> handling of USB audio devices.<br>
><br>
> Since my only USB audio device is a Logiteck webcam (per the ticket),<br>
> all I had to do is unplug it and the system now boots to gdm/Gnome<br>
> just fine.<br>
><br>
> tom<br>
<br>
</div>OK, same here. However, isn't this still a pulseaudio issue since<br>
the webcam is certainly not usable unplugged?<br>
<div class="HOEnZb"><div class="h5">--<br>
</div></div></blockquote><div><br></div><div>I would presume that no user process should be able to put the kernel into the observed state.<br><br></div><div>tom<br></div></div>-- <br>Tom London
</div></div>