<div class="gmail_quote">On Fri, May 29, 2009 at 12:25 PM, Gene Heskett <span dir="ltr"><<a href="mailto:gene.heskett@verizon.net">gene.heskett@verizon.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Friday 29 May 2009, Kevin Kofler wrote:<br>
</div><div class="im">>Gene Heskett wrote:<br>
>> And that IIRC, was one of the things in my kmenu that never ran, ever.<br>
><br>
>Then PulseAudio is not working. (pavucontrol at least used to just segfault<br>
>if PA was not running or not accepting connections because it didn't find a<br>
>working hardware device.)<br>
><br>
>> And since kde4, we no longer have the name of the executable listed in the<br>
>> menu's, there seems to be no way to try such stuff from a cli to see what<br>
>> error falls out when it doesn't run.<br>
><br>
>The pavucontrol name doesn't show up because the .desktop file doesn't<br>
>contain it. (It only has a Name field containing a generic name and no<br>
>GenericName field.) Complain to the pavucontrol maintainer(s) about that.<br>
>Where the names are contained in the .desktop file (i.e. for most KDE<br>
>apps), Kickoff will show them if you mouse over that item. Alternatively,<br>
>you can use the classic menu, which can be configured to show any<br>
>combination of Name and GenericName.<br>
><br>
>> What do I have to re-install to make these utils such as what you name<br>
>> above, actually work?<br>
><br>
>yum install kde-settings-pulseaudio<br>
>should drag in all you need. (You need at least pulseaudio and<br>
>alsa-plugins-pulseaudio.)<br>
><br>
> Kevin Kofler<br>
</div>That pulled in:<br>
Installing : pulseaudio<br>
1/4<br>
Installing : alsa-plugins-pulseaudio<br>
2/4<br>
Installing : pulseaudio-module-x11<br>
3/4<br>
Installing : kde-settings-pulseaudio<br>
<br>
Now what do I service ??? restart to bring it up?<br>
<div class="im"><br></div></blockquote></div><br>Just logging out and back in should do it but a full restart wouldn't hurt. Alternatively you could try opening a terminal and type "pulseaudio -D" which would allow you to see error messages if any. This is from memory so someone correct me if I'm wrong as I only have access to windows at work. <br>
<br>Richard<br>