Re: [gentoo-user] Plasma teething problems - Part II

2019-06-24 Thread Mick
On Monday, 24 June 2019 12:44:34 BST Dale wrote:
> Mick wrote:
> > I often find a number of speech-dispatcher processes running:
> >  4732 ?SLl0:00 /usr/lib64/speech-dispatcher-modules/sd_dummy
> >  /etc/> 
> > speech-dispatcher/modules/dummy.conf
> > 
> >  4734 ?SLl0:00 /usr/lib64/speech-dispatcher-modules/sd_generic
> >  /
> > 
> > etc/speech-dispatcher/modules/generic.conf
> > 
> >  4736 ?SLl0:00 /usr/lib64/speech-dispatcher-modules/sd_cicero
> >  /
> > 
> > etc/speech-dispatcher/modules/cicero.conf
> > 
> >  4737 ?Z  0:00  \_ [sd_cicero] 
> >  4739 ?SLl0:00 /usr/lib64/speech-dispatcher-modules/sd_espeak
> >  /
> > 
> > etc/speech-dispatcher/modules/espeak.conf
> > 
> >  4744 ?Ssl0:00 /usr/bin/speech-dispatcher --spawn
> >  --communication-> 
> > method unix_socket --socket-path
> > /run/user/1000/speech-dispatcher/speechd.sock
> > 
> > I don't know what is starting these processes or what they have to offer
> > to my desktop.  Checking systemsettings5/Accessibility Options/Screen
> > Reader, I can see it is NOT enabled.
> > 
> > How can I get rid of these?
> 
> I would start out by finding out what package /usr/bin/speech-dispatcher
> belongs too. Equery can help with that but other tools can as well. 
> Once you find that, then check the USE flags to see what can be adjusted
> to get rid if that.  I don't have it here so I can't do it on my system. 
> 
> Dale
> 
> :-)  :-) 

Good call Dale, here's what I found:

app-accessibility/speech-dispatcher is required by dev-qt/qtspeech,

which is required by kde-apps/kdepim-runtime and  kde-apps/kpimtextedit, 
neither of which have a USE flag to stop speech-dispatcher kicking off.

However, speech-dispatcher has USE="espeak" enabled, which I will try to 
disable and see what happens thereafter.

-- 
Regards,

Mick

signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Plasma teething problems - Part II

2019-06-24 Thread Mick
On Monday, 24 June 2019 16:22:01 BST Mick wrote:
> On Monday, 24 June 2019 12:44:34 BST Dale wrote:
> > Mick wrote:
> > > I often find a number of speech-dispatcher processes running:
> > >  4732 ?SLl0:00 /usr/lib64/speech-dispatcher-modules/sd_dummy
> > >  /etc/>
> > > 
> > > speech-dispatcher/modules/dummy.conf
> > > 
> > >  4734 ?SLl0:00
> > >  /usr/lib64/speech-dispatcher-modules/sd_generic
> > >  /
> > > 
> > > etc/speech-dispatcher/modules/generic.conf
> > > 
> > >  4736 ?SLl0:00
> > >  /usr/lib64/speech-dispatcher-modules/sd_cicero
> > >  /
> > > 
> > > etc/speech-dispatcher/modules/cicero.conf
> > > 
> > >  4737 ?Z  0:00  \_ [sd_cicero] 
> > >  4739 ?SLl0:00
> > >  /usr/lib64/speech-dispatcher-modules/sd_espeak
> > >  /
> > > 
> > > etc/speech-dispatcher/modules/espeak.conf
> > > 
> > >  4744 ?Ssl0:00 /usr/bin/speech-dispatcher --spawn
> > >  --communication->
> > > 
> > > method unix_socket --socket-path
> > > /run/user/1000/speech-dispatcher/speechd.sock
> > > 
> > > I don't know what is starting these processes or what they have to offer
> > > to my desktop.  Checking systemsettings5/Accessibility Options/Screen
> > > Reader, I can see it is NOT enabled.
> > > 
> > > How can I get rid of these?
> > 
> > I would start out by finding out what package /usr/bin/speech-dispatcher
> > belongs too. Equery can help with that but other tools can as well.
> > Once you find that, then check the USE flags to see what can be adjusted
> > to get rid if that.  I don't have it here so I can't do it on my system.
> > 
> > Dale
> > 
> > :-)  :-)
> 
> Good call Dale, here's what I found:
> 
> app-accessibility/speech-dispatcher is required by dev-qt/qtspeech,
> 
> which is required by kde-apps/kdepim-runtime and  kde-apps/kpimtextedit,
> neither of which have a USE flag to stop speech-dispatcher kicking off.
> 
> However, speech-dispatcher has USE="espeak" enabled, which I will try to
> disable and see what happens thereafter.

I also found this beauty in /etc/speech-dispatcher/speechd.conf, which I 
uncommented:

# The DisableAutoSpawn option will disable the autospawn mechanism.
# Thus the server will not start automatically on requests from the clients
DisableAutoSpawn

-- 
Regards,

Mick

signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Plasma teething problems - Part II

2019-06-24 Thread Dale
Mick wrote:
> On Monday, 24 June 2019 12:44:34 BST Dale wrote:
>> Mick wrote:
>>> I often find a number of speech-dispatcher processes running:
>>>  4732 ?SLl0:00 /usr/lib64/speech-dispatcher-modules/sd_dummy
>>>  /etc/> 
>>> speech-dispatcher/modules/dummy.conf
>>>
>>>  4734 ?SLl0:00 /usr/lib64/speech-dispatcher-modules/sd_generic
>>>  /
>>>
>>> etc/speech-dispatcher/modules/generic.conf
>>>
>>>  4736 ?SLl0:00 /usr/lib64/speech-dispatcher-modules/sd_cicero
>>>  /
>>>
>>> etc/speech-dispatcher/modules/cicero.conf
>>>
>>>  4737 ?Z  0:00  \_ [sd_cicero] 
>>>  4739 ?SLl0:00 /usr/lib64/speech-dispatcher-modules/sd_espeak
>>>  /
>>>
>>> etc/speech-dispatcher/modules/espeak.conf
>>>
>>>  4744 ?Ssl0:00 /usr/bin/speech-dispatcher --spawn
>>>  --communication-> 
>>> method unix_socket --socket-path
>>> /run/user/1000/speech-dispatcher/speechd.sock
>>>
>>> I don't know what is starting these processes or what they have to offer
>>> to my desktop.  Checking systemsettings5/Accessibility Options/Screen
>>> Reader, I can see it is NOT enabled.
>>>
>>> How can I get rid of these?
>> I would start out by finding out what package /usr/bin/speech-dispatcher
>> belongs too. Equery can help with that but other tools can as well. 
>> Once you find that, then check the USE flags to see what can be adjusted
>> to get rid if that.  I don't have it here so I can't do it on my system. 
>>
>> Dale
>>
>> :-)  :-) 
> Good call Dale, here's what I found:
>
> app-accessibility/speech-dispatcher is required by dev-qt/qtspeech,
>
> which is required by kde-apps/kdepim-runtime and  kde-apps/kpimtextedit, 
> neither of which have a USE flag to stop speech-dispatcher kicking off.
>
> However, speech-dispatcher has USE="espeak" enabled, which I will try to 
> disable and see what happens thereafter.
>


I went through this a few years ago.  I had some large programs
installed that I didn't use, Kmail and others.  I wanted to clean them
out but at the time I had installed KDE with kde-meta.  Basically, that
installs everything KDE, wanted or not.  I uninstalled that and went
these instead:


root@fireball / # equery list *kde*meta*
 * Searching for *kde*meta* ...
[IP-] [  ] kde-apps/kdeadmin-meta-19.04.2:5
[IP-] [  ] kde-apps/kdebase-meta-19.04.2:5
[IP-] [  ] kde-apps/kdecore-meta-19.04.2:5
[IP-] [  ] kde-apps/kdegames-meta-19.04.2:5
[IP-] [  ] kde-apps/kdegraphics-meta-19.04.2:5
[IP-] [  ] kde-apps/kdemultimedia-meta-19.04.2:5
root@fireball / #


Of course, there was still things I wanted to remove because I didn't
use them.  Of course there was things I wanted that I had to install
manually as well.  I got rid of some things with USE flags and others I
just had to live with.  Still, I slimmed it down a lot.  If I put in
more effort, I could slim it down more I suspect but it's close enough. 

This is one of the things I like about Gentoo, being able to cut off or
get rid of things I don't want.  USE flags help with that a lot. 

Glad you got it sorted out. 

Dale

:-)  :-)