[gentoo-user] Plasma teething problems - Part II

[gentoo-user] Plasma teething problems - Part II

[Mick]

[-- Attachment #1: Type: text/plain, Size: 977 bytes --]

I often find a number of speech-dispatcher processes running:

 4732 ?        SLl    0:00 /usr/lib64/speech-dispatcher-modules/sd_dummy /etc/
speech-dispatcher/modules/dummy.conf
 4734 ?        SLl    0:00 /usr/lib64/speech-dispatcher-modules/sd_generic /
etc/speech-dispatcher/modules/generic.conf
 4736 ?        SLl    0:00 /usr/lib64/speech-dispatcher-modules/sd_cicero /
etc/speech-dispatcher/modules/cicero.conf
 4737 ?        Z      0:00  \_ [sd_cicero] <defunct>
 4739 ?        SLl    0:00 /usr/lib64/speech-dispatcher-modules/sd_espeak /
etc/speech-dispatcher/modules/espeak.conf
 4744 ?        Ssl    0: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?

-- 
Regards,

Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

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

[Dale]

Mick wrote:
> I often find a number of speech-dispatcher processes running:
>
>  4732 ?        SLl    0:00 /usr/lib64/speech-dispatcher-modules/sd_dummy /etc/
> speech-dispatcher/modules/dummy.conf
>  4734 ?        SLl    0:00 /usr/lib64/speech-dispatcher-modules/sd_generic /
> etc/speech-dispatcher/modules/generic.conf
>  4736 ?        SLl    0:00 /usr/lib64/speech-dispatcher-modules/sd_cicero /
> etc/speech-dispatcher/modules/cicero.conf
>  4737 ?        Z      0:00  \_ [sd_cicero] <defunct>
>  4739 ?        SLl    0:00 /usr/lib64/speech-dispatcher-modules/sd_espeak /
> etc/speech-dispatcher/modules/espeak.conf
>  4744 ?        Ssl    0: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

:-)  :-) 

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

[Mick]

[-- Attachment #1: Type: text/plain, Size: 1872 bytes --]

On Monday, 24 June 2019 12:44:34 BST Dale wrote:
> Mick wrote:
> > I often find a number of speech-dispatcher processes running:
> >  4732 ?        SLl    0:00 /usr/lib64/speech-dispatcher-modules/sd_dummy
> >  /etc/> 
> > speech-dispatcher/modules/dummy.conf
> > 
> >  4734 ?        SLl    0:00 /usr/lib64/speech-dispatcher-modules/sd_generic
> >  /
> > 
> > etc/speech-dispatcher/modules/generic.conf
> > 
> >  4736 ?        SLl    0:00 /usr/lib64/speech-dispatcher-modules/sd_cicero
> >  /
> > 
> > etc/speech-dispatcher/modules/cicero.conf
> > 
> >  4737 ?        Z      0:00  \_ [sd_cicero] <defunct>
> >  4739 ?        SLl    0:00 /usr/lib64/speech-dispatcher-modules/sd_espeak
> >  /
> > 
> > etc/speech-dispatcher/modules/espeak.conf
> > 
> >  4744 ?        Ssl    0: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

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

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

[Mick]

[-- Attachment #1: Type: text/plain, Size: 2303 bytes --]

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 ?        SLl    0:00 /usr/lib64/speech-dispatcher-modules/sd_dummy
> > >  /etc/>
> > > 
> > > speech-dispatcher/modules/dummy.conf
> > > 
> > >  4734 ?        SLl    0:00
> > >  /usr/lib64/speech-dispatcher-modules/sd_generic
> > >  /
> > > 
> > > etc/speech-dispatcher/modules/generic.conf
> > > 
> > >  4736 ?        SLl    0:00
> > >  /usr/lib64/speech-dispatcher-modules/sd_cicero
> > >  /
> > > 
> > > etc/speech-dispatcher/modules/cicero.conf
> > > 
> > >  4737 ?        Z      0:00  \_ [sd_cicero] <defunct>
> > >  4739 ?        SLl    0:00
> > >  /usr/lib64/speech-dispatcher-modules/sd_espeak
> > >  /
> > > 
> > > etc/speech-dispatcher/modules/espeak.conf
> > > 
> > >  4744 ?        Ssl    0: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

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

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

[Peter Humphrey]

On Monday, 24 June 2019 16:32:19 BST Mick wrote:

> I also found this beauty in /etc/speech-dispatcher/speechd.conf, which I
> uncommented:
> 
> # The DisableAutoSpawn option will disable the autospawn mechanism.

That's the sort of stupid explanation that gives technical authors and other 
program documenters a bad name. Gentoo seems to be particularly heavily 
afflicted with it.

> # Thus the server will not start automatically on requests from the clients
> DisableAutoSpawn

-- 
Regards,
Peter.

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

[Mick]

[-- Attachment #1: Type: text/plain, Size: 751 bytes --]

On Monday, 24 June 2019 18:04:06 BST Peter Humphrey wrote:
> On Monday, 24 June 2019 16:32:19 BST Mick wrote:
> > I also found this beauty in /etc/speech-dispatcher/speechd.conf, which I
> > uncommented:
> > 
> > # The DisableAutoSpawn option will disable the autospawn mechanism.
> 
> That's the sort of stupid explanation that gives technical authors and other
> program documenters a bad name. Gentoo seems to be particularly heavily
> afflicted with it.
> 
> > # Thus the server will not start automatically on requests from the
> > clients
> > DisableAutoSpawn

Clearly you have suffered in the hands of USE flag descriptors, which would make 
even the priestesses of the Oracle of Delphi sound coherent and unambiguous.  
LOL!
-- 
Regards,

Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

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

[Peter Humphrey]

On Monday, 24 June 2019 18:35:21 BST Mick wrote:
> On Monday, 24 June 2019 18:04:06 BST Peter Humphrey wrote:
> > On Monday, 24 June 2019 16:32:19 BST Mick wrote:
> > > I also found this beauty in /etc/speech-dispatcher/speechd.conf, which I
> > > uncommented:
> > > 
> > > # The DisableAutoSpawn option will disable the autospawn mechanism.
> > 
> > That's the sort of stupid explanation that gives technical authors and
> > other program documenters a bad name. Gentoo seems to be particularly
> > heavily afflicted with it.
> 
> Clearly you have suffered in the hands of USE flag descriptors, which would
> make even the priestesses of the Oracle of Delphi sound coherent and
> unambiguous. LOL!

I even raised a bug about it a few years ago. There was quite a flurry of 
activity in rewriting USE flag descriptions, but it soon died away.

-- 
Regards,
Peter.

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

[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 ?        SLl    0:00 /usr/lib64/speech-dispatcher-modules/sd_dummy
>>>  /etc/> 
>>> speech-dispatcher/modules/dummy.conf
>>>
>>>  4734 ?        SLl    0:00 /usr/lib64/speech-dispatcher-modules/sd_generic
>>>  /
>>>
>>> etc/speech-dispatcher/modules/generic.conf
>>>
>>>  4736 ?        SLl    0:00 /usr/lib64/speech-dispatcher-modules/sd_cicero
>>>  /
>>>
>>> etc/speech-dispatcher/modules/cicero.conf
>>>
>>>  4737 ?        Z      0:00  \_ [sd_cicero] <defunct>
>>>  4739 ?        SLl    0:00 /usr/lib64/speech-dispatcher-modules/sd_espeak
>>>  /
>>>
>>> etc/speech-dispatcher/modules/espeak.conf
>>>
>>>  4744 ?        Ssl    0: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

:-)  :-) 

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

[Mick]

[-- Attachment #1: Type: text/plain, Size: 2210 bytes --]

On Monday, 24 June 2019 21:16:51 BST Dale wrote:

> 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:

According to the current wiki page these days the kde-meta has been replaced 
with plasma-meta.  This is how I have configured plasma-meta:

     Installed versions:  5.15.5(5)(12:58:00 14/06/19)(bluetooth browser-
integration crypt desktop-portal display-manager elogind handbook legacy-
systray pam pm-utils sddm wallpapers -consolekit -discover -grub -gtk -
networkmanager -plymouth -pulseaudio -sdk -systemd)

BUT ... I am thinking of uninstalling it, deplclean-ing my world and 
installing  kde-plasma/plasma-desktop which is the slim version, while keeping 
some select kde-meta packages I need/want.

> root@fireball / # equery list *kde*meta*
>  * Searching for *kde*meta* ...
> [IP-] [  ] kde-apps/kdeadmin-meta-19.04.2:5
I have this installed too.

> [IP-] [  ] kde-apps/kdebase-meta-19.04.2:5
I think the kdebase-meta was meant to be a transitional package from KDE4 to 
plasma/KDE5.  I suspect this has been superseded by kde-plasma/plasma-meta, 
but I'm not sure.  In any case, I do not have this installed.

> [IP-] [  ] kde-apps/kdecore-meta-19.04.2:5
I have this installed too.

> [IP-] [  ] kde-apps/kdegames-meta-19.04.2:5
No games for me, thanks.

> [IP-] [  ] kde-apps/kdegraphics-meta-19.04.2:5
> [IP-] [  ] kde-apps/kdemultimedia-meta-19.04.2:5
I have these two installed, plus:

[IP-] [  ] kde-apps/kdenetwork-meta-18.12.3:5
[IP-] [  ] kde-apps/kdepim-meta-18.12.3:5
[IP-] [  ] kde-apps/kdeutils-meta-18.12.3:5


> 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. 

Sadly I'm not there yet.   I've got to figure out how to get back my Suspend to 
Ram, Hibernate, Reboot, and Shutdown buttons, without re-importing 
NetworkManager, or at least without having it being started by powerdevil.  

-- 
Regards,

Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

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

[Mick]

[-- Attachment #1: Type: text/plain, Size: 6306 bytes --]

On Monday, 24 June 2019 21:40:07 BST you wrote:
> On Monday, 24 June 2019 21:16:51 BST Dale wrote:
> > 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:
> According to the current wiki page these days the kde-meta has been replaced
> with plasma-meta.  This is how I have configured plasma-meta:
> 
>      Installed versions:  5.15.5(5)(12:58:00 14/06/19)(bluetooth browser-
> integration crypt desktop-portal display-manager elogind handbook legacy-
> systray pam pm-utils sddm wallpapers -consolekit -discover -grub -gtk -
> networkmanager -plymouth -pulseaudio -sdk -systemd)
> 
> BUT ... I am thinking of uninstalling it, deplclean-ing my world and
> installing  kde-plasma/plasma-desktop which is the slim version, while
> keeping some select kde-meta packages I need/want.
> 
> > root@fireball / # equery list *kde*meta*
> > 
> >  * Searching for *kde*meta* ...
> > 
> > [IP-] [  ] kde-apps/kdeadmin-meta-19.04.2:5
> 
> I have this installed too.
> 
> > [IP-] [  ] kde-apps/kdebase-meta-19.04.2:5
> 
> I think the kdebase-meta was meant to be a transitional package from KDE4 to
> plasma/KDE5.  I suspect this has been superseded by kde-plasma/plasma-meta,
> but I'm not sure.  In any case, I do not have this installed.
> 
> > [IP-] [  ] kde-apps/kdecore-meta-19.04.2:5
> 
> I have this installed too.
> 
> > [IP-] [  ] kde-apps/kdegames-meta-19.04.2:5
> 
> No games for me, thanks.
> 
> > [IP-] [  ] kde-apps/kdegraphics-meta-19.04.2:5
> > [IP-] [  ] kde-apps/kdemultimedia-meta-19.04.2:5
> 
> I have these two installed, plus:
> 
> [IP-] [  ] kde-apps/kdenetwork-meta-18.12.3:5
> [IP-] [  ] kde-apps/kdepim-meta-18.12.3:5
> [IP-] [  ] kde-apps/kdeutils-meta-18.12.3:5
> 
> > 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.
> 
> Sadly I'm not there yet.   I've got to figure out how to get back my Suspend
> to Ram, Hibernate, Reboot, and Shutdown buttons, without re-importing
> NetworkManager, or at least without having it being started by powerdevil.

Hmm ... plasma-desktop was already installed, dragged in by plasma-meta.  So 
no need to reinstall it.  Sadly trying to depclean after removing plasma-meta 
will get rid of a lot of packages, something I'm not keen to do:

>>> These are the packages that would be unmerged:

 kde-plasma/plasma-browser-integration
    selected: 5.15.5 
   protected: none 
     omitted: none 

 kde-plasma/plasma-vault
    selected: 5.15.5 
   protected: none 
     omitted: none 

 kde-plasma/kdeplasma-addons
    selected: 5.15.5 
   protected: none 
     omitted: none 

 kde-plasma/kscreen
    selected: 5.15.5 
   protected: none 
     omitted: none 

 kde-plasma/kwrited
    selected: 5.15.5 
   protected: none 
     omitted: none 

 kde-plasma/kwayland-integration
    selected: 5.15.5 
   protected: none 
     omitted: none 

 kde-plasma/xembed-sni-proxy
    selected: 5.15.5 
   protected: none 
     omitted: none 

 kde-plasma/plasma-workspace-wallpapers
    selected: 5.15.5 
   protected: none 
     omitted: none 

 kde-plasma/bluedevil
    selected: 5.15.5 
   protected: none 
     omitted: none 

 kde-plasma/kgamma
    selected: 5.15.5 
   protected: none 
     omitted: none 

 kde-plasma/drkonqi
    selected: 5.15.5 
   protected: none 
     omitted: none 

 kde-plasma/kwallet-pam
    selected: 5.15.5 
   protected: none 
     omitted: none 

 kde-plasma/user-manager
    selected: 5.15.5 
   protected: none 
     omitted: none 

 kde-plasma/xdg-desktop-portal-kde
    selected: 5.15.5-r1 
   protected: none 
     omitted: none 

 kde-plasma/kinfocenter
    selected: 5.15.5 
   protected: none 
     omitted: none 

 kde-plasma/sddm-kcm
    selected: 5.15.5 
   protected: none 
     omitted: none 

 kde-plasma/systemsettings
    selected: 5.15.5 
   protected: none 
     omitted: none 

 kde-plasma/kmenuedit
    selected: 5.15.5 
   protected: none 
     omitted: none 

 kde-plasma/ksshaskpass
    selected: 5.15.5 
   protected: none 
     omitted: none 

 sys-fs/cryfs
    selected: 0.9.9 
   protected: none 
     omitted: none 

 dev-libs/libpwquality
    selected: 1.4.0 
   protected: none 
     omitted: none 

 kde-frameworks/kxmlrpcclient
    selected: 5.57.0 
   protected: none 
     omitted: none 

 kde-frameworks/bluez-qt
    selected: 5.57.0 
   protected: none 
     omitted: none 

 sys-apps/accountsservice
    selected: 0.6.50-r1 
   protected: none 
     omitted: none 

 net-misc/socat
    selected: 1.7.3.2 
   protected: none 
     omitted: none 

 kde-plasma/khotkeys
    selected: 5.15.5 
   protected: none 
     omitted: none 

 sys-apps/xdg-desktop-portal
    selected: 1.2.0 
   protected: none 
     omitted: none 

 x11-misc/sddm
    selected: 0.18.0 
   protected: none 
     omitted: none 

 dev-libs/crypto++
    selected: 7.0.0-r3 
   protected: none 
     omitted: none 

All selected packages: =dev-libs/crypto++-7.0.0-r3 =kde-plasma/xembed-sni-
proxy-5.15.5 =dev-libs/libpwquality-1.4.0 =kde-plasma/ksshaskpass-5.15.5 =kde-
plasma/kinfocenter-5.15.5 =kde-plasma/kwallet-pam-5.15.5 =kde-plasma/
khotkeys-5.15.5 =kde-plasma/xdg-desktop-portal-kde-5.15.5-r1 =kde-plasma/
kgamma-5.15.5 =kde-plasma/drkonqi-5.15.5 =kde-plasma/systemsettings-5.15.5 
=kde-frameworks/kxmlrpcclient-5.57.0 =kde-plasma/plasma-vault-5.15.5 =net-
misc/socat-1.7.3.2 =kde-plasma/plasma-workspace-wallpapers-5.15.5 =x11-misc/
sddm-0.18.0 =kde-plasma/sddm-kcm-5.15.5 =kde-plasma/kwrited-5.15.5 =kde-
plasma/kscreen-5.15.5 =kde-plasma/user-manager-5.15.5 =kde-plasma/plasma-
browser-integration-5.15.5 =kde-plasma/kdeplasma-addons-5.15.5 =kde-plasma/
kwayland-integration-5.15.5 =kde-plasma/bluedevil-5.15.5 =kde-plasma/
kmenuedit-5.15.5 =sys-fs/cryfs-0.9.9 =sys-apps/accountsservice-0.6.50-r1 =sys-
apps/xdg-desktop-portal-1.2.0 =kde-frameworks/bluez-qt-5.57.0

>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.

I need to find a different solution ...
-- 
Regards,

Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

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

[Jack]

On 2019.06.24 16:54, Mick wrote:
> On Monday, 24 June 2019 21:40:07 BST you wrote:
> > On Monday, 24 June 2019 21:16:51 BST Dale wrote:
> > > 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:
> > According to the current wiki page these days the kde-meta has been  
> replaced
> > with plasma-meta.  This is how I have configured plasma-meta:
> >
> >      Installed versions:  5.15.5(5)(12:58:00 14/06/19)(bluetooth  
> browser-
> > integration crypt desktop-portal display-manager elogind handbook  
> legacy-
> > systray pam pm-utils sddm wallpapers -consolekit -discover -grub  
> -gtk -
> > networkmanager -plymouth -pulseaudio -sdk -systemd)
> >
> > BUT ... I am thinking of uninstalling it, deplclean-ing my world and
> > installing  kde-plasma/plasma-desktop which is the slim version,  
> while
> > keeping some select kde-meta packages I need/want.
> >
> > > root@fireball / # equery list *kde*meta*
> > >
> > >  * Searching for *kde*meta* ...
> > >
> > > [IP-] [  ] kde-apps/kdeadmin-meta-19.04.2:5
> >
> > I have this installed too.
> >
> > > [IP-] [  ] kde-apps/kdebase-meta-19.04.2:5
> >
> > I think the kdebase-meta was meant to be a transitional package  
> from KDE4 to
> > plasma/KDE5.  I suspect this has been superseded by  
> kde-plasma/plasma-meta,
> > but I'm not sure.  In any case, I do not have this installed.
> >
> > > [IP-] [  ] kde-apps/kdecore-meta-19.04.2:5
> >
> > I have this installed too.
> >
> > > [IP-] [  ] kde-apps/kdegames-meta-19.04.2:5
> >
> > No games for me, thanks.
> >
> > > [IP-] [  ] kde-apps/kdegraphics-meta-19.04.2:5
> > > [IP-] [  ] kde-apps/kdemultimedia-meta-19.04.2:5
> >
> > I have these two installed, plus:
> >
> > [IP-] [  ] kde-apps/kdenetwork-meta-18.12.3:5
> > [IP-] [  ] kde-apps/kdepim-meta-18.12.3:5
> > [IP-] [  ] kde-apps/kdeutils-meta-18.12.3:5
> >
> > > 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.
> >
> > Sadly I'm not there yet.   I've got to figure out how to get back  
> my Suspend
> > to Ram, Hibernate, Reboot, and Shutdown buttons, without  
> re-importing
> > NetworkManager, or at least without having it being started by  
> powerdevil.
> 
> Hmm ... plasma-desktop was already installed, dragged in by  
> plasma-meta.  So
> no need to reinstall it.  Sadly trying to depclean after removing  
> plasma-meta
> will get rid of a lot of packages, something I'm not keen to do:
> 
> >>> These are the packages that would be unmerged:

[snip long list of packages]

I just chose the specific packages I wanted and explicitly emerged  
them.  You can just add them to your world file (either manually, or  
with "emerge --noreplace package" so they won't be depcleaned.  I have  
lots of kde stuff (37 items from grep kde worldfile) but kdecore-meta  
and kdegraphics-meta are the only meta packages in my world file.

Jack

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

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 574 bytes --]

On Mon, 24 Jun 2019 21:54:20 +0100, Mick wrote:

> >>> 'Selected' packages are slated for removal.
> >>> 'Protected' and 'omitted' packages will not be removed.  
> 
> I need to find a different solution ...

The solution I opted for was to create a kde5 set containing the apps I
wanted, then emerge -n @kde5.

Then it was just a case of running emerge -cp to see if there was
anything else I needed to add to the set before depcleaning in anger.


-- 
Neil Bothwick

Help a man when he is in trouble and he will remember you when he is in
trouble again

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

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

[Peter Humphrey]

On Monday, 24 June 2019 21:40:07 BST Mick wrote:

> According to the current wiki page these days the kde-meta has been
> replaced with plasma-meta.  This is how I have configured plasma-meta:
> 
>      Installed versions:  5.15.5(5)(12:58:00 14/06/19)(bluetooth browser-
> integration crypt desktop-portal display-manager elogind handbook legacy-
> systray pam pm-utils sddm wallpapers -consolekit -discover -grub -gtk -
> networkmanager -plymouth -pulseaudio -sdk -systemd)
> 
> BUT ... I am thinking of uninstalling it, deplclean-ing my world and
> installing  kde-plasma/plasma-desktop which is the slim version, while
> keeping some select kde-meta packages I need/want.

I made quite a determined attempt to do that on this system. I would uninstall 
a meta package, then see what packages would be removed by emerge -c, and 
emerge --noreplace any that I wanted to keep. Sounds simple, eh? Not so. I 
soon found myself mired in loops and contradictory dependencies which I 
couldn't escape.

I ended up reinstalling from scratch, avoiding as many meta-packages as I 
could. I tried to build on kde-plasma/plasma-desktop, but it was simply too 
basic. I spent a long time trying to find packages to restore what I was used 
to in kde-plasma, but I concluded that it would need the knowledge of a kde 
packager.

So I do still have five meta-packages. Ho hum.

I don't want to warn you off altogether, but at least be ready for some tricky 
work. Lots of it!

-- 
Regards,
Peter.

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

[Mick]

[-- Attachment #1: Type: text/plain, Size: 1953 bytes --]

On Tuesday, 25 June 2019 10:00:11 BST Peter Humphrey wrote:
> On Monday, 24 June 2019 21:40:07 BST Mick wrote:
> > According to the current wiki page these days the kde-meta has been
> > 
> > replaced with plasma-meta.  This is how I have configured plasma-meta:
> >      Installed versions:  5.15.5(5)(12:58:00 14/06/19)(bluetooth browser-
> > 
> > integration crypt desktop-portal display-manager elogind handbook legacy-
> > systray pam pm-utils sddm wallpapers -consolekit -discover -grub -gtk -
> > networkmanager -plymouth -pulseaudio -sdk -systemd)
> > 
> > BUT ... I am thinking of uninstalling it, deplclean-ing my world and
> > installing  kde-plasma/plasma-desktop which is the slim version, while
> > keeping some select kde-meta packages I need/want.
> 
> I made quite a determined attempt to do that on this system. I would
> uninstall a meta package, then see what packages would be removed by emerge
> -c, and emerge --noreplace any that I wanted to keep. Sounds simple, eh?
> Not so. I soon found myself mired in loops and contradictory dependencies
> which I couldn't escape.
> 
> I ended up reinstalling from scratch, avoiding as many meta-packages as I
> could. I tried to build on kde-plasma/plasma-desktop, but it was simply too
> basic. I spent a long time trying to find packages to restore what I was
> used to in kde-plasma, but I concluded that it would need the knowledge of
> a kde packager.
> 
> So I do still have five meta-packages. Ho hum.
> 
> I don't want to warn you off altogether, but at least be ready for some
> tricky work. Lots of it!

Thank you Peter, I have been down that rabbit hole myself a few times and I'd 
rather avoid repeating it as long as I can.  The very reason I have not 
implemented the same approach on this PC and thought of stiking to the wiki, 
is because my package-at-a-time KDE approach invariably ends up breaking some 
of the plasma desktop integration I want/need.

-- 
Regards,

Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]