Re: [gentoo-user] skylake and x265 movie display

[Daniel Frey]

On 6/25/19 4:57 PM, Adam Carter wrote:
My skylake (i3-6100U) system drops frames when watching x265 movies (in 
mpv and kodi), with all cores at 100% CPU. I've re-run through 
https://wiki.gentoo.org/wiki/Intel and tried changing from the intel 
driver to modsetting, and it appears to use less CPU for x264 at least. 
Still maxed out for x265 so I cant tell if there's a difference for that.


I'm going through the USE flags for kodi, mpv and ffmpeg, which flags 
are the most important? Is there some way to run a simple movie playback 
benchmark to assess the impact of changes?


Current settings;


What about USE flags for mesa and libva?

This wouldn't happen to be a 10-bit encoded x265, would it? If it is, 
10-bit hardware decoding is only supported in Kaby Lake or newer (this 
could explain it decoding in software/on CPU instead of GPU.)


I also had to boot with UEFI or no hardware decoding happened at all. 
Mine was old enough to give you a choice but video performance suffered 
in BIOS boot mode.


When I got my celeron-based NUC I discovered that just because the CPU 
has some hardware offloading doesn't mean software will use it. :(


Dan

[gentoo-user] skylake and x265 movie display

[Adam Carter]

My skylake (i3-6100U) system drops frames when watching x265 movies (in mpv
and kodi), with all cores at 100% CPU. I've re-run through
https://wiki.gentoo.org/wiki/Intel and tried changing from the intel driver
to modsetting, and it appears to use less CPU for x264 at least. Still
maxed out for x265 so I cant tell if there's a difference for that.

I'm going through the USE flags for kodi, mpv and ffmpeg, which flags are
the most important? Is there some way to run a simple movie playback
benchmark to assess the impact of changes?

Current settings;
CPU_FLAGS_X86="aes avx avx2 fma3 mmx mmxext sse sse2 sse3 sse4_1 sse4_2
ssse3 -3dnow -3dnowext -fma4 -xop"

ffmpeg USE: X alsa bzip2 encode gpl hardcoded-tables iconv libdrm mp3
network opengl openssl opus postproc pulseaudio sdl svg threads truetype
vaapi vorbis x264 xcb xvid zlib (-altivec) -amr -amrenc (-appkit) -bluray
-bs2b -cdio -chromaprint -chromium -codec2 -cpudetection -debug -doc -fdk
-flite -fontconfig -frei0r -fribidi -gcrypt -gme -gmp -gnutls -gsm
-iec61883 -ieee1394 -jack -jpeg2k -kvazaar -ladspa -libaom -libass -libcaca
-libilbc -libressl -librtmp -libsoxr -libv4l -libxml2 -lv2 -lzma
(-mipsdspr1) (-mipsdspr2) (-mipsfpu) (-mmal) -modplug -openal -opencl
-openh264 -oss -pic -rubberband -samba -snappy -speex -srt -ssh
-static-libs -test -theora -twolame -v4l -vdpau -vpx -wavpack -webp -x265
-zeromq -zimg -zvbi

mpv USE: X alsa cdda cli dvd egl iconv jpeg lcms libass lua luajit opengl
pulseaudio uchardet vaapi xv zlib (-aqua) -archive -bluray (-coreaudio)
-cplugins -cuda -doc -drm -dvb -gbm -jack -javascript -libcaca -libmpv
-openal -oss (-raspberry-pi) -rubberband -samba -sdl (-selinux) -test
-tools -v4l -vdpau -vulkan -wayland -zsh-completion

kodi USE: X alsa bluetooth css dbus dvd gles lcms opengl pulseaudio
(system-ffmpeg) systemd udev udisks upower vaapi xslt -airplay -bluray
-caps -cec -gbm -libressl -libusb -lirc -mariadb -mysql -nfs -samba -test
-upnp -vdpau -wayland -webserver -zeroconf

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

[Neil Bothwick]

On Tue, 25 Jun 2019 17:09:02 +0300, Nikos Chantziaras wrote:

> > [1] kde-plasma/plasma-meta requires kde-plasma/powerdevil, which
> > requires kde- frameworks/networkmanager-qt, which requires
> > net-misc/networkmanager, which requires net-misc/modemmanager  
> 
> I use Plasma, and NW is not installed. I have "-networkmanager" in my 
> USE flags in make.conf.

That's not enough, powerdevil doesn't have a networkmanager USE flag, you
have to set -wireless for powerdevil. Here's the relevant portion of the
DEPEND definition in the ebuild

wireless? (
$(add_frameworks_dep bluez-qt)
$(add_frameworks_dep networkmanager-qt)
)


-- 
Neil Bothwick

Bagpipe for free: Stuff cat under arm. Pull legs, chew tail.


pgp8exFCMqM04.pgp
Description: OpenPGP digital signature

[gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]

[»Q«]

On Mon, 24 Jun 2019 21:19:09 +0100
Mick  wrote:

> Can someone please explain how the removal of the 'wireless' USE flag
> from powerdevil ends up with no buttons for Suspend-to-RAM,
> Hibernation, Reboot or Shutdown under the Leave tab of the KMenu?
> What does wireless have to do with those functions which should work
> regardless?

I have the wireless flag on, and I'm sometimes missing those buttons.
I've never figured out why, but they usually return after I log out of
KDE and back in -- sometimes it takes a reboot.

> Also, the sddm DM shutdown/reboot buttons now do not work. O_O

Those have never worked for me.

Re: [gentoo-user] fdm fails during ./configure: libssl not found

[Michael Orlitzky]

On 6/24/19 6:53 PM, Bryant Morrow wrote:
> ---
> 
> fdm-1.9 consistently fails to build,


I just drive-by committed v2.0, give that a try.

Re: [gentoo-user] Re: Strange behavior of "tab" key with Libreoffice Calc and Plasma

[Neil Bothwick]

On Tue, 25 Jun 2019 14:59:39 +0100, Mick wrote:

> > Unless my eyes are playing tricks on me, I think you mean which VCL
> > (not VLC) is being used.   
> 
> I beg your pardon, yes, I meant to say vcl.  I just started LOcalc from
> within Enlightenment, which does not load the KDE env profile and which
> shows:
> 
> Version: 6.2.4.2.0+
> Build ID: Gentoo official package
> CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: x11; 
> 
> There's no tab problem with this one.

I "solved" this by putting SAL_USE_VCLPLUGIN=gtk3 in a file in /etc/env.d
and running env-update.


-- 
Neil Bothwick

Modulation in all things.


pgpwqcmY96cpS.pgp
Description: OpenPGP digital signature

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

[Nikos Chantziaras]

On 24/06/2019 14:00, Mick wrote:

I've installed plasma-meta plus some kde-apps meta packages as follows:

kde-apps/kdeadmin-meta
kde-apps/kdecore-meta
kde-apps/kdegraphics-meta
kde-apps/kdemultimedia-meta
kde-apps/kdenetwork-meta
kde-apps/kdepim-meta
kde-apps/kdeutils-meta
kde-apps/kwalletmanager
kde-frameworks/oxygen-icons
kde-plasma/plasma-meta

One of the above[1] brought in NetworkManager, which I don't use because for
my use case there's nothing wrong with openrc netifrc scripts.
[...]
[1] kde-plasma/plasma-meta requires kde-plasma/powerdevil, which requires kde-
frameworks/networkmanager-qt, which requires net-misc/networkmanager, which
requires net-misc/modemmanager


I use Plasma, and NW is not installed. I have "-networkmanager" in my 
USE flags in make.conf. Add that, and do a:


emerge -auDN --with-bdeps=y @world
emerge -a --depclean

You should then be able to install Plasma without NW.

Re: [gentoo-user] Re: Strange behavior of "tab" key with Libreoffice Calc and Plasma

[Mick]

On Tuesday, 25 June 2019 14:17:21 BST »Q« wrote:
> On Mon, 24 Jun 2019 21:15:55 +0100
> 
> Mick  wrote:
> > On Monday, 24 June 2019 21:11:48 BST Philip Webb wrote:
> > > 190624 Stefano Crocco wrote:
> > > > On domenica 23 giugno 2019 22:31:33 CEST Philip Webb wrote:
> > > >> That's what it does for me now, using LO 6.2.4.2 on KDE.
> > > >> Here, pressing Tab-Tab simply moves  2  cells to the right.
> > > > 
> > > > Do you have the kde use flag enabled ?
> > > > This morning I've tried several combinations of flags
> > > > and only disabling the kde one this issue disappeared.
> > > > 
> > >   root:529 ~> eix libreoffice
> > >   [I] app-office/libreoffice
> > >   Available versions:  6.1.5.2 6.2.4.2 **6.2. **
> > > 
> > > {accessibility bluetooth +branding coinmp +cups dbus debug eds
> > > firebird googledrive gstreamer +gtk gtk2 java kde ldap +mariadb
> > > mysql odk pdfimport postgres test vlc ELIBC="FreeBSD"
> > > LIBREOFFICE_EXTENSIONS="nlpsolver scripting-beanshell
> > > scripting-javascript wiki-publisher"
> > > PYTHON_SINGLE_TARGET="python2_7 python3_5 python3_6 python3_7"
> > > PYTHON_TARGETS="python2_7 python3_5 python3_6 python3_7"} Installed
> > > versions:  6.2.4.2([2019-06-19 06:18:11])(accessibility cups dbus
> > > gtk gtk2 pdfimport -bluetooth -branding -coinmp -debug -eds
> > > -firebird -googledrive -gstreamer -java -kde -ldap -mariadb -odk
> > > -postgres -test -vlc ELIBC="-FreeBSD"
> > > LIBREOFFICE_EXTENSIONS="-nlpsolver -scripting-beanshell
> > > -scripting-javascript -wiki-publisher"
> > > PYTHON_SINGLE_TARGET="python3_6 -python2_7 -python3_5 -python3_7"
> > > PYTHON_TARGETS="python2_7 python3_6 -python3_5 -python3_7")
> > > 
> > > So, yes (smile).
> > 
> > It depends on which VLC plugin is used, KDE, or Gtk.  Go to
> > Help/About and you can see when loaded with the KDE VLC plugin the
> > 'tab-losing-cell-focus' bug is present.  With the Gtk VLC plugin
> > loaded, the tab works as it should.
> 
> Unless my eyes are playing tricks on me, I think you mean which VCL
> (not VLC) is being used. 

I beg your pardon, yes, I meant to say vcl.  I just started LOcalc from within 
Enlightenment, which does not load the KDE env profile and which shows:

Version: 6.2.4.2.0+
Build ID: Gentoo official package
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: x11; 

There's no tab problem with this one.
 
-- 
Regards,

Mick

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

[gentoo-user] Re: Strange behavior of "tab" key with Libreoffice Calc and Plasma

[»Q«]

On Mon, 24 Jun 2019 21:15:55 +0100
Mick  wrote:

> On Monday, 24 June 2019 21:11:48 BST Philip Webb wrote:
> > 190624 Stefano Crocco wrote:  
> > > On domenica 23 giugno 2019 22:31:33 CEST Philip Webb wrote:  
> > >> That's what it does for me now, using LO 6.2.4.2 on KDE.
> > >> Here, pressing Tab-Tab simply moves  2  cells to the right.  
> > > 
> > > Do you have the kde use flag enabled ?
> > > This morning I've tried several combinations of flags
> > > and only disabling the kde one this issue disappeared.  
> > 
> >   root:529 ~> eix libreoffice
> >   [I] app-office/libreoffice
> >   Available versions:  6.1.5.2 6.2.4.2 **6.2. **
> > {accessibility bluetooth +branding coinmp +cups dbus debug eds
> > firebird googledrive gstreamer +gtk gtk2 java kde ldap +mariadb
> > mysql odk pdfimport postgres test vlc ELIBC="FreeBSD"
> > LIBREOFFICE_EXTENSIONS="nlpsolver scripting-beanshell
> > scripting-javascript wiki-publisher"
> > PYTHON_SINGLE_TARGET="python2_7 python3_5 python3_6 python3_7"
> > PYTHON_TARGETS="python2_7 python3_5 python3_6 python3_7"} Installed
> > versions:  6.2.4.2([2019-06-19 06:18:11])(accessibility cups dbus
> > gtk gtk2 pdfimport -bluetooth -branding -coinmp -debug -eds
> > -firebird -googledrive -gstreamer -java -kde -ldap -mariadb -odk
> > -postgres -test -vlc ELIBC="-FreeBSD"
> > LIBREOFFICE_EXTENSIONS="-nlpsolver -scripting-beanshell
> > -scripting-javascript -wiki-publisher"
> > PYTHON_SINGLE_TARGET="python3_6 -python2_7 -python3_5 -python3_7"
> > PYTHON_TARGETS="python2_7 python3_6 -python3_5 -python3_7")
> > 
> > So, yes (smile).  
> 
> It depends on which VLC plugin is used, KDE, or Gtk.  Go to
> Help/About and you can see when loaded with the KDE VLC plugin the
> 'tab-losing-cell-focus' bug is present.  With the Gtk VLC plugin
> loaded, the tab works as it should.

Unless my eyes are playing tricks on me, I think you mean which VCL
(not VLC) is being used. 

Re: [gentoo-user] What the devil?!! [or Plasma teething problems Ia.]

[Mick]

On Tuesday, 25 June 2019 10:14:59 BST Peter Humphrey wrote:
> On Monday, 24 June 2019 21:19:09 BST Mick wrote:

> > Also, the sddm DM shutdown/reboot buttons now do not work. O_O

> It seems that you're a victim of the hopelessly reticulate interactions
> among plasma components.

Yes, it seems by removing plasma-meta and reinstalling I caused some plasma-
KDE hickup, which a revdep-rebuild following this morning's update is now 
hopefully trying to address. 

-- 
Regards,

Mick

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

Re: [gentoo-user] What the devil?!! [or Plasma teething problems Ia.]

[Mick]

Thank you both for your suggestions,

On Tuesday, 25 June 2019 09:47:16 BST Neil Bothwick wrote:
> On Tue, 25 Jun 2019 00:12:56 +0100, Mick wrote:
> > > > Can someone please explain how the removal of the 'wireless' USE
> > > > flag from powerdevil ends up with no buttons for Suspend-to-RAM,
> > > > Hibernation, Reboot or Shutdown under the Leave tab of the KMenu?
> > > > What does wireless have to do with those functions which should work
> > > > regardless?
> > > 
> > > Those options are still present here.
> > 
> > Thanks Neil, these are the packages which were depcleaned following
> > USE="- wireless" for powerdevil, USE="-espeak" for speech-dispatcher
> 
> > and USE="device- mapper-only -thin" for lvm:
> Has nobody ever told you about changing only one thing at a time? ;_)
> 
> > 1561390348: Started emerge on: Jun 24, 2019 16:32:28
> > 1561390348:  *** emerge --ask --verbose --depclean
> > 1561390348:  >>> depclean
> > 1561390428: === Unmerging... (virtual/w3m-0)
> > 1561390432:  >>> unmerge success: virtual/w3m-0
> > 1561390432: === Unmerging... (virtual/linux-sources-3)
> > 1561390436:  >>> unmerge success: virtual/linux-sources-3
> > 1561390436: === Unmerging... (kde-frameworks/networkmanager-qt-5.57.0)
> > 1561390440:  >>> unmerge success:
> > kde-frameworks/networkmanager-qt-5.57.0 1561390440: === Unmerging...
> > (sys-block/thin-provisioning-tools-0.7.0) 1561390445:  >>> unmerge
> > success: sys-block/thin-provisioning-tools-0.7.0 1561390445: ===
> > Unmerging... (app-accessibility/espeak-1.48.04-r1) 1561390449:  >>>
> > unmerge success: app-accessibility/espeak-1.48.04-r1 1561390449: ===
> > Unmerging... (www-client/w3m-0.5.3_p20180125) 1561390453:  >>> unmerge
> > success: www-client/w3m-0.5.3_p20180125 1561390453: === Unmerging...
> > (media-sound/sox-14.4.2-r1) 1561390458:  >>> unmerge success:
> > media-sound/sox-14.4.2-r1 1561390458: === Unmerging...
> > (net-misc/networkmanager-1.16.0) 1561390464:  >>> unmerge success:
> > net-misc/networkmanager-1.16.0 1561390464: === Unmerging...
> > (net-dialup/ppp-2.4.7-r7) 1561390468:  >>> unmerge success:
> > net-dialup/ppp-2.4.7-r7 1561390468: === Unmerging...
> > (net-misc/dhcp-4.4.1) 1561390473:  >>> unmerge success:
> > net-misc/dhcp-4.4.1 1561390473: === Unmerging...
> > (dev-libs/boehm-gc-7.6.4) 1561390478:  >>> unmerge success:
> > dev-libs/boehm-gc-7.6.4 1561390478: === Unmerging...
> > (media-sound/gsm-1.0.13-r1) 1561390482:  >>> unmerge success:
> > media-sound/gsm-1.0.13-r1 1561390482: === Unmerging...
> > (net-libs/libndp-1.7) 1561390486:  >>> unmerge success:
> > net-libs/libndp-1.7 1561390486: === Unmerging...
> > (net-misc/modemmanager-1.8.2-r1) 1561390493:  >>> unmerge success:
> > net-misc/modemmanager-1.8.2-r1 1561390493: === Unmerging...
> > (dev-libs/newt-0.52.20) 1561390497:  >>> unmerge success:
> > dev-libs/newt-0.52.20 1561390497: === Unmerging...
> > (net-dialup/ppp-scripts-0) 1561390501:  >>> unmerge success:
> > net-dialup/ppp-scripts-0 1561390501: === Unmerging...
> > (sys-libs/slang-2.3.2) 1561390505:  >>> unmerge success:
> > sys-libs/slang-2.3.2 1561390505: === Unmerging...
> > (net-libs/libqmi-1.20.2) 1561390510:  >>> unmerge success:
> > net-libs/libqmi-1.20.2 1561390510: === Unmerging...
> > (net-libs/libmbim-1.16.2) 1561390515:  >>> unmerge success:
> > net-libs/libmbim-1.16.2 1561390515:  *** exiting successfully.
> > 1561390515:  *** terminating.
> > 1561390536: Started emerge on: Jun 24, 2019 16:35:36
> > 1561390536:  *** emerge --ask --verbose @preserved-rebuild
> > 1561390543:  *** exiting successfully.
> > 1561390543:  *** terminating.
> 
> I don't have most of those packages either, I do have w3m and sox but
> you'd have to be pretty desperate to start suspecting them.

I am!  O_O


> [ebuild   R] kde-plasma/powerdevil-5.16.1:5::gentoo
> USE="-brightness-control -debug handbook -wireless" 0 KiB
> 
> It doesn't look like USE affects it either.
> 
> > I can't see anything in there.  I also uninstalled and reinstalled
> > plasma- meta, but did not depclean anything.  Could there be something
> > in systemsettings?  Yep! Power Management is greyed out:
> > 
> > "Power management configuration module could not be loaded. The Power
> > Management Service appears not to be running.  This can be solved by
> > starting or scheduling it inside "Startup and Shutdown".
> > 
> > What am I supposed to add in "Startup and Shutdown"?  There is no Power
> > Management to start up and no button to add any services.  :-/
> 
> I can't see anything power related in there. I have everything but
> automounting enabled.
> 
> Have you tried logging in as a new user, to see if it's a configuration
> option that's wrong somewhere?

I've done one better, installed Enlightenment to try it out on this machine, 
in case it works without intermittently spinning up the CPU when the screen 
goes to sleep, but all the power settings were missing in Enlightenment too.

I run an update today which brought in a new dbus package.  Although 

Re: [gentoo-user] What the devil?!! [or Plasma teething problems Ia.]

[Peter Humphrey]

On Monday, 24 June 2019 21:19:09 BST Mick wrote:
> Can someone please explain how the removal of the 'wireless' USE flag from
> powerdevil ends up with no buttons for Suspend-to-RAM, Hibernation, Reboot
> or Shutdown under the Leave tab of the KMenu?

It doesn't, by itself. I have -wireless set on powerdevil and I have Reboot 
and Shutdown buttons.

> What does wireless have to do with those functions which should work
> regardless?

Nothing, one hopes.

> Also, the sddm DM shutdown/reboot buttons now do not work. O_O
> 
> Is Plasma/KDE trying to emulate the inflexibility of Gnome? (no flamewar
> intended please).

It seems that you're a victim of the hopelessly reticulate interactions among 
plasma components. As I said a minute ago, finding myself similarly afflicted, 
I just had to cut the Gordian knot and start again. (Sorry - a bit of verbal 
diarrhoea there.)

-- 
Regards,
Peter.

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

[Mick]

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

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

[gentoo-user] Re: fdm fails during ./configure: libssl not found

[nunojsilva]

On 2019-06-24, Bryant Morrow wrote:

> ---
>
> fdm-1.9 consistently fails to build, with configure citing a lack of
> libssl as the reason. I have openssl installed, and
> /usr/lib64/libssl.so (symlink to /usr/lib64/libssl.so.1.1) exists.
> I've looked for similar problems online, with no luck. It originally
> seemed to be related to a broken version of openssl being unmasked
> along with the use of ~amd64 in ACCEPT_KEYWORDS, but resolving that
> made no difference. It seems to me that fdm's config scripts simply
> can't find libssl, but they appear to be looking in all of the correct
> places. I had it installed and working in the past, but it was removed
> due to a stupid (on my part) accident with emerge --depclean and now
> fails to reinstall.
>
> Output of emerge -pqv 'net-mail/fdm-1.9::gentoo':
> http://dpaste.com/2B1YBPZ //emerge -pqv
>
> Output of emerge --info 'net-mail/fdm-1.9::gentoo':
> http://dpaste.com/0D1PK0E //emerge --info
>
> Contents of build.log: http://dpaste.com/1CFZF87 //build.log
>
> Contents of portage environment file: http://dpaste.com/2XJD461
> //environment

This looks like bug 677484 - the problem would indeed be the way this
config script tries to detect libssl.

I don't use fdm, but from what I read in the bug report, I suppose you
could try downgrading openssl to 1.0.*, or change the fdm ebuild to
apply the patch from comment 9.

https://bugs.gentoo.org/show_bug.cgi?id=677484

-- 
Nuno Silva

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] What the devil?!! [or Plasma teething problems Ia.]

[Neil Bothwick]

On Tue, 25 Jun 2019 00:12:56 +0100, Mick wrote:

> > > Can someone please explain how the removal of the 'wireless' USE
> > > flag from powerdevil ends up with no buttons for Suspend-to-RAM,
> > > Hibernation, Reboot or Shutdown under the Leave tab of the KMenu?
> > > What does wireless have to do with those functions which should work
> > > regardless?  
> > 
> > Those options are still present here.  
> 
> Thanks Neil, these are the packages which were depcleaned following
> USE="- wireless" for powerdevil, USE="-espeak" for speech-dispatcher
> and USE="device- mapper-only -thin" for lvm:

Has nobody ever told you about changing only one thing at a time? ;_)

> 1561390348: Started emerge on: Jun 24, 2019 16:32:28
> 1561390348:  *** emerge --ask --verbose --depclean
> 1561390348:  >>> depclean
> 1561390428: === Unmerging... (virtual/w3m-0)
> 1561390432:  >>> unmerge success: virtual/w3m-0
> 1561390432: === Unmerging... (virtual/linux-sources-3)
> 1561390436:  >>> unmerge success: virtual/linux-sources-3
> 1561390436: === Unmerging... (kde-frameworks/networkmanager-qt-5.57.0)
> 1561390440:  >>> unmerge success:
> kde-frameworks/networkmanager-qt-5.57.0 1561390440: === Unmerging...
> (sys-block/thin-provisioning-tools-0.7.0) 1561390445:  >>> unmerge
> success: sys-block/thin-provisioning-tools-0.7.0 1561390445: ===
> Unmerging... (app-accessibility/espeak-1.48.04-r1) 1561390449:  >>>
> unmerge success: app-accessibility/espeak-1.48.04-r1 1561390449: ===
> Unmerging... (www-client/w3m-0.5.3_p20180125) 1561390453:  >>> unmerge
> success: www-client/w3m-0.5.3_p20180125 1561390453: === Unmerging...
> (media-sound/sox-14.4.2-r1) 1561390458:  >>> unmerge success:
> media-sound/sox-14.4.2-r1 1561390458: === Unmerging...
> (net-misc/networkmanager-1.16.0) 1561390464:  >>> unmerge success:
> net-misc/networkmanager-1.16.0 1561390464: === Unmerging...
> (net-dialup/ppp-2.4.7-r7) 1561390468:  >>> unmerge success:
> net-dialup/ppp-2.4.7-r7 1561390468: === Unmerging...
> (net-misc/dhcp-4.4.1) 1561390473:  >>> unmerge success:
> net-misc/dhcp-4.4.1 1561390473: === Unmerging...
> (dev-libs/boehm-gc-7.6.4) 1561390478:  >>> unmerge success:
> dev-libs/boehm-gc-7.6.4 1561390478: === Unmerging...
> (media-sound/gsm-1.0.13-r1) 1561390482:  >>> unmerge success:
> media-sound/gsm-1.0.13-r1 1561390482: === Unmerging...
> (net-libs/libndp-1.7) 1561390486:  >>> unmerge success:
> net-libs/libndp-1.7 1561390486: === Unmerging...
> (net-misc/modemmanager-1.8.2-r1) 1561390493:  >>> unmerge success:
> net-misc/modemmanager-1.8.2-r1 1561390493: === Unmerging...
> (dev-libs/newt-0.52.20) 1561390497:  >>> unmerge success:
> dev-libs/newt-0.52.20 1561390497: === Unmerging...
> (net-dialup/ppp-scripts-0) 1561390501:  >>> unmerge success:
> net-dialup/ppp-scripts-0 1561390501: === Unmerging...
> (sys-libs/slang-2.3.2) 1561390505:  >>> unmerge success:
> sys-libs/slang-2.3.2 1561390505: === Unmerging...
> (net-libs/libqmi-1.20.2) 1561390510:  >>> unmerge success:
> net-libs/libqmi-1.20.2 1561390510: === Unmerging...
> (net-libs/libmbim-1.16.2) 1561390515:  >>> unmerge success:
> net-libs/libmbim-1.16.2 1561390515:  *** exiting successfully.
> 1561390515:  *** terminating.
> 1561390536: Started emerge on: Jun 24, 2019 16:35:36
> 1561390536:  *** emerge --ask --verbose @preserved-rebuild
> 1561390543:  *** exiting successfully.
> 1561390543:  *** terminating.

I don't have most of those packages either, I do have w3m and sox but
you'd have to be pretty desperate to start suspecting them.

[ebuild   R] kde-plasma/powerdevil-5.16.1:5::gentoo 
USE="-brightness-control -debug handbook -wireless" 0 KiB

It doesn't look like USE affects it either.

> I can't see anything in there.  I also uninstalled and reinstalled
> plasma- meta, but did not depclean anything.  Could there be something
> in systemsettings?  Yep! Power Management is greyed out:
> 
> "Power management configuration module could not be loaded. The Power 
> Management Service appears not to be running.  This can be solved by
> starting or scheduling it inside "Startup and Shutdown".
> 
> What am I supposed to add in "Startup and Shutdown"?  There is no Power 
> Management to start up and no button to add any services.  :-/
> 

I can't see anything power related in there. I have everything but
automounting enabled.

Have you tried logging in as a new user, to see if it's a configuration
option that's wrong somewhere?


-- 
Neil Bothwick

As long as you do not move you can still choose any direction.


pgpEOhTdTbL7f.pgp
Description: OpenPGP digital signature

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.